doscam für coolstream und raspberryPi
doscam für coolstream und raspberryPi
Code:
Version History:
V0.01
- Cryptoworks EMU
- Camd3.keys format
v0.02
- Nagra Aladin EMU (mapping necessary for KD Free)
V0.03
- Seca EMU
v0.04
- Via2.6 EMU
- Via3.0 EMU
- Conversion to SoftCam.Key
- No mapping for Digital Cable Free longer necessary
V0.05
- Via1 EMU for mezzo-added (0500:007400).
- Raspberry Fix
- Other minor bug fixes
v0.06
- Fixed ABSat
v0.07
- SoftNDS EMU (CAID ViaSat 0x090F)
- BISS
The minimum config of the EMU looks like this:
[CODE][reader]
label = emu
protocol = constcw
device = /var/keys/SoftCam.Key
Of course, also a Group and other parameters can be added, as seen on her regular readers.
It is definitely advisable with the CAID (s) specified as such a reader-matching occurs and not blindly every CAID will be tried.
Example:
Code:
[reader]
label = emu
protocol = constcw
device = /var/keys/SoftCam.Key
caid = 1801,0D05,0500,0100
If e.g. ORF is only seen enough, even 0D05 and the rest can get out. I think the logic behind it should be clear. If despite CAID still problems, it makes sense in the corresponding CAID oscam.dvbapi prioritize. Example oscam.dvbapi for ORF, Digital Cable Free & TNTSAT:
Code:
P: 0D05 #ORF
P: 1801 #Kabel Digital Free
P: 0500:030B00 #TNTSat
Notes:
- Case-insensitive when device path for SoftCam.Key (case-sensitive)! SoftCam.Key example, is something other than Softcam.key You can see the file we call you want, but it must also be so with device = ... stand.
- TNTSAT (0500:030 B00) uses long ECMs, which are not supported by each protocol. Is locally dvbapi users there of course, but the reader should be shared on the network, then the camd3 or cccam-protocol can be used. With the newcamd protocol, it does not work! Any other station also works with the newcamd protocol.
[/CODE]
Code:
[B][COLOR="Navy"]V0.08 vom 13.12.2012
- Irdeto2 EMU [/COLOR][/B]
Thx @BigBlock
