Continuity Counter Errors
Posted: Mon Mar 04, 2013 3:24 pm
I am suffering from continuity counter errors despite having a seemingly fine signal on the affected tuner (SNR > 90%). I can reproduce one failure mode using the test script below. When one tuner is in use there are no cc errors, when the other three tuners are enabled I start getting errors as can be seen in the log on pastebin (search for "continuity error"). The signal still seems fine on the affected tuner and BER=0. The failure is reproducible when tuned to this specific mux, 10903 V on Thor 0.8W (http://www.lyngsat.com/packages/canaldigital.html).
What are the possible causes of these cc errors?
I am running Ubuntu Server 12.04 x64 with drivers v130127.
Test script:
The output log can be found on pastebin:
http://pastebin.com/e7V8CJ1L
What are the possible causes of these cc errors?
I am running Ubuntu Server 12.04 x64 with drivers v130127.
Test script:
- Code: Select All Code
uname -a
date
echo "Enable adapter 0"
szap-s2 -H -a 0 -n 1 -S 1 -r &
sleep 2
dvbsnoop -adapter 0 -s feinfo
dvbsnoop -adapter 0 -s signal -n 2
dvbsnoop -adapter 0 -s bandwidth -tsraw -n 2000
dvbsnoop -adapter 0 -s pidscan
dvbsnoop -adapter 0 -nohexdumpbuffer -pd 3 -s ts -tsraw | awk -v a=adapter0 '/continuity error/ { "date +%T" | getline d; print d, ": ", a, ": ", $0; close("date +%T") }' &
sleep 200
date
echo "Enable remaining adapters"
szap-s2 -a 1 -n 3 -r > /dev/null &
sleep 2
szap-s2 -a 2 -n 4 -r > /dev/null &
sleep 2
szap-s2 -a 3 -n 8 -r > /dev/null &
sleep 2
echo "Adapter 0 signal:"
dvbsnoop -adapter 0 -s signal -n 2
echo "Adapter 1 signal:"
dvbsnoop -adapter 1 -s signal -n 2
echo "Adapter 2 signal:"
dvbsnoop -adapter 2 -s signal -n 2
echo "Adapter 3 signal:"
dvbsnoop -adapter 3 -s signal -n 2
sleep 200
killall -PIPE dvbsnoop
killall szap-s2
The output log can be found on pastebin:
http://pastebin.com/e7V8CJ1L