Rainbow Electronics MG260 - Manual (Page 239)

FLYFOT-MG260-MODULE
Page: 239 / 246
This document is the sole and exclusive property of FLYFOT. Not to be distributed or divulged without
prior written agreement.
message class applies.
Cause no 96: "Invalid mandatory information"
This cause indicates that the equipment sending this cause has received a message where a
mandatory information element is missing and/or has a content error (the two cases are
undistinguishable).
Cause no 97: "Message type non-existent or not implemented"
This cause indicates that the equipment sending this cause has received a message with a
message type it does not recognize either because this is a message not defined or defined but not
implemented by the equipment sending this cause.
Cause no 98: "Message not compatible with short message protocol state"
This cause indicates that the equipment sending this cause has received a message such that the
procedures do not indicate that this is a permissible message to receive while in the short
message transfer state.
Cause no 99: "Information element non-existent or not implemented"
This cause indicates that the equipment sending this cause has received a message which includes
unrecognized information elements because the information element identifier is not defined or it
is defined but not implemented by the equipment sending the cause. However, the information
element is not required to be present in the message so that the equipment sends the cause to
process the message.
Cause no 111: "Protocol error, unspecified"
This cause is used to report a protocol error event only when no other cause applies.
Cause no 127: "Interworking, unspecified"
This cause indicates that there has been interworking with a network which does not provide causes
for actions it takes; thus, the precise cause for a message which is being sent cannot be ascertained.
All values other than specified should be treated as error Cause No 41
19.7 Data / Commands multiplexing protocol
Introduction
The MG260 multiplexing protocol operates between a DCE (Data Communication Equipment: the
product) and a DTE (Data Terminal Equipment). It allows a double session over a serial link interface：
one for AT commands and one for DATA communications.
In Multiplexing Mode, AT commands and
DATA are encapsulated into packets. The header of these packets allows to recognize whether it is a
DATA packet or an AT command packet.
AT+WMUX=1 activates the Multiplexing Mode. With this mode, AT commands and DATA are
encapsulated into packets. The header of these packets allows to recognize whether it is a DATA
packet or an AT command packet. AT+WMUX=0 deactivates the Multiplexing Mode and gets the
product back to the default mode.
AT command packets
An AT command is encapsulated into a packet with a header which allows to separate it from DATA
packets. This packet is formed by a header (3 bytes), the AT command itself and a checksum (1 byte) :