Changeset 5090 for trunk/Distribution
- Timestamp:
- 04/27/11 08:31:15 (13 years ago)
- Location:
- trunk/Distribution/doc
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/Distribution/doc/man/oscam.server.5
r5006 r5090 112 112 .RE 113 113 .PP 114 \fBcaid\fP = \fBCAID[&<mask>][,CAID[&<mask>]]...\fP 115 .RS 3n 116 define CAID for reader, some protocols only support one CAID, default:\fBmask\fP=FFFF 117 118 example: CAID = 0100,0200&FFDF 114 \fBcaid\fP = \fB<CAID>[&<mask>][:<CAID>][,<CAID>[&<mask>][:<CAID>]]...\fP 115 .RS 3n 116 define and mapping of CAIDs for reader, default:all CAIDs with mask FFFF 117 118 example: caid = 0100 119 caid = 0200&ffee:0300 120 caid = 0400&ff00:0500,0600 119 121 .RE 120 122 .PP -
trunk/Distribution/doc/txt/oscam.server.txt
r5006 r5090 1 oscam.server(5) 1 oscam.server(5) oscam.server(5) 2 2 3 3 … … 7 7 8 8 SYNOPSIS 9 The server configuration file for OSCam contains reader parameters. sections in oscam.server are recurring (more than one reader possible). At least one [reader] section is10 required.9 The server configuration file for OSCam contains reader parameters. sections in oscam.server are recurring (more than one reader possi‐ 10 ble). At least one [reader] section is required. 11 11 12 12 DESCRIPTIONS … … 35 35 constantcw: constant CW file name 36 36 37 constant CW file format: CA (4 digits):ID (6 digits):SID (4 digits):PMT PID (4 digits):ECM PID (4 digits):: key (16 Bytes seperated by spaces) 37 constant CW file format: CA (4 digits):ID (6 digits):SID (4 digits):PMT PID (4 digits):ECM PID (4 digits):: key (16 Bytes seperated by 38 spaces) 38 39 39 40 example: 1234:123456:1234:1234:1234::00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F … … 84 85 camd 3.x reader logport, camd 3.x UDP must be activated, only works if there's no camd 3.x cascading, 0 = disabled, default=0 85 86 86 caid = CAID[&<mask>][,CAID[&<mask>]]... 87 define CAID for reader, some protocols only support one CAID, default:mask=FFFF 88 89 example: CAID = 0100,0200&FFDF 87 caid = <CAID>[&<mask>][:<CAID>][,<CAID>[&<mask>][:<CAID>]]... 88 define and mapping of CAIDs for reader, default:all CAIDs with mask FFFF 89 90 example: caid = 0100 91 caid = 0200&ffee:0300 92 caid = 0400&ff00:0500,0600 90 93 91 94 audisabled = 0|1 … … 107 110 108 111 deprecated = 0|1 109 Frist the SC will be initialized in normal mode. If it fails, the SC will be automatically reverted to deprecated mode, so that the SC speed will not be changed and the commu‐110 nication will remain on normal ATR speed of 9600 baud.112 Frist the SC will be initialized in normal mode. If it fails, the SC will be automatically reverted to deprecated mode, so that the SC 113 speed will not be changed and the communication will remain on normal ATR speed of 9600 baud. 111 114 112 115 1 = use deprecated SC mode only, default:0 … … 196 199 197 200 readnano = [path]filename 198 write file (usually a copy of a file saved by savenano) to your smartcard, if no path is specified, the specified file is searched for in the configuration directory, only199 valid for physical readers, default:none201 write file (usually a copy of a file saved by savenano) to your smartcard, if no path is specified, the specified file is searched for 202 in the configuration directory, only valid for physical readers, default:none 200 203 201 204 example: readnano = write.emm … … 294 297 · Dreambox and other internal readers 295 298 296 For Dreambox and other internal readers the highest possible clockrate will be auto detected. The mhz parameter lets you override the values chosen by OSCam, if it differs 297 from 357 and 358, but usually you will not set any value for mhz. 298 299 For certain Dreamboxes (especially PPC clones) the default mhz parameter leads to slow ECM times and/or "not found" ECMs. By setting mhz to values like 200, 300, 400, ... 1600 300 you can find a value that works for your receiver and your card. The higher the mhz value, the slower the ECM time (strange enough). 301 302 If you choose the value too low, your card is not recognized (no ATR or "card not supported"). If you choose the value too high, you get slow ECM times. Our experience is that 303 either no mhz line, or a line mhz = 1000 works best. 299 For Dreambox and other internal readers the highest possible clockrate will be auto detected. The mhz parameter lets you override the 300 values chosen by OSCam, if it differs from 357 and 358, but usually you will not set any value for mhz. 301 302 For certain Dreamboxes (especially PPC clones) the default mhz parameter leads to slow ECM times and/or "not found" ECMs. By setting mhz 303 to values like 200, 300, 400, ... 1600 you can find a value that works for your receiver and your card. The higher the mhz value, the 304 slower the ECM time (strange enough). 305 306 If you choose the value too low, your card is not recognized (no ATR or "card not supported"). If you choose the value too high, you get 307 slow ECM times. Our experience is that either no mhz line, or a line mhz = 1000 works best. 304 308 305 309 · Phoenix / Smartmouse reader 306 310 307 Overclocking does not work with Windows and Mac OS X. Set mhz equivalent to the frequency of the reader. OSCam can not set the frequency of the reader. 311 Overclocking does not work with Windows and Mac OS X. Set mhz equivalent to the frequency of the reader. OSCam can not set the fre‐ 312 quency of the reader. 308 313 309 314 · Smargo Smartreader+ … … 311 316 Set the reader frequency with the native Smargo Smartreader+ tool (srp_tools). Do not set mhz and cardmhz. 312 317 313 OSCam tries to set the baudrate automatically. A standard serial port has limited baudrate settings, so SC overclocking might not work. When using a serial reader the best way 314 for overclocking is connecting it to a FTDI based USB to serial port adapter. 315 316 If overclocking does not work, verify the effective baudrate in the logfile. If it deviates too much from the requested baudrate, the SC will not be recognized (no ATR) and the 317 value for mhz should be adjusted again. The higher the baudrate, the more accurate the effective baudrate can be. 318 OSCam tries to set the baudrate automatically. A standard serial port has limited baudrate settings, so SC overclocking might not work. 319 When using a serial reader the best way for overclocking is connecting it to a FTDI based USB to serial port adapter. 320 321 If overclocking does not work, verify the effective baudrate in the logfile. If it deviates too much from the requested baudrate, the SC 322 will not be recognized (no ATR) and the value for mhz should be adjusted again. The higher the baudrate, the more accurate the effective 323 baudrate can be. 318 324 319 325 EXAMPLES … … 430 436 431 437 SEE ALSO 432 list_smargo(1), oscam(1), oscam.ac(5), oscam.cert(5), oscam.conf(5), oscam.dvbapi(5), oscam.guess(5), oscam.ird(5), oscam.provid(5), oscam.services(5), oscam.srvid(5),433 oscam. tiers(5), oscam.user(5)434 435 436 437 438 list_smargo(1), oscam(1), oscam.ac(5), oscam.cert(5), oscam.conf(5), oscam.dvbapi(5), oscam.guess(5), oscam.ird(5), oscam.provid(5), 439 oscam.services(5), oscam.srvid(5), oscam.tiers(5), oscam.user(5) 440 441 442 443 oscam.server(5)
Note:
See TracChangeset
for help on using the changeset viewer.