Help to adjust oscam, two cards conax OB00 ident000000 different operators, there is a conflict how to adjust a clean sheet and to learn ECM oscam
Version: oscam-1.20_svn-r11635
Compiler: i686-linux-gnu-libusb-pcsc
Thanks.
The help oscam 0B00
- ahssv
- Thread is marked as Resolved.
-
Hi.
Please specify your question in more detail. What exactly do you want to achieve and where exactly is the problem? You have two identical 0B00 CAIDs (Conax encoding) but a different operator. If the operator is different, then this ident should be different and not 000000 for both, or am I wrong?
Use the basic configuration. Oscam can do everything himself. It tries to search for channel (PID) availability first on the first reader and then immediately on the second reader. If it finds and the ECM request is successful, it will be used this one card-reader for this one channel (PID).
-
Hi.
Please specify your question in more detail. What exactly do you want to achieve and where exactly is the problem? You have two identical 0B00 CAIDs (Conax encoding) but a different operator. If the operator is different, then this ident should be different and not 000000 for both, or am I wrong?
Use the basic configuration. Oscam can do everything himself. It tries to search for channel (PID) availability first on the first reader and then immediately on the second reader. If it finds and the ECM request is successful, it will be used this one card-reader for this one channel (PID).
Prompt how correctly to write down options in Oscam, there are two cards Conax different operators caid 0B00 and ident 000000 identical at cards and there is a conflict one card constantly works on other card writes the coded channel? Thanks.
-
Yes the Nordic provider use the same caid:ident.
But s3n0 is correct this is no problem at all.
But if you where to use 2 CommonInterfaces you would have bigger problem ;)
Solution ther is CommonInterface assignment. Where you add correct channels to the correct CommonInterface
This settings works just fine
[reader]
label = Sweden
protocol = internal
device = /dev/sci0
detect = cd
mhz = 450
cardmhz = 2700
group = 2
emmcache = 1,3,10,0
blockemm-unknown = 1
blockemm-g = 1
[reader]
label = Norway
protocol = internal
device = /dev/sci1
detect = cd
mhz = 450
cardmhz = 2700
group = 1
emmcache = 1,3,10,0
blockemm-unknown = 1
-
Display More
Yes the Nordic provider use the same caid:ident.
But s3n0 is correct this is no problem at all.
But if you where to use 2 CommonInterfaces you would have bigger problem ;)
Solution ther is CommonInterface assignment. Where you add correct channels to the correct CommonInterface
This settings works just fine
[reader]
label = Sweden
protocol = internal
device = /dev/sci0
detect = cd
mhz = 450
cardmhz = 2700
group = 2
emmcache = 1,3,10,0
blockemm-unknown = 1
blockemm-g = 1
[reader]
label = Norway
protocol = internal
device = /dev/sci1
detect = cd
mhz = 450
cardmhz = 2700
group = 1
emmcache = 1,3,10,0
blockemm-unknown = 1
On one card blocking by inquiries as it is possible to bypass it? In 30 minutes blocking is disconnected
-
Do you mean SurfLock function in the firmware algorithm on the decoder card ? This feature prevents ECM requests from being frequent, such as sharing protection.
Of course, the problem can be elsewhere. Algorithm in the decoder card firmware, can contain any other functions.
For example, a decoding card may request to receive a particular EMM packet of a certain type, always on a regular basis, at certain time intervals. Sometimes it's once a month, other times it's a day, and other times it's 10 minutes, for example.
Of course, the problem may involve other things as well. Not what I mentioned above. However, you need to describe your problem (your question) in more detail.
-
Display More
Do you mean SurfLock function in the firmware algorithm on the decoder card ? This feature prevents ECM requests from being frequent, such as sharing protection.
Of course, the problem can be elsewhere. Algorithm in the decoder card firmware, can contain any other functions.
For example, a decoding card may request to receive a particular EMM packet of a certain type, always on a regular basis, at certain time intervals. Sometimes it's once a month, other times it's a day, and other times it's 10 minutes, for example.
Of course, the problem may involve other things as well. Not what I mentioned above. However, you need to describe your problem (your question) in more detail.
Can I will help log
Display MoreYes the Nordic provider use the same caid:ident.
But s3n0 is correct this is no problem at all.
But if you where to use 2 CommonInterfaces you would have bigger problem ;)
Solution ther is CommonInterface assignment. Where you add correct channels to the correct CommonInterface
This settings works just fine
[reader]
label = Sweden
protocol = internal
device = /dev/sci0
detect = cd
mhz = 450
cardmhz = 2700
group = 2
emmcache = 1,3,10,0
blockemm-unknown = 1
blockemm-g = 1
[reader]
label = Norway
protocol = internal
device = /dev/sci1
detect = cd
mhz = 450
cardmhz = 2700
group = 1
emmcache = 1,3,10,0
blockemm-unknown = 1
Has written down so
[reader]
label = BigBang
protocol = stapi
device = SC0
detect = cd
mhz = 450
cardmhz = 2700
group = 2
emmcache = 1,3,10,0
blockemm-unknown = 1
blockemm-g = 1
[reader]
label = telekarta
protocol = stapi
device = SC1
detect = cd
mhz = 450
cardmhz = 2700
group = 1
emmcache = 1,3,10,0
blockemm-unknown = 1
(reader) BigBang [conax] Warning: needed try nr 2, next ECM has some delay
2022/01/29 21:36:02 67E47BBF c (ecm) root (0B00&/0000/190A/0582/67:B4B87347E84CB2CF3F623B7347992605.0947780A_008ED765828452582A7431CFF9638FEB HOP:00): found (107 ms) by telekarta (L/2/2/2)
2022/01/29 21:36:02 2B462E20 r (dvbstapi) stapi: STSMART-IFD: RawRead ErrCode: 720898
2022/01/29 21:36:23 2B462E20 r (reader) BigBang [conax] Warning: needed try nr 2, next ECM has some delay
2022/01/29 21:36:23 67E47BBF c (ecm) root (0B00&/0000/190A/0582/67:40E423F5A56971DE8B0BD399EBD13DA1.DF4BFF49_008ED76582845258959CC7F8B77C6396 HOP:00): found (105 ms) by telekarta (L/2/2/2)
2022/01/29 21:36:44 67E47BBF c (ecm) root (0B00&/0000/190A/0582/67:5CAC87F199318DF64C362AF44F6222BD.D6A7A8FC_8C5005E1971DC175959CC7F8B77C6396 HOP:00): found (105 ms) by telekarta (L/2/2/2)
2022/01/29 21:36:46 2B462E20 r (dvbstapi) stapi: STSMART-IFD: RawRead ErrCode: 11
2022/01/29 21:36:46 2B462E20 r (reader) BigBang [conax] Warning: needed try nr 2, next ECM has some delay
2022/01/29 21:36:47 2B462E20 r (dvbstapi) stapi: STSMART-IFD: RawRead ErrCode: 11
2022/01/29 21:36:58 67E47BBF c (dvbapi) Demuxer 0 Unable to open PMT file /tmp/pmt1_1.tmp -> stop descrambling!
2022/01/29 21:36:58 67E47BBF c (dvbapi) Demuxer 0 stopped descrambling for program 0582 (0B00@000000:0582 unknown)
2022/01/29 21:36:58 67E47BBF c (dvbapi) Demuxer 0 ecmpid 0 CAID: 0B00 ECM_PID: 1770 PROVID: 000000
2022/01/29 21:36:58 67E47BBF c (dvbapi) Demuxer 0 ecmpid 1 CAID: 0B02 ECM_PID: 1771 PROVID: 000000
2022/01/29 21:36:58 67E47BBF c (dvbapi) Demuxer 0 found 2 ECM pids and 2 STREAM pids in CA PMT
2022/01/29 21:36:58 67E47BBF c (dvbapi) Demuxer 0 trying to descramble PID 0 CAID 0B00 PROVID 000000 ECMPID 1770 ANY CHID PMTPID 0000 VPID 00C8
2022/01/29 21:36:59 67E47BBF c (dvbapi) Demuxer 0 found 2 ECM pids and 2 STREAM pids in PMT
2022/01/29 21:37:00 2B462E20 r (dvbstapi) stapi: STSMART-IFD: RawRead ErrCode: 11
2022/01/29 21:37:00 2B462E20 r (reader) BigBang [conax] Warning: needed try nr 2, next ECM has some delay
2022/01/29 21:37:01 2B462E20 r (dvbstapi) stapi: STSMART-IFD: RawRead ErrCode: 11
2022/01/29 21:37:01 67E47BBF c (ecm) root (0B00&/0000/1770/0321/37:F37FE1376477EE0D2CD1E7852A609639.7BDCE8D0_00000000000000000000000000000000 HOP:00): not found (2014 ms) by BigBang (F/2/2/2)
2022/01/29 21:37:01 67E47BBF c (dvbapi) Demuxer 0 restarting decoding requests after 1 ms with 1 enabled and 1 disabled ecmpids!
2022/01/29 21:37:01 67E47BBF c (dvbapi) Demuxer 0 trying to descramble PID 0 CAID 0B00 PROVID 000000 ECMPID 1770 ANY CHID PMTPID 0321 VPID 00C8
2022/01/29 21:37:01 67E47BBF c (dvbstapi) overtake: clear pid: 0
2022/01/29 21:37:02 2B462E20 r (dvbstapi) stapi: STSMART-IFD: RawRead ErrCode: 11
2022/01/29 21:37:02 2B462E20 r (reader) BigBang [conax] Warning: needed try nr 2, next ECM has some delay
2022/01/29 21:37:03 2B462E20 r (dvbstapi) stapi: STSMART-IFD: RawRead ErrCode: 11
2022/01/29 21:37:03 67E47BBF c (ecm) root (0B00&/0000/1770/0321/37:926EBD1526445C306565BF6C0972E2DD.3376FAAB_00000000000000000000000000000000 HOP:00): not found (3910 ms) by BigBang (F/2/2/2)
2022/01/29 21:37:03 67E47BBF c (ecm) root (0B00&/0000/1770/0321/37:926EBD1526445C306565BF6C0972E2DD.3376FAAB_00000000000000000000000000000000 HOP:00): not found (1833 ms) by BigBang (F/2/2/2)
2022/01/29 21:37:03 67E47BBF c (dvbapi) Demuxer 0 restarting decoding requests after 4 ms with 1 enabled and 1 disabled ecmpids!
-
What box and image are you using??
-
Has written down so
[reader]
The protocol and device on both readers are wrong. Use the reader configs seagen posted then share another oscam log.
-
What box and image are you using??
OSCam << cardserver log switched, version 1.20_svn, build r11546-798 (sh4-linux-stapi)
2022/01/29 21:32:21 00000000 s (main) System name = Linux
Has written down so
[reader]
The protocol and device on both readers are wrong. Use the reader configs seagen posted then share another oscam log.
With those options does not work absolutely
If one card works
If two does not work
-
STAPI interface ? Hmmm ... is this an Android system ? Write which set-top box you use (manufacturer + type). Please do not write the detected platform from the LOG, but write what the exact device is. Is it some Android-Box ? What brand and type ? Of course, the STAPI interface is configured a little differently.
-
Is it some Android-Box ?
STAPI - SH4 is receivers with Spark STI 7111 or 7162 Processors.
-
Is it some Android-Box ?
STAPI - SH4 is receivers with Spark STI 7111 or 7162 Processors.
Openbox S6 (Lunux)
OSCam Support Forum
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!
