Digital Eliteboard - Das Digitale Technik Forum

Registriere dich noch heute kostenloses um Mitglied zu werden! Sobald du angemeldet bist, kannst du auf unserer Seite aktiv teilnehmen, indem du deine eigenen Themen und Beiträge erstellst und dich über deinen eigenen Posteingang mit anderen Mitgliedern unterhalten kannst! Zudem bekommst du Zutritt zu Bereiche, welche für Gäste verwehrt bleiben

oscam in dbox2

fuhre88

Freak
Registriert
27. März 2010
Beiträge
214
Reaktionspunkte
4
Punkte
78
hi
ich komme einfach nicht weiter,ich möchte oscam zum laufen bringen so das sie slot1 und slot2(mc) meine so2 karte liest und cccam auf oscam zugreift damit ich hchairing zur zweiten dbox machen kann,bekomme die oscam server,user,cfg und die cccam.cfg einfach nicht gebacken,bin neu auf dem gebiet,hat vielleicht einer die dateien schon fertig so das ich sie nur austausche,würde mich sehr freuen,denn desto mehr ich lesen,um so weniger verstehe ich
 
in tuxbox/config,habe oscam online installiert,hier meine letzten einstellungen

[global]
nice = -1
WaitForCards = 1
ClientTimeout = 5
LogFile = stdout
Level = 15
CacheDelay = 120
saveinithistory = 1
[webif]
httpport = 83
httprefresh = 10
httpallowed = 192.168.0.0-192.168.255.255
httphideidleclients = 1
httpreadonly = 0
[cccam]
port = 12000
reshare = 1
version = 2.1.1
build = 2971
[dvbapi]
enabled = 1
au = 1
boxtype = dbox2
user = DBOX
pmt_mode = 0


[reader]
label = Sky-S02
device = /dev/tts/0
Protocol = mouse
detect = cd
enable = 1
smargopatch = 1
services = Sky-S02
CAID = 1702,1833
ident = 000000
emmcache = 1,3,2
group = 1
mhz = 600
cardmhz = 600
[reader]
label = Sky-S02
device = /dev/tts/1
Protocol = mouse
detect = cd
enable = 1
smargopatch = 1
services = Sky-S02
CAID = 1702,1833
ident = 000000
emmcache = 1,3,2
group = 1
mhz = 600
cardmhz = 600

[account]
user = user1
pwd = pass1
group = 1
monlevel = 1
au = 0
keepalive = 1
caid = 1702,1833
services = Sky-S02
 
hier der log


-------------------------------------------------------------------------------
>> OSCam << cardserver started at Thu Jan 1 02:00:31 1970
-------------------------------------------------------------------------------
1970/01/01 2:00:31 4000 s version=1.00-unstable_svn, build #3818, system=powerpc-tuxbox-linux, nice=-1
1970/01/01 2:00:31 4000 s client max. idle=120 sec, debug level=0
1970/01/01 2:00:31 4000 s max. logsize=unlimited
1970/01/01 2:00:31 4000 s client timeout=5000 ms, fallback timeout=2500 ms, cache delay=120 ms
1970/01/01 2:00:32 4000 s auth size=4800
1970/01/01 2:00:32 4000 s services reloaded: 0 services freed, 3 services loaded
1970/01/01 2:00:32 4000 s userdb reloaded: 0 accounts freed, 1 accounts loaded, 0 expired, 0 disabled
1970/01/01 2:00:32 4000 s signal handling initialized (type=sysv)
1970/01/01 2:00:32 4000 s 113 service-id's loaded
1970/01/01 2:00:32 4000 s can't open file "/var/tuxbox/config/oscam.tiers" (err=2), no tier-id's loaded
1970/01/01 2:00:32 4000 s can't open file "/var/tuxbox/config/oscam.provid" (err=2), no provids's loaded
1970/01/01 2:00:32 4000 s 22 lengths for caid guessing loaded
1970/01/01 2:00:32 4000 s monitor: disabled
1970/01/01 2:00:32 4000 s camd33: disabled
1970/01/01 2:00:32 4000 s camd35: disabled
1970/01/01 2:00:32 4000 s cs378x: disabled
1970/01/01 2:00:32 4000 s newcamd: disabled
1970/01/01 2:00:32 4000 s cccam: initialized (fd=6, port=12000, ip=192.168.2.30, crypted)
1970/01/01 2:00:32 4000 s radegast: disabled
1970/01/01 2:00:32 4000 s http disabled
1970/01/01 2:00:32 4000 s creating thread for device /dev/tts/0 slot 0
1970/01/01 2:00:32 4002 r reader thread started (thread= 4002, device=/dev/tts/0, detect=cd, mhz=600, cardmhz=600)
1970/01/01 2:00:32 4000 s creating thread for device /dev/tts/1 slot 0
1970/01/01 2:00:32 8003 r reader thread started (thread= 8003, device=/dev/tts/1, detect=cd, mhz=600, cardmhz=600)
1970/01/01 2:00:32 8003 r WARNING: your card is asking for custom_baudrate = 1200, but your configuration can only deliver custom_baudrate = -2147483648
1970/01/01 2:00:32 8003 r You are over- or underclocking, try OSCam when running your reader at normal clockspeed as required by your card, and setting mhz and cardmhz parameters accordingly.
1970/01/01 2:00:32 8003 r You are probably connecting your reader via a serial port, OSCam has more flexibility switching to custom_baudrates when using an USB->serial converter, preferably based on FTDI chip.
1970/01/01 2:00:32 4002 r WARNING: your card is asking for custom_baudrate = 1200, but your configuration can only deliver custom_baudrate = -2147483648
1970/01/01 2:00:32 4002 r You are over- or underclocking, try OSCam when running your reader at normal clockspeed as required by your card, and setting mhz and cardmhz parameters accordingly.
1970/01/01 2:00:32 4002 r You are probably connecting your reader via a serial port, OSCam has more flexibility switching to custom_baudrates when using an USB->serial converter, preferably based on FTDI chip.
1970/01/01 2:00:32 4000 s waiting for local card init
1970/01/01 2:00:33 8003 r WARNING: your card is asking for custom_baudrate = 9600, but your configuration can only deliver custom_baudrate = -2147483648
1970/01/01 2:00:33 8003 r You are over- or underclocking, try OSCam when running your reader at normal clockspeed as required by your card, and setting mhz and cardmhz parameters accordingly.
1970/01/01 2:00:33 8003 r You are probably connecting your reader via a serial port, OSCam has more flexibility switching to custom_baudrates when using an USB->serial converter, preferably based on FTDI chip.
1970/01/01 2:00:33 4002 r WARNING: your card is asking for custom_baudrate = 9600, but your configuration can only deliver custom_baudrate = -2147483648
1970/01/01 2:00:33 4002 r You are over- or underclocking, try OSCam when running your reader at normal clockspeed as required by your card, and setting mhz and cardmhz parameters accordingly.
1970/01/01 2:00:33 4002 r You are probably connecting your reader via a serial port, OSCam has more flexibility switching to custom_baudrates when using an USB->serial converter, preferably based on FTDI chip.
1970/01/01 2:00:34 4002 r card detected
1970/01/01 2:00:45 4002 r Error activating card.
1970/01/01 2:00:56 4002 r Error activating card.
2011/02/18 9:23:37 4002 r Error activating card.
2011/02/18 9:23:48 4002 r Error activating card.
 
AW: oscam in dbox2

In der config sind schon einige Fehler drin,...

Aber erst mal was anderes:
Warum willst du OScam und CCcam gemeinsam laufen lassen - für eine S02 reicht eins von beiden.
Mach doch die ganze Sache so einfach wie möglich - ist doch dann auch leichter den Überblick zu behalten.



Gruß Superhansi
 
würde ich gerne,aber wie,wenn dann nur oscam,bräuchte dann nur die cfg dateien und die c-line für die klienten
 
AW: oscam in dbox2

Die S02 ist überhaupt kein Problem, die funzt mit CCcam only oder mit OScam only, Clienten kannst du genauso anbinden (da hast bei OScam sogar mehr Möglichkeiten).

Die CCcam ist in der Konfiguration wesentlich einfacher, kann aber nicht mit allen Karten umgehen (z.B. die schwarze HD+).

OScam ist in der Konfiguration etwas komplizierter (gerade für Neueinsteiger),
dafür kann OScam mit allen Karten umgehen und unterstützt viele Protokolle. Du bist also flexibler mit OScam.

Beides gemeinsam funzt auch, du mußt dann aber auch beides Konfigurieren.

Wenn es dir nur um die S02 geht und du mit HD+ nichts am Hut hast, dann nutze doch CCcam only.

Wie schon gesagt, bevor wir an den config's "rumbasteln" solltest du dich erst entscheiden welchen Weg du gehen willst.



Gruß Superhansi
 
hatte cccam+newcs lief top möchte jetzt oscam,falls ich mir hd hole,habe oscam neu online(glj) installiert,brauche also nur die cfg dateien,damit slot1 und 2 mit der so2 läuft
 
AW: oscam in dbox2

Also nur cccam auf der dbox mit multicam geht nicht weil cccam in der dbox2 nicht direkt auf das multicam usw. zugreifen kann. Deshalb bedarf es auch immer einem davor geschalteten Cardserver wie NewCS oder Oscam wenn cccam genutzt werden soll der die daten quasi ausliest und übergibt.

Wichtig zu lesen für das Thema oscam wäre auch noch dieser Thread...da kann nämlich der Hund schon begraben sein wie ich selber erst festellen musste.
Gerade in Bezug auf die Oscam Version die noch bis zuletzt via online update im GLJ Image angeboten wurde kann ich sagen das diese zu 100% nicht funktionierte.
Hab das GLJ Team diesbzgl. zwar schon angetriggert und die wollten das auch auf eine andere Version ändern aber ob dies aktuell schon geschehen ist weiß ich nicht.

Gruß
Ruler
 
Zuletzt bearbeitet:
AW: oscam in dbox2

Wenn Ruler sagt, daß CCcam only auf der dbox2 nicht funzt wird er wohl Recht haben - mit der dbox kenne ich mich nicht aus.

Du musst dich Anmelden oder Registrieren um den Inhalt der Angebote zu sehen!
Na dann ist ja alles klar.


Du musst dich Anmelden oder Registrieren um den Inhalt der Angebote zu sehen!
Was mir noch unklar ist wieso du slot1 und 2 brauchst, du hast doch nur eine S02 - oder habe ich was nicht kapiert?
Oder ist das was, was nur die dbox (von der ich keine Ahnung habe) betrifft.


Du musst dich Anmelden oder Registrieren um den Inhalt der Angebote zu sehen!
Das Board (oder in dem Fall ich) ist keine Maschine wo du deine Wünsche eingibst und hinten fällt die fertige config raus - mußt schon selber mitmachen und dich in OScam einlesen.

Ich werde mir deine config mal anschauen und was mir so auffällt markieren.


Gruß Superhansi
 
AW: oscam in dbox2

Also gerade aus den letzten Tagen sind in dem Bereich hier genug Threads offen, wo man mit ein wenig einlesen und ausprobieren zum Ziel kommen sollte. Ich habs gelernt durch ewiges rumprobieren und testen ohne Erfolg. Am Ende war es eine nicht funktionierende oscam Version aber nirgends stand davon was bis ich irgendwann den Tip bekam. Lernen durch schmerzen geht immer noch am besten *gg* :dance3:
 
wenn multicam wäre schon ok,hier die config
[global]
nice = -1
WaitForCards = 1
ClientTimeout = 5
LogFile = stdout
Level = 15
CacheDelay = 120
saveinithistory = 1
serverip=192.168.2.30
logfile=/var/log/os
[webif
httpport = 83
httprefresh = 10
httpallowed = 192.168.0.0-192.168.255.255
httphideidleclients = 1
httpreadonly = 0
[cccam]
port = 12345
version = 1.2.3
build = 1234
reshare = 0

[dvbapi]
enabled = 1
au = 1
boxtype = dbox2
user = DBOX
pmt_mode = 0

[reader]
label = Sky-S02
device = /dev/tts/0
Protocol = mouse
detect = cd
enable = 1
smargopatch = 1
services = Sky-S02
CAID = 1702,1833
ident = 1702:000000,1833:000000
emmcache = 1,3,2
group = 1
mhz = 600
cardmhz = 600
[reader]
label = Sky-S02
device = /dev/tts/1
Protocol = mouse
detect = cd
enable = 1
smargopatch = 1
services = Sky-S02
CAID = 1702,1833
ident = 1702:000000,1833:000000
emmcache = 1,3,2
group = 1
mhz = 600
cardmhz = 600

[account]
user = user1
pwd = pass1
group = 1
monlevel = 1
au = 0
keepalive = 1
caid = 1702,1833
services = Sky-S02
[account]
user = DBOX
group = 1
au = 1
CAID = 1702,1833
 
-------------------------------------------------------------------------------
>> OSCam << cardserver started at Thu Jan 1 02:00:33 1970
-------------------------------------------------------------------------------
1970/01/01 2:00:33 4000 s >> OSCam << cardserver started version 1.00-unstable_svn, build #4569 (powerpc-tuxbox-linux)
1970/01/01 2:00:33 4000 s version=1.00-unstable_svn, build #4569, system=powerpc-tuxbox-linux, nice=-1
1970/01/01 2:00:33 4000 s client max. idle=120 sec, debug level=0
1970/01/01 2:00:33 4000 s max. logsize=unlimited
1970/01/01 2:00:33 4000 s client timeout=5000 ms, fallback timeout=2500 ms, cache delay=120 ms
1970/01/01 2:00:33 4000 s auth size=4976
1970/01/01 2:00:33 4000 s services reloaded: 0 services freed, 3 services loaded
1970/01/01 2:00:33 4000 s userdb reloaded: 2 accounts loaded, 0 expired, 0 disabled
1970/01/01 2:00:33 4000 s signal handling initialized (type=sysv)
1970/01/01 2:00:33 4000 s oscam.srvid loading failed, old format
1970/01/01 2:00:33 4000 s can't open file "/var/tuxbox/config/oscam.tiers" (err=2), no tier-id's loaded
1970/01/01 2:00:33 4000 s can't open file "/var/tuxbox/config/oscam.provid" (err=2), no provids's loaded
1970/01/01 2:00:33 4000 s 22 lengths for caid guessing loaded
1970/01/01 2:00:33 4000 s monitor: disabled
1970/01/01 2:00:33 4000 s camd33: disabled
1970/01/01 2:00:33 4000 s camd35: disabled
1970/01/01 2:00:33 4000 s cs378x: disabled
1970/01/01 2:00:33 4000 s newcamd: disabled
1970/01/01 2:00:33 4000 s cccam: initialized (fd=8, port=12345, ip=192.168.2.30, crypted)
1970/01/01 2:00:33 4000 s radegast: disabled
1970/01/01 2:00:33 4000 s http thread started
1970/01/01 2:00:33 4000 s creating thread for device /dev/tts/0
1970/01/01 2:00:33 8003 h HTTP Server listening on port 83
1970/01/01 2:00:33 C004 r reader thread started (thread= C004, label=sky-s02, device=/dev/tts/0, detect=cd, mhz=600, cardmhz=600)
1970/01/01 2:00:33 C004 r WARNING: your card is asking for custom_baudrate = 1200, but your configuration can only deliver custom_baudrate = -2147483648
1970/01/01 2:00:33 C004 r You are over- or underclocking, try OSCam when running your reader at normal clockspeed as required by your card, and setting mhz and cardmhz parameters accordingly.
1970/01/01 2:00:33 4000 s creating thread for device /dev/tts/1
1970/01/01 2:00:33 C004 r You are probably connecting your reader via a serial port, OSCam has more flexibility switching to custom_baudrates when using an USB->serial converter, preferably based on FTDI chip.
1970/01/01 2:00:33 10005 r reader thread started (thread= 10005, label=sky-s02, device=/dev/tts/1, detect=cd, mhz=600, cardmhz=600)
1970/01/01 2:00:33 10005 r WARNING: your card is asking for custom_baudrate = 1200, but your configuration can only deliver custom_baudrate = -2147483648
1970/01/01 2:00:33 10005 r You are over- or underclocking, try OSCam when running your reader at normal clockspeed as required by your card, and setting mhz and cardmhz parameters accordingly.
1970/01/01 2:00:33 4000 s loadbalancer: can't read from file /tmp/.oscam/stat
1970/01/01 2:00:33 4000 s waiting for local card init
1970/01/01 2:00:33 10005 r You are probably connecting your reader via a serial port, OSCam has more flexibility switching to custom_baudrates when using an USB->serial converter, preferably based on FTDI chip.
1970/01/01 2:00:34 C004 r WARNING: your card is asking for custom_baudrate = 9600, but your configuration can only deliver custom_baudrate = -2147483648
1970/01/01 2:00:34 C004 r You are over- or underclocking, try OSCam when running your reader at normal clockspeed as required by your card, and setting mhz and cardmhz parameters accordingly.
1970/01/01 2:00:34 C004 r You are probably connecting your reader via a serial port, OSCam has more flexibility switching to custom_baudrates when using an USB->serial converter, preferably based on FTDI chip.
1970/01/01 2:00:34 10005 r WARNING: your card is asking for custom_baudrate = 9600, but your configuration can only deliver custom_baudrate = -2147483648
1970/01/01 2:00:34 10005 r You are over- or underclocking, try OSCam when running your reader at normal clockspeed as required by your card, and setting mhz and cardmhz parameters accordingly.
1970/01/01 2:00:34 10005 r You are probably connecting your reader via a serial port, OSCam has more flexibility switching to custom_baudrates when using an USB->serial converter, preferably based on FTDI chip.
1970/01/01 2:00:35 C004 r sky-s02 card detected
1970/01/01 2:00:35 10005 r sky-s02 card detected
1970/01/01 2:00:35 10005 r WARNING: your card is asking for custom_baudrate = 9600, but your configuration can only deliver custom_baudrate = -2147483648
1970/01/01 2:00:35 10005 r You are over- or underclocking, try OSCam when running your reader at normal clockspeed as required by your card, and setting mhz and cardmhz parameters accordingly.
1970/01/01 2:00:35 10005 r You are probably connecting your reader via a serial port, OSCam has more flexibility switching to custom_baudrates when using an USB->serial converter, preferably based on FTDI chip.
1970/01/01 2:00:46 C004 r Error activating card.
1970/01/01 2:00:46 10005 r Error activating card.
1970/01/01 2:00:46 C004 r WARNING: your card is asking for custom_baudrate = 9600, but your configuration can only deliver custom_baudrate = -2147483648
1970/01/01 2:00:46 C004 r You are over- or underclocking, try OSCam when running your reader at normal clockspeed as required by your card, and setting mhz and cardmhz parameters accordingly.
1970/01/01 2:00:46 C004 r You are probably connecting your reader via a serial port, OSCam has more flexibility switching to custom_baudrates when using an USB->serial converter, preferably based on FTDI chip.
1970/01/01 2:00:47 10005 r WARNING: your card is asking for custom_baudrate = 9600, but your configuration can only deliver custom_baudrate = -2147483648
1970/01/01 2:00:47 10005 r You are over- or underclocking, try OSCam when running your reader at normal clockspeed as required by your card, and setting mhz and cardmhz parameters accordingly.
1970/01/01 2:00:47 10005 r You are probably connecting your reader via a serial port, OSCam has more flexibility switching to custom_baudrates when using an USB->serial converter, preferably based on FTDI chip.
2011/02/18 11:50:43 C004 r Error activating card.
2011/02/18 11:50:43 10005 r Error activating card.
2011/02/18 11:50:43 C004 r WARNING: your card is asking for custom_baudrate = 9600, but your configuration can only deliver custom_baudrate = -2147483648
2011/02/18 11:50:43 C004 r You are over- or underclocking, try OSCam when running your reader at normal clockspeed as required by your card, and setting mhz and cardmhz parameters accordingly.
2011/02/18 11:50:43 C004 r You are probably connecting your reader via a serial port, OSCam has more flexibility switching to custom_baudrates when using an USB->serial converter, preferably based on FTDI chip.
2011/02/18 11:50:44 10005 r WARNING: your card is asking for custom_baudrate = 9600, but your configuration can only deliver custom_baudrate = -2147483648
2011/02/18 11:50:44 10005 r You are over- or underclocking, try OSCam when running your reader at normal clockspeed as required by your card, and setting mhz and cardmhz parameters accordingly.
2011/02/18 11:50:44 10005 r You are probably connecting your reader via a serial port, OSCam has more flexibility switching to custom_baudrates when using an USB->serial converter, preferably based on FTDI chip.
2011/02/18 11:50:54 C004 r Error activating card.
2011/02/18 11:50:54 10005 r Error activating card.
2011/02/18 11:50:54 C004 r card initializing error
2011/02/18 11:50:55 10005 r card initializing error
2011/02/18 11:50:55 4000 s init for all local cards done
2011/02/18 11:50:55 4000 s anti cascading disabled
2011/02/18 11:50:55 14006 c plain dvbapi-client granted (DBOX, au=auto)
2011/02/18 11:50:55 14006 c dvbapi: can't open priority file /var/tuxbox/config/oscam.dvbapi
2011/02/18 11:50:55 14006 c dvbapi: found pmt file /tmp/pmt.tmp
2011/02/18 11:50:55 14006 c dvbapi: found pmt file /tmp/pmt.tmp
2011/02/18 11:50:55 14006 c dvbapi: found pmt file /tmp/pmt.tmp
2011/02/18 11:50:55 14006 c dvbapi: [ADD PID 0] CAID: 1702 ECM_PID: 1742 PROVID: 000000
2011/02/18 11:50:55 14006 c dvbapi: [ADD PID 1] CAID: 1722 ECM_PID: 1642 PROVID: 000000
2011/02/18 11:50:55 14006 c dvbapi: [ADD PID 2] CAID: 1833 ECM_PID: 1842 PROVID: 000000
2011/02/18 11:50:55 14006 c dvbapi: [ADD PID 3] CAID: 1834 ECM_PID: 1C42 PROVID: 000000
2011/02/18 11:50:55 14006 c dvbapi: [ADD PID 4] CAID: 1836 ECM_PID: 1843 PROVID: 000000
2011/02/18 11:50:55 14006 c dvbapi: [ADD PID 5] CAID: 09C4 ECM_PID: 1B42 PROVID: 000000
2011/02/18 11:50:55 14006 c dvbapi: [ADD PID 6] CAID: 09C7 ECM_PID: 1D42 PROVID: 000000
2011/02/18 11:50:55 14006 c dvbapi: [ADD PID 7] CAID: 09AF ECM_PID: 1F42 PROVID: 000000
2011/02/18 11:50:55 14006 c dvbapi: [ADD PID 8] CAID: 1861 ECM_PID: 1942 PROVID: 000000
2011/02/18 11:50:55 14006 c dvbapi: new program number: 000A (1702:000A unknown)
2011/02/18 11:50:55 14006 c dvbapi: [ADD PID 0] CAID: 1702 ECM_PID: 1742 PROVID: 000000
2011/02/18 11:50:55 14006 c dvbapi: [ADD PID 0] CAID: 1702 ECM_PID: 1742 PROVID: 000000
2011/02/18 11:50:55 14006 c dvbapi: stoping demux for pmt file /tmp/pmt.tmp
2011/02/18 11:50:55 14006 c dvbapi: [ADD PID 1] CAID: 1722 ECM_PID: 1642 PROVID: 000000
2011/02/18 11:50:55 14006 c dvbapi: [ADD PID 2] CAID: 1833 ECM_PID: 1842 PROVID: 000000
2011/02/18 11:50:55 14006 c dvbapi: [ADD PID 3] CAID: 1834 ECM_PID: 1C42 PROVID: 000000
2011/02/18 11:50:55 14006 c dvbapi: [ADD PID 4] CAID: 1836 ECM_PID: 1843 PROVID: 000000
2011/02/18 11:50:55 14006 c dvbapi: [ADD PID 5] CAID: 09C4 ECM_PID: 1B42 PROVID: 000000
2011/02/18 11:50:55 14006 c dvbapi: [ADD PID 6] CAID: 09C7 ECM_PID: 1D42 PROVID: 000000
2011/02/18 11:50:55 14006 c dvbapi: [ADD PID 7] CAID: 09AF ECM_PID: 1F42 PROVID: 000000
2011/02/18 11:50:55 14006 c dvbapi: [ADD PID 8] CAID: 1861 ECM_PID: 1942 PROVID: 000000
2011/02/18 11:50:55 14006 c dvbapi: new program number: 000A ()
2011/02/18 11:50:55 14006 c DBOX (1702&000000/000A/93:AFB3): not found (61 ms) (of 2 avail 2)
2011/02/18 11:50:56 14006 c DBOX (1722&000000/000A/93:FC08): rejected caid (121 ms) (of 0 avail 0) (invalid caid 1722)
2011/02/18 11:50:56 14006 c DBOX (1833&000000/000A/89:F395): rejected group (127 ms) (of 0 avail 0) (no matching reader)
2011/02/18 11:50:56 14006 c DBOX (1834&000000/000A/89:3F72): rejected caid (130 ms) (of 0 avail 0) (invalid caid 1834)
2011/02/18 11:50:56 14006 c DBOX (1836&000000/000A/89:9392): rejected caid (127 ms) (of 0 avail 0) (invalid caid 1836)
2011/02/18 11:50:57 14006 c DBOX (09C4&000000/000A/90:2B7C): rejected caid (127 ms) (of 0 avail 0) (invalid caid 9c4)
2011/02/18 11:50:57 14006 c DBOX (09C7&000000/000A/A6:27CC): rejected caid (126 ms) (of 0 avail 0) (invalid caid 9c7)
2011/02/18 11:50:57 14006 c DBOX (09AF&000000/000A/8D:E33C): rejected caid (127 ms) (of 0 avail 0) (invalid caid 9af)
2011/02/18 11:50:57 14006 c dvbapi: try pids again #1
2011/02/18 11:50:57 14006 c DBOX (1861&000000/000A/89:19FA): rejected caid (127 ms) (of 0 avail 0) (invalid caid 1861)
2011/02/18 11:50:58 14006 c dvbapi: read error 110 on fd 25
2011/02/18 11:50:58 14006 c DBOX (1722&000000/0000/93:FC08): rejected caid (145 ms) (of 0 avail 0) (invalid caid 1722)
2011/02/18 11:51:00 14006 c DBOX (1833&000000/0000/89:83F7): rejected group (127 ms) (of 0 avail 0) (no matching reader)
2011/02/18 11:51:00 14006 c DBOX (1702&000000/000A/93:A082): not found (137 ms) (of 2 avail 2)
2011/02/18 11:51:00 14006 c DBOX (1722&000000/000A/93:58CA): rejected caid (131 ms) (of 0 avail 0) (invalid caid 1722)
2011/02/18 11:51:00 14006 c DBOX (1834&000000/0000/89:E4C3): rejected caid (123 ms) (of 0 avail 0) (invalid caid 1834)
2011/02/18 11:51:00 14006 c DBOX (1836&000000/0000/89:190D): rejected caid (129 ms) (of 0 avail 0) (invalid caid 1836)
2011/02/18 11:51:01 14006 c DBOX (09C4&000000/0000/90:4EE7): rejected caid (131 ms) (of 0 avail 0) (invalid caid 9c4)
2011/02/18 11:51:01 14006 c DBOX (09C7&000000/0000/A6:9461): rejected caid (132 ms) (of 0 avail 0) (invalid caid 9c7)
2011/02/18 11:51:01 14006 c DBOX (09AF&000000/0000/8D:EAA0): rejected caid (130 ms) (of 0 avail 0) (invalid caid 9af)
2011/02/18 11:51:01 14006 c dvbapi: try pids again #1
2011/02/18 11:51:01 14006 c DBOX (1861&000000/0000/89:2EF5): rejected caid (131 ms) (of 0 avail 0) (invalid caid 1861)
2011/02/18 11:51:02 14006 c DBOX (1702&000000/000A/93:AFB3): timeout (5003 ms) (of 0 avail 0)
2011/02/18 11:51:03 14006 c DBOX (1834&000000/000A/89:E4C3): rejected caid (124 ms) (of 0 avail 0) (invalid caid 1834)
2011/02/18 11:51:03 14006 c DBOX (1836&000000/000A/89:190D): rejected caid (123 ms) (of 0 avail 0) (invalid caid 1836)
2011/02/18 11:51:03 14006 c DBOX (09C4&000000/000A/90:4EE7): rejected caid (123 ms) (of 0 avail 0) (invalid caid 9c4)
2011/02/18 11:51:03 14006 c DBOX (1833&000000/0000/89:F395): timeout (5175 ms) (of 0 avail 0)
2011/02/18 11:51:04 14006 c DBOX (1722&000000/0000/93:58CA): rejected caid (127 ms) (of 0 avail 0) (invalid caid 1722)
2011/02/18 11:51:04 14006 c DBOX (09C7&000000/000A/A6:9461): rejected caid (128 ms) (of 0 avail 0) (invalid caid 9c7)
2011/02/18 11:51:04 14006 c DBOX (09AF&000000/000A/8D:EAA0): rejected caid (124 ms) (of 0 avail 0) (invalid caid 9af)
2011/02/18 11:51:04 14006 c dvbapi: try pids again #2
2011/02/18 11:51:04 14006 c DBOX (1861&000000/000A/89:2EF5): rejected caid (124 ms) (of 0 avail 0) (invalid caid 1861)
2011/02/18 11:51:05 14006 c DBOX (1833&000000/000A/89:83F7): timeout (5228 ms) (of 0 avail 0)
2011/02/18 11:51:06 14006 c DBOX (1722&000000/000A/93:58CA): rejected caid (125 ms) (of 0 avail 0) (invalid caid 1722)
2011/02/18 11:51:07 14006 c DBOX (1833&000000/000A/89:0447): rejected group (124 ms) (of 0 avail 0) (no matching reader)
2011/02/18 11:51:07 14006 c DBOX (1834&000000/000A/89:C85F): rejected caid (125 ms) (of 0 avail 0) (invalid caid 1834)
2011/02/18 11:51:07 14006 c DBOX (1836&000000/000A/89:50A2): rejected caid (126 ms) (of 0 avail 0) (invalid caid 1836)
2011/02/18 11:51:07 14006 c DBOX (09C4&000000/000A/90:D4AF): rejected caid (126 ms) (of 0 avail 0) (invalid caid 9c4)
2011/02/18 11:51:08 14006 c DBOX (09C7&000000/000A/A6:1293): rejected caid (126 ms) (of 0 avail 0) (invalid caid 9c7)
2011/02/18 11:51:08 14006 c DBOX (09AF&000000/000A/8D:905F): rejected caid (127 ms) (of 0 avail 0) (invalid caid 9af)
2011/02/18 11:51:08 14006 c dvbapi: try pids again #3
2011/02/18 11:51:08 14006 c dvbapi: can't decode channel
2011/02/18 11:51:08 14006 c DBOX (1861&000000/000A/89:8DB0): rejected caid (126 ms) (of 0 avail 0) (invalid caid 1861)
2011/02/18 11:51:09 14006 c DBOX (1833&000000/0000/89:83F7): timeout (5226 ms) (of 0 avail 0)
2011/02/18 11:51:09 14006 c DBOX (1834&000000/0000/89:C85F): rejected caid (128 ms) (of 0 avail 0) (invalid caid 1834)
2011/02/18 11:51:09 14006 c dvbapi: can't decode channel
2011/02/18 11:51:09 14006 c DBOX (1702&000000/000A/93:A082): timeout (5136 ms) (of 0 avail 0)
2011/02/18 11:51:10 14006 c DBOX (1836&000000/0000/89:50A2): rejected caid (128 ms) (of 0 avail 0) (invalid caid 1836)
2011/02/18 11:51:10 14006 c DBOX (09C4&000000/0000/90:D4AF): rejected caid (128 ms) (of 0 avail 0) (invalid caid 9c4)
2011/02/18 11:51:10 14006 c DBOX (09C7&000000/0000/A6:1293): rejected caid (128 ms) (of 0 avail 0) (invalid caid 9c7)
2011/02/18 11:51:10 14006 c DBOX (09AF&000000/0000/8D:905F): rejected caid (129 ms) (of 0 avail 0) (invalid caid 9af)
2011/02/18 11:51:11 14006 c dvbapi: try pids again #2
2011/02/18 11:51:11 14006 c DBOX (1861&000000/0000/89:8DB0): rejected caid (129 ms) (of 0 avail 0) (invalid caid 1861)
2011/02/18 11:51:11 14006 c dvbapi: can't decode channel
2011/02/18 11:51:11 14006 c DBOX (1833&000000/000A/89:83F7): timeout (5387 ms) (of 0 avail 0)
2011/02/18 11:51:12 14006 c DBOX (1833&000000/0000/89:0447): timeout (5024 ms) (of 0 avail 0)
2011/02/18 11:51:12 14006 c DBOX (1722&000000/0000/93:0728): rejected caid (137 ms) (of 0 avail 0) (invalid caid 1722)
2011/02/18 11:51:14 14006 c DBOX (1833&000000/0000/89:670A): rejected group (121 ms) (of 0 avail 0) (no matching reader)
2011/02/18 11:51:14 14006 c DBOX (1834&000000/0000/89:1EED): rejected caid (122 ms) (of 0 avail 0) (invalid caid 1834)
2011/02/18 11:51:14 14006 c DBOX (1836&000000/0000/89:190E): rejected caid (122 ms) (of 0 avail 0) (invalid caid 1836)
2011/02/18 11:51:14 14006 c DBOX (09C4&000000/0000/90:1255): rejected caid (122 ms) (of 0 avail 0) (invalid caid 9c4)
2011/02/18 11:51:15 14006 c DBOX (09C7&000000/0000/A6:4C11): rejected caid (122 ms) (of 0 avail 0) (invalid caid 9c7)
2011/02/18 11:51:15 14006 c DBOX (09AF&000000/0000/8D:18B3): rejected caid (123 ms) (of 0 avail 0) (invalid caid 9af)
2011/02/18 11:51:15 14006 c dvbapi: try pids again #3
2011/02/18 11:51:15 14006 c dvbapi: can't decode channel
2011/02/18 11:51:15 14006 c DBOX (1861&000000/0000/89:8345): rejected caid (122 ms) (of 0 avail 0) (invalid caid 1861)
2011/02/18 11:51:17 14006 c dvbapi: can't decode channel
2011/02/18 11:51:17 14006 c DBOX (1833&000000/0000/89:0447): timeout (5163 ms) (of 0 avail 0)
 
tja ich lese schon 2tage und bastle rum,weiß auch nicht wo de fehler steckt,vielleicht liegt es ja doch an der online oscam,das sie nicht funktionieren soll
 
AW: oscam in dbox2

Nehm mal die Idents für 1702 und 1833 aus den Readern heraus. Dann musst du die Option Smargopatch bei seriellen Readern deaktivieren. Wenn es dann immer noch nicht geht, aktiviere mal das Loadbalancing Oldest Reader First. Aber generell würde ich dazu raten, eine Karte nach der anderen zu konfigurieren. Und nicht beide gleichzeitig. Da fehlt ein bissl Struktur bei der Vorgehensweise. Also Schritt für Schritt....erste Reader...erste Karte zum laufen bringen. Danach die zweite...und dann final Load Balancing.
 
Zurück
Oben