CI+ protocol implementation in minisatip

Support forum for minisatip
solut
Posts: 14
Joined: Wed Jan 03, 2018 4:49 pm

Re: CI+ protocol implementation in minisatip

Post by solut »

Hi Yuri,

I'm using two SatIP server with 4 tuners each, so I followed the minisatip documentation:
-e --enable-adapters list_of_enabled adapters: enable only specified adapters
eg: -e 0-2,5,7 (no spaces between parameters)
keep in mind that the first adapters are the local ones starting with 0 after that are the satip adapters if you have 3 local dvb cards 0-2 will be the local adapters, 3,4, ... will be the satip servers specified with argument -s
But I saw on the logs that u are right, the CIs are set after the SatIP devices...

SoI tried 8 and 9, switching the input of my CI adapter, but I didn't had any success.
Exactly the same bevaviour - the CAM get's initialized (CI+ is OK), but I get one time
found CW: 0
and then only
found CW: -1
What else can I try ?

Thanks, solut.
solut
Posts: 14
Joined: Wed Jan 03, 2018 4:49 pm

Re: CI+ protocol implementation in minisatip

Post by solut »

It's working!
I deleted the bin files + bootid (?) and start minisatip with --ca-pin 8:xxxx (no ca assignment).

Thanks, solut.
sardonis
Posts: 20
Joined: Sat Jun 17, 2017 7:10 pm

Re: CI+ protocol implementation in minisatip

Post by sardonis »

I have problems on raspberry pi 4 with raspbian buster. I'm running a TechnoTrend TT-connect CT2-4650 CI USB tuner with default kernel media drivers. FTA channels are not a problem but encrypted channels don't work. Same tuner with same CI+ module is working on rpi3 with raspbian stretch without issues.

[12/02 09:12:32.354 AD0]: found CW: -1 for VIER HD PMT 4, pid 212, master 4, 0 ms ago, parity 1: not found
[12/02 09:12:32.406 AD0]: PID Continuity error (adapter 0): pid: 4201, Expected CC: A, Actual CC: 1, CC Before 9

On other occasions, I see a lot of error 524 in the logs. I'm suspecting a driver issue but I'm not sure. FTA picture is playing perfecly without any blocks or hickups.

[12/02 09:25:47.179 signal]: ad 0 ioctl fd 11 FE_READ_SIGNAL_STRENGTH failed, error 524 (Unknown error 524)
[12/02 09:25:47.179 signal]: ad 0 ioctl fd 11 FE_READ_SNR failed, error 524 (Unknown error 524)
[12/02 09:25:47.483 signal]: ad 0 ioctl fd 11, FE_READ_BER failed, error 524 (Unknown error 524)

Please find logs attached.
minisatip-logs.zip
(57.79 KiB) Downloaded 1066 times
sardonis
Posts: 20
Joined: Sat Jun 17, 2017 7:10 pm

Re: CI+ protocol implementation in minisatip

Post by sardonis »

I opened an issue on Github with more logs.

https://github.com/catalinii/minisatip/issues/713
sardonis
Posts: 20
Joined: Sat Jun 17, 2017 7:10 pm

Re: CI+ protocol implementation in minisatip

Post by sardonis »

I'm using a system with mixed tuners dvb-c and dvb-s. For the decryption of dvb-c channels, I'm using a CI+ module. For decryption of dvb-s channels, I use a dvbapi connection to local oscam server running a seca card.
For some reason minisatip still tries to send ecm's with default ecmpid 0 to the dvbapi connection when I tune to an encrypted dvb-c channel.

2020/03/17 19:20:01 071B0C98 c (ecm) dvbapi (****@00****/0000/03ED/4F:00000000000000000000000000000000): rejected caid (0 ms) (invalid caid 0x****)
2020/03/17 19:20:04 071B0C98 c (dvbapi) Demuxer 0 stopped descrambling for program 03ED (****@00****:03ED unknown)
2020/03/17 19:20:04 071B0C98 c (dvbapi) Demuxer 0 ecmpid 0 CAID: **** ECM_PID: 07D5 PROVID: 000000
2020/03/17 19:20:04 071B0C98 c (dvbapi) Demuxer 0 ecmpid 1 CAID: **** ECM_PID: 0839 PROVID: 000000

Is this normal behaviour? It's kind of useless so I was thinking it might come in handy to have a parameter for minisatip that can ignore certain CAID's or ecmpid's for certain adapter numbers/types.
Last edited by sardonis on Thu Apr 08, 2021 8:38 pm, edited 1 time in total.
cata
Site Admin
Posts: 768
Joined: Tue May 12, 2015 1:01 am

Re: CI+ protocol implementation in minisatip

Post by cata »

pid 0 should not be the ECMpid as it is a PAT pid.

Can you upload the logs and highlight the time it happens?

Thanks
sardonis
Posts: 20
Joined: Sat Jun 17, 2017 7:10 pm

Re: CI+ protocol implementation in minisatip

Post by sardonis »

cata wrote: Sun Apr 05, 2020 10:41 pm pid 0 should not be the ECMpid as it is a PAT pid.

Can you upload the logs and highlight the time it happens?

Thanks
I have added some logs with parameters http,pmt,dvbapi

Corresponding oscam logs:

2020/05/06 23:33:06 61FB11B3 c (dvbapi) Demuxer 0 ecmpid 0 CAID: **** ECM_PID: 07D5 PROVID: 000000
2020/05/06 23:33:06 61FB11B3 c (dvbapi) Demuxer 0 ecmpid 1 CAID: **** ECM_PID: 0839 PROVID: 000000
2020/05/06 23:33:06 61FB11B3 c (dvbapi) Demuxer 0 ecmpid 2 CAID: **** ECM_PID: 089D PROVID: 000000
2020/05/06 23:33:06 61FB11B3 c (dvbapi) Demuxer 0 ecmpid 3 CAID: **** ECM_PID: 0901 PROVID: 0********
2020/05/06 23:33:06 61FB11B3 c (dvbapi) Demuxer 0 ecmpid 4 CAID: **** ECM_PID: 0965 PROVID: 000000
2020/05/06 23:33:06 61FB11B3 c (dvbapi) Demuxer 0 found 5 ECM pids and 11 STREAM pids in CA PMT
2020/05/06 23:33:06 61FB11B3 c (dvbapi) Demuxer 0 trying to descramble PID 0 CAID **** PROVID 000000 ECMPID 07D5 ANY CHID PMTPID 00CD VPID 0DAD
2020/05/06 23:33:06 61FB11B3 c (ecm) dvbapi (****@00****/0000/03ED/4F:7675D3DAF5453A923D398C63C6C93F6F): rejected group (3 ms) (no matching reader)
2020/05/06 23:33:07 61FB11B3 c (ecm) dvbapi (****@00****/0000/03ED/4F:7675D3DAF5453A923D398C63C6C93F6F): rejected group (4 ms) (no matching reader)
2020/05/06 23:33:10 61FB11B3 c (dvbapi) Demuxer 0 stopped descrambling for program 03ED (****@00****:03ED unknown)
2020/05/06 23:33:11 61FB11B3 c (dvbapi) Demuxer 0 ecmpid 0 CAID: **** ECM_PID: 07D5 PROVID: 000000
2020/05/06 23:33:11 61FB11B3 c (dvbapi) Demuxer 0 ecmpid 1 CAID: **** ECM_PID: 0839 PROVID: 000000
2020/05/06 23:33:11 61FB11B3 c (dvbapi) Demuxer 0 ecmpid 2 CAID: **** ECM_PID: 089D PROVID: 000000
2020/05/06 23:33:11 61FB11B3 c (dvbapi) Demuxer 0 ecmpid 3 CAID: **** ECM_PID: 0901 PROVID: 0******
2020/05/06 23:33:11 61FB11B3 c (dvbapi) Demuxer 0 ecmpid 4 CAID: **** ECM_PID: 0965 PROVID: 000000
2020/05/06 23:33:11 61FB11B3 c (dvbapi) Demuxer 0 found 5 ECM pids and 11 STREAM pids in CA PMT
2020/05/06 23:33:11 61FB11B3 c (dvbapi) Demuxer 0 trying to descramble PID 0 CAID 1801 PROVID 000000 ECMPID 07D5 ANY CHID PMTPID 00CD VPID 0DAD
minisatip.zip
(20.13 KiB) Downloaded 945 times
Last edited by sardonis on Thu Apr 08, 2021 8:37 pm, edited 1 time in total.
Validate
Posts: 7
Joined: Tue Mar 30, 2021 11:27 am

Re: CI+ protocol implementation in minisatip

Post by Validate »

Does it work with ECP Cams? I've got Black Tivusat, it descrambles only regular HD channels, none of 4K work. DEC-ERRORS: 12724
cata
Site Admin
Posts: 768
Joined: Tue May 12, 2015 1:01 am

Re: CI+ protocol implementation in minisatip

Post by cata »

Feel free to upload logs

./minisatip -f -l http
Validate
Posts: 7
Joined: Tue Mar 30, 2021 11:27 am

Re: CI+ protocol implementation in minisatip

Post by Validate »

cata wrote: Wed Apr 07, 2021 7:09 am Feel free to upload logs
./minisatip -f -l http
I have confirmed, it does work fine. Tested on tivusat uhd black. It was a mater of correct startup flags. Thanks.
Post Reply