Table 3:
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 command lines
and the relative response 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:
1. information response to +CMD1?
<CR><LF>+CMD1:2,1,10<CR><LF>
2. information response to +CMD1=?
<CR><LF>+CMD1(0-2),(0,1),(0-15)<CR><LF>
3. result code <CR><LF>OK<CR><LF>
Moreover, there are two other types of result codes: