R
ADIO
B
RIDGE
RBM101
U
SER
G
UIDE
C
OPYRIGHT
©
2017,
R
ADIO
B
RIDGE
I
NC
.
R
ADIO
B
RIDGE
RBM101
U
SER
G
UIDE
P
AGE
9
OF
35
4.2.
Messages from the Module
The messages from the device do not have an “AT” prefix but have the
following structure:
Table 8 Module Messages Structure
Message Type
Space 0x20
Message
Carriage Return 0x0D
3 bytes
1 byte
2-n bytes
1 byte
The message types are one of the following ASCII-coded values:
•
“CMD”: Command Response
•
“ERR”: Error Message
•
“STA”: Status Message
•
“SNF”: Sniffer
•
“APP”: Application Payload
4.2.1.
“C
MD
”: Command Response
Response from a previous AT command. For example, for AT commands that set valid
parameters the host would expect the response:
CMD OK
If the AT command is requesting the firmware version which happens to be v1.01 the
response would be:
CMD 0101
4.2.2.
“
ERR
”:
Error Message
This is an error message from the module that sends a 4-digit error code as ASCII coded hex
characters. For instance, error code 0x0000 would be represented by:
ERR 0000
Some error messages have an associated Device ID, and if this is the case then the error code
would be followed by the Device ID. For example, the status message for an out-of-sequence
message for Device ID 12345678 would be:
ERR 0002 12345678
See the
Error Messages
section for more detail.
4.2.3.
“
STA
”:
Status Message
This is general status message from the module that sends a 4-digit status code as ASCII coded
hex characters. For instance, status message 0x0000 would be represented by:
STA 0000