CI+ protocol implementation in minisatip

Support forum for minisatip
Post Reply
retrofan

Re: CI+ protocol implementation in minisatip

Post by retrofan »

deleted
Last edited by retrofan on Tue Oct 15, 2019 5:17 pm, edited 2 times in total.
retrofan

Re: CI+ protocol implementation in minisatip

Post by retrofan »

balou1974 wrote: Mon Jun 10, 2019 2:09 pm 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.
@cata: is this problem solved?
cata
Site Admin
Posts: 768
Joined: Tue May 12, 2015 1:01 am

Re: CI+ protocol implementation in minisatip

Post by cata »

Yes, it should be
retrofan

Re: CI+ protocol implementation in minisatip

Post by retrofan »

OK, nice, thanks.
Last edited by retrofan on Tue Oct 15, 2019 5:17 pm, edited 6 times in total.
retrofan

Re: CI+ protocol implementation in minisatip

Post by retrofan »

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

Re: CI+ protocol implementation in minisatip

Post by solut »

Hi,

I have some problems getting DD Octopus Twin CI v4 to work with CI+ to work.
I'm using the actual master of minisatip and v0.9.33 ddbridge of kernel v5.3.8.

The CI+ init seems to be OK:

Code: Select all

[31/10 09:46:35.539 CA8]: auth ok!
...
[31/10 09:46:36.399 CA8]: 00:ca_ca_info_callback
[31/10 09:46:36.399 CA8]:   Supported CA ID: xxxx for CA8
[31/10 09:46:36.399 CA8]: CA 0 can handle CAID xxxx mask FFFF on adapter 8 at position 0
...
[31/10 09:46:36.442 AD0]: DDCI 8 CAID xxxx and mask FFFF matched PMT 7
...
[31/10 09:46:36.600 CA8]: 00:CAM successfully connected to resource 00400041, session_number 7
...
[31/10 09:46:36.651 AD8]: CAID xxxx and mask FFFF matched PMT 7
[31/10 09:46:36.651 AD8]: PMT CA 8 pid 98 () len 84 ver 1 sid 116 (74), pos 0, only
[31/10 09:46:36.651 AD8]: CW 0 for  PMT 7, master 7, pid 98, expiry in 3600000 ms, algo 3, parity 1: B7 FF EF 73 DD 13 0D 2B
[31/10 09:46:36.651 AD8]: Skip processing pmt for ddci adapter 8
[31/10 09:46:36.651 AD8]: found CW: 0 for  PMT 7, pid 98, master 7, 0 ms ago, parity 1: B7 FF EF 73 B3 13 0D 2B, IV: 06 A9 FF F3 22 FF B9 60
[31/10 09:46:36.652 AD8]: push_ts_to_ddci_buffer: 72192 bytes, left 0, ro 0, wo 72192
[31/10 09:46:36.700 CA8]: 00:ca_dt_enquiry_callback
[31/10 09:46:36.700 CA8]:   response_interval:0
[31/10 09:46:36.702 AD0]: writing 24628 bytes to DDCI device 8, fd 31, sock -1
[31/10 09:46:36.702 AD0]: ddci_process_ts ro 0, wo 72192 max 18800000
and then I get

Code: Select all

[31/10 09:46:36.702 AD0]: Could not push more data for adapter 0, rlen 72192, lbuf 72192, new pos -1
[31/10 09:46:36.702 AD0]: adapter 0 buffer full, DD 8, ro 67116, wo 72192
...
[31/10 09:46:37.171 AD8]: Parity change for  PMT 7, new active parity 0 pid 767 [47 02 FF 9E], last_parity_change 0
[31/10 09:46:37.171 AD8]: found CW: -1 for  PMT 7, pid 98, master 7, 0 ms ago, parity 0: not found
...
[31/10 09:46:45.565 AD0]: DDCI not ready yet
I realy don't know, what's going wrong, any hints appreciated.

Thanks, solut.
Last edited by solut on Tue Nov 05, 2019 4:01 pm, edited 1 time in total.
9000h
Posts: 89
Joined: Tue May 12, 2015 1:49 pm

Re: CI+ protocol implementation in minisatip

Post by 9000h »

Hi,
can first try to upgrade the drivers to 0.9.37 https://github.com/DigitalDevices/dddvb
CU
9000h
solut
Posts: 14
Joined: Wed Jan 03, 2018 4:49 pm

Re: CI+ protocol implementation in minisatip

Post by solut »

Hi, tried with actual dddvb master branch, same behaviour.
I don't see any direct errors in the log.
Do you know if it should work with Sky CI+ Cam?

Thanks, solut.
9000h
Posts: 89
Joined: Tue May 12, 2015 1:49 pm

Re: CI+ protocol implementation in minisatip

Post by 9000h »

Hi,
sorry I cannot do any similar tests here.
CU
9000h
Yuri
Posts: 68
Joined: Thu Oct 01, 2015 7:26 pm

Re: CI+ protocol implementation in minisatip

Post by Yuri »

Hi,
you have wrong start pharameters:
[31/10 09:46:09.272 main]: Forcing CA 0 to CI
[31/10 09:46:09.272 main]: Forcing CA 1 to CI
[31/10 09:46:09.272 main]: Setting CA 0 pin to xxxx
why you forcing CA1 and CA0?
you set pin to CA0 but your CAM in CA8

BR,
Yuri
Post Reply