Multiplexer Driver Developer’s Guide
4.2 Settings Stored in the Windows Registry
s
Table 6: Registry values
Value | Data (Example) | Properties |
|
|
|
Optional values supported as of Multiplexer Protocol version 4, i.e. supported by the WinMux2k driver version 3.000 or later.
The following optional values can be manually added to the Registry when needed.
MaxMuxVersion | 3 | This registry value provides the possibility to force the driver |
|
| to use a lower multiplex protocol version than the maximum |
|
| supported. The multiplex protocol has been improved con- |
|
| tinuously by adding several features. The multiplex protocol |
|
| version is negotiated with the connected module during mul- |
|
| tiplex startup. It is used to ensure compatibility between dif- |
|
| ferent multiplex driver and module generations. The registry |
|
| value isn’t mandatory, by default the WinMux driver uses |
|
| always the latest protocol implementation with all available |
|
| features. If for some reason an older multiplex protocol shall |
|
| be used it can be controlled with that registry value. For fur- |
|
| ther information about the multiplex protocol versions refer |
|
| to the “Multiplexer User’s Guide”. |
HdlcWindowSize | 4 | Modules with multiplex protocol version 4 and above use a |
|
| kind of HDLC framing to secure the data transmission on the |
|
| virtual ports and avoid data loss at high transfer rates and |
|
| much data traffic. This registry value provides the possibility |
|
| to adjust the size of the HDLC window which defines the |
|
| maximal number of outstanding HDLC packets. It can be |
|
| between 2 and 7. |
|
| This Registry value is not mandatory. If it is not added to the |
|
| Registry the value 4 will be assumed by default. Please note |
|
| that the value is negotiated with the module. |
|
|
|
Mux_Drv_DevGuide_v07 | Page 23 of 36 | |
Confidential / Released |
|
|
