Cinterion
®
EHS6 AT Command Set
1.5 AT Command Syntax
EHS6_ATC_V03.001 15/12/3
Confidential / Released
Page 20 of 513
1.5.2 Concatenating AT Commands
Concatenating AT commands on the same line is possible, though not recommended because of restrictions
listed below (for more details see ITU-T V.250 [16]).
When concatenating AT commands you need to enter the "AT" or "at" prefix only once at the beginning of a com-
mand line. Basic commands (i.e., ITU-T V.250 commands) are concatenated without delimiter. Extended com-
mands (i.e., commands starting with AT+ or AT^) use a semicolon as delimiter.
Disadvantages and restrictions:
• There is no way to control the minimum time to wait between finishing an AT command and sending the next
one. Please refer to Section 1.6, Communication between Customer Application and EHS6 for details about
timing.
• The sequence of processing the AT commands may be different from the sequential order of command input.
• Many AT commands cannot be concatenated (see list below). Concatenating these commands might end up
with an error result code, or leads to an unexpected order of responses.
1.5.3 Application Design Considerations
When designing your application keep in mind that parameters given in AT command responses, result codes
and unsolicited result codes are only separated by commas with no spaces in between. Please take care that
your application ignores any additional spaces that may, nevertheless, be inserted in some AT command
responses, result codes and unsolicited result codes provided by EHS6.
AT command type Comment
3GPP TS 27.007 commands Cannot be concatenated with extended commands
(prefix AT^S)
3GPP TS 27.005 commands (SMS) To be used standalone
Commands starting with AT& To be used standalone
AT+IPR To be used standalone
To Next Page
Loading...
