OSCam/en/examples/Overclocking: Unterschied zwischen den Versionen
K (Überschriften und Absätze angepasst) |
ValD (Diskussion | Beiträge) (Translated to English.) |
||
Zeile 2: | Zeile 2: | ||
{{OSCamHomeLinks}} | {{OSCamHomeLinks}} | ||
== Overclocking Configuration Example == | |||
=== Dreambox and other internal readers === | |||
For the Dreambox and other internal readers, the maximum clock rate is determined automatically. The '''MHz parameters''' in the <tt>[reader]</tt> section allow you to configure a value higher than the one automatically determined by OSCam, if it is different than 357 and 358. Usually, there should be no value entered for <tt>mhz</tt>. | |||
In certain Dreambox STBs (particularly PPC clones), using the default value for the <tt>mhz</tt> parameter leads to high ECM latency and/or <tt>"not found"</tt> results. By gradually ramping up the frequency, e.g. 200, 300, 400, and so on, up to 1600, you can find what value works well with both the received and the card. The higher the MHz value, the lower the ECM-time (oddly enough;-)). | |||
If the frequency value is too low, the card is not recognized ('''no ATR''' or '''card not supported'''). If the value is too high, the ECM-times will be low. | |||
Experience shows that it's best to either leave out the <tt>mhz</tt> line or use <tt>mhz = 1000</tt>. | |||
=== easymouse2 Reader === | === easymouse2 Reader === | ||
==== | ==== Example configuration S02 ==== | ||
Dip switch: | |||
1. Dip = | 1. Dip = bottom (5 Volt) | ||
2. Dip = | 2. Dip = bottom (Phoenix) | ||
3. Dip = | 3. Dip = top ---> Settings in Dip 4! | ||
4. Dip = 10 MHz | 4. Dip = 10 MHz | ||
Zeile 40: | Zeile 39: | ||
=== Phoenix/Smartmouse Reader === | === Phoenix/Smartmouse Reader === | ||
Overclocking | Overclocking does not work under Windows and Mac OS X. Settings are right on the reader (usually dip-switch). OSCam itself should work in this case, no frequencies! | ||
=== Smargo Smartreader+ === | === Smargo Smartreader+ === | ||
Set the frequencies with the Smargo Smartreader+ Tool (srp_tools). Don't configure <tt>mhz</tt> and <tt>cardmhz</tt> parameters. | |||
=== | === Baud Rates === | ||
OSCam | OSCam tries to set the baud rate automatically. In a '''standard Serial Port''', the baud rate options are limited, so that overclocking might not work. Therefore, when using Serial readers the best way to Overclocking is by connecting the reader through a '''FTDI USB to serial port adapter'''. | ||
If overclocking is not working, the effective baud rate should be determined in the logfile. If it differs too much from the required baud rate, the card is not recognized ('''no ATR'''). If that happens, the value should be adjusted through the <tt>mhz</tt> parameter again. The higher the baud rate, the better it will work. | |||
{{OSCamTranslatedLinks}} | {{OSCamTranslatedLinks}} |
Version vom 17. März 2011, 11:15 Uhr
OSCam Übersicht OSCam Home OSCam Accueil OSCam Home
Overclocking Configuration Example
Dreambox and other internal readers
For the Dreambox and other internal readers, the maximum clock rate is determined automatically. The MHz parameters in the [reader] section allow you to configure a value higher than the one automatically determined by OSCam, if it is different than 357 and 358. Usually, there should be no value entered for mhz.
In certain Dreambox STBs (particularly PPC clones), using the default value for the mhz parameter leads to high ECM latency and/or "not found" results. By gradually ramping up the frequency, e.g. 200, 300, 400, and so on, up to 1600, you can find what value works well with both the received and the card. The higher the MHz value, the lower the ECM-time (oddly enough;-)).
If the frequency value is too low, the card is not recognized (no ATR or card not supported). If the value is too high, the ECM-times will be low. Experience shows that it's best to either leave out the mhz line or use mhz = 1000.
easymouse2 Reader
Example configuration S02
Dip switch:
1. Dip = bottom (5 Volt) 2. Dip = bottom (Phoenix) 3. Dip = top ---> Settings in Dip 4! 4. Dip = 10 MHz
Configuration Reader:
[reader] label = mymouse enable = 1 protocol = mouse device = /dev/ttyUSB0 services = skywelt,skyweltextra,skyfilm caid = 1702 force_irdeto = 1 boxkey = 1122334455667788 detect = cd mhz = 1000 cardmhz = 600 ident = group = 1,2,3 emmcache = 1,3,2 blockemm-unknown = 1 lb_weight = 100
Phoenix/Smartmouse Reader
Overclocking does not work under Windows and Mac OS X. Settings are right on the reader (usually dip-switch). OSCam itself should work in this case, no frequencies!
Smargo Smartreader+
Set the frequencies with the Smargo Smartreader+ Tool (srp_tools). Don't configure mhz and cardmhz parameters.
Baud Rates
OSCam tries to set the baud rate automatically. In a standard Serial Port, the baud rate options are limited, so that overclocking might not work. Therefore, when using Serial readers the best way to Overclocking is by connecting the reader through a FTDI USB to serial port adapter.
If overclocking is not working, the effective baud rate should be determined in the logfile. If it differs too much from the required baud rate, the card is not recognized (no ATR). If that happens, the value should be adjusted through the mhz parameter again. The higher the baud rate, the better it will work.
Diese Seite in anderen Sprachen - This page in other languages - Cette page dans d'autres langues - Queste pagine in altre Lingue
[[OSCam/de/{{#titleparts:OSCam/en/examples/Overclocking|3|3}}|Deutsch]] [[OSCam/en/{{#titleparts:OSCam/en/examples/Overclocking|3|3}}|English]] [[OSCam/fr/{{#titleparts:OSCam/en/examples/Overclocking|3|3}}|Français]] [[OSCam/it/{{#titleparts:OSCam/en/examples/Overclocking|3|3}}|Italiano]]