Quectel BG96 - EMQ Unsolicited Response Codes (Urcs)

+EMQ Unsolicited Response Codes (URCs)
When AWS publishes data to your thing, the ETM application forwards the data through the AT
command interface using an appropriate URC.
If the data buffer contains only printable characters, it is presented unmodified. This makes transfer of
JSON and ASCII text transparent. If non-printable characters are contained in the buffer, the entire
buffer is converted to ASCII-hex and sent within quotes.
URC Description
+EMQ:<S>,<len>\r\n<data>
or
+EMQ:<id>,<len>\r\n<data>
Indicates data received on a subscribed topic, where:
•
S is for singletopic only. Indicates data received on a
single topic, in ASCII-hex format. For information about
singletopic, see EMQ – publish a message to singletopic
on page45.
•
<id> is the subscribed topic index number, not for
singletopic use
•
<len> is the length of the incoming data
•
<data> is the received data in either ASCII-hex format or
as text, depending on both the urcautoformat setting
in the configuration file, and if <data> appears within
quotes.
For example, if the urcautoformat setting = 1, then:
•
<id>,<len>\r\n"<data>" reports data in
ASCII-hex format
•
<id>,<len>\r\n<data> reports data in text
format
For more information, see Using the Quectel BG96
module configuration file on page62.
+EMQPERSIST:<len>
<JSON>
Reports a message from the cloud service indicating something
in the persistence service has changed.
For simple AWSSHADOW mode, only the '{"state":{...'
parameters that have changed in the AWSdelta are listed.
For example:
+EMQPERSIST:{"key1":"value1","key2":"value2"}
where value1 and value2 are any type of value, including
strings, integers, decimals and negative numbers.
For complete AWSSHADOW mode, the entire JSON is listed.
For example:
55
Eseye-enabled Quectel BG96 module Developer Guide v1.8
MQTT telemetry ATcommands