Project

General

Profile

[Solved] EIT causing "Continuity counter error" and "Transport error indicator" ?

Added by Anti S almost 7 years ago

Hello to all.

My current Tvheadend setup:

Motheboard: Gigabyte GA-N3150N-D2H
RAM: 4GB
TV card: TBS6205 DVB-T2/T/C Quad TV Tuner PCIe Card (using in DVB-C mode)
Operating system: Ubuntu 16.04.3 LTS
Kernel: 4.8.0-58-generic
Driver: tbs-open-linux-drivers_v171016.zip
Tvheadend version: 4.2.5-18~g951777a~xenial
OSCam version: svn11398
Smartcard Reader: 08e6:3437 Gemalto (was Gemplus) GemPC Twin SmartCard Reader
Service Provider: Estonian cable operator STV

I have experianced for some time an issue where I get continuity counter errors and transport error indicators randomly during watching live or recording a broadcast. Randomy means couple of times during two hours or once in an hour.

I have debugged the problem now by letting Tvheadend record a bunch of content and examining the log. What I witness in my logs are the following situations (in short):

...
2018-02-05 01:14:13.721 [ DEBUG]:tbl-base: sdt: completed pid 17 table 00000040 / 000000f8
2018-02-05 01:14:18.705 [ DEBUG]:tbl-base: sdt: onid 0064 (100) tsid 0006 (6)
2018-02-05 01:14:18.705 [ DEBUG]:tbl-base: sdt: mux 346MHz in STV
2018-02-05 01:14:18.705 [ DEBUG]:tbl-base: sdt: sid 00CA (202) running 0 free_ca 1
2018-02-05 01:14:18.705 [ DEBUG]:tbl-base: sdt: sid 00D5 (213) running 4 free_ca 1
2018-02-05 01:14:18.705 [ DEBUG]:tbl-base: sdt: sid 00CB (203) running 4 free_ca 1
2018-02-05 01:14:18.705 [ DEBUG]:tbl-base: sdt: sid 00C9 (201) running 4 free_ca 1
2018-02-05 01:14:18.705 [ DEBUG]:tbl-base: sdt: sid 00D4 (212) running 4 free_ca 1
2018-02-05 01:14:18.705 [ DEBUG]:tbl-base: sdt: sid 00D0 (208) running 4 free_ca 1
2018-02-05 01:14:18.705 [ DEBUG]:tbl-base: sdt: sid 00CD (205) running 0 free_ca 1
2018-02-05 01:14:18.705 [ DEBUG]:tbl-base: sdt: sid 00D6 (214) running 4 free_ca 1
2018-02-05 01:14:18.705 [ DEBUG]:tbl-base: sdt: sid 00D2 (210) running 4 free_ca 1
2018-02-05 01:14:18.705 [ DEBUG]:tbl-base: sdt: sid 00CE (206) running 0 free_ca 1
2018-02-05 01:14:18.705 [ DEBUG]:tbl-base: sdt: sid 00CC (204) running 4 free_ca 1
2018-02-05 01:14:18.705 [ DEBUG]:tbl-base: sdt: completed pid 17 table 00000040 / 000000f8
2018-02-05 01:14:29.608 [WARNING]:TS: STV/306MHz/TV3 Transport error indicator (total 2)
2018-02-05 01:14:29.613 [ DEBUG]:tbl-eit: eit: 306MHz in STV: PID 0012 CC error 7 != 3

2018-02-05 01:14:34.346 [ DEBUG]:cwc: Sending ECM (PID 5103) section=0/0, for service "TV3" (seqno: 10301)
2018-02-05 01:14:34.738 [ DEBUG]:cwc: Received ECM reply (PID 5103) for service "TV3" [0] even: c3.af.37.a9.02.58.8f.e9 odd: f8.a8.51.f1.d4.7f.23.76 (seqno: 10301 Req delay: 387 ms)
2018-02-05 01:14:34.738 [ DEBUG]:descrambler: info - service='TV3' caid=0B00(Conax) provid=000000 ecmtime=387 hops=1 reader='' from='localhost:xxxxx' protocol='newcamd'
2018-02-05 01:14:52.867 [ DEBUG]:tbl-base: sdt: onid 0064 (100) tsid 0025 (37)
2018-02-05 01:14:52.867 [ DEBUG]:tbl-base: sdt: mux 618MHz in STV
2018-02-05 01:14:52.867 [ DEBUG]:tbl-base: sdt: sid 0E7A (3706) running 4 free_ca 1
2018-02-05 01:14:52.867 [ DEBUG]:tbl-base: sdt: sid 0E79 (3705) running 4 free_ca 1
2018-02-05 01:14:52.867 [ DEBUG]:tbl-base: sdt: sid 0E78 (3704) running 4 free_ca 1
2018-02-05 01:14:52.867 [ DEBUG]:tbl-base: sdt: sid 0E77 (3703) running 4 free_ca 1
2018-02-05 01:14:52.867 [ DEBUG]:tbl-base: sdt: sid 0E76 (3702) running 4 free_ca 1
2018-02-05 01:14:52.867 [ DEBUG]:tbl-base: sdt: sid 0E75 (3701) running 0 free_ca 1
2018-02-05 01:14:52.867 [ DEBUG]:tbl-base: sdt: completed pid 17 table 00000040 / 000000f8
...
2018-02-05 03:33:58.654 [ DEBUG]:tbl-base: sdt: completed pid 17 table 00000040 / 000000f8
2018-02-05 03:34:13.664 [WARNING]:TS: STV/306MHz/TV3 Transport error indicator (total 6)
2018-02-05 03:34:13.668 [ DEBUG]:tbl-eit: eit: 306MHz in STV: PID 0012 CC error 14 != 11

2018-02-05 03:34:23.680 [ DEBUG]:tbl-base: sdt: onid 0064 (100) tsid 0021 (33)
2018-02-05 03:34:23.680 [ DEBUG]:tbl-base: sdt: mux 602MHz in STV
2018-02-05 03:34:23.680 [ DEBUG]:tbl-base: sdt: sid 0CEC (3308) running 4 free_ca 1
2018-02-05 03:34:23.680 [ DEBUG]:tbl-base: sdt: sid 0CE6 (3302) running 4 free_ca 1
2018-02-05 03:34:23.680 [ DEBUG]:tbl-base: sdt: sid 0CEE (3310) running 4 free_ca 1
2018-02-05 03:34:23.680 [ DEBUG]:tbl-base: sdt: sid 0CE7 (3303) running 4 free_ca 1
2018-02-05 03:34:23.680 [ DEBUG]:tbl-base: sdt: sid 0CED (3309) running 4 free_ca 1
2018-02-05 03:34:23.680 [ DEBUG]:tbl-base: sdt: sid 0CE5 (3301) running 4 free_ca 1
2018-02-05 03:34:23.681 [ DEBUG]:tbl-base: sdt: sid 0CE9 (3305) running 4 free_ca 1
2018-02-05 03:34:23.681 [ DEBUG]:tbl-base: sdt: sid 0CEB (3307) running 4 free_ca 1
2018-02-05 03:34:23.681 [ DEBUG]:tbl-base: sdt: sid 0CEA (3306) running 0 free_ca 1
2018-02-05 03:34:23.681 [ DEBUG]:tbl-base: sdt: completed pid 17 table 00000040 / 000000f8
2018-02-05 03:34:24.547 [ DEBUG]:cwc: Sending ECM (PID 5103) section=0/0, for service "TV3" (seqno: 14524)
2018-02-05 03:34:24.956 [ DEBUG]:cwc: Received ECM reply (PID 5103) for service "TV3" [0] even: 78.62.f2.cc.44.be.f6.f8 odd: ba.c2.73.ef.22.c6.c4.ac (seqno: 14524 Req delay: 407 ms)
2018-02-05 03:34:24.956 [ DEBUG]:descrambler: info - service='TV3' caid=0B00(Conax) provid=000000 ecmtime=407 hops=1 reader='' from='localhost:xxxxx' protocol='newcamd'
2018-02-05 03:34:28.691 [ DEBUG]:tbl-base: sdt: onid 0064 (100) tsid 0021 (33)
...
2018-02-05 04:48:50.223 [ DEBUG]:tbl-base: sdt: completed pid 17 table 00000040 / 000000f8
2018-02-05 04:48:51.033 [ DEBUG]:cwc: Sending ECM (PID 5103) section=0/0, for service "TV3" (seqno: 16774)
2018-02-05 04:48:51.435 [ DEBUG]:cwc: Received ECM reply (PID 5103) for service "TV3" [0] even: fa.f4.54.42.63.c1.57.7b odd: f0.f3.2c.0f.7c.44.f0.b0 (seqno: 16774 Req delay: 403 ms)
2018-02-05 04:48:51.436 [ DEBUG]:descrambler: info - service='TV3' caid=0B00(Conax) provid=000000 ecmtime=403 hops=1 reader='' from='localhost:xxxxx' protocol='newcamd'
2018-02-05 04:48:53.081 [ DEBUG]:tbl-eit: eit: 306MHz in STV: PID 0012 CC error 2 != 14
2018-02-05 04:48:53.111 [WARNING]:TS: STV/306MHz/TV3: MPEG2VIDEO #301 Continuity counter error (total 2)
2018-02-05 04:48:53.111 [WARNING]:TS: STV/306MHz/TV3: MPEG2AUDIO
#302 Continuity counter error (total 1)
2018-02-05 04:48:57.662 [ DEBUG]:tbl-base: sdt: onid 0064 (100) tsid 0025 (37)
2018-02-05 04:48:57.662 [ DEBUG]:tbl-base: sdt: mux 618MHz in STV
2018-02-05 04:48:57.662 [ DEBUG]:tbl-base: sdt: sid 0E7A (3706) running 4 free_ca 1
2018-02-05 04:48:57.662 [ DEBUG]:tbl-base: sdt: sid 0E79 (3705) running 4 free_ca 1
...
2018-02-05 06:53:30.007 [ INFO]:dvr: About to set stop timer for "Paw Patrol" on "Nickelodeon" at start 1517806500 and original stop 1517807400 and overall stop at 1517808900
2018-02-05 06:53:30.009 [ DEBUG]:service: 3: Nickelodeon si 0x7fc7e80090f0 TurboSight TBS 6205 DVB-T/T2/C #3 : DVB-C #0 weight 0 prio 110 error 0
2018-02-05 06:53:30.009 [ DEBUG]:service: 12: Nickelodeon si 0x7fc7e8030060 TurboSight TBS 6205 DVB-T/T2/C #0 : DVB-C #0 weight 0 prio 210 error 0
2018-02-05 06:53:30.009 [ DEBUG]:service: 9: Nickelodeon si 0x7fc7e8016ba0 TurboSight TBS 6205 DVB-T/T2/C #1 : DVB-C #0 weight 0 prio 310 error 0
2018-02-05 06:53:30.009 [ DEBUG]:service: 6: Nickelodeon si 0x7fc7e801af50 TurboSight TBS 6205 DVB-T/T2/C #2 : DVB-C #0 weight 0 prio 410 error 0
2018-02-05 06:53:30.009 [ INFO]:mpegts: 322MHz in STV - tuning on TurboSight TBS 6205 DVB-T/T2/C #2 : DVB-C #0
2018-02-05 06:53:30.009 [ DEBUG]:linuxdvb: TurboSight TBS 6205 DVB-T/T2/C #2 : DVB-C #0 - starting 322MHz in STV
2018-02-05 06:53:30.009 [ DEBUG]:mpegts: 322MHz in STV - started
2018-02-05 06:53:30.009 [ DEBUG]:mpegts: 322MHz in STV - open PID 0012 (18) [20/0x7fc7e8007760]
2018-02-05 06:53:30.010 [ DEBUG]:tbl-eit: eit: installed table handlers
2018-02-05 06:53:30.010 [ DEBUG]:tbl-eit: eit: grab started
2018-02-05 06:53:30.011 [ DEBUG]:mpegts: 322MHz in STV - open PID 0384 (900) [8/0x560b98af8310]
2018-02-05 06:53:30.011 [ DEBUG]:mpegts: 322MHz in STV - open PID 0385 (901) [8/0x560b98af8310]
2018-02-05 06:53:30.011 [ DEBUG]:mpegts: 322MHz in STV - open PID 0386 (902) [8/0x560b98af8310]
2018-02-05 06:53:30.011 [ DEBUG]:mpegts: 322MHz in STV - open PID 0387 (903) [8/0x560b98af8310]
2018-02-05 06:53:30.011 [ DEBUG]:mpegts: 322MHz in STV - open PID 0388 (904) [8/0x560b98af8310]
2018-02-05 06:53:30.011 [ DEBUG]:mpegts: 322MHz in STV - open PID 0384 (900) [16/0x7fc7e8004be0]
2018-02-05 06:53:30.011 [ DEBUG]:cwc: STV/322MHz/Nickelodeon using CWC localhost:xxxxx
2018-02-05 06:53:30.011 [ INFO]:subscription: 0032: "DVR: Paw Patrol" subscribing on channel "Nickelodeon", weight: 300, adapter: "TurboSight TBS 6205 DVB-T/T2/C #2 : DVB-C #0", network: "STV", mux: "322MHz", provider: "STV", service: "Nickelodeon", profile="matroska"
2018-02-05 06:53:30.061 [WARNING]:linuxdvb: Unhandled ERROR_BLOCK_COUNT scale: 0
2018-02-05 06:53:30.166 [ DEBUG]:linuxdvb: TurboSight TBS 6205 DVB-T/T2/C #2 : DVB-C #0 - status GOOD (SIGNAL | CARRIER | VITERBI | SYNC | LOCK)
2018-02-05 06:53:30.167 [ DEBUG]:linuxdvb: TurboSight TBS 6205 DVB-T/T2/C #2 : DVB-C #0 - locked
2018-02-05 06:53:30.168 [ DEBUG]:mpegts: 322MHz in STV - open PID 0000 (0) [20/0x7fc7e8006060]
2018-02-05 06:53:30.168 [ DEBUG]:mpegts: 322MHz in STV - open PID 0001 (1) [16/0x7fc7e80179b0]
2018-02-05 06:53:30.168 [ DEBUG]:mpegts: 322MHz in STV - open PID 0010 (16) [16/0x7fc7e8018e30]
2018-02-05 06:53:30.168 [ DEBUG]:mpegts: 322MHz in STV - open PID 0011 (17) [20/0x7fc7e8009a90]
2018-02-05 06:53:30.168 [ DEBUG]:mpegts: 322MHz in STV - open PID 0011 (17) [16/0x7fc7e800af10]
2018-02-05 06:53:30.181 [ DEBUG]:mpegts: 322MHz in STV - open PID 14BD (5309) [32/0x7fc7e8015430]
2018-02-05 06:53:30.181 [ DEBUG]:service: STV/322MHz/Nickelodeon: Status changed to [Hardware input]
2018-02-05 06:53:30.181 [ DEBUG]:service: STV/322MHz/Nickelodeon: Status changed to [Hardware input] [Input on service]
2018-02-05 06:53:30.181 [ DEBUG]:service: STV/322MHz/Nickelodeon: Status changed to [Hardware input] [Input on service] [No access]
2018-02-05 06:53:30.181 [ DEBUG]:service: STV/322MHz/Nickelodeon: Status changed to [Hardware input] [Input on service] [Demuxed packets] [No access]
2018-02-05 06:53:30.211 [ DEBUG]:tbl-base: nit: network 0064 (100) [STV]
2018-02-05 06:53:30.211 [ DEBUG]:tbl-base: nit: DVB-C freq 306000000 sym 6956000 mod QAM/256 fec AUTO
2018-02-05 06:53:30.211 [ DEBUG]:tbl-base: nit: onid 0064 (100) tsid 0001 (1) mux 306MHz in STV
2018-02-05 06:53:30.211 [ DEBUG]:tbl-base: nit: service 038F (911) type 01 (1)
2018-02-05 06:53:30.211 [ DEBUG]:tbl-base: nit: service 0388 (904) type 01 (1)
...
2018-02-05 06:57:46.002 [ DEBUG]:tbl-base: sdt: mux 346MHz in STV
2018-02-05 06:57:46.002 [ DEBUG]:tbl-base: sdt: sid 00CA (202) running 0 free_ca 1
2018-02-05 06:57:46.002 [ DEBUG]:tbl-base: sdt: sid 00D5 (213) running 4 free_ca 1
2018-02-05 06:57:46.002 [ DEBUG]:tbl-base: sdt: sid 00CB (203) running 4 free_ca 1
2018-02-05 06:57:46.002 [ DEBUG]:tbl-base: sdt: sid 00C9 (201) running 4 free_ca 1
2018-02-05 06:57:46.002 [ DEBUG]:tbl-base: sdt: sid 00D4 (212) running 4 free_ca 1
2018-02-05 06:57:46.002 [ DEBUG]:tbl-base: sdt: sid 00D0 (208) running 4 free_ca 1
2018-02-05 06:57:46.002 [ DEBUG]:tbl-base: sdt: sid 00CD (205) running 0 free_ca 1
2018-02-05 06:57:46.002 [ DEBUG]:tbl-base: sdt: sid 00D6 (214) running 4 free_ca 1
2018-02-05 06:57:46.002 [ DEBUG]:tbl-base: sdt: sid 00D2 (210) running 4 free_ca 1
2018-02-05 06:57:46.002 [ DEBUG]:tbl-base: sdt: sid 00CE (206) running 0 free_ca 1
2018-02-05 06:57:46.002 [ DEBUG]:tbl-base: sdt: sid 00CC (204) running 4 free_ca 1
2018-02-05 06:57:46.002 [ DEBUG]:tbl-base: sdt: completed pid 17 table 00000040 / 000000f8
2018-02-05 06:57:48.168 [ DEBUG]:cwc: Sending ECM (PID 5309) section=0/0, for service "Nickelodeon" (seqno: 17608)
2018-02-05 06:57:48.568 [ DEBUG]:cwc: Received ECM reply (PID 5309) for service "Nickelodeon" [0] even: c6.3f.4a.4f.7b.9e.61.7a odd: 7e.e2.05.65.09.52.fd.58 (seqno: 17608 Req delay: 399 ms)
2018-02-05 06:57:48.568 [ DEBUG]:descrambler: info - service='Nickelodeon' caid=0B00(Conax) provid=000000 ecmtime=399 hops=1 reader='' from='localhost:xxxxx' protocol='newcamd'
2018-02-05 06:57:50.704 [WARNING]:TS: STV/322MHz/Nickelodeon Transport error indicator (total 1)
2018-02-05 06:57:50.709 [ DEBUG]:tbl-eit: eit: 322MHz in STV: PID 0012 CC error 14 != 13
2018-02-05 06:57:50.709 [ DEBUG]:tbl-eit: eit: 322MHz in STV: PID 0012 CC error 0 != 15
2018-02-05 06:57:50.709 [ DEBUG]:tbl-eit: eit: 322MHz in STV: PID 0012 CC error 2 != 1
2018-02-05 06:57:51.245 [ DEBUG]:tbl-base: sdt: onid 0064 (100) tsid 0009 (9)
2018-02-05 06:57:51.245 [ DEBUG]:tbl-base: sdt: mux 370MHz in STV
2018-02-05 06:57:51.245 [ DEBUG]:tbl-base: sdt: sid 01FE (510) running 4 free_ca 1
2018-02-05 06:57:51.245 [ DEBUG]:tbl-base: sdt: sid 01F8 (504) running 4 free_ca 1
2018-02-05 06:57:51.245 [ DEBUG]:tbl-base: sdt: sid 01FB (507) running 0 free_ca 1
2018-02-05 06:57:51.245 [ DEBUG]:tbl-base: sdt: sid 01FC (508) running 0 free_ca 1
2018-02-05 06:57:51.245 [ DEBUG]:tbl-base: sdt: sid 01FF (511) running 4 free_ca 1
2018-02-05 06:57:51.245 [ DEBUG]:tbl-base: sdt: sid 01F7 (503) running 4 free_ca 0
2018-02-05 06:57:51.245 [ DEBUG]:tbl-base: sdt: sid 01F6 (502) running 4 free_ca 1
2018-02-05 06:57:51.245 [ DEBUG]:tbl-base: sdt: sid 01FA (506) running 4 free_ca 1
2018-02-05 06:57:51.245 [ DEBUG]:tbl-base: sdt: sid 01F9 (505) running 4 free_ca 1
2018-02-05 06:57:51.245 [ DEBUG]:tbl-base: sdt: sid 0200 (512) running 4 free_ca 1
2018-02-05 06:57:51.245 [ DEBUG]:tbl-base: sdt: sid 01F5 (501) running 4 free_ca 1
2018-02-05 06:57:51.245 [ DEBUG]:tbl-base: sdt: completed pid 17 table 00000040 / 000000f8
...

EPG grabber in use is "Over-The-Air EIT: DVB Gabber".

Could someone shed some light on this why those CC and TS errors actually happen :-) ? Or is it just me who cannot configure the service properly?

Thank you in advance,

Anti.


Replies (3)

RE: EIT causing "Continuity counter error" and "Transport error indicator" ? - Added by Anti S over 6 years ago

same thing happens with 4.3-1039~gd1c9d1f~xenial:

...
2018-02-08 06:50:13.393 [ DEBUG]:tbl-base: sdt: completed pid 17 table 00000040 / 000000f8
2018-02-08 06:50:19.648 [WARNING]:TS: STV/322MHz/Nickelodeon Transport error indicator (total 1)
2018-02-08 06:50:19.650 [ DEBUG]:tbl-eit: eit: 322MHz in STV: PID 0012 CC error 6 != 5
2018-02-08 06:50:19.673 [WARNING]:TS: STV/322MHz/Nickelodeon: MPEG2VIDEO @ #901 Continuity counter error (total 1)
2018-02-08 06:50:20.222 [ DEBUG]:tbl-base: sdt: onid 0064 (100) tsid 000B (11)
2018-02-08 06:50:20.222 [ DEBUG]:tbl-base: sdt: mux 386MHz in STV
...

RE: EIT causing "Continuity counter error" and "Transport error indicator" ? - Added by Anti S over 6 years ago

Out of the blue those errors were gone.

One vague hint might be that my service provider is in the middle of upgrading it's whatever core equipment ("more capacity", "more reliability" etc). As I have changed nothing this is currenty the only reasonable reason so far.

So obviously original problem is not related with TVHeadend and also not with kernel module.

RE: [Solved] EIT causing "Continuity counter error" and "Transport error indicator" ? - Added by Anti S over 6 years ago

After pushing it more after similar occurrences the official statement from my service provider is that yes, those kind of errors are coming from them. The reason is that the signal they receive via satellite is sometimes unclean and it is then relayed to the DVB-C network as is.

    (1-3/3)