Opened 9 years ago

Closed 8 years ago

#3200 closed defect (fixed)

[gbox] 0D05/95 crytoworks ecm failed

Reported by: felixka Owned by: devs
Priority: minor Component: General
Severity: low Keywords: gbox ecm cw
Cc: Sensitive: no

Description

Revision

all rev with gbox support

Description

oscam-gbox (client) no cryptoworks ecm from gbox.net & gbox2.25 (server).

ORF 0D05 & 0D95 failed
Sky 1702 works fine

Cryptoworks fail might be caused by missing or incorrect prov mapping? prov = 000004 -> 0400 in gbox world.
There is some code in gbox.c to take care about that, but might not work.

Code

switch (ercaid >> 8) {

cryptoworks

case 0x0d:
erprid = erprid << 8;
break; }

Attachment:

2 logs -d255
1.) 1702 ecm ok
2.) 0D05 ecm nok

Attachments (2)

0D05_oscam.log (88.3 KB ) - added by felixka 9 years ago.
1702_oscam.log (140.5 KB ) - added by felixka 9 years ago.

Download all attachments as: .zip

Change History (4)

by felixka, 9 years ago

Attachment: 0D05_oscam.log added

by felixka, 9 years ago

Attachment: 1702_oscam.log added

comment:1 by felixka, 9 years ago

From the attached logs, you can see that no ecm is send out at all in case of Cryptoworks.
I tried to find out why, but it is to difficult for me with basic c skills.

In function: gbox_send_ecm()

There is a switch to change Provider in case of cryptoworks caid 0Dxx.

switch (ercaid >> 8) {

cryptoworks
case 0x0d:

erprid = erprid << 8;
break;

}

so erprid is changed from 000004 to 000400 which is correct.

1st issue:
so far so good, but I dont see in the code, where 'erprid' is assembled into the ecm.

2nd issue:
code:
if (!cont_card_1)

return 0;


(!cont_card_1) is false in case of cryptoworks, so sending of ecm is blocked

Maybe someone can help.

comment:2 by felixka, 8 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.