Mux Customer Packet; Mux Customer Open Source Code Packet - Motorola G24 Guide Developer's Manual

At commands
Hide thumbs Also See for G24 Guide:
Table of Contents

Advertisement

A change in the status of the first group of signals can be made only by the G24. A change in the
status of the second group of signals can be made by a specific channel in DTE (IDLC).
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:
CTS - 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.
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.
M_FC - When G24 is ready and able to receive data, it updates the "FC" value and sends the
MSC "FC on" frame. When G24 is not able to receive data, it sets the "FC" bit and sends the
MSC "FC off" frame.
Note:
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:
RTS - Not supported, always on.
D_FC - When an IDLC is ready and able to receive data, it updates the "FC" value and sends
the MSC "FC on" frame. When an IDLC is not able to receive data, it sets the "FC" bit and
sends the MSC "FC off" frame.
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.
Note:

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).
December 31, 2007
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" and "CTS on".
The reception or sending of MSC frames does not affect the G24 hardware RS232 pins.
AT Commands Reference Manual
Appendix B: MUX
B-7

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents