Multiplexer Driver Developer’s Guide
4.2 Settings Stored in the Windows Registry
s
Table 6: Registry values
Value | Data (Example) | Properties |
|
|
|
ReinitOnDSR | 1 | 0 Default for XC18 |
|
| The driver does not try to reconnect to the module if DSR |
|
| changes. This feature can be switched off if an application |
|
| controls the DSR line with AT&S. |
|
| 1 Default for all modules except XC18 |
|
| The driver tries to reconnect to the module if DSR changes. |
|
| The driver can detect if the module was disconnected and |
|
| reinitializes it before the first data errors occur. |
ClosePort | AT+IPR=0 | A |
(not applicable to | AT^SMSO |
|
TC45 and XC18) |
|
|
ClosePort | AT+IPR=0 | A |
(TC45, XC18 only) |
|
|
PowerDown | AT+CFUN=0 | A |
|
| mode or hibernate state. |
|
| The command AT+CFUN=0 has been chosen as factory |
|
| default for compatibility with older Siemens products. If you |
|
| prefer to use one of the more efficient CYCLIC SLEEP |
|
| modes it can be replaced with AT+CFUN=5 or 6 or 7 or 8 or |
|
| 9. See [3] and [4] to verify the SLEEP mode types supported |
|
| by your product. To avoid editing the Windows Registry you |
|
| can alter the corresponding parameter in the winmux2k.inf |
|
| file and then reinstall the driver. |
ShutDown | AT+IPR=0 | A |
| AT^SMSO | rebooted. |
|
| Note: Some PCs generate a DTR spike during turn off and |
|
| the module wakes up again. |
WaitForDSR | 1 | 0 Default for TC45 and XC18 |
|
| The driver does not wait for the DSR signal to go low when |
|
| the module is shut down. Instead, the parameter Recover- |
|
| Time (see below) is used. |
|
| 1 Default for all modules except TC45 and XC18 |
|
| The driver waits for the DSR signal to go low when the mod- |
|
| ule is shut down. In this case the parameter RecoverTime is |
|
| not used. If the module is not switched off with the AT com- |
|
| mands defined in the parameter ClosePort this parameter |
|
| must be set to 0. |
RecoverTime | 2000 | Minimum number of milliseconds between close and the |
|
| next open call. |
PowerDownFrame | 2 | From version 3 onwards, the Multiplexer Protocol supports |
|
| power saving control with a special multiplex control frame. |
|
| This provides the possibility of sending power down com- |
|
| mands to the module without accessing any data channel. |
|
| If the connected module only supports the Multiplexer Pro- |
|
| tocol version 2 this value is not used. If the supported Multi- |
|
| plexer Protocol version is 3 or higher, the multiplex power |
|
| control is used instead of the values “PowerCmdPort” and |
|
| “PowerDown”. In this case this value corresponds to the |
|
| power down command of the multiplex power down frame |
|
| described in [5]. If the value is greater than 255 there is no |
|
| power down frame sent for Multiplexer Protocol 3. |
|
|
|
Mux_Drv_DevGuide_v07 | Page 22 of 36 | |
Confidential / Released |
|
|