Manual

APPENDIXES
Technical Appendixes
© Restricted
Page: 51 / 80
This document is the sole and exclusive property of Wavecom. Not to be distributed or divulged without
prior written agreement.
WM_DEV_OAT_UGD_049 - 001 APPENDIXES August 23, 2007
3.2.1.1 Restrictions
• Only basic option and UIH framing is supported.
• Only convergence layers type 1 and 3 are supported.
• Autobauding is not compatible with multiplex mode. It is neither possible to
start multiplexing when autobauding is active (AT+IPR=0), nor to set
autobauding during multiplex mode, since the multiplexer uses only a fixed
baud rate. In the same way, the bit rate can not be changed through AT+IPR
command while multiplex mode is active. Therefore, AT+IPR=<rate> should
not be used, and will have no effect.
Before starting multiplexing mode, port speed must be configured by
AT+IPR=<rate> command, to be compliant with defined values for <port
_speed> parameter (in the volume 1, refer to "Multiplexing Mode +CMUX"
section, "Parameters and Defined Values" section).
3.2.1.2 Specific Behaviors
• In multiplexing mode, AT configuration commands (as AT+CMEE for example),
(see: [2]§ 1.10) will be applied to all logical channels.
• In multiplexing mode, unsolicited result code (see: [2]§ 1.7) will be transmitted
to all logical channels
• AT commands are grouped by classes (SMS, phonebook, GPRS, SIM TOOL
KIT, … See [2] §3.7.1) and launching an AT command from a port, has for the
effect to lock all commands belonging to the same class.
If another port launches an AT command of the locked class, an +CME ERROR:
536 will occur as long as the class is not released (at first command’s
completion time).
• If Bluetooth is started, it is not possible to start CMUX on UART2.
In the same way, it MUX is started on UART2, it is not possible to start
Bluetooth.
• After an
at+cfun=1 during a CMUX session, CMUX is automatically restarted
by the Wireless CPU
®
with previous parameters, and all previous opened DLCs
are reopened, with the speed of
at+ipr? Command.
• DCD, RI and DTR signals are managed virtually:
When V24 sets DCD,RI or DTR signal, a MSC frame is sent to remote part, to
indicate a virtual state change .Everything is logical, no physical signals are
involved.
• +++ Escape Sequence is always possible to get offline.
• Flow control is managed physically or virtually by MSC.
By default, the Wireless CPU
®
manage a hardware flow control on a UART, and
this flow control becomes virtual on logical channels when some DLCs are
opened.
At CMUX session stop, Wavecom the Wireless CPU
®
automatically goes back into AT
mode, without having to reset the Wireless CPU
®
.
• Two timeouts are implemented for CMUX connection: