Siemens 7 - Manual (Page 15)

Multiplexer Driver Developer’s Guide
2.6 Module Initializing Sequence
s
Mux_Drv_DevGuide_v07 Page 15 of 36 2006-9-27
Confidential / Released
2.6 Module Initializing Sequence
Due to different requirements of the supported products the initialization sequence varies with the module type.
This means that when you migrate to another module type you are required to uninstall the driver and reinstall it
with the new module. The settings are taken from the winmux2k.inf file.
The tables below list the commands sent to the module during the initialization. As the init string information is
stored in the Windows Registry the corresponding values are also listed. For further details on the Registry see
Section 4.2 .
Note: The initialization sequence overrides the user profile settings defined with AT&W on channel 1 for the com-
mands AT&S, AT\Qn and AT+ICF. After restart without multiplexer, the user profile will be loaded with all your
individual settings.
Table 4: Module initialization of supported modules
Command Response Function Associated Registry
value
AT OK Detection of connected module.
AT+IPR=115200 OK Baud rate specified in the Windows
Registry during WinMux2k installation.
The value may be different according to
individual settings. “BaudRateString”
AT OK Check if change of baud rate was suc-
cessful. “ModemInit”
AT&S0\Q3 OK Sets DSR always on and hardware flow
control. The settings are read from the
Windows Registry. “ModemInit”
AT+ICF=3 OK/ERROR Sets interface mode 8N1. This com-
mand works only on modules support-
ing different interface modes (TC35i,
TC63, TC65, MC75, AC75). The set-
tings are read from the Windows Regis-
try.
The resulting ERROR on modules with-
out support of the AT+ICF command is
ignored by the WinMux2k driver.
“ModemInit”
AT+CMUX=0 OK Switches to multiplexer mode. This
sequence is read from the Windows
Registry. More AT commands can be
sent to the module at this point. “ModemInit”