ME310G1/ME910G1/ML865G1 AT Commands Reference Guide
80617ST10991A Rev.4 Page 22 of 545 2020-04-15
2.2.2.3. Carriage Returns, Line Feeds and Log
Generally, the number of carriage returns <CR> and line feeds <LF> at the end of command responses may
vary. This scenario may also vary from software version to software version. We do not have evidence of this
behavior in URC lines.
Command responses examples:
AT#LWM2MMON?<CR>
<CR><LF>
#LWM2MMON: "4"<LF>#LWM2MMON: "3" missing <CR>
<CR><LF>
<CR><LF>
OK
<CR><LF>
AT#LWM2MFYACKURI=0,2<CR>
<CR><LF>
#LWM2MNFYACKURI: "/3/0/9"<LF>#LWM2MNFYACKURI: "/3/0/8" missing <CR>
<CR><LF>
<CR><LF>
OK
<CR><LF>
The user must be aware of this aspect before writing a script to parse the commands lines and the relative
responses lines to generate a log.
2.2.3. Information Responses and Result Codes
The TA response, in case of verbose response format enabled, for the previous examples command line could
be as shown below:
• information response to +CMD1?
<CR><LF>+CMD1:2,1,10<CR><LF>
• information response to +CMD1=?
<CR><LF>+CMD1(0-2),(0,1),(0-15)<CR><LF>
• result code <CR><LF>OK<CR><LF>
Moreover, there are other two types of result codes:
• result codes that inform about progress of TA operation (e.g. connection establishment CONNECT)
• result codes that indicate occurrence of an event not directly associated with issuance of a command
from TE (e.g. ring indication RING).
Here the basic result codes according to ITU-T V25Ter recommendation