AirPrime - Extended at Commands Manual - Rev5.0
AirPrime - Extended at Commands Manual - Rev5.0
AirPrime
4115730
5.0
March 26, 2015
Extended AT Commands Manual Overview
Important Notice
Due to the nature of wireless communications, transmission and reception of data can never be
guaranteed. Data may be delayed, corrupted (i.e., have errors) or be totally lost. Although significant
delays or losses of data are rare when wireless devices such as the Sierra Wireless modem are used
in a normal manner with a well-constructed network, the Sierra Wireless modem should not be used
in situations where failure to transmit or receive data could result in damage of any kind to the user or
any other party, including but not limited to personal injury, death, or loss of property. Sierra Wireless
accepts no responsibility for damages of any kind resulting from delays or errors in data transmitted or
received using the Sierra Wireless modem, or for failure of the Sierra Wireless modem to transmit or
receive such data.
The driver or operator of any vehicle should not operate the Sierra Wireless modem while in control of
a vehicle. Doing so will detract from the driver or operator’s control and operation of that vehicle. In
some states and provinces, operating such communications devices while in control of a vehicle is an
offence.
Limitations of Liability
This manual is provided “as is”. Sierra Wireless makes no warranties of any kind, either expressed or
implied, including any implied warranties of merchantability, fitness for a particular purpose, or
noninfringement. The recipient of the manual shall endorse all risks arising from its use.
The information in this manual is subject to change without notice and does not represent a
commitment on the part of Sierra Wireless. SIERRA WIRELESS AND ITS AFFILIATES
SPECIFICALLY DISCLAIM LIABILITY FOR ANY AND ALL DIRECT, INDIRECT, SPECIAL,
GENERAL, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES INCLUDING,
BUT NOT LIMITED TO, LOSS OF PROFITS OR REVENUE OR ANTICIPATED PROFITS OR
REVENUE ARISING OUT OF THE USE OR INABILITY TO USE ANY SIERRA WIRELESS
PRODUCT, EVEN IF SIERRA WIRELESS AND/OR ITS AFFILIATES HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES OR THEY ARE FORESEEABLE OR FOR CLAIMS BY ANY
THIRD PARTY.
Notwithstanding the foregoing, in no event shall Sierra Wireless and/or its affiliates aggregate liability
arising under or in connection with the Sierra Wireless product, regardless of the number of events,
occurrences, or claims giving rise to liability, be in excess of the price paid by the purchaser for the
Sierra Wireless product.
Customer understands that Sierra Wireless is not providing cellular or GPS (including A-GPS)
services. These services are provided by a third party and should be purchased directly by the
Customer.
Patents
This product may contain technology developed by or for Sierra Wireless Inc.
This product includes technology licensed from QUALCOMM®.
This product is manufactured or sold by Sierra Wireless Inc. or its affiliates under one or more patents
licensed from InterDigital Group and MMP Portfolio Licensing.
Copyright
© 2015 Sierra Wireless. All rights reserved.
Trademarks
Sierra Wireless®, AirPrime®, AirLink®, AirVantage®, WISMO®, ALEOS® and the Sierra Wireless and
Open AT logos are registered trademarks of Sierra Wireless, Inc. or one of its subsidiaries.
Watcher® is a registered trademark of Netgear, Inc., used under license.
Windows® and Windows Vista® are registered trademarks of Microsoft Corporation.
Macintosh® and Mac OS X® are registered trademarks of Apple Inc., registered in the U.S. and other
countries.
QUALCOMM® is a registered trademark of QUALCOMM Incorporated. Used under license.
Other trademarks are the property of their respective owners.
Contact Information
Phone: 1-604-232-1488
Sales Desk: Hours: 8:00 AM to 5:00 PM Pacific Time
Contact: http://www.sierrawireless.com/sales
Sierra Wireless
13811 Wireless Way
Post:
Richmond, BC
Canada V6V 3A4
Technical Support: [email protected]
RMA Support: [email protected]
Fax: 1-604-231-1109
Web: http://www.sierrawireless.com/
Consult our website for up-to-date product descriptions, documentation, application notes, firmware
upgrades, troubleshooting tips, and press releases: www.sierrawireless.com
Document History
Version Date Updates
The AirPrime embedded modules to which the manual applies are the following:
Q2698
SL3010T
SL8080T
SL8082T
SL8084T
Embedded module
External AT
Application
Send AT command
Serial Link
Receive AT response
1.4.1. Abbreviations
Abbreviation Definition
Abbreviation Definition
Abbreviation Definition
Abbreviation Definition
1.4.2. Definitions
The words "Mobile Station" (MS) or "Mobile Equipment" (ME) are used for mobile terminals
supporting GSM/GPRS services.
Terminal Equipment is the Man-Machine Interface of a GSM/GPRS device (modem or handset). A TE
can be a handset MMI or the AT command line interface.
User TE ME
A call from a GSM/GPRS mobile station to the PSTN is called a "mobile originated call" (MOC) or
"outgoing call", and a call from a fixed network to a GSM/GPRS mobile station is called a "mobile
terminated call" (MTC) or "incoming call"
In this document, the word "product" refers to any Sierra Wireless product supporting the AT
commands interface.
SL808xT (SL8080T,
Description Q2698 SL3010T
SL8082T, SL8084T)
General Configuration
IP Protocol Services
Ping Services
AT Command Reference
+GPSHELP F F F
+GPSNMEA P P P
SL808xT (SL8080T,
Description Q2698 SL3010T
SL8082T, SL8084T)
+GPSPVT N N N
+GPSSAVE F F F
+GPSSTART F F F
+GPSSTATE F F F
+GPSINIT P P P
+GPSSTOP F F F
+GPSSLEEP P P P
+GPSTTFF F F F
+GPSRELEASE F F F
+GPSVERS F F F
+GPSCONF P P P
+GPSDEBUG N N N
+GPSAID P P P
+GPSCORE N N N
Security Commands
+SSLINIT F F F
+SSLSET F F F
+SSLSETOPTS F F F
+SSLRELEASE F F F
+SSLSTATE F F F
+SSLBOOST F F F
+SSLVERSION F F F
SL808xT (SL8080T,
Description Q2698 SL3010T
SL8082T, SL8084T)
Audio Commands
+AUDIOINIT F N N
+AUDIOEXIT F N N
+AUDIOFILE F N N
+AUDIOCONVERT F N N
+INBMINIT F N N
+INBMEXIT F N N
+INBMGETVER F N N
+INBMSTATE F N N
+INBMOPEN F N N
+INBMCLOSE F N N
+INBMCHSTATE F N N
+INBMSETMSD F N N
+INBMPUSH F N N
+INBMMSDFORMAT F N N
+INBMTIMERCFG F N N
SL808xT (SL8080T,
Description Q2698 SL3010T
SL8082T, SL8084T)
CECALL functionality
+CECALLINIT F N N
+CECALL F N N
+ECALLINIT F N N
+ECALLCFG F N N
+ECALLSETMSD F N N
+ECALLCANCEL F N N
+ECALLRELEASE F N N
+ECALLGETSTATE F N N
+ECALLVERSION F N N
AT Commands
+ERAGINIT F N N
+ERAGSETERA F N N
+ERAGCALL F N N
+ERAGSETMSD F N N
+ERAGCALLCANCEL F N N
+ERAGRELEASE F N N
+ERAGGETSTATE F N N
+ERAGVERSION F N N
+ERAGOPTDATA F N N
Asynchronous Events
+ERAGEV F N N
+ERAGMSD F N N
+ERAGERROR F N N
SL808xT (SL8080T,
Description Q2698 SL3010T
SL8082T, SL8084T)
+FSINIT F N N
+FSEXIT F N N
+FS F N N
3.1.1.1. Description
The +WIPCFG command is used for performing the following operations:
start TCP/IP stack
stop TCP/IP stack
configuring TCP/IP stack
displaying version information
3.1.1.2. Syntax
if<mode>=0,1
Action Command
AT+WIPCFG=<mode>
OK
if <mode>=2
Action Command
AT+WIPCFG=<mode>,<opt num>,<value>
OK
if <mode>=3
Action Command
AT+WIPCFG=<mode>
WIPsoft vXX.YY.ZZ on Open AT OS vA.B
MMM-DDD-YYYY HH:MM:SS <WIPlib: version number> <WIPsoft: version number>
OK
if <mode>=4
Action Command
AT+WIPCFG=<mode>,<action>
OK
Read Command
AT+WIPCFG?
+WIPCFG: <optnum>,<value>
[+WIPCFG: <optnum>,<value>[..]]
OK
Test Command
AT+WIPCFG=?
OK
The IP protocol provides a facility for the Internet layer to know about the various
tradeoffs that should be made for a particular packet. This is required because paths
through the Internet vary widely in terms of the quality of service provided. This facility
is defined as the "Type of Service" facility, abbreviated as the "TOS facility".
The TOS facility is one of the features of the Type of Service octet in the IP datagram
header. The Type of Service octet consists of following three fields:
0 1 2 3 4 5 6 7
+-----+-----+-----+-----+-----+-----+-----+-----+
| | | |
| PRECEDENCE | TOS | MBZ |
| | | |
+-----+-----+-----+-----+-----+-----+-----+-----+
command). It allows the application to buffer a certain amount of data before writing on
IP network side.
Each unit in the range represents 100 msec. For example, value 10 for this option will
give a wait time of 1sec (10*100msec).
Default value for AT_WIP_NET_OPT_PREF_TIMEOUT_VALUE option is 0. This value
means that no specific process is done to avoid TCP packets segmentation: data are
written onto IP network without any delay after the reception of data from the mapped
UART/serial port (please see +WIPDATA AT command). In this case some TCP
packets sent on the IP network may be smaller than TCP_MIN_MSS value.
Setting e.g. a 10 value for this option will make the application to wait at least 1 second
or twice the TCP_MIN_MSS value to be reached before sending data on IP network. In
this case, TCP packets size sent on the IP network should be equal to at least
TCP_MIN_MSS (Default value = 536 bytes).
range: 0- 100 (default value: 0)
13 AT_WIP_NET_OPT_ESC_SEQ_NOT_SENT : Used to configure whether a “+++”
escape sequence should be sent as data to the peer. By default, this option is set to 0
which means that the “+++”sequence is sent to the peer as data. If set to 1,
“+++”sequence is not sent as data to the peer.
range: 0 -1(default value:0)
14 AT_WIP_NET_OPT_AUTO_SWITCH - Used for TCP socket, to switch back
automatically to AT command mode when the TCP connection is closed by peer entity
0: Does not switch automatically to AT mode
1: Switches automatically to AT mode
range: 0-1 (default value:0)
15 Set DATA offline (+WIPDATARW) RX and TX buffer size in bytes
range : 1 – 32000 (default value 2048)
16 WIP_NET_OPT_TCP_REXMT_MAX – Maximum timeout of TCP packets; the
maximum time between TCP retransmissions
range: 1 - 64 (default value:64 seconds)
17 WIP_NET_OPT_TCP_REXMT_MAXCNT - Max number of TCP packet retransmissions
range: 1 - 12 (default value:12)
20 AT_WIP_NET_OPT_TCP_NOTIMEWAIT : Enables or Disables WIPLIB option
WIP_NET_OPT_TCP_NOTIMEWAIT.
0: Set WIPLIB Option WIP_NET_OPT_TCP_NOTIMEWAIT to FALSE
1: Set WIPLIB Option WIP_NET_OPT_TCP_NOTIMEWAIT to TRUE
range: 0-1 (default value:0)
21 WIP_NET_OPT_IP_FORWARD - Activate IP forwarding in NET.
Default value : FALSE
22 WIP_NET_OPT_DHCPS_ADDR - Listening address of the DHCP server.
Default value : 0.0.0.0
23 WIP_NET_OPT_DHCPS_NB_ADDR - Number of IP addresses of the range managed
by the server.
Default value : 1
24 WIP_NET_OPT_DHCPS_FIRST_ADDR - First IP address of the range managed by
the server.
Default value : 0.0.0.0
25 WIP_NET_OPT_DHCPS_SUBNET_MASK - Mask of the subnet managed by the
server.
Default value : 0.0.0.0
26 WIP_NET_OPT_DHCPS_LEASE - Lease time for IP address (in seconds).
Default value : 500
27 WIP_NET_OPT_DHCPS_MAX_LEASE- Maximum lease time for IP address (in
seconds).
Default value : 125000
28 WIP_NET_OPT_DHCPS - Activate DHCP server in NET. Valid configuration
parameters must be set up before activation.
Note: (WIP_NET_OPT_SOCK_MAX + 1) sockets are reserved when UDP sockets are created (and not for
TCP sockets); one socket buffer is added to support/afford DNS accesses
Note: For <opt num> numbers 6 through 11, the AT+WIPS command must be issued. For complete details
regarding AT+WIPS, please refer the Firmware AT Commands Interface Manual.
3.1.1.6. Examples
Command Responses
AT+WIPCFG=1
OK
Note: Start IP Stack
+WIPCFG: 0,64
+WIPCFG: 1,0
+WIPCFG: 2,60
+WIPCFG: 3,0
+WIPCFG: 4,536
+WIPCFG: 5,0
+WIPCFG: 6,8
+WIPCFG: 7,32
+WIPCFG: 8,0
+WIPCFG: 9,0
+WIPCFG: 10,4
AT+WIPCFG?
+WIPCFG: 11,4
+WIPCFG: 12,10
+WIPCFG: 13,0
+WIPCFG: 14,0
+WIPCFG: 15,2048
+WIPCFG: 16,64
+WIPCFG: 17,12
+WIPCFG: 18,80
+WIPCFG: 20,0
OK
Command Responses
+WIPCFG: 0,64
+WIPCFG: 1,0
+WIPCFG: 2,60
+WIPCFG: 3,0
+WIPCFG: 4,536
+WIPCFG: 5,0
+WIPCFG: 6,20
+WIPCFG: 7,32
+WIPCFG: 8,0
+WIPCFG: 9,0
+WIPCFG: 10,4
+WIPCFG: 11,4
+WIPCFG: 12,0
+WIPCFG: 13,0
+WIPCFG: 14,0
+WIPCFG: 15,2048
AT+WIPCFG?
Note: response for an SL8 RD module
+WIPCFG: 16,64
+WIPCFG: 17,12
+WIPCFG: 18,80
+WIPCFG: 20,0
+WIPCFG: 22,0.0.0.0
+WIPCFG: 23,1
+WIPCFG: 24,0.0.0.0
+WIPCFG: 25,0.0.0.0
+WIPCFG: 26,500
+WIPCFG: 27,125000
+WIPCFG: 28,0
+WIPCFG: 29,0
+WIPCFG: 30,0.0.0.0
+WIPCFG: 31,0.0.0.0
+WIPCFG: 32,0.0.0.0
OK
AT+WIPCFG=2,0,10
OK
Note: Configure TTL of IP Stack
Command Responses
+WIPCFG: 0,10
+WIPCFG: 1,0
+WIPCFG: 2,60
+WIPCFG: 3,0
+WIPCFG: 4,536
+WIPCFG: 5,0
+WIPCFG: 6,8
+WIPCFG: 7,32
+WIPCFG: 8,0
+WIPCFG: 9,0
+WIPCFG: 10,4
AT+WIPCFG?
+WIPCFG: 11,4
+WIPCFG: 12,10
+WIPCFG: 13,0
+WIPCFG: 14,0
+WIPCFG: 15,2048
+WIPCFG: 16,64
+WIPCFG: 17,12
+WIPCFG: 18,80
+WIPCFG: 20,0
OK
AT+WIPCFG=0
OK
Note: Stop the TCP/IP Stack
AT+WIPCFG=4,1
Note: Store IP configuration parameters into OK
FLASH
AT+WIPCFG=4,0
Note: Free IP configuration parameters stored in OK
FLASH
3.1.1.7. Notes
It is recommended to change the default settings of the Internet Library stack using +WIPCFG only
when it is required. Changing the parameter values especially the max number of sockets and the
max TCP buffer size with the high values lead to over consumption of the stack memory which causes
the Internet Application to crash. Hence, care must be taken when the default settings of the stack is
changed using +WIPCFG command.
Following option values set by +WIPCFG command are taken into consideration at the run time. The
below option values except for AT_WIP_NET_OPT_PREF_TIMEOUT_VALUE and
AT_WIP_NET_OPT_ESC_SEQ_NOT_SENT will be taken into consideration at next start up only if
these are saved in the flash before stopping the stack.
WIP_NET_OPT_IP_TTL
WIP_NET_OPT_IP_TOS
WIP_NET_OPT_IP_FRAG_TIMEO
WIP_NET_OPT_TCP_MAXINITWIN
WIP_NET_OPT_TCP_MIN_MSS
WIP_NET_OPT_DEBUG_PORT
AT_WIP_NET_OPT_PREF_TIMEOUT_VALUE
AT_WIP_NET_OPT_ESC_SEQ_NOT_SENT
AT_WIP_NET_OPT_TCP_NOTIMEWAIT
AT_WIP_NET_OPT_AUTO_SWITCH
3.1.2.1. Description
The +WIPBR command can be used to
select the bearer
start/open/close/stop the bearer
configure different bearer options such as access point name
3.1.2.2. Syntax
if <cmdtype>=0,1 or 5
Action Command
AT+WIPBR=<cmdtype>,<bid>
OK
if <cmdtype>=2
Action Command
AT+WIPBR=<cmdtype>,<bid>,<opt num>,<value>
OK
if <cmdtype>=3
Action Command
AT+WIPBR=<cmdtype>,<bid>,<opt num>
+WIPBR: <bid>,<opt num>,<value>
OK
if <cmdtype>=4
Action Command
AT+WIPBR=<cmdtype>,<bid>,<mode>[,<login>,<password>,[<caller
identity>]]
OK
if <cmdtype>=6
Action Command
AT+WIPBR=<cmdtype>,<bid>,<mode>
OK
Read Command
AT+WIPBR?
<bid>,<state>
[<bid>,<state>[..]]
OK
Test Command
AT+WIPBR=?
OK
if <mode>=1
Unsolicited response
+WIPBR: <bid>,<status>,<local IP @>,<remote IP @>,<DNS1 @>, <DNS2 @>
0 close bearer
1 open bearer
4 start bearer
5 stop bearer
1 UART1
2 UART2
3 N/A
4 ETHER
5 GSM
6 GPRS
Note: This option is available only for UART PPP and GSM PPP, and is not
applicable for GPRS bearer.
<value>:
range of value for different bearer options
<mode>:
mode of operation
0 client
1 server
<state>:
current state of the bearer
0 stopped
1 started
<status>: result of the connection process
0 successful
any other to be matched to error code value (e.g. “814” means PPP authentication failure )
value
<local IP @*>:
local IP address
<remote IP @*>:
remote IP address. (first node in internet)
<DNS1 IP @*>:
Domain Name Server address
<DNS2 IP @*>:
Domain Name Server address
<login>:
PPP login
<passwd>:
PPP password
<caller identity>:
optional ASCII string (type ascii*).
If not specified, then target will accept all DATA calls (independently of caller
identification). If specified, then target will only accept calls from <caller
identity>(which is the GSM data call number of the GSM client).
* IP @ are displayed in alpha numeric dot format. e.g. 192.168.0.1…When no IP address is known,
“0.0.0.0“ is displayed.
Also the option WIP_BOPT_IP_MAC can be read after the bearer connection is open successfully. If
an attempt is made to read the options value before the bearer connection is open, incorrect IP
address will be received.
If the Ethernet bearer supported is defined, the MAC address is read from the Ethernet driver on
opening the bearer(i.e., +WIPBR=4,1).
“+CMEE” AT
Description
error code
3.1.2.6. Examples
Command Responses
1,0
6,1
AT+WIPBR? OK
Note: Bearer UART1 is open but not started bearer GPRS is open
and started
OK
AT+WIPBR?
Note: No bearer has been opened yet
AT+WIPBR=1,6
OK
Note: Open GPRS bearer
AT+WIPBR=2,6,11,”APN name”
OK
Note: Set APN of GPRS bearer
AT+WIPBR=2,6,21,600
OK
Note: set GPRS connection timeout value to 60s
AT+WIPBR=4,6,0
OK
Note: Start GPRS bearer
AT+WIPBR=5,6
OK
Note: Stop GPRS bearer
AT+WIPBR=0,6
OK
Note: Close GPRS bearer
AT+WIPBR=1,5
OK
Note: Open GSM bearer
AT+WIPBR=2,5,0,”login”
OK
Note: Set the login for GSM bearer
Command Responses
AT+WIPBR=2,5,1,”password”
OK
Note: Set the password for GSM bearer
AT+WIPBR=2,5,2,”phonenumber”
OK
Note: Set the phone number for GSM bearer
AT+WIPBR=2,5,15,”1.1.1.1”
OK
Note: Set the local IP address for GSM bearer
AT+WIPBR=2,5,16,”2.2.2.2”
OK
Note: Set the destination IP address for GSM bearer
OK
OK
AT+WIPBR=4,5,0
OK
Note: Start the GSM bearer as a client
AT+WIPBR=5,5
OK
Note: Stop the GSM bearer
AT+WIPBR=0,5
OK
Note: Close the GSM bearer
AT+WIPBR=1,4
OK
Note: Opens the Ethernet bearer.
AT+WIPBR=4,4,0
OK
Note: Starts the Ethernet bearer in client mode.
AT+WIPBR=5,4
OK
Note: Stops the Ethernet bearer.
AT+WIPBR=0,4
OK
Note: Closes the Ethernet bearer.
Command Responses
AT+WIPBR=2,4,23,”1”
OK
Note: Sets the DHCP to TRUE. Default: TRUE.
AT+WIPBR=2,4,26,” <netmask IP
@*>” OK
Note: Sets the Network mask address.
3.1.2.7. Notes
1,3,11,14,21,24 0 None
1,3,11,14,21,24 1 <PPP login>, <PPP password>
5 0 None
5 1 <login>,<password>[,<caller identity>]
6 0 None
Starting bearer as a server requires additional parameters as mentioned in the above table.
For PPP server, only parameters <login> and <password> are required. They will be
compared with remote PPP client login and password.
For GSM server, <login> and <password> will be used for PPP over GSM establishment
(same behavior as described for PPP server).
The <caller identity> is an optional ASCII string (type ASCII*). If not specified, then target will accept
all DATA calls (independently of caller identification). If specified, then target will only accept calls
from <caller identity> (which is the GSM data call number of the GSM client.
Opening bearer only consists in associating the IP protocol stack with the specified bearer. The
corresponding bearer setup has to be done through the adequate already existing AT commands
(please refer to +WMFM commands for UART1 and UART2, +CMUX command for CMUX virtual
ports and GSM/GPRS AT commands).
Several bearers can be opened at the same time but only one bearer can be started at a time.
If both DNS1 and DNS2 are displayed as “0.0.0.0” in the unsolicited message when bearer is opened
in server mode, it means that connecting to a remote IP host through an URL will fail.
The options WIP_BOPT_DIAL_REDIALCOUNT and WIP_BOPT_DIAL_REDIALDELAY will not be
implemented through AT commands. Nevertheless, for future compatibility reason, Opt num 3 and 4
are kept as reserved.
For GSM bearer, the options WIP_BOPT_IP_ADDR and WIP_BOPT_IP_DST_ADDR will display
valid addresses only when the bearer is started and connected, else it will display an address
“0.0.0.0”.
The Ethernet bearer can be started only in client mode.
3.2.1.1. Description
The +WIPCREATE command is used to create UDP, TCP client, SSL TCP client and TCP server
sockets associated with the specified index and FTP/HTTP/SMTP/ POP3 service. Only one
FTP/HTTP/SMTP/POP3/MMS session at a time is available.
If a local port is specified while creating a socket, the created socket will be assigned to this port; if
not, a port will be assigned dynamically by Internet Library application. If peer IP and peer port is
specified, the created socket will be connected to the specified IP and port.
TCP server cannot be used to transfer data. To transfer data, it creates a local TCP client socket. This
process of creating local socket is referred as “spawning”. When a server socket is created using,
socket passively listens on a specified port for incoming connections. The below mentioned diagram
shows different states managed for TCP server.
Closed
Listen
On reception of a connection request from a remote client socket, a server socket does the following,
spawns a new socket (client) to connect to the remote socket
data transfer is done between the spawned socket and the remote socket
server socket remains in the listening mode and is ready to accept the request from other
clients
Below mentioned diagram shows connection establishment procedure.
Connect request
Spawn a new
socket Client Socket Spawned
By Server
Connected
Transfer data
Socket Closed
3.2.1.2. Syntax
if <mode>=1
Action Command
AT+WIPCREATE=<mode>,<communication index>,<local port> [,<peer
IP>,<peer port>]
OK
if <mode>=2 or 9
Action Command
AT+WIPCREATE=<mode>,<communication index>,<peer IP>,<peer port>
OK
if <mode>=3
Action Command
AT+WIPCREATE=<mode>,<server index>,<local port>,<from idx>,<to
idx>
OK
if <mode>=4
Action Command
AT+WIPCREATE=<mode>,<index>,<server>,[<peer_port>],<username>,
<password>[,<account>]
OK
if <mode>=5
Action Command
AT+WIPCREATE=<mode>,<index>,[<server>[,<peer
port>]][,<username>,<password>][,<header list>[...]]]
OK
if <mode>=6 or 7
Action Command
AT+WIPCREATE=<mode>,<index>,<server>[,<peer
port>][,<username>,<password>]
OK
if <mode>=8
Action Command
AT+WIPCREATE=<mode>,<index>,<server>,<peer port>,<url>
OK
Test Command
AT+WIPCREATE=?
OK
Read Command
AT+WIPCREATE?
+WIPREADY: <mode>, <communication index>[, <peer IP>[, <user name>[, <password>]]]
(mode = 1, 2, 4, 5, 6, 7, 8, or 9)
+WIPSERV: <mode>, <communication index>, <local port>, <from idx>, <to idx>
(mode = 1 and 3)
Test Command
AT+WIPCREATE=?
OK
if <mode>=1, 2, or 9
Unsolicited response
+WIPREADY: <mode>,<communication index>
if <mode>=3
Unsolicited response
+WIPACCEPT: <server index>,<communication idx>
if <mode>=5, 6, 7 or 8
Unsolicited response
+WIPREADY: <mode>,<index>
1 UDP
2 TCP Client
3 TCP server
4 FTP
5 HTTP Client
6 SMTP Client
7 POP3 Client
8 MMS Client
<user name>:
username for the authentication in string format
Authentication is disabled when this parameter is not specified for
HTTP, SMTP and POP3.
<password>:
password for the authentication in string format
Authentication is disabled when this parameter is not specified for
HTTP, SMTP and POP3.
<account>:
account information of the user in string format
This is required by some FTP server during authentication phases.
<header list>:
HTTP header message (name-value pair)
The first string in the message header field is the name of the
header and the second string is the value of the header.
<url>:
URL of the MMS server
This is an alphanumeric string format for hostname starting with
“http://”.
<…>
additional HTTP message header fields
more pairs(name, value) of HTTP message header field can be
added
3.2.1.6. Examples
Command Responses
AT+WIPCREATE=1,1,80 OK
AT+WIPCREATE=1,1,”www.sierrawireless.com”,
80 OK
AT+WIPCREATE=3,1,80,5,8 OK
AT+WIPCREATE=2,1,”IP ADDR”,80 OK
Command Responses
AT+WIPCREATE=5,1,”proxyaddress”,,”user
OK
name”,”password”,”User-Agent”,”WIP-HTTP-
Client/1.0” +WIPREADY: 5, 1
AT+WIPCREATE=5,1,”proxyaddress”,,”user
name”,”password”,”User-Agent”,”WIP-HTTP- OK
Client/1.0”,"Accept-
Encoding","gzip","Accept-Language","en-US" +WIPREADY: 5, 1
AT+WIPCREATE=5,1,“proxyaddress“,,”user”,”p OK
ass”
+WIPREADY: 5, 1
AT+WIPCREATE=6,1,"smtp.mail.yahoo.fr","587 OK
","user","pass"
+WIPREADY: 6, 1
AT+WIPCREATE=7,1,"192.168.1.4","110","user OK
","pass"
+WIPREADY: 7, 1
OK
AT+WIPCREATE=7,1, "pop.mail.server.com"
+WIPREADY: 7, 1
AT+WIPCREATE=8,1, OK
"192.168.10.200",8080,"http://mms.orange.f
r" +WIPREADY: 8, 1
Command Responses
AT+WIPCREATE=9,1,”IP ADDR”,4433 OK
Note: Create the SSL TCP client on port 4433 with index=1
embedded module acts as a SSL TCP client : it can from now on Note: An unsolicited event +WIPREADY: 9,1 will be
communicate with the remote specified entity through received once the SSL TCP client is ready for usage
communication index 1
AT+WIPCREATE? OK
AT+WIPCREATE=3,1,80,3,4 OK
+WIPACCEPT: 1,3
+WIPACCEPT: 1,4
+WIPREADY: 2,3,"192.168.0.2"
+WIPREADY: 2,4,"192.168.10.20"
AT+WIPCREATE?
+WIPSERV: 3,1,80,3,4
OK
3.2.1.7. Notes
The maximum number of sockets can be set to 23 so that Internet Application can handle in the same
time either one FTP session (in passive mode)/HTTP/SMTP/POP3, 8 UDP sockets, 8 TCP client (with
1 SSL TCP client maximum included) sockets and 4 TCP servers.
SSL TCP client socket requires Security Library (refer to Security Library UGD). “+CME ERROR: 839”
error code is returned if Security Library is not initializes or not present.
Starting a TCP server requires to specify the maximum number of communication sockets that can be
spawned. This can be done using <from idx> and <to idx> parameters. Note that the value set for <to
idx> should be equal or more than <from idx>.
The maximum communication socket that can be created using Internet Application is 8. Hence, the
range for <communication index> and <from idx>, <to idx> is 1-8. Note that the spawned
communication socket and the TCP client socket share the same communication index.
It is not possible to create a client socket with AT+WIPCREATE=2, x, y, z when x is already reserved
by a server with AT+WIPCREATE=3,<server idx>, <local port>,a,b where a≤x≤b. Similarly, it is not
possible to reserve a range with AT+WIPCREATE=3, <server idx>, <local port>, a, b if one of the
TCP client socket indexes between a and b is already reserved, be it by a client or a server range
The <from idx> and <to idx> are reserved for the server socket till the server socket and the spawned
sockets are closed explicitly. So when trying to create a new TCP server socket, the <from idx> and
<to idx> should be different from what was used earlier. A parameter used as <from_idx> can’t be
used as <to_idx> anymore for other TCP server socket creation until spawned sockets with specified
<from_idx> and <to_idx> are closed along with the TCP server socket explicitly and vice versa.
When no more communication index is available in the TCP server’s range (or no more resources to
accept new incoming connections), any peer trying to connect to the server will receive an accept ()
immediately followed by a shutdown () (“peer close”).
It is possible to have a TCP client and TCP server sockets running at the same time in the same
embedded module. In this scenario, when the connection is established between the TCP server and
TCP client sockets, it is necessary to unmap the mapped socket on one index in order to send/receive
data on socket which is created on another index. It is possible to use CMUX logical ports and can
have an interface connection (like UART connection) for each socket for e.g. TCP client socket on
one logical port and TCP server socket on another. In this case, it is not necessary to map or unmap
the UART connections to send or receive the data from the socket.
The +WIPCREATE command causes the connection and authentication to the FTP server. If several
file uploads and retrievals are required to/from the same server, a single connection with
+WIPCREATE is needed. Then, each file operation will be done (one +WIPFILE command per
operation), and the FTP connection will be released with +WIPCLOSE.
SIM card is required only if FTP session is established through GSM or GPRS. An FTP session upon
an UART will work without a SIM card.
3.2.2.1. Description
The +WIPCLOSE command is used to close a socket or FTP/HTTP/SMTP/POP3/MMS session.
When one serial port (UART or CMUX DLCI) is used to map a socket for read/write operations, [ETX]
character can also be used to close the socket.
An unsolicited event is generated, when socket or FTP/HTTP/SMTP/POP3/MMS session is closed.
3.2.2.2. Syntax
Action command
AT+WIPCLOSE=<protocol>,<idx>
OK
Read Command
AT+WIPCLOSE?
NONE
Test Command
AT+WIPCLOSE=?
OK
Unsolicited response
+WIPPEERCLOSE: <protocol>,<idx>
1 UDP
2 TCP client
3 TCP server
4 FTP
5 HTTP
6 SMTP
7 POP3
8 MMS
3.2.2.6. Examples
Command Responses
AT+WIPCLOSE=1,1 OK
AT+WIPCLOSE=2,1 OK
AT+WIPCLOSE=3,1 OK
AT+WIPCLOSE=4,1 OK
AT+WIPCLOSE=5,1 OK
AT+WIPCLOSE=6,1 OK
AT+WIPCLOSE=7,1 OK
AT+WIPCLOSE=8,1 OK
AT+WIPCLOSE=9,1 OK
Command Responses
3.2.2.7. Notes
After issuing +WIPCLOSE command, no more data can be sent and received over the
socket/session. In case of FTP protocol, the closure of FTP session is indicated by +WIPEERCLOSE
unsolicited response when +WIPCLOSE command is used for closing the session.
In case of TCP and UDP sockets, response “OK” is returned when the +WIPCLOSE command is
executed irrespective of whether the socket is active or not. But in case of FTP/HTTP/SMTP/POP3
session, “OK” response is returned if +WIPCLOSE command is executed when the session is active
else “+CME ERROR: 831” error code is returned.
3.2.3.1. Description
The +WIPOPT command is used to read and/or to configure different parameters on sockets and
FTP/HTTP/SMTP/POP3/MMS service.
3.2.3.2. Syntax
if <action>=1
Action Command
AT+WIPOPT=<protocol>,<idx>,<action>,<optnum>
OK
Action Command
AT+WIPOPT=<protocol>,<idx>,<action>,<optnum>,<optval>
OK
Action Command
AT+WIPOPT=<protocol>,<idx>,<action>,<optnum>,<optval>
[,<optval2>,[<optval3>],[<optval4>]]
OK
Read Command
AT+WIPOPT?
NONE
Test Command
AT+WIPOPT=?
OK
if <action>=1
Unsolicited response
+WIPOPT: <protocol>,<optnum>,<optval>
Unsolicited response
+WIPOPT: 5,54,<message header field name>,<message header field value>,[…]
1 UDP
2 TCP client
3 TCP server
4 FTP
5 HTTP
6 SMTP
7 POP3
8 MMS
<idx>:
socket or FTP/HTTP/SMTP/POP3/MMS session identifier
<action>:
requested operation
3.2.3.6. Examples
Command Responses
AT+WIPOPT=2,1,2,8,20
OK
Note: Set TTL for TCP client
Command Responses
AT+WIPOPT=5,1,2,52,0 OK
+WIPOPT: 5,52,0
AT+WIPOPT=5,1,1,52
OK
AT+WIPOPT=6,1,2,61,”[email protected]” OK
AT+WIPOPT=6,1,2,67,0 OK
Note: The application will format the mail header and send
it during the data sending phase
+WIPOPT: 6,61,”[email protected]”
AT+WIPOPT=6,1,1,61
OK
Command Responses
+WIPOPT: 7,72,243000
AT+WIPOPT=7,1,1,72
OK
+WIPOPT: 7,73,”1,1024”
+WIPOPT: 7,73,”2,5237”
+WIPOPT: 7,73,”3,128”
AT+WIPOPT=7,1,1,73
+WIPOPT: 7,73,”4,36400”
+WIPOPT: 7,73,”5,356”
OK
+WIPOPT: 7,74,10
AT+WIPOPT=7,1,2,74,10
OK
3.2.3.7. Notes
It is possible to change and retrieve option value using +WIPOPT command only when the
socket/session (given by <idx>) is active else it returns error.
3.2.3.7.1. Options that can be applied to UDP, TCP Client, TCP Server
Sockets
Minimum amount of
available space that
must be available in the
emission buffer before
4 1-5839 WIP_COPT_SND_LOWAT triggering a - RW RW
WIP_CEV_WRITE
event
default: 1024
Number of bytes that
can currently be read
6 0-65535 WIP_COPT_NREAD on that socket R R -
default: 0
When set to TRUE,
TCP packets are sent
immediately, even if the
buffer is not full
enough.
When set to FALSE,
the packets will be sent
7 0-1 WIP_COPT_NODELAY either, - RW RW
a) by combining
several small packets
into a bigger packet
b) when the data is
ready to send and the
stack is idle.
default: 0
Time-to-leave for
8 0-255 WIP_COPT_TTL packets RW RW RW
default: 64
Type of service
9 0-255 WIP_COPT_TOS RW RW RW
default: 0
2 The option WIP_COPT_BOUND is used to check whether an UDP socket is bound to any other UDP socket or not.
When the UDP socket is created without specifying the IP address of the peer, then the option WIP_COPT_BOUND will
be read as FALSE. This is because there is no destination IP address to communicate with. If the UDP socket is created
by specifying the peer IP address, the option WIP_COPT_BOUND will be read as TRUE. This is because the peer IP
address will be resolved by the DNS and the socket is said to be bounded to the peer socket. Hence this option will be
read as TRUE.
Caution: Option 54 (WIP_COPT_HTTP_HEADER) is not implemented and hence attempt to read this option
will result in +CME ERROR: 834.
Caution: When option WIP_COPT_SMTP_FORMAT_HEADER is set to 0, application can format the mail
header to attach documents (see RFC 2822 for Standard for the Format of ARPA Internet Text
Messages for formatting details). Note that +WIPFILE command is used to send both mail header and
body.
Caution: When option WIP_COPT_SMTP_STATUS_CODE is used to retrieve the error code and the
associated error string for the SMTP session creation, it will not return any error code and error string if
no error occurred during that particular SMTP session creation. For example, After the SMTP session
is created successfully, an attempt to retrieve the error code and the associated error string, using the
option WIP_COPT_SMTP_STATUS_CODE, will result in an error code “0” and the error string
corresponding to the successful case. Create a SMTP session for the second time which will result in
the “+CME ERROR: 840” error code because the session is already active. Now an attempt to retrieve
the error code along with the associated error string, using the option
WIP_COPT_SMTP_STATUS_CODE, will result in error code “0” and the associated error string
because the first SMTP session was successful.
Caution: When option WIP_COPT_POP3_STATUS_CODE is used to retrieve the error code and the
associated error string for the POP3 session creation, it will not return any error code and error string if
no error occurred during that particular POP3 session creation.
For example, after the SMTP session is created successfully, an attempt to retrieve the error code and
the associated error string, using the option WIP_COPT_POP3_STATUS_CODE, will result in an error
code “0” and the error string corresponding to the successful case. Create a POP3 session for the
second time which will result in the “+CME ERROR: 840” error code because the session is already
active. Now an attempt to retrieve the error code along with the associated error string, using the
option WIP_COPT_POP3_STATUS_CODE, will result in error code “0” and the associated error string
because the first POP3 session was successful
* See the Phone/Mail Option Notes subsections for additional information about this option type.
Caution: For the WIP_MMS_ADD_FILE and WIP_MMS_ADD_FILE_ANY options, the total MMS size depends
on the application’s available memory (if the application is linked with 256kBytes or 1MBytes+ of RAM
memory).
• For 256kBytes (Internet Application) total MMS size must not exceed 150kBytes.
• For 1MBytes+ (Extended AT Application) total MMS size must not exceed 300kBytes.
0 PERSONAL default
1 INFORMATIONAL
2 ADVERTISEMENT
3 AUTO
0 LOW
1 NORMAL default
2 HIGH
These are the file types that correspond to the values predefined in the MMS header specification.
For other types of file the MIME type has to be explicitly set as a string.
3.2.3.7.6.5. Recipients
The total number of recipient (To+Cc+Bcc) must be less than or equal to 12, and for each recipient list
(To or Cc or Bcc), the string length must be less than 250 characters, including "/TYPE=PLMN" in
case of phone recipient type.
If you enter
AT+WIPOPT=8,1,2,81,”0683517984” (set WIP_MMS_TO_PHONE option)
then
AT+WIPOPT=8,1,2,82,[email protected] (set WIP_MMS_TO_MAIL option)
After entering AT+WIPOPT=8,1,1,81 (get WIP_MMS_TO_PHONE option) or AT+WIPOPT=8,1,1,82
(get WIP_MMS_TO_MAIL option), the response will be:
+WIPOPT: 8,82,”0683517984/TYPE=PLMN;[email protected]”
3.3.1.1. Description
The +WIPFILE command defines the “file system” services that send a block of data through standard
TCP/IP protocols. This command is used for file transfer/reception.
The data can be transferred using two modes: continuous mode and continuous transparent mode.
The FTP/HTTP/SMTP/MMS protocols support continuous mode of operation. But, continuous
transparent mode is supported only by FTP protocol.
By default, all these protocols transfer data using continuous mode. However, data transfer using FTP
protocol can be configured using <dle_mode> parameter.
Note: There is no <dle_mode> parameter specified in the +WIPFILE command to configure mode of
operation for HTTP/SMTP protocol.
Desktop PC2
Internet
GSM/GPRS
WCPU1
Desktop PC1
The above schematic explains how [ETX] characters which have a special meaning in Internet
Application are handled on Sierra Wireless embedded module.
On transmitting side, when [ETX] characters are escaped by a DLE (use case: Desktop PC1 sends
data to the embedded module. Data contains an [ETX] character escaped by a [DLE] character ([DLE]
[ETX] sequence), then the [ETX] character is transmitted as data.
On the receiving side, when [ETX] character is received as data (use case: The PC2 sends data to
the embedded module. Data contains an [ETX] character), then the [ETX] character will be preceded
by a [DLE] character when it is sent to host through the serial port.
Desktop PC2
Internet
GSM/GPRS
WCPU1
Desktop PC1
The above schematic explains how [DLE] characters which have a special meaning in Internet
Application are handled on Sierra Wireless embedded module.
On the transmitting side, when [DLE] characters are escaped by another [DLE] character (use case:
Desktop PC1 sends data to the embedded module. Data contains a non escaped [DLE] character,
and another escaped [DLE] character ([DLE][DLE] sequence), then the [DLE] character is transmitted
as data. A single [DLE] character is ignored and not transmitted.
On the receiving side, when [DLE] character is received as data (use case: The PC2 sends data to
the embedded module. Data contains an [DLE] character), then the [DLE] character will be preceded
by another [DLE] character when it is sent to host through the serial port.
3.3.1.4. Syntax
if <protocol>=4
Action Command
AT+WIPFILE=<protocol>,<index>,<mode>,<filename>[,<dle_mode>]
CONNECT
...
OK
if <protocol>=5
Action Command
AT+WIPFILE=<protocol>,<index>,<mode>,<filename>[,<username>,
<password>][,<headers list>[…]]
CONNECT
...
OK
if <protocol>=6
Action Command
AT+WIPFILE=<protocol>,<index>,<mode>
CONNECT
...
OK
if <protocol>=7
Action Command
AT+WIPFILE=<protocol>,<index>,<mode>,<filename>
CONNECT
...
OK
if <protocol>=8
Action Command
AT+WIPFILE=<protocol>,<index>,<mode>,[<filename>],[<content-
id>][<lastindicator>]
CONNECT
...
OK
if <protocol>=5
Unsolicited response
+WIPFILE: 5,<index>,<mode>,<http status code>,<http status reason>
Read command
AT+WIPFILE?
OK
Test Command
AT+WIPFILE=?
OK
4 FTP
5 HTTP
6 SMTP
7 POP3
8 MMS
<idx>:
channel identifier
<mode>:
file transfer mode
1 This command switches the UART to data mode and prints the content of the file
on UART. The end of the file is marked by [ETX] character and UART switches
back to AT mode.
This mode is used for downloading file from the FTP server if <protocol>=4.
This mode is used for downloading data of the specified URL using HTTP GET
method if <protocol>=5.
This mode is used for retrieving mail without deleting it from the POP3 server if
<protocol>=7.
This mode is not supported by SMTP protocol.
2 This command switches the UART to data mode and accepts a stream of data
terminated by [ETX] character.
This mode is used for uploading file to the FTP server if <protocol>=4.
This mode is used for uploading data to the specified URL using HTTP PUT
method if <protocol>=5.
This mode is used for sending mail to the SMTP server if <protocol>=6.
This mode is not supported by POP3 protocol.
3 This mode is used for deleting the specified URL using HTTP DELETE method if
<protocol>=5.
This mode is used for retrieving mail and deletion after retrieval from the POP3
server if <protocol>=7.
This mode is not supported by FTP and SMTP protocol.
4 This command switches the UART in data mode and accepts a stream of data
terminated by [ETX] character.
This mode is used for uploading data to the HTTP server using HTTP POST
method if <protocol>=5.
This mode is not supported by FTP, SMTP and POP3 protocol.
5 This command switches the UART to data mode and accepts a stream of data
terminated by [ETX] character.
This mode is used for uploading file using FTP APPEND method server if
<protocol>=4.
This mode is not supported by other protocols
6 This mode is used to upload DATA in Data Offline mode(1) (by using
+WIPDATARW command).
This mode is used for uploading files to the FTP server if <protocol>=4.
This mode is used for sending mail to the SMTP server if <protocol>=6.
This mode is not supported by other protocols.
7 This mode is used to download and display DATA in Data Offline mode(1) (by
using +WIPDATARW command).
This mode is used for downloading a file from the FTP server if <protocol>=4.
This mode is used for downloading data of the specified URL using HTTP GET
method if <protocol>=5.
This mode is used for retrieving mail without deleting it from the POP3 server if
<protocol>=7.
This mode is not supported by other protocols.
8 This mode is used for retrieving mail and deleting after retrieval from the POP3
server if <protocol>=7 in Data Offline mode(1) (by using +WIPDATARW
command).
This mode is not supported by other protocols.
9 This mode is used for uploading a file using FTP APPEND method server if
<protocol>=4 in Data Offline mode(1) (by using +WIPDATARW command).
This mode is not supported by other protocols
<filename>:
file name
if <protocol>=4: specify the name of the file to upload or download
The maximum file length is limited to 128 characters. The actual filename,
including path name has to be used.
if <protocol>=5: URL of the HTTP request
if <protocol>=7: mail id in string format
if <protocol>=8: the identifier matching the identifier specified in WIPOPT.
<lastindicator>
Indicates that the file is the last of the files to send.
1
: See the DATA Offline session +WIPDATARW section for more information.
3.3.1.8. Examples
Command Responses
CONNECT
AT+WIPFILE=4,1,1,”data.bin” <data received terminated by [ETX]
character>
CONNECT
AT+WIPFILE=4,1,2,”report.log”
<data terminated by [ETX] character>
CONNECT
AT+WIPFILE=4,1,5,”report.log”
<data terminated by [ETX] character>
Note: Upload file in continuous mode; data will be added at the end of
OK
file
CONNECT
AT+WIPFILE=4,1,1,”data.bin”,1 <data>
+++
OK
CONNECT
AT+WIPFILE=4,1,2,”report.log”,1 <data>
+++
OK
CONNECT
AT+WIPFILE=4,1,1,”data.bin”,0 <data received terminated by [ETX]
character>
CONNECT
AT+WIPFILE=4,1,2,”report.log”,0
<data terminated by [ETX] character>
Command Responses
CONNECT
<data terminated by [ETX] character>
AT+WIPFILE=5,1,2,”urlForPut” OK
+WIPFILE:5,1,2,<http status
code>,<http status reason>
CONNECT
<data received terminated by [ETX]
character>
AT+WIPFILE=5,1,3,”urlForDelete”
OK
+WIPFILE:5,1,3,<http status
code>,<http status reason>
CONNECT
<data received terminated by [ETX]
character>
AT+WIPFILE=5,1,4,”urlForPost”
OK
+WIPFILE:5,1,4,<http status
code>,<http status reason>
CONNECT
<data sent terminated by [ETX]
AT+WIPFILE=6,1,2
character>
OK
CONNECT
<data received terminated by [ETX]
AT+WIPFILE=7,1,1,”15”
character >
OK
CONNECT
<data received terminated by [ETX]
AT+WIPFILE=7,1,3,”1”
character >
OK
Note: Retrieve data from the given ID Note: Retrieve mail ID 1 and delete it after retrieval
3.3.1.9. Notes
The [ETX] character is considered as an end of data. Hence, in case [ETX] character needs to be
transmitted, it should be preceded by [DLE] character.
For MMS, when sending file data through AT+WIPFILE command, if data size is greater than the one
specified via WIP_MMS_ADD_FILE or WIP_MMS_ADD_FILE_ANY options, the data will be
truncated to said option’s size, and module will leave the data mode. When going back to AT mode,
+WIPFILE: proto,index,size will be received with the size equal to the size of the data that will be
included in the MMS file.
3.3.2.1. Description
The +WIPDATA command is used to read/write from/to a socket. On successful execution of the
command, the UART switches to data mode. The UART can be switched back to AT mode by
sending “+++” with 1 second guard time before and after the sequence. If data is not read using
+WIPDATA command, further data will be delayed.
An unsolicited event is received when there is a data to read on socket.
Data can be sent on the sockets using two modes
continuous mode
continuous transparent mode
Note: When using the UDP protocol, consider that you cannot send more than the
WIP_COPT_RCV_BUFSIZE data receiving buffer size. Based on this, be sure that no data will be
lost, as it depends on the bearer "speed".
All data written on an UDP socket is collected till an [ETX] character is encountered or the maximum
size of the datagram1 is reached and will be sent as a single datagram. Similarly when reading data,
all data will be read till an [ETX] character is encountered which indicates the end of the datagram.
Note that, in this mode, packet segmentation feature is not supported.
In case an [ETX]/[DLE] character needs to be transmitted, it should be preceded by [DLE] character
similar to TCP socket.
When the UART leaves DATA mode, either because of “+++” escape sequence or because of an
AT+WIPDATA=1, index, 0 on another UART, the currently unsent data are sent as a single datagram.
The above schematic explains how [ETX] characters – which have a special meaning in Internet
Application – are handled on Sierra Wireless embedded module.
On transmitting side, when [ETX] are not escaped (use case: Desktop PC1 sends data towards
embedded module. Data contain a non escaped [ETX] ( no [DLE][ETX] sequence), then [ETX] is
not transmitted but an action is done on embedded module regarding the concerned socket:
UDP socket: a non escaped [ETX] marks the boundary of the current datagram to be sent.
Datagram is immediately sent and the [ETX] is not sent towards the desktop PC2.
TCP socket: a non escaped [ETX] causes a TCP shutdown operation on the transmitting
direction: peer is informed that embedded module will not send any more data on that socket.
1
Maximum size of an UDP datagram has been fixed to 8192 bytes. This limit is an arbitrary one. Nevertheless, note that
smaller the datagram is the surer it will reach the aimed destination. Note that UDP is not a reliable transport layer.
Usually, peer will shutdown the other way (downlink) and this will result in a “peer close event”
on the socket.
On receiving side, when [ETX] are not escaped (use case: embedded module sends data towards
Desktop PC1. Data contain a non escaped [ETX] ( no [DLE][ETX] sequence), then [ETX] means
that a special “IP” event occurred on embedded module regarding the concerned socket:
UDP socket: a non escaped [ETX] signals the boundary of the current received datagram.
TCP socket: a non escaped [ETX] signal that the peer TCP connected TCP unit shutdown the
downlink way. Desktop PC1 should then close the uplink socket to totally terminate the TCP
“session”.
Note: The behavior is symmetrical: apply both on transmitting/receiving side of mapped UART.
The above schematic explains how [DLE] characters – which have a special meaning in Internet
Application – are handled on Sierra Wireless embedded module.
On transmitting side, when [DLE] is not escaped (use case: Desktop PC1 sends data towards
embedded module. Data contains a non escaped [DLE] ( no [DLE][DLE] sequence), then [DLE] is
not transmitted.
On transmitting side, when [DLE] is escaped (use case: Desktop PC1 sends data towards embedded
module. Data contain an escaped [DLE] ( [DLE][DLE] sequence) then [DLE] data is transmitted.
On the receiving side (use case: when Desktop PC2 sends data towards embedded module. Data
contains a no escaped [DLE]) the data sent from the embedded module to Desktop PC1 will contain
an escaped [DLE] preceding the [DLE] character (Desktop PC1 receives [DLE][DLE] character from
embedded module).
The scenario is same for both TCP and UDP sockets.
To avoid sending of this “+++” as data, it is recommended to set the value of option
AT_WIP_NET_OPT_ESC_SEQ_NOT_SENT to 1 using command AT+WIPCFG=2,13,x.
3.3.2.6. Syntax
Action Command
AT+WIPDATA=<protocol>,<idx>,<mode>[,<send size>,<wait time>]
CONNECT
Note: Once the +WIPDATA indication has been received, on peer closed, +WPPEERCLOSE indication
won't be received unless AT+WIPDATA has been sent.
Read Command
AT+WIPDATA?
NONE
Test Command
AT+WIPDATA=?
OK
if <protocol>=1
Unsolicited response
+WIPDATA: <protocol>,<idx>,<datagram size>,<peer IP>,<peer port>
Caution: Using +WIP AT commands, when receiving several UDP datagrams on an IP bearer, +WIPDATA
indication is sent once for the first received datagram. Next indication (for next remaining UDP
datagram to read) is sent once the first datagram have been read (using +WIPDATA command).
if <protocol>=2 or 9
Unsolicited response
+WIPDATA: <protocol>,<idx>,<number of readable bytes>
Caution: The value returned by <number of readable bytes> indicates that there is some TCP data ready to be
read but number of bytes returned might not be reliable. Moreover, using +WIPAT commands, when
receiving several TCP packets on an IP bearer, +WIPDATA indication is sent once for the first
received packet. The next indication (for the next remaining TCP packet to read) is sent after the first
packet have been read (using +WIPDATA command).
1 UDP
2 TCP client
3 Data Offline: Activate Data Data Offline mode(1) on the specified socket.
In this mode, [DLE]/[ETX] characters are considered as normal data and not special
characters.
<send size>: data packet size: This parameter specifies the size of the data packet that needs to
be sent to the peer. This parameter is supported only for UDP continuous transparent
mode.
range: 8-1460 (default value: 1020)
<wait time>: timeout for configuring the packet segmentation on IP network side: This parameter
specifies the timeout after which the buffered data will be sent to the peer irrespective
of size of the data packet. This parameter is supported only for UDP continuous
transparent mode.
range: 1-100 (default value: 2)
1
: See the DATA Offline session +WIPDATARW section for more information.
3.3.2.10. Examples
Command Responses
CONNECT
<read/write data>
AT+WIPDATA=2,5,1
+++
OK
CONNECT
<read/write data>
AT+WIPDATA=2,5,1,10,5
+++
OK
Command Responses
CONNECT
<read/write data>
AT+WIPDATA=1,5,1
+++
OK
CONNECT
<read/write data>
AT+WIPDATA=1,5,1
<ETX>
OK
CONNECT
<read/write data>
AT+WIPDATA=1,5,2
+++
OK
CONNECT
<read/write data>
AT+WIPDATA=1,5,2,20,2
+++
OK
CONNECT
<read/write data>
AT+WIPDATA=2,5,1,20,10
+++
OK
CONNECT
<read/write data>
AT+WIPDATA=2,5,2,10,5
+++
OK
Command Responses
CONNECT
<read/write data>
AT+WIPDATA=2,5,2
+++
OK
3.3.2.11. Notes
In the above schematic, a TCP socket is connected. On the transmitting side, data and [ETX] is sent
(use case: Desktop PC1 is an embedded module which sends data to PC2 which is either a PC or a
embedded module), the data is received on PC2 and [ETX] character shutdowns the socket on the
transmitting side and displays a message “[CR][LF]SHUTDOWN[CR][LF]” on the mapped UART of
PC2.
When PC2 is switched back to AT mode, “+WIPPEERCLOSE: <protocol>,<idx>” indication is
received indicating that no more data can be sent by PC1 but can read data sent from PC2.
There are different indications received for shutdown and reset for a TCP socket. When a TCP socket
is reset, [ETX] character is sent on the mapped UART to indicate the end of communication. The
mapped UART switches to AT mode and “+CME ERROR: 843” is displayed on the UART. The reset
and shutdown can therefore be distinguished by the indications received on the UART.
3.3.2.11.3. Time out Mechanism to know the state of the Peer TCP Socket
In a TCP server-client connection between two remote devices if the peer socket is closed down
abruptly (e.g. powered off) the peer TCP socket does not get any indication message. This is a
normal behavior. The TCP protocol uses a timeout mechanism to check the state of the TCP sockets
in a TCP socket connection. According to this mechanism, to know the state of the peer TCP socket
the data needs to be sent and wait for the acknowledgement within a specified time period. If the
acknowledgement is not received within the specified time out period then the data is retransmitted.
But if the time out occurs before receiving acknowledgement then it implies that the peer TCP socket
is closed.
3.3.3.1. Restrictions
DATA offline feature is not recommended to send or received quickly high data volume. In
this case, the nominal online mode shall be used.
DATA offline does not support multisession, meaning if two sockets are created, both sockets
cannot be used simultaneously in DATA offline mode.
To improve AT command exchange and behavior, the use of USB com port is recommended.
Otherwise, UART com port buffer threshold shall be decrease with +WHCNF command (see
General AT Command User Guide).
Be careful for TCP socket (+WIPDATA), a maximum of 5840 bytes can be send. Over this
size data are lost but no error is returned.
+WIDATARW command should not be used to fill TX sender buffer with more than 5840
bytes (4*1460) for TCP socket.
3.3.3.2. Syntax
Read Command
AT+WIPDATARW?
OK
Test Command
AT+WIPDATARW=?
OK
1 WRITE and Send: Add DATA in TX buffer then send all data stored in the buffer.
3 WRITE, Send and close: Add DATA in TX buffer, send all data stored in the buffer, then
close the current DATA offline session.
This command is only supported for +WIPDATA session.
<state>:
2 Data reading
3 Data sent
To send more than 200 bytes data, use +WIPDATARW with <command> = 2 to add data to buffer
and use for the last block
Data must be written in TX buffer with <command> = 2 by 200 byte block and the last block must be
written with <command> =1 to write it and send the TX buffer.”
Only 200 data bytes can be read or written at a time. DATA received are displayed by 200 byte block
if received data buffer to display is bigger than 200 bytes.
3.3.3.6. Examples
Command Responses
AT+WIPDATA=1,1,3
+WIPDATARW:1,1
(UDP socket have been previously
OK
created)
AT+WIPDATARW=1,1,"30313233343536373839 +WIPDATARW:3,1,10
" OK
Note : send 10 data byte on channel idx 1 Note : 10 data bytes had been sent
+WIPDATA: 1,1,10,"192.168.1.2",1357
+WIPDATARW:2,1,1,1,"3132333435363738"
OK
AT+WIPDATARW=2,1,"30[…]39"
OK
Note : Write 200 Data bytes in TX Buffer Note : 200 data bytes are stored in TX Buffer
AT+WIPDATARW=2,1,"30[…]39"
OK
Note : Write 200 Data bytes in TX Buffer Note : 200 data bytes are stored in TX Buffer
+WIPDATARW:3,1,402
AT+WIPDATARW=1,1,"3039"
OK
Note : Write 2 Data bytes in TX Buffer and send
buffer. Note : 402 data bytes have been sent
+WIPDATARW:0,1
AT+WIPDATARW=0,1
OK
Note : try to send 10 bytes on channel index 1 Note : WIPDATARW session is not open in channel idx 1
Command Responses
AT+WIPFILE=4,2,6,”./filename.txt” +WIPDATARW:1,2
OK
AT+WIPDATARW=1,2,"30313233343536373839 +WIPDATARW:4,2,10
" +WIPDATARW:0,2
OK
+WIPDATARW:3,2,2,1,"31[…]"
AT+WIPFILE=4,2,7,”./filename.txt” +WIPDATARW:3,2,2,2,"31[…]"
+WIPDATARW:0,2
OK
Note : More than 200 data downloaded
Note : Download and display “filename.txt” file WIPDATARW session closed on channel idx 2
3.4.1.1. Description
The +WIPPING command is used to configure different PING parameters and to send PING requests.
An unsolicited response is displayed each time a “PING” echo event is received or a timeout expires.
3.4.1.2. Syntax
Action Command
AT+WIPPING=<host>,[<repeat>,<interval>,[<timeout>,[<nwrite>,[<tt
l>]]]]
OK
Read Command
AT+WIPPING?
OK
Test Command
AT+WIPPING=?
OK
Unsolicited response
+WIPPING:<timeout_expired>,<packet_idx>,<response_time>
3.4.1.6. Examples
Command Responses
OK
AT+WIPPING=”www.sierrawireless.com”
+WIPPING: 1,0,0
OK
AT+WIPPING=”192.168.0.1”
+WIPPING: 0,0,224
OK
AT+WIPPING=”192.168.0.1”,2,2000,1000 +WIPPING: 0,0,880
+WIPPING: 1,1,xxxx
OK
AT+WIPCREATE=3,1,80,5,8 //create the server on port 80, idx = 1. The server //is listening
for connection request on port //80.Spawned sockets will be
OK
given the index 5, //6, 7 and 8. It will accept connection request
//until it has no more socket left.
… //read, write
OK
AT+WIPCREATE=3,1,80,5,8 //create the server on port 80, idx = 1. The server //is listening
OK for connection request on port //80.Spawned sockets will be
given the index 5, //6, 7 and 8. It will accept connection request
//until it has no more socket left.
… //read, write
OK
+WIPREADY: 2,1 //unsolicited: the TCP client socket is connected //to the peer
… //read, write
OK
AT+WIPCREATE=2,1,”ip addr”,80 //create a TCP client towards peer IP device @ “ip //addr”, port
80
+WIPREADY: 2,1 //unsolicited: the TCP client socket is connected to //the peer
… //read, write
OK
+WIPREADY: 1,1 //unsolicited: the UDP client socket is “pseudo” //connected to the
peer (no //real connection is UDP)
… //read, write
OK
AT+WIPCREATE=1,1,1234 //start a UDP server and listen for datagram on port //1234
+WIPREADY: 1,1 //unsolicited: the UDP client socket is “pseudo” //connected to the
peer (no real connection is UDP)
AT+WIPDATA=1,1,1
CONNECT
abcedghijklmnopqrstuvwxyz[ETX] //here 25 bytes + the [ETX] character (marking the //bound of the
datagram) have been read.
+++ or AT+WIPDATA=1,1,0 //type on this UART “+++” escape sequence or un //map the
UART on other control port (USB UART)
AT+WIPDATA=1,1,1
CONNECT
abcedghijklmnopqrstuvwxyzabcedghijklmnopq //here 25 bytes + the [ETX] character (marking the //bound of the
rstuvwxyz [ETX] datagram) have been read.
3.5.3. PING
AT+WIPCFG=1 //start IP stack
OK
3.5.4. FTP
AT+WIPCFG=1 //start IP stack
OK
3.5.6. HTTP
AT+WIPCFG=1 //start IP stack
OK
3.5.7. SMTP
AT+WIPCFG=1 //start IP stack
OK
3.5.8. POP3
AT+WIPCFG=1 //start IP stack
OK
3.5.9. MMS
Example of sending an MMS with multiple recipients and multiple files with the same extensions.
Please note that files are not buffered, but sent directly to the MMS Server.
Detailed information about the files is needed for the headers before and must be set for each file
using WIPOPT before sending the file via WIPFILE.
AT+WIPCFG=1 //start IP stack
OK
AT+WIPBR=1,6 //open GPRS bearer
OK
AT+WIPBR=2,6,11,"orange.fr" //set APN name of GPRS bearer
OK
AT+WIPOPT=8,1,2,92,1, // set the multipart type to Related and specify that the first
"application/smil","<001>" file that should be read is a type SMIL with the content-id
“<001>”
OK
AT+WIPOPT=8,1,2,93,9,100, "1.smil", "<001>" // add a SMIL multimedia presentation file of size 100 Bytes
with filename “1.smil” and content-id “<001>”
OK
AT+WIPOPT=8,1,2,93,2,222,"2.txt", // add a text file of type USC2 of size 222 bytes with the
filename “2.txt” but no content-id.
OK
AT+WIPOPT=8,1,2,93,3,304,,<003>" // add a text file of type ASCII of size 304 Bytes with no
filename but content-id “<003>”.
OK
AT+WIPOPT=8,1,2,93,4,1024,"4.jpeg","<004>" // add a JPEG picture of size 1024 Bytes with the filename
“4.jpeg” and content-id “<004>”.
OK
AT+WIPOPT=8,1,2,93,5,2048,"5.gif", "<005>" // add a GIF picture of size 2048 Bytes with the filename
“5.gif” and content-id “<005>”.
OK
CONNECT
<user starts sending the file with the UART
in data mode and ends with an [ETX] character
>
OK
AT+WIPCREATE=3,2,80,1,2 //create the server on port 80, idx=2. The server //is listening
OK for connection request on port 80. //Spawned sockets will be
given the index 1 or //2.It will accept connection request until
has //nor more socket left.
+WIPREADY: 2,3 //unsolicited: the TCP client socket is connected //to the
peer.
AT+WIPCREATE=3,2,81,2,3 //create the server on port 81, idx=2 and from_idx=2 and
to_idx=3
+CME ERROR:845 //TCP client socket with idx 2 was reserved by //the previous
server socket and it was not //closed explicitly. Hence error
is returned.
+WIPREADY: 2,1 //unsolicited: the TCP client socket is connected //to the
peer.
AT+WIPCREATE=1,9,63,”192.168.0.1”
,83
+CME ERROR: 830 th
//8 UDP sockets have been created and hence //9 attempt
fails
AT+WIPCREATE=3,1,80,1,1 //create one server on port 80, idx = 1. One //TCP client
OK socket is reserved on index 1
AT+WIPCREATE=3,2,81,2,2 //create one server on port 81, idx = 2. One //TCP client
OK socket is reserved on index 2
AT+WIPCREATE=3,3,82,3,3 //create one server on port 82, idx = 3. One //TCP client
OK socket is reserved on index 3
AT+WIPCREATE=3,4,83,4,4 //create one server on port 83, idx = 4. One //TCP client
OK socket is reserved on index 4
AT+WIPCREATE=3,5,84,5,5 //4 TCP servers have been created and hence //creation of
th
+CME ERROR: 830 5 TCP server socket fails
+WIPREADY: 2,5 //unsolicited: the TCP client socket is connected //to the
peer.
+WIPREADY: 2,6 //unsolicited: the TCP client socket is connected //to the
peer
+WIPREADY: 2,7 //unsolicited: the TCP client socket is connected //to the
peer
+WIPREADY: 2,8 //unsolicited: the TCP client socket is connected //to the
peer
AT+WIPCREATE=1,9,63,”192.168.0.1”
,83
+CME ERROR: 830 th
//8 UDP sockets have been created and hence //9 attempt
fails
AT+WIPCREATE=3,1,83,1,1 //create one server on port 83, idx = 1. One //TCP client
OK socket is reserved on index 1
AT+WIPCREATE=3,2,84,2,2 //create one server on port 84, idx = 2. One //TCP client
OK socket is reserved on index 2
AT+WIPCREATE=3,3,85,3,3 //create one server on port 85, idx = 3. One //TCP client
OK socket is reserved on index 3
AT+WIPCREATE=3,4,86,4,4 //create one server on port 86, idx = 4. One //TCP client
OK socket is reserved on index 4
AT+WIPCREATE=3,5,84,5,5 //4 TCP servers have been created and hence //creation of
th
+CME ERROR: 830 5 TCP server socket fails
AT+WIPCREATE=2,1,”192.168.0.1”,83 //4 TCP server have been created and each of //them
th
+CME ERROR: 845 reserved 1 TCP client socket and hence //5 attempt of
creating TCP server fails
+WIPREADY: 2,5 //unsolicited: the TCP client socket is connected //to the
peer.
+WIPREADY: 2,6 //unsolicited: the TCP client socket is connected //to the
peer
+WIPREADY: 2,7 //unsolicited: the TCP client socket is connected //to the
peer
+WIPREADY: 2,8 //unsolicited: the TCP client socket is connected //to the
peer
AT+WIPCREATE=7,1,”POP3
server”,,”user name”,”mail id”
+CME ERROR: 840
//attempt of creating a OP3 session returns an //error as
already 1 FTP session is active.
OK
+WIPPEERCLOSE: 4,1 //unsolicited: FTP session is closed //successfully
AT+WIPCREATE=3,2,80,1,2 //create the server on port 80, idx=2. The server //is listening
OK for connection request on port 80. //Spawned sockets will be
given the index 1 or //2.It will accept connection request until
has //nor more socket left.
+WIPREADY: 2,3 //unsolicited: the TCP client socket is connected //to the
peer.
“+CMEE” AT
Description
error code
“+CMEE” AT
Description
error code
“+CMEE” AT
Description
error code
specified parameters to the command is more or less than the maximum number of
851
mandatory parameters
852 IP stack not initialized
853 Data offline buffer filled
854-859 reserved for future use
860 protocol undefined or internal error
861 username rejected by server
862 password rejected by server
863 delete error
864 list error
865 authentication error
866 server not ready error
867 POP3 email retrieving error
868 POP3 email size error
869-879 reserved for future use
880 SMTP sender email address rejected by server
881 SMTP recipient email address rejected by server
882 SMTP CC recipient email address rejected by server
883 SMTP BCC recipient email address rejected by server
884 SMTP email body send request rejected by server
890 Service denied
891 Message format corrupt
892 Address unresolved
893 Message not found
894 Network problem
895 Content not accepted
896 Unsupported message
897 Unspecified error
4.1.1.1. Description
This AT Command is used to display the Location AT commands help.
Note: +GPSHELP command syntax is subject to change with application evolution.
4.1.1.2. Syntax
Action command
AT+GPSHELP=[<at_command>]
OK
Test command
AT+GPSHELP=?
+GPSHELP: (list of supported <at_command>s)
OK
<at_command >: The string parameter specifies the AT command described by help display.
4.1.1.4. Examples
Command Responses
+GPSINIT= <hw>[,<spi>,<cs>,<reset>,<enable>,
AT+GPSHELP <clock32k>]
Note: displays all supported Location …
Services AT command format.
OK
Command Responses
AT+GPSHELP=GPSSTART +GPSSTART=[<starting_mode>]
Note: displays information about the <starting_mode>: 0 [GPS_HOT_START]
+GPSSTART AT command.
<starting_mode>: 1 [GPS_WARM_START]
<starting_mode>: 2 [GPS_COLD_START]
<starting_mode>: 3 [GPS_FACTCOLD_START]
OK
AT+GPSHELP=? +GPSHELP:
Note: displays all supported Location (GPSINIT,GPSNMEA,GPSSTART,GPSSTOP,GPSSTATE,GPSTTFF,GPSS
AT command. AVE, etc.)OK
4.1.2.1. Description
This AT command configures the NMEA frames flow, the output port and the NMEA sentences
encode mask.
Note: NMEA sentences are output as unsolicited AT command responses. In consequence, in case the output
port is not dedicated but shared with AT commands, NMEA frames output will be suspended while an AT
command is being processed, and resume once the AT command has returned. In case of significant
delay, some NMEA sentences may be partially or totally lost.
4.1.2.2. Syntax
Action command
AT+GPSNMEA=[<output>][,[<rate>][,<nmea_mask>],[<nmea_profile>]]
OK
Read command
AT+GPSNMEA?
+GPSNMEA: <output>,<rate>,<nmea_mask>,<nmea_profile>
OK
Test command
AT+GPSNMEA=?
<output>: This parameter specifies the port which is to be used by the application to transmit
the NMEA frames. (Hexadecimal value entered without the prefix “0x”). This port
can also be used simultaneously as the PVT sentences output port if need be.
If omitted: last known value within current session.
Factory default value: 1.
Note: The port has to be different from the port used for the communication
between GPS receiver and the Embedded Module. See +GPSINIT for more
details.
0 NMEA frames are not output.
4 NMEA frames output on port where the +GPSNMEA command was received.
The supported ports are described above.
0x1X CMUX virtual port, Logical ports over UART1 where 1 <= X <=4
0x2X CMUX virtual port, Logical ports over UART2 where 1 <= X <=4
0x5X CMUX virtual port, Logical ports over UART3 where 1 <= X <=4
<rate>: This parameter defines the NMEA frames update rate in seconds.
If omitted: last known value within current session.
Factory default value: 1.
Range: 0-65535
Note: If this parameter is equal to 0, the NMEA frames will be sent only once,
on the next occurrence of the NMEA frames update.
Note: This parameter is impacted by the Reduced Rate GPS Navigation.
Please refer to +GPSCONF AT command for more information.
<nmea_mask>: NMEA sentences list encode mask (Hexadecimal value entered without the
prefix “0x”).
This parameter defines the NMEA sentences encode mask as described
hereunder.
If omitted: last known value within current session
Factory default value: 0xFFFF.
Range: 0x0-0xFFFF
Note: [] All NMEA frames may not be supported depending on GPS receiver
type.
(1 << 0): GPS_NMEA_GGA_EN - NMEA $GPGGA (GPS Fix Data) output enabled
(1 << 1): GPS_NMEA_GGSA_EN - NMEA $--GSA (GNSS DOPS and Active Satellites)
output enabled.
(1 << 3): GPS_NMEA_VTG_EN - NMEA $--VTG (Course Over Ground and Ground
Speed) output enabled.
(1 << 7): GPS_NMEA_ZDA_EN - NMEA $--ZDA (Time & Date) output enabled (if
supported by GPS receiver).
Note: [] All NMEA profiles may not be supported depending on GPS
receiver type.
0: GPS_NMEA_PROFILE_NONE - No NMEA profile.
4.1.2.4. Examples
Command Responses
AT+GPSNMEA=3 OK
or
Note: request NMEA frames output on port 3 +GPS ERROR: X
(USB).
Note: For more information about X value, please refer to Location AT
commands error codes description.
AT+GPSNMEA=1,5 OK
or
Note: request NMEA frames output on UART1 (1) +GPS ERROR: X
with an update rate of 5 seconds.
Note: For more information about X value, please refer to Location AT
commands error codes description.
AT+GPSNMEA=1,1,FFFF OK
or
Note: request all NMEA frames output on UART1 +GPS ERROR: X
(1) with an update rate of 1 second.
Note: For more information about X value, please refer to Location AT
commands error codes description.
AT+GPSNMEA=1,1,FFFF,3 OK
or
Note: request all NMEA frames output on UART1 +GPS ERROR: X
(1) with an update rate of 1 second, only for GPS
and GLONASS constellation ( No GN Note: For more information about X value, please
NMEA sentence will be displayed ). refer to Location AT commands error codes
description.
AT+GPSNMEA=,60,19
OK
or
Note: request VTG+GGA+GLL NMEA sentences +GPS ERROR: X
output on default port with an update rate of 60
seconds. Note: For more information about X value, please refer to Location AT
commands error codes description.
AT+GPSNMEA=,,19 OK
or
Note: request VTG+GGA+GLL NMEA sentences +GPS ERROR: X
output on default port with the default update rate.
Note: For more information about X value, please refer to Location AT
commands error codes description.
AT+GPSNMEA=?
+GPSNMEA: (0-5,11-14,21-24,51-54),(0-65535),(0-
FFFF), (0-FF)
OK
Command Responses
AT+GPSNMEA?
+GPSNMEA: 1,1,FFFF,FF
4.1.3.1. Description
This AT command configures the PVT sentences flow including the output port, the output rate, and
the PVT sentences output mask.
The PVT sentences include the main GPS information like Fix Status, Position, Velocity, Time and
satellites information.
Note: PVT sentences are output as unsolicited AT command responses. In consequence, in case the output
port is not dedicated but shared with AT commands, PVT sentences output will be suspended while an
AT command is being processed, and resume once the AT command has returned. In case of significant
delay, some PVT sentences may be partially or totally lost.
Note: [] +GPSPVT AT command is not supported for gpsOne.
4.1.3.2. Syntax
Action command
AT+GPSPVT=[<output>][,[<rate>][,<pvt_mask>]]
OK
Read command
AT+GPSPVT?
+GPSPVT: <output>,<rate>,<pvt_mask>
OK
Test command
AT+GPSPVT=?
+GPSPVT: (list of supported <output>s),(list of supported <rate>s), (list of
supported <pvt_mask>s)
OK
<output>: This parameter specifies the port which is to be used by the application to transmit
the PVT sentences. (Hexadecimal value entered without the prefix “0x”). This port
can also be used simultaneously as the NMEA frames output port if need be.
If omitted: last known value within current session.
Factory default value: 0.
Note: The port has to be different from the port used for the communication
between GPS receiver and the Embedded Module. See +GPSINIT for more
details.
0 PVT sentences are not output.
4 PVT sentences output on port where the +GPSPVT command was received.
0x1X CMUX virtual port, Logical ports over UART1 where 1 <= X <=4
0x2X CMUX virtual port, Logical ports over UART2 where 1 <= X <=4
0x5X CMUX virtual port, Logical ports over UART3 where 1 <= X <=4
<rate>: This parameter defines the PVT sentences update rate in seconds.
If omitted: last known value within current session.
Factory default value: 1.
Range: 0-65535
Note: If this parameter is equal to 0, the PVT sentences will be sent only once,
on the next occurrence of the PVT sentences update.
Note: This parameter is impacted by the Reduced Rate GPS Navigation.
Please refer to +GPSCONF AT command for more information.
<pvt_mask>: PVT sentences list encode mask (Hexadecimal value entered without the prefix
“0x”).
This parameter defines the PVT sentences encode mask as described
hereunder.
The PVT sentence includes the header +GPSPVT: X with X defined as the PVT
sentence identifier. All the fields are separated by a comma.
If omitted: last known value within current session.
Factory default value: 0xFFFF.
Range: 0x0-0xFFFF
0: PVT sentence including the main GPS position information. The fields are
described hereunder:
Header: +GPSPVT: 0
1: UTC of position fix in HH:MM:SS format
2: Date in dd/mm/yyyy format
3: GPS position fix state: “NO FIX”, “ES FIX” (Estimated Fix), “2D FIX” or “3D
FIX”
4: Latitude: Direction (‘N’ North or ‘S’ South) and the Latitude in DD MM’SS.SS”
5: Longitude: Direction (‘E’ East or ‘W’ West) and the Longitude in DDD
MM’SS.SS”
6: Altitude above Mean Sea Level in meters in +/-mmmm format
Example:
+GPSPVT: 0,08:17:32,27/04/2010,3D FIX,N 48 34'52.90'',E 002
21'58.65'',+0010m
1: PVT sentence including the Course and the Speed over the ground. The fields
are described hereunder:
Header: +GPSPVT: 1
1: Dimensional Course Over Ground in degrees in ddd.d format [0-359.9].
2: Dimensional Speed Over Ground in meter per second in sss format
Example:
+GPSPVT: 1,087.5deg,021m/s
2: PVT sentence including the main satellites information. The fields are described
hereunder:
Header: +GPSPVT: 2
1: Satellites in View used for Navigation followed by “SV”
2: HDOP (Horizontal Dilution of Precision) followed by “HDOP”
3: Satellites in View Maximum Signal To Noise Ratio [dBHz, integer value]
4: Satellites in View Average Signal To Noise Ratio [dBHz, 1 decimal value]
Example:
+GPSPVT: 2,05SV,1.7HDOP,23,12.0
4.1.3.4. Examples
Command Responses
AT+GPSPVT=3 OK
or
Note: request PVT sentences output on port 3 +GPS ERROR: X
(USB).
Note: For more information about X value, please refer to Location AT
commands error codes description.
AT+GPSPVT=3,5 OK
or
Note: request PVT sentences output on port 3 +GPS ERROR: X
(USB) with an update rate of 5 seconds.
Note: For more information about X value, please refer to Location AT
commands error codes description.
AT+GPSPVT=3,1,FFFF OK
or
Note: request all PVT sentences output on USB +GPS ERROR: X
(3) with an update rate of 1 second.
Note: For more information about X value, please refer to Location AT
commands error codes description.
AT+GPSPVT=?
+GPSPVT: (0-5,11-14,21-24,51-54),(0-65535),(0-
FFFF)
OK
AT+GPSPVT?
+GPSPVT: 1,1,FFFF
+GPSEVSTART: 1
+GPSEVPOS: 0
+GPSPVT: 1,000.0deg,000m/s
+GPSPVT: 2,06SV,0.0HDOP,04,3.5
+GPSPVT: 3,1,1,[02,U,03],[04,U,04],[09,U,04],[12,U,04],[14,U,03],[32,U,03]
+GPSPVT: 1,000.0deg,000m/s
+GPSPVT: 2,06SV,0.0HDOP,28,19.7
+GPSPVT: 3,1,1,[02,U,11],[04,U,19],[09,U,16],[12,U,23],[14,U,28],[32,U,21]
…
Warning: The +GPSEVSTART: 1 event is sent only if the GPS firmware has been successfully loaded. This
may take several seconds.
4.1.4.1. Description
The current setting is stored in FLASH memory as the new default settings when the command
+GPSSAVE=1 is entered. All the parameters of +GPS AT commands are saved. These settings will
be used after each Embedded Module reset as default configuration.
If the user wants the application to retrieve the default factory configuration (refer to each Location AT
command description), the command AT+GPSSAVE = 0 should be given and the Embedded Module
should be reset.
The application state is also saved as default configuration and used at the start (after the Embedded
Module reset) to put the application in this state. This configuration is used for the automatic start.
Note: The AT port where unsolicited Location AT command responses are sent is also saved with +GPSSAVE
AT command.
4.1.4.2. Syntax
Action command
AT+GPSSAVE= <mode>
OK
Read command
AT+GPSSAVE?
+GPSSAVE:<mode>
OK
Test command
AT+GPSSAVE=?
+GPSSAVE: (list of supported <mode>s)
OK
0 The application should reset all settings to their factory default values for the
next Embedded Module reset.
1 The application should save the current settings as new default settings. If the
Embedded Module is reset, the application uses those settings at restart.
4.1.4.4. Examples
Command Responses
AT+GPSSAVE? +GPSSAVE: 0
OK
Note: 0 if no saved settings or 1 if settings have been saved.
AT+GPSSAVE=1 OK
Note: The current settings are saved. or
+GPS ERROR: X
Note: For more information about X value, please refer to Location AT
commands error codes description.
AT+GPSSAVE=?
+GPSSAVE: (0-1)
OK
Location AT application
started
+GPSSAVE?
(Does Location Application +GPSSAVE: 1
+GPSSAVE: 0
Flash Object exist?) (YES)
(NO)
Note: The factory default values are described for each field in tables describing Location AT commands.
Note: If +GPSSAVE already equals 1 and a setting is modified through an AT command (for example
+GPSCONF), the modified setting is not saved until the +GPSSAVE=1 command is entered.
Note: The configuration of current session can be retrieved with the read command of each +GPS AT
command, for example “AT+GPSCONF?”.
4.1.5.1. Description
This AT command starts the GPS or restarts the GPS after the +GPSSTOP or +GPSSLEEP
command. The input parameter specifies the type of START command.
When AT+GPSSTART (without parameter) is entered, the GPS starts with the last known starting mode
value within current session. That starting mode can be retrieved using “+GPSTART?” read command.
OK is returned if the request has been processed. The final result will be sent to the associated event
through an unsolicited response after the action has been completed.
4.1.5.2. Syntax
Action command
AT+GPSSTART= [<starting_mode>]
OK
Read command
AT+GPSSTART?
+GPSSTART:<starting_mode>
OK
Test command
AT+GPSSTART=?
+GPSSTART: (list of supported <starting_mode>s)
OK
Unsolicited response
+GPSEVSTART: <status>
<starting_mode>: The parameter specifies the GPS starting mode of the application. These
starting modes are used for test purposes.
If omitted: last known value within current session.
Factory default value: 0.
2 "COLD" start with NO previous NV store data except calibration data, updated
Almanac, and Extended Ephemeris if available. Time and last location are
unknown.
3 "FACTCOLD" start with Factory Default Data instead of previous run data.
Note: GPS Data are stored to NV memory during specific Location Services Application transition.
Note: [] gpsOne: For WARM, COLD and FACTORY commanded Starting Modes, a HOT Starting Mode
could be performed if the duration between stop and start transitions is too short. In that case, the
“+GPSEVERROR: -23,9” error event will be received. Recommended value for that duration is 80
seconds.
4.1.5.4. Examples
Command Responses
AT+GPSSTART? +GPSSTART: 0
OK
Note: The current starting mode is the “HOT” start.
AT+GPSSTART=1 OK
+GPSEVSTART: 1
Note: Starts GPS in WARM mode. or
+GPS ERROR: X
Note: For more information about X value, please refer to Location AT
commands error codes description.
4.2.1.1. Description
This AT command returns the current application state.
4.2.1.2. Syntax
Read command
AT+GPSSTATE?
+GPSSTATE:<state>
OK
Test command
AT+GPSSTATE=?
OK
4.2.1.4. Examples
Command Responses
AT+GPSSTATE? +GPSSTATE: 0
OK
AT+GPSSTATE=? OK
4.2.2.1. Description
This AT command initializes the Location Services. It is accepted only if application is in
GPS_UNINITIALIZED state. It allows specifying the hardware setup of the system.
Some predefined setups (Hardware Configuration) are available for ease of use.
If this command is omitted, last saved hardware setup is used. If no hardware setup was saved,
default factory configuration is used.
OK is returned if the request has been processed. The final result will be sent to the associated event
through an unsolicited response after the request has been processed.
4.2.2.2. Syntax
Action command
AT+GPSINIT= <hw>
[,<bus_type>,<bus_number>,<on_off>,<reset>,<gps_wakeup>,<host_wakeup>,<clock32k>,<a
ppli_led>]
OK
Read command
AT+GPSINIT?
+GPSINIT:<hw>,<bus_type>,<bus_number>,<on_off>,<reset>,<gps_wakeup>,
<host_wakeup>,<clock32k>,<appli_led>
OK
Test command
AT+GPSINIT=?
+GPSINIT: (list of supported <hw>s), (list of supported <bus_type>s), (list of
supported <bus_number>s), (list of supported <on_off>s),(list of supported < reset
>s),(list of supported <gps_wakeup>s),(list of supported <host_wakeup >s),(list of
supported <clock32k>s),(list of supported <appli_led>s)
OK
Unsolicited response
+GPSEVINIT: <status>
<hw >: Hardware value: Hardware Type or Hardware Configuration for initialization.
If a Hardware Configuration is provided, no other parameter can be specified.
If a Hardware Type is provided, the other hardware settings should be specified or
previously specified parameters apply.
See the Hardware Configuration section for more details on default hardware settings.
1 UART
2 I2C
1 Bus number 1
2 Bus number 2, for example UART2 (if a UART bus type is selected)
Range: 0-65535
In case the user intends to manage GPS receiver power up/power down on its own
(i.e., independently of +GPSSTART and +GPSSTOP command), then the
parameter shall be set to 65535.
Range: 0-65535
Range: 0-65535
In case GPS receiver wake-up is not to be driven by a dedicated GPIO, parameter
must be set to 65535.
Note: For UART bus type, 65535 is the only accepted value. For I2C, 65535 is
not accepted, a GPIO must be specified.
<host_wakeup>: Host Wakeup external interrupt input ID / External Interrupt number
Range: 0-65535
In case application Led is not to be driven by a GPIO, parameter must be set to
65535.
In case application Led GPIO is to be automatically selected by the Location AT
application upon Embedded Module type, parameter must be set to 65534. In this
case the application Led GPIO is forced to GPIO31 for the Q26/WMP Embedded
Modules and GPIO20 for the SL6087 Embedded Module.
4.2.2.4. Examples
Command Responses
AT+GPSINIT? +GPSINIT:
1,1,2,22,23,65535,65535,1,65534
OK
Note: [] Default configuration response for XM0110
AT+GPSINIT=1 OK
Note: For default configuration applied on XM0110 +GPSEVINIT: 1
or
+GPS ERROR: X
Note: For more information about X value, please
refer to Location AT commands error codes
description.
AT+GPSINIT=11 OK
Note: [] For XM0110 Dev Kit DB V2 HW settings for UART +GPSEVINIT: 1
or
+GPS ERROR: X
Note: For more information about X value, please
refer to Location AT commands error codes
description.
Command Responses
AT+GPSINIT=2 OK
Note: [] Example for gpsOne +GPSEVINIT: 1
or
+GPS ERROR: X
Note: For more information about X
value, please refer to Location AT
commands error codes description.
AT+GPSINIT=30 OK
Note: [] Example for SiRFV +GPSEVINIT: 1
or
+GPS ERROR: X
Note: For more information about X
value, please refer to Location AT
commands error codes description.
AT+GPSINIT=1,1,2,22,23,65535,0,1,65534 OK
Note: [] XM0110: For same HW settings as Hardware Configuration +GPSEVINIT: 1
11 but with INT0 as host wake-up interrupt.
or
+GPS ERROR: X
Note: For more information about X value, please
refer to Location AT commands error codes
description.
Hardware Type 1
(<hw>=1), or Hardware Hardware
Hardware Configuration 13 Configuration 10
Configuration 11 (<hw>=13) (<hw>=10)
(<hw>=11)
XM0110 Dev Kit DB XM0110 Dev Kit DB Old XM0110 Dev Kit DB
Hardware setup (WM0701201-23-2X) (WM0701201-23-2X) (WM0701201-23-10)
compatibility
for UART. for I2C for UART.
<hw> 1 1 1
Hardware Type 1
(<hw>=1), or Hardware Hardware
Hardware Configuration 13 Configuration 10
Configuration 11 (<hw>=13) (<hw>=10)
(<hw>=11)
<bus_type> 1 2 1
<bus_number> 2 1 2
<on_off> 22 22 22
<reset> 23 23 19
<gps_wakeup> 65535 (Not managed) 24 65535 (Not managed)
<host_wakeup> 65535 (Not managed) 65535 (Not managed) 65535 (Not managed)
<clock32k> 1 1 1
65534 (GPIO
65534 (GPIO automatically
automatically selected
selected depending on
depending on embedded
<appli_led> embedded module type: 20
module type: GPIO31 for
GPIO31 for Q26/WMP and
Q26/WMP and GPIO20
GPIO20 for SL6087).
for SL6087).
Note: The following Hardware Configuration is obsolete:
<hw>=12 (XM0110 Dev Kit DB V2 WM0701201-23-10 + SL6087 Dev Kit + UART config.)
<hw>=11 should now be used for this hardware setup.
Hardware setup
AR6220-G Embedded Module
compatibility
<hw> 3
<bus_type> 1
<bus_number> 2
<on_off> 101 (Internal GPIO)
<reset> 100 (Internal GPIO)
<gps_wakeup> 65535 (Not managed)
4.2.3.1. Description
This AT command stops the Location Services.
OK is returned if the request has been processed. The final result will be sent to the associated event
through an unsolicited response after the action has been completed.
GPS Data are stored to NV memory during specific Location Services Application transitions.
4.2.3.2. Syntax
Action command
AT+GPSSTOP
OK
Test command
AT+GPSSTOP=?
OK
Unsolicited response
+GPSEVSTOP: <status>
4.2.3.4. Examples
Command Responses
AT+GPSSTOP OK
+GPSEVSTOP: 1
or
+GPS ERROR: X
Note: For more information about X value, please refer to Location AT
commands error codes description.
AT+GPSSTOP=?
OK
4.2.4.1. Description
This AT command puts the GPS receiver into the specified GPS sleep mode.
This command stops the GPS processing and put the GPS receiver in a low power mode. This
consumes slightly more power than complete off mode, but allows faster restarts when the GPS is
restarted with the +GPSSTART command.
OK is returned if the request has been processed. The final result will be sent to the associated event
through an unsolicited response after the action has been completed.
GPS Data are stored to NV memory during specific Location Services Application transitions.
Note: [] gpsOne: +GPSSLEEP AT command is supported but without effect on power consumption.
4.2.4.2. Syntax
Action command
AT+GPSSLEEP = [<sleep_mode>]
OK
Read command
AT+GPSSLEEP?
+GPSSLEEP:<sleep_mode>
OK
Test command
AT+GPSSLEEP=?
Unsolicited response
+GPSEVSLEEP: <status>
Note: [] For XM0110 and SiRFV: GPS 3D fix is needed to switch in IDLE mode. If 20 seconds after the
command was sent, if the GPS receiver has not been capable to switch to IDLE mode, the event
+GPSEVSLEEP: 0 will be received.
4.2.4.4. Examples
Command Responses
AT+GPSSLEEP OK
+GPSEVSLEEP: 1
or
+GPS ERROR: X
Note: For more information about X value, please refer to Location AT
commands error codes description.
4.2.5.1. Description
This command reports the calculated TTFF (2-Dimensional Position Fix and 3-Dimensional Position
Fix) of the last run if no new run has started, an error if the current run has no fix yet, or the calculated
TTFF of this run if it has fixed.
Note: 2D TTFF value can be equal to 3D TTFF value if 3-Dimensional Position is directly fixed. This is
subjected to GPS conditions.
Note: GPS_ERR_GPS_POS_NOT_FIXED (-30) is returned if the current run is not fixed.
4.2.5.2. Syntax
Read command
AT+GPSTTFF?
+GPSTTFF:<2D_time>,<3D_time>
OK
Test command
AT+GPSTTFF=?
OK
4.2.5.4. Examples
Command Responses
Command Responses
AT+GPSTTFF=? OK
4.2.6.1. Description
This AT Command releases the Location Services hardware and software resources.
OK is returned if the request has been processed. The final result will be sent to the associated event
through an unsolicited response after the action has been completed.
4.2.6.2. Syntax
Action command
AT+GPSRELEASE
OK
Test command
AT+GPSRELEASE=?
OK
Unsolicited response
+GPSEVRELEASE: <status>
4.2.6.4. Examples
Command Responses
AT+GPSRELASE OK
+GPSEVRELEASE: 1
or
+GPS ERROR: X
Note: For more information about X value, please refer to Location AT
commands error codes description.
AT+GPSRELEASE=?
OK
4.2.7.1. Description
This AT Command reports the Software Version of the Location AT command set.
4.2.7.2. Syntax
Read command
AT+GPSVERS?
+GPSVERS:<version>
OK
Test command
AT+GPSVERS=?
OK
4.2.7.4. Examples
Command Responses
AT+GPSVERS=?
OK
4.2.8.1. Description
This AT command configures the Location service and GPS receiver.
4.2.8.2. Syntax
Action command
AT+GPSCONF= <config_type>,<config_value>
OK
Read command
AT+GPSCONF?
+GPSCONF: <config_type>,<config_value>
[+GPSCONF: <config_type>,<config_value>]
OK
Test command
AT+GPSCONF=?
+GPSCONF:<config_type>,(list of supported <config_value>s)
[+GPSCONF:<config_type>,(list of supported <config_value>s)]
OK
<config_type>: This parameter specifies the configuration type on which the configuration value is
applied.
0 Sets GPS navigation low power modes. Reduces power consumption while in
GPS_RUNNING state without impacting update rate, but at the expense of GPS
accuracy degradation. Please refer to [2] for more details about the navigation low
power modes.
3 Configures the host Wakeup software mechanism allowing the Location Library to
be compatible with the Embedded Module sleep mode.
4 Defines the banking time. This option is used only for debug purpose.
For <config_type> = 0 If omitted: last known value within current session. Please refer to Diagram for
settings management for more information.
Factory default value: 0.
For <config_type> = 1 If omitted: last known value within current session. Please refer to Diagram for
settings management for more information.
Factory default value: 1.
0: Receive chain optimized for internal LNA, and GPS receiver LNA_EN output signal
is automatically driven.
1: Receive chain optimized for external LNA, and GPS receiver LNA_EN output signal
is automatically driven.
2: Receive chain optimized for internal LNA, and GPS receiver LNA_EN output signal
is always OFF.
3: Receive chain optimized for external LNA, and GPS receiver LNA_EN output signal
is always OFF.
For <config_type> = 2 If omitted: last known value within current session. Please refer to Diagram for
settings management for more information.
Factory default value: 0.
For <config_type> = 3 If omitted: last known value within current session. Please refer to Diagram for
settings management for more information.
Factory default value: 0.
For <config_type> = 4 Specifies the number of seconds to wait before disabling AEE calculation.
If omitted: last known value within current session. Please refer to Diagram for
settings management for more information.
Factory default value: -1.If -1, the banking time is not taken account.
If 0, the AEE calculation will be stopped immediately.
For <config_type> = 5 Defines the targeted Reduced Rate GPS Navigation in seconds.
If omitted: last known value within current session. Please refer to Diagram for
settings management for more information.
Factory default value: 1.
0: TX Blanking disabled.
1: TX Blanking activated.
If omitted: last known value within current session. Please refer to Diagram for
settings management for more information.
If omitted: last known value within current session. Please refer to Diagram for
settings management for more information. If value has been changed,
+GPSSAVE=1 AT Command must be send, and reset must be issued after
using this command.
Factory default value: 1.
Note: [] gpsOne: RESET must be issued after this option is configured.
Note: For <config_type>3 (host Wakeup software mechanism configuration), the host Wakeup external
interrupt input must be specified through the +GPSINIT AT command before the activation of this option,
otherwise the error GPS_ERR_SERVICE (-26) will be returned by the +GPSCONF AT command.
Note: For <config_type>=4, the value is applied at each +GPSSTART AT command. Therefore the banking
time is reinitialized for GPS_INITIALIZED & GPS_SLEEP state to GPS_RUNNING state transition.
Note: For <config_type>=5, <config_value> defines the targeted Reduced Rate GPS Navigation. The applied
Rate GPS Navigation can be lower than targeted value in order to maintain best GPS navigation
conditions. Applied Rate GPS Navigation depends on GPS conditions and could be changed
automatically from minimum value (1 second) to targeted <config_value>.
Note: For <config_type>=5, <config_value> impacts NMEA frames update rate specified by +GPSNMEA AT
command, PVT frames update rate specified by +GPSPVT AT command and Core information update
rate specified by +GPSCORE AT command as those options are based on this Reduced Rate GPS
Navigation. For example, if <config_value> is equal to 2, the NMEA frames update rate and PVT frames
update rate will be typically doubled.
Note: For <config_type>=6, the blanking is automatically disabled every time the state machine goes to
GPS_RUNNING.
Note: For <config_type>=7, for [] XM0110, the setting of CW removal is automatically disabled every time the
state machine goes to GPS_RUNNING. The user has to set it again a few seconds after start event. This
parameter is not restored by the +GPSSAVE AT Command.
GPS_HIBERNATE_MODE
Option
GPS_INITIALIZED
GPS_IDLE_MODE
GPS_RUNNING
GPS_SLEEP /
GPS_SLEEP /
<config_type> = 0 (Nav mode) Allowed Allowed Allowed Allowed
<config_type> = 2 (Aiding
Not allowed Not allowed Allowed Allowed
mode)
<config_type> = 3 (Host
Not allowed Not allowed Allowed Allowed
wakeup)
<config_type> = 4 (Banking
Not allowed Not allowed Allowed Allowed
time)
<config_type> = 5 (Reduced
Allowed Allowed Allowed Allowed
Rate)
<config_type> = 7 (CW
Allowed Not allowed Not allowed Not allowed
removal) for [] XM0110
<config_type> = 7 (CW
Allowed Allowed Allowed Allowed
removal) for [] SiRFV
<config_type> = 8 (GPS
Allowed Allowed Allowed Not allowed
enabled)
4.2.8.5. Examples
AT+GPSCONF=0,0 OK OK
or or
Note: request continuous navigation +GPS ERROR: X +GPS ERROR: X
mode.
Note: For more information about X Note: For more information about X
value, please refer to Location AT value, please refer to Location AT
commands error codes description. commands error codes description.
4.2.9.1. Description
This AT command configures the debug mode and the output port of the debug data.
4.2.9.2. Syntax
Action command
AT+GPSDEBUG= <output>,<debug_data>
OK
Read command
AT+GPSDEBUG?
+GPSDEBUG: <output>,<debug_data>
OK
Test command
AT+GPSDEBUG=?
+GPSDEBUG: (list of supported <output>s),(list of supported <debug_data>s)
OK
<output>: This parameter specifies the port which is to be used by the application to transmit
the raw data. (Hexadecimal value entered without the prefix “0x”).
If omitted: last known value within current session. Please refer to Diagram for
settings management for more information.
Factory default value: 0.
0x1X CMUX virtual port, Logical ports over UART1 where 1 <= X <=4
0x2X CMUX virtual port, Logical ports over UART2 where 1 <= X <=4
0x5X CMUX virtual port, Logical ports over UART3 where 1 <= X <=4
(1<<0) Raw data activated. The raw data are used only for GPS debug purpose.
(1<<1) Debug Core information activated. The debug core information is used only for
debug purposes.
Debug Core information is received through Developer Studio Trace level 2.
Note: Raw data output, due to its binary format, requires the use of the port in the exclusive online mode. No
AT command can be entered or received on same port The specified port (<output> parameter) must
then be different from the port which is to be used by the application to transmit the NMEA frames
(configured by the +GPSNMEA command).
Note: The production mode must be set to receive consistent Raw Data flow. Consequently, Raw Data and
Debug Core information (received through Developer Studio Trace level 2) cannot be received
simultaneously.
4.2.9.4. Examples
Command Responses
AT+GPSDEBUG=3,1 OK
or
Note: request raw data output on port 3 (USB). +GPS ERROR: X
Note: For more information about X value, please refer to Location AT
commands error codes description.
AT+GPSDEBUG=3,0 OK
or
Note: disable raw data output. +GPS ERROR: X
Note: For more information about X value, please refer to Location AT
command error codes description.
AT+GPSDEBUG=0,2 OK
or
Note : Activates Debug Core Information on +GPS ERROR: X
Developer Studio Traces.
Note: For more information about X value, please refer to Location AT
command error codes description.
AT+GPSDEBUG?
+GPSDEBUG: 0,0
4.2.10.2.1. Foreword
Intention has been to limit as much as possible the Location Library GPS Aiding Service AT
commands changes while porting to gpsOne GPS solution. As a consequence some terminology
may not be as accurate as it could be when considering gpsOne iso XM010/SiRFV GPS solution. For
example, “Assistance data” or “Predicted Orbit data” would have been more appropriate than
Downloaded Extended Ephemeris as in gpsOne case those data are not only Ephemeris.
Three servers are provided (URLs set by default) so that the requests are load balanced. XTRA
Servers and XTRA data are fully hosted by QCT and provided as free service.
XTRA Data is downloaded using an http get as a binary file that must be injected into the gpsOne
GPS Engine.
Note: []gpsOne – SL3010T: file system is used for gpsOneXTRA feature. When DEE is downloaded, a file
“xtra.bin” is created in “\location” folder. This file should not be removed as it is used in injection process.
4.2.10.3. Syntax
For <config_type> = 0
Action command
AT+GPSAID=<config_type>,<aee_mode>
OK
For <config_type> = 1
Action command
AT+GPSAID=<config_type>,<dee_mode>[, [<dee_period>] [,[<dee_server_address>]
[,[<dee_server_port>]
[,[<dee_server_code>][,[<dee_socket_type>][,[<dee_timeout>]]]]]]]
OK
For <config_type> = 2
Action command
AT+GPSAID=<config_type>,<dee_command>
OK
Action command
AT+GPSAID=<config_type>,<dee_server_type>,<dee_secondary_server_addr
ess>,<dee_tertiary_server_address>
OK
For <config_type> = 3 and <dee_server_type>=2
Action command
AT+GPSAID=<config_type>,<dee_server_type>,<dee_primary_sntp_server_a
ddress>,<dee_secondary_sntp_server_address>,<dee_tertiary_sntp_serve
r_address>
OK
Read command
AT+GPSAID?
+GPSAID: 0,<aee_mode>
+GPSAID: 1,<dee_mode>,
<dee_period>,<dee_server_address>,<dee_server_port>,<dee_server_code>,<dee_socket_t
ype>,<dee_timeout>
+GPSAID: 2,<dee_command>
+GPSAID: 3,1,<dee_secondary_server_address>,<dee_tertiary_server_address>
+GPSAID:
3,2,<dee_primary_sntp_server_address>,<dee_secondary_sntp__server_address>,
<dee_tertiary_sntp_server_address>
OK
Test command
AT+GPSAID=?
+GPSAID: 0,(list of supported <aee_mode>s)
+GPSAID: 1,(list of supported <dee_mode>s),(list of supported <dee_period>s),(list
of supported <dee_server_address>s),(list of supported <dee_server_port>s), (list
of supported <dee_server_code>s),(list of supported <dee_socket_type>s),(list of
supported <dee_timeout>s)
+GPSAID: 2,(list of supported <dee_command>s)
+GPSAID: 3,1,(list of supported <dee_secondary_server_address>s),(list of
supported <dee_tertiary_server_address>s)
+GPSAID: 3,2,(list of supported <dee_primary_sntp__server_address>s),(list
of supported <dee_secondary_sntp_server_address>s),(list of supported
<dee_tertiary_sntp_server_address>s)
OK
<config_type>: This parameter specifies the configuration type on which the configuration is applied.
0 AEE configuration.
1 DEE configuration.
2 DEE command.
<aee_mode>: This parameter specifies the AEE (Autonomous Extended Ephemeris) mode.
If omitted: last known value within current session. Please refer to Diagram for
settings management for more information.
Factory default value: 0.
0: AEE is deactivated.
1: AEE is activated.
<dee_mode>: This parameter specifies the DEE (Downloaded Extended Ephemeris) mode.
If omitted: last known value within current session. Please refer to Diagram for
settings management for more information.
Factory default value: 0.
Note: [] gpsOne: RESET must be issued after this option is configured.
0: DEE is deactivated.
1: DEE is activated.
Range: 0-65535
1: This command requests EE file download from a remote source and its injection.
3: This command forces EE file download from a remote source and its injection.
This command is used only for test purpose.
Note: [] gpsOne: That command is not supported and result will be similar to
<dee_command>=1.
4 This command forces EE file injection from a local source. The requirements
applied to that file are listed below:
- Files to be injected have to be stored in file system in “\location\fileName” path.
- DEE Validity of the file has to be coherent with parameter <dee_period>.
- In case of multi-constellations solution, there must be at least one DEE file
matching with the active constellations. If not,
GPS_AIDING_DEE_FILE_ERROR (-14) is raised
[] gpsOne – SL3010T: “FileName” must be “xtra.bin”.
[] SiRFV: “FileName” must have this form: XXX_YY.dee, with XXX the
constellation (GPS for GPS constellation and GLO for GLONASS constellation)
and YY the DEE validity in days (always coded on two digits and filled with a
preceding zero for single digit validity). For example, “FileName” can be
“GPS_07.dee”, or “GLO_14.dee”
Note: [] XM0110 and gpsOne – SL808xT, that command is not supported
<dee_server_type>: This parameter specifies the DEE server type on which the configuration is
applied.
Note: The main DEE server address is configured through the
<dee_server_address> parameter.
1: DEE Data Server(s)
Note: [] XM0110 and SiRFV: Before <dee_command> configuration, <dee_server_xxxx> parameters should
be configured.
Note: <dee_command> = 1 allows DEE file update as described hereunder:
Note: <dee_command> is automatically configured to 0 when the DEE file is updated. If the command is
pending, for example in GPS_INITIALIZED state, the read of this parameter returns the last entered DEE
command.
Note: If a newer DEE file is available on DEE server, DEE file download is performed. If no updated DEE file is
available on the DEE server, DEE file download is aborted. Consequently, the following event is
received:
Note: [] XM0110 and SiRFV: +GPSEVAID event will be received informing that DEE download is aborted
with abort cause equal to GPS_AIDING_DEE_NACK_ERROR.
Note: [] gpsOne: +GPSEVAID event will be received informing that DEE download is aborted with abort
cause equal to GPS_AIDING_OK.
Note: Factory start (please refer to GPSSTART section) removes DEE file. To retrieve it, DEE file download
should be requested once again.
GPS_HIBERNATE_MODE
Option
GPS_IDLE_MODE
GPS_NITIALIZED
GPS_RUNNING
GPS_SLEEP /
GPS_SLEEP /
<config_type> = 0 (AEE configuration) Allowed Not allowed Not allowed Allowed
(1) In this state that AT command is authorized but the configuration will become effective in “Allowed” state.
4.2.10.6. Examples
Command Responses
AT+GPSAID=0,1 OK
or
Note: activates the AEE mode. +GPS ERROR: X
Note: For more information about X value, please refer to Location AT commands error
codes description.
AT+GPSAID=1,1 OK
or
Note: activates the DEE mode. +GPS ERROR: X
Note: For more information about X value, please refer to
Location AT commands error codes description.
AT+GPSAID=2,1 OK
or
Note: requests EE file download. +GPS ERROR: X
Note: For more information about X value, please refer to
Location AT commands error codes description.
For more information regarding “Authorized” state(s), please refer to Aiding Service Configuration
Restrictions.
AT+GPSINIT=11
OK
+GPSEVINIT: 1
AT+GPSNMEA=0
OK
AT+GPSAID=2,1
OK
AT+GPSSTART=3
OK
+GPSEVAID: 1,1
+GPSEVSTART: 1
+GPSEVPOS: 0
+GPSEVAID: 1,2
+GPSEVPOS: 2
+GPSEVPOS: 3
+GPSEVAID: 1,4,0,3720
…
For more information regarding “Allowed” state(s), please refer to Aiding Service Configuration
Restrictions.
AT+GPSINIT=11
OK
+GPSEVINIT: 1
AT+GPSNMEA=0
OK
AT+GPSSTART=3
OK
+GPSEVSTART: 1
+GPSEVPOS: 0
AT+GPSAID=2,1
OK
+GPSEVAID: 1,1
+GPSEVAID: 1,2
+GPSEVPOS: 2
+GPSEVPOS: 3
+GPSEVAID: 1,4,0,3720
…
AT+CFUN=1 or HW reset
AT+GPSINIT=2
+GPSEVINIT: 1
AT+GPSAID=1,1
AT+GPSAID=2,1
+GPSEVAID: 1,2
+GPSEVAID: 1,4,1,yy/MM/dd,hh:mm:ss,yy/MM/dd,hh:mm:ss
AT+GPSSTART=3
OK
+GPSEVSTART: 1
+GPSEVPOS: 0
+GPSEVPOS: 3
…
4.2.11.1. Description
This AT command configures core information mode and the output port of the core information.
4.2.11.2. Syntax
Action command
AT+GPSCORE=[<output>][,[<rate>][,<core_info>]]
OK
Read command
AT+GPSCORE?
+GPSCORE: <output>,<rate>,<core_info>
OK
Test command
AT+GPSCORE=?
+GPSCORE: (list of supported <output>s) ,(list of supported <rate>s)
,(list of supported <core_info>s)
OK
<output>: This parameter specifies the port to be used by the application to transmit the core
information. (Hexadecimal value entered without the prefix “0x”).
If omitted: last known value within current session. Please refer to Diagram for
settings management for more information.
Factory default value: 0.
4 Core information output on port where the +GPSCORE command was received.
0x1X CMUX virtual port, Logical ports over UART1 where 1 <= X <=4
0x2X CMUX virtual port, Logical ports over UART2 where 1 <= X <=4
0x5X CMUX virtual port, Logical ports over UART3 where 1 <= X <=4
<rate>: This parameter defines the core information update rate in seconds.
If omitted: last known value within current session. Please refer to Diagram for
settings management for more information.
Factory default value: 1.
Range: 0-65535
Note: If this parameter equals 0, the core information frames will be sent only
once, on the next occurrence of the core information frames update.
Note: This parameter is impacted by the Reduced Rate GPS Navigation.
Please refer to +GPSCONF AT command for more information.
<core info>: Core information list encode mask. Hexadecimal value entered without the prefix
“0x”.
If omitted: last known value within current session. Please refer to Diagram for
settings management for more information.
Factory default value: 0.
[]< rate> parameter for this <core info> has no effect on SiRFV.
Note: Core information is received through +GPSEVCORE asynchronous event. Please refer to Asynchronous
Events for more information.
4.2.11.4. Examples
Command Responses
AT+GPSCORE=1,1,1 OK
or
Note: request jammers detection information +GPS ERROR: X
output on port 1.
Note: For more information about X value, please refer to Location AT
commands error codes description.
AT+GPSCORE=1,1,0 OK
or
Note: disable core information output. +GPS ERROR: X
Note: For more information about X value, please refer to Location AT
command error codes description.
AT+GPSCORE?
+GPSCORE: 0,1,0
+GPSEVINIT: 1
AT+GPSNMEA=0
OK
AT+GPSCORE=1,1,1
OK
AT+GPSSTART=3
OK
+GPSEVSTART: 1
+GPSEVPOS: 0
+GPSEVCORE: 0,0000,00,0000,00,0000,00,0000,00,0000,00,0000,00,0000,00,1575,65
+GPSEVCORE: 0,1575,77,0000,00,0000,00,0000,00,0000,00,0000,00,0000,00,0000,00
+GPSEVCORE: 0,1575,76,0000,00,0000,00,0000,00,0000,00,0000,00,0000,00,0000,00
+GPSEVCORE: 1,602,73,0000,00,0000,00,0000,00,0000,00,0000,00,0000,00,0000,00
Note: [] +GPSEVCORE event with GLONASS information is only available on SiRFV
4.3.1. Description
The following asynchronous events can be received as unsolicited responses:
+GPSEVABORT: Following error detection, the Location Services are aborted and the application is
stopped. After this event the application state is automatically changed to GPS_INITIALIZED.
+GPSEVERROR: An error has been detected. Please refer to Location AT commands error codes for
more details.
+GPSEVAID: Describes Aiding events and related information.
+GPSEVAIDERROR: An error has been detected for Aiding modes. Please refer to Aiding Event
Error Codes for more details.
The others events are associated to the following AT Commands described in this document:
+GPSINIT, +GPSSTART, +GPSSTOP, +GPSSLEEP and +GPSRELEASE.
4.3.2. Syntax
Unsolicited response
+GPSEVPOS: <pos_event>
Unsolicited response
+GPSEVABORT: <abort_cause>
Unsolicited response
+GPSEVERROR: <error>,<ext_error>
Unsolicited response
+GPSEVINIT: <status>
Unsolicited response
+GPSEVSTART: <status>
Unsolicited response
+GPSEVSTOP: <status>
Unsolicited response
+GPSEVSLEEP: <status>
Unsolicited response
+GPSEVRELEASE: <status>
Unsolicited response
+GPSEVAID: <aid_mode>,<aid_event>
Unsolicited response
+GPSEVAID: <aid_mode>,<aid_event>,<aee_svid>,<aee_svValidity>
Unsolicited response
+GPSEVAID: <aid_mode>,<aid_event>,<dee_abort_cause>
Unsolicited response
+GPSEVAID: <aid_mode>,<aid_event>,<dee_validity_format>,<dee_validity_duration>
Unsolicited response
+GPSEVAID:
<aid_mode>,<aid_event>,<dee_validity_format>,<dee_validity_start>,<dee_validity_end
>
Unsolicited response
+GPSEVAIDERROR: <aid_error>,<aid_ext_error>
For <core_info> = 0
Unsolicited response
+GPSEVCORE:
<core_info>,<jam_freq_1>,<jam_lev_1>,<jam_freq_2>,<jam_lev_2>,<jam_freq_3>,<jam_lev
_3>,<jam_freq_4>,<jam_lev_4>,<jam_freq_5>,<jam_lev_5>,<jam_freq_6>,<jam_lev_6>,<jam
_freq_7>,<jam_lev_7>,<jam_freq_8>,<jam_lev_8>
<pos_event>
1 GPS fix state has been changed to estimated (i.e. forward predicted) Position.
<aid_event>
For <aid_mode>=0
2 AEE information
For <aid_mode>=1
0 DEE is stopped
1 DEE is started
2 DEE is valid
3 DEE is aborted
Note: [] XM0110: That information is available if the DEE is valid and if
GPS position is known.
Note: Available for <dee_validity_format> = 0.
<dee_validity_start> DEE Validity UTC Start timestamp with the format “yy/MM/dd,hh:mm:ss”.
Note: The GPS_AIDING_DEE_NACK_ERROR error is received if no updated file is available on the DEE
server. The download procedure is indeed stopped if the DDE file previously downloaded and stored to
the Non-Volatile Store media (Embedded Module FLASH memory) is identical to the available DEE file
from the DEE server.
5.1.1.1. Description
This AT command initializes the Security Library. This command must always be called as the first
command. All values are set to default, as explained in subsection 5.1.2.3.
5.1.1.2. Syntax
Action command
AT+SSLINIT
OK
Read command
AT+SSLINIT?
OK
Test command
AT+SSLINIT=?
OK
5.1.1.4. Examples
Command Responses
AT+SSLINIT
OK
Note: Initializes the Security Library.
5.1.2.1. Description
This AT command configures the parameters for TLS/SSL connection before opening the connection.
If a parameter is not explicitly set, the default value will be used. Please note that the default values
are set to a recommended value.
5.1.2.2. Syntax
For <option> values 0, 1 and 2.
Action command
AT+SSLSET=<option>,<optionvalue>[,<password>]
OK
Action command
AT+SSLSET=<option>,<optionvalue>
OK
Read command
AT+SSLSET?
+SSLSET: <option>,<optionvalue>
[+SSLSET: <option>,<optionvalue>]
OK
Test command
AT+SSLSET=?
+SSLSET: <option>,(range for <optionvalue>)
OK
The password needed to access the directory containing the file. string -
5.1.2.4. Examples
Command Responses
AT+SSLSET=0,"/dir/client-cert.pem"
OK
Note: Set the path to the Client Certificate file that is already
present in the file system.
AT+SSLSET=1,"/dir/ca.pem"
OK
Note: Set the path to the CA file that is already present in the file
system.
AT+SSLSET=2,"/dir/client-key.pem"
OK
Note: Set the path to the Client Private Key that is already present
in the file system..
AT+SSLSET=3,"randomstring123456789"
OK
AT+SSLSET=4,1
OK
AT+SSLSET=5,0
OK
AT+SSLSET=6,1
OK
AT+SSLSET=7,5
OK
Command Responses
AT+SSLSET=8,3
OK
AT+SSLSET=9,3
OK
AT+SSLSET=10,1
OK
5.1.3.1. Description
This AT command sets all parameters previously provided via AT+SSLSET. If the command is
successfully called in state SSL_INITLIALIZED, the state changes to SSL_PARAMETRIZED.
5.1.3.2. Syntax
Action command
AT+SSLSETOPTS
OK
Read command
AT+SSLSETOPTS?
OK
Test command
AT+SSLSETOPTS=?
OK
5.1.4.1. Description
This AT command closes the library and frees the associated resources. After this is called all settings
previously set will be reset to default values. State will be SSL_UNINITIALIZED after this command is
successfully called.
5.1.4.2. Syntax
Action command
AT+SSLRELEASE
OK
Read command
AT+SSLRELEASE?
OK
Test command
AT+SSLRELEASE=?
OK
5.1.4.4. Examples
Command Responses
AT+SSLRELEASE OK
Note: Frees all resources and resets all parameters.
5.1.5.1. Description
This AT command will return the state.
5.1.5.2. Syntax
Action command
AT+SSLSTATE
+SSLSTATE: <state>
OK
Read command
AT+SSLSTATE?
OK
Test command
AT+SSLSTATE=?
OK
0 SSL_UNINITIALIZED
1 SSL_INITIALIZED
2 SSL_CONNECTED
3 SSL_PARAMETRIZED
5.1.5.4. Examples
Command Responses
AT+SSLSTATE 0
OK
5.1.6.1. Description
This AT command boosts the system to give extra calculation power during the SSL connection.
More specifically, it takes control of the Varispeed service, boosts the CPU speed, and then disables
the Software watchdog.
5.1.6.2. Syntax
Action command
AT+SSLBOOST=<option>
OK
Read command
AT+SSLBOOST?
+SSLBOOST: <option>
OK
Test command
AT+SSLBOOST=?
+SSLBOOST: (range for <option>)
OK
5.1.6.4. Examples
Command Responses
AT+SSLBOOST=0 OK
Note: Disables SSL BOOST.
Command Responses
AT+SSLBOOST=1
OK
Note: Enables SSL BOOST.
5.1.7.1. Description
This AT command displays the underlying versions of different system.
5.1.7.2. Syntax
Action command
AT+SSLVERSION=<option>
+SSLVERSION: (version string)
OK
Read command
AT+SSLVERSION?
OK
Test command
AT+SSLVERSION=?
+SSLVERSION: (range for <option>)
OK
5.1.7.4. Examples
Command Responses
OK
OK in success
ADL_RET_ERR_NOT_SUPPORTED if the Sierra Wireless stack does not support the network scan
networkscan_Unsubscribe
This API has to be used to unsubscribe from the Network Scan Library.
void networkscan_Unsubscribe ( void );
Command Answers
[PLMN:<PlmnName>,MCC:<MCC>,MNC:<MNC>,CellNb:<CellNb>,Mea
nPower:<MeanPower>
1:Arfcn:<ARFCN>,Bsic:<Bsic>,Lac:<Lac>,Rxlev:<Rxlev>,Qual:<Qual>,S
tatus:<Status>
[2:Arfcn:<ARFCN>,Bsic:<Bsic>,Lac:<Lac>,Rxlev:<Rxlev>,Qual:<Qual>,
Status:<Status>
AT+NWKSCAN
[...]]
Note: <RequestedCellNb> and
[PLMN:<PlmnName>,MCC:<MCC>,MNC:<MNC>,CellNb:<CellNb>,Mea
<Format> parameters are omitted.
nPower:<MeanPower>
Default value: <RequestedCellNb> =
1:Arfcn:<ARFCN>,Bsic:<Bsic>,Lac:<Lac>,Rxlev:<Rxlev>,Qual:<Qual>,S
7 and <Format> = 0
tatus:<Status>
[2:Arfcn:<ARFCN>,Bsic:<Bsic>,Lac:<Lac>,Rxlev:<Rxlev>,Qual:<Qual>,
Status:<Status>
[...]]
[...]
OK
[PLMN:<PlmnName>,MCC:<MCC>,MNC:<MNC>,CellNb:<CellNb>,Mea
nPower:<MeanPower>
1:Arfcn:<ARFCN>,Bsic:<Bsic>,Lac:<Lac>,Rxlev:<Rxlev>,Qual:<Qual>,S
tatus:<Status>
[2:Arfcn:<ARFCN>,Bsic:<Bsic>,Lac:<Lac>,Rxlev:<Rxlev>,Qual:<Qual>,
Status:<Status>
AT+NWKSCAN=<RequestedCellNb> [...]]
[,<Format>] [PLMN:<PlmnName>,MCC:<MCC>,MNC:<MNC>,CellNb:<CellNb>,Mea
Note: <Format> parameter = 0 or nPower:<MeanPower>
omitted 1:Arfcn:<ARFCN>,Bsic:<Bsic>,Lac:<Lac>,Rxlev:<Rxlev>,Qual:<Qual>,S
tatus:<Status>
[2:Arfcn:<ARFCN>,Bsic:<Bsic>,Lac:<Lac>,Rxlev:<Rxlev>,Qual:<Qual>,
Status:<Status>
[...]]
[...]
OK
[<PlmnName>,<MCC>,<MNC>,<CellNb>,<MeanPower>
<ARFCN>,<Bsic>,<Lac>,<Rxlev>,<Qual>,<Status>
[<ARFCN>,<Bsic>,<Lac>,<Rxlev>,<Qual>,<Status>
[...]]
AT+NWKSCAN=<RequestedCellNb>
[<PlmnName>,<MCC>,<MNC>,<CellNb>,<MeanPower>
[,<Format>]
<ARFCN>,<Bsic>,<Lac>,<Rxlev>,<Qual>,<Status>
Note: <Format> parameter = 1
[<ARFCN>,<Bsic>,<Lac>,<Rxlev>,<Qual>,<Status>
[...]]
[...]
OK
AT+NWKSCAN=<RequestedCellNb> [<PlmnName>,<CellNb>,<MeanPower>
[,<Format>] [<PlmnName>,<CellNb>,<MeanPower>
Note: <Format> parameter = 2 [...]]]
(Synthesis) OK
Values Default
Parameter Description
range value
Values Default
Parameter Description
range value
The PLMN are returned by decreasing <CellNb> parameter values and, then, by decreasing
<MeanPower> parameter values.
For one PLMN, the returned cells are listed by decreasing <RxLev> parameter values.
The estimated maximum treatment time for this command is around 2 minutes.
6.4. Examples
Command Answers
PLMN:"SFR",MCC:208,MNC:10,CellNb:8,MeanPower:30
1:Arfcn:1020,Bsic:31,Lac:8,RxLev:38,Qual:0,Status:SUITABLE
2:Arfcn:1008,Bsic:32,Lac:9,RxLev:33,Qual:1,Status:SUITABLE
3:Arfcn:1009,Bsic:33,Lac:10,RxLev:32,Qual:2,Status:SUITABLE
4:Arfcn:1003,Bsic:34,Lac:11,RxLev:29,Qual:1,Status:SUITABLE
5:Arfcn:792,Bsic:35,Lac:12,RxLev:27,Qual:1,Status:SUITABLE
6:Arfcn:790,Bsic:36,Lac:13,RxLev:26,Qual:2,Status:SUITABLE
7:Arfcn:1013,Bsic:37,Lac:14,RxLev:26,Qual:1,Status:SUITABLE
PLMN:"Orange F",MCC:208,MNC:01,CellNb:7,MeanPower:26
AT+NWKSCAN
1:Arfcn:32,Bsic:1,Lac:1,RxLev:35,Qual:0,Status:SUITABLE
2:Arfcn:8,Bsic:2,Lac:2,RxLev:35,Qual:1,Status:SUITABLE
3:Arfcn:10,Bsic:3,Lac:3,RxLev:27,Qual:0,Status:SUITABLE
4:Arfcn:17,Bsic:4,Lac:4,RxLev:26,Qual:2,Status:SUITABLE
5:Arfcn:48,Bsic:5,Lac:5,RxLev:24,Qual:0,Status:SUITABLE
6:Arfcn:539,Bsic:6,Lac:6,RxLev:22,Qual:1,Status:SUITABLE
7:Arfcn:550,Bsic:7,Lac:7,RxLev:20,Qual:2,Status:SUITABLE
OK
Note: Request 7 cells per PLMN in text format
PLMN:"SFR",MCC:208,MNC:10,CellNb:8,MeanPower:30
1:Arfcn:1020,Bsic:31,Lac:8,RxLev:38,Qual:0,Status:SUITABLE
2:Arfcn:1008,Bsic:32,Lac:9,RxLev:33,Qual:1,Status:SUITABLE
3:Arfcn:1009,Bsic:33,Lac:10,RxLev:32,Qual:2,Status:SUITABLE
4:Arfcn:1003,Bsic:34,Lac:11,RxLev:29,Qual:1,Status:SUITABLE
5:Arfcn:792,Bsic:35,Lac:12,RxLev:27,Qual:1,Status:SUITABLE
6:Arfcn:790,Bsic:36,Lac:13,RxLev:26,Qual:2,Status:SUITABLE
7:Arfcn:1013,Bsic:37,Lac:14,RxLev:26,Qual:1,Status:SUITABLE
PLMN:"Orange F",MCC:208,MNC:01,CellNb:7,MeanPower:26
AT+NWKSCAN=,1
1:Arfcn:32,Bsic:1,Lac:1,RxLev:35,Qual:0,Status:SUITABLE
2:Arfcn:8,Bsic:2,Lac:2,RxLev:35,Qual:1,Status:SUITABLE
3:Arfcn:10,Bsic:3,Lac:3,RxLev:27,Qual:0,Status:SUITABLE
4:Arfcn:17,Bsic:4,Lac:4,RxLev:26,Qual:2,Status:SUITABLE
5:Arfcn:48,Bsic:5,Lac:5,RxLev:24,Qual:0,Status:SUITABLE
6:Arfcn:539,Bsic:6,Lac:6,RxLev:22,Qual:1,Status:SUITABLE
7:Arfcn:550,Bsic:7,Lac:7,RxLev:20,Qual:2,Status:SUITABLE
OK
Note: Request 7 cells per PLMN in numeric format
Command Answers
"SFR",208,10,8,30
1020,31,8,38,0,0
1008,32,9,33,1,0
1009,33,10,32,2,0
1003,34,11,29,1,0
792,35,12,27,1,0
"Orange F",208,01,7,26
AT+NWKSCAN=5,1
32,1,1,35,0,0
8,2,2,35,1,0
10,3,3,27,0,0
17,4,4,26,2,0
48,5,5,24,0,0
OK
Note: Request 5 cells per PLMN in numeric format
"SFR",8,30
"Orange F",7,26
AT+NWKSCAN=,2
OK
Note: Synthesis
Command Answers
+WJAM: <mode>
AT+WJAM?
OK
+WJAM: (list of supported <mode>s),(list of supported <threshold>s)
AT+WJAM=?
OK
ERROR
AT+WJAM=<mode>[,<threshold>] or
OK
Values Default
Parameter Description
range value
If the jamming detection algorithm is started, each time a PLMN scan is performed the following
unsolicited result is displayed :
+WJAM: <Status Type>: <result>
Where Status Type parameter is equal to "INTERMEDIATE STATUS" or "FINAL STATUS" and result
parameter is
!!! JAMMED !!!
HIGH
MEDIUM
LOW
NULL
Note: To execute the sample, Open AT application must be enabled in the embedded module. If it is not
enabled, execute AT+WOPEN=1 command to enable it. Only when Open AT application is enable , the
application provides the desired functionality.
Action command
AT+AUDIOINIT
OK
Read command
None
Test command
None
8.1.3. Example
Command Response
AT+AUDIOINIT OK
Action command
AT+AUDIOEXIT
OK
Read command
None
Test command
None
8.2.3. Examples
AT+AUDIOINIT OK
AT+AUDIOEXIT OK
Action command
AT+AUDIOFILE=<operation>,<name>,<resource>,<audio processing>[,<loop>]
OK
+AUDIOFILE: <event>,<resource>,<audio processing>
if <operation>="playstop" or "recordstop"
Action command
AT+AUDIOFILE=<operation>,<resource>,<audio processing>
OK
+AUDIOFILE: <event>,<resource>,<audio processing>
if <operation>="playparam"
Action command
AT+AUDIOFILE="playparam",<gain>
OK
if <operation>="recordparam"
Action command
AT+AUDIOFILE="recordparam",<duration>
OK
Read command
AT+AUDIOFILE?
+AUDIOFILE : "playparam",<gain>
+AUDIOFILE : "recordparam",<duration>
OK
Test command
AT+AUDIOFILE=?
+AUDIOFILE : ("playstart","recordstart"),"filename",(list of supported
<resource>),(list of supported <audio processing>)
+AUDIOFILE : ("playstop","recordstop"),(list of supported <resource>),(list of
supported <audio processing>)
+AUDIOFILE : "playparam",(-78-42)
+AUDIOFILE : "recordparam",(1-255)
OK
Parameter/Defined
Audio Operation
Value
8.3.3. Examples
Command Response
AT+AUDIOFILE="playstart","/dir1/Music1.wav","spk","nopro
c" OK
+AUDIOFILE:1,
Note: Start playing on speaker without digital audio processing (from (1) to "spk","noproc"
(A))
AT+AUDIOFILE="playstop","spk","noproc" OK
+AUDIOFILE:0,
Note: Stop playing on speaker without digital audio processing (from (1) to
"spk","noproc"
(A))
AT+AUDIOFILE="recordstart","/dir3/Music2.wav","mic","aud
ioproc" OK
+AUDIOFILE:3,"mic","audio
Note: Start recording from microphone with digital audio processing (from proc"
(B) to (4))
AT+AUDIOFILE="recordstop","mic","audioproc" OK
+AUDIOFILE:2,"mic","audio
Note: Stop recording from microphone with digital audio processing (from
proc"
(B) to (4))
AT+AUDIOFILE="playstart","/dir1/Music1.wav","mic","nopro
c" +CME ERROR:4
Note: Operation not supported, impossible to play on microphone
AT+AUDIOFILE="playstart","/dir2/Melody.wav","spk","audio
proc" OK
+AUDIOFILE:4,"spk","audio
Note: Start playing on speaker with digital audio processing (from (3) to (A)) proc"
but the file is not found.
AT+AUDIOFILE="playstart","/dir1/Music1.wav","spk","proc"
+CME ERROR:3
Note: Invalid syntax parameter ("proc" is an invalid parameter)
8.3.4. Errors
This event error occurs when an ADL API fails within the AT audio
commands library. This error occurs for :
memory allocation failure
file system closing failure
audio failures like the audio resource is not able to play or record now
Action command
AT+AUDIOCONVERT=<amr_file>,<pcm_file>
OK
+AUDIOCONVERT: 0
Note: +AUDIOCONVERT: 0 means the transcoding is successful.
Read command
AT+AUDIOCONVERT?
OK
Test command
AT+AUDIOCONVERT=?
+AUDIOCONVERT=<amr_file>,<pcm_file>
OK
<amr_file> Full input filename and file path to operate. File path is an absolute path.
<pcm_file> Full ouptput filename and file path to operate. File path is an absolute path.
8.4.3. Examples
Command Response
AT+AUDIOCONVERT="/dir1/InMusic1.amr","/dir2/OutMusic2.wav" OK
Note: +AUDIOCONVERT: 0 means the transcoding is successful. +AUDIOCONVERT: 0
8.4.4. Errors
Errors are indicated with "+AUDIOCONVERT: xxx" messages.
OK is returned when all AT command parameters are correct and when the first operations on FS &
memory run perfectly.
Thus if an error occurs during the transcoding process, the error is indicated with an unsolicited
message "+AUDIOCONVERT: xxx".
If one parameter is wrong or something wrong occurs with FS & memory management, only the
"+AUDIOCONVERT: xxx" message will occur. In other words, there is no OK.
9.1.1.1.1. Description
This AT Command is used to initialize the eCall In-Band Modem Library.
9.1.1.1.2. Syntax
Action command
AT+INBMINIT=[<SrcType>]
OK
Test command
AT+INBMINIT=?
+INBMINIT: (list of supported <at_command>s)
OK
9.1.1.1.4. Examples
Command Responses
AT+INBMINIT=?
+INBMINIT: 0
Note: displays all supported AT
OK
command format.
AT+INBMINIT=0 OK
or
+INBMERROR: <id> (In case the command fails. <id>,
specifies the error cause)
9.1.1.2.1. Description
This AT command cleans up the eCall In-Band Modem Library.
9.1.1.2.2. Syntax
Action command
AT+INBMEXIT
OK
9.1.1.2.3. Examples
Command Responses
AT+INBMEXIT OK
or
+INBMERROR: <id> (In case the command fails.
<id>, specifies the error cause)
9.1.1.3.1. Description
This AT command is used to request to get the In-Band Modem Library version
9.1.1.3.2. Syntax
Read command
AT+INBMGETVER?
[In-Band Modem Library version information]
OK
9.1.1.3.3. Examples
Command Responses
9.1.1.4.1. Description
The above command requests for the state of In-Band Modem Library.
9.1.1.4.2. Syntax
Read command
AT+INBMSTATE?
+INBMSTATE:<state>
OK
9.1.1.4.4. Examples
Command Responses
AT+INBMSTATE? +INBMSTATE: 0
OK
OR
Note: 0 if state is not initialized.
+INBMSTATE: 1
OK
Note: 1 if state is initialized.
OR
9.1.2.1.1. Description
This AT command is used to activate the In-Band Modem channel.
If “MSD” is not specified along with “AT+INMBOPEN” command, then default MSD value will be sent
as follows:
“0x015C0681D54970D65C3597CA0420C41464583ADE68AC52E9BB8413F149C07414FB414F6010
180813E82181823230"
9.1.2.1.2. Syntax
Action command
AT+INBMOPEN=<mode>,[“MSD”]
OK
Test command
AT+INBMOPEN=?
+INBMOPEN: (list of supported <mode>s),(<”MSD”>)
OK
0 Pull mode
1 Push mode
<MSD> maximum 140 This is an optional parameter. If the MSD is not provided a default 140 bytes of
byte string MSD would be considered. The MSD should be in double quotes.
permitted
9.1.2.1.4. Examples
Command Responses
AT+INBMOPEN? +INBMOPEN:(0,1),<MSD>
OK
AT+INBMOPEN=0,“MSD”
+INBMOPEN: 0
OK
Note: 0 if mode is pull mode.
+INBMEV: <ev>
AT+INBMOPEN=1,“MSD” +INBMOPEN: 1
OK
+INBMEV: <ev>
OR
Note: 1 if mode is push mode.
AT+INBMOPEN=0,”2541DE22” +INBMOPEN: 0
OK
AT+INBMOPEN=1,”6574FE24DD78” +INBMOPEN: 1
OK
9.1.2.2.1. Description
This AT command is used to de-activate/close the In-Band modem channel. Once the channel is de-
activated, no MSD transaction would occur.
9.1.2.2.2. Syntax
Action command
AT+INBMCLOSE
OK
9.1.2.2.3. Examples
Command Responses
AT+INBMCLOSE OK
or
+INBMERROR: <id> (In case the command fails.
<id>, specifies the error cause)
9.1.2.3.1. Description
This AT command helps in retrieving the channel state.
9.1.2.3.2. Syntax
Read command
AT+INBMCHSTATE?
+INBMCHSTATE:<ch_state>
OK
<ch_state >: Channel state is defined by this variable. It can have following values.
0 INBM_CHANNEL_IDLE
1 INBM_CHANNEL_MSD_REQ_SENDING
2 INBM_CHANNEL_MSD_SENDING
3 INBM_CHANNEL_WAITING_HLACK
9.1.2.3.4. Examples
Command Responses
AT+INBMCHSTATE? +INBMCHSTATE: 0
OK
OR
9.1.3.1.1. Description
This AT command is used to provide an updated MSD. Collects the MSD and provides the same the
Library for further processing. The channel will have to be in IDLE State to issue this command
9.1.3.1.2. Syntax
Action command
AT+INBMSETMSD=”MSD”
OK
<MSD >: This defines the length of Minimum Set of Data sent.
If MSD data is in ASCII format , the maximum data length will be up to 140
bytes.
If MSD data is in Binary format , the maximum data length will be up to 280
digits.
9.1.3.1.4. Examples
Command Responses
AT+INBMSETMSD=? OK
or
+INBMERROR: <id> (In case the
command fails. <id>, specifies the
error cause)
AT+INBMSETMSD=”015C0681D54970D65C359
7CA0420C41464583ADE68AC52E9BB8413F14 OK
9C07414FB414F6010180813E82181823230"
AT+INBMSETMSD=”SIERRA WIRELESS” OK
9.1.3.2.1. Description
This AT command is used to activate the PUSH mode.
9.1.3.2.2. Syntax
Action command
AT+INBMPUSH
OK
9.1.3.2.3. Examples
Command Responses
AT+INBMPUSH +INBMOPEN: 1
OK
or
+INBMERROR: <id> (In case the command fails.
<id>, specifies the error cause)
9.1.3.3.1. Description
This AT command is used to set the MSD format either in Binary or ASCII.
Default value is 0 which indicates MSD format is in Binary.
9.1.3.3.2. Syntax
Action command
AT+INBMMSDFORMAT=<MSD_format>
OK
Read command
AT+ INBMMSDFORMAT?
+ INBMMSDFORMAT:<MSD_format>
OK
<MSD_format >: Format of the MSD string being sent. It can have following values.
0 Binary format
1 ASCII format
9.1.3.3.4. Examples
Command Responses
Command Responses
AT+INBMMSDFORMAT? +INBMMSDFORMAT: 0
OK
or
+INBMMSDFORMAT: 1
OK
or
+INBMMSDFORMAT: <id> (If the command fails.
<id>, specifies the error cause)
9.1.3.4.1. Description
This AT command is used to configure the eCall In-Band Modem HLAP timer values.
9.1.3.4.2. Syntax
Action command: Used to set the timer values. The number of timer values that can be set is minimum of 1
parameter and maximum of 5 parameters.
AT+INBMTIMERCFG =<T2>,<T3>,<T5>,<T6>,<T7>
or
AT+INBMTIMERCFG =<”T2”>,<”T3”>,<”T5”>,<”T6”>,<”T7”>
OK
(Where <T2>,<T3>,<T5>,<T6>,<T7> are timer values to be set.)
The default timer values are CEN values as specified in the table below.
Table 4. Default Timer Values
T2 3600
T3 2
T5 5
T6 5
T7 20
T2 1 3600
T3 1 3600
T5 1 3600
T6 1 3600
T7 1 3600
9.1.3.4.5. Examples
9.1.4.1.1. Description
This AT command initialized the AT+CECALL functionality. If the SIM is eCall Only, it enables spy
mode.
9.1.4.1.2. Syntax
Action command
AT+CECALLINIT
OK
9.1.4.1.4. Examples
Command Responses
AT+CECALLINIT OK
or
ERROR (if already called)
9.1.4.2.1. Description
This AT command implements the AT command AT+CECALL as described in the corresponding
3GPP standard document.
If the SIM is eCall Only, it disables Spy Mode during the call. It will also stay registered on the network
for the duration of the T10 timer the call has finished, then go back to Spy Mode.
9.1.4.2.2. Syntax
Action command
AT+CECALL=<type_of_eCall>
OK
<type_of_eCall>: Format of the MSD string being sent. It can have following values.
0 Test Call. The number must be present on the SIM. If the number is not present
this command will fail.
1 Reconfiguration call eCall. The number must be present on the SIM. If the number
is not present this command will fail.
9.1.4.2.4. Examples
AT+CECALL=0
Start an Test Call. OK
AT+INBMINIT=0
OK
AT+INBMOPEN=1
+INBMOPEN: 1
OK
AT+INBMSETMSD="015C0681D54970D65C3597CA0420C41464583ADE68AC52E9BB8413F149C07414FB41
4F6010180813E82181823230"
OK
AT+CECALL=3
OK
AT+INBMINIT=0
OK
AT+INBMOPEN=1
+INBMOPEN: 1
OK
AT+INBMSETMSD="015C0681D54970D65C3597CA0420C41464583ADE68AC52E9BB8413F149C07414FB41
4F6010180813E82181823230"
OK
...
AT+INBMCLOSE=0
OK
AT+CECALL=3
OK
…
(after call)
AT+INBMOPEN=1
+INBMOPEN: 1
OK
9.1.5.1.1. Description
This AT command is used to initializes the Unified eCall Application and provides the vehicle related
information of the MSD.
It will also perform the equivalent of AT+CECALLINIT needed for the AT+CECALL.
9.1.5.1.2. Syntax
Action command
AT+ECALLINIT=<eCallMode>
OK
Read command
AT+ECALLINIT?
[+ECALLINIT: <eCallMode>]
OK
or
ERROR
Test command
AT+ECALLINIT=?
+ECALLINIT: (0-1)
OK
0 PAN EU Mode
9.1.5.1.4. Examples
Command Responses
AT+ECALLINIT=0 OK
or
ERROR
AT+ECALLINIT? +ECALLINIT: 0
OK
9.1.5.2.1. Description
There are certain parameters that affect the UNIFIED ECALL Specific behavior.
They all have default values according to [3]. One or several values can be changed via this
command.
Each parameter is optional, so if there is no need to change the default value, it can be left empty.
9.1.5.2.2. Syntax
If <action> = 0. Override Timer values.
Action command
AT+ECALLCFG=<action>,[<CCFT_T2>],[<INVITATION_SIGNAL_DURATION_T3>],
[<SEND_MSG_PERIOD_T5>],[<AL_ACK_PERIOD_T6>],
[<MSD_MAX_TRANSMISSION_TIME_T7>],[<ECALL_DIAL_DURATION>],
[<ECALL_AUTO_DIAL_ATTEMPS>],[<ECALL_MANUAL_DIAL_ATTEMPS>],[<ECALL_TIME_BETWEEN_REDI
ALS>]
OK
Action command
AT+ECALLCFG=<action>,<testNbr>,<reconfigurationNbr>
OK
Read command
AT+ECALLCFG?
+ECALLCFG: 0,<CCFT_T2>,<INVITATION_SIGNAL_DURATION_T3>,
<SEND_MSG_PERIOD_T5>,<AL_ACK_PERIOD_T6>,<MSD_MAX_TRANSMISSION_TIME_T7>,
<ECALL_DIAL_DURATION>,<ECALL_AUTO_DIAL_ATTEMPS>,<ECALL_MANUAL_DIAL_ATTEMPS>,<ECALL_
TIME_BETWEEN_REDIALS>
+ECALLCFG: 1,<testNbr>,<reconfigurationNbr>
OK
Test command
AT+ECALLCFG=?
+ECALLCFG: (0-1),(list of supported <CCFT_T2>),
(list of supported <INVITATION_SIGNAL_DURATION_T3>),
(list of supported <SEND_MSG_PERIOD_T5>),
(list of supported <AL_ACK_PERIOD_T6>),
(list of supported <MSD_MAX_TRANSMISSION_TIME_T7>),
(list of supported <ECALL_DIAL_DURATION>),
(list of supported <ECALL_AUTO_DIAL_ATTEMPS>),
(list of supported <ECALL_MANUAL_DIAL_ATTEMPS>)
(list of supported <ECALL_TIME_BETWEEN_REDIALS>)
OK
9.1.5.2.4. Examples
9.1.5.3.1. Description
This AT command updates the MSD with the values given and returns the encoded MSD in ASN1
PER format. This will be useful for queue handling and eSMS.
If the PSAP calls the IVS, the UNIFIED ECALL Service Manager will return this MSD.
The use case is that if a eCall fails to send the MSD, then the host should try to send a eSMS. This
helps the Host to encode it into ASN1 encoding.
9.1.5.3.2. Syntax
For <action> = 0. Setting the static parameters of the MSD.
Action command
AT+ECALLSETMSD=<action>,<ID>,<vehicleType>,<isowmi>,<isovds>,<isovisModelYear>,<iso
visSeqPlant>,<vehiclePropulsionStorageType>
OK
Action command
AT+ECALLSETMSD=<action>,<MsgId>,<control>,<timeStamp>,
<vehicleLocation.PositionLatitude>,
<vehicleLocation.PositionLongitude>,<vehicleDirection>
[,[<recentVehicleLocationN1.latitudeDelta>]
[,[<recentVehicleLocationN1.longitudeDelta>]
[,[<recentVehicleLocationN2.latitudeDelta>]
[,[<recentVehicleLocationN2.longitudeDelta>]
[,<numberOfPassengers>
[,<additionalData.oid>,<additionalData.data>]]]]]]
OK
For <action> = 2. Setting an already encoded MSD in hexadecimal string form.
Action command
AT+ECALLSETMSD=<action>,<ASN1encodedMSD>
OK
Read command
AT+ECALLSETMSD?
[+ECALLSETMSD: <ASN1encodedMSD>]
[+ECALLSETMSD: <ID>,<vehicleType>,<isowmi>,<isovds>,
<isovisModelYear>,<isovisSeqPlant>,<vehiclePropulsionStorageType>,
<MsgId>,<control>, <timeStamp>,<vehicleLocation.PositionLatitude>,
<vehicleLocation.PositionLongitude>,<vehicleDirection>
[,[<recentVehicleLocationN1.latitudeDelta>]
[,[<recentVehicleLocationN1.longitudeDelta>]
[,[<recentVehicleLocationN2.latitudeDelta>]
[,[<recentVehicleLocationN2.longitudeDelta>]
[,<numberOfPassengers>
[,<additionalData.oid>,<additionalData.data>]]]]]]]
OK
Test command
AT+ECALLSETMSD=?
OK
9.1.5.3.3. ISO-fields
Please note that the below mentioned fields accepts only a limited set of characters. Here are the
possible values as stated by ISO 3779 standard:
Values with
Field Min Max special
meaning
Values with
Field Min Max special
meaning
0x7FFFFFFF=
Integer for location -
+324000000 2147483647:
Latitude value 324000000
<vehicleLocation. locationLatitude> latitude is
according to [3]. (+90°)
(-90°) invalid or
Unit is in mas.
unknown
0x7FFFFFFF
- =
Integer for location +648000000
648000000 2147483647:
<vehicleLocation.PositionLongitude> Longitude value
(+180°) longitude is
according to [3]. (-180°) invalid or
unknown
Integer for vehicle
Direction according 0xFF:
to [3]. direction is
<vehicleDirection> 0 179
Degrees from invalid or
magnetic North, 2- unknown
deg steps.
Integer for location
Latitude value
according to
-512
[3]. – OPTIONAL +511
<recentVehicleLocationN1.latitudeDelta> (51.2''S) -
VALUE (51.1''N)
Unit is 100-mas
steps (latitude
delta).
Values with
Field Min Max special
meaning
9.1.5.3.5. Examples
Command Responses
AT+ECALLSETMSD=0,1,1,"WWW","VDSVD
S","Y","A123456",17
OK
AT+ECALLSETMSD=1,1,7,123456789,173
881200,41822520,14,,,,,5
OK
AT+ECALLSETMSD? +ECALLSETMSD:
"01040381D75D70D65C3597CA0420C414675E0EB79A
2B14BA6EE104FC52701C0A "
OK
9.1.5.4.1. Description
This AT command cancels the ongoing manual call if it has not yet been established and goes back to
idle. It is up to the Host to verify that the user has rights to cancel corresponding to parameter
ECALL_MANUAL_CAN_CANCEL in the case that this is applicable.
9.1.5.4.2. Syntax
Action command
AT+ECALLCANCEL
OK
Read command
AT+ECALLCANCEL?
OK
Test command
AT+ECALLCANCEL=?
OK
9.1.5.4.3. Examples
Command Responses
AT+ECALLCANCEL OK
or
ERROR
(if the cancel was not allowed)
9.1.5.5.1. Description
This command closes the UNIFIED ECALL Service functionality. All values go back to default. Host
will have to call AT+ECALLINIT to restart.
9.1.5.5.2. Syntax
Action command
AT+ECALLRELEASE
OK
Read command
AT+ECALLRELEASE?
OK
Test command
AT+ECALLRELEASE=?
OK
9.1.5.5.3. Examples
Command Responses
AT+ECALLRELEASE OK
or
ERROR
9.1.5.6.1. Description
This command returns the state of the Unified eCall Service manager.
9.1.5.6.2. Syntax
Action command
AT+ECALLGETSTATE
+ECALLGETSTATE: <state>
OK
Read command
AT+ECALLGETSTATE?
OK
Test command
AT+ECALLGETSTATE=?
OK
0 ECALL_STATE_INACTIVE
1 ECALL_STATE_IDLE
2 ECALL_STATE_CALLING
3 ECALL_STATE_CONNECTED
4 ECALL_STATE_SENDING_MSD
5 ECALL_STATE_VOICE_CALL
9.1.5.7.1. Description
This command returns the version of the Unified eCall Service manager.
9.1.5.7.2. Syntax
Action command
AT+ECALLVERSION
+ECALLVERSION: <version>
OK
Read command
AT+ECALLVERSION?
OK
Test command
AT+ECALLVERSION=?
OK
9.1.5.8.1. Description
The MSD contains optional data. The optional data is an OID, that describes how the data part should
be interpreted and then the data which is ANS.1 encoded.
The ERA GLONASS union has proposed one encoding for the optional data.
This AT command helps encode the data part of the optional data part of the MSD into ASN.1 format.
This is a utility command that permits to encode the optional data part for ERA GLONASS.
It is up to the caller to then paste the encoded ANS.1 string into the AT+ECALLSETMSD command.
Note that the optional part of the MSD is current not used in the PAN European standard.
The ASN.1 specification
ERAAdditionalData ::= SEQUENCE {
crashSeverityASI15 INTEGER(0..2047) OPTIONAL,
diagnosticResult DiagnosticResult OPTIONAL,
crashInfo CrashInfo OPTIONAL,
...
}
9.1.5.8.2. Syntax
Action command
AT+ECALLOPTDATA= <ID>[,<crashSeverityASI15>]
[,<PresenceMaskDiagnosticResult>,<diagnosticResult>]
[,<PresenceMaskCrashInfo>,<crashInfo>]
OK
Read command
AT+ ECALLOPTDATA?
+ECALLOPTDATA: <ID>,<crashSeverityASI15>
,<PresenceMaskDiagnosticResult>,<diagnosticResult>
,<PresenceMaskCrashInfo>,<crashInfo>
OK
Test command
AT+ECALLOPTDATA=?
OK
<crashSeverityASI15 > Optional integer representing the crash severity. Value range
[0.2047}
bit 0 crashFront
bit 1 crashLeft
bit 2 crashRight
bit 3 crashRear
bit 4 crashRollover
bit 5 crashSide
bit 6 crashFrontOrSide
bit 7 crashAnotherType
9.1.5.8.4. Examples
Command Responses
AT+ECALLOPTDATA=1,2000,1FFFFF,0
,1F,14
Note:
crashSeverityASI15 – 2000.
crashFront FALSE,
crashLeft FALSE,
crashRight TRUE,
crashRear FALSE,
crashRollover TRUE
9.1.5.9.1. Description
This AT command is used to call an emergency number, test number or reconfiguration number as
specified by SIM.
Note that this command is specified in 3GPP and could be used apart from the Unified eCall
Manager. But if the Unified eCall manager is initialized, it will handle the retry attempts. The Unified
Ecall Service manager will then handle the call and call retries in accordance to Unified eCall settings
values.
For complete information regarding the +CECALL, see the previous +CECALL section.
9.2.1.1. Syntax
Unsolicited response
+INBMEV: <ev> (Unsolicited events to display the progress on the open channel)
9.2.2.1.1. Description
The following asynchronous events can be received as unsolicited responses:
+ECALLEV: During the Emergency call and sending of the MSD informational indications will be
given, indicating the event that occurred and the state before and after the event was processed.
9.2.2.1.2. Syntax
Unsolicited response
+ECALLEV: <eventid>,<statebefore>,<stateafter>
9.2.2.2.1. Description
The following asynchronous events can be received as unsolicited responses:
+ECALLERROR: An error has been detected somewhere outside the scope of a normal AT command
call. Not to be confused with the CME Errors.
9.2.2.2.2. Syntax
Unsolicited response
+ECALLERROR: <error>
<error> An error event has occurred, these are the following values and meanings.
Also see eCall_error_event_e.
-100 ECALL_EV_ERROR_NO_SIM
-101 ECALL_EV_ERROR_PIN_NOT_READY
-102 ECALL_EV_ERROR_NO_CARRIER
-103 ECALL_EV_ERROR_SETUP_ERROR
-104 ECALL_EV_ERROR_NO_ANSWER
-105 ECALL_EV_ERROR_BUSY
3.AT+INBMOPEN=0,”015C0681D54970D65C3597CA0420C41464583ADE68AC52E9BB8413F149C07414FB414F601018081
3E82181823230"
+INBMOPEN: 0
OK
5. AT+INBMCHSTATE?
+INBMCHSTATE: 0
OK
6.
AT+INBMSETMSD=”015C0681D54970D65C3597CA0420C41464583ADE68AC52E9BB8413F149C07414FB414F601018081
3E82181823230"
[Note: Only If the channel State is IDLE]
OK
7. AT+INBMPUSH [ Send the MSD_SEND_REQ to PSAP server to initiate the MSD transaction]
+INBMOPEN: 1
OK
8. AT+INBMCHSTATE?
+INBMCHSTATE: 1
OK
9. AT+INBMCLOSE
OK
10. AT+INBMEXIT
OK
11. Disconnect the Voice call with PSAP Server.
3.AT+INBMOPEN=1,”015C0681D54970D65C3597CA0420C41464583ADE68AC52E9BB8413F149C07414FB414F601018081
3E82181823230"
+INBMOPEN: 1
OK
5. AT+INBMCHSTATE?
+INBMCHSTATE: 0
OK
6. AT+INBMCLOSE
OK
7. AT+INBMEXIT
OK
10.1.1.1. Description
This AT command is used to initializes the ERA GLONASS Application and provides the vehicle
related information of the MSD.
10.1.1.2. Syntax
Action command
AT+ERAGINIT=<vehicleType>,<isowmi>,<isovds>,<isovisModelYear>,<isovisSeqPlant>,<veh
iclePropulsionStorageType>
OK
Read command
AT+ERAGINIT?
+ERAGINIT: <vehicleType>,<isowmi>,<isovds>,<isovisModelYear>,
<isovisSeqPlant>,<vehiclePropulsionStorageType>
OK
Test command
AT+ERAGINIT=?
OK
Please note that the above mentioned fields accepts only a limited set of characters. Here are the
possible values as stated by ISO 3779 standard:
10.1.1.4. Examples
Command Responses
AT+ERAGINIT=1,"WM9",
"VDSVDS","Y","A12345
6",A OK
or
ERROR: (In case the command fails)
10.1.2.1. Description
There are certain parameters that affect the ERA GLONASS Specific behavior.
They all have default values according to [3]. One or several values can be changed via this
command.
Each parameter is optional, so if there is no need to change the default value, it can be left empty.
10.1.2.2. Syntax
Action command
AT+ERAGSETERA=[<CCFT_T2>],[<INVITATION_SIGNAL_DURATION_T3>],
[<SEND_MSG_PERIOD_T5>],[<AL_ACK_PERIOD_T6>],
[<MSD_MAX_TRANSMISSION_TIME_T7>],[<ECALL_DIAL_DURATION>],
[<ECALL_AUTO_DIAL_ATTEMPS>],[<ECALL_MANUAL_DIAL_ATTEMPS>],
[<ECALL_TIME_BETWEEN_REDIALS>],[<ECALL_TIME_BEFORE_UNMUTE_AFTER_AL_ACK>]
OK
Read command
AT+ERAGSETERA?
+ERAGSETERA: <CCFT_T2>,<INVITATION_SIGNAL_DURATION_T3>,
<SEND_MSG_PERIOD_T5>,<AL_ACK_PERIOD_T6>,<MSD_MAX_TRANSMISSION_TIME_T7>,
<ECALL_DIAL_DURATION>,<ECALL_AUTO_DIAL_ATTEMPS>,<ECALL_MANUAL_DIAL_ATTEMPS>,<ECALL_
TIME_BETWEEN_REDIALS>,<ECALL_TIME_BEFORE_UNMUTE_AFTER_AL_ACK>
OK
Test command
AT+ERAGSETERA=?
+ERAGSETERA: (list of supported <CCFT_T2>),
(list of supported <INVITATION_SIGNAL_DURATION_T3>),
(list of supported <SEND_MSG_PERIOD_T5>),
(list of supported <AL_ACK_PERIOD_T6>),
(list of supported <MSD_MAX_TRANSMISSION_TIME_T7>),
(list of supported <ECALL_DIAL_DURATION>),
(list of supported <ECALL_AUTO_DIAL_ATTEMPS>),
(list of supported <ECALL_MANUAL_DIAL_ATTEMPS>)
(list of supported <ECALL_TIME_BETWEEN_REDIALS>)
(list of supported <ECALL_TIME_BEFORE_UNMUTE_AFTER_AL_ACK>)
OK
Default
Parameter name Type The type of option to set
Values
10.1.2.4. Examples
10.1.3.1. Description
This AT command is used to call an emergency number or test number. MSD related information
must be provided for it to work.
The ERA GLONASS Service manager will then handle the call and call retries in accordance to ERA
GLONASS settings values.
If the MSD is successfully updated it will result in an unsolicited response +ERAGMSD.
10.1.3.2. Syntax
Action command
AT+ERAGCALL=<number>,<ID>,<MsgId>,<control>,<timeStamp>,
<vehicleLocation.PositionLatitude>,
<vehicleLocation.PositionLongitude>,<vehicleDirection>
[,[<recentVehicleLocationN1.latitudeDelta>]
[,[<recentVehicleLocationN1.longitudeDelta>]
[,[<recentVehicleLocationN2.latitudeDelta>]
[,[<recentVehicleLocationN2.longitudeDelta>]
[,<numberOfPassengers>
[,<additionalData.oid>,<additionalData.data>]]]]]]
OK
Read command
AT+ERAGCALL?
OK
Test command
AT+ERAGCALL=?
OK
Values with
Field Min Max special
meaning
The telephone
<number> number to call. May
specify category.
- - -
Values with
Field Min Max special
meaning
Values with
Field Min Max special
meaning
10.1.3.4. Examples
Command Responses
AT+ERAGCALL="112",1,0,7,123456,123,4 OK
56,255,,,,,2
Note: any errors will be given
OK through unsolicited +ERAGERROR.
10.1.3.5. +ERAGSETMSD
10.1.3.6. Description
This AT command updates the MSD with the values given and returns the encoded MSD in ASN1
PER format. This will be useful for queue handling and eSMS.
If the PSAP calls the IVS, the ERA GLONASS Service Manager will return this MSD.
The use case is that if a eCall fails to send the MSD, then the host should try to send a eSMS. This
helps the Host to encode it into ASN1 encoding.
If the MSD is successfully updated it will result in an unsolicited response +ERAGMSD.
10.1.3.7. Syntax
Action command
AT+ERAGSETMSD=<ID>,<MsgId>,<control>,<timeStamp>,
<vehicleLocation.PositionLatitude>,
<vehicleLocation.PositionLongitude>,<vehicleDirection>
[,[<recentVehicleLocationN1.latitudeDelta>]
[,[<recentVehicleLocationN1.longitudeDelta>]
[,[<recentVehicleLocationN2.latitudeDelta>]
[,[<recentVehicleLocationN2.longitudeDelta>]
[,<numberOfPassengers>
[,<additionalData.oid>,<additionalData.data>]]]]]]
OK
Read command
AT+ERAGSETMSD?
+ERAGSETMSD: <ID>,<MsgId>,<control>,<timeStamp>,
<vehicleLocation.PositionLatitude>,
<vehicleLocation.PositionLongitude>,<vehicleDirection>,
[<recentVehicleLocationN1.latitudeDelta>],
[<recentVehicleLocationN1.longitudeDelta>],
[<recentVehicleLocationN2.latitudeDelta>],
[<recentVehicleLocationN2.longitudeDelta>],
[<numberOfPassengers>],
[<additionalData.oid>,<additionalData.data>]
OK
Test command
AT+ERAGSETMSD=?
OK
<recentVehicleLocationN1.l Integer for location Latitude value according to [3]. – OPTIONAL VALUE
atitudeDelta>
<recentVehicleLocationN1.l Integer for location Longitude value according to [3]. – OPTIONAL VALUE
ongitudeDelta>
<recentVehicleLocationN2.l Integer for location Latitude value according to [3]. – OPTIONAL VALUE
atitudeDelta>
<recentVehicleLocationN2.l Integer for location Longitude value according to [3]. – OPTIONAL VALUE
ongitudeDelta>
10.1.3.9. Examples
Command Responses
10.1.4.1. Description
This AT command updates the MSD with the values given and returns the encoded MSD in ASN1
PER format. This will be useful for queue handling and eSMS.
If the PSAP calls the IVS, the ERA GLONASS Service Manager will return this MSD.
The use case is that if a eCall fails to send the MSD, then the host should try to send a eSMS. This
helps the Host to encode it into ASN1 encoding.
If the MSD is successfully updated it will result in an unsolicited response +ERAGMSD.
10.1.4.2. Syntax
Action command
AT+ERAGSETMSD=<ID>,<MsgId>,<control>,<timeStamp>,
<vehicleLocation.PositionLatitude>,
<vehicleLocation.PositionLongitude>,<vehicleDirection>
[,[<recentVehicleLocationN1.latitudeDelta>]
[,[<recentVehicleLocationN1.longitudeDelta>]
[,[<recentVehicleLocationN2.latitudeDelta>]
[,[<recentVehicleLocationN2.longitudeDelta>]
[,<numberOfPassengers>
[,<additionalData.oid>,<additionalData.data>]]]]]]
OK
Read command
AT+ERAGSETMSD?
+ERAGSETMSD: <ID>,<MsgId>,<control>,<timeStamp>,
<vehicleLocation.PositionLatitude>,
<vehicleLocation.PositionLongitude>,<vehicleDirection>,
[<recentVehicleLocationN1.latitudeDelta>],
[<recentVehicleLocationN1.longitudeDelta>],
[<recentVehicleLocationN2.latitudeDelta>],
[<recentVehicleLocationN2.longitudeDelta>],
[<numberOfPassengers>],
[<additionalData.oid>,<additionalData.data>]
OK
Test command
AT+ERAGSETMSD=?
OK
Values with
Field Min Max special
meaning
0x7FFFFFFF=
Integer for location -
+324000000 2147483647:
Latitude value 324000000
<vehicleLocation. locationLatitude> latitude is
according to [3]. Unit (+90°)
(-90°) invalid or
is in mas.
unknown
0x7FFFFFFF
- =
Integer for location +648000000
648000000 2147483647:
<vehicleLocation.PositionLongitude> Longitude value
(+180°) longitude is
according to [3]. (-180°) invalid or
unknown
Integer for vehicle
Direction according to 0xFF:
[3]. direction is
<vehicleDirection> 0 179
Degrees from invalid or
magnetic North, 2-deg unknown
steps.
Integer for location
Latitude value
according to -512
<recentVehicleLocationN1.latitudeDelta +511
[3]. – OPTIONAL (51.2''S) -
> (51.1''N)
VALUE
Unit is 100-mas steps
(latitude delta).
Values with
Field Min Max special
meaning
10.1.4.4. Examples
Command Responses
10.1.5.1. Description
This AT command cancels the ongoing manual call if it has not yet been established and goes back
to idle. It is up to the Host to verify that the user has rights to cancel corresponding to parameter
ECALL_MANUAL_CAN_CANCEL.
10.1.5.2. Syntax
Action command
AT+ERAGCALLCANCEL
OK
Read command
AT+ERAGCALLCANCEL?
OK
Test command
AT+ERAGCALLCANCEL=?
OK
10.1.5.3. Examples
Command Responses
AT+ERAGCALLCANCEL OK
or
ERROR: (In case the command fails)
10.1.6.1. Description
This command closes the ERA GLONASS Service functionality. All values go back to default. Host
will have to call AT+ERAGINIT to restart.
10.1.6.2. Syntax
Action command
AT+ERAGRELEASE
OK
Read command
AT+ERAGRELEASE?
OK
Test command
AT+ERAGRELEASE=?
OK
10.1.6.3. Examples
Command Responses
AT+ERAGRELEASE OK
or
ERROR: (In case the command fails)
10.1.7.1. Description
This command returns the state of the ERA GLONASS Service manager.
10.1.7.2. Syntax
Action command
AT+ERAGGETSTATE
+ERAGGETSTATE: <state>
OK
Read command
AT+ERAGGETSTATE?
OK
Test command
AT+ERAGGETSTATE=?
OK
0 ERAG_STATE_INACTIVE
1 ERAG_STATE_IDLE
2 ERAG_STATE_CALLING
3 ERAG_STATE_CONNECTED
4 ERAG_STATE_SENDING_MSD
5 ERAG_STATE_VOICE_CALL
10.1.8.1. Description
This command returns the version of the ERA GLONASS Service manager.
10.1.8.2. Syntax
Action command
AT+ERAGVERSION
+ERAGVERSION: <version>
OK
Read command
AT+ERAGVERSION?
OK
Test command
AT+ERAGVERSION=?
OK
10.1.9.1. Description
The MSD contains optional data. The optional data is an OID, that describes how the data part should
be interpreted and then the data which is ANS.1 encoded.
This AT command helps encode the data part of the optional data part of the MSD into ASN.1 format.
The result can is returned in a format directly applicable for the <additionalData.data>
AT+ERAGCALL and AT+ERAGSETMSD setting of the OID and data part.
10.1.9.2. Syntax
Action command
AT+ERAGOPTDATA=
<ID>[,<crashSeverityASI15>]ID[,crashSeverityASI15]
[,<PresenceMaskDiagnosticResult>,<diagnosticResult>]
[,<PresenceMaskCrashInfo>,<crashInfo>]
DiagnosticResultdiagnosticResultCrashInfocrashInfoOK
Read command
10.1.9.2.1.1. AT+ ERAGOPTDATA?
+ERAGOPTDATA: <ID>,<crashSeverityASI15>
,<PresenceMaskDiagnosticResult>,<diagnosticResult>
,<PresenceMaskCrashInfo>,<crashInfo>
OK
Test command
AT+ERAGOPTDATA=?
OK
bit 0 crashFront
bit 1 crashLeft
bit 2 crashRight
bit 3 crashRear
bit 44 crashRollovercrashRollover
bit 55 crashSide
bit 66 crashFrontOrSidecrashFrontOrSide
bit 77 crashAnotherType
10.1.10. Examples
Command Responses
AT+ERAGOPTDATA=1,2000,1FFFFF,0,
1F,14
Note:
crashSeverityASI15 – 20002000.
OK
PresenceMaskCrashInfo – values in bit 0 to 4 is present in or
the CrashInfo
ERROR
crashInfo– followingcrashInfofollowing values are present
and set
crashFront FALSE,
crashLeft FALSE,
crashRight TRUE,
crashRear FALSE,
crashRollover TRUE
10.2.1.1. Description
The following asynchronous events can be received as unsolicited responses:
+ERAGEV: During the Emergency call and sending of the MSD informational indications will be given,
indicating the event that occurred and the state before and after the event was processed.
10.2.1.2. Syntax
Unsolicited response
+ERAGEV: <eventid>,<statebefore>,<stateafter>
0 ERAG_EVENT_INBM_MSD_REQ_RECEIVED
1 ERAG_EVENT_INBM_MSD_REQ_NOT_RECEIVED
2 ERAG_EVENT_INBM_LLACK_RECEIVED
3 ERAG_EVENT_INBM_HLACK_RECEIVED
4 ERAG_EVENT_INBM_LLACK_NOT_RECEIVED
5 ERAG_EVENT_INBM_HLACK_NOT_RECEIVED
6 ERAG_EVENT_INBM_ABORT_RECEIVED
7 ERAG_EVENT_INBM_HLACK_RECEIVED_CLEARDOWN
20 ERAG_EVENT_CALL_CONNECTED
21 ERAG_EVENT_CALL_NOT_CONNECTED
22 ERAG_EVENT_CALL_ENDED
23 ERAG_EVENT_CALL_WILL_RETRY
24 ERAG_EVENT_CALL_ATTEMPT_FAILED
25 ERAG_EVENT_CALL_INCOMING
40 ERAG_EVENT_ERAGINIT
41 ERAG_EVENT_ERAGRELEASE
42 ERAG_EVENT_ERAGCALL
43 ERAG_EVENT_ERAGCALLCANCEL
44 ERAG_EVENT_ERAGSETMSD
45 ERAG_EVENT_ERAGSETERA
50 ERAG_EVENT_TIMER_EXPIRED_DIAL_DURATION
51 ERAG_EVENT_TIMER_EXPIRED_T2_CALL_DURATION
<statebefore>, State before and after will have the following numerical values
Also see erag_states_e.
<stateafter>
0 ERAG_STATE_INACTIVE
1 ERAG_STATE_IDLE
2 ERAG_STATE_CALLING
3 ERAG_STATE_CONNECTED
4 ERAG_STATE_SENDING_MSD
5 ERAG_STATE_VOICE_CALL
10.2.2.1. Description
The following asynchronous events can be received as unsolicited responses:
+ERAGMSD: A MSD has just been updated and ANS1-encoded using AT+ERAGCALL or
AT+ERAGSETMSD and the result is shared via this response.
10.2.2.2. Syntax
Unsolicited response
+ERAGMSD: <msd>
10.2.3.1. Description
The following asynchronous events can be received as unsolicited responses:
+ERAGERROR: An error has been detected somewhere outside the scope of a normal AT command
call. Not to be confused with the CME Errors.
10.2.3.2. Syntax
Unsolicited response
+ERAGERROR: <error>
<error> An error event has occurred, these are the following values and meanings.
Also see erag_error_event_e.
-100 ERAG_EV_ERROR_NO_SIM
-101 ERAG_EV_ERROR_PIN_NOT_READY
-102 ERAG_EV_ERROR_NO_CARRIER
-103 ERAG_EV_ERROR_SETUP_ERROR
-104 ERAG_EV_ERROR_NO_ANSWER
-105 ERAG_EV_ERROR_BUSY
-1
ERAG_CERR_BAD_STATE Function was called when the state when the
function cannot be executed.
-2
ERAG_CERR_UNKNOWN_STATE State machine has reached an unknown state.
-3
ERAG_CERR_UNHANDLED_EVENT Unhandled event in this state.
-4
ERAG_CERR_MSD_VALUE_RANGE Updating the MSD values failed. While trying to
encode the MSD with the new values, the ASN1
encoding failed. New values are not taken into
account.
-5
ERAG_CERR_NULL_VALUE Null value found when NULL is not allowed.
-6
ERAG_CERR_INBND_MDM_ERROR Error from InBand Modem.
-7
ERAG_CERR_UNKNOWN_ERROR Unspecified error occurred.
-8
ERAG_CERR_PARAM Bad parameter value. Also see
ERAG_CERR_MSD_VALUE_RANGE and
ERAG_CERR_NULL_VALUE.
AT+ERAGINIT=1,"WWW","VDSVDS","Y","A123456",17
OK
+ERAGEV: 40,0,1
AT+ERAGCALL="112",1,0,7,123456789,173881200,41822520,14,,,,,5
OK
+ERAGMSD: 01040381D75D70D65C3597CA0420C414675E0EB79A2B14BA6EE104FC52701C0A
+ERAGEV: 42,1,2
+ERAGEV: 20,2,3
+ERAGEV: 0,3,4
+ERAGEV: 2,4,4
+ERAGEV: 3,4,5
+ERAGEV: 22,5,1
Command Response
AT+FSINIT OK
Command Response
AT+FSEXIT OK
Command Response
AT+FS=<operation>[,<param1>][,<param2>] OK
if <operation>="install"
Action command
AT+FS="install",<name>
Note: The module resets if command is successful. So there is no OK final response in the case a valid file is given.
if <operation>="fsstat"
Action command
AT+FS=<operation>
+FS: <free size>,<total size>
OK
if <operation>="mkdir","rmdir"
Action command
AT+FS=<operation>,<directory path>
OK
if <operation>="ls"
Action command
AT+FS=<operation>,<directory path>,<first>
+FS: <name>,<free size>,<creation date>,<type>,<more>
OK
if <operation>="rm"
Action command
AT+FS=<operation>,<name>
OK
if <operation>="fstat"
Action command
AT+FS=<operation>,<name>
+FS: <size>,<creation date>,<creation time>
OK
if <operation>="read"
Action command
AT+FS=<operation>,<name>,<size>
Note: "C" character launches the upload, content of file is uploaded on port where AT+FS was sent, using 1K-X modem
protocol.
if <operation>="write"
Action command
AT+FS=<operation>,<name>,<size>
+FS: 0
Note: Download mode started. File can be sent using the terminal application.
Read Command
None
Test Command
AT+FS=?
+FS: (list of supported <operation>s)
OK
11.3. Examples
Command Answers
AT+FSINIT
OK
Note: Initialize File System Driver
Command Answers
AT+FS="ls","/dir2/sub_dir2",1 +FS:
OK
Note: This is the content of /dir2/sub_dir2 directory
AT+FS="rmdir","/dir2/sub_dir2" OK
Note: Remove /dir2/sub_dir2 directory (it must be empty,
except . and .. of course)
AT+FS="rm","/dir2/file4.txt" OK
Note: Deletes /dir2/file4.txt file
AT+FS="mkdir","/new_dir" OK
Note: Creates new_dir directory at root
AT+FS="write","/new_dir/new_file.bin",2014 +FS: 0
Note: /new_dir/new_file.bin file created, download mode
started. File can be sent using X modem
Command Answers
AT+FSEXIT
OK
Note: Close File System Driver