OSCam/en/examples/Overclocking: Unterschied zwischen den Versionen

Aus Streamboard Wiki
Zur Navigation springen Zur Suche springen
(Translated to English.)
K (Rephrased some.)
Zeile 4: Zeile 4:
== Overclocking Configuration Example ==
== Overclocking Configuration Example ==
=== Dreambox and other internal readers ===
=== 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>.
For Dreambox and other internal readers the highest possible clock rate will be auto detected. The <tt>mhz</tt> parameter lets you override the values chosen by OSCam, if it differs from 357 and 358, but usually you will not set any value 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;-)).
For certain Dreamboxes (especially PPC clones) the default <tt>mhz</tt> parameter leads to slow ECM times and/or "not found" ECMs. By setting <tt>mhz</tt> to values like 200, 300, 400, ... 1600, you can find a value that works for your receiver and your card. The higher the<tt>mhz</tt> value, the slower the ECM time (strange 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.
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 either no <tt>mhz</tt> line, or a line <tt>mhz = 1000</tt> works best.
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 ===
Zeile 39: Zeile 38:


=== Phoenix/Smartmouse Reader ===
=== 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!
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.


=== 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.
Set the reader frequency with the native Smargo Smartreader+ tool (srp_tools). Do not set <tt>mhz</tt> and <tt>cardmhz</tt>.


=== Baud Rates ===
=== 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'''.
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 for overclocking is connecting it to a '''FTDI based 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.


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 value for <tt>mhz</tt> should be adjusted again.  The higher the baudrate, the more accurate the effective baudrate can be.


{{OSCamTranslatedLinks}}
{{OSCamTranslatedLinks}}

Version vom 20. März 2011, 10:27 Uhr

OSCam Übersicht OSCam Home OSCam Accueil OSCam Home

Overclocking Configuration Example

Dreambox and other internal readers

For Dreambox and other internal readers the highest possible clock rate will be auto detected. The mhz parameter lets you override the values chosen by OSCam, if it differs from 357 and 358, but usually you will not set any value for mhz.

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, you can find a value that works for your receiver and your card. The higher themhz value, the slower the ECM time (strange enough).

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 either no mhz line, or a line mhz = 1000 works best.

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 with Windows and Mac OS X. Set mhz equivalent to the frequency of the reader. OSCam can not set the frequency of the reader.

Smargo Smartreader+

Set the reader frequency with the native Smargo Smartreader+ tool (srp_tools). Do not set mhz and cardmhz.

Baud Rates

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 for overclocking is connecting it to a FTDI based USB to serial port adapter.

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 value for mhz should be adjusted again. The higher the baudrate, the more accurate the effective baudrate can be.

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]]

Abgerufen von „http://wiki.streamboard.tv/index.php?title=OSCam/en/examples/Overclocking&oldid=6178“