Continuity counter errors - VERY interesting discovery for my CC problems - only every 2nd tuner of my 8 tuners causes this?! - Tvheadend

Continuity counter errors - VERY interesting discovery for my CC problems - only every 2nd tuner of my 8 tuners causes this?!

Hi all

I have been struggling back and forth with the infamous continuity errors for a year.
On some versions it has been very good with no CC errors at all (except during very heavy thunderstorms which must be seen as normal).

Latest unstable 3.9.1353 (precise-amd64) has been very stable and I am very happy with this release.

I am running on Ubuntu 12.04 LTS updated with all the latest patches.
The TV server I am running TVH on is Intel Quad Core I3-2120 @ 3.30GHz with 16 GB RAM.

The tuner cards are 2 PCIe cards from Digital Devices, the Cine S2 cards with 2 tuners originally on the card but I have added the option DuoFlex S2 which expands each card to 4 tuners each, i.e. I have totally 8 tuners connected to my satellite dish that has an octo LNB.
(Tuner card info: http://www.digitaldevices.de/english/DDD-Images/Cine_S2_engl_02-2013.pdf)

I have measured the signal and quality strength at the connector end that is connected to the tuner cards. I have measured with a SatLink WS-6926 (http://www.satlink.de/satlink-ws-6926-hd-second-edition.html) and all 8 cables are showing anywhere from 75 to 85% signal strenght as well as 72 to 82% signal quality. So no problem with the signal coming into my tuner cards.

I am using the drivers found at http://linuxtv.org/hg/~endriss/media_build_experimental/ and I have followed the instruction at

http://shop.digital-devices.de/epages/62357162.sf/?ObjectPath=/Shops/62357162/Categories/DownloadsNew1/Linux_Unterstuetzung_fuer_Digital_Devices_Produkte

Initially I suspected that the reason for my CC errors/problems were to one or two defective tuners on one of the tuner cards since I always got CC errors on Tuner 2 and 4 but after more testing and research I discovered the following VERY strange pattern:

If I have ALL 8 tuners enabled in TVH configuration I always get CC errors (for HD channels only!) if TVH uses ANY of the seconday tuners?! So on the first Cine S2 the 2nd tuner creates CC errors and on the 2nd tuner on the DuoFlex S2 card (the addon card on the first main card).
Same thing on my 2nd main card Cine S2 and the DuoFlex S2 addon card to that.

If I disable every 2nd tuner in TVH it all works fine without any CC errors at all even if I use all 4 enabled tuners at the same time. This is very strange!

Ok so I removed the 2nd main card (Cine S2) plus its mounted add on card DuoFlex S2 and only have one tuner card with 4 tuners (Cine S2 + DuoFlex S2) installed.
Result? CC errors as soon as I start using all 4 tuners and the tuners causing the CC errors is the 2nd tuner on the main Cine S2 card and the 2nd tuner on the DuoFlex S2 add on card. Definately a strange pattern here!
As soon as I disable the 2nd tuner on the main Cine S2 card and the 2nd tuner on the DuoFlex S2 add on card and only utilize the 2 remaining "main/primary" tuners on each card it works fine again without any CC errors at all.

I even tried with removing the add on cards DuoFlex S2 from the main boards and only used the Cine S2 card with 2 tuners but same problem again if I enable both tuners. CC errors as soon as TVH starts to use the 2nd tuner.

Same thing if I remove the DuoFlex S2 from my 2nd main card Cine S2 and mount 2 of the Cine S2 cards into my computer, i.e. 4 tuners in total but without the DuoFlex S2 cards.
CC errors again on every 2nd tuner and as soon as I disable them the remaining 2 tuners out of 4 works fine without any CC errors.

So I have now mounted back everything into my computer and I have now 8 tuners in my computer but I have disabled 4 of them (every 2nd tuner or if you want to call it the secondary tuner) and it all works fine without any CC errors at all even if I use all 4 tuners at the same time for recording and/or live TV watching.

However, it feels very sad to be able to only utilize 50% of my tuner "park".

I have contacted Digital Devices with my findings but (as expected) no response at all.

I am keen on testing the TBS6985 DVB S2 quad tuner card to see if I would get the same problems but when I searched through the TBS forums I found a guy that had IDENTICAL issues as me with every 2nd tuner causing CC errors on HD channels:
http://www.tbsdtv.com/forum/viewtopic.php?f=142&t=8868

And another very interesting thread were similar issues are discussed:
http://www.tbsdtv.com/forum/viewtopic.php?f=37&t=8278#p28202 (however, in this thread they are discussing the TBS6984-card but TBS is commenting in that thread about replacing the 6984-card with a 6985-card due to totally different construction on the newer card)

Looks like it is boiling down to some kind of PCIe latency issues causing packets being lost?

Adam Bark Sutton, may I ask you if you currently are using the TBS6985 card and are you using the original drivers from TBS or the alternative driver from Luis?

Have you tested to utilize all 4 tuners at the same time and for HD channels on all 4 tuners to see if you get any CC errors?

Replies (45)

RE: Continuity counter errors - VERY interesting discovery for my CC problems - only every 2nd tuner of my 8 tuners causes this?! - Added by saen acro about 10 years ago

Is any one try to see what happen in IRQ loading
disable all unneeded in bios /sound com/printer/usb/1394 ports/
all dual/quad card share same resources from where come problems
lsdev show very interesting stuff

irq_week.png (60.4 KB) irq_week.png

irq

RE: Continuity counter errors - VERY interesting discovery for my CC problems - only every 2nd tuner of my 8 tuners causes this?! - Added by Latty Jordan about 10 years ago

I had a system that was working perfectly on a Pogoplug E02, runnng Arch Linux. Then I upgraded both Linux (pacman -Syu which I've done lots of times before) and Tvheadend and suddenly I was getting 100+ errors an hour (as reported by ProjectX processing the recordings). I rolled back tvheadend from 3.9.1352 to the previously stable 3.9.1107, but that hasn't made any difference. I then rolled back my linux kernel from linux-kirkwood-3.16.1-1-arm to linux-kirkwood-3.15.1-1-arm, and the single half hour test recording I've done so far seems to have just 4 errors, all occurring simultaneously and one in each of four PIDs. So there may be something that had changed in the 3.16 kernel that doesn't get on with tvheadend. lsdev isn't installed, but these little boxes run headless with no sound, video or attached keyboard, so I wouldn't expect to see many IRQ requests at all.

RE: Continuity counter errors - VERY interesting discovery for my CC problems - only every 2nd tuner of my 8 tuners causes this?! - Added by Crazy Fin about 10 years ago

Rob Rob wrote:

Your signal strength is low to being with and SNR is borderline acceptable. You are in the real of just not getting CC/PMT/BER errors in good to reasonable weather, you chuck some fairly heavy rain outside and your CC erros will be back with avengence. You need to improve your dish needs checking over 100% with results like that.
A lazy installer will often say "it's all ok", when it isn't you need to make damn sure they check a few channels on difference frequencies and polarities.

Your solution is just making the best of a bad setup, alignment, skew, EMI is a fact of life and it does affect satellite signals negatively if they are bad to begin with.

Robert E Rob: I can not really agree with you that it is all about incoming signal quality. One of my neighbours who is 4 houses away from me and with a bigger dish and better free sight to the Thor satellite has about 98% signal strength and 85-92% signal quality on different channels is also having a lot of CC errors. He is using the TBS 6985 card with driver from TBS. All his CC errors occurs on HD channels, nothing on SD channels.

I am also surprised that when I measure with my Satlink WS-6926 meter it shows about 5-8 percentage units higher signal than TVH gui shows (i.e. around 80-85% signal quality according to my Satlink meter) . Is it the Cine S2 tuners that loose so much? (I measure at the same connector end that goes into the CINE S2 tuner cards.)

I still believe it is EMI/RF interference, PCI buss/IRQ latency problem, Linux driver problem (or mostly a combo of all of them). I do not see that many people having problems with lost packets using Windows 7 and the same cards (either Cine S2 from Digital Devices or TBS 6985 or other similar cards). I might try a Windows 7 setup just to confirm this but I really want to use Linux, TVH, OSCAM and XBMC since there are no good software like Oscam and TVH under Windows (well you could run Oscam in Windows using CYGWIN).

My problems has also escalated when moving from TVH 3.4 to 3.9 and Linux kernels 3.16 and newer.

RE: Continuity counter errors - VERY interesting discovery for my CC problems - only every 2nd tuner of my 8 tuners causes this?! - Added by saen acro about 10 years ago

Windows migration is not so bad except descrambling,
but first test with mumudvb on current configuration

RE: Continuity counter errors - VERY interesting discovery for my CC problems - only every 2nd tuner of my 8 tuners causes this?! - Added by Crazy Fin about 10 years ago

48 hours no and VERY few CC errors (at most only 8-10 aggregated for all 8 tuners for the last 48 hours!) This is great!

See attached screenshot.

Still the question if it is PCI-e bus latency and/or interrupt problems, RF/EMI interference from motherboard and/or graphics driver, CINE S2 Linux driver or a combo of everything.

I will try to do two things during the coming weekend to test further:

1. Re-align satellite dish and make sure alignment and skew are properly set and try to get a higher signal strength and signal quality. Maybe I will test with a bigger dish later on. My current one is 60-70 cm (I think). A 90 cm or even a 120 cm dish should help quite much in my case to improve signal strength and quality.

2. Try with another motherboard that has built-in graphics.

TVH - no CC errors anymore - 2.png (40.3 KB) TVH - no CC errors anymore - 2.png

RE: Continuity counter errors - VERY interesting discovery for my CC problems - only every 2nd tuner of my 8 tuners causes this?! - Added by Latty Jordan about 10 years ago

Reverting to kernel 3.15 seems to have cured my problem with continuity errors, but here's another interesting observation. According to this thread on the Arch Linux forum http://archlinuxarm.org/forum/viewtopic.php?f=9&t=7692 there have been similar symptoms appearing due to samba. So I redownloaded the one recording that I had saved from when I was running kernel 3.16, processed it with ProjectX, and no CC errors were reported. Although there had previously been a couple of hundred when I downloaded that same file when the tvheadend box was running kernel 3.16. So in my particular case the recordings seems to have been absolutely fine, but the errors were introduced when I downloaded those recordings from the computer running tvheadend.

RE: Continuity counter errors - VERY interesting discovery for my CC problems - only every 2nd tuner of my 8 tuners causes this?! - Added by Meindert Oldenburger about 10 years ago

TVHeadend crash today. I also have problems with recordings that fail with Continuity counter error(s) It look likes the decription did not work properly?! (First 10 seconds of the recording did not look good)

TVHeadend crashed after some minutes.

below syslog and oscam log from 18:30, the time the program starts.

SYSLOG:

Aug 30 18:39:30 core2 tvheadend¹⁰⁰⁴: dvr: "NOS Jeugdjournaal" on "NED 3 HD" recorder starting
Aug 30 18:39:30 core2 tvheadend¹⁰⁰⁴: mpegts: 12187.5H in Astra 3 NL HD - tuning on Conexant CX24117/CX24132 : DVB-S #2
Aug 30 18:39:30 core2 tvheadend¹⁰⁰⁴: capmt: Starting CAPMT server for service "NPO3 HD" on adapter 2 seq 0x0002
Aug 30 18:39:30 core2 tvheadend¹⁰⁰⁴: subscription: "DVR: NOS Jeugdjournaal" subscribing on "NED 3 HD", weight: 300, adapter: "Conexant CX24117/CX24132 : DVB-S #2", network: "Astra 3 NL HD", mux: "12187.5H", provider: "M7 Group", service: "NPO3 HD"
Aug 30 18:39:32 core2 tvheadend¹⁰⁰⁴: TS: Astra 3 NL HD/12187.5H/NPO3 HD: H264 #518 Continuity counter error (total 1) Aug 30 18:39:32 core2 tvheadend[1004]: TS: Astra 3 NL HD/12187.5H/NPO3 HD: TELETEXT #38 Continuity counter error (total 1)
Aug 30 18:39:32 core2 tvheadend¹⁰⁰⁴: TS: Astra 3 NL HD/12187.5H/NPO3 HD: AC3 #106 Continuity counter error (total 1) Aug 30 18:39:32 core2 tvheadend[1004]: dvr: "NOS Jeugdjournaal" on "NED 3 HD": Updated Timer Aug 30 18:39:43 core2 tvheadend[1004]: TS: Astra 3 NL HD/12187.5H/NPO3 HD: H264 #518 Continuity counter error (total 335)
Aug 30 18:39:43 core2 tvheadend¹⁰⁰⁴: TS: Astra 3 NL HD/12187.5H/NPO3 HD: TELETEXT #38 Continuity counter error (total 157) Aug 30 18:39:43 core2 tvheadend[1004]: TS: Astra 3 NL HD/12187.5H/NPO3 HD: AC3 #106 Continuity counter error (total 227)
Aug 30 18:39:46 core2 tvheadend¹⁰⁰⁴: pmt: invalid checksum (len 249, errors 1)
Aug 30 18:39:54 core2 tvheadend¹⁰⁰⁴: TS: Astra 3 NL HD/12187.5H/NPO3 HD: H264 #518 Continuity counter error (total 680) Aug 30 18:39:54 core2 tvheadend[1004]: TS: Astra 3 NL HD/12187.5H/NPO3 HD: AC3 #106 Continuity counter error (total 438)
Aug 30 18:39:54 core2 tvheadend¹⁰⁰⁴: TS: Astra 3 NL HD/12187.5H/NPO3 HD: TELETEXT #38 Continuity counter error (total 307) Aug 30 18:40:05 core2 tvheadend[1004]: TS: Astra 3 NL HD/12187.5H/NPO3 HD: H264 #518 Continuity counter error (total 1014)
Aug 30 18:40:05 core2 tvheadend¹⁰⁰⁴: TS: Astra 3 NL HD/12187.5H/NPO3 HD: AC3 #106 Continuity counter error (total 648) Aug 30 18:40:05 core2 tvheadend[1004]: TS: Astra 3 NL HD/12187.5H/NPO3 HD: TELETEXT #38 Continuity counter error (total 457)
Aug 30 18:40:07 core2 tvheadend¹⁰⁰⁴: dvr: /data3/tvheadend/NOS Jeugdjournaal.2014-08-30.18-45.mkv from adapter: "Conexant CX24117/CX24132 : DVB-S #2", network: "Astra 3 NL HD", mux: "12187.5H", provider: "M7 Group", service: "NPO3 HD"
Aug 30 18:40:07 core2 tvheadend¹⁰⁰⁴: dvr: # type lang resolution aspect ratio sample rate channels
Aug 30 18:40:07 core2 tvheadend¹⁰⁰⁴: dvr: 1 H264 1920x1080 16:9
Aug 30 18:40:07 core2 tvheadend¹⁰⁰⁴: dvr: 2 AC3 dut ? ? <disabled, no valid input>
Aug 30 18:40:07 core2 tvheadend¹⁰⁰⁴: dvr: 3 TELETEXT dut <disabled, no valid input>
Aug 30 18:40:07 core2 tvheadend¹⁰⁰⁴: dvr: 4 CA
Aug 30 18:40:07 core2 tvheadend¹⁰⁰⁴: dvr: 5 CA
Aug 30 18:40:07 core2 tvheadend¹⁰⁰⁴: dvr: 6 CA
Aug 30 18:40:11 core2 tvheadend¹⁰⁰⁴: dvr: "RTL Nieuws" on "RTL 4 HD": Updated Timer
Aug 30 18:40:16 core2 tvheadend¹⁰⁰⁴: TS: Astra 3 NL HD/12187.5H/NPO3 HD: H264 #518 Continuity counter error (total 1364) Aug 30 18:40:16 core2 tvheadend[1004]: TS: Astra 3 NL HD/12187.5H/NPO3 HD: AC3 #106 Continuity counter error (total 871)
Aug 30 18:40:16 core2 tvheadend¹⁰⁰⁴: TS: Astra 3 NL HD/12187.5H/NPO3 HD: TELETEXT #38 Continuity counter error (total 609) Aug 30 18:40:16 core2 tvheadend[1004]: cat: invalid checksum (len 181, errors 1) Aug 30 18:40:24 core2 tvheadend[1004]: TS: Astra 3 NL HD/12187.5H/NPO3 HD Transport error indicator (total 1) Aug 30 18:40:27 core2 tvheadend[1004]: TS: Astra 3 NL HD/12187.5H/NPO3 HD: H264 #518 Continuity counter error (total 1718)
Aug 30 18:40:27 core2 tvheadend¹⁰⁰⁴: TS: Astra 3 NL HD/12187.5H/NPO3 HD: TELETEXT #38 Continuity counter error (total 759) Aug 30 18:40:27 core2 tvheadend[1004]: TS: Astra 3 NL HD/12187.5H/NPO3 HD: AC3 #106 Continuity counter error (total 1097)
Aug 30 18:40:38 core2 tvheadend¹⁰⁰⁴: TS: Astra 3 NL HD/12187.5H/NPO3 HD: AC3 #106 Continuity counter error (total 1305) Aug 30 18:40:38 core2 tvheadend[1004]: TS: Astra 3 NL HD/12187.5H/NPO3 HD: H264 #518 Continuity counter error (total 2057)
Aug 30 18:40:38 core2 tvheadend¹⁰⁰⁴: TS: Astra 3 NL HD/12187.5H/NPO3 HD: TELETEXT @ #38 Continuity counter error (total 916)
Aug 30 18:40:46 core2 tvheadend¹⁰⁰⁴: TS: Astra 3 NL HD/12187.5H/NPO3 HD Transport error indicator (total 6)

......

Aug 30 18:43:16 core2 tvheadend¹⁰⁰⁴: mpegts: 12187.5H in Astra 3 NL HD - tuning on Conexant CX24117/CX24132 : DVB-S #1
Aug 30 18:43:17 core2 tvheadend¹⁰⁰⁴: capmt: Starting CAPMT server for service "NPO3 HD" on adapter 1 seq 0x0003
Aug 30 18:43:17 core2 tvheadend¹⁰⁰⁴: subscription: "DVR: NOS Jeugdjournaal" subscribing on "NED 3 HD", weight: 300, adapter: "Conexant CX24117/CX24132 : DVB-S #1", network: "Astra 3 NL HD", mux: "12187.5H", provider: "M7 Group", service: "NPO3 HD"
Aug 30 18:43:17 core2 tvheadend¹⁰⁰⁴: CRASH: Signal: 6 in PRG: /usr/local/bin/tvheadend (3.9.1355~g9eea481) [c3f3140402fe7f19e6fff508beca9e5615a2e873] CWD: /
Aug 30 18:43:17 core2 tvheadend¹⁰⁰⁴: CRASH: Fault address 0x72000003ec (N/A)
Aug 30 18:43:17 core2 tvheadend¹⁰⁰⁴: CRASH: Loaded libraries: linux-vdso.so.1 /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 /lib/x86_64-linux-gnu/libz.so.1 /usr/lib/liburiparser.so.1 /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 /usr/lib/x86_64-linux-gnu/libavcodec.so.55 /usr/lib/x86_64-linux-gnu/libavutil.so.52 /usr/lib/x86_64-linux-gnu/libavformat.so.55 /usr/lib/x86_64-linux-gnu/libswscale.so.2 /lib/x86_64-linux-gnu/libdbus-1.so.3 /lib/x86_64-linux-gnu/libdl.so.2 /lib/x86_64-linux-gnu/libpthread.so.0 /lib/x86_64-linux-gnu/libm.so.6 /lib/x86_64-linux-gnu/librt.so.1 /lib/x86_64-linux-gnu/libc.so.6 /usr/lib/x86_64-linux-gnu/libswresample.so.0 /usr/lib/x86_64-linux-gnu/libva.so.1 /usr/lib/x86_64-linux-gnu/libzvbi.so.0 /usr/lib/x86_64-linux-gnu/libxvidcore.so.4 /usr/lib/x86_64-linux-gnu/libx265.so.31 /usr/lib/x86_64-linux-gnu/libx264.so.142 /usr/lib/x86_64-linux-gnu/libvpx.so.1 /usr/lib/x86_64-linux-gnu/libvorbisenc.so.2 /usr/lib/x86_64-linux-gnu/libvorbis.so.
Aug 30 18:43:17 core2 tvheadend¹⁰⁰⁴: CRASH: Register dump [23]: 00007f73c800c56000000000000000010000000000000008000000000000020200007f73c800c3c000000000004209600000000656b4d140000000000000000000000000000003ec0000000000000a5d00000000026635500000000002977df000000000000000060000000000000000ffffffffffffffff00007f73fd7f16b800007f74103604070000000000000202a94800000000003300000000000000000000000000000000fffffffe7ffbba170000000000000000
Aug 30 18:43:17 core2 tvheadend¹⁰⁰⁴: CRASH: STACKTRACE
Aug 30 18:43:17 core2 tvheadend¹⁰⁰⁴: CRASH: /usr/local/src/tvheadend/src/trap.c:148 0x431346
Aug 30 18:43:17 core2 tvheadend¹⁰⁰⁴: CRASH: ??:0 0x7f7410bec8d0
Aug 30 18:43:17 core2 tvheadend¹⁰⁰⁴: CRASH: gsignal+0x37 (/lib/x86_64-linux-gnu/libc.so.6)
Aug 30 18:43:17 core2 tvheadend¹⁰⁰⁴: CRASH: abort+0x148 (/lib/x86_64-linux-gnu/libc.so.6)
Aug 30 18:43:17 core2 tvheadend¹⁰⁰⁴: CRASH: /usr/local/src/tvheadend/src/plumbing/globalheaders.c:281 0x44de1d
Aug 30 18:43:17 core2 tvheadend¹⁰⁰⁴: CRASH: /usr/local/src/tvheadend/src/subscriptions.c:466 0x420a4f
Aug 30 18:43:17 core2 tvheadend¹⁰⁰⁴: CRASH: /usr/local/src/tvheadend/src/streaming.c:348 0x41e286
Aug 30 18:43:17 core2 tvheadend¹⁰⁰⁴: CRASH: /usr/local/src/tvheadend/src/service.c:1151 0x423f73
Aug 30 18:43:17 core2 tvheadend¹⁰⁰⁴: CRASH: /usr/local/src/tvheadend/src/service.h:510 0x44515b
Aug 30 18:43:17 core2 tvheadend¹⁰⁰⁴: CRASH: /usr/local/src/tvheadend/src/input/mpegts/tsdemux.c:105 0x470b6f
Aug 30 18:43:17 core2 tvheadend¹⁰⁰⁴: CRASH: /usr/local/src/tvheadend/src/descrambler/tvhcsa.c:134 (discriminator 3) 0x4939ba
Aug 30 18:43:17 core2 tvheadend¹⁰⁰⁴: CRASH: /usr/local/src/tvheadend/src/descrambler/descrambler.c:361 (discriminator 2) 0x461828
Aug 30 18:43:17 core2 tvheadend¹⁰⁰⁴: CRASH: /usr/local/src/tvheadend/src/input/mpegts/tsdemux.c:228 0x470e3e
Aug 30 18:43:17 core2 tvheadend¹⁰⁰⁴: CRASH: /usr/local/src/tvheadend/src/input/mpegts/mpegts_input.c:760 0x46546e
Aug 30 18:43:17 core2 tvheadend¹⁰⁰⁴: CRASH: /usr/local/src/tvheadend/src/wrappers.c:125 0x40ef8c
Aug 30 18:43:17 core2 tvheadend¹⁰⁰⁴: CRASH: ??:0 0x7f7410be50a4
Aug 30 18:43:17 core2 tvheadend¹⁰⁰⁴: CRASH: clone+0x6d (/lib/x86_64-linux-gnu/libc.so.6)

OSCAM log:
2014/08/30 10:05:55 10DC8F0 c meindert (0100&00006A/5C00/17C0/64:ADDFC63D6091B8B48A402458D511D9F3): found (343 ms) by CanalDigitaal - Nederland 2 HD
2014/08/30 10:05:57 10DC8F0 c meindert (0100&00006A/5C00/17C0/64:8A53B2116A346EF9385C112DB5484331): found (335 ms) by CanalDigitaal - Nederland 2 HD
2014/08/30 18:39:30 10DC8F0 c [ADD PID 0] CAID: 0500 ECM_PID: 0C37 PROVID: 051900
2014/08/30 18:39:30 10DC8F0 c [ADD PID 1] CAID: 0100 ECM_PID: 0723 PROVID: 00006C
2014/08/30 18:39:30 10DC8F0 c [ADD PID 2] CAID: 1818 ECM_PID: 0723 PROVID: 000000
2014/08/30 18:39:30 10DC8F0 c [ADD PID 3] CAID: 0100 ECM_PID: 070F PROVID: 00006A
2014/08/30 18:39:30 10DC8F0 c [ADD PID 4] CAID: 1817 ECM_PID: 070F PROVID: 000000
2014/08/30 18:39:30 10DC8F0 c Found 5 ECMpids and 1 STREAMpids in PMT
2014/08/30 18:39:30 10DC8F0 c [DVBAPI] Receiver wants to demux srvid 5230 on adapter 0002 camask 0004 index 0000 pmtpid 0000
2014/08/30 18:39:30 10DC8F0 c New program number: 5230 (0500:5230 unknown) [pmt_list_management 3]
2014/08/30 18:39:30 10DC8F0 c [DVBAPI] Demuxer #0 trying to descramble PID #3 CAID 0100 PROVID 00006A ECMPID 070F ANY CHID PMTPID 0000 VPID 0002
2014/08/30 18:39:30 10DC8F0 c [DVBAPI] Demuxer #0 continue decoding of SRVID 5230
2014/08/30 18:39:30 10DC8F0 c [SKIP STREAM 0] CAID: 0500 ECM_PID: 0C37 PROVID: 051900
2014/08/30 18:39:30 10DC8F0 c [SKIP STREAM 1] CAID: 0100 ECM_PID: 0723 PROVID: 00006C
2014/08/30 18:39:30 10DC8F0 c [SKIP STREAM 2] CAID: 1818 ECM_PID: 0723 PROVID: 000000
2014/08/30 18:39:30 10DC8F0 c [SKIP STREAM 3] CAID: 0100 ECM_PID: 070F PROVID: 00006A
2014/08/30 18:39:30 10DC8F0 c [SKIP STREAM 4] CAID: 1817 ECM_PID: 070F PROVID: 000000
2014/08/30 18:39:30 10DC8F0 c Found 5 ECMpids and 1 STREAMpids in PMT
2014/08/30 18:39:30 10DC8F0 c [DVBAPI] Receiver wants to demux srvid 5230 on adapter 0002 camask 0004 index 0000 pmtpid 0000
2014/08/30 18:39:30 10DC8F0 c New program number: 5230 (0500:5230 unknown) [pmt_list_management 3]
2014/08/30 18:39:31 10DC8F0 c meindert (0100&00006A/5C00/5230/64:47937B8BA236CF29BCC270E4A61AB3EA): found (338 ms) by CanalDigitaal - Nederland 3 HD
2014/08/30 18:39:36 10DC8F0 c meindert (0100&00006A/5C00/5230/64:DA440A47E7B6368CE200969C2C2EA172): found (335 ms) by CanalDigitaal - Nederland 3 HD
2014/08/30 18:39:46 10DC8F0 c meindert (0100&00006A/5C00/5230/64:BF270B0C247BD058829CCF499432EEC7): found (336 ms) by CanalDigitaal - Nederland 3 HD
2014/08/30 18:39:56 10DC8F0 c meindert (0100&00006A/5C00/5230/64:EF4299338BE925FCF146D463D084597A): found (334 ms) by CanalDigitaal - Nederland 3 HD
2014/08/30 18:40:06 10DC8F0 c meindert (0100&00006A/5C00/5230/64:201202432C0EF34F264B210D9792922A): found (338 ms) by CanalDigitaal - Nederland 3 HD
2014/08/30 18:40:16 10DC8F0 c meindert (0100&00006A/5C00/5230/64:06A9FA3032907B7F81622DDE02F08D9F): found (336 ms) by CanalDigitaal - Nederland 3 HD
2014/08/30 18:40:26 10DC8F0 c meindert (0100&00006A/5C00/5230/64:2E4F5C3164C970918A26BE6324ED286C): found (335 ms) by CanalDigitaal - Nederland 3 HD
2014/08/30 18:40:36 10DC8F0 c meindert (0100&00006A/5C00/5230/64:3D10E00B7026CFBCEBBD13D9BE5567B7): found (334 ms) by CanalDigitaal - Nederland 3 HD
2014/08/30 18:40:46 10DC8F0 c meindert (0100&00006A/5C00/5230/64:5D9B48F4E33DCF31CC418C92FCACA214): found (348 ms) by CanalDigitaal - Nederland 3 HD
2014/08/30 18:40:56 10DC8F0 c meindert (0100&00006A/5C00/5230/64:9AF60B06E2EE9121F5DF2D3F6EE8ADFF): found (334 ms) by CanalDigitaal - Nederland 3 HD
2014/08/30 18:41:06 10DC8F0 c meindert (0100&00006A/5C00/5230/64:26411A59336526487F84BDCF2DE47CB9): found (342 ms) by CanalDigitaal - Nederland 3 HD
2014/08/30 18:41:16 10DC8F0 c meindert (0100&00006A/5C00/5230/64:704C4CCB152E81A7179C93C77AA285AB): found (343 ms) by CanalDigitaal - Nederland 3 HD
2014/08/30 18:41:26 10DC8F0 c meindert (0100&00006A/5C00/5230/64:88E9C8222B4B9F3D1DFA795E47E1A1D1): found (340 ms) by CanalDigitaal - Nederland 3 HD
2014/08/30 18:41:36 10DC8F0 c meindert (0100&00006A/5C00/5230/64:54EA23FE9A1818829D0557364DBB0F65): found (335 ms) by CanalDigitaal - Nederland 3 HD
2014/08/30 18:41:46 10DC8F0 c meindert (0100&00006A/5C00/5230/64:9BEFF25ECB1D2EA4ADAF37A64249C5B3): found (334 ms) by CanalDigitaal - Nederland 3 HD
2014/08/30 18:41:56 10DC8F0 c meindert (0100&00006A/5C00/5230/64:DFAAF19087E45A28D7300638522BC088): found (336 ms) by CanalDigitaal - Nederland 3 HD
2014/08/30 18:42:06 10DC8F0 c meindert (0100&00006A/5C00/5230/64:DA00379231E0A90847FC8569D4748B3E): found (342 ms) by CanalDigitaal - Nederland 3 HD
2014/08/30 18:42:16 10DC8F0 c meindert (0100&00006A/5C00/5230/64:108C23DEBEDD024E206431EBC93FA8C5): found (335 ms) by CanalDigitaal - Nederland 3 HD
2014/08/30 18:42:23 10D14F0 r CanalDigitaal [seca] Request provider 1
2014/08/30 18:42:24 10D14F0 r CanalDigitaal [seca] provider 1: 0000, valid: 1, name: MANAGMENT, expiry date: 2014/10/23
2014/08/30 18:42:24 10D14F0 r CanalDigitaal [seca] SA: ########
2014/08/30 18:42:24 10D14F0 r CanalDigitaal [seca] PBM for provider 1: 799008001c000
2014/08/30 18:42:24 10D14F0 r CanalDigitaal [seca] meindert emmtype=shared, len=119, idx=0, cnt=1: written (454 ms)
2014/08/30 18:42:26 10DC8F0 c meindert (0100&00006A/5C00/5230/64:9B944F8A955AE3DE2446F37C38BC7501): found (337 ms) by CanalDigitaal - Nederland 3 HD
2014/08/30 18:42:36 10DC8F0 c meindert (0100&00006A/5C00/5230/64:40A2B360B0DA475AB83E26AE7A04EB3D): found (336 ms) by CanalDigitaal - Nederland 3 HD
2014/08/30 18:42:46 10DC8F0 c meindert (0100&00006A/5C00/5230/64:1E0F6C314A0E05E19F6395B1E30CC6CE): found (352 ms) by CanalDigitaal - Nederland 3 HD
2014/08/30 18:42:56 10D14F0 r CanalDigitaal [seca] Request provider 2
2014/08/30 18:42:56 10D14F0 r CanalDigitaal [seca] Detected seca3 card
2014/08/30 18:42:56 10D14F0 r CanalDigitaal [seca] provider 2: 006A, valid: 1, name: CANALDIGITAAL, expiry date: 2014/10/23
2014/08/30 18:42:56 10D14F0 r CanalDigitaal [seca] SA: ########
2014/08/30 18:42:56 10D14F0 r CanalDigitaal [seca] PBM for provider 2: c200000000000000
2014/08/30 18:42:56 10D14F0 r CanalDigitaal [seca] meindert emmtype=shared, len=119, idx=1, cnt=1: written (466 ms)
2014/08/30 18:42:56 10DC8F0 c meindert (0100&00006A/5C00/5230/64:6D617CDD1BD55EA79D8E2635E6D14E4B): found (334 ms) by CanalDigitaal - Nederland 3 HD
2014/08/30 18:43:06 10DC8F0 c meindert (0100&00006A/5C00/5230/64:9A1A2E226BAF4D098D872CBD3D45BD68): found (336 ms) by CanalDigitaal - Nederland 3 HD
2014/08/30 18:43:17 10DC8F0 c [ADD PID 0] CAID: 0500 ECM_PID: 0C37 PROVID: 051900
2014/08/30 18:43:17 10DC8F0 c [ADD PID 1] CAID: 0100 ECM_PID: 0723 PROVID: 00006C
2014/08/30 18:43:17 10DC8F0 c [ADD PID 2] CAID: 1818 ECM_PID: 0723 PROVID: 000000
2014/08/30 18:43:17 10DC8F0 c [ADD PID 3] CAID: 0100 ECM_PID: 070F PROVID: 00006A
2014/08/30 18:43:17 10DC8F0 c [ADD PID 4] CAID: 1817 ECM_PID: 070F PROVID: 000000
2014/08/30 18:43:17 10DC8F0 c Found 5 ECMpids and 1 STREAMpids in PMT

RE: Continuity counter errors - VERY interesting discovery for my CC problems - only every 2nd tuner of my 8 tuners causes this?! - Added by Crazy Fin about 10 years ago

=================

FINAL (hopefully) report for my "adventure" with CC errors...

=================

Alright all, after 24 hours of work with my TV-PC server system with just 6 hours sleep, I am pleased (for now at least) to say that it looks like I have solved my CC errors! :-)

Here is what I have done since Friday evening:

1. Replaced the motherboard Gigabyte GA-P61-USB3-B3 with a quite interesting motherboard that is actually special built by Asrock to be used in bitcoining servers:

Asrock H61 PRO BTC, http://www.asrock.com/mb/Intel/H61%20Pro%20BTC/index.asp

This card has 5 (!!) motherboard slots that are PCIe 2.0 x1. The good thing is that 4 of them are located at the bottom of the motherboard and far away from the top of the board where the CPU is located. Another good thing is also that it has built-in graphics (as long as you use a CPU with integrated graphics) so no need to "disturb" the PCIe tuner cards with a graphics card on a PCIe x1 slot.
And not to mention the price, only 440 SEK here in Sweden (approx 45 EUR). Socket is LGA1155 but there is a version for socket LGA1150 as well, model no H81 Pro BTC.
Also a built-in motherboard COM1 connector that fits my serial Phoneix card reader (built-into the chassi). So as I think, a perfect card for a multi-tuner-card TV-server. :-)

2. Did a brand new and clean install of Ubuntu 14.04 and downloaded new drivers for my Cine S2 cards (as described on http://shop.digital-devices.de/epages/62357162.sf/en_GB/?ViewObjectPath=%2FShops%2F62357162%2FCategories%2FDownloadsNew1%2FLinux_Unterstuetzung_fuer_Digital_Devices_Produkte)

3. Installed latest build of TVH (3.9.1358), latest Oscam and then finally latest stable release of XBMC with the TVH PVR plugin.

4. Did all the TVH setup and conf and voilaaaa! A really nice working TVH setup and you know what.... NO CC errors whatsoever even if I tune in to 4 HD channels at the same time and recording on for example 2 more HD channels! Well, I have about 4-8 CC errors during the last 12 hours but that is fine (and probably expected since most of those has occured when fast switching and jumping back and forth between channels).

I even have NO CC errors at all eventhough sometimes I get below 70% signal quality (indicator goes brown) so I really believe that the signal strength TVH shows is not always correct. When I had those low signal qualities I pulled out that SAT cable from the tuner card and measured with my Satlink WS-6926 and it shows around 80% signal quality. Anyway, look at the attached screenshot and you can see that I have NO CC errors on any of the tuners used in that screenshot.

I will still probably replace my smaller dish with a dish around 100-120 cm in dia in order to get as good as possible signal quality even when I get thunderstorms and heavy snowfall in the coming winter. (Probably something like this VISIOSAT SMC DTH, h24-files.s3.amazonaws.com/83431/227259-NX8wc.pdf, very expensive though, around 390 EUR here in Sweden at http://www.satpro.se/default.asp?id=96001&art_nr=695758&cat_nr=103&ucat_nr=110)

For now on I am very happy with having solved the dreading CC errors. I´ll report back during coming week if this continues to work fine.

TVH showing low quality sometimes on all tuners - still no CC errors though.PNG (36.9 KB) TVH showing low quality sometimes on all tuners - still no CC errors though.PNG

RE: Continuity counter errors - VERY interesting discovery for my CC problems - only every 2nd tuner of my 8 tuners causes this?! - Added by saen acro about 10 years ago

install Webmin + Webmin System stats http://sourceforge.net/projects/webminstats/
easy to monitor all parameters of motherboard and hardisk

RE: Continuity counter errors - VERY interesting discovery for my CC problems - only every 2nd tuner of my 8 tuners causes this?! - Added by Miro K. about 10 years ago

crazy XXX Finn,

do you still have the tuners isolated from the pc-case?
I have had similar problems with my Cine S2 V6.5. I also bought it as bundle with Duo-Flex. My Interferences where on the Tuner 1 (Adapter 0) and time to time on Tuner 2 (Adapter 1). Disabing the first 2 tuners (build in) was solving the problem for me too. I switched my mainboard from GigaByte (H77) also to AsRock(z77) but without any change. I also switched the kernel for KVM from standard pass-trough (2.6.32) to VirtIO (3.10) (I run it virtualized). But the final sollution was, I got RMA and sent the card back to DigitalDevices. Yesterday it came back with the Base replaced(Duoflex is still the same) but in additionally, the put an Floppy power cable bridge inside, connecting both cards together (without external power supply anymore) so my CC errors are gone, but I don't know, if it is the new tuner card or the kind of powering the Duo-Flex now... guess it could be booth, since you have isolated for F-Connectors before.

~~One more question, are you still patching your signal monitor on tvhe build or is it now working out of the box?~~
Answered this myself.. its now out of the box.Just pulled 3.9.1358~g2746998, I love that, I love tvheadend, thx !!!

RE: Continuity counter errors - VERY interesting discovery for my CC problems - only every 2nd tuner of my 8 tuners causes this?! - Added by Crazy Fin about 10 years ago

@Miro K:

Nope, no isolation from the PC-chassi anymore.

Interesting to hear about that you also solved your CC errors temporarily by disabling every 2nd tuner.
Do you have easy access to your Cine S2 card? Would be great if you could take a photo of the "mod" that Digital Devices did.

I am very happy (at the moment) since I have now tested with 4 HD recorsings on the same time while running for different players at HD channels too and NO CC errors at all. So great!

RE: Continuity counter errors - VERY interesting discovery for my CC problems - only every 2nd tuner of my 8 tuners causes this?! - Added by Miro K. about 10 years ago

@ Crazy Fin, for me it wans't every 2nd, but the first 2 tuners (the build-in).

In fact they didn't changend nothing on their cards, they just connected the power connectors together with this..

RE: Continuity counter errors - VERY interesting discovery for my CC problems - only every 2nd tuner of my 8 tuners causes this?! - Added by Crazy Fin about 10 years ago

Ahaaa, strange! So instead of connecting the main card CINE S2 and the add on card DuoFlex S2 to power with their own cables, Digital Devices now takes power from the PCIe buss directly and distributes it further on the the add on card with the new cable you are showing.

Might be a good tip for other CINE S2 version 6.5 card users to test before replacing motherboard like I did.
My neighbor who also has a lot of CC errors even though he has a signal quality above 90% has also a motherboard with a added PCIe graphics card. He has the TBS6985 card and he was keen on testing to either pull out the card from the motherboard and chassi using a PCIe extender cable or to try with a motherboard that has built in graphics.

I am now on my full second day without TVH crashes or any increasing CC errors. I´ll keep it running for the rest of the week and if it works fine I´ll go into "production environment" here at home and let my 2 kids and my wife go crazy on using XBMC in full on each of their own computers. Will be a good test! :-)

RE: Continuity counter errors - VERY interesting discovery for my CC problems - only every 2nd tuner of my 8 tuners causes this?! - Added by Miro K. about 10 years ago

crazy XXX Finn,

can you check, whenever your EPG gets regurally updated? Mine stopped updating SKY EPG. I can see a lot of updates on start of TVHE, but after some time it becomes rearly as finally no updates happens at all. This could be a reason, why CC errors are gone too.. (as they appeared only while tuning on other tuners)

RE: Continuity counter errors - VERY interesting discovery for my CC problems - only every 2nd tuner of my 8 tuners causes this?! - Added by Crazy Fin about 10 years ago

My EPG:s seems to be updated regularly as far as I can see in the syslog. Latest update was for example just 2 hours before I wrote this post. It looks like my EPG scan is done either every hour or at least every 2nd hour.

I can also see in the TVH GUI that the EPG is 7 days ahead currently which looks correct.

RE: Continuity counter errors - VERY interesting discovery for my CC problems - only every 2nd tuner of my 8 tuners causes this?! - Added by Miro K. about 10 years ago

Thanks, my old versions used to scan every transponder of my 3 satellites (19.2, 13.0, 23.5) endlessly switching the frequencies in about 2-3 sec, now ist stays very long on the same frequencies, and it stops using all the tuners (right now, 5 minutes after starts its scans only on 2 out of 4 tuner, before it utilized them all)..
Speaking only about EPG/eit. DVR and streaming is working fine. On channels beeing used by LiveTV or DVR the EPG was updatet too, but the others none.. (I switched now to latest build 3.9.1367)

RE: Continuity counter errors - VERY interesting discovery for my CC problems - only every 2nd tuner of my 8 tuners causes this?! - Added by Slaine Roth about 10 years ago

I have the same problem with cc errors (about 50 errors/hour). But if I run stress tool on Ubuntu (enough for 1 core of 4: “stress – c 1”) the cc errors disappeared (0 errors for 5 hours). I’m not Linux/HW expert so I don’t know what does it means. Can someone help me to interpret/solve this problem?
My system:
MB: Supermicro X10SBA (J1900 chipset), Bios v.: R 1.0c
TV card: TBS6985
OS: Ubuntu server 14.0.4.1 (3.13.0-35-generic), TBS Driver – 140819, MSI enabled,
TVheadend: 3.4.28

Thanx and sorry for my English.

RE: Continuity counter errors - VERY interesting discovery for my CC problems - only every 2nd tuner of my 8 tuners causes this?! - Added by Rob D almost 10 years ago

Slaine Roth wrote:

I have the same problem with cc errors (about 50 errors/hour). But if I run stress tool on Ubuntu (enough for 1 core of 4: “stress – c 1”) the cc errors disappeared (0 errors for 5 hours). I’m not Linux/HW expert so I don’t know what does it means. Can someone help me to interpret/solve this problem?
My system:
MB: Supermicro X10SBA (J1900 chipset), Bios v.: R 1.0c
TV card: TBS6985
OS: Ubuntu server 14.0.4.1 (3.13.0-35-generic), TBS Driver – 140819, MSI enabled,
TVheadend: 3.4.28

Thanx and sorry for my English.

Has anyone else tried this? Worked for me as well.

RE: Continuity counter errors - VERY interesting discovery for my CC problems - only every 2nd tuner of my 8 tuners causes this?! - Added by Robin Karlsson almost 10 years ago

crazy XXX Finn, how do you connect/power your Digital Devices DVB-S2 PCI-E+Duoflex?
Single PSU-floppy cable to the pcie card?
Single PSU-floppy cable to the extension card?
Two PSU-floppy cables to each card?
Floppy "bridge" cable between the cards, taking power from pcie-slot.

atm i use the "bridged" cable and i'm having CC errors when switching channels etc.
No errors if i use the same sat+cables to a box with a usb dvb-s2+dvbviewer.
Currently running 3.9.2388~g60f959b~trusty + some months old experimental drivers since they broke the current git.

Thanks in advance.

RE: Continuity counter errors - VERY interesting discovery for my CC problems - only every 2nd tuner of my 8 tuners causes this?! - Added by Crazy Fin almost 10 years ago

Hi Robin

It was a while ago since I completed the setup and it has been working fine since then. Don't exactly remember how I finally chose to supply power to both cards but I thiiiink it was by using a separate power cable to each card. (I´ll check during the weekend, I will anyway open up my server since I need to check if one of the extension cards is broken since I cant use them to tune, I get "resource not available" on those two tuners on the extensioncard when I try to for example use the "femon"-command to check signal strength).

However, I am quite convinced that what solved my CC problems was the change to a motherboard having 5 (!!) motherboard slots that are PCIe 2.0 x1. The good thing is that 4 of them are located at the bottom as well, far away from graphics chip and other possible signal interfering sources.
Special built by Asrock to be used in bitcoining servers:
Asrock H61 PRO BTC, http://www.asrock.com/mb/Intel/H61%20Pro%20BTC/index.asp

After that I started to use that motherboard I have had no problems with CC errors.
(Only thing that has happened was that I totally lost the signal during a heavy snowstorm 2 weeks ago but that is only due to me having a quite small parabol with a little bit too low signal level. I´ll change to VISIOSAT SMC DTH, http://h24-files.s3.amazonaws.com/83431/227259-NX8wc.pdf and https://www.hm-sat-shop.de/en/antennen-visiosat-smc/visiosat-smc-parabolantenne-120cm.html together with a heating system on the parabol dish to avoid heavy snow to get stuck on the dish and decreasing the signal strength.)

« Previous
1
2
Next »

(26-45/45)

Project

General

Profile

Tvheadend