Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#3112 closed defect (fixed)

Unable to configure ins7e with 26*00

Reported by: system2_it Owned by:
Priority: major Component: Reader
Severity: medium Keywords:
Cc: Sensitive: no



OSCAM 1.20-unstable_svn build r8222

Issue Description

From r8222 is not possible to insert ins7e with 26*00, although this does not seem to make sense, but the original box processes that ins7e with 26*00 responding 91 00.
It is possible to change function check_filled so you can enter 26*00?

When the issue occurs

for the system nds, inserting the ins7e = 26*00 is not considered

Change History (6)

comment:1 by gf, 10 years ago

How does you reader config look like?

comment:2 by system2_it, 10 years ago

First, a clarification on the description ticket, the answer to ins7e set with 26*00 is 90 21 and not 91 00.
sorry I did not understand the request, you mean this?
the reader.conf is set:
ins7e = 0000000000000000000000000000000000000000000000000000
and based on your check_filled is not considered
thanks for your attention

comment:3 by gf, 10 years ago

Are you sure ins7e is valid when it contains only 00. If it is valid, then I'll have to revert r8222. Can anyone clue me on ins7E and ins7E11 settings?

comment:4 by system2_it, 10 years ago

Yes is valid, the original box NDS Videoguard2 sends the ins7e with 26*00 and is processed, if you can return before the change r8222, at least for one ins7e.

comment:5 by gf, 10 years ago

Resolution: fixed
Status: newclosed

Fix was commited in r8244. Thank you for your patience.

comment:6 by system2_it, 10 years ago

Thank you for the great work ;)

Note: See TracTickets for help on using tickets.