AirPrime and HL7548 AT Commands Interface Guide Rev10 0

4116303 Rev 10.0 August 10, 2017 18
AT Commands Interface Guide
Introduction
1.2.1. Parameters
In this document, the default parameters are underlined and the optional parameters are enclosed in
square brackets.
Optional parameters or sub-parameters can be omitted unless they are followed by other parameters.
A parameter in the middle of a string can be omitted by replacing it with a comma.
When the parameter is a character string, the string must be enclosed in quotation marks.
All space characters will be ignored when using strings without quotation marks.
1.2.2. Answers and Responses
There is always an answer sent by the TA to an AT Command line (except the very special case of a
TA setup for no answer, see ATQ).
The answer is always terminated by an indication of success or failure. However, regarding the setup
of the TA (by AT Commands), the message may be different.
Classical messages OK or ERROR
Extended Error message (see AT+CMEE) +CME ERROR: <n>
(See Appendix for the different values for <n>)
Numeric Mode (see ATV) <n> with: <n> = 0  OK or <n> is an error code
1.2.3. Multiple AT Commands on the Same Command
Line
You may enter several AT commands on the same line. This eliminates the need to type the "AT" or
"at" prefix before each command and to wait for the answer for each command. The main advantage
is to avoid losing bandwidth on the link between DTE and the Module.
There is no separator between two basic commands but a semi-colon character is necessary between
two extended commands (prefix +). The command line buffer accepts a maximum of 391 characters.
If this number is exceeded none of the commands will be executed and TA returns ERROR.
If a command is not supported, then the treatment of the line is stopped (i.e. the following ones are
not treated) and an error message is returned.
Example:
Command: ATZ&K3+CBST=7,0,1;+CBST?
Answer: +CBST=7,0,1
OK
1.2.4. AT Commands on Separate Lines
When you enter a series of AT commands on separate lines, it is strongly advised to leave a pause
between the preceding and the following command until the final answer (OK or Error message)
appears. This avoids sending too many AT commands at a time without waiting for a response for
each.