QAMTrak Overview PDF

PathTrak QAMTrakTM Analyzer
Featuring LivePacketTM Technology

Available now on all RPM3000
monitored nodes
PathTrak RPM3000 Technology
LivePacket™ Technology - Demodulates LIVE DOCSIS upstreams
– Reveals linear and non-linear impairments within the carrier, not just simple ingress
• Group delay, microreflection, laser clipping, compression
– Provides real-time MER and other health measurements on subscribers’ DOCSIS packets
– Provides consistency across enterprise versus CMTS data – values independent of CMTS HW
or firmware versions
QAMTrakTM QAM analyzer (with embedded LivePacketTM)

– Determine root cause of impairments before rolling a truck using traditional spectrum and
LivePacketTM technology
– Demodulate inserted out-of-band QAM carriers from DSAM to troubleshoot adjacent carriers or
test for new carriers
– Eliminates need for traditional standalone QAM/spectrum analyzer for troubleshooting return
paths
– Updates in real-time for live troubleshooting, unlike stale CMTS data
Extended Frequency and Dynamic Range

– .5MHz to 85MHz
• See below 5Mhz for AM ingress
• See laser clipping effects beyond return path band
• Full support for DOCSIS3.0 frequency range
– 50dB dynamic range
• Useful for low noise floor seen on 64QAM upstreams
Fully compatible with RPM1000/2000
2 © 2009 JDSU. All rights reserved. JDSU CONFIDENTIAL & PROPRIETARY INFORMATION
QAM Analyzer Display (PathTrak Client Shown)
Constellation Display:
The number of grids on the
constellation will change with
modulation type selected
White dots are the latest packet

demodulated or selected packet in a
paused display
Green points are all of the packets

which have been demodulated in
current session or since last reset
What is a “Paused Display”

Live QAM Analyzer sessions can be paused and packets viewed one by one
– Pause button ( ) on the toolbar pauses display, Arrow buttons ( ) on the toolbar or cursor
allow scrolling through captured packets
Average/Min/Max Stats:
MER (dB) – Average, min, max MER
for all packets captured in current
session or since last reset
Level (dBmV, dBm or dBuV) –
Average, min, max level for all packets
captured in current session or since
last reset
– Indication if some modems transmitting
too high or too low
– RF too high: can lead to laser
saturation or clipping
– RF too low: can leave modes
susceptible to noise
• May indicate modems incapable of
reaching CMTS at requested level due
to customer prem wiring issues, plant
alignment, others
– Oscillating levels may indicate rapidly
changing RF plant
• Caused by loose seizure screw, cracked
hardline, others
Latest Packet Stats:

Time - Time the most recent packet
or selected packet in a paused or
imported display was captured
MER (dB) – MER for the most

recent packet captured or selected
packet in a paused display
Level (dBmV, dBm or dBuV) - for the

most recent packet captured or
selected packet in a paused display
Symbols – The number of symbols

captured in the packet
Strip Chart:
Chart traces represent MER and Level for
up to the most recent 600 packets
demodulated
– Most recent packets are on the right edge,
oldest packets are on the left edge of the
strip chart
Green trace represents unequalized MER

– MER scale is on the left Y-Axis
Blue trace (Level) represents the power

of the entire carrier
– Level scale is on the right Y-Axis
QAM Analyzer Window – Normal vs Bad Node
Normal Node:
Minimal variation Relatively tight symbol
in symbol
location in QAM dispersion in constellation
constellation Relatively consistent MER
across QAM Analyzer session
Minimal variation in MER well above 21dB
MER/Level in strip suggested certification limit
chart
Bad Node:
Interference easily
Much variation in symbol
visible in QAM location within constellation
constellation
cells
Large variation in MER packet
to packet
Interference causing
intermittent low MER
Many packets below 18dB
functional minimum
Common Impairments as Viewed in PathTrak QAM Analyzer
Gaussian Noise / White Noise
Walsh Clip 12 I52 noisy QA.JPG

SA.JPG

This is perhaps the most common type of impairment
Display will generally have a random pattern for affected packets
– Increased variation in symbol location will cause constellation display to “bloom”
Usually caused by ingress into HFC
Most common source is between tap and CPE, can also be corroded connectors, poor
termination, or other outside plant impairments
Viewing exported or paused constellation views packet by packet can yield clues as to
similarities between the footprints of low MER packets

Uniform round blooming of constellation
cells suggests Gaussian noise as source
of impairment (Top right picture)
Relatively consistent MER across time

(green trace) with little packet to packet
variation also suggest Gaussian noise
(bottom right picture)
Impulse Noise
Impulse Noise:
Display will sometimes show just a few symbols
randomly scattered when impulse noise is present
– Note the white dots in the screen capture (The last
packet captured)
– This pattern is likely the result of an impulse noise
issue
Impulse noise may also manifest as a single burst

with much greater than average random variation
across all symbols
– Note the white dots in the screen capture (The last
packet captured)
– This pattern is likely the result of an impulse noise
issue
Coherent Interference
Coherent Interference:
If the accumulation looks like a “donut”, the problem is likely coherent
interference
– Often caused by off-air ingress such as citizens band radio, shortwave
radio, or other AM-based ingress sources
– May also be caused by FSK signal
Common Impairments: Group Delay / Microreflections
Group Delay / Microreflections:

If the accumulation takes on a diamond shape, the problem is likely a group
delay issue
– Constellation may take on a diamond or square shape
– Clarity of diamond shape will vary with percentage of packets affected
– Microreflections are a common cause of group delay
– Often caused by unterminated or improperly terminated lines or faulty CPE (cheap
TV or VCR)
– Group delay can also result from a carrier placed too close to the band edge of the
diplex filter
Case Study: Group Delay Caused By Carrier Placement
Too Close to Band Edge of Diplex Filter
Case Study Setup:
Inject QAM signal into HFC
plant using DSAM meter
Carrier:
36 MHz Vary carrier center frequency
until diplex roll-off impact is
observed
Setup Details:
– 16QAM carrier
– 5.12 MSPS symbol rate
Carrier:
– 6.4 MHz Bandwidth
38 MHz
– 42MHz diplex filter
Conclusion:
– Group Delay can be induced
as a QAM carrier edge
approaches the diplex roll-off
Carrier:
39 MHz
Amplifier Compression / Laser Clipping
Amplifier Compression:
Amplifier compression often manifests as rounding
of the corners of the constellation
Usually caused by overdriving an amplifier usually
due to ingress or misalignment (unity gain)
Laser Clipping:
Laser clipping often manifests as increased spread
in the corners of the constellation
Often caused by overdriving a laser usually due to
ingress or misalignment (unity gain)
Troubleshooting Methods For In-Band Linear Impairments
Scenario: Customer Trouble Ticket comes in for poor voice quality (VOIP service)
Spectrum Analyzer looks clean for affected node

return path as viewed from the headend
QAMTrakTM analyzer as viewed from headend

shows good average MER, occasional packets
with diamond-shape in constellation
– Indicates likely a localized group delay issue
Truck is rolled to
affected customer
premises
DSAM used to inject QAM carrier at ground block, constellation/MER viewed via
WebView QAMTrak on laptop with wireless card
– Constellation shows diamond pattern, strip chart shows nearly all packets affected
Carrier injected at output side of tap
– Constellation shows diamond pattern, strip chart shows nearly all packets affected
Carrier injected at output side of tap

– Constellation still shows diamond pattern
Carrier injected at input side of tap

• Constellation appears normal
Conclusion: Source of group delay lives

between tap input and tap output
Likely improperly terminated tap port on low

value tap
Why Add RPM3000 Cards to Your Return Path Toolbox?
RPM3000 cards enable access to PathTrak’s exclusive LivePacket Technology
Only with Livepacket can you :

– Demodulate live inservice packets in a bursty upstream
– See linear impairments in revenue-generating carriers such as group delay and laser
clipping commonly invisible to traditional spectrum analyzers
– Receive real-time MER and other health measurements on subscribers’ DOCSIS
packets
RPM3000 cards are fully compatible with existing PathTrak systems

– RPM1000/2000 cards can coexist with RPM3000 cards in the same HCU!
When is the right time to add RPM3000 cards to your system:

– Node splits – Have QAMTrak available on every node that you add
– Add at least one RPM3000 per headend/hub for on-demand troubleshooting uses
– Upgrade by exchange program makes it easier to upgrade your troubleshooting and
monitoring capabilities by swapping out existing cards for RPM3000’s

QAMTrak Overview PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

QAMTrak Overview PDF

Uploaded by

Copyright:

Available Formats

PathTrak QAMTrakTM Analyzer

Featuring LivePacketTM Technology

QAMTrakTM QAM analyzer (with embedded LivePacketTM)

Extended Frequency and Dynamic Range

Fully compatible with RPM1000/2000

White dots are the latest packet

Green points are all of the packets

What is a “Paused Display”

Latest Packet Stats:

MER (dB) – MER for the most

Level (dBmV, dBm or dBuV) - for the

Symbols – The number of symbols

Green trace represents unequalized MER

Blue trace (Level) represents the power

Walsh Clip 12 I52 noisy QA.JPG

Gaussian Noise / White Noise

Gaussian Noise / White Noise

Relatively consistent MER across time

Impulse noise may also manifest as a single burst

Group Delay / Microreflections:

Spectrum Analyzer looks clean for affected node

QAMTrakTM analyzer as viewed from headend

Carrier injected at output side of tap

Carrier injected at input side of tap

Conclusion: Source of group delay lives

Likely improperly terminated tap port on low

RPM3000 cards enable access to PathTrak’s exclusive LivePacket Technology

Only with Livepacket can you :

RPM3000 cards are fully compatible with existing PathTrak systems

When is the right time to add RPM3000 cards to your system:

You might also like