Support Digital Devices CI Interfaces

Jasmin Jessich · 2017-11-12T19:42:48+00:00

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...

Alexander P

Today I had some time for further debugging...

Here are the results of the logs: https://pastebin.com/CjdHJQjp

Log started with viewing a V14 (ACL) encrypted channel, than switching to a HD01 (oscam) encrypted channel (line 895), than disbaling the CI slot (line 1901).

I hope, this log will help you, because I have no idea what it means ^^

Saen Acro

Jasmin Jessich wrote:
> [...]
> 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:
> [...]
> The result is then in the file "tvh.log" in the execution directory.
> BR,

> Jasmin

this is fixed #4400

Jasmin Jessich

Alexander P wrote:

> Here are the results of the logs: https://pastebin.com/CjdHJQjp

I am not sure if the problem is solved in the recent TVH version. If no, here is the

analysis of the logfile (sorry for the delay, but I am still on vacation):


2018-01-07 13:38:57.158 [  TRACE]:ddci: CAM ci0 recv rd(CAM ->):494592, wr:494592
2018-01-07 13:38:57.158 [  TRACE]:ddci: CAM ci0 send buff rd(-> CAM):456950, wr:456950
---> This lines are telling us that the DD CI CAM is getting data and the data is read from
     the CAM, too.
     And I can tell you, the CAM was able to descramble it, because there is no line
     containing "scrambled packets from CAM".

2018-01-07 13:39:09.588 [ NOTICE]:ddci: CAM ci0 unassigned from 0x5594ca71e660
2018-01-07 13:39:09.588 [  TRACE]:ddci: CAM ci0 send buff rd(-> CAM):508317, wr:508317
---> Now you stopped watching the service, which was using the CAM.

2018-01-07 13:39:10.099 [  TRACE]:dvbcam: start service 0x5594cd075ff0
2018-01-07 13:39:10.099 [  TRACE]:dvbcam: dvbca0-0/0x5594cd075ff0: match CAID 098C PID 6892 (1AEC)
2018-01-07 13:39:10.099 [  TRACE]:dvbcam: dvbca0-0/0x5594cd075ff0: add CAID 098C to selection
2018-01-07 13:39:10.099 [ NOTICE]:ddci: CAM ci0 assigned to 0x5594cd075ff0
2018-01-07 13:39:10.099 [  TRACE]:dvbcam: dvbca0-0/0x5594cd075ff0: add ECM PID 6892 (1AEC) for CAID 098C
---> Now you started a service, which requires a descrambler. TVH did select again the DD CI
     CAM, because of the CAID of the service. Because the DD CI CAM was not used at this time
     TVH was able to choose it (based on the CAID).

2018-01-07 13:39:11.694 [  TRACE]:en50221: dvbca0-slot0-app00400041/0006: display control sending reply
2018-01-07 13:39:11.994 [  TRACE]:en50221: 9F 88 03 0B 97 41 6C 70 68 61 43 72 79 70 74 9F .....AlphaCrypt.
2018-01-07 13:39:11.994 [  TRACE]:en50221: 88 03 01 20 9F 88 03 10 05 44 72 FC 63 6B 65 6E ... .....Dr.cken
2018-01-07 13:39:11.994 [  TRACE]:en50221: 20 53 69 65 20 4F 4B 20 9F 88 03 1C 53 69 65 20  Sie OK ....Sie 
2018-01-07 13:39:11.994 [  TRACE]:en50221: 68 61 62 65 6E 20 6B 65 69 6E 65 20 42 65 72 65 haben keine Bere
2018-01-07 13:39:11.994 [  TRACE]:en50221: 63 68 74 69 67 75 6E 67 9F 88 03 1E 64 69 65 73 chtigung....dies
2018-01-07 13:39:11.994 [  TRACE]:en50221: 65 73 20 50 72 6F 67 72 61 6D 6D 20 7A 75 20 65 es Programm zu e
2018-01-07 13:39:11.994 [  TRACE]:en50221: 6D 70 66 61 6E 67 65 6E 20 21 80 02 01 00       mpfangen !....
---> This tells us, that the CAM can't descramble the selected service.

Q: Why you define the CAID of a service which can't be descrambled by your CAM in the

CAID list?


2018-01-07 13:39:17.252 [  TRACE]:ddci: CAM ci0 recv rd(CAM ->):566496, wr:566496 
2018-01-07 13:39:17.252 [  TRACE]:ddci: CAM ci0 got 48624 scrambled packets from CAM
2018-01-07 13:39:17.252 [  TRACE]:ddci: CAM ci0 send buff rd(-> CAM):20892, wr:20892
---> This tells us, that DD CI sends/receives data to/from the CAM, but the CAM couldn't,
     descramble the TS stream. Which is clear, because the CAM told us already, that it will
     be not able to descramble the stream, with the CAID 098C.

There is a setting in the Alpha Crypt CAM to announce all CAIDs or only those, the smart

card does really support. You should set it to announce only the supported ones.

If you think there is still a problem in TVH, we need to dig deeper in this and add debug
outputs in the selection mechanism. In my opinion the code in dvbcam does what it should
do and does select the DD CI CAM based on the CAIDs and if it is free (currently only one

service per DD CI).

BR,

Jasmin

Saen Acro

@Jasmin Jessich
In current condition DD code not handle
http://en.aston-france.com/cams/conax-professional.php

or some of the "hybrid" cams with also can handle more then one service at time.

On other side, standard operators cam, can handle two services simultaneous,
to make PiP (Picture in Picture) work.

Jasmin Jessich

My answer was concerning the problem Alexander P. has observed.

saen acro wrote:
> In current condition DD code not handle
> http://en.aston-france.com/cams/conax-professional.php

> or some of the "hybrid" cams with also can handle more then one service at time.

Äh yes, and?
I know that several CAMs can handle more than one service, but the first part of the DD CI integration to TVH was only ONE Service per CAM.

I already started to work om MCD (second step), but this will take some time (currently I am on vacation).

BR,
Jasmin
<<

Saen Acro

Don't hurry back from vacation,
Don't get loaded with complicated mental activities,

Even rest for us.

Later we will recall for this ;)

Jasmin Jessich

Hello TVH and DD CI users!

I have implemented MCD (Multi Channel Decoding), the second step, to the DD CI code.

There is currently no MTD (Multi Tuner Decoding) implemented.

I tested this with my ORF card in an Alphacrypt CAM with "ORF1 HD", "ORF2W HD" and "ServusTV HD Oesterreich" (these are all on the same transponder).

Please note, that you have to activate "CAM can decode multi channels" and set the "Service limit" to the number of channels your CAM can decode (3 or 4 is a good value for the Alphacrypt CAM) in the CA configuration.

You can find the code at GitHub on the ddci_mcd branch:
> https://github.com/jasmin-j/tvheadend/tree/ddci_mcd Configure it with the new option "--enable-ddci_mcd".

I will submit a pull request when some people did test this. Please write your experience here or send me an eMail.

Have fun and BR,
Jasmin

Alexander P

Hello Jasmin,

I hope you had a nice vacation :)

On my setup your MCD implementation looks good! I was able to decode two Sky channels at the same time (on the same transponder).

My previous problem using OSCam and DDCI at the same time, still exists...
I didn't find any settings in the ACL to configure the "announcement" of supported CAIDs...

Jasmin Jessich

Hello Alexander!

> On my setup your MCD implementation looks good! I was able to decode two Sky channels at the same time (on the same transponder).

Perfect! THX for testing this. I will change the commits on the branch and then do the PR.

> I didn't find any settings in the ACL to configure the "announcement" of supported CAIDs...

First of all, I have an AlphaCrypt 3.27 from Mascom and not the ACL. So maybe the ACL doesn't support such a setting.
My CAM reports:

CAM INFO: AlphaCrypt, 01, 4A20, 4A20

On my CAM it is in the Expert Menue:

CA-Systems: Single dbox Compatibility: on

> My previous problem using OSCam and DDCI at the same time, still exists...

As I wrote already I don't understand why. When the HW CAM is used completely (limit set to 1), TVH should select automatically the next descrambler which can decode the stream. And this can be a SW CAM also.

My CAM is also announcing all CAIDs:


CAM supported CAIDs: 0D95 (CryptoWorks ICE) 0648 (Irdeto) 1702 (BetaCrypt) 1722 (BetaCrypt)
CAM supported CAIDs: 1762 (BetaCrypt) 4A20 (0x4a20) 0500 (Viaccess) 0B00 (Conax)
CAM supported CAIDs: 0100 (Seca) 1833 (NagraVision) 1834 (NagraVision) 0D05 (CryptoWorks)
CAM supported CAIDs: 0D22 (CryptoWorks)
caids_count 13

I do now select only the correct CAID (0D95) in the list on the WEB UI.

Then I get this:

dvbcam: dvbca0-0/0x7fcdc528e300: match CAID 0D95 PID 0 (0000) dvbcam: dvbca0-0/0x7fcdc528e300: add CAID 0D95 to selection ddci: CAM ci2 assigned to 0x7fcdc528e300

When I tune now to a channel on the same transponder and the limit is set to 1, TVH will not find a CAM.

Then TVH should execute the start function of all other registered CA clients. This is done in "caclient_start" (caclient.c):


  TAILQ_FOREACH(cac, &caclients, cac_link)
    if (cac->cac_enabled)
      cac->cac_start(cac, t);

To prove that, you can add a debug line to "cclient.c" (I think this is used for OsCAM) after this line (1055):


 "extern const idclass_t mpegts_service_class;"

The debug line:


  tvhtrace(LS_DVBCAM, "Card Client");

Start TVH with this parameters or enable the tracing in the GUI.

-l tvh.log --trace linuxdvb,ddci,dvbcam

In fact the code in "cc_service_start" should then select the SW CAM.
If you see the added debug line, you need to add more debug code to "cc_service_start" to find why your SW CAM is not selected.
If you don't see the debug line, then add debug lines to "caclient_start" and find why it does not execute the start functions of all registered CAM class types. In "caclient_create"(caclient.c) all the CAM class create functions are executed.

Sorry, but I can't do more for you then explaining you how you can debug that.

BR,
Jasmin

Jasmin Jessich

Hi!

I think I was wrong with assuming OsCAM is handled by the cclient :(

It is handled by capmt, so you need to add the debug printing to "capmt_service_start".

BR,
Jasmin

Jasmin Jessich

Hi!

> I will submit a pull request when some people did test this.
My pull request has been accepted!

DD CI MCD support is now available on TVH master.

With that the second phase of the DD CI integration is finished.

When I have time I will start with MTD (https://tvheadend.org/issues/4750), the third step. Please note, this is not that simple and requires to touch other parts in TVH beside the DD CI code (e.g.: CA-PMT generation). So this will require some design (eMails to Jaroslav) in advance. Don't expect this feature soon, as I will work at first on a CI related problem in the Kernel (EN 50221 protocol driver).

BR,
Jasmin

Saen Acro

Maybe stupid question bit, is it can descramble services on different tuners/transponders on same TAB

Jasmin Jessich

> can descramble services on different tuners/transponders on same TAB
No, because a tuner on the same TAB is also another tuner and therefore another mux/input for TVH.

Alfons Zitterbacke

Hi,

thanks for this cool piece of work! I am using an up-to-date Arch Linux machine with Tvheadend 4.3-1133~ge339005ab (just build today). I have a couple issues and I'd like to get your advice on them:

1. The descrambled stream apparently contains video only:
- Regardless of which stream profile I choose, VLC only reports (and plays) a singe stream (video).
- If I use Tvheadend to record the stream, VLC does the same thing with the recorded file. Also, TSDoctor (the software I use to cut recordings) reports that the scream starts scrambled. It offers to cut away these scrambled bits, ending up with only a video stream (and, curiously, a Teletext stream -- although I am not sure I'd trust this info).

- The Tvheadend log doesn't provide any clues, except maybe for the message "Invalid start code" (followed by some number, e.g. d8:95:b9) right when it starts the stream.

2. EMMs are apparently not sent (or written?) to the card. (Using the same CAM/CI combination in an Octopus Net box worked perfectly, so I don't think it's the hardware's fault.)

Does anyone have an idea what I could do about these issues?

Jasmin Jessich

> 1. The descrambled stream apparently contains video only:
I have no clue why this happens. The dvbcam code gets the PIDs to subscribe from the PAT/PMT. I never observed such a behaviour during my tests.
When you save record the resulting stream with


   wget -O a.ts "http://admin:admin@vdr-jasmin:9981/stream/channelname/ORF1 HD?profile=pass"

Change:


  admin:admin -> username:password
  vdr-jasmin  -> IP of your TVH box
  ORF1 HD     -> service name

Then you can use DVBinspector (https://sourceforge.net/projects/dvbinspector/files) to analyse the a.ts file.

In should contain the PAT, PMT and all the A/V streams. Maybe you can find by analysing PAT/PMT what is wrong.

> Also, TSDoctor (the software I use to cut recordings) reports that the scream starts scrambled.

This is normal because the CAM needs some time before it can decode. But is does decode, so all the required ECMs are sent to the CAM.

> - The Tvheadend log doesn't provide any clues, except maybe for the message "Invalid start code"

I don't know what this means ... .

> 2. EMMs are apparently not sent (or written?) to the card.
There is code to subscribe the EMM PIDs. I can re-test if this is really working. Maybe there is a problem with the CAT decoder.
You could activate tracing for dvbcam (see above in this thread for more info). You should then see lines:


 "add EMM PID ??? (???) for CAID ???"

> Does anyone have an idea what I could do about these issues?
I have no idea, but we need to debug this with your help.

And you can contact me per eMail also.

BR,
Jasmin

Alexander P

Finally I had some time for some debugging...

After upgrading from jessie to stretch, I had some issues with the build of the openssl components...

After "fixing" it (dependency is libssl1.0-dev, not longer libssl-dev), I added some debug lines.

When switching to an oscam channel or an alphacrypt light channel, "caclient_start" and "capmt_service_start" are executed... at this level, there seems to be no difference...
Any idea what makes sense to check next?

Jasmin Jessich

> When switching to an oscam channel or an alphacrypt light channel, "caclient_start" and "capmt_service_start" are executed...
Which is clear (I wrote this already in my previous post https://tvheadend.org/d/5337-support-digital-devices-ci-interfaces?r=31478#message-31478):

Then TVH should execute the start function of all other registered CA clients. This is done in "caclient_start" (caclient.c)

> Any idea what makes sense to check next?

You need to add debug prints to dvbcam_service_start and capmt_service_start and find out which of the CA clients is used and why dvbcam_service_start wins. In Theory it should return without selecting the CAM for the new service, when there is no free slot available (limit set to 1).

BR,
Jasmin

Stian B. Barmen

Hello, I am not a DVB expert but I have been using my digitaldevices setup on windows for years and finally it seems a linux solutution is on the horizon!

Right now I am running the HTS Tvheadend 4.3-1500~g7185713f4~bionic version and I can finally get my CI to decode my channels, jay!! Only issue is that I have on CI CAM and that is shared on 4 tuners. On Windows I can share this CI and it is bought especially to have the ability to do 8 decodes in paralell if needed. :P

Is there any way I can enable to share this CAM for all my tuners? I am running on Mint 19 currently.

Thanks!

Stian B. Barmen

Got this email from Digital Devices:

The only what you can do is to make a redirect from one tuner to one CI, but you have no MTD and can only decrypt channels from one transponder.

Here you can find instruction how you can make a redirect:

https://github.com/DigitalDevices/dddvb/blob/master/docs/redirect

MTD is a hack in the Windows driver and only available in Windows, under Linux the TV software must support it.

A TV Software which should support this is VDR(2.4.0).

Stian B. Barmen

No input on this?

Attached a picture of my CA settings. When I hover over the "CAM can decode multiple channels" I see the text, enable MCD and MTD for this CAM so it seems the functionality is enabled but not working correctly.

Here is some data from my logs:

Nov 1 09:33:34 mint tvheadend[10691]: subscription: 0028: service instance is bad, reason: No descrambler Nov 1 09:33:35 mint tvheadend[10691]: mpegts: 298MHz in DVB-C Network - tuning on ST STV0367 DDB DVB-C/T #3 : DVB-C #0 Nov 1 09:33:35 mint tvheadend[10691]: subscription: 0036: "epggrab" subscribing to mux "298MHz", weight: 4, adapter: "ST STV0367 DDB DVB-C/T #3 : DVB-C #0", network: "DVB-C Network", service: "Raw PID Subscription" Nov 1 09:33:35 mint tvheadend[10691]: mpegts: mux 354MHz in DVB-C Network old params DVB-C freq 354000000 sym 6952000 mod QAM/256 fec NONE ds 0 plp -1 (00020000) Nov 1 09:33:35 mint tvheadend[10691]: mpegts: mux 354MHz in DVB-C Network new params DVB-C freq 354000000 sym 6952000 mod QAM/256 fec 3/5 ds 0 plp -1 (00020000) Nov 1 09:33:36 mint tvheadend[10691]: mpegts: mux 362MHz in DVB-C Network old params DVB-C freq 362000000 sym 6952000 mod QAM/256 fec NONE ds 0 plp -1 (00020000) Nov 1 09:33:36 mint tvheadend[10691]: mpegts: mux 362MHz in DVB-C Network new params DVB-C freq 362000000 sym 6952000 mod QAM/256 fec 3/5 ds 0 plp -1 (00020000) Nov 1 09:33:36 mint tvheadend[10691]: mpegts: mux 370MHz in DVB-C Network old params DVB-C freq 370000000 sym 6952000 mod QAM/256 fec NONE ds 0 plp -1 (00020000) Nov 1 09:33:36 mint tvheadend[10691]: mpegts: mux 370MHz in DVB-C Network new params DVB-C freq 370000000 sym 6952000 mod QAM/256 fec 3/5 ds 0 plp -1 (00020000) Nov 1 09:33:36 mint tvheadend[10691]: mpegts: mux 378MHz in DVB-C Network old params DVB-C freq 378000000 sym 6952000 mod QAM/256 fec NONE ds 0 plp -1 (00020000) Nov 1 09:33:36 mint tvheadend[10691]: mpegts: mux 378MHz in DVB-C Network new params DVB-C freq 378000000 sym 6952000 mod QAM/256 fec 3/5 ds 0 plp -1 (00020000) Nov 1 09:33:36 mint tvheadend[10691]: mpegts: mux 386MHz in DVB-C Network old params DVB-C freq 386000000 sym 6952000 mod QAM/256 fec NONE ds 0 plp -1 (00020000) Nov 1 09:33:36 mint tvheadend[10691]: mpegts: mux 386MHz in DVB-C Network new params DVB-C freq 386000000 sym 6952000 mod QAM/256 fec 3/5 ds 0 plp -1 (00020000) Nov 1 09:33:36 mint tvheadend[10691]: mpegts: mux 402MHz in DVB-C Network old params DVB-C freq 402000000 sym 6952000 mod QAM/256 fec NONE ds 0 plp -1 (00020000) Nov 1 09:33:36 mint tvheadend[10691]: mpegts: mux 402MHz in DVB-C Network new params DVB-C freq 402000000 sym 6952000 mod QAM/256 fec 3/5 ds 0 plp -1 (00020000) Nov 1 09:33:36 mint tvheadend[10691]: mpegts: mux 410MHz in DVB-C Network old params DVB-C freq 410000000 sym 6952000 mod QAM/256 fec NONE ds 0 plp -1 (00020000) Nov 1 09:33:36 mint tvheadend[10691]: mpegts: mux 410MHz in DVB-C Network new params DVB-C freq 410000000 sym 6952000 mod QAM/256 fec 3/5 ds 0 plp -1 (00020000) Nov 1 09:33:36 mint tvheadend[10691]: mpegts: mux 418MHz in DVB-C Network old params DVB-C freq 418000000 sym 6952000 mod QAM/256 fec NONE ds 0 plp -1 (00020000) Nov 1 09:33:36 mint tvheadend[10691]: mpegts: mux 418MHz in DVB-C Network new params DVB-C freq 418000000 sym 6952000 mod QAM/256 fec 3/5 ds 0 plp -1 (00020000) Nov 1 09:33:36 mint tvheadend[10691]: mpegts: mux 426MHz in DVB-C Network old params DVB-C freq 426000000 sym 6952000 mod QAM/256 fec NONE ds 0 plp -1 (00020000) Nov 1 09:33:36 mint tvheadend[10691]: mpegts: mux 426MHz in DVB-C Network new params DVB-C freq 426000000 sym 6952000 mod QAM/256 fec 3/5 ds 0 plp -1 (00020000) Nov 1 09:33:36 mint tvheadend[10691]: mpegts: mux 474MHz in DVB-C Network old params DVB-C freq 474000000 sym 6952000 mod QAM/256 fec NONE ds 0 plp -1 (00020000) Nov 1 09:33:36 mint tvheadend[10691]: mpegts: mux 474MHz in DVB-C Network new params DVB-C freq 474000000 sym 6952000 mod QAM/256 fec 3/5 ds 0 plp -1 (00020000) Nov 1 09:33:37 mint tvheadend[10691]: subscription: 0028: No input source available for subscription "10.0.0.114 [ tv | Kodi Media Center ]" to channel "TV Norge HD"

These logs are captured when one channels live and working on one client and I try to play another channel on another client (both KODI). I have only two DVB-C cards running, and I have enabled them one at a time to check that they work. Is there any more tricks I should do?

This is my dmesg:


[ 6731.246159] ddbridge 0000:02:00.0: DVB: adapter 3 frontend 0 frequency 4294967274 out of range (48000000..864000000)
[ 6731.246501] ddbridge 0000:02:00.0: DVB: adapter 2 frontend 0 frequency 4294967274 out of range (48000000..864000000)
[ 6731.246787] ddbridge 0000:02:00.0: DVB: adapter 1 frontend 0 frequency 4294967276 out of range (48000000..864000000)
[ 6731.247110] ddbridge 0000:02:00.0: DVB: adapter 0 frontend 0 frequency 4294967285 out of range (48000000..864000000)
[ 6732.091670] dvb_ca_en50221: dvb_ca adapter 4: DVB CAM detected and initialised successfully
[ 7901.424178] perf: interrupt took too long (2540 > 2500), lowering kernel.perf_event_max_sample_rate to 78500
[ 8047.807309] dvb_ca_en50221: dvb_ca adapter 4: DVB CAM detected and initialised successfully
[ 8059.315281] ddbridge 0000:02:00.0: DVB: adapter 3 frontend 0 frequency 4294967279 out of range (48000000..864000000)
[ 8059.316445] ddbridge 0000:02:00.0: DVB: adapter 2 frontend 0 frequency 4294967281 out of range (48000000..864000000)
[ 8059.317556] ddbridge 0000:02:00.0: DVB: adapter 1 frontend 0 frequency 4294967276 out of range (48000000..864000000)
[ 8059.318820] ddbridge 0000:02:00.0: DVB: adapter 0 frontend 0 frequency 4294967286 out of range (48000000..864000000)
[ 8060.159265] dvb_ca_en50221: dvb_ca adapter 4: DVB CAM detected and initialised successfully
[ 8829.345902] dvb_ca_en50221: dvb_ca adapter 4: DVB CAM detected and initialised successfully
[ 8839.094109] ddbridge 0000:02:00.0: DVB: adapter 3 frontend 0 frequency 4294967285 out of range (48000000..864000000)
[ 8839.094686] ddbridge 0000:02:00.0: DVB: adapter 2 frontend 0 frequency 4294967285 out of range (48000000..864000000)
[ 8839.096071] ddbridge 0000:02:00.0: DVB: adapter 1 frontend 0 frequency 4294967276 out of range (48000000..864000000)
[ 8839.096583] ddbridge 0000:02:00.0: DVB: adapter 0 frontend 0 frequency 4294967281 out of range (48000000..864000000)
[ 8839.938050] dvb_ca_en50221: dvb_ca adapter 4: DVB CAM detected and initialised successfully

# Sorry one image is wrong, but I dont know how to delete it.

« Previous Page Next Page »