CI+ protocol implementation in minisatip
Re: CI+ protocol implementation in minisatip
What is the output of DMESG after you insert the CAM?
Re: CI+ protocol implementation in minisatip
97917.370509] usb 1-1.1.3: new high-speed USB device number 6 using dwc_otg
[97917.501208] usb 1-1.1.3: New USB device found, idVendor=0b48, idProduct=3015, bcdDevice= 0.00
[97917.501224] usb 1-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[97917.501234] usb 1-1.1.3: Product: TechnoTrend USB2.0
[97917.501243] usb 1-1.1.3: Manufacturer: CityCom GmbH
[97917.501252] usb 1-1.1.3: SerialNumber: 20151107
[97917.810521] usb 1-1.1.3: dvb_usb_v2: found a 'TechnoTrend TT-connect CT2-4650 CI v1.1' in warm state
[97917.810951] usb 1-1.1.3: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxe
r
[97917.810995] dvbdev: DVB: registering new adapter (TechnoTrend TT-connect CT2-4650 CI v1.1)
[97917.812250] usb 1-1.1.3: dvb_usb_v2: MAC address: bc:ea:2b:65:07:bb
[97917.838802] i2c i2c-3: Added multiplexed i2c bus 4
[97917.838821] si2168 3-0064: Silicon Labs Si2168-B40 successfully identified
[97917.838832] si2168 3-0064: firmware version: B 4.0.2
[97917.850553] si2157 4-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached
[97917.865688] sp2 3-0040: CIMaX SP2 successfully attached
[97917.865831] usb 1-1.1.3: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
[97917.866121] Registered IR keymap rc-tt-1500
[97917.866257] rc rc0: TechnoTrend TT-connect CT2-4650 CI v1.1 as /devices/platform/soc/3f980000.usb/usb1/1-
1/1-1.1/1-1.1.3/rc/rc0
[97917.866498] input: TechnoTrend TT-connect CT2-4650 CI v1.1 as /devices/platform/soc/3f980000.usb/usb1/1-1
/1-1.1/1-1.1.3/rc/rc0/input1
[97917.866843] rc rc0: lirc_dev: driver dvb_usb_dvbsky registered at minor = 0, scancode receiver, no transm
itter
[97917.866856] usb 1-1.1.3: dvb_usb_v2: schedule remote query interval to 300 msecs
[97917.866874] usb 1-1.1.3: dvb_usb_v2: 'TechnoTrend TT-connect CT2-4650 CI v1.1' successfully initialized a
nd connected
[97917.867032] usbcore: registered new interface driver dvb_usb_dvbsky
[97919.070572] Under-voltage detected! (0x00050005)
[97925.310618] Voltage normalised (0x00000000)
[97934.080611] dvb_ca_en50221: dvb_ca adapter 0: DVB CAM did not respond
[97917.501208] usb 1-1.1.3: New USB device found, idVendor=0b48, idProduct=3015, bcdDevice= 0.00
[97917.501224] usb 1-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[97917.501234] usb 1-1.1.3: Product: TechnoTrend USB2.0
[97917.501243] usb 1-1.1.3: Manufacturer: CityCom GmbH
[97917.501252] usb 1-1.1.3: SerialNumber: 20151107
[97917.810521] usb 1-1.1.3: dvb_usb_v2: found a 'TechnoTrend TT-connect CT2-4650 CI v1.1' in warm state
[97917.810951] usb 1-1.1.3: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxe
r
[97917.810995] dvbdev: DVB: registering new adapter (TechnoTrend TT-connect CT2-4650 CI v1.1)
[97917.812250] usb 1-1.1.3: dvb_usb_v2: MAC address: bc:ea:2b:65:07:bb
[97917.838802] i2c i2c-3: Added multiplexed i2c bus 4
[97917.838821] si2168 3-0064: Silicon Labs Si2168-B40 successfully identified
[97917.838832] si2168 3-0064: firmware version: B 4.0.2
[97917.850553] si2157 4-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached
[97917.865688] sp2 3-0040: CIMaX SP2 successfully attached
[97917.865831] usb 1-1.1.3: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
[97917.866121] Registered IR keymap rc-tt-1500
[97917.866257] rc rc0: TechnoTrend TT-connect CT2-4650 CI v1.1 as /devices/platform/soc/3f980000.usb/usb1/1-
1/1-1.1/1-1.1.3/rc/rc0
[97917.866498] input: TechnoTrend TT-connect CT2-4650 CI v1.1 as /devices/platform/soc/3f980000.usb/usb1/1-1
/1-1.1/1-1.1.3/rc/rc0/input1
[97917.866843] rc rc0: lirc_dev: driver dvb_usb_dvbsky registered at minor = 0, scancode receiver, no transm
itter
[97917.866856] usb 1-1.1.3: dvb_usb_v2: schedule remote query interval to 300 msecs
[97917.866874] usb 1-1.1.3: dvb_usb_v2: 'TechnoTrend TT-connect CT2-4650 CI v1.1' successfully initialized a
nd connected
[97917.867032] usbcore: registered new interface driver dvb_usb_dvbsky
[97919.070572] Under-voltage detected! (0x00050005)
[97925.310618] Voltage normalised (0x00000000)
[97934.080611] dvb_ca_en50221: dvb_ca adapter 0: DVB CAM did not respond
Re: CI+ protocol implementation in minisatip
hmm like 9000h said; issues with the combinations of the dvbsky driver and your cam. I would advise you to try a TBS tuner or equivalent..
Re: CI+ protocol implementation in minisatip
how about tbs-5580? will it work?
Re: CI+ protocol implementation in minisatip
As long as the driver works there should be no issue
Re: CI+ protocol implementation in minisatip
Thanks to sardonis, I now have a new cabletuner (tbs 5881) and it seems to work - even with ci+ (unitymedia).
But there is one big problem, the CI+ needs the tuner to be tuned to an encrypted channel to start authentication on start of minisatip.
If it starts without being tuned to an encrypted channel it will stop after about 30% with error 17 and thats it ...
You will have to reboot and start dvb-viewer on an encrypted channel while minisatip is starting ...
It would be nice to have an automated new init of CI+ when init is stalled ...
Maybe someone has an idea what to do ...
But there is one big problem, the CI+ needs the tuner to be tuned to an encrypted channel to start authentication on start of minisatip.
If it starts without being tuned to an encrypted channel it will stop after about 30% with error 17 and thats it ...
You will have to reboot and start dvb-viewer on an encrypted channel while minisatip is starting ...
It would be nice to have an automated new init of CI+ when init is stalled ...
Maybe someone has an idea what to do ...
Re: CI+ protocol implementation in minisatip
Forget about my last post!!! CI plus just takes a little time for init - and than just works ...
Thanks a lot, good work!!!
Thanks a lot, good work!!!
Re: CI+ protocol implementation in minisatip
Hello together!
Latest commit breaks CI+ decoding (DVB Viewer Pro does no longer work with encrypted channels)
commit 266feb1d7e7ad2bc1d6f554a38cc66f874eef4dc
Author: root <root@localhost.localdomain>
Date: Mon Jun 10 16:02:50 2019 +0200
Revert "Prevent checking if the pmt is decrypted"
This reverts commit 03169ab9599be435a9c4bae690a8bda472308aa1.
Latest commit breaks CI+ decoding (DVB Viewer Pro does no longer work with encrypted channels)
commit 266feb1d7e7ad2bc1d6f554a38cc66f874eef4dc
Author: root <root@localhost.localdomain>
Date: Mon Jun 10 16:02:50 2019 +0200
Revert "Prevent checking if the pmt is decrypted"
This reverts commit 03169ab9599be435a9c4bae690a8bda472308aa1.
Re: CI+ protocol implementation in minisatip
Can you upload a log before and after? ./minisatip -f -l http
Thank you
Thank you
Re: CI+ protocol implementation in minisatip
Hello cata!
I cloned the whole source again and copied ca.c for ciplus in place. Decoding works again but something is still wrong, sometimes decoding works only directly after rebooting the machine (qnap ts251pl with debian). Actually I am at the holidays and I am not able to test and log the problem ...
I cloned the whole source again and copied ca.c for ciplus in place. Decoding works again but something is still wrong, sometimes decoding works only directly after rebooting the machine (qnap ts251pl with debian). Actually I am at the holidays and I am not able to test and log the problem ...