Support Digital Devices CI Interfaces

Jasmin Jessich

Hello TVH and DD CI users!

I have implemented the support for the Digital Devices CI interfaces (see also https://tvheadend.org/issues/4477). Currently only one service can use the dedicated CI at a time. There is no MCD (Multi Channel Decoding) or MTD (Multi Tuner Decoding) implemented.

It is 95% working, but sometimes the CAM doesn't decrypt. This is no problem of the new code, but of the PID selection for CAMs in TVH general, I guess. I tried to find the reason, but TVH is too complicated in this area and I am not willing to spend hours and hours to analyse this part of TVH. The DD CI code is 100% finished and works, if the PIDs are set properly by TVH. This has been already tested by me and another TVH user.

I also asked Jaroslav for support, but he has currently no time, so I stopped the project at this stage. As long as I don't get more support, I am not willing to continue working on this! I am not using TVH at all and did this only, because a friend asked me to do this. Without proper support form any TVH developer the last 5% can't be implemented.

You can find the code at GitHub on the ddci branch:
> https://github.com/jasmin-j/tvheadend/tree/ddci

I will not submit a pull request, because it is not 100% working. Once the last 5% are done, it can be integrated to TVH.

Have fun and BR,
Jasmin

mpmc

Jasmin Jessich wrote:
> .. snip ..

> I will not submit a pull request, because it is not 100% working. Once the last 5% are done, it can be integrated to TVH.

Don't worry about that - open a PR anyway so people can discuss your changes on github :).

>
> Have fun and BR,

> Jasmin

Jasmin Jessich

Mark Clarkstone wrote:

> Don't worry about that - open a PR anyway so people can discuss your changes on github :).

I crated pull request 1031 (https://github.com/tvheadend/tvheadend/pull/1031). It is open for comments now.

I created a new branch (ddci_phase1) for the review, so that the comments will keep after incorporating them into the main development branch (ddci) and squashing them.

BR,
Jasmin

sharky :-)

You merged branch to the master right ? Now it should possible to test my interface right ?

Jasmin Jessich

Yes, it should be all an master and work as expected for Phase 1.

Phase 1 means only ONE service can use the DD CI CAM.

Phase 2 is Multi Channel Decoding (MCD) where several services of the same mux can use the DD CI CAM.

I am not sure if I can implement Phase 2 before my vacation (15.12.2017..3.2.2018), but I will try.

BR,
Jasmin

sharky :-)

Hey Jasmin ,

I could compile the latest git. Tvh starts successfully .

CAM Module and Cine S6.5 are visible under tv adapters.yay CAM Module recognized that I have pluged in a alphacrypt module ( module is green / ready state )

Enter my PIN and saved the configuration.

Tuning to a non decrypted channel works out of the box. *Yippie'

Tuning to a decrypted channel does not work. Do I have to assign anything ?

The following debug ist generated.

2017-11-29 00:15:56.849 mpegts: 10817.5V in DVB-S Network - tuning on STV090x Multistandard #0 : DVB-S #0
2017-11-29 00:15:57.368 subscription: 000F: "HTTP" subscribing to service "DVB-S Network/10817.5V/FOX HD", weight: 100, adapter: "STV090x Multistandard #0 : DVB-S #0", network: "DVB-S Network", mux: "10817.5V", provider: "DIGITAL+", profile="pass", hostname="192.168.10.33", client="VLC/2.2.6 LibVLC/2.2.6"

2017-11-29 00:15:59.334 subscription: 000F: service instance is bad, reason: No descrambler

Do I have to link the cam and the tuner or does it happen automatically ?

Thanks !

Jasmin Jessich

> I could compile the latest git.

Did you compile with "./configure --enable-ddci" ?

You need to see in the configure output:
libdvben50221 yes

ddci yes

> Tuning to a decrypted channel does not work. Do I have to assign anything ?

No, all is done automatically.

> The following debug is generated.
This log says nothing!
You need to start TVH with:

./build.linux/tvheadend -l tvh.log --trace linuxdvb,ddci,en50221,dvbcam

The trace outout in tvh.log is the thing I need.

Then I can tell you more, but first be sure ddci is enabled in the configuration.

BR,
Jasmin

sharky :-)

Thank you, I think it was to late :-)

Just for documentation.

AUTOBUILD_CONFIGURE_EXTRA=--enable-ddci ./Autobuild.sh -j4

Decrypting is working !

Jasmin Jessich

sharky :-) wrote:
> Decrypting is working !

Nothing else I would have expected :D

Saen Acro

sharky :-) wrote:
> Just for documentation.
>
> AUTOBUILD_CONFIGURE_EXTRA=--enable-ddci ./Autobuild.sh -j4

to be more correct


AUTOBUILD_CONFIGURE_EXTRA=--enable-ddci ./Autobuild.sh -j$(nproc)

/I have 16 cores ;) /

Daniel Scheller

FYI (for anyone using Gentoo):

https://github.com/gentoo/gentoo/pull/6399

(and, semi-related: https://github.com/gentoo/gentoo/pull/6401 - might come in handy for anyone wanting to test patches).

Alexander P

Thx to Jasmin to implement this feature in in TVH!

It works almost perfect, but maybe I found a bug in the current implementation.

In my setup I have two smartcards for decrypting my channels. One card can only be used in an AlphaCryptLight Module and the other one is handled by OSCAM. With the most recent version of the code, I'm now able to use the ACL in the DDCI. But after I inserted the ACL module, only ACL related channels are decrypted, but no channels, which should be handled by OSCAM... When I disconnect the ACL Module, OSCAM channels are decrypted as usual.

It seems, that for now it is not possible to have both ways of decrypting channels at the same time. Can someone confirm that?

Saen Acro

CAID filter list used?

Alexander P

Yes, tried it... same results...

Maybe the problem is, that the channels I want to descramble with OSCAM are also using the same CAID, which is handled by the card in my ACL...
(For german users: ACL with Sky V14, CAID 098C; OSCAM with HD+ HD01, CAID 1830)

Saen Acro

HD+ 1843 and 1860 work Perfect ;)
experiment with CAID selection

Alexander P

First Hit, Last Hit and All CAIDs...

No difference

CAID filter list: 098C

Jasmin Jessich

Alexander P wrote:
> Thx to Jasmin to implement this feature in in TVH!

And also THX to Jaroslav for rewriting big parts of the dvbcam code to allow reusing it for DD CI!

If the problem still persists after you playing with the CAIDs, please activate the trace mode with "dvbcam" enabled and look if you find "first CAID XXXX selected" or "add CAID XXXX to selection" or "last CAID XXXX selected" when you tune.

When the text is printed, the DVB CAM (DD CI) is used for the service. If not, the service should be decoded by your OsCAM device. If it is not printed and the service is not decoded by OsCAM, we need to debug this further. But then it is a general problem and not located in the DD CI extensions.

BR,
Jasmin

Alexander P

I did some trial and error using the trace messages...

Switching between the different options in "CAID selection" seems only to have an effect to the the trace log message (first/last/add).

When my ACL module is not connected, there is no message like "first/last/add CAID 098C selected/to selection" and all HD+ channels are decrypted perfectly (with OSCam).

2017-12-29 17:48:47.082 [ INFO]:subscription: 0034: "192.168.0.31 [ kodi | Kodi Media Center ]" unsubscribing from "ProSieben HD", hostname="192.168.0.31", username="kodi", client="Kodi Media Center" 2017-12-29 17:48:47.085 [ INFO]:mpegts: 11464.25H in Astra 19.2E - tuning on STV090x Multistandard : DVB-S #0 2017-12-29 17:48:47.338 [ TRACE]:dvbcam: start service 0x5594cd087c80 2017-12-29 17:48:47.338 [ INFO]:subscription: 0038: "192.168.0.31 [ kodi | Kodi Media Center ]" subscribing on channel "SAT.1 HD", weight: 150, adapter: "STV090x Multistandard : DVB-S #0", network: "Astra 19.2E", mux: "11464.25H", provider: "ProSiebenSat.1", service: "SAT.1 HD", profile="htsp", hostname="192.168.0.31", username="kodi", client="Kodi Media Center" 2017-12-29 17:48:47.860 [ TRACE]:dvbcam: Astra 19.2E/11464.25H/SAT.1 HD: cannot find active service entry 2017-12-29 17:48:47.861 [ TRACE]:dvbcam: Astra 19.2E/11464.25H/SAT.1 HD: cannot find active service entry 2017-12-29 17:48:47.861 [ TRACE]:dvbcam: Astra 19.2E/11464.25H/sixx HD Austria: cannot find active service entry 2017-12-29 17:48:47.861 [ TRACE]:dvbcam: Astra 19.2E/11464.25H/Pro7 MAXX HD Austria: cannot find active service entry 2017-12-29 17:48:47.931 [ TRACE]:dvbcam: Astra 19.2E/11464.25H/kabel eins HD Austria: cannot find active service entry 2017-12-29 17:48:48.004 [ TRACE]:dvbcam: Astra 19.2E/11464.25H/ProSieben HD: cannot find active service entry 2017-12-29 17:48:48.074 [ TRACE]:dvbcam: Astra 19.2E/11464.25H/kabel eins HD: cannot find active service entry 2017-12-29 17:48:48.217 [WARNING]:TS: Astra 19.2E/11464.25H/SAT.1 HD: TELETEXT @ #32 Continuity counter error (total 1) 2017-12-29 17:48:48.244 [ TRACE]:dvbcam: Astra 19.2E/11464.25H/Pro7 MAXX HD: cannot find active service entry 2017-12-29 17:48:48.244 [ TRACE]:dvbcam: Astra 19.2E/11464.25H/SIXX HD: cannot find active service entry 2017-12-29 17:48:59.493 [ INFO]:mpegts: 11464.25H in Astra 19.2E scan complete

After connecting my ACL module, the HD+ channel, that I've subscribed before is still decrypted via OSCam. But when I switch to a HD+ channel I get errors...


2017-12-29 17:52:25.441 [ NOTICE]:linuxdvb: dvbca0-0: CAM slot 0 status changed to module init
2017-12-29 17:52:26.238 [ NOTICE]:linuxdvb: dvbca0-0: CAM slot 0 status changed to module connected
2017-12-29 17:52:27.538 [   INFO]:en50221: dvbca0-slot0-app00030041/0002: CAM supported CAIDs: 098C (NDS) 098C (NDS) 098C (NDS) 098C (NDS)
2017-12-29 17:52:27.538 [   INFO]:en50221: dvbca0-slot0-app00030041/0002: CAM supported CAIDs: 098C (NDS) 098C (NDS) 098C (NDS) 098C (NDS)
2017-12-29 17:52:27.538 [   INFO]:en50221: dvbca0-slot0-app00030041/0002: CAM supported CAIDs: 098C (NDS) 098C (NDS) 098C (NDS) 098C (NDS)
2017-12-29 17:52:27.538 [   INFO]:en50221: dvbca0-slot0-app00030041/0002: CAM supported CAIDs: 098C (NDS) 098C (NDS) 098C (NDS) 098C (NDS)
2017-12-29 17:52:27.538 [   INFO]:en50221: dvbca0-slot0-app00030041/0002: CAM supported CAIDs: 098C (NDS) 098C (NDS)
2017-12-29 17:52:27.538 [  TRACE]:dvbcam: register cam 0x5594ce018280 caids_count 18
2017-12-29 17:52:27.738 [ NOTICE]:linuxdvb: dvbca0-0: CAM slot 0 status changed to module ready
2017-12-29 17:52:28.538 [   INFO]:en50221: dvbca0-slot0-app00020041/0004: CAM INFO: AlphaCrypt, 01, 4A20, 4A22
2017-12-29 17:53:06.986 [   INFO]:subscription: 003B: "192.168.0.31 [ kodi | Kodi Media Center ]" unsubscribing from "ProSieben HD", hostname="192.168.0.31", username="kodi", client="Kodi Media Center"
2017-12-29 17:53:06.992 [   INFO]:mpegts: 11464.25H in Astra 19.2E - tuning on STV090x Multistandard : DVB-S #0
2017-12-29 17:53:07.255 [  TRACE]:dvbcam: start service 0x5594cd087c80
2017-12-29 17:53:07.255 [  TRACE]:dvbcam: dvbca0-0/0x5594cd087c80: match CAID 098C PID 6890 (1AEA)
2017-12-29 17:53:07.255 [  TRACE]:dvbcam: dvbca0-0/0x5594cd087c80: add CAID 098C to selection
2017-12-29 17:53:07.255 [ NOTICE]:ddci: CAM ci0 assigned to 0x5594cd087c80
2017-12-29 17:53:07.255 [  TRACE]:dvbcam: dvbca0-0/0x5594cd087c80: add ECM PID 6890 (1AEA) for CAID 098C
2017-12-29 17:53:07.255 [   INFO]:subscription: 003D: "192.168.0.31 [ kodi | Kodi Media Center ]" subscribing on channel "SAT.1 HD", weight: 150, adapter: "STV090x Multistandard : DVB-S #0", network: "Astra 19.2E", mux: "11464.25H", provider: "ProSiebenSat.1", service: "SAT.1 HD", profile="htsp", hostname="192.168.0.31", username="kodi", client="Kodi Media Center"
2017-12-29 17:53:07.664 [  TRACE]:dvbcam: 0x5594cd087c80: add EMM PID 4104 (1008) for CAID 098C
2017-12-29 17:53:07.737 [  TRACE]:dvbcam: Astra 19.2E/11464.25H/ProSieben HD: cannot find active service entry
2017-12-29 17:53:07.783 [  TRACE]:dvbcam: Astra 19.2E/11464.25H/kabel eins HD Austria: cannot find active service entry
2017-12-29 17:53:07.807 [  TRACE]:dvbcam: Astra 19.2E/11464.25H/sixx HD Austria: cannot find active service entry
2017-12-29 17:53:07.807 [  TRACE]:dvbcam: Astra 19.2E/11464.25H/Pro7 MAXX HD Austria: cannot find active service entry
2017-12-29 17:53:07.808 [  TRACE]:dvbcam: Astra 19.2E/11464.25H/kabel eins HD: cannot find active service entry
2017-12-29 17:53:07.953 [  TRACE]:dvbcam: Astra 19.2E/11464.25H/Pro7 MAXX HD: cannot find active service entry
2017-12-29 17:53:07.954 [  TRACE]:dvbcam: Astra 19.2E/11464.25H/SIXX HD: cannot find active service entry
2017-12-29 17:53:09.162 [   INFO]:en50221: dvbca0-0: ops menu: {"selectable":true}
2017-12-29 17:53:17.162 [WARNING]:subscription: 003D: service instance is bad, reason: No input detected
2017-12-29 17:53:17.164 [ NOTICE]:ddci: CAM ci0 unassigned from 0x5594cd087c80
2017-12-29 17:53:19.163 [ NOTICE]:subscription: 003D: No input source available for subscription "192.168.0.31 [ kodi | Kodi Media Center ]" to channel "SAT.1 HD"
2017-12-29 17:53:21.163 [ NOTICE]:subscription: 003D: No input source available for subscription "192.168.0.31 [ kodi | Kodi Media Center ]" to channel "SAT.1 HD"

It looks like DDCI itself is working pretty well, but the "decision" in TVH when to use what for decrypting has some issues...

Saen Acro

maby load-balance with active fail-back is needed ;)
CI = hop 0

Softcam = hop 1

of course this is code must be before before ddci and softcam

Jasmin Jessich


2017-12-29 17:52:27.538 [   INFO]:en50221: dvbca0-slot0-app00030041/0002: CAM supported CAIDs: 098C (NDS) 098C (NDS) 098C (NDS) 098C (NDS)
2017-12-29 17:52:27.538 [   INFO]:en50221: dvbca0-slot0-app00030041/0002: CAM supported CAIDs: 098C (NDS) 098C (NDS) 098C (NDS) 098C (NDS)
2017-12-29 17:52:27.538 [   INFO]:en50221: dvbca0-slot0-app00030041/0002: CAM supported CAIDs: 098C (NDS) 098C (NDS) 098C (NDS) 098C (NDS)
2017-12-29 17:52:27.538 [   INFO]:en50221: dvbca0-slot0-app00030041/0002: CAM supported CAIDs: 098C (NDS) 098C (NDS) 098C (NDS) 098C (NDS)
2017-12-29 17:52:27.538 [   INFO]:en50221: dvbca0-slot0-app00030041/0002: CAM supported CAIDs: 098C (NDS) 098C (NDS)
2017-12-29 17:52:27.538 [  TRACE]:dvbcam: register cam 0x5594ce018280 caids_count 18

This looks strange to me. The CAM reports 18 CAIDs, but there is always the same printed. I guess Jaroslav needs to look at this. He recently added the en50221 handling to TVH and I guess there is something not correct, at least with the printing.

I am missing the DD CI traces. Please trace with these trace settings: "linuxdvb,ddci,en50221,dvbcam". This will log much more, so maybe you should write it to a logfile. This is how I start for debugging:


./build.linux/tvheadend -l tvh.log --trace linuxdvb,ddci,en50221,dvbcam

The result is then in the file "tvh.log" in the execution directory.

Why I needs that?
I am not sure if DD CI is used for the service, even if it is assigned.

If it is really used, then the CAM doesn't decode your service.

> maby load-balance with active fail-back is needed ;)

As far as I understood the code, this should be already the case, when DD CI is used by a service (currently only one service per DD CI possible).

A DVB CAM is always searched first (highest priority) and DD CI is a DVB CAM.

BR,
Jasmin