Example output:
ch=qam:33 lock=qam256 ss=83(-10dBmV) snq=90(29dB) seq=100 bps=38807712 pps=0
● ch = channel requested
● lock = actual modulation detected
● ss = signal strength.
● snq = signal to noise quality (MER).
● seq = symbol error quality (based on the number of uncorrectable digital errors detected).
● bps = raw channel bits per second.
● pps = packets per second sent through the network.
More advanced information can be obtained by using the get debug command:
Format: hdhomerun_config <device id> get /tuner<n>/debug
Example: hdhomerun_config FFFFFFFF get /tuner0/debug
Example output:
tun: ch=qam:33 lock=qam256 ss=84 snq=88 seq=100 dbg=22081-6930
dev: resync=0 overflow=0
ts: bps=38809216 ut=94 te=0 miss=0 crc=0
flt: bps=38809216
net: pps=0 err=0 stop=0
Each line contains a prefix to indicate the type of data, followed by the values.
● tun = tuner status
○ see above section
● dev = device status
● ts = transport stream
○ bps = bits per second
○ ut = utilization percentage (100% is filled to capacity)
○ te = transport error counter (uncorrectable reception error)
○ miss = missed packet counter (jump in sequence numbers)
○ crc = crc error counter
● flt = results after pid filtering
○ bps = bits per second
● net = network status
○ pps = packets per second
○ err = packets or TS frames dropped before transmission.
○ stop = reason for stopping the stream
The counters are reset to zero upon a channel change, but may indicate a small number of errors
caused before the tuner locks on the channel. As a result, diagnostics should be based on the
change in values over time, and not the initial values.
To Next Page
Loading...
