51 replies to this topic

[littlesat]

I see... here it is giving a SysID instead of provider ID...

i hope there are no other 'dialects'

Edited by littlesat, 7 August 2012 - 14:29.

[alsat1]

So can we expect a fix?Best regards.

[littlesat]

FYI: http://openpli.git.s...5809ebac63632f1

Crasy that gbox is making this different for Nagravision????????

Edited by littlesat, 7 August 2012 - 15:02.

[alsat1]

Its almost ok,now showing also info from my card(slot with time ecm and caid also ok),but not decoding any channels in nagravision from peers,but Iam sure it should decode without problem,I have friends with full n3 polsat card and they are conected.
No ecm.info in tmp when try to decode polsat channel from peer.

Mayby one more fix is needed....

Thanks a lot for continuing job.Best regards.

[Taykun345]

@littlesat

your inbox is full apperantly...

[littlesat]

Then post a ecm.info that helped me to debug.... But I suggest not decoding (no ecm.info) is not related to the encoder at all....

P.S. try PM again....

Edited by littlesat, 7 August 2012 - 15:25.

[alsat1]

How to make GetEcmInfo.py make visible on pli 2.1?couse I want copy this orginal file(from my another dreambox) to pc and then copy to dreambox in my living room(for test),or that file with fix nagravision to dm in bedroom and check there couse there I have polsat sport hd from peer,but I have there old GetEcmInfo.py

regards.

[littlesat]

Doesn't care.... it is for 3.0 and 2.1.... everything is on the same location.

[alsat1]

Then post a ecm.info that helped me to debug.... But I suggest not decoding (no ecm.info) is not related to the encoder at all....

P.S. try PM again....

You have right just checked now on my dm800hd on pli 2.1 with your new GetEcmInfo.py and there is ok,its decoding nagravision card from my dm800hd and showing all caids etc ok.

Doesn't care.... it is for 3.0 and 2.1.... everything is on the same location.

Yes,I just forgot to make opkg update.

But there now problem on my dm800hd with conax card.All ecms,caids ok from peers,also from my dm800se with nagravision card,but when decoding from slot this conax card is not showing anything.,just the same problem like was on dm800se in post nr 18 in this thread.

Here ecm info:

==== Conax ECM on CaID 0x0B00, pid 0x0903 =====
CW0: 60 35 AE 43 11 45 B9 0F
CW1: 05 0B 6B 7B B9 AE CD 34
decode:slot-1
response:237

I think it need to be fixed in all caid for internal decoding(own cards).

Keep going with fix,You nearly done it.

Best regards.

Edited by alsat1, 7 August 2012 - 20:39.

[littlesat]

Just another dialect.....
FYI: http://openpli.git.s...8add597b852150a

Edited by littlesat, 7 August 2012 - 23:07.

[Erik Slagter]

I did not realise enigma gets its encryption information from these files.

The output of the oscam ecm file(s) is also not completely the same as that from cccam, so some readings are incorrect (as well), decryption info always shows only one service, even though more are being decrypted, because oscam only creates 1 file. I guess that's something that should be corrected in oscam....

Edited by Erik Slagter, 8 August 2012 - 16:54.

[littlesat]

CCcam creates more ecm.info files.... where ecm.info is the first. So when the tuner is receiving and recording another channel you see there the first service tuned...
For Oscam it is alternating (the last time I checked)...

[Erik Slagter]

Yes that is correct. And yes I think that is an error of oscam, it should create ecm files for every service it decrypts, like cccam does.

[alsat1]

Just another dialect.....
FYI: http://openpli.git.s...8add597b852150a

Tested,and ok now.Very thank you.
Is that new GetEcmInfo.py will be from now on daily new images as standard or I should save it on my pc and then copy to receiver.

Best regards and thanks again.

[blzr]

The output of the oscam ecm file(s) is also not completely the same as that from cccam...

speaking of oscam/cccam differences - little OT:
see attached screenshots (1-st oscam, 2-nd cccam) - such a little curiosity (same card, same service)/???/
//and I guess it's because of this 'nagra tunneled through seca' card, but which highlighting is 'true'? or both are?

Attached Files

•  oscam.jpg   30.73KB   123 downloads
•  cccam.jpg   29.8KB   120 downloads

[littlesat]

WHen you prefer the nagra vision ECM to the card en block the Seca ECM then this is right...

[blzr]

hmm, so it seems that cccam prefers seca and oscam prefers nagra /?/...
and even if I set in oscam.dvbapi P: 0100:000068 I: 1813:000068, oscam still chooses nagra
//but of course it's the question for another topic (and in fact it's no big deal for me at all, I am just curious )
so, end of OT

[littlesat]

When Oscam prefers Nagra that is set into a setting.... In the past this was a trick to get around the Seca2/3 ECM selection... So it is simply a setting...

[Erik Slagter]

blzr, it is very probably that Cyfra+ (I assume that's we're talking about) uses exactly the same (broken) system to use both seca2 and nagra3 through the same caid as CDS does over here in NL.

If both seca2 and nagra3 would be offered through separate caid's, there would be no problem at all, with both cccam and oscam. Both caid's would be tried and the one working would be used (if not overriden by configuration).

The problem is that both seca2 and nagra3 are sent over the same (seca) caid (+ ident!). The only thing that differs, is the ecm pid. That means ecm's for nagra3 may show up when seca2 ecm's are expected. At least oscam used to decide then it could not decode this caid and blacklisted the caid, both ecm pids.

There are two workarounds (for oscam, cccam works with CDS/TVV out of the box, I don't know about Cyfra+). The first is to blacklist, per channel the ecm pid that you don't want, e.g. the seca2 pid if you're using a nagra3 card and v.v. This is a bothersome process, because you can't (easily) see which one is which...

The other workaround is to make the cam peek into the ecm's and have it decide by itself what ecm pid to use. Oscam currently does this on CDS/TVV, I am not sure for Cyfra+, probably not.

[blzr]

here in CYFRA+ there's slightly different situation (though our current cards are identical /?/ as these of CDS) - S2 cards are long forgotten...
I am not sure, but seca ecm is required for ancient philipses/pioneers etc. that were distributed by operator and are still in use; (our cards are called 'cameleon' because of this 'nagra tunneled through seca' ability...)
because of that, there's no ecm for seca2 cards per se,/?/ and the card could answer with no problem on both 0100 and 1813 ecm, and oscam just like cccam works for me ootb (but prefers nagra over seca, and cccam quite opposite/?/)... so in fact there's no real problem, except my curiosity
//and there is quite a big chance I just confused everything above, I am not an expert in this regard by any means...

Edited by blzr, 9 August 2012 - 15:46.