OSCam 11764 - emu-r801
ALL Images mips - arm
Thanks: audi06_19
● Re-enable Base64 object in order to fix UTF8 characters on webif live log page
Unexpected error accessing webif vu+ ziro 4k
OSCam 11764 - emu-r801
ALL Images mips - arm
Thanks: audi06_19
● Re-enable Base64 object in order to fix UTF8 characters on webif live log page
Unexpected error accessing webif vu+ ziro 4k
Display MoreOSCam 11.760 - emu-r801
ALL Images mips - arm
- fix Building without Nagra not possible at Nagra_Merlin (thanks to Opti)..
UPDATE 06.04.2024:
- Oscam-emu
- libdvbcsa-ffdecsa
Thanks: audi06_19
Support: dreamosat-forum.com
unexpected error accessing webif: OSCam webif disabled!
guys do no use this smargo triple shit reader it's shitty and fucked whole my *** card just see latest logs which my ATR from
3F FD 13 25 02 50 80 0F 54 B0 04 69 FF 4A 50 D0 80 00 49 54 03
changed to
3F FD FF 25 02 50 80 0F 54 B0 04 69 FF 4A 50 D0 80 00 49 54 03
jsc_triple [mouse] ATR: 40 00
jsc_triple [mouse] ERROR: Could not read reader->convention
jsc_triple [mouse] Error activating card.
ATR is malformed, it reports 15 historical bytes but there are only 8
jsc_triple [mouse] ATR: 40 FF 00 5B BF F5 FE 0F D5 F2 DF 69 00 AD F5 F4 FE FF 6D D5 3F 03 40 00 5B BF F5 FE 0F D5 F2 DF
jsc_triple [mouse] ERROR: Could not read reader->convention
jsc_triple [mouse] Error activating card.
jsc_triple [mouse] ATR: 3F FD FF 25 02 50 80 0F 54 B0 04 69 FF 4A 50 D0 80 00 49 54 03
jsc_triple [mouse] Warning: F=0 is invalid, forcing FI=1
jsc_triple [mouse] Maximum frequency for this card is formally 5 Mhz, clocking it to 3.57 Mhz
jsc_triple [mouse] card system not supported
jsc_triple [mouse] Normal mode failed, reverting to Deprecated Mode
jsc_triple [mouse] ATR: 40 00
jsc_triple [mouse] ERROR: Could not read reader->convention
jsc_triple [mouse] Error activating card.
jsc_triple [mouse] ATR: 40 00
jsc_triple [mouse] ERROR: Could not read reader->convention
jsc_triple [mouse] Error activating card.
jsc_triple [mouse] ATR: 40 00
jsc_triple [mouse] ERROR: Could not read reader->convention
jsc_triple [mouse] Error activating card.
jsc_triple [mouse] card initializing error
Display More
Im somewhat limited to what I can view on my phone, but ill see if I can find anything when im on pc im sure your not the first person to get the error message, or indeed the last.
this is decoder error 02
I don't think so:( and I don't know what happens! strange error ! searched all over net and find no one telling at least whats the problem!
Now it's even more strange it says
*** verificare il corretto inserimento della smart card in original decoder!
trying now with the newer version 7373 the same result
I don't think the problem is version of oscam because I run it on 7253 before
Smargo version is latest 1.7 which is impossible to downgrade
Another thing is that I have no problem inserting my JSC card on it
Setting the mhz in oscam.server is pointless as the frequency needs to be set on the smargo itself with the smargo update utility, the mhz & cardmhz setting is for internal cardreaders only.
yes I have it and using smartreader_settings17.exe to change mhz with mhz of oscam
Any other tips?
I have strange problem after changing my reader mhz to get better ecm time but
Warning: F=0 is invalid, forcing FI=1 was the last result :(
Please help how can I sort out the problem
The error comes from icc_async.c and this section:
//make sure no zero values
double F = (double) atr_f_table[FI];
if (!F) {
FI = ATR_DEFAULT_FI;
cs_log("Warning: F=0 is invalid, forcing FI=%d", FI);
}
if (!d) {
d = ATR_DEFAULT_D;
cs_log("Warning: D=0 is invalid, forcing D=%.0f",d);
}
if (deprecated == 0)
return InitCard (reader, atr, FI, d, n, deprecated);
else
return InitCard (reader, atr, ATR_DEFAULT_FI, ATR_DEFAULT_D, n, deprecated);
}
cs_log("Warning: F=0 is invalid, forcing FI=%d", FI);
Display More
OSCAM 1.20-unstable_svn build #7253
Tested many mhz with both mouse and smartreader protocols with the exact same result!
it works without any problem before changing the frequency on this version before!
Any suggestion?
Full log:
[smartreader] Reader initialized (device=002:003_***IT, detect=cd, mhz=357, cardmhz=357)
[smartreader] card detected
[smartreader] ATR: 3F FD FF 25 02 50 80 0F 54 B0 04 69 FF 4A 50 D0 80 00 49 54 03
[smartreader] Warning: F=0 is invalid, forcing FI=1
[smartreader] Maximum frequency for this card is formally 5 Mhz, clocking it to 4.80 Mhz
[smartreader] card system not supported
[smartreader] Normal mode failed, reverting to Deprecated Mode
[smartreader] ATR: 3F FD FF 25 02 50 80 0F 54 B0 04 69 FF 4A 50 D0 80 00 49 54 03
[smartreader] Warning: F=0 is invalid, forcing FI=1
[smartreader] Maximum frequency for this card is formally 5 Mhz, clocking it to 4.80 Mhz
[smartreader] card system not supported
[smartreader] card initializing error
Display More
oscam.server:
[reader]
label = ***it
description = ***_Smargo_USB
protocol = smartreader
device = 002:003_***IT
services = cinema pack,sports pack,children pack,documentary pack,news pack,lifestyle pack
smargopatch = 1
cacheex = 2
caid = 09CD
boxid = xxxxxxxx
ecmwhitelist = B7,51
detect = cd
mhz = 358
cardmhz = 357
ident = 09CD:000000
group = 1
emmcache = 1,3,2
blockemm-unknown = 1
blockemm-u = 1
blockemm-s = 1
blockemm-g = 1
blockemm-bylen = 183,81
blocknano = all
audisabled = 1
Display More
please post such a useful info for CSP too
please edit first post link to
http://www.streamboard.tv/svn/oscam/trunk/
else the update wouldn't works!
just wanna make a note that the ECM length is 3C for my JSC card! and yes the ECM whitelist in oscam page is incorrect
but anyone can check the length in oscam status page easily :)
I'm thinking about the concept of block-caid-mismatch and as you may know
ca-profiles/block-caid-mismatch
true/false (default: true) Block all replies where the request had a different ca-id. Determines whether M flag transactions are blocked or not (i.e returned as failures to the clients). Since the cache is global, it is possible for a client to send requests to the wrong port and still get valid replies (which may cause it to ignore the caid in the card-data and keep sending to the wrong port - potentially destroying the service mapping for that profile).
NOTE: As of 0.9.1, this will also apply to cross-profile cache hits that have the same ca-id (but where ecms were sent to different profiles). Such configurations with several profiles receiving the same traffic aren't really supported, but if you you know what you're doing and you're sure you understand the implications - it will continue to work as before if you set this to false.
1) As above said it is possible for a client to send requests to the wrong port and still get valid replies how a client gets valid cw reply when he send a wrong caid in a wrong port and that reader only sorted to receive and process only one specific caid in oscam!
2) what is cross-profile? how it works?
You have provided no configs so you can't actually expect an answer to that question can you ?
Check your logs
I think in crashes logs helps more than configs!
same caid network id should be insrerted in one single profile and no need create more than one profile
just active it (turn this plugin to enabled) in xml file
and how do you explain the block of some cards with emm locked and inserted in the original decoder for upgrades only ?
I mean blocked emm a,u,g nano ... dude
kabise
Yes but I won't share when I'm not sure its costly for me I prefer use it in original btw, I heared some one sell NDS blocker or PIC NDS Hardware blocker don't know if it works fine or not and whats that at all!
Also the usual situation before card to be killed is that oscam shows many emm blocked in on day and after some days card deactive itself
I'm thinking when we upgrade or married a card with a box except box id all other info also be important and monitored randomly by chip like STBID Driver sw ver,vrifier ver these info exist in diagnostic section of pace receiver
I have 09cd for 3 month till now searching to find a solution to avoid 9994 or 9995 errors and still afraid of using it in oscam however I can upgrade in original box but I read many complains, cards killed in 3 mins,2days,1week or 1 month and I really don't know a safe way.
is it by chance?
What I know is a user with sCam 1.49 used it with no share and the card killed and a user with full of shares use this card with the same emm blocked, manual upgrade, ecmwhitelist... with no problem.
This have a high risk specially for prepaid cards like mine which cannot replaced with another one like post paid (pay per month) card
no matter oscam cccam or other cs protocols or any type of readers, they can easily kill card if the card not used on original box.
one guy in oscam forum said when he is not blocking emms the card reject group for decoding and after blocking emms in config card starts decoding!
in original pace *** decoder when we insert cart all channels listed separately in one direction (hotbird) , does it means the card allowed to decode channels only on this satellite and if card detects some other chid on other satellites flag the card for suspect?
Any suggestion?
Please do no reply there is no way noone knows just tell me what do you think what kind of protection may exist.
If it's ECM how we block it what kind of ECM in length and content?
Find the answer
It's in Admin section not status web!
Very intresting plugin to check freezes If you add 900 your new ECM time is now old ECM+900 and add it till get freeze on your caid!
PS remember to set <max-cw-wait>x</max-cw-wait> in profile
x should be 1 second more than your current test-delay
for ex if test-delay is 3000 ms set max-cw-wait to 4
Hi guys
I have read about this plugin to get max_cw_wait but today after enabling it there is no way to set a delay (set-test-delay) like they said in their optimization read me:
To help figure out the exact cutoff point for clients (the maximum time they can wait before they experience a freeze),
use the LoggingPlugin and the [COLOR='#FF0000']set-test-delay ctrl command (via the status web)[/COLOR]. This allows you to experiment by adding
a gradually increasing delay for a specific test-client (use the ip filter)...
What is set-test-delay ctrl command? how to set it?! there is no such thing in status web section only:
Plugin: LoggingPlugin
Logs all ecm traffic between client sessions and proxy to file.
delay: 0
loggers: 1
ip-filter: *
Thanks for your help