SARA-R4/N4 series-AT Commands Manual
UBX-17003787 - R09

1AT command settings
Page 14 of 307
Verbose Numeric Result code type Description
In case of data/fax call, see Circuit 108/2, +++ behaviour for the
different &D: summarizing table to return in command mode
and disconnect the call.
Command aborted 3000 Final Command execution aborted issuing a character to the DCE
Table 1: Allowed result codes
SARA-R4 / SARA-N4
The AT commands can not be aborted, except if explicitly stated in the corresponding AT command
description.
Intermediate outputs as well as descriptive outputs of a command are formatted as information text
responses; if more than one string has to be printed out (see for example the +CGDCONT command
description), additional command line termination and linefeed characters may be inserted for sake of
readability.
If the command is not accepted by the MT an error result code will be displayed. The AT+CMEE command
configures the error result code format as follows:
• "+CMS ERROR: <err>" for SMS-related AT commands
• "+CME ERROR: <err>" for any other AT commands
where <err> represents the verbose or numeric error result code depending on the +CMEE AT command
setting.
The most typical error result codes are the following:
• If the command is not supported or unknown, either "+CME ERROR: unknown" or "+CME ERROR: operation
not supported" is sent
• If the command syntax is wrong, "+CME ERROR: operation not supported" is sent ("+CMS ERROR: operation
not supported" for SMS related commands)
The list of all the possible error result codes is available in Appendix A.1 and Appendix A.2. For some commands
only the "ERROR" final result code is displayed and is documented in the command description.
The proprietary AT commands supporting the following features implement a different error
management and provide different error result codes:
• Firmware update Over AT command and over the air: see the Appendix A.3 and Appendix A.4
• TCP and UDP connections, FTP and HTTP: see the Appendix A.5, Appendix A.6, Appendix A.6.1,
Appendix A.6.2
The corresponding sections provide more details for retrieving the error result codes for these operations.
1.2î™–î™–î™–î™–Storing of AT commands setting
Several user settings may be stored in the cellular module's memory. Some are directly stored in the non volatile
memory (NVM), while the others are organized into two personal profiles. The first profile is the default profile,
whose data is by default loaded during the module's power on.
Appendix B.2 lists the complete settings that can be directly stored in NVM and the corresponding commands.
Appendix B.1 lists the complete settings stored in the profiles and the corresponding commands.
SARA-R4 / SARA-N4
The module does not store the AT commands setting in the profiles.
1.3î™–î™–î™–î™–S-parameters
The S-parameters, as specified in ITU-T recommendation V250 [20], constitute a group of commands that
begin with the string "ATS". They are generally indicated as S registers and are used to configure the way the
module operates. Their syntax is:
ATS<parameter_number>?
ATS<parameter_number>=<value>
The number following the "ATS" is the referenced S parameter.
u-blox cellular modules support the following set of S-parameters (<parameter_number>):
To Next Page
Loading...
Need help?
General
