I do not have such cable installed.

Would I need such a cable? Before I would spend money buying such a cable, can you explain what makes you think that cable is needed?

I did believe this section in the log tells us packets are being sent to the CAM for descambling, however they are returned descambled. I might be completely wrong of course! Just wanting to learn about it...

2021-01-04 10:00:08.910 [  TRACE]:ddci: CAM ci0 recv rd(CAM ->):5376, wr:5376
2021-01-04 10:00:08.910 [  TRACE]:ddci: CAM ci0 got 5225 scrambled packets from CAM
2021-01-04 10:00:08.910 [  TRACE]:ddci: CAM ci0 send buff rd(-> CAM):5694, wr:5694
5 days later
Just for those that are interested in my solution:
I setup minisatip to handle the heavy lifting with tuners and ci modules. minisatip does have MTD support and within TvHeadend it does not matter much if you use the tuners using minisatip or directly.
My CI is working with TVHeadend and able to descramble multiple channels from 1 mux (MCD),

but after while (few days or weeks) it always stops working and begin logging same message as noted above (*You are not entitled, to receive this programme !*)

When I pull the module from Octopus and insert it to the TV, it "reactivates" and I am able to use it with TVHeadend for a while.

Then I must reactivate it again..

Robin Brouwer wrote:
> Just for those that are interested in my solution:

> I setup minisatip to handle the heavy lifting with tuners and ci modules. minisatip does have MTD support and within TvHeadend it does not matter much if you use the tuners using minisatip or directly.

Thanks for info, can you share how exactly you made it?

I guess this will be a bit offtopic, but I doubt anyone will care...

It depends on how you setup linux. I'm using Ubuntu 20.04, which comes with kernel drivers for my tuner. (I only had to recompile the kernel for setting CONFIG_DVB_MAX_ADAPTERS to something higher than 8!)

After that I did: 

git clone https://github.com/catalinii/minisatip
./configure
nano src/Makefile
make
In the src/Makefile file 1 line should be changed (hence the nano command). DDCI=0 should be changed into DDCI=1, which made the section at the top end up looking like:

CC=gcc
EMBEDDED=0
DVBCSA=1
DVBAES=1
DVBCA=1
SATIPCLIENT=1
NETCVCLIENT=0
STATIC=0
DVBAPI=1
LINUXDVB=1
AXE=0
ENIGMA=0
DDCI=1
T2MI=0

If for you things like DVBCSA or DVBAES or DVBCA are set to 0, it's time to apt install some extra libs and start again with ./configure! There's also a possible DDCI_TEST=1, which you could add below DDCI. Then minisatip should work in case you use DD's drivers.

After compiling is completed, follow the steps in tools/autostart.readme for installing it into Ubuntu.

And then finally you will of course disable all tuners in Tvheadend and enable those coming from minisatip!
2 months later
Robin Brouwer wrote:
> I guess this will be a bit offtopic, but I doubt anyone will care...
>
> It depends on how you setup linux. I'm using Ubuntu 20.04, which comes with kernel drivers for my tuner. (I only had to recompile the kernel for setting CONFIG_DVB_MAX_ADAPTERS to something higher than 8!)
>
> After that I did: [...]In the src/Makefile file 1 line should be changed (hence the nano command). DDCI=0 should be changed into DDCI=1, which made the section at the top end up looking like:
> [...]
> If for you things like DVBCSA or DVBAES or DVBCA are set to 0, it's time to apt install some extra libs and start again with ./configure! There's also a possible DDCI_TEST=1, which you could add below DDCI. Then minisatip should work in case you use DD's drivers.
>
> After compiling is completed, follow the steps in tools/autostart.readme for installing it into Ubuntu.
>

> And then finally you will of course disable all tuners in Tvheadend and enable those coming from minisatip!

Hi Robin,
How have you started the ./minisatip? Have you added any options for it?
I have build the minisatip (with the DDCI=1), disabled all tuners at the TVH and started ./minisatip, then tried to configure sat2ip tuner(s) at the TVH. Free to Air channels works well, but not the Encrypted. Card is
Digital Devices OctopusCI S2 Pro Advanced - Twin CI and Twin DVB-S2 Tuner for PCIe Slot
a month later
saen acro wrote:
> Robin Brouwer wrote:
> > saen acro wrote:
> > > Disable messages
> > > [...]
> > >
> > > is tuner and ci are on same TAB?
> >
> > The tuner and ci are different adapters; Digital Devices Max A8i TV Card + Octopus Twin CI. I believe there's no bridging is available for that hardware combination (if it is, I will post dmesg so we can see that) and I believe with dd ci that is not needed, right?
> >
> > Turning "Smartcard Messages: OFF" will remove those nasty "ops menu: {"selectable":true,"title":"AlphaCrypt","subtitle":" ","bottom":"Press OK","choices":["You are not entitled","to receive this programme !"]}" lines, but it will not descamble with that OFF either.
>
> https://www.digital-devices.eu/shop/en/accessoires/cables/156/ribbon-cable-12-cm-data-cable-for-connection-of-expansion-modules?c=175 >

> do you have such cable? from tuner to CI?

Bullshit: there is no cable from "tuner to CI".
_ mpajer wrote:
> My CI is working with TVHeadend and able to descramble multiple channels from 1 mux (MCD),

> but after while (few days or weeks) it always stops working and begin logging same message as noted above (*You are not entitled, to receive this programme !*)

After 12 weeks.

> When I pull the module from Octopus and insert it to the TV, it "reactivates" and I am able to use it with TVHeadend for a while.
> Then I must reactivate it again..

>

There is no entitlement handling within TVH. This is the procdure you have to have when using tvh.
saen acro wrote:
> Disable messages
> [...]
>

> is tuner and ci are on same TAB?

There is no possiblity on DD HW to have tuner and ci on the same tab.
the man wrote:
> Robin Brouwer wrote:
> > I guess this will be a bit offtopic, but I doubt anyone will care...
> >
> > It depends on how you setup linux. I'm using Ubuntu 20.04, which comes with kernel drivers for my tuner. (I only had to recompile the kernel for setting CONFIG_DVB_MAX_ADAPTERS to something higher than 8!)
> >
> > After that I did: [...]In the src/Makefile file 1 line should be changed (hence the nano command). DDCI=0 should be changed into DDCI=1, which made the section at the top end up looking like:
> > [...]
> > If for you things like DVBCSA or DVBAES or DVBCA are set to 0, it's time to apt install some extra libs and start again with ./configure! There's also a possible DDCI_TEST=1, which you could add below DDCI. Then minisatip should work in case you use DD's drivers.
> >
> > After compiling is completed, follow the steps in tools/autostart.readme for installing it into Ubuntu.
> >
> > And then finally you will of course disable all tuners in Tvheadend and enable those coming from minisatip!
>
> Hi Robin,
> How have you started the ./minisatip? Have you added any options for it?
> I have build the minisatip (with the DDCI=1), disabled all tuners at the TVH and started ./minisatip, then tried to configure sat2ip tuner(s) at the TVH. Free to Air channels works well, but not the Encrypted. Card is

> Digital Devices OctopusCI S2 Pro Advanced - Twin CI and Twin DVB-S2 Tuner for PCIe Slot

Would you pls show the dmesg output for these solution ? Especially the

lines with "tab" are important.

For minisatip you have to use the ddbridge reallocation option.

Search for adapter_alloc=3.

It is not needed to disable all tuners within tvh. But make sure that only one of these two is running.

Unfortunatly a reboot is needed when swizching between minisatip and tvh. ddbridge states that

the needed echo command may not work if the module has been in use :(


@ user#26583 why not edit your posts, and not flood so many serial post's
saen acro wrote:

> @ user#26583 why not edit your posts, and not flood so many serial post's

Dont understand.
Der Depp vom Dienst wrote:
> saen acro wrote:
> > @ user#26583 why not edit your posts, and not flood so many serial post's
>

> Dont understand.

Edit your last post, do not post new one, there is a yellow pencil for that.
saen acro wrote:
> Der Depp vom Dienst wrote:
> > saen acro wrote:
> > > @ user#26583 why not edit your posts, and not flood so many serial post's
> >
> > Dont understand.
>

> Edit your last post, do not post new one, there is a yellow pencil for that.

Why ? I didn't get the point.
Der Depp vom Dienst wrote:
> the man wrote:
> Would you pls show the dmesg output for these solution ? Especially the
> lines with "tab" are important.
>
> For minisatip you have to use the ddbridge reallocation option.
> Search for adapter_alloc=3.
>
> It is not needed to disable all tuners within tvh. But make sure that only one of these two is running.
>
> Unfortunatly a reboot is needed when swizching between minisatip and tvh. ddbridge states that

> the needed echo command may not work if the module has been in use :(

I use the drivers included multimedia part of the ubuntu kernel. I did not set them up with adapter_alloc=3 as compiling minisatip with ddci=1 does allow it to use the cam when needed for a stream with mtd!

dmesg for my tuner is:

[    3.355202] mc: Linux media interface: v0.10
[    3.363565] ddbridge: Digital Devices PCIE bridge driver 0.9.33-integrated, Copyright (C) 2010-17 Digital Devices GmbH
[    3.377520] xen: --> pirq=19 -> irq=36 (gsi=36)
[    3.378126] ddbridge 0000:00:05.0: detected Digital Devices Octopus CI
[    3.378152] ddbridge 0000:00:05.0: HW 0101000c REGMAP 00010005
[    3.384300] ddbridge 0000:00:05.0: Port 0: Link 0, Link Port 0 (TAB 1): NO MODULE
[    3.389492] ddbridge 0000:00:05.0: Port 1: Link 0, Link Port 1 (TAB 2): NO MODULE
[    3.389494] ddbridge 0000:00:05.0: Port 2: Link 0, Link Port 2 (TAB 3): CI internal
[    3.389495] ddbridge 0000:00:05.0: Port 3: Link 0, Link Port 3 (TAB 4): CI internal
[    3.390257] dvbdev: DVB: registering new adapter (DDBridge)
[    3.390258] dvbdev: DVB: registering new adapter (DDBridge)
[    3.398115] xen: --> pirq=16 -> irq=40 (gsi=40)
[    3.398401] ddbridge 0000:00:06.0: detected Digital Devices MAX A8 C2T2I
[    3.398410] ddbridge 0000:00:06.0: HW 00010008 REGMAP 00010002
[    3.517240] ddbridge 0000:00:06.0: Port 0: Link 0, Link Port 0 (TAB 1): DUAL DVB-C2T2 ISDB-T CXD2854
[    3.521698] ddbridge 0000:00:06.0: Port 1: Link 0, Link Port 1 (TAB 2): DUAL DVB-C2T2 ISDB-T CXD2854
[    3.526162] ddbridge 0000:00:06.0: Port 2: Link 0, Link Port 2 (TAB 3): DUAL DVB-C2T2 ISDB-T CXD2854
[    3.530211] ddbridge 0000:00:06.0: Port 3: Link 0, Link Port 3 (TAB 4): DUAL DVB-C2T2 ISDB-T CXD2854
[    3.530778] dvbdev: DVB: registering new adapter (DDBridge)
[    3.530778] dvbdev: DVB: registering new adapter (DDBridge)
[    3.530779] dvbdev: DVB: registering new adapter (DDBridge)
[    3.530779] dvbdev: DVB: registering new adapter (DDBridge)
[    3.530779] dvbdev: DVB: registering new adapter (DDBridge)
[    3.530780] dvbdev: DVB: registering new adapter (DDBridge)
[    3.530780] dvbdev: DVB: registering new adapter (DDBridge)
[    3.530780] dvbdev: DVB: registering new adapter (DDBridge)
[    3.538668] i2c i2c-2: cxd2841er_attach(): I2C adapter 00000000097c5629 SLVX addr 6e SLVT addr 6c
[    3.538741] i2c i2c-2: cxd2841er: i2c wr failed=-5 addr=6c reg=00 len=1
[    3.540984] i2c i2c-2: cxd2841er_attach(): attaching CXD2854ER DVB-C/C2/T/T2/ISDB-T frontend
[    3.540985] i2c i2c-2: cxd2841er_attach(): chip ID 0xc1 OK.
[    3.556833] ddbridge 0000:00:06.0: DVB: registering adapter 2 frontend 0 (Sony CXD2854ER DVB-T/T2/C and ISDB-T demodulator)...
[    3.557070] i2c i2c-2: cxd2841er_attach(): I2C adapter 00000000097c5629 SLVX addr 6f SLVT addr 6d
[    3.558107] i2c i2c-2: cxd2841er: i2c wr failed=-5 addr=6d reg=00 len=1
[    3.560209] i2c i2c-2: cxd2841er_attach(): attaching CXD2854ER DVB-C/C2/T/T2/ISDB-T frontend
[    3.560210] i2c i2c-2: cxd2841er_attach(): chip ID 0xc1 OK.
[    3.576106] tda18212 2-0063: NXP TDA18212HN/S successfully identified
[    3.576124] ddbridge 0000:00:06.0: DVB: registering adapter 3 frontend 0 (Sony CXD2854ER DVB-T/T2/C and ISDB-T demodulator)...
[    3.576321] i2c i2c-3: cxd2841er_attach(): I2C adapter 000000002b4b965e SLVX addr 6e SLVT addr 6c
[    3.577276] i2c i2c-3: cxd2841er: i2c wr failed=-5 addr=6c reg=00 len=1
[    3.579311] i2c i2c-3: cxd2841er_attach(): attaching CXD2854ER DVB-C/C2/T/T2/ISDB-T frontend
[    3.579313] i2c i2c-3: cxd2841er_attach(): chip ID 0xc1 OK.
[    3.590785] tda18212 3-0060: NXP TDA18212HN/M successfully identified
[    3.590800] ddbridge 0000:00:06.0: DVB: registering adapter 4 frontend 0 (Sony CXD2854ER DVB-T/T2/C and ISDB-T demodulator)...
[    3.590980] i2c i2c-3: cxd2841er_attach(): I2C adapter 000000002b4b965e SLVX addr 6f SLVT addr 6d
[    3.591798] i2c i2c-3: cxd2841er: i2c wr failed=-5 addr=6d reg=00 len=1
[    3.594324] i2c i2c-3: cxd2841er_attach(): attaching CXD2854ER DVB-C/C2/T/T2/ISDB-T frontend
[    3.594325] i2c i2c-3: cxd2841er_attach(): chip ID 0xc1 OK.
[    3.602562] tda18212 3-0063: NXP TDA18212HN/S successfully identified
[    3.602578] ddbridge 0000:00:06.0: DVB: registering adapter 5 frontend 0 (Sony CXD2854ER DVB-T/T2/C and ISDB-T demodulator)...
[    3.602764] i2c i2c-4: cxd2841er_attach(): I2C adapter 00000000d4ea463a SLVX addr 6e SLVT addr 6c
[    3.603575] i2c i2c-4: cxd2841er: i2c wr failed=-5 addr=6c reg=00 len=1
[    3.606247] i2c i2c-4: cxd2841er_attach(): attaching CXD2854ER DVB-C/C2/T/T2/ISDB-T frontend
[    3.606248] i2c i2c-4: cxd2841er_attach(): chip ID 0xc1 OK.
[    3.615386] tda18212 4-0060: NXP TDA18212HN/M successfully identified
[    3.615408] ddbridge 0000:00:06.0: DVB: registering adapter 6 frontend 0 (Sony CXD2854ER DVB-T/T2/C and ISDB-T demodulator)...
[    3.615594] i2c i2c-4: cxd2841er_attach(): I2C adapter 00000000d4ea463a SLVX addr 6f SLVT addr 6d
[    3.616598] i2c i2c-4: cxd2841er: i2c wr failed=-5 addr=6d reg=00 len=1
[    3.619074] i2c i2c-4: cxd2841er_attach(): attaching CXD2854ER DVB-C/C2/T/T2/ISDB-T frontend
[    3.619075] i2c i2c-4: cxd2841er_attach(): chip ID 0xc1 OK.
[    3.624321] cryptd: max_cpu_qlen set to 1000
[    3.639361] tda18212 4-0063: NXP TDA18212HN/S successfully identified
[    3.639379] ddbridge 0000:00:06.0: DVB: registering adapter 7 frontend 0 (Sony CXD2854ER DVB-T/T2/C and ISDB-T demodulator)...
[    3.639592] i2c i2c-5: cxd2841er_attach(): I2C adapter 0000000072ee92ce SLVX addr 6e SLVT addr 6c
[    3.641137] i2c i2c-5: cxd2841er: i2c wr failed=-5 addr=6c reg=00 len=1
[    3.642430] i2c i2c-5: cxd2841er_attach(): attaching CXD2854ER DVB-C/C2/T/T2/ISDB-T frontend
[    3.642431] i2c i2c-5: cxd2841er_attach(): chip ID 0xc1 OK.
[    3.656208] tda18212 5-0060: NXP TDA18212HN/M successfully identified
[    3.656231] ddbridge 0000:00:06.0: DVB: registering adapter 8 frontend 0 (Sony CXD2854ER DVB-T/T2/C and ISDB-T demodulator)...
[    3.656546] i2c i2c-5: cxd2841er_attach(): I2C adapter 0000000072ee92ce SLVX addr 6f SLVT addr 6d
[    3.657405] i2c i2c-5: cxd2841er: i2c wr failed=-5 addr=6d reg=00 len=1
[    3.660939] i2c i2c-5: cxd2841er_attach(): attaching CXD2854ER DVB-C/C2/T/T2/ISDB-T frontend
[    3.660940] i2c i2c-5: cxd2841er_attach(): chip ID 0xc1 OK.
[    3.670418] AVX2 version of gcm_enc/dec engaged.
[    3.670419] AES CTR mode by8 optimization enabled
[    3.674214] tda18212 5-0063: NXP TDA18212HN/S successfully identified
[    3.674230] ddbridge 0000:00:06.0: DVB: registering adapter 9 frontend 0 (Sony CXD2854ER DVB-T/T2/C and ISDB-T demodulator)...
[    9.038512] dvb_ca_en50221: dvb_ca adapter 0: DVB CAM detected and initialised successfully
[   25.422341] dvb_ca_en50221: dvb_ca adapter 0: DVB CAM detected and initialised successfully

Given I do not have debug logs enabled, minisatip does not show much:

Apr 29 13:04:36 minisatip systemd[1]: Started Multi-threaded SAT>IP server.
Apr 29 13:04:36 minisatip minisatip[712]: [29/04 13:04:36.694 main]: minisatip version 1.0.4-9f3f923, compiled in Jan 10 2021 12:39:24, with s2api version: 050B
Apr 29 13:04:37 minisatip kernel: [  464.312394] dvb_ca_en50221: dvb_ca adapter 0: DVB CAM detected and initialised successfully
Apr 29 13:04:46 minisatip minisatip[712]: [29/04 13:04:46.076 main]: Initializing with 10 devices
Please note that minisatip sees all 10 devices! Also the cams!

Robin Brouwer wrote:

> Given I do not have debug logs enabled, minisatip does not show much:
> [...]

> Please note that minisatip sees all 10 devices! Also the cams!

Is the redirect enabled ?

Somthing like "echo "10 02" > /sys/class/ddbridge/ddbridge0/Redirect

IMHO minsatip still needs the redirection.

tvh should in theory work with both representations but too often it does not.

5 days later

When compiling minisatip with ddci=1 in the make file, minisatip will do the redirection itself without ddbridge needing to do it!

Update: Minisatip version: v1.1.4-65f7685 Fixed emm processing for ddci. So on my setup this version of minisatip will descramble perfectly. You might want to look at the -c parameter. It allows setting the maximum amount of channels that will be descrambled using a single cam. It defaults to 2 now. If you know you can do more, it is wise to use that parameter to adjust that for each cam.
a month later
Robin Brouwer wrote:
> When compiling minisatip with ddci=1 in the make file, minisatip will do the redirection itself without ddbridge needing to do it!
>

> Update: Minisatip version: v1.1.4-65f7685 Fixed emm processing for ddci. So on my setup this version of minisatip will descramble perfectly. You might want to look at the -c parameter. It allows setting the maximum amount of channels that will be descrambled using a single cam. It defaults to 2 now. If you know you can do more, it is wise to use that parameter to adjust that for each cam.

Hello Robin, and also all in the topic,

very thanks for an update! I will try it as well.

Last time i tried to make minisat2ip work with the ddci=1 did not bring a success (((

I have Digital Devices OctopusCI S2 Pro Advanced - Twin CI and Twin DVB-S2 Tuner

The smartcard is a black Astra HD02 with the AlphaCrypt light r.2.2.
Checked this combination On windows, and it works well there...