Technical information

Table Of Contents
Appendix B: MUX
January 31, 2007 AT Commands Reference Manual B-7
When a change is made by the G24 to the status of any of the first group of signals in an IDLC, it
sends an MSC frame to the DTE with the new status, as follows:
M_FC, CTS and FC bit - Not supported always on.
RI – When an IDLC receives an incoming call alert, it updates the RI signal value, similar to
what is done in GRLC. The G24 sends the MSC "RI on" frame, followed 1 second later by an
MSC "RI off" frame, followed 4 seconds later by another "RI on" frame. This pattern repeats
until the incoming call alert is halted.
DCD – Each IDLC changes its virtual DCD according to its specific &C setting (like in
GRLC). Upon a change in an IDLC DCD status, the G24 sends the MSC DCD frame. This
change in DCD status may is dependent on a change to an &C value.
CTS – The G24 will NOT change its CTS signal status value in any case. The IDLC CTS
signal value will always be 1 (ON).
DSR – When an IDLC is opened via the SABMi command, the G24 sends an MSC frame to
the DTE. In this MSC frame the DSR bit is set to ON. When an IDLC is closed via the DISCi
command, the G24 sends an MSC frame to the DTE. In this MSC frame, the DSR bit is set to
OFF.
Note: The first MSC frame sent from G24 to a specific IDLC after a SABMi command keeps
its default values, which are: "M_FC on", "RI off", "DCD off", "CTS on" and "FC on".
When a change is made by a DTE-specific IDLC to the status of any of the second group of
signals, it sends an MSC frame to the G24 with the new status, as follows:
D_FC – Not supported.
DTR – The G24 passes on to the relevant IDLC the change in its DTR signal. The IDLC
reacts to the DTR change according to its AT&D setting (like in GRLC). When an IDLC has
its DTR set to OFF, no AT command or data will be conveyed to or from it.
MUX Customer Packet
MUX Customer Open Source Code Packet
Each of the following points represents an API user interface:
Point 1: The RX data is generated by the user ISR. At this point, the data is unpacked and
dispatched to the correct API TS0710_rx_handler_api channel.
Point 2: The MIP either generates or triggers an API function for each
TS0710_DLC_APP_rx_handler_api() channel.
Point 3: The user wants to send data from the API TS0710_application_send_data channel.
Point 4: The MIP either generates or triggers an API function for sending the API
USER_tx_service() frame TX.
Point 5: The Manager is used to close the MUX, open the MUX, and for testing (echo, ping).
Notes: The reception or sending of MSC frames does not affect the G24 hardware RS232
pins.