u-blox lisa-c200 and fw75-c200

LISA-C200 and FW75-C200 CDMA 1XRTT Cellular Modules AT Commands Manual

Abstract Description of standard and proprietary AT Commands used with u-blox LISA-C200 and FW75-C200 cellular modules.

These modules are complete and cost efficient CDMA solutions offering 153 kb/s data speed dual-band 800/1900 MHz data transmission technology in compact form factors.

www.u-blox.com

UBX-13000621 - R10

http://www.u-blox.com/

LISA-C200 and FW75-C200 - AT Commands Manual

UBX-13000621 - R10 of 149

Document Information

Title LISA-C200 and FW75-C200

Subtitle CDMA 1XRTT Cellular Modules

Document type AT Commands Manual

Document number UBX-13000621

Revision and date R10 01-Oct-2014

Document status Production Information

Document status explanation

Objective Specification Document contains target values. Revised and supplementary data will be published later.

Advance Information Document contains data based on early testing. Revised and supplementary data will be published later.

Early Production Information Document contains data from product verification. Revised and supplementary data may be published later.

Production Information Document contains the final product specification.

This document applies to the following products:

Name Type number Firmware version PCN reference

FW75-C200 FW75-C200-02S-00 E0.S.04.00.03R UBX-TN-12070

LISA-C200 LISA-C200-02S-00 E0.S.04.00.03R UBX-TN-12070

FW75-C200 FW75-C200-22S-00 E0.V.04.00.03R UBX-TN-12070

LISA-C200 LISA-C200-22S-00 E0.V.04.00.03R UBX-TN-12070

FW75-C200 FW75-C200-02S-01 E0.S.05.00.04R UBX-TN-12077

LISA-C200 LISA-C200-02S-01 E0.S.05.00.04R UBX-TN-12077

FW75-C200 FW75-C200-22S-01 E0.V.05.00.02R UBX-TN-12077

LISA-C200 LISA-C200-22S-01 E0.V.05.00.03R UBX-TN-12077

LISA-C200 LISA-C200-03S-00 E0.S.06.00.07R UBX-13005454

LISA-C200 LISA-C200-23S-00 E0.V.06.00.06R UBX-13005454

LISA-C200 LISA-C200-04S-00 E0.S.07.00.07R UBX-14042040

LISA-C200 LISA-C200-24S-00 E0.V.07.00.07R UBX-14042040

u-blox reserves all rights to this document and the information contained herein. Products, names, logos and designs described herein may in whole or in part be subject to intellectual property rights. Reproduction, use, modification or disclosure to third parties of this document or any part thereof without the express permission of u-blox is strictly prohibited. The information contained herein is provided “as is” and u-blox assumes no liability for the use of the information. No warranty, either express or implied, is given, including but not limited, with respect to the accuracy, correctness, reliability and fitness for a particular purpose of the information. This document may be revised by u-blox at any time. For most recent documents, visit www.u-blox.com. Copyright © 2014, u-blox AG. u-blox® is a registered trademark of u-blox Holding AG in the EU and other countries. ARM® is the registered trademark of ARM Limited in the EU and other countries.


UBX-13000621 - R10 Production Information Preface

of 149

Preface u-blox Technical Documentation As part of our commitment to customer support, u-blox maintains an extensive volume of technical documentation for our products. In addition to our product-specific technical data sheets, the following manuals are available to assist u-blox customers in product design and development.

AT Commands Manual: This document provides the description of the supported AT commands by cellular modules to verify all implemented functionalities.

System Integration Manual: This Manual provides hardware design instructions and information on how to set up production and final product tests.

How to use this Manual This AT Commands Manual provides the necessary information to successfully design in and configure these u-blox cellular modules. For navigating this document, note the following:

This manual has a modular structure. It is not necessary to read it from the beginning to the end.

The following symbols are used to highlight important information within the manual:

An index finger points out key information pertaining to module integration and performance.

A warning symbol indicates actions that could negatively impact or damage the module.

Questions If you have any questions about u-blox cellular hardware integration:

• Read this manual carefully.

• Contact our information service on our homepage http://www.u-blox.com

• Read the questions and answers on our FAQ database

Technical Support Worldwide Web

Our website (www.u-blox.com) is a rich pool of information. Product information, technical documents and helpful FAQ can be accessed 24h a day.

By E-mail

If you have technical problems or cannot find the required information in the provided documents, contact the nearest Technical Support office by email. Use our service pool email addresses rather than any personal email address of our staff. This makes sure that your request is processed as soon as possible. You will find the contact details at the end of the document.

Helpful Information when Contacting Technical Support

When contacting Technical Support, have the following information ready:

• Module type (e.g. LISA-C200-04S-00) and firmware version (e.g. E0.S.07.00.07R)

• Module configuration

• Clear description of your question or the problem

• A short description of the application

• Your complete contact details




UBX-13000621 - R10 Production Information Content

of 149

Content

Preface ................................................................................................................................ 3

Content ............................................................................................................................... 4

1 Introduction ................................................................................................................ 10 1.1 Purpose .............................................................................................................................................. 10 1.2 Definitions .......................................................................................................................................... 10 1.3 AT commands mode........................................................................................................................... 10

2 IPC – Inter Processor Communication ........................................................................ 12 2.1 Multiplexing mode +CMUX ................................................................................................................ 12

3 General commands ..................................................................................................... 13 3.1 Device Information ATI ....................................................................................................................... 13 3.2 Request Manufacturer Identification +GMI ......................................................................................... 13 3.3 Request model identification +GMM .................................................................................................. 14 3.4 Request revision identification +GMR ................................................................................................. 14 3.5 Request product serial number identification +GSN ............................................................................ 14 3.6 Request international mobile subscriber identification +CIMI .............................................................. 15 3.7 DTE-DCE local flow control +IFC ......................................................................................................... 15 3.8 Set the DTE Rate +IPR ......................................................................................................................... 16 3.9 Set the Rm interface protocol +CRM .................................................................................................. 16 3.10 Read the PRL ID $PRL ...................................................................................................................... 17 3.11 Read/write the current MDN $MDN ................................................................................................ 17 3.12 Read/write the current MSID $MSID ................................................................................................ 17 3.13 Set the Echo ON/OFF E .................................................................................................................... 18 3.14 Set the Result Code Suppression ON/OFF Q .................................................................................... 18 3.15 Response Format V ......................................................................................................................... 18 3.16 HW version +UHWVER .................................................................................................................... 19 3.17 Returns Temperature +UTEMP ........................................................................................................ 19 3.18 Antenna detection AT+UANTR ........................................................................................................ 19 3.19 Set up Aeris PRI (special RTN for Aeris) +UAERIS .............................................................................. 20 3.20 Update ACCOLC +UPACCOLC ....................................................................................................... 21 3.21 Set up US Cellular PRI (special RTN for US Cellular) +UUSCELL ........................................................ 21

4 Mobile equipment control and status commands ................................................... 23 4.1 Phone activity status +CPAS ............................................................................................................... 23 4.2 Switch off MT +CPWROFF .................................................................................................................. 23 4.3 Device reset command $RTN .............................................................................................................. 24 4.4 Set phone functionality +CFUN ........................................................................................................... 24 4.5 Power Saving control +UPSV .............................................................................................................. 24



of 149

4.6 Indicator control +CIND ...................................................................................................................... 26 4.7 Clock +CCLK ...................................................................................................................................... 27 4.8 Mobile termination event reporting +CMER........................................................................................ 27 4.9 Report mobile termination error +CMEE ............................................................................................. 28 4.10 Reset to factory default without resetting NAM (special RTN) +UCLEAN ......................................... 29 4.11 Provision State +UPROVSTATE ........................................................................................................ 29

5 Call control commands ............................................................................................... 30 5.1 Dial command D ................................................................................................................................. 30 5.2 Call answer A ..................................................................................................................................... 30 5.3 Dial voice call +CDV ............................................................................................................................ 30 5.4 Hang Up voice call +CHV .................................................................................................................... 31 5.5 Hang up call +CHUP ........................................................................................................................... 31 5.6 Call status messages +UCST ............................................................................................................... 31 5.7 Extended error report +CEER .............................................................................................................. 32 5.8 Tone Duration +VTD ........................................................................................................................... 32 5.9 DTMF and tone generation +VTS ........................................................................................................ 33 5.10 Configure Ring Indicator +URINGCFG ............................................................................................. 33 5.11 Configure Call precedence during socket operations +USORNGCFG ............................................... 34 5.12 Read call status +UCSTRD ............................................................................................................... 34

6 Network service commands ...................................................................................... 35 6.1 Network Service information +USVC .................................................................................................. 35 6.2 Signal quality +CSQ ............................................................................................................................ 35 6.3 Network registration and roaming information +CREG ....................................................................... 36 6.4 Return the debugging information $DEBUG ....................................................................................... 37 6.5 CDMA network parameters +NETPAR ................................................................................................ 37 6.6 To display protocol revision in use $QCPREV ....................................................................................... 38 6.7 Um Packet Data Inactivity Timer +CTA ................................................................................................ 38 6.8 System information +CSS ................................................................................................................... 39 6.9 Query Analog or Digital Service +CAD ................................................................................................ 39

7 1XRTT Data commands .............................................................................................. 40 7.1 Mobile Station IP Address +CMIP ........................................................................................................ 40 7.2 Base Station IP Address +CBIP ............................................................................................................ 40 7.3 Request overall capabilities +GCAP ..................................................................................................... 40 7.4 Enable/disable Mobile IP functionality $QCMIP ................................................................................... 40 7.5 Set the active Mobile Profile ID $QCMIPP............................................................................................ 41 7.6 Enable/disable the RFC2002bis Authentication $QCMIPT .................................................................... 41 7.7 Enable/disable the active profile $QCMIPEP ........................................................................................ 42 7.8 Display information to Specific Profile $QCMIPGETP ........................................................................... 42 7.9 Set NAI for active profile $QCMIPNAI ................................................................................................. 43 7.10 Set the reverse tunneling on currently active profile $QCMIPRT ...................................................... 43 7.11 Set MN-AAA Shared Secrets $QCMIPMASS .................................................................................... 44 7.12 Set MN-AAA Shared Secrets in HEX format $QCMIPMASSX ........................................................... 45



of 149

7.13 Set MN-HA Shared Secrets $QCMIPMHSS ....................................................................................... 45 7.14 Set MN-HA Shared Secrets in Hex format $QCMIPMHSSX .............................................................. 46 7.15 Set MN-HA SPI Shared Secrets $QCMIPMHSPI ................................................................................ 46 7.16 Set MN-AAA SPI Shared Secrets $QCMIPMASPI .............................................................................. 47 7.17 MIP Indicator +CMIPIND ................................................................................................................. 47

8 Short Messages Service commands .......................................................................... 49 8.1 Show text mode parameters +CSDH ................................................................................................... 49 8.2 New message indication +CNMI ......................................................................................................... 49 8.3 List message +CMGL .......................................................................................................................... 50 8.4 Read message +CMGR ....................................................................................................................... 51 8.5 Send message +CMGS ....................................................................................................................... 53 8.6 Set text mode parameters +CSMP ...................................................................................................... 53 8.7 Delete SMS +CMGD ........................................................................................................................... 54 8.8 Unsolicited Response (new SMS-DELIVER receipt indication) +CMTI .................................................... 55 8.9 Write Message to Memory +CMGW ................................................................................................... 55 8.10 Send Message from Storage +CMSS ............................................................................................... 55

9 Supplementary services commands .......................................................................... 57 9.1 Calling line identification presentation +CLIP ...................................................................................... 57

10 Sprint OMA-DM provisioning commands ................................................................. 58 10.1 Enable/ Disable OMA-DM capabilities +OMADM ............................................................................ 58 10.2 Enable/ Disable PRL provisioning +PRL ............................................................................................. 58 10.3 Enable/ Disable FUMO provisioning +FUMO .................................................................................... 59 10.4 HFA Session Enable/Disable +UOMAHFA ........................................................................................ 59 10.5 Session Cancel +UOMADM ............................................................................................................. 60 10.6 Enable / Disable OMADM/FUMO unsolicited status messages +UOMASTAT .................................... 60 10.7 Roaming status $ROAM .................................................................................................................. 61 10.8 Device reset command $RTN ........................................................................................................... 61 10.9 Device power cycle command $RESET ............................................................................................. 61 10.10 Check data service command +SERVICE.......................................................................................... 62 10.11 Set IMSI Data +UIMSIDATA ............................................................................................................. 62 10.12 Set call termination enabled indicators +UMOBTERM ...................................................................... 63 10.13 Set Home SID/NID pair +USIDNIDPR ................................................................................................ 63 10.14 Write PRL file +UPRLWRITE ............................................................................................................. 64

11 Verizon OTA Provisioning commands ....................................................................... 66 11.1 Initiate OTA Provisioning (+CDV=*22899)....................................................................................... 66 11.2 OTA Provisioning Activation Indicator (+UACTIND) .......................................................................... 66

12 GPIO AT-commands .................................................................................................... 67 12.1 Introduction .................................................................................................................................... 67 12.2 LISA-C200 GPIO mapping ............................................................................................................... 67 12.3 GPIO select configuration command +UGPIOC ............................................................................... 67 12.4 GPIO read command +UGPIOR ....................................................................................................... 68



of 149

12.5 GPIO set command +UGPIOW ........................................................................................................ 69

13 Audio ........................................................................................................................... 70 13.1 Introduction .................................................................................................................................... 70 13.2 Microphone Gain (Microphone Gain Control) +UMGC ................................................................... 70 13.3 Speaker Gain (Speaker Gain Control) +USGC .................................................................................. 71 13.4 Sidetone (SideTone) +USTN ............................................................................................................. 72 13.5 Uplink Digital Filter +UUBF .............................................................................................................. 73 13.6 Downlink Digital Filters +UDBF ........................................................................................................ 74 13.7 Hands-Free Parameters +UHFP ........................................................................................................ 74 13.8 Audio Path mode setting (Set Path Mode) +USPM .......................................................................... 77 13.9 PCM Digital Interface Setup +UPCM ............................................................................................... 77 13.10 Play audio file +UPLAYFILE .............................................................................................................. 78 13.11 Stop audio file +USTOPFILE ............................................................................................................. 79

14 TCP/IP UDP/IP .............................................................................................................. 80 14.1 Introduction .................................................................................................................................... 80 14.2 Packet Switched Data Action Configuration +UPSDACFG ............................................................... 80 14.3 Packet Switched Data Action +UPSDA ............................................................................................ 81 14.4 Create Socket +USOCR ................................................................................................................... 81 14.5 Set Socket Option +USOSO ............................................................................................................. 82 14.6 Get Socket Option +USOGO ........................................................................................................... 83 14.7 Close Socket +USOCL ..................................................................................................................... 83 14.8 Get Socket Error +USOER ................................................................................................................ 84 14.9 Connect Socket +USOCO ............................................................................................................... 84 14.10 Write Socket Data +USOWR ........................................................................................................... 85 14.11 Socket Connection Timeout Control +USOABT ............................................................................... 86 14.12 Send To command +USOST (UDP only) ........................................................................................... 86 14.13 Read Socket Data +USORD ............................................................................................................. 88 14.14 Receive From command +USORF (UDP only) ................................................................................... 89 14.15 Set Listening Socket +USOLI ............................................................................................................ 90 14.16 Set socket in Direct Link mode +USODL .......................................................................................... 91 14.17 Socket Control +USOCTL ................................................................................................................ 92 14.18 Configure Maximum Segment Size +UMSS ..................................................................................... 93

15 DNS .............................................................................................................................. 94 15.1 Resolve Name / IP Number through DNS +UDNSRN ........................................................................ 94

16 File system AT Commands ......................................................................................... 95 16.1 Download File +UDWNFILE ............................................................................................................. 95 16.2 Delete File +UDELFILE ...................................................................................................................... 95 16.3 Read File +URDFILE ......................................................................................................................... 96 16.4 List Files Information +ULSTFILE ....................................................................................................... 96

17 FTP ............................................................................................................................... 98 17.1 FTP Control +UFTP .......................................................................................................................... 98



of 149

17.2 FTP Command +UFTPC ................................................................................................................... 99 17.3 FTP Unsolicited Data URC +UUFTPCD............................................................................................ 101 17.4 FTP Command Result URC +UUFTPCR........................................................................................... 102 17.5 FTP Error +UFTPER......................................................................................................................... 102

18 HTTP .......................................................................................................................... 103 18.1 HTTP Control +UHTTP ................................................................................................................... 103 18.2 HTTP Command +UHTTPC ............................................................................................................ 104 18.3 HTTP Command Result URC +UUHTTPCR ..................................................................................... 105 18.4 HTTP Protocol Error +UHTTPER ...................................................................................................... 106

19 GNSS .......................................................................................................................... 107 19.1 GNSS Power Management +UGPS ................................................................................................ 107 19.2 Assisted GNSS unsolicited indication +UGIND ............................................................................... 109 19.3 GNSS Profile configuration +UGPRF .............................................................................................. 110 19.4 AssistNow Online configuration +UGAOP ..................................................................................... 111 19.5 AssistNow Offline configuration +UGAOF ..................................................................................... 112 19.6 Aiding server configuration +UGSRV ............................................................................................. 113 19.7 GNSS Aiding request command +UGAOS ..................................................................................... 115 19.8 Send of UBX string +UGUBX ......................................................................................................... 115 19.9 GNSS Indications timer +UGTMR .................................................................................................. 116 19.10 Get GNSS Time and date +UGZDA ................................................................................................ 117 19.11 Get GNSS fix data +UGGGA ......................................................................................................... 117 19.12 Get geographic position +UGGLL .................................................................................................. 118 19.13 Get number of GNSS satellites in view +UGGSV ........................................................................... 119 19.14 Get recommended minimum GNSS data +UGRMC ....................................................................... 120 19.15 Get course over ground and ground speed +UGVTG .................................................................... 120 19.16 Get satellite information +UGGSA ................................................................................................ 121 19.17 Ask for localization information +ULOC ........................................................................................ 122 19.18 Configure GNSS sensor +ULOCGNSS ............................................................................................ 124 19.19 Configure cellular location sensor (CellLocate®) +ULOCCELL ........................................................ 126 19.20 Get Base Station LAT/LONG +UBSLOC .......................................................................................... 127

20 Specific ...................................................................................................................... 128 20.1 Change data connection settings +UDCONF ................................................................................. 128 20.2 Start and stop tone generation +UVTS .......................................................................................... 128 20.3 Transmit and Receive States +UTEST ............................................................................................. 129 20.4 Firmware Update over AT command (FOAT) +UFWUPD ................................................................ 131

A Appendix 1 ............................................................................................................... 133 A.1 Networking error class ...................................................................................................................... 133 A.2 Internal TCP/UDP/IP stack error codes ............................................................................................... 137 A.3 Mobile Termination error result codes +CME ERROR ........................................................................ 139 A.4 Message service failure result codes +CMS ERROR ............................................................................ 140

B AT Commands List .................................................................................................... 141



of 149

B.1 Parameters stored in non-volatile memory ........................................................................................ 141

C Glossary .................................................................................................................... 143

Related documents......................................................................................................... 146

Revision history .............................................................................................................. 148

Contact ............................................................................................................................ 149


UBX-13000621 - R10 Production Information Introduction

of 149

1 Introduction

1.1 Purpose This document describes the u-blox AT Commands used for the FW75-C200 and LISA-C200 product families, including:

1. IS707.3 AT commands

2. GSM 07.07 when applicable

3. GSM 07.05 when applicable

4. ITU-T v25 when applicable

5. u-blox proprietary AT commands for M2M features and enhancements

6. Carrier specific AT commands

1.2 Definitions In this document the following naming conventions are used:

• DCE (Data Communications Equipment) or MT (Mobile Terminal): u-blox cellular module

• DTE (Data Terminal Equipment) or TE (Terminal Equipment): terminal that sends commands to the module

Some modules implement more than one interface between DTE and DCE, either virtual interfaces (MUX channels) or physical interfaces (UART, USB, SPI, etc., when available). Each interface works as specified by the followings definitions. If not differently stated, all the subsequent descriptions are applicable to every interface.

1.3 AT commands mode

1.3.1 Action command An Action command is used to force the DCE to transmit information or execute a specific action for the command. A typical usage of this command mode is to provide the manufacturer settings proper of the DCE like manufacturer name, firmware version, etc.

1.3.2 Set command A Set command is performed to set the preferred settings for the specific command. The set command is the only way to set the preferred settings in the DCE.

NOTE: Unless specifically stated, settings are not stored in Non-Volatile memory and will be lost when the modem is power-cycled.

1.3.3 Read command A Read command provides the current values of the command parameters. It is used to know the last configuration of the parameters of the command.

1.3.4 Test command A Test command provides the complete list of the values supported by each parameter of the command.

1.3.5 Unsolicited Result Code (URC) An unsolicited result code is a string message (provided by the DCE) which is not a response to a previous AT command and can be output, when enabled, at any time to inform the DTE of a specific event or status change. The URC can have the same name of the command that enables it (e.g. +CREG) or can be enabled by another command (e.g. unsolicited result code: +CMTI, command that enables it: +CNMI).


UBX-13000621 - R10 Production Information Introduction

of 149

1.3.6 Intermediate Result Code (IRC) An intermediate result code is a string message (provided by the DCE) which informs the DTE of the processing status of the pending AT command.


UBX-13000621 - R10 Production Information IPC – Inter Processor Communication

of 149

2 IPC – Inter Processor Communication

2.1 Multiplexing mode +CMUX

2.1.1 Description Enables the multiplexing protocol control channel as defined in 3GPP 27.010. (For more details refer to 3GPP TS 27.010 V3.4.0 - Terminal Equipment to User Equipment (TE-UE) multiplexer protocol [43].) The command sets parameters for the control channel. If parameters are not specified, the default values are used. The response code is returned using the original interface baud rate. The parameters become active only after sending “OK”. The multiplexer supports 3 channels as follows:

• Channel 0: control channel, transparent to applications. • Channel 1: AT command channel, this channel is used for all AT commands except the ATD#777

command, which sets up a data call. • Channel 2: data channel, this channel is used for data calls and is only set up by ATD#777.

The multiplexer implementation has these limitations:

• When an AT command has been sent on channel 1, the application must wait for a response prior to sending the ATD#777 command on channel 2 and vice versa.

• When a data call is active on channel 2, the application can’t use any AT commands that require data services on channel 1. This includes; FTP, HTTP and sockets.

• The CMUX command can’t be used again once the multiplexer has been enabled. • The UART baud rate can’t be changed once the multiplexer has been enabled, so the +IPR command

should be used to set the desired baud rate prior to using +CMUX. • The multiplexer frame size, N1, must typically be greater than 64, below this size there may be issues

with the host to modem PPP data transfers.

Type Syntax Response Example

Set AT+CMUX=<mode>[,<subset>[,<port_speed>[,<N1>]]]

OK AT+CMUX=0,0,0,32 OK

Read AT+CMUX? +CMUX=<mode>,<subset>,<port_speed>,<N1> OK

+CMUX: 0, 0, 0, 32 OK

Test AT+CMUX=? +CMUX: (list of supported <mode>s), (list of supported <subset>s), (list of supported <port_speed>s), (list of supported <N1>s) OK

+CMUX: 0, 0, 0, (1-256) OK

The user needs to set baud rate using IPR before enabling the MUX. Once MUX is running, this command cannot be used to change the baud rate.

2.1.2 Defined Values Parameter Type Description

<mode> number Mux Mode 0 = basic mode , only basic mode is supported, any other value return error

<subset> number Defines how MUX control channel is setup. 0 = UIH frames use only , any other value return error

<port_speed> number Port speed 0 = no change, do not support baud rate change through this API, any other value return error

<N1> number Maximum Frame Size If blank default will be used of 32, 0 should return error, valid range 1-256, any other value returns Error


UBX-13000621 - R10 Production Information General commands

of 149

3 General commands

3.1 Device Information ATI

3.1.1 Description This command returns the device information like Manufacturer, Model, Revision, MEID.


Action ATI <Info>

OK

Manufacturer: UBLOX

Model: LISA-C200 or FW75-C200

Revision: E0.S.04.00.01R

MEID: 270113179708322920

0xA10000157EFF68

+GCAP: +CIS707-A, +MS, +ES, +DS, +FCLASS

OK


<Info> String Manufacturer Information

Model ID

Firmware Revision

MEID (Decimal)

MEID (Hexadecimal)

Protocol

Modulation Control

Error Control

Data Compression

Facsimile modem Control

3.2 Request Manufacturer Identification +GMI

3.2.1 Description Text string, determined by the manufacturer, identifying the manufacturer.


Action AT+GMI <manufacturer>

OK

u-blox

OK


<manufacturer> String Manufacturer name



of 149

3.3 Request model identification +GMM

3.3.1 Description Text string, determined by the manufacturer, identifying the model identification.


Action AT+GMM <model>

OK

FW75-C200

OK


<model> Number Model ID. Currently FW75-C200 or LISA-C200

3.4 Request revision identification +GMR

3.4.1 Description Returns the firmware version of the module.


Action AT+GMR <version>

OK

E0.S.02.00.01

OK


<version> String Firmware version of the device.

3.5 Request product serial number identification +GSN

3.5.1 Description Return the pseudo ESN or MEID.


Action AT+GSN <decimal value of MEID>

<Hexadecimal value of MEID>

OK

270113179708322904

0xA10000157EFF58

OK


<decimal value of MEID> Number Decimal value of MEID

<Hexadecimal value of MEID> Hex Number Hex-decimal value of MEID



of 149

3.6 Request international mobile subscriber identification +CIMI

3.6.1 Description Return 15-digit IMSI (International Mobile Subscriber Identity).


Read AT+CIMI <imsi>

OK

310009132017368

OK


<imsi> Number IMSI of the device, in this format <MCC><IMSI 11_12><IMSI_S>. IMSI 11_12 will have values 00, 01, 02 etc

3.7 DTE-DCE local flow control +IFC

3.7.1 Description This command controls the operation of local flow between the DTE and DCE.


Set AT+IFC=[<m>[,<n>]] OK AT+IFC=0,0

OK

AT+IFC=2,2 ( Default Value )

OK

Read AT+IFC? +IFC: <m>,<n>

OK

+IFC: 2,2

OK

Test AT+IFC=? +IFC: (list of supported formats<m>s in <DCE_by_DTE>),(list of supported formats<n>s in <DTE_by_DCE>)

OK

+IFC: (0,2),(0,2)

OK


<m> Number 0: none 2: RTS

<n> Number 0: none 2: CTS

On the UART interface and if +UPSV=2, only +IFC=0,0 (no flow control) is allowed.



of 149

3.8 Set the DTE Rate +IPR

3.8.1 Description This command provides a method to change the DTE(modem) Transmit and Receive baud rates. Currently baud rate auto detect is not supported.


Set AT+IPR=[<rate>] OK AT+IPR=115200

OK

Read AT+IPR? +IPR: <rate>

OK

+IPR: 115200

OK

Test AT+IPR=? +IPR: (list of baud rates)

OK

+IPR: (2400,4800,9600,19200,38400, 57600,115200, 230400)

OK


<rate> Number Baud rate:

2400, 4800, 9600, 19200, 38400, 57600, 115200(default value), 230400

3.9 Set the Rm interface protocol +CRM

3.9.1 Description This command enables set the protocol on Rm interface.


Set AT+CRM=<n> OK AT+CRM=2

Read AT+CRM? +CRM: <n>

OK

+CRM: 2

OK

Test AT+CRM=? +CRM: (list of supported <n>)

OK

+CRM: (0-2)

OK


<n> Number 0: asynchronous data or fax 1: packet data service, Relay Layer Rm interface 2: packet data service, Network Layer Rm interface, PPP (DEFAULT VALUE)

To set CRM as 0 or 1, you need to first change to SIP only mode by AT$QCMIP=0.

The settings are saved in NV memory and maintained through power cycle.



of 149

3.10 Read the PRL ID $PRL

3.10.1 Description This command reads the current PRL ID saved in the active NAM.


Read AT$PRL? <n>

OK

10077


<n> Number PRL ID

3.11 Read/write the current MDN $MDN

3.11.1 Description This command reads or writes the current 10-digit MDN (Mobile Directory Number) related to the subscriber.


Set AT$MDN=<MSL>,<number> OK AT$MDN=000000, 8588479611

OK

Read AT$MDN? <mdn>

OK

8588479611

OK


<MSL> Number 6 digit MSL

<mdn> Number 10 digit MDN of the device

3.12 Read/write the current MSID $MSID

3.12.1 Description This command reads or writes the current 10-digit MSID related to the subscriber.


Set AT$MSID=<MSL>,<number> OK AT$MSID=000000, 8588479611

OK

Read AT$MSID? <number>

OK

8588479611

OK


<MSL> Number 6 digit MSL

<msid> Number 10 digit MSID of the device



of 149

3.13 Set the Echo ON/OFF E

3.13.1 Description This command determines whether input characters are echoed to output.


Set ATE<value>

OK ATE1

OK

3.13.2 3.13.2 Defined Values Parameter Type Description

<value> Number 0: Echo off 1: Echo on (Default)

3.14 Set the Result Code Suppression ON/OFF Q

3.14.1 Description Determines if DCE transmits result codes to the DTE or not. When result codes are being suppressed, no

portion of any intermediate, final or URC is transmitted. Information text transmitted in response to commands

is not affected by this setting


Set ATQ<value>

OK ATQ0

OK


<value> Number 0: DCE transmits result codes (Default) 1: Result codes are suppressed and not transmitted

3.15 Response Format V

3.15.1 Description This command determines the response format of the data adapter and the contents of the header and trailer transmitted with the result codes and information responses. This command also determines whether the result codes are transmitted in a numeric or an alphabetic (“verbose”) form. The text portion of information responses is not affected by this setting.


Set ATV<value>

OK ATV1

OK


<value> Number 0: DCE transmits limited headers and trailers and numeric result codes 1: DCE transmits full headers and trailers (Default)



of 149

3.16 HW version +UHWVER

3.16.1 Description This command returns the model and hardware version.


Read AT+UHWVER? <HW Version>

OK

AT+UHWVER?

LISA-C200,0.4

OK


<hw_version> String The versions of HW supported.

3.17 Returns Temperature +UTEMP

3.17.1 Description This command returns the temperature of crystal oscillator.


Read AT+UTEMP? <XO_temp >

OK

AT+UTEMP?

25

OK

3.17.2 Defined Values Parameter Type Range Description

<XO_temp> Number -30 C to 80 C Temp of crystal oscillator in degree Celsius.

3.18 Antenna detection AT+UANTR

3.18.1 Description Measures the DC component of the CDMA Antenna load. The antenna load is expressed in kΩ (kilo-ohm).

NOTE: The antenna load resistor should be in the range 10 kΩ to 20 kΩ to avoid invalid test results.


Set AT+UANTR=<antenna_id> +UANTR:

<antenna_id>,<antenna_load>

OK

AT+UANTR=0

+UANTR: 0,20

OK



of 149


Test AT+UANTR=? +UANTR: (list of supported

<antenna_id>s)

OK

AT+UANTR=?

+UANTR: (0)

OK


<antenna_id> Number Antenna identifier (optional parameter)

0: CDMA antenna

<antenna_load> Number Measured value in kΩ of the antenna load with a resolution of 1 kΩ. The range goes from -1 to 37 (only integer values can be assumed), where:

-1: open circuit

0: short circuit

1: 1 kΩ (minimum limit of the measurement range)

…

37: 37 kΩ (maximum limit of the measurement range)

Load resistor values below the minimum limit of 1 kΩ are identified as short circuit (<antenna_load>=0), while values above the maximum limit of 37 kΩ are identified as open circuit (<antenna_load>=-1).

+UANTR is supported on LISA-C200 only.

3.19 Set up Aeris PRI (special RTN for Aeris) +UAERIS

This command is supported by Sprint version only

3.19.1 Description This command sets the module to Aeris default PRI and power cycle the device. This command only works for Sprint release.


Set AT+UAERIS=<build type> OK AT+UAERIS=0

OK

Read AT+UAERIS? +UAERIS: <build type>

OK

AT+UAERIS?

+UAERIS: Aeris build

OK

(or)

AT+UAERIS?

+UAERIS: Non Aeris Build (Sprint)

OK

Test AT+UAERIS =? +UAERIS: (list of supported build type)

OK

AT+UAERIS=?

+UAERIS: (0)

OK



of 149


<build type> Number 0: Aeris build

Change Sprint PRI settings to Aeris default PRI.

Only works for Sprint build.

You can switch back and forth only between Sprint and Aeris PRI.

To switch back to Sprint build, you can run $RTN.

AT$RTN=000000

OK

3.20 Update ACCOLC +UPACCOLC

This command is supported by Sprint version only

3.20.1 Description This command sets the AOC=ACCOLC to the correct value per the carrier requirements after there is an update to the MSID.


Set AT+UPACCOLC OK AT+UPACCOLC

OK

3.21 Set up US Cellular PRI (special RTN for US Cellular) +UUSCELL

This command is supported by Verizon version only

3.21.1 Description This command sets the module to US Cellular default PRI and power cycle the device. This command only works for Verizon release.


Set AT+UUSCELL=<build type> OK AT+UUSCELL=3

OK

Read AT+USCELL? +UUSCELL: <build type>

OK

AT+UUSCELL?

+UUSCELL: US Cellular Build

OK

(or)

AT+UUSCELL?

+UUSCELL: Non US Cellular Build (Verizon)

OK

Test AT+UUSCELL=? +UUSCELL: (list of supported build type)

OK

AT+UUSCELL=?

+UUSCELL : (3)

OK



of 149


<build type> Number 3: US Cellular build

Change Verizon PRI settings to US Cellular default PRI.

Only works for Verizon build.

You can switch back and forth only between Verizon and US Cellular PRI. To switch back to Verizon build, you can run $RTN.


UBX-13000621 - R10 Production Information Mobile equipment control and status commands

of 149

4 Mobile equipment control and status commands

4.1 Phone activity status +CPAS

4.1.1 Description This command returns the activity status <pas> of the MT.


Action AT+CPAS +CPAS: <pas>

OK

+CPAS: 0

OK

Test AT+CPAS=? +CPAS: (list of supported <pas>s)

OK

+CPAS: (0,1,3,4)

OK


<pas> Number 0: ready (MT allows commands from DTE) 1: Unavailable (MT does not allow commands from DTE) 3: ringing (MT is ready for commands from DTE, but the ringer is active) 4: call in progress (MT is ready for commands from DTE, but a call is in progress, e.g. call active, hold, disconnecting)

4.2 Switch off MT +CPWROFF

4.2.1 Description This command powers off the modem by means of the modem software. This command should always be used to power down the modem as during this power down critical RF calibration values are saved in Non-volatile memory.

Powering off the modem by simply removing the power supply is not recommended and should be avoided.

After ending the CPWROFF command an OK is returned before the power down process is started. So it’s prudent to wait at least 5 seconds before commencing communication with the modem again.


Action AT+CPWROFF OK

Shut down the MT and return OK.

Test AT+CPWROFF=? OK

Returns OK. But do not shut down the MT.



of 149

4.3 Device reset command $RTN

4.3.1 Description This command sets the module to factory defaults and power cycle the device if the current MSL

is entered.


Action AT$RTN=<MSL> OK AT$RTN=000000

OK

Note: After the correct MSL is entered, the device will power cycle and set to factory defaults.


<MSL> Number It is the 6-digit device MSL.

4.4 Set phone functionality +CFUN

4.4.1 Description This command selects level of functionality <fun> in the MT.


Set AT+CFUN=<fun> OK AT+CFUN=1

OK

Read AT+CFUN? +CFUN: <mode>

OK

+CFUN: 0

OK

Test AT+CFUN=? +CFUN: (list of supported <fun>’s)

OK

+CFUN: (0,1,2)

OK


<fun> Number Selected functionality

0: Normal operation. 1: Reset the modem. 2: RF Tx and Rx circuits disabled.

<mode> Number 0: Normal operation mode. 2: Low power mode.

4.5 Power Saving control +UPSV

4.5.1 Description This command lets you set up the low power mode



of 149

• If power saving is enabled (+UPSV=1), the UART interface is cyclically enabled and the module enters idle-mode automatically whenever possible

• If power saving is disabled (+UPSV=0), the UART interface is always enabled and the module does not enter idle-mode

• If power saving is controlled by the UART RTS signal (+UPSV=2), the UART interface is enabled and the module does not enter idle-mode as long as the UART RTS line is ON


Set AT+UPSV=<mode>,<timeout> OK AT+UPSV=1,1280

OK

Read AT+UPSV? +UPSV: <mode>,<timeout>

OK

+UPSV: 1,1280

OK

Test AT+UPSV=? +UPSV: (list of supported <mode>’s), (list of supported <timeout>’s)

OK

+UPSV: (0,1,2,4),(40-300000)

OK


<mode>

Number Selected functionality

0: Normal operation. ( Default ) 1: enabled

• The UART is re-enabled from time to time to give to the DTE a chance for the transmission and the module switches from idle to active-mode in a cyclic way. If during the active-mode any data is received, the UART (and the module) is forced to stay "awake" for a time specified by the <Timeout> parameter. Any subsequent data reception during the "awake" period resets and restarts the "awake" timer

2: power saving is controlled by UART RTS signal:

• If the RTS state is set to OFF, the power saving mode is allowed • If the RTS state is set to ON, the module shall exit from power saving mode

<mode>=2 is allowed only if HW flow control has been previously disabled on UART interface (e.g. with AT+IFC=0,0,), otherwise the command returns an error response.

4: Low Power:

• After setting the module to the low power mode, we need to reset the module. After the module is up and running, you should be able to read the UPSV mode : 4 which means that the module is in Low Power consumption mode.

<Timeout> Number If <mode>=1 and active-mode entered, provides the guard period of no reception of characters on the UART interface, expressed in ms, before entering idle-mode again.

• The range goes from 40 to 300000 ; the default value is 1280 ms. • This parameter is accepted only when <mode>=1

Timeout value for mode 1 will not be saved in NVM. After we reboot the module, timeout value is lost and will be set to the default timeout value.

When mode 1 is enabled, the UART is re-enabled from time to time to give the DTE a chance for the transmission, and the module switches from idle to active–mode in a cyclic way. If during active-mode any data is received, the UART (and the module) is forced to stay “awake” for a time specified by the <Timeout> parameter. Any subsequent data reception during the “awake” period resets the “awake” timer.

<mode>= 1 and <mode>= 2 are applicable only in reference to the UART interface, even if the command is accepted by all the serial interfaces. If the command is issued on the USB/MUX channel, all the AT profiles are accordingly update, but the setting is only applied to the UART interface.



of 149

4.6 Indicator control +CIND

4.6.1 Description The command provides indication states related to network status, memory and so on.

In Set mode, the command does not allow setting the values for those indications which are set according to module state (see <descr> parameter).

The list of indications for set and read follows the indexes reported in the <descr> parameter, so that the first <ind> corresponds to “signal” and so on.

For more details, refer to 3GPP TS 27.007 Technical Specification [2].


Read AT+CIND? +CIND: <signal>,<service>,<message>,<call>, <roam>,<smsfull>,<callsetup>,<ruimcard>

OK

+CIND: 5,1,0,0,0,0,0,0

OK

Test AT+CIND=? +CIND: (list of <descr>s)

OK

+CIND: ((signal,(0-5)),(service,(0-1)),(message,(0-1)),(call,(0-1)),(roam,(0-1)),(smsful,(0-1)),(callsetup,(0-3)), (ruimcard,(0-1)))

OK


<descr> String Reserved by the norm and their <ind> ranges; it may have the values:

• "signal": signal quality o 0: < -107 dBm o 1: < -93 dBm o 2: < -81 dBm o 3: < -69 dBm o 4: < - 57 dBm o 5: >= -57 dBm

• "service": network service availability o 0: Not registered to the network o 1: Registered to the network

• "message": Unread message available in <mem1> storage o 0: no messages o 1: unread message available

• "call": call in progress o 0: No call in progress o 1: Call in progress

• "roam": Registration on a roaming network o 0: Not in roaming o 1: Roaming

• "smsfull": Indication that an SMS has been rejected with the cause of SMS storage full o 0: SMS storage not full o 1: SMS Storage full

• "callsetup" : call set-up: o 0: no call set-up o 1: incoming call not accepted or rejected o 2: outgoing call in dialing state o 3: outgoing call in remote party alerting state

• "ruimcard" : RUIM card: o 0: no R-UIM card available. The value is also applicable to non R-UIM

module o 1: R-UIM card is available



of 149

The <descr> values cannot be changed with +CIND set.

4.7 Clock +CCLK

4.7.1 Description This command reads the network-time from the MT.


Read AT+CCLK? +CCLK: <time>

OK

+CCLK: 12/07/09,17:14:50-28

OK


<time> String It reports the UTC time with local time zone information. Format is "yy/MM/dd,hh:mm:ss±TZ ". Characters indicate year, month, day, hour, minutes, seconds, time zone.

“TZ”: The Time Zone information is represented by two digits and is expressed in steps of 15 minutes.

4.8 Mobile termination event reporting +CMER

4.8.1 Description Enables or disables sending of URCs from MT to DTE for indications. <mode> parameter controls the processing of URCs specified within this command.

The URC is generated each time an indicator defined in the +CIND command changes status. The code is submitted to MT according to the settings of +CMER.


Set AT+CMER=[<mode>] OK AT+CMER=1

OK

Read AT+CMER? +CMER: <mode>

OK

+CMER: 1

OK

Test AT+CMER=? +CMER: (list of supported <mode>’s)

OK

+CMER: (0-1)

OK

URC +CIEV: <descr>,<value>


<mode> Number 0: disable 1: enable

<descr> Number 1 ("signal"): <value> provides the signal quality • 0: < -107 dBm • 1: < -93 dBm • 2: < -71 dBm • 3: < -69 dBm



of 149

Parameter Type Description

• 4: < - 57 dBm • 5: >= -57 dBm

2 ("service"): <value> provides the network service availability • 0: Not registered to the network • 1: Registered to the network

3 ("message"): <value> provides the unread message available in <mem1> storage • 0: no messages • 1: unread message available

4 ("call"): <value> provides the call in progress • 0: No call in progress • 1: Call in progress

5 ("roam"): <value> provides the registration on a roaming network • 0: Not in roaming • 1: Roaming

6 ("smsfull"): <value> provides the indication that an SMS has been rejected with the cause of SMS storage full

• 0: SMS storage not full • 1: SMS Storage full

7 ("callsetup") : <value> provides the call set-up: • 0: no call set-up • 1: incoming call not accepted or rejected • 2: outgoing call in dialing state • 3: outgoing call in remote party alerting state

8 ("R-UIM ready") : <value> provides the R-UIM state: • 0: R-UIM ready

9 ("R-UIM Removal Indication") : <value> provides the information on R-UIM card removal ( The software doesn’t support card insertion/detection ):

o 0: R-UIM card removed from phone. This value is not supported on non R-UIM modules

The settings are saved not in NV memory.

4.9 Report mobile termination error +CMEE

4.9.1 Description Enables or disables the use of result code +CME ERROR: <err> as an indication of an error relating to the functionality of the MT. When enabled, MT related errors cause +CME ERROR: <err> final result code instead of the regular ERROR final result code. ERROR is returned normally when the error is related to syntax, invalid parameters or MT functionality.


Set AT+CMEE=[<n>] OK AT+CMEE=2

OK

Read AT+CMEE? +CMEE: <n>

OK

+CMEE: 0

OK

Test AT+CMEE=? +CMEE: (list of supported <n>s)

OK

+CMEE: (0-2)

OK


<n> Number 0: disable +CME ERROR: <err> result code and use ERROR instead (Default) 1: enable +CME ERROR: <err> result code and use numeric <err> values 2: enable +CME ERROR: <err> result code and use verbose <err> values



of 149

The settings are saved not in NV memory.

4.10 Reset to factory default without resetting NAM (special RTN) +UCLEAN

4.10.1 Description This command resets the device to factory defaults without resetting the NAM.


Set AT+UCLEAN=<MSL> OK AT+UCLEAN=000000

OK

Note: After the correct MSL is entered, the device will power cycle and set to factory defaults except for NAM.


<MSL> Number It is the 6-digit device MSL.

4.11 Provision State +UPROVSTATE

4.11.1 Description The +UPROVSTATE command returns an indication as to whether or not the cellular module has ever been provisioned over-the-air (e.g. thru OMADM).

Type Syntax Response Examples

Read AT+UPROVSTATE? +UPROVSTATE : <prov_flag>

OK

+UPROVSTATE: 1

OK

4.11.2 Defined values Parameter Type Description

<prov_flag> Number Provides the current provisioning status.

0: Module has not been provisioned over-the-air 1: Module has been provisioned over-the-air


UBX-13000621 - R10 Production Information Call control commands

of 149

5 Call control commands

5.1 Dial command D

5.1.1 Description This command lists characters that may be used in a dialing string for making a data call or controlling supplementary services in accordance with the indicated kind of call. The default call type is data call, for example atd#777 for 1XRTT CDMA Data Call.


Action ATD<number> See 5.1.2 “Responses” (Supplementary Services)

ATD#777

CONNECT

5.1.2 Responses The following table lists the possible responses to the command. The response is formatted using the ATV command.

Verbose Numeric Description

OK 0 Acknowledges successful execution of the command; this response is provided only during voice calls

CONNECT 1 A connection has been established

NO CARRIER 3 The connection was terminated by the remote party or the attempt to establish a connection failed

ERROR 4 General failure

BUSY 7 Engaged signal detected (the called number is busy)

NO ANSWER 8 If no hang up is detected after a fixed network timeout

CONNECT<data rate> 9 Same as CONNECT but includes the data rate (data call)

5.2 Call answer A

5.2.1 Description This command instructs the DCE to answer the incoming voice call after a RING indication show to the terminal.


Action ATA OK RING

ATA

OK

5.3 Dial voice call +CDV

5.3.1 Description This command dials a voice calls.


Action AT+CDV=<number> OK AT+CDV=1234567890

OK

Special characters like “Pause” are not supported by this command.



of 149

5.4 Hang Up voice call +CHV

5.4.1 Description This command hangs up a voice calls.


Action AT+CHV OK AT+CHV

OK

5.5 Hang up call +CHUP

5.5.1 Description Causes the MT to hang up the current call.

In case of multiple calls, all active calls will be released, while waiting and held calls are not.

The command does not replace the ITU-T V.250 [20] command H, but gives an assured procedure to terminate an alternating mode call. For further information refer to 3GPP TS 27.007 [2][2].


Action AT+CHUP OK AT+CHUP

OK

Test AT+CHUP=? OK AT+CHUP=?

OK

This command is supported from version x3S onwards.

5.6 Call status messages +UCST

5.6.1 Description This command enables/disables the unsolicited indication of any change in the call processing state.


Set AT+UCST=<n> OK AT+UCST=1

OK

Read AT+UCST? +UCST:<n>

OK

+UCST:1

OK

URC +UCST:<status>

+UCST:1


<n> Number 0: Disables URC 1: Enables URC

<status> Number 1: Idle State

3: Active Call State

68: No Service



of 149

5.7 Extended error report +CEER

5.7.1 Description This command causes the MT to return one or more lines of information text <report>, determined by the MT manufacturer, which offer an extended report of the reason for:

• The failure in the last unsuccessful call setup or in-call modification

• The last call release


Action AT+CEER +CEER: <type>[,<cause>, <error_description>][,<SS_cause_error>][, <tag>, <SS_cause>]

OK

+CEER: normal, NO CARRIER

OK

Test AT+CEER=? OK

5.8 Tone Duration +VTD

5.8.1 Description This command refers to an integer <n> that defines the length of tones emitted as a result of the +VTS command.

The effective maximum DTMF tone duration is network dependent, i.e. the receiver can experience a shorter tone duration than the one specified with +VTD (or with +VTS).


Set AT+VTD=[<n>],[<m>] OK AT+VTD=150,100

OK

Read AT+VTD? +VTD: <duration>,<interval>

OK

+VTD: 150, 100

OK

Test AT+VTD=? +VTD: (list of supported <duration>s), (list of supported <interval>s)

OK

+VTD: (95, 150, 200, 250, 300, 350),(60, 100, 150, 200)

OK


<duration> Number It specifies the length of DTMF tones in msec. Possible values are 95, 150, 200, 250, 300 & 350. Default is 350 msec, if not specified in +VTD command.

<interval> Number It specifies the interval between tones in msec. Possible values are 60, 100, 150 and 200. Default is 200 msec, if not specified in +VTD command.



of 149

5.9 DTMF and tone generation +VTS

5.9.1 Description This command allows transmission of DTMF tones. These tones may be used e.g. when announcing the start of a recording period. The command can only be used during an active voice call. If the optional parameter <duration> is left out or set to 0. The tone duration is given by the setting +VTD (see +VTD description). The command is abort able if a character is sent to DCE during the command execution, and it is not covered by the 3GPP specification. Type Syntax Response Example

Set AT+VTS=<DTMF>,[<duration>],[<interval>]]

OK AT+VTS=150

OK

Test AT+VTS=? +VTS: (list of supported <DTMF>s), (list of supported <duration>s), (list of supported <intervals>s)

OK

+VTS: (0-9,#,*),(0, 95, 150, 200, 250, 300, 350),(60, 100, 150, 200)

OK


<DTMF> Number String of ACII characters in the set 0-9, #, *.

<duration> Number It specifies the length of DTMF tones in msec. Possible values are 0, 95, 150, 200, 250, 300 & 350.(350 ms is the default value, if not specified in +VTS or +VTD)

<interval> Number It specifies the interval between tones in msec. Possible values are 60, 100, 150 and 200. (200 ms is the default value, if not specified in +VTS or +VTD)

If 0 is used for duration, then a value of 350 will be used instead

If the command is invoked when not in a call, an error is reported (“CME ERROR: no connection to phone” if +CMEE is set to 2).

5.10 Configure Ring Indicator +URINGCFG

5.10.1 Description The +URINGCFG command is used to configure when the RI (Ring Indicator) is signaled. By default, all events (SMS received, Incoming Voice call and Incoming Data call) will trigger the ring indicator. The settings can be combined such that AT+URINGCFG=3 will enable the RI for both SMS and Data. The setting reverts to default upon reset or power cycle.


Set AT+ URINGCFG=<config> OK AT+ URINGCFG =1

OK

Read AT+URINGCFG? +URINGCFG: <curent config> +URINGCFG: 0

OK

Test AT+ URINGCFG=? +URINGCFG: (valid config supported)

OK

+ URNIGCFG: (0-7)

OK



of 149


<config> Number 0: SMS, data and voice ringers are disabled

1: SMS ringer is enabled

2: Data ringer is enabled

4: Voice ringer is enabled

7: SMS, Data, Voice ringers are all enabled (default value)

5.11 Configure Call precedence during socket operations +USORNGCFG

5.11.1 Description The +USORNGCFG command is used to configure the precedence of an incoming call over an existing data call during socket operation. By default, if the device has a data call up and is performing socket operations, an incoming call will terminate the data call. To prevent interruptions by calls during socketed data operations, set the +USORNGCFG=1.


Set AT+ USORNGCFG=<config> OK AT+ USORNGCFG =1

OK

Read AT+USORNGCFG? +USORNGCFG: <curent config> +USORNGCFG:0

OK

Test AT+ USORNGCFG=? +USORNGCFG: (valid config supported)

OK

+ USORNGCFG: [0,1]

OK


<config> Number 0: Incoming call (default)

1: Data call

5.12 Read call status +UCSTRD

5.12.1 Description This command displays the current state of the call processing.


Read AT+UCSTRD? +UCSTRD:<status>

OK

+UCSTRD:1

OK


<status> Number 1: Idle State

3: Active Call State

68: No Service


UBX-13000621 - R10 Production Information Network service commands

of 149

6 Network service commands

6.1 Network Service information +USVC

6.1.1 Description This command displays general information about the current network. (Note: Additional information may later be appended to the output of this command in future releases. Consequently, any unexpected data found beyond the last parameter should be ignored, not tagged as an error.)

Set command returns “ERROR” if an invalid number parameter is entered regardless of the value of +CMEE.


Set AT+USVC=<n> OK

Or

ERROR

AT+USVC=1

OK

Read AT+USVC? +USVC: <n><in_svc>,<roaming>

OK

+USVC: 0,1,1

OK

Test AT+USVC=? +USVC: (list of supported <n>s) +USVC: (0-1)

OK

URC +UUSVC:<in_svc>,<roaming> +UUSVC:1,0


<n> Number 0: To disable the general information unsolicited result code.

1: To enable the general information unsolicited result code +USVC

<in_svc>,<roaming>

<in_svc> Number 0: Not in service

1: In service

<roaming> Number 0: Home

1: Roaming – same network

2: Roaming – different network

6.2 Signal quality +CSQ

6.2.1 Description Returns Signal Quality Measure <sqm> and the Frame Error Rate <fer> from the MT.


Action AT+CSQ <sqm>,<fer>

OK

+CSQ: 27,99

OK



of 149


Test AT+CSQ=? +CSQ: (list of supported <sqm>s,(list of supported <fer>s)

OK

+CSQ: (0-31,99),(99)

OK


<sqm> Number Signal Quality Measure

0..30: from -113 to -76 dBm 31: -75 dBm or greater 99: not known or not detectable

<fer> Number Frame Error Rate

99: not known or not detectable.

6.3 Network registration and roaming information +CREG

6.3.1 Description This command displays the indication of the current network registration and roaming status.


Set AT+CREG=<n> OK

Or

+CME ERROR: <err>

AT+CREG=1

OK

Read AT+CREG? +CREG: <n><SID>,<NID>,<stat>

OK

+CREG: 0,4145,7,1

OK

Test AT+CREG=? +CREG: (list of supported <n>s)

OK

+CREG: (0-1)

OK

URC +CREG:<SID>,<NID>,<stat>

+CREG:4145,86,2


<n> Number 0: To disable the network registration unsolicited result code.

1 : To enable the network registration unsolicited result code +CREG:

<SID>,<NID>,<stat>.

<SID> Number Home SID from 0 to 32767

<NID> Number Network ID from 0 to 65535

<stat> Number 0: Not registered.

1: Registered, home network.

2: Not registered, but the ME is currently searching for a new operator to which to register.

3: Registration denied.

5: Registered, roaming.



of 149

6.4 Return the debugging information $DEBUG

6.4.1 Description This command displays the debugging information for 1XRTT only.


Test AT$DEBUG? $DEBUG: <SID>,<NID>,<CH>,<BAND>,<FER>,<TXP>,<RXP>,<usedSCI>,<namSCI>,<maxSCI>,<PN0>,<PN 1>,<PN 2>,<PN 3>,<PN 4>,<PN 5>,<pilotEcIo0>,<pilotEcIo1>,<pilotEcIo2>,<pilotEcIo3>,<pilotEcIo4>,<pilotEcIo5>

OK

$DEBUG: 4145,7,25,1,99,-9,-105,2,2,2,123,477,183,309,174,210,9,25,63,63,63,63

OK



< NID > Number Network ID from 0 to 65535

<CH> Number Current frequency Channel Range from 0 to 2047

<BAND> Number Current band class

<FER> Number Frame Error Rate

<TXP> Number transmit mean power level - True value in dBm

<RXP> Number RX power – Value is represented in ½ dBm units

<usedSCI> Number Slot cycle index that has been used

<namdSCI> Number Slot cycle index in NAM

<maxSCI> Number Slot cycle index of network

<PN> Number Active Pilot Set

<pilotEcIo[x]> Number Active pilot strength (Ec/Io) in dB

6.5 CDMA network parameters +NETPAR

6.5.1 Description This command lists the cellular network parameters for active, candidate and neighbor cell.


Set AT+NETPAR=<mode> +NETPAR: <channel>,<PN>,<SID>,<NID>,<slot cycle index>,<rssi>,<Ec/Io>,<Tx Power>,<Tc Adj>

OK

+NETPAR: 25,477,4145,7,2,-89,11,-189,0

OK

Test AT+NETPAR=? +NETPAR: <(List of supported modes)>

OK

+NETPAR: (0)

OK


<mode> Number 0: Active cell



of 149

<channel> Number An ASCII number between 0 and 2047 representing the channel number.

<PN> Number The PN sequence offset of the active pilot as ASCII (0 - 511).

<SID> Number 0-32767 Cellular System ID.

<NID> Number 0-65535 Cellular Network ID.

<slot cycle index> Number 0-7 index of Slot Cycle

<rssi> Number Signal strength in dBm

e.g: -52dbm etc.

<Ec/Io> Number Page Channel active pilot Ec/Io value.- Value is represented in (-1/2) dBm units.

e.g: the returned value 60 refers to -30dBm.

<Tx Power> Number Mobile terminating transmit mean power level - True value in dBm.

e.g: -52dbm etc.

<Tx Adj> Number Tx gain adjustment value - Value is represented in 1/2 dBm units

e.g: the returned value 60 refers to 30dBm.

6.6 To display protocol revision in use $QCPREV

6.6.1 Description This command displays the protocol reversion in use.


Read AT$QCPREV? <Rev>

OK

6

OK


<rev> Number 1: JSTD008 3: IS_95A 4: IS_95B 6: IS_2000

6.7 Um Packet Data Inactivity Timer +CTA

6.7.1 Description This command is used to Read the Um packet data inactivity timer.


Read AT+CTA? <timer>

OK

+CTA: 30

OK


<timer> Number 0: Traffic channel not released during inactivity periods. 20-255: Release the Traffic Channel after <timer> 1-second intervals have elapsed since last sending or receiving RLP data frames on the Um interface. (default 30)



of 149

6.8 System information +CSS

6.8.1 Description This command is used to display the serving system band and the SID in the format.


Read AT+CSS +CSS: <band class>,<Band>,<SID>

OK

+CSS: P,PA,4145

OK


<band class> string C – the MS is registered with a cellular system. P – the MS is registered with a PCS system.

<Band> string CA – MS is registered with cellular A-band system CB – MS is registered with cellular B-band system PA – MS is registered with PCS A-band system PB – MS is registered with PCS B-band system PC – MS is registered with PCS C-band system PD – MS is registered with PCS D-band system PE – MS is registered with PCS E-band system PF – MS is registered with PCS F-band system Z – MS is not registered


6.9 Query Analog or Digital Service +CAD

6.9.1 Description This command queries the Analog or Digital Service. (read-only)


Read AT+CAD <service>

OK

1

OK


<service> Number 0: if no service is available 1: if CDMA Digital service available (default) 3: if Analog service is available


UBX-13000621 - R10 Production Information 1XRTT Data commands

of 149

7 1XRTT Data commands

7.1 Mobile Station IP Address +CMIP

7.1.1 Description This command is used to display the mobile station's temporary IP address. The value displayed is in standard IP address format.


Read AT+CMIP? +CMIP: xxx.xxx.xxx.xxx

OK

7.2 Base Station IP Address +CBIP

7.2.1 Description This command is used to display the base station's temporary IP address. The value displayed is in standard IP address format.


Read AT+CBIP? +CBIP: xxx.xxx.xxx.xxx

OK

7.3 Request overall capabilities +GCAP

7.3.1 Description This command indicates the major capability areas of the FW75 and LISA-C200. The support of different areas is presented in the response of the +GCAP command. Each area may be presented by the selection command name of a specific capability area.


Read AT+GCAP +GCAP:

<list of supported features>

OK

+GCAP: +CIS707-A, +MS, +ES, +DS, +FCLASS

OK

Test AT+GCAP=? OK

7.4 Enable/disable Mobile IP functionality $QCMIP

7.4.1 Description This command enables/disables Mobile IP functionality in the module.


Set AT$QCMIP=<n> OK

Or

+CME ERROR: <err>

AT$QCMIP=2

OK



of 149


Read AT$QCMIP? $QCMIP: <n>

OK

or

+CME ERROR: <err>

AT$QCMIP: 2

OK

Test AT$QCMIP=? $QCMIP: (list of supported <n>s)

OK

$QCMIP: (0-2)


<n> number 0: Simple IP only. 1: Mobile IP preferred (default value for Verizon). 2 -Mobile IP only (default value for Sprint).

7.5 Set the active Mobile Profile ID $QCMIPP

7.5.1 Description This command sets the active Mobile Profile ID value.


Set AT$QCMIPP=<n> OK

Or

+CME ERROR: <err>

$QCMIPP=1

OK

Read AT$QCMIPP? $QCMIPP: <n>

OK

or

+CME ERROR: <err>

$QCMIPP: 1

OK

Test AT$QCMIPP=? $QCMIPP: (list of supported <n>s)

OK

$QCMIPP: (0-5)

OK


<n> number 0-5 – Mobile profile ID.

7.6 Enable/disable the RFC2002bis Authentication $QCMIPT

7.6.1 Description This command enables/disables the RFC2002bis authentication value.


Set AT$QCMIPT=<n> OK

Or

+CME ERROR: <err>

AT$QCMIPT=0

OK



of 149


Read AT$QCMIPT? $QCMIPT: <n>

OK

or

+CME ERROR: <err>

$QCMIPT: 0

OK

Test AT$QCMIPT=? $QCMIPT: (list of supported <n>s)

OK

$QCMIPT: (0-1)

OK


<n> number 0: disable RFC2002bis. RFC2002 style authentication is used instead. 1: enable RFC20002bis

7.7 Enable/disable the active profile $QCMIPEP

7.7.1 Description This command enables/disables the current active profile.


Set AT$QCMIPEP=<mode> OK

Or

+CME ERROR: <err>

AT$QCMIPEP=1

OK

Read AT$QCMIPEP? $QCMIPEP: <mode>

OK

or

+CME ERROR: <err>

$QCMIPEP: 1

OK

Test AT$QCMIPEP=? $QCMIPEP: (list of supported mode)

OK

$QCMIPEP: (0-1)

OK


<mode> number 0: disable the current active profile. 1: enable the current active profile

7.8 Display information to Specific Profile $QCMIPGETP

7.8.1 Description

This command returns the information of a specific profile.


Test AT$QCMIPGETP=? $QCMIPGETP: (list of supported index)

OK

$QCMIPGETP: (0-5)

OK



of 149


Read AT$QCMIPGETP=<index> <information>

OK

Profile:1 Enabled

NAI:[email protected]

Home Addr:0.0.0.0

Primary HA:255.255.255.255

Secondary HA:68.28.89.76

MN-AAA SPI:1234

MN-HA SPI:1234

Rev Tun:1

MN-AAA SS:Set

MN-HA SS:Set

OK


<index> number 0 - 5

7.9 Set NAI for active profile $QCMIPNAI

7.9.1 Description This command set the NAI for the current active profile.


Set AT$QCMIPNAI=<nai>,<y> OK

Or

+CME ERROR: <err>

[email protected],1

OK

Read AT$QCMIPNAI? <nai>,<y>

OK

or

+CME ERROR: <err>

[email protected],1

OK

Test AT$QCMIPNAI=? $QCMIPNAI: (List of supported y)

OK

$QCMIPNAI: (0-1)

OK


<nai> string Network access identifier string.

<y> number 0: do not save to NVM 1: save to NVM

7.10 Set the reverse tunneling on currently active profile $QCMIPRT

7.10.1 Description This command sets the reverse tunneling on currently active profile.



of 149


Set AT$QCMIPRT=<x>,<y> OK

Or

+CME ERROR: <err>

AT$QCMIPRT=1,1

OK

Read AT$QCMIPRT? $QCMIPRT: <x>,<y>

OK

or

+CME ERROR: <err>

$QCMIPRT: 1,1

OK

Test AT$QCMIPRT=? $QCMIPRT: (List of supported x) ,(List of supported y)

OK

$QCMIPRT: (0-1),(0-1)

OK


<x> number 0: Reverse tunneling OFF 1: Reverse tunneling ON


7.11 Set MN-AAA Shared Secrets $QCMIPMASS

7.11.1 Description This command sets the MN-AAA shared secret for the currently active profile in string format.


Set AT$QCMIPMASS=<string>,<y> OK

Or

+CME ERROR: <err>

AT$QCMIPMASS= secret,1

OK

Read AT$QCMIPMASS? $QCMIPMASS: <s>

OK

or

+CME ERROR: <err>

$QCMIPMASS: Set

OK

Test AT$QCMIPMASS=? $QCMIPMASS: (List of supported <y>)

OK

$QCMIPMASS: (0-1)

OK


<string> String value without quotes Share secret string.


<s> string Set or Unset



of 149

7.12 Set MN-AAA Shared Secrets in HEX format $QCMIPMASSX

7.12.1 Description This command sets the MN-AAA shared secret for the currently active profile in hex format.


Set AT$QCMIPMASSX=<hex>,<y> OK

Or

+CME ERROR: <err>

AT$QCMIPMASSX= 12ef8,1

OK

Read AT$QCMIPMASSX? $QCMIPMASSX: <s>

OK

or

+CME ERROR: <err>

$QCMIPMASSX: Set

OK

Test AT$QCMIPMASSX=? $QCMIPMASSX: (List of supported ,hex>), (List of supported <y>)

OK

$QCMIPMASSX: (0-FFFFFFFF),(0-1)

OK


<hex> hex Hex Mobile Node AAA shared secret of up to 16 bytes



7.13 Set MN-HA Shared Secrets $QCMIPMHSS

7.13.1 Description This command sets the MN-HA shared secret for the currently active profile in string format.


Set AT$QCMIPMHSS=<string>,<y> OK

Or

+CME ERROR: <err>

AT$QCMIPMHSS= secret,1

OK

Read AT$QCMIPMHSS? $QCMIPMHSS: <s>

OK

or

+CME ERROR: <err>

$QCMIPMHSS: Set

OK

Test AT$QCMIPMHSS=? $QCMIPMHSS: (List of supported <y>)

OK

$QCMIPMHSS: (0-1)

OK


<string> String value without quotes

Share secret string..



of 149



7.14 Set MN-HA Shared Secrets in Hex format $QCMIPMHSSX

7.14.1 Description This command sets the MN-HA (Home Agent) shared secret for the currently active profile in hex format.


Set AT$QCMIPMHSSX=<hex>,<y> OK

Or

+CME ERROR: <err>

AT$QCMIPMASS= 12ef8,1

OK

Read AT$QCMIPMHSSX? $QCMIPMHSSX: <s>

OK

or

+CME ERROR: <err>

$QCMIPMHSSX: Set

OK

Test AT$QCMIPMHSSX=? $QCMIPMHSSX: (List of supported <hex>), (List of supported <y>)

OK

$QCMIPMHSSX: (0-FFFFFFFF),(0-1)

OK


<hex> hex Hex Mobile Node HA (Home Agent) shared secret of up to 16 bytes



7.15 Set MN-HA SPI Shared Secrets $QCMIPMHSPI

7.15.1 Description This command sets the MN-HA (Home Agent) SPIs for the currently active profile.


Set AT$QCMIPMHSPI=<spi>,<y> OK

Or

+CME ERROR: <err>

at$qcmipmhspi=1234,1

OK

Read AT$QCMIPMHSPI? $QCMIPMHSPI: <spi>,<y>

OK

or

+CME ERROR: <err>

$QCMIPMHSPI: 1234,1

OK

Test AT$QCMIPMHSPI=? $QCMIPMHSPI: (List of supported <spi>), (List of supported <y>)

OK

$QCMIPMHSPI: (0-4294967295),(0-1)

OK



of 149


<spi> number (0-4294967295) - Spi value.


7.16 Set MN-AAA SPI Shared Secrets $QCMIPMASPI

7.16.1 Description This command sets the MN-AAA SPIs for the currently active profile.


Set AT$QCMIPMASPI=<spi>,<y> OK

Or

+CME ERROR: <err>

AT$QCMIPMASPI=1234,1

OK

Read AT$QCMIPMASPI? $QCMIPMASPI: <spi>,<y>

OK

or

+CME ERROR: <err>

$QCMIPMASPI: 1234,1

OK

Test AT$QCMIPMASPI=? $QCMIPMASPI: (List of supported <spi>), (List of supported <y>)

OK

$QCMIPMASPI: (0-4294967295),(0-1)

OK


<spi> number (0-4294967295) - Spi value.


7.17 MIP Indicator +CMIPIND

7.17.1 Description Enables or disables sending of URC notification of a change in the MIP/PPP link.


Set AT+CMIPIND=<mode> OK AT+CMIPIND=1

OK

Read AT+CMIPIND? +CMIPIND : <mode>

OK

+CMIPIND:1

OK

URC +CMIPIND: <mip_status> +CMIPIND:1


<mode> Number Enables or disables the notification



of 149


0: Module disables notification of MIP/PPP status change 1: Module enables notification of MIP/PPP status change

<mip_status> Number State of MIP/PPP link

0: MIP/PPP link has come down 1: MIP/PPP link has gone up

IP address may be queried thru use of AT+CMIP command.

MIP status notification is only provided for data activity directly requested by client. Any MIP activity triggered indirectly (e.g. download of ephemeris data to support GPS functionality) shall not trigger a notification.


UBX-13000621 - R10 Production Information Short Messages Service commands

of 149

8 Short Messages Service commands

8.1 Show text mode parameters +CSDH

8.1.1 Description This command controls whether detailed header information is shown in text mode result codes.


Set AT+CSDH=[<show>] OK AT+CSDH=1

OK

Read AT+CSDH? +CSDH: <show>

OK

+CSDH: 0

OK

Test AT+CSDH=? +CSDH: (list of supported <show>s)

OK

+CSDH: (0-1)

OK


<show> Number 0: do not show detailed header information in text mode result codes 1: show detailed header information in text mode result codes

8.2 New message indication +CNMI

8.2.1 Description This command enables the unsolicited notification to the DTE when a SMS is received by the MT. The set command controls how messages are routed when received from the network.


Set AT+CNMI=[<mode>[,<mt>[,<bm>]]] OK AT+CNMI=1,1

OK

Read AT+CNMI? +CNMI= <mode>,<mt>,<bm>

OK

+CNMI: 0,0,0

OK

Test AT+CNMI=? +CNMI: (list of supported <mode>s),(list of supported <mt>s),(list of supported <bm>s)

OK

+CNMI: (0-2),(0-3),(0-1)

OK

URC +CMTI: <mem>,<index>


<mode> number SMS notification mode(currently supported mode = 1) 0: Buffer unsolicited result codes. 1: Forward result codes to TE. 2: Buffer result codes if TE is busy, then send when not busy.



of 149


Notification: Unsolicited result codes will be stored in RAM; The result codes may get lost when the module is powered off before MT was sending.

<mt> number Controls the storing of received messages. 0: No SMS-DELIVER indications are routed to TE. 1: SMS-DELIVER is stored in ME and indication of memory Location is sent to TE - +CMT: <mem>, <index> 2: SMS-DELIVERS are routed directly to the TE using an unsolicited result code, except class 2 messages.

3: Class 3 SMS-DELIVERs are routed directly to the TE.

Messages of other classes are handled as in <mt> = 1.

<bm> number Currently not supported

<mem> String Message memory spec: “ME” Message storage

<index> Number Location of new message

8.3 List message +CMGL

8.3.1 Description This command returns SMS messages with status value <stat> from message storage <mem1> to the DTE. Some parameters are displayed only when setting +CSDH=1.


Set AT+CMGL[=<stat>] Command successful and SMS-DELIVERs:

+CMGL: <index>,<stat>,<oa>,[<alpha>],[<scts>][,<tooa>,<length>]

<data>

[+CMGL: <index>,<stat>,<oa>,[<alpha>],[<scts>][,<tooa>,<length>]<data>[...]]

OK

AT+CMGL=”ALL”

+CMGL: 0,"REC READ","9132017368","12/06/04,14:30:40+00",,129,5

Hi 1

OK

Command successful and SMS-SUBMITs:

+CMGL: <index>,<stat>,<da>,[<alpha>],[<toda>, <length>]

<data>

[+CMGL: <index>,<stat>,<da>,[<alpha>],[<toda>, <length>]<data>[...]]

OK

Test

AT+CMGL=? +CMGL: (list of supported <stat>s)

OK

+CMGL: ("REC UNREAD","REC READ","STO UNSENT","STO SENT","ALL")

OK


<stat> Number or String String type in text mode (default value: “REC UNREAD”); indicates the status of message in memory

“REC UNREAD” in text mode: received unread SMS messages “REC READ” in text mode: received read SMS messages “STO UNSENT” in text mode: stored unsent SMS messages



of 149


“STO SENT” in text mode: stored sent SMS messages “ALL” in text mode: all SMS messages

<index> Number Storage position

<oa> String Originator address

<alpha> String Alphanumeric representation of <da> or <a> corresponding to the entry found in the phonebook.

<scts> String Service center time stamp in time-string format; refer to <dt>

<tooa> Number Type of address of <oa> - octet

<length> Number Number of characters

<data> String This is the TP-User-Data in text mode.

<da> String Destination address

<toda> Number Type of address of <da> - octet

<fo> Number First octet of TS 23.040 SMS-DELIVER, SMS-SUBMIT (default 17), SMS-STATUS-REPORT, or SMS-COMMAND (default 2)

<mr> Number Message reference

<ra> String Recipient address field

<tora> Number Type of address of <ra> - octet

<dt> String Discharge time in format “yy/MM/dd,hh:mm:ss+zz”; the time zone is expressed in steps of 15 minutes

<st> Number Status of an SMS STATUS-REPORT

<ct> Number TP-Command-Type (default 0)

<sn> Number CBM serial number

<mid> Number CBM message identifier

<dcs> Number SMS Data Coding Scheme (default 0), or Cell Broadcast Data Coding Scheme

MO messages using +CMGW and +CMGS don’t have a timestamp. The <dt> parameter in such cases will be “00/00/00,00:00:00+00”.

If the network provider uses Local time zone, then <dt> parameter’s “zz” value will always be “+00”

Only Teleservice IDs 4096-4098 are supported.

8.4 Read message +CMGR

8.4.1 Description This command returns the message from message storage <mem1> to the DTE. Some parameters are displayed only when setting +CSDH=1. If status of the received message is “received unread”, then status in the storage changes to “received read”.


Set AT+CMGR=<index> Command successful and SMS-DELIVERs:

+CMGR: <stat>,<oa>,[<alpha>],[<scts>][,<tooa>,<length>]

<data>

[+CMGL: <index>,<stat>,<oa>,[<alpha>],[<scts>][,<tooa>,<length>]<data>[...]]

OK

AT+CMGR=0

+CMGR: "REC READ","9132017368","12/06/04,14:30:40+00",,129,5

Hi 1

OK



of 149


Command successful and SMS-SUBMITs:

+CMGR: <stat>,<da>,[<alpha>],[<toda>, <length>]

<data>

[+CMGL: <index>,<stat>,<da>,[<alpha>],[<toda>, <length>]<data>[...]]

OK

Test

AT+CMGR=? OK AT+CMGR=?

OK



<oa> String Originator address

<alpha> String Alphanumeric representation of <da> or <a> corresponding to the entry found in the phonebook.

<scts> String Service center time stamp in time-string format; refer to <dt>

<tooa> Number Type of address of <oa> - octet

<length> Number number of characters

<data> String This is the TP-User-Data in text mode.



<fo> Number First octet of TS 23.040 SMS-DELIVER, SMS-SUBMIT (default 17), SMS-STATUS-REPORT, or SMS-COMMAND (default 2)


<ra> String Recipient address field

<tora> Number Type of address of <ra> - octet

<dt> String Discharge time in format “yy/MM/dd,hh:mm:ss+zz”; the time zone is expressed in steps of 15 minutes

<st> Number Status of an SMS STATUS-REPORT

<ct> Number TP-Command-Type (default 0)

<sn> Number CBM serial number

<mid> Number CBM message identifier

<dcs> Number SMS Data Coding Scheme (default 0), or Cell Broadcast Data Coding Scheme

MO messages using +CMGW and +CMGS don’t have a timestamp. The <dt> parameter in such cases will be “00/00/00,00:00:00+00”.



of 149

8.5 Send message +CMGS

8.5.1 Description This command sends a message from a DTE to the network (SMS-SUBMIT). Message reference value <mr> is returned to the DTE on successful message delivery.

LISA-C200 module uses the Short Message Peer-to-Peer (SMPP) protocol for sending an SMS.

Send SMS message length is limited to 160 characters.


Set AT+CMGS=<da>[,<toda>]<CR>

<text><ctrl-Z/ESC>

>

+CMGS: <mr>

OK

AT+CMGS=”0171112233”<CR>

>“This is the text”<Ctrl-Z>

+CMGS:2

OK

Test AT+CMGS=? OK

Entered text is preceded by a ‘>’ (greater-than) character, and this shows that the interface is in “text enter” mode. The DCD signal shall be in ON state while text is entered.

When ESC is used instead of ctrl-Z, the message is not sent and the module will not generate any URC.. ESC is only used if we want to escape from “text enter“ mode.




<text> String SMS String


<length> Number Number of characters

8.6 Set text mode parameters +CSMP

8.6.1 Description This command selects values for additional parameters needed when SMS is sent to the network or placed in storage when text format message mode is selected.


Set AT+CSMP=<teleservice id>,<vpf>,<vp> OK AT+CSMP=4098,0,"12/06/07,17:30:00"

OK

Read AT+CSMP? +CSMP:=<teleservice id>,<vpf>,<vp>

OK

+CSMP: 4098,0,"12/06/07,17:30:00"

OK

Test AT+CSMP=? OK



of 149


<teleservice id> Number Recognized values are [4097-4099]

Default: 4098

<vpf> Number Validity Period format

0: Validity Period – Absolute (string in next param)

1: Validity Period – Relative (number in next param)

<vp> Number or quoted string

Absolute format: “yy/MM/dd,hh:mm:ss”

Relative format: [0..248]

Reference: TIA/EIA-637-B, section 4, Section 4.5.5 and Table 4.5.6-1, p.4-32

8.7 Delete SMS +CMGD

8.7.1 Description This command deletes a message from preferred message storage <mem1>, if <flag> = 0 or not present, in location <index>. Otherwise the messages are deleted following the rules specified by <flag>.

When deleting a message from an empty location, the modem returns "OK".

If the <index> value is out of range or it refers to an empty position, then the error “+CMS ERROR: invalid memory index” is returned.


Set AT+CMGD=<index>[,<flag>] OK AT+CMGD=3

OK

Test AT+CMGD=? +CMGD: (list of supported <index>s), (list of supported <flag>s)

OK

+CMGD: (0-99),(0-4)

OK



<flag> Number Deletion flag. If present and different from 0 <index> is ignored:

0: Default. Delete the message specified in <index>

1: Delete all read messages from preferred message storage, leaving unread messages and stored mobile originated messages (whether sent or not) untouched

2: Delete all read messages from preferred message storage and sent mobile originated messages, leaving unread messages and unsent mobile originated messages untouched

3: Delete all read messages from preferred message storage, sent and unsent mobile originated messages leaving unread messages untouched.

4: Delete all messages from preferred message storage including unread messages.



of 149

8.8 Unsolicited Response (new SMS-DELIVER receipt indication) +CMTI

8.8.1 Description The +CMTI unsolicited response is sent to the TE upon receipt of a new SMS_DELIVER SMS, if the +CNMI parameter <mt> is set to 1. This unsolicited message indicates that a new SMS-DELIVER message was received, and is stored in location <index>. +CMTI: <mem>,<index>


URC +CMTI: <mem>,<index> AT+CMTI: “ME”,1


<mem> String Message memory spec: “ME” Message storage

<index> Number Location of new message

8.9 Write Message to Memory +CMGW

8.9.1 Description This command is used to write and save a message to <mem2>. The message is saved in memory, and the message index is displayed to the user. By default, messages are saved with the status of "STO UNSENT", but status "STO SENT" can be applied using the <stat> parameter. Type Syntax Response Example

Set AT+CMGW=<da> OK AT+CMGW=”8584441111” ”<CR>

>“This is the text”<Ctrl-Z>

+CMGW:2

OK


<da> Number Destination address in quoted string. This field contains a single phone number.

8.10 Send Message from Storage +CMSS

8.10.1 Description This command sends a pre-stored message, written previously using the +CMGW command. If these parameters are given, the message is sent accordingly. Otherwise the message is sent according to +CMGW setting. If no DA is found, an error occurs.

Send SMS message length is limited to 160 characters.


Set AT+CMSS=<index>[,<da>] +CMSS: <mr>

OK

AT+CMSS=3

+CMSS: 1

OK



of 149


<index> Number Location of the message

<da> Number Destination address in quoted string. This field contains a single phone number.



UBX-13000621 - R10 Production Information Supplementary services commands

of 149

9 Supplementary services commands

9.1 Calling line identification presentation +CLIP

9.1.1 Description This command controls the calling line identification presentation. When CLI (Calling Line Identification) is enabled, +CLIP response is returned after every RING result code. The URC is displayed after RING if the CLI presentation at the TE is enabled.


Set AT+CLIP=[<n>] OK AT+CLIP=1

OK

Read AT+CLIP? +CLIP: <n>, <m>

OK

+CLIP: 0,1

OK

Test AT+CLIP=? +CLIP: (list of supported <n>s)

OK

+CLIP: (0-1)

OK

URC +CLIP: <number>,<number_type> +CLIP: "9132017368",2


<n> Number Optional parameter sets/shows the result code presentation in the TA

0: disable (default value) 1: enable

<m> Number It tells whether CLIP is supported by the network

0: Not supported by the service provider

1: Supported by the service provider (Always 1 for Sprint and Verizon)

<number> String Phone number of calling address

<number_type> Number List of possible values for Number type, in CDMA network: 0: Unknown 1: International # 2: National # 3: Network Specific 4: Subscriber # 5: Reserved 6: Abbreviated # 7: Reserved for extension

CLIP URC is not available on the 1st RING, it will appear after the 2nd RING.


UBX-13000621 - R10 Production Information Sprint OMA-DM provisioning commands

of 149

10 Sprint OMA-DM provisioning commands

10.1 Enable/ Disable OMA-DM capabilities +OMADM

10.1.1 Description This command enables and disables OMA-DM capabilities.


Read AT+OMADM=? <status>

OK

DM session Disabled

OK

Set AT+OMADM =<mode> OK

If failed:

+CME ERROR:<err>

AT+OMADM=1

OK


<status> String Tells whether OMADM is enabled or disabled. • DM session is Disabled • DM session is Enabled

<mode> number 0: disable OMA-DM capabilities 1: enable OMA-DM capabilities (default) 2: launch a client initiated OMA-DM session Notes:

• The module must ignore network initiated OMA-DM WAP Push messages when OMA-DM is disabled.

• If the user attempts a client initiated OMA-DM session when OMA-DM is disabled, the module MUST perform a client initiated OMA-DM session but will not enable OMA-DM capabilities.

10.2 Enable/ Disable PRL provisioning +PRL

10.2.1 Description This command enables and disables PRL provisioning updates.


Read AT+PRL=? <status> (will return the current PRL update setting)

OK

PRL update disabled

Set AT+PRL =<mode> OK

If failed:

+CME ERROR:<err>

AT+PRL=2

OK


<status> String Tells whether PRL update capability is enabled or disabled • PRL update disabled • PRL update enabled • PRL update Auto 45 days • PRL update Auto 90 days



of 149


<mode> number 0: disable PRL update capabilities Notes:

• The module must ignore all network initiated PRL updates when PRL update is disabled.

• If the user attempts a client initiated PRL update when PRL update is disabled, the module must perform a client initiated PRL update but will not enable PRL updates.

1: enable PRL update capabilities (default) 2: perform a client initiated PRL update Notes:

• If PRL update is currently disabled, this AT command will launch a client initiated PRL update but will not enable PRL update capabilities

3: will set the device to check for PRL updates every 45 days. 4: will set the device to check for PRL updates every 90 days. Notes:

• Module will enable PRL update capabilities when it is set to automatically check for updates.

10.3 Enable/ Disable FUMO provisioning +FUMO

10.3.1 Description This command enables and disables FUMO capabilities.


Read AT+FUMO=? <status> (will return the current OMA-DM setting)

OK

FUMO session Enabled

OK

Set AT+FUMO=<mode> OK

If failed:

+CME ERROR:<err>

AT+FUMO=1

OK


<status> String Tells whether FUMO capability is enabled or disabled • FUMO session Disabled • FUMO session Enabled

<mode> number 0: disable FUMO capabilities 1: enable FUMO capabilities (default) 2: perform a client initiated FUMO session Notes:

• The module must ignore all network initiated FUMO messages when FUMO is disabled.

• If the user attempts a client initiated FUMO session when FUMO is disabled, the module will not perform a client initiated FUMO session.

10.4 HFA Session Enable/Disable +UOMAHFA

10.4.1 Description: This command enables/disables Hands Free Activation




of 149


Read AT+UOMAHFA=? +UOMAHFA:<list of available modes>

OK

+UOMAHFA:(0-1)

OK

Set AT+UOMAHFA=<n> +UOMAHFA:<mode>

OK

AT+UOMAHFA=1

OK


<mode> number 0: disables HFA 1: enables HFA (default)

By default, AT+UOMAHFA command is set to 1; to cancel any future HFA session, then the command should be set to 0 (the current cycle of HFA will continue).

10.5 Session Cancel +UOMADM

10.5.1 Description: This command stops any current OMADM session, DC, FUMO, PRL


Set AT+UOMADM=0 OK

If failed:

+CME ERROR:<err>

AT+UOMADM=0

OK

The +UOMADM command with parameter 0 should be used to cancel an OMA session. This command is intended for OEM factory use only. Sending the $RTN command will enable HFA. There is no URC associated with this command

10.6 Enable / Disable OMADM/FUMO unsolicited status messages +UOMASTAT

10.6.1 Description: To enable/disable OMADM/FUMO unsolicited status messages.


Set AT+UOMASTAT=<n> OK AT+UOMASTAT=1

OK

URC +UOMASTAT:<SessionType>,<State>,<Error>

+UOMASTAT:1,0,0


<n> number 0: disables status messages 1: enables status messages

<SessionType> number 1: DM Session 2: Download Session

<State> number 0: Session started 1: Session completed successfully 2: Session aborted



of 149

<Error> number 0: No Error other: Error code

10.7 Roaming status $ROAM

10.7.1 Description: This command sets the module roaming status.


Read AT$ROAM=? <mode> (will return the current roaming setting)

OK

1

OK

Set AT$ROAM =<mode> OK

If failed:

+CME ERROR:<err>

AT$ROAM=1

OK


<mode> number 0: set the module to Sprint only mode 1: set the module to automatic mode (default)

10.8 Device reset command $RTN

10.8.1 Description: This command sets the module to factory defaults and power cycles the device if the current MSL is entered.


Set AT$RTN =XXXXXX OK

If failed:

+CME ERROR:<err>

AT$RTN=000000

OK


<XXXXXX> number “XXXXXX” is a 6-digit device MSL.

Note: After the correct MSL is entered, the device will set all NAM and Mobile IP values to factory defaults and then power cycle.

10.9 Device power cycle command $RESET

10.9.1 Description: This command immediately initiates a device reset.




of 149


Set AT$RESET OK

If failed:

+CME ERROR:<err>

AT$RESET

OK

10.10 Check data service command +SERVICE

10.10.1 Description: This command returns the integer index of data service.


Read AT+SERVICE? +SERVICE: <service>

OK

or

+CME ERROR:<err>

+SERVICE: 1

OK


<service> number 0: NO Service

1: 1xRTT Service

2: EVDO Service

3: EVDO Rev A

4: GPRS

10.11 Set IMSI Data +UIMSIDATA

10.11.1 Description

This command reads or writes the following IMSI data to the device NVM: IMSI_M_CLASS, IMSI_M_ADDR_NUM, MCC_M and IMSI_M_11_12.


Set AT+UIMSIDATA=< IMSI_M_CLASS>, <IMSI_M_ADDR_NUM>,<MCC_M>,<IMSI_M_11_12>

OK AT+UIMSIDATA=0,255,209,99

OK

Read AT+UIMSIDATA? +UIMSIDATA: < IMSI_M_CLASS>, <IMSI_M_ADDR_NUM>,<MCC_M>,< IMSI_M_11_12>

OK

+UIMSIDATA: 0,255,209,99

OK

Test AT+UIMSIDATA=? +UIMSIDATA: <IMSI_M_CLASS>,<IMSI_M_ADDR_NUM>,<MCC_M>,<IMSI_M_11_12>

OK

+UIMSIDATA: <IMSI_M_CLASS>,<IMSI_M_ADDR_NUM>,<MCC_M>,<IMSI_M_11_12>

OK



of 149


<IMSI_M_CLASS> Number IMSI_M Class assignment of the mobile station

0: Class 0 1: Class 1

<IMSI_M_ADDR_NUM> Number Number of IMSI_M address digits

<MCC_M> Number Mobile Country Code of the MIN based IMSI

< IMSI_M_11_12> Number The 11th and 12th digits of IMSI_M

10.12 Set call termination enabled indicators +UMOBTERM

10.12.1 Description This command reads or writes the following call termination enabled indicators to the device NVM: MOB_TERM_HOME, MOB_TERM_FOR_SID, MOB_TERM_FOR_NID.


Set AT+UMOBTERM= <MOB_TERM_HOME>,<MOB_TERM_FOR_SID>,<MOB_TERM_FOR_NID>

OK AT+UMOBTERM=1,1,1

OK

Read AT+UMOBTERM? +UMOBTERM: <MOB_TERM_HOME>,<MOB_TERM_FOR_SID>,<MOB_TERM_FOR_NID>

OK

+UMOBTERM: 1,1,1

OK

Test AT+UMOBTERM=? +UMOBTERM: <MOB_TERM_HOME>,<MOB_TERM_FOR_SID>,<MOB_TERM_FOR_NID>

OK

+UMOBTERM: <MOB_TERM_HOME>,<MOB_TERM_FOR_SID>,<MOB_TERM_FOR_NID>

OK


<MOB_TERM_HOME> Number Home (non-roaming) registration enable indicator.

0: Disabled 1: Enabled

<MOB_TERM_FOR_SID> Number Foreign SID roaming registration enable indicator


<MOB_TERM_FOR_NID> Number Foreign NID roaming registration enable indicator


10.13 Set Home SID/NID pair +USIDNIDPR

10.13.1 Description This command reads or writes the Home SID/NID pair(s) to the device NVM.



of 149


Set AT+USIDNIDPR= <SID_NID_IDX>,<SID>,<NID>

OK AT+USIDNIDPR=0,4139,65535

OK

Read AT+USIDNIDPR? + USIDNIDPR:

<SID1>,<NID1>

….

<SID19>,<NID19>

OK

+USIDNIDPR:

4139,65535

0,0

0,0

0,0

0,0

0,0

0,0

0,0

0,0

0,0

0,0

0,0

0,0

0,0

0,0

0,0

0,0

0,0

0,0

0,0

OK

Test AT+USIDNIDPR=? +SIDNIDPR: <SID_NID_IDX>,<SID>,<NID>

OK

+SIDNIDPR: <SID_NID_IDX>,<SID>,<NID>

OK


<SID_NID_IDX> Number SID/NID pair index (0-19).

<SID> Number SID from Home (SID/NID) pair

<NID> Number NID from Home (SID/NID) pair

10.14 Write PRL file +UPRLWRITE

10.14.1 Description This command writes a PRL file to the device NVM.



of 149


Set AT+UPRLWRITE: <PRL file size> >

Start transfer of PRL file data

OK

AT+UPRLWRITE=4000

>these bytes are the PRL file data

OK


<PRL file size> Number PRL file size expressed in bytes

The stream of bytes can be entered after the “>” prompt has been provided to the user. The PRL file transfer is terminated exactly when <size> bytes have been entered and either OK or an error message is returned. The feed process cannot be interrupted, i.e. command mode is re-entered once the user has provided the declared number of bytes.


UBX-13000621 - R10 Production Information Verizon OTA Provisioning commands

of 149

11 Verizon OTA Provisioning commands

11.1 Initiate OTA Provisioning (+CDV=*22899)

11.1.1 Description This command is used to initiate the Verizon OTA provisioning.


Set AT+CDV=*22899 OK AT+CDV=*22899

OK

11.2 OTA Provisioning Activation Indicator (+UACTIND)

11.2.1 Description It is an unsolicited message that is sent out after a Verizon activation attempt. It is always ON and cannot be turned OFF.


Message +UACTIND:<result>

OK

+UACTIND: 0

OK


<result> Number Tells the result of the Verizon activation initiated by AT+CDV=*22899

0: Activation Success 1: Activation Fail


UBX-13000621 - R10 Production Information GPIO AT-commands

of 149

12 GPIO AT-commands

12.1 Introduction This section describes the AT commands used to manage the GPIO pins provided with u-blox CDMA cellular modules.

GPIO supported on LISA-C200 only.

12.2 LISA-C200 GPIO mapping <gpio_id> Pin name Pin number

20 GPIO1 20

21 GPIO2 21

23 GPIO3 23

24 GPIO4 24

51 GPIO5 51

Table 1: LISA-C200 GPIO mapping

12.3 GPIO select configuration command +UGPIOC

12.3.1 Description This command allows the user to configure GPIOs pins as input, output or tristate. When GPIOs pins are configured as output pin, it is possible to set the value. The test command provides the list of the supported GPIOs, the supported functions and the status of all GPIOs.

Not all GPIO functions can be assigned to each GPIO pin. If the configuration is not allowed, an error message will be returned (error code 1502 – “+CME ERROR: Select GPIO mode error”).


Set AT+UGPIOC=<gpio_id>,<gpio_mode>[,<gpio_out_val>]

OK AT+UGPIOC=21,0,1

OK

Read AT+UGPIOC? +UGPIOC:

<gpio_id>,<gpio_mode>

[<gpio_id>,<gpio_mode>

[….]]

OK

+UGPIOC:

20,255

21,1

23,0

24,255

51,0

OK

Test AT+UGPIOC=? +UGPIOC: (list of supported GPIOs pins),(list of supported <gpio_mode>), (list of supported <gpio_out_val>)

OK

+UGPIOC: (20,21,23,24,51),(0,1,3,4,5,6,255),(0-1)

OK



of 149


<gpio_id> Number GPIO pin identifier: pin number

Refer to Table 1 for GPIO pins and their mapping on LISA-C200.

<gpio_mode> Number Mode identifier: configured function

Possible values:

0: output 1: input

3: output, pin 21, GPS_SUPPLY_ENABLE

4: input , pin 23, GPS_DATA_READY

5: output, pin 24, GPS_RTC_SHARING

6: network status indication. Where 1) "No Service" - Indicates No Network coverage or Not Registered (but there can be coverage in limited service) Continuous Output/Low. 2) "Registered Home Network CDMA" - Indicates registered with home CDMA network (full or limited service). Cyclic Output/High for 100ms, Output/Low for 2sec. 3) "Registered Roaming CDMA" - Indicates registered with visitor CDMA network (roaming, full or limited service). Cyclic Output/High for 100ms, Output/Low for 100ms, Output/High for 100ms, Output/Low for 2sec. 4) "Transmission" - Indicates ongoing voice or data call. Continuous Output/High

255: Tristate, with active pull down.

<gpio_out_val> Number GPIO output value (for output function <gpio_mode>=0, 3 or 5 only):

0: low (default) 1: high

12.4 GPIO read command +UGPIOR

12.4.1 Description This command reads the current value of the specified GPIO, no matter whether it is configured as input or output (refer to +UGPIOC AT command to define the GPIO function). The syntax and the parameters range is shown in the response to the test command.


Set AT+UGPIOR=<gpio_id> +UGPIOR: <gpio_id>,<gpio_val>

OK

AT+UGPIOR=21

+UGPIOR: 21, 0

OK

Test AT+UGPIOR=? +UGPIOR: (list of supported <gpio_id>s)

OK

+UGPIOR: (20,21,23,24,51)

OK


<gpio_id> Number GPIO pin identifier: pin number.


<gpio_val> Number GPIO value (0-1)


The command works only if the parameter <gpio_mode> of the +UGPIOC AT command is set to 0 or 1.



of 149

12.5 GPIO set command +UGPIOW

12.5.1 Description This command sets (“writes”) the output of the specified GPIO, but only if it is configured in output function (refer to +UGPIOC AT command to set the pin as output).


Set AT+UGPIOW=<gpio_id>,<gpio_out_val> OK AT+UGPIOW=21,1

OK

Test AT+UGPIOW=? +UGPIOW: (list of supported <gpio_id>s),(list of supported <gpio_out_val>)

OK

+UGPIOW: (20,21,23,24,51),(0-1)

OK


<gpio_id> Number GPIO pin identifier: pin number.


<gpio_out_val> Number GPIO value (0-1)


The command works only if the parameter <gpio_mode> of the +UGPIOC AT command is set to 0.


UBX-13000621 - R10 Production Information Audio

of 149

13 Audio

13.1 Introduction The LISA-C200 supports analog audio and digital (PCM) audio. The commands in this section provide the user with a means to calibrate both analog and digital audio paths and to select the required paths.

The following Audio commands are currently supported.

• AT+UHFP: Hands Free Features, Echo cancellation, AGC etc

• AT+UMGC: Microphone Gain Control

• AT+USGC: Speaker Gain Control

• AT+USTN: Sidetone

• AT+UUBF: Uplink Filters

• AT+UDBF: Downlink Filters

• AT+USPM: Select the Audio path Analog or Digital.

• AT+UPCM: Configure the PCM interface

The settings are saved in NVM and so are maintained through power cycle.

The settings will not take effect until a power cycle.

All the parameters can be set to default values (see individual command description and defined values for details).

Audio is supported on LISA-C200 only.

Figure 1: LISA-C200 audio paths

13.2 Microphone Gain (Microphone Gain Control) +UMGC

13.2.1 Description This command is used to set the microphone gain of the current audio path.

PCM_Rx Downlink



of 149


Set AT+UMGC=<path>,<micLna>,<codecTxGain>,<txVolume>

OK AT+UMGC=0,1,8231,12345

OK

Read AT+UMGC? +UMGC:

Path <path>:

<micLna>,<codecTxGain>,<txVolume>

[…]

(for all the supported paths)

OK

+UMGC:

Path 0:

1, 8231, 12345

Path 2:

NA,NA,16384

OK

Test AT+UMGC=? +UMGC: (list of supported <paths>s,(list of supported <micLna >s),(list of supported <codecTxGain >s),(list of supported <txVolume>s)

OK

+UMGC: (0,2),(0-1,65535),(1- 64763),(1 - 65226)

OK


<path> Number Specifies the downlink path 0: handset_mic 2: PCM_Tx

<micLna> Number Specifies the gain of micLna 0: 0 dB 1: 24 dB (Default) 65535: resets selected paths parameters; micLNA , codecTxGain and txVolume back to default.

This control would typically be used during audio tuning. Only valid with path 0 and only 65535 is valid for Path 2 to reset Tx Volume ( ex: AT+UMGC=2,65535)

<codecTxGain> Number Gain of codexTx; Range: 1-64763) where 1 = -66dB and 64763 = +30dB (Gdb = 20*log(CodecTxGain/2048); default: 8153 (12dB) This control would typically be used to control Txgain/vol. Only valid with path 0.

<txVolume> Number Range: 1-65226 where 1 = -84db and 65226 = +12dB (Gdb = 20*log(tcVloume/16384); default: 16384 (0dB) This control would typically be used during audio tuning.

When setting the parameters for Path 2, leave the <micLna> and <codecTxGain> fields empty since only <txVolume> is available for Path 2. Eg:

AT+UMGC=2,,,12345

OK

13.3 Speaker Gain (Speaker Gain Control) +USGC

13.3.1 Description This command is used by the application to tune the receive gain of the speaker. If the modem is in the idle state, it will generate an audible tone at the selected volume.


Set AT+USGC=<path>,<rxVolume>,<codecRxGain>

OK AT+USGC=0,2,600

OK

Read AT+USGC? +USGC:

+USGC:

Path 0:



of 149


Path <path>:

<rxVolume>,<codecRxGain>

[…]


OK

2,600

Path 4:

4,NA

OK

Test AT+USGC=? +USGC: (list of supported <paths>s,(list of supported < rxVolume >s), (list of supported < codecRxGain >s)

OK

+USGC: (0,4),(0-7,65535),(1-64763)

OK


<path> Number Specifies the downlink path 0: Analog Earpiece 4: Digital RX

<rxVolume> Number Range: 0-7; (0 is mute, 1=-10dB to 7=8dB with 3dB/step); default: 3 (-4dB) Settings this to 65535 resets both params back to default on selected path.

<codecRxGain> Number Range: 1 - 64763 (-66dB to +30dB) where (Gdb = 20*log(codecRxGain/2048) ; default: 16384 (18dB). Note : Use this as main gain control. Only valid with path 0 and will be ignored for path4

13.4 Sidetone (SideTone) +USTN

13.4.1 Description This command is used to set the level of audio feedback in the speaker (microphone feedback in the speaker). Sidetone is a part of the user’s speech on uplink path that should be heard on downlink path by the user himself to have perception the call is on.


Set AT+USTN=<path>,<CodecSTGain> OK AT+USTN=0,12

OK

Read AT+USTN? +USTN:

Path <path:

<CodecSTGain>

[…]


OK

+USTN:

Path 0:

12

OK

Test AT+USTN=? +USTN: (list of supported <path>s), list of supported <CodecSTGain>s)

OK

+USTN: (0),( 0-16384,65535)

OK


<path> Number Specifies the downlink path 0: Analog TX (microphone)



of 149


<CodecSTGain> Number Specified the Sidetone gain

Range: 0-16384 (-96 dB to 0 dB where GdB = 20*LOG(<CodecSTGain>/16384)-12dB) ; default: 8211(-18dB) Settings this to 65535 resets the param back to default.

13.5 Uplink Digital Filter +UUBF

13.5.1 Description This command changes the digital audio filter parameters for a specific Uplink path.


Set AT+UUBF=<path>,<filter_number>,<h0/h12>,<h1/h11>,<h2/h10>,<h3/h9>,<h4/h8>,<h5/h7>,<h6>

OK AT+UUBF=0,1,1265,2249,4377,32512,50480,29762,45104

OK

Read AT+UUBF? +UUBF:

Path <path >:

Filter1: h0/h12:<h0/h12>, h1/h11: <h1/h11>, h2/h10:<h2/h10>, h3/h9:<h3/h9>, h4/h8:<h4/h8>, h5/h7: <h5/h7>, h6:<h6>

[…]


OK

+UUBF:

Path 0:

Filter1: h0/h12:1265, h1/h11:2249, h2/h10:4377, h3/h9:32512, h4/h8:50480, h5/h7:29762, h6:45104

Path 2:

Filter1: h0/h12:65523, h1/h11:29, h2/h10:65465, h3/h9:363, h4/h8:64113, h5/h7:

3080, h6:12442

OK

Test AT+UUBF=? +UUBF: (list of supported <path >s),(list of supported <filter_number>s),(list of supported <h0/h12>s),(list of supported <h1/h11>s),(list of supported <h2/h10>s),(list of supported <h3/h9>s),(list of supported <h4/h8>s),(list of supported <h5/h7>s),(list of supported <h6>s)

OK

+UUBF: (0,2),(1,65535),(0-65535),(0-65535),(0-65535),(0-65535),(0-65535),(0-65535),(0-65535)

OK


<path> Number 0: handset mic 2: PCM_Tx

<filter_number> Number 1: There is only 1 Filter, so entering data set this to 1.

65535: Set to this value and it will reset selected paths parameters to default value.

<h0/h12>,<h1/h11>, <h2/h10>,<h3/h9>, <h4/h8>,<h5/h7>,<h6>

Number These parameters are the filter coefficient. Where <h0/h12> is filter coefficient for h0 and h12 taps and so on.

The range goes from 0 to 65535. Default values for <h0/h12>:65523 ,<h1/h11>:29 ,<h2/h10>:65465 , <h3/h9>:363 ,<h4/h8>:64113 ,<h5/h7>:3080 ,<h6>:12442

Output sequence y[n]=h0x[n]+h1x[n-1]+…+h12x[n-12]



of 149

13.6 Downlink Digital Filters +UDBF

13.6.1 Description This command changes the digital audio filters parameters for a specific downlink path.


Set AT+UDBF=<path>,<filter_number>,<h0/h12>,<h1/h11>,<h2/h10>,<h3/h9>,<h4/h8>,<h5/h7>,<h6>

OK AT+UDBF=0,1,1265,2249,4377,32512,50480,29762,45104

OK

Read AT+UDBF? +UDBF:

Path <path>:

Filter1: h0/h12:<h0/h12>, h1/h11:<h1/h11>, h2/h10:<h2/h10>, h3/h9:<h3/h9>, h4/h8:<h4/h8>, h5/h7:<h5/h7>, h6:<h6>

[…]


OK

+UDBF:

Path 0:


Path 4:


OK

Test AT+UDBF=? +UDBF: (list of supported <path >s),(list of supported <filter_number>s),(list of supported <h0/h12>s),(list of supported <h1/h11>s),(list of supported <h2/h10>s),(list of supported <h3/h9>s),(list of supported <h4/h8>s),(list of supported <h5/h7>s),(list of supported <h6>s)

OK

+UDBF: (0,4),(1,65535),(0-65535),(0-65535),(0-65535),(0-65535),(0-65535),(0-65535),(0-65535)

OK


<path> Number 0: Analog TX , mic 4: PCM_Rx

<filter_number> Number 1: There is only 1 Filter, so entering data set this to 1.

65535: Set to this value and it will reset selected paths parameters to default value.

<h0/h12>,<h1/h11>, <h2/h10>,<h3/h9>, <h4/h8>,<h5/h7>,<h6>

Number These parameters are the filter coefficient. Where <h0/h12> is filter coefficient for h0 and h12 taps and so on.

The range goes from 0 to 65535; default value for all 7 coefficients is 0. <h6>=0 disables the filter.

Output sequence y[n]=h0x[n]+h1x[n-1]+…+h12x[n-12]

13.7 Hands-Free Parameters +UHFP

13.7.1 Description This command changes the parameters that control the Hands-Free audio application for a specific uplink path. The Hands-Free application consists of four distinct operating parts:

• Echo Canceller (EC) • Noise Suppression (NS) • Automatic Gain Control (AGC) • Automatic Volume Control (AVC)



of 149


Set AT+UHFP=<path>,<algo_ctrl>[,<param_1>[,<param_2>,<param_3>,<param_4>[,<param_5>,<param_6>,<param_7>]]]

OK AT+UHFP=0,32

OK

Read AT+UHFP? +UHFP:

Path <path>:

EC=<n>, NS=<n>, AGC=<n>, AVC=<n> agc_param: <param_1>,<param_2>,<param_3>,<param_4> avc_param: <param_1> ec_param: <param_1>,<param_2>,<param_3>,<param_4>,<param_5>,<param_6>,<param_7>

[…]


OK

+UHFP:

Path 0:

EC=1, NS=1, AGC=1, AVC=1

agc_param: 0,65535,32613,0

avc_param: 61696

ec_param: 20,2048,2048,19000,6000,10361,450

Path 2:

EC=1, NS=1, AGC=1, AVC=1

agc_param: 0,65535,32613,0

avc_param: 61696

ec_param: 20,2048,2048,19000,6000,10349,512

OK

Test AT+UHFP=? +UHFP: (list of supported <path>s, list of supported <algo_ctrl>s,(list of supported <rx_agc_static_gain>,list of supported <rx_agc_aig>,list of supported <tx_agc_static_gain>,list of supported <tx_agc_aig>),(list of supported <rx_avc_sensitivity>),(list of supported <echo_path_delay>,list of supported <OutputGain>,list of supported <NLPP_gain>,list of supported <DENS_tail_alpha>,list of supported <DENS_tail_portion>,list of supported <DENS_limit_NS>,list of supported <DENS_NL_atten>)

OK

+UHFP: (0,2),(0-32768),(((8192-65071),(0,65535),(8192-65071),(0,65535)),((46336-65535,0-19200)),((0-959),(2048-32459),(2048-32459),(4000-29000),(1000-16000),(1-32768),(50-1024)))

OK


<path> Number 0: Analog TX_mic 2: PCM_Tx

<algo_ctrl> Number This parameter controls the activity and initialization of the EC, AGC,NS blocks • Bit #0: Initialize Echo Canceller(EC), EC parameters follow this

parameter 1. <param_1>: echo_path_delay - range: 0-959, default: 20



of 149


2. <param_2>: OutputGain - range: 2048 – 32459 (-66dB - 24dB), default: 2048 (0dB) (GdB=20*LOG(OutputGain/2048))

3. <param_3>: NLPP_gain – range: 2048 – 32459 (-66dB - 24dB), default: 2048 (0dB) (GdB=20*LOG(NLPP_gain/2048))

4. <param_4>: DENS_tail_alpha - range: 4000 - 29000, default: 19000

5. <param_5>: DENS_tail_portion - range: 1000 - 16000, default: 6000

6. <param_6>: DENS_limit_NS - range: 1 - 32768 (-90 - 0dB), default: 10361 (-1 0dB). Should not need to change this. (GdB=20*LOG(DENS_limit_NS/32768))

7. <param_7>: DENS_NL_atten - range: 50 - 1024, default: 450

• Bit #1: Not Used • Bit #2: Echo Canceller(EC); 0=OFF, 1=ON • Bit #3: Not Used • Bit #4: Not Used • Bit #5: Noise Suppression(NS); 0=OFF, 1=ON • Bit #6: Not Used • Bit #7: Initialize TX/RX AGC parameters, TX/RX AGC parameters

follow this parameter 1. <param_1>: rx_agc_static_gain - range: 8192 – 65071 (0

- 18dB), default: 8192 (0dB) (GdB=20*LOG(rx_agc_static_gain/8192))

2. <param_2>: rx_agc_aig - range: 0=static gain, 65535=adaptive gain, default: 65535

3. <param_3>: tx_agc_static_gain - range: 8192 – 65071 (0 - 18dB), default: 32613 (12dB) (GdB=20*LOG(tx_agc_static_gain/8192))

4. <param_4>: tx_agc_aig - range: 0=static gain, 65535=adaptive gain, default: 0

• Bit #8: AGC; 0=OFF, 1=ON • Bit #9: Initialize AVC parameters, AVC parameters follow this

parameter 1. <param_1>: rx_avc_sensitivity - range: 46336-65535, 0-

19200 (-75 - +75dB)(where 46336=-75dB, 65535=-1dB, 0=0dB, 19200=75dB), default: -3840 ( -15dB) (valdB= rx_avc_sensitivity/256)

• Bit #10: AVC; 0=OFF, 1=ON (AGC Bit8 must also be 1 ON for this to be turned ON)

• Bit #11: Not Used • Bit #12: Not Used • Bit #13: Not Used • Bit #14: Not Supported • Bit #15: Reset all to factory default. If this is set, then all other bits

should be 0. Note: Bits 2,5,8,10 can be set together as the provide ON/OFF Bits 0,7,9 cannot be set together. Example, if bit 0 is set then the modem expects Echo Canceller parameters to follow directly after this parameter. If more than one of these bits is set the command will be rejected completely.

13.7.2.1 Examples:

• Turn EC ON: +UHFP=0,4

• Turn NS ON: +UHFP=0,32

• Turn AGC ON: +UHFP=0,256

• Turn AVC ON: +UHFP=0, 1280

• Turn EC, NS, AGC, AVC ON: +UHFP=0,1316



of 149

• Turn EC, NS, AGC, AVC ON + EC parameters: +UHFP=0,1317,<echo_path_delay>,<OutputGain>,<NLPP_gain>,<DENS_tail_alpha>,<DENS_tail_portion>,<DENS_limit_NS>,<DENS_NL_atten>

• Turn ON EC, NS, AGC, AVC + AGC parameters: +UHFP=0,1444,<rx_agc_static_gain>,<rx_agc_aig>,<tx_agc_static_gain>,<tx_agc_aig>

• Turn ON EC, NS, AGC, AVC + AVC parameters: +UHFP=0,1828,<rx_avc_sensitivity>

• Toggle EC param set: +UHFP=0,16384

• Reset all settings to factory default: +UHFP=0,32768

13.8 Audio Path mode setting (Set Path Mode) +USPM

13.8.1 Description The path mode command is used to switch between Analog and Digital (PCM) audio paths for transmit and receive audio paths.


Set AT+USPM=<main_uplink>,<main_downlink>

OK AT+USPM= 0,0

OK

Read AT+USPM? +USPM: <main_uplink>,<main_downlink>

OK

+USPM: 0,0

OK

Test AT+USPM=? +USPM: (list of supported <main_uplink>s,(list of supported <main_downlink>s)

OK

+USPM: (0,2),(0,4)

OK


<main_uplink> Number Specifies the audio output path used for speech 0: Analog microphone 2: PCM_TX

<main_downlink> Number Specifies the audio input path used for speech 0: Analog earpiece 4: PCM_Rx

You can only select similar type of audio path for uplink and downlink. Eg, if analog microphone is selected as the uplink path then audio earpiece should be selected as the downlink path.

13.9 PCM Digital Interface Setup +UPCM

13.9.1 Description This command is used by the application to configure the PCM Digital Interface.


Set AT+UPCM=<pcm_codec_intfc>,<pcm_ctl>

OK AT+UPCM=2,2

OK



of 149


Read AT+UPCM? +UPCM: <pcm_codec_intfc>,<pcm_ctl>

OK

AT+UPCM?

+UPCM: 2,2

OK

Test AT+UPCM =? +UPCM: (list of supported <pcm_codec_intfc>s,(list of supported <pcm_ctl>s)

OK

AT+UPCM=?

+UPCM: (0-55,65535),(0-2)

OK


<pcm_codec_intfc> Number • Bit 0: 0 - Long sync is aligned to the rising edge of the PCM_CLK (Default). 1 - Long sync is launched 1/4 cycle ahead of the rising edge of PCM CLK.

• Bit 1: 0 - Short sync is aligned to the rising edge of the PCM_CLK (Default). 1 - Short sync is launched 1/4 cycle ahead of the rising edge of PCM CLK.

• Bit 2: 0 - PCM_SYNC is not inverted (Default).

1 - The polarity of PCM_SYNC driven out of MSM in master mode is inverted.

• Bits 3,4: 00 - MASTER (PRIM_PCM Short sync) (Default)

01 - MASTER (AUX_PCM long sync)

10 - SLAVE (PRIM_PCM Short sync)

Defines the PRIM_PCM/AUX_PCM master/slave mode selection. In master mode, the MSM provides the clock and sync (short/long) to the external Codec. In slave mode, the external codec drives the clock and sync signals to the MS

• Bit 5: 0 - disable the output clock REF_XOSC_OUT 1 - enable the output clock REF_XOSC_OUT

• 65535 – Setting this field to 65535 resets this parameter to default settings.

<pcm_ctl> Number 0: Alaw 1: uLaw 2: 16 Linear

LISA-C200 modules support a bi-directional 4-wire I2S digital audio interface. The modules act as “master” only.

FW75-C200 modules do not support this interface.

13.10 Play audio file +UPLAYFILE

13.10.1 Description Play the specified audio file stored into the file system. The audio signal from the player is only routed to the downlink path. For more details about file system description refer to Chapter 16.

The player is stopped and a URC (+UPLAYFILE: 0) is provided in the following cases:

• Incoming or outgoing call during file playing • Call hang-up during file playing



of 149


Set AT+UPLAYFILE=<filename> OK AT+UPLAYFILE="file1.amr"

OK

Read AT+UPLAYFILE? +UPLAYFILE: <playstatus> OK

+UPLAYFILE: 0 OK

URC +UPLAYFILE: 0


<filename> String String Specifies the audio resource file name to be played

<playstatus> Number Play status

0: no file is playing

1: the file is playing

Device only supports playing AMR file. Any other audio format will result in +UPLAYFILE: 0 URC.

13.11 Stop audio file +USTOPFILE

13.11.1 Description Stop the audio file playing from +UPLAYFILE.

A URC is provided after the AT+USTOPFILE command correctly stopped the file.


Set AT+USTOPFILE OK AT+USTOPFILE

OK

URC +UPLAYFILE: 0


UBX-13000621 - R10 Production Information TCP/IP UDP/IP

of 149

14 TCP/IP UDP/IP

14.1 Introduction AT commands for both reading and writing data on sockets are provided and URC notifies the external application of incoming data and transmission result, no need for polling.

When these commands report an error which is not a +CME ERROR, the error code can be queried using the +USOER (more details in section 14.8) AT command.

Some network operators close dynamic NATs after few minutes if there is no activity on the connection (no data transfer in the period). To solve this problem enable the TCP keep alive options with 1 minute delay (view +USOSO command, paragraph 14.5).

IP dotted notation doesn’t support a leading 0 in an IP address (e.g. IP = 010.128.076.034 is not supported, 10.128.76.34 is supported).

The maximum number of sockets that can be managed is 12 (6 – TCP and 6 – UDP).

14.2 Packet Switched Data Action Configuration +UPSDACFG

14.2.1 Description This command allows enable/disable of starting and terminating an independent PPP connection, the default state being “disable”.


Set AT+UPSDACFG=<mode> OK AT+UPSDACFG=1

OK

Read AT+UPSDACFG? +UPSDACFG: <mode>

OK +UPSDACFG: 1

OK

Test AT+UPSDACFG=? +UPSDACFG: [ist of supported <mode>’s]

OK

+UPSDACFG: [0,1]

OK


<mode>


0: Disable. ( Default )

1: Enabled.

Notes :

After enabling the configuration the PPP start call can be made using the AT+UPSDA command.

By default AT+USOCR starts a PPP call in the background.

By setting AT+UPSDACFG=1, the PPP call shall no longer be started when the client creates a socket using AT+USOCR, and the AT+USOCR shall only return the socket identifier.

This feature will avoid the wait/polling for device to acquire IP while creating a socket.

The configuration mode does not persist on device shutdown and needs to be done on every device power-up.



of 149

14.3 Packet Switched Data Action +UPSDA

14.3.1 Description Start/Terminate PPP connection, this will allow the device to attach/detach (acquire IP) independent of any other data operation. This command is dependent on the AT+UPSDACFG value, if the value is enabled AT+UPSDA can be used to start/terminate PPP connection. If AT+UPSDACFG is disabled, this command returns an ERROR.


Set AT+UPSDA=<mode> OK AT+UPSDA=3

OK

Test AT+UPSDA=? +UPSDA: [list of supported <mode>’s]

OK

+UPSDA: [3,4]

OK


<mode>


3: PPP start.

4: PPP stop.

By setting AT+UPSDACFG=0, the AT+UPSDA command will be disabled and the default PPP start will be enabled on creating a socket using AT+USOCR.

By setting the AT+UPSDACFG=0, AT+USOCR command will start a PPP connection in the background and the user has to poll for AT+CMIP to check for the device IP to make sure the call is succeeded.

14.4 Create Socket +USOCR

14.4.1 Description Creates a socket and associates it with the specified protocol (TCP or UDP), returns a number identifying the socket. Such command corresponds to the BSD socket routine. Up to 6 TCP sockets and up to 6 UDP sockets can be created. It is possible to specify the local port to bind within the socket in order to send data from a specific port. The bind functionality is available for both TCP and UDP.


Set AT+USOCR=<protocol>[,<local_port>] +USOCR: <socket>

OK

AT+USOCR=6

+USOCR: 18

OK

Test AT+USOCR=? +USOCR: [6,17][[,1-65535]]

OK


<protocol> Number 6: TCP 17: UDP



of 149

<socket> Number Socket identifier to be used for any future operation on that socket

<local_port> Number Number Local port to be used while sending data. The range goes from 1 to 65535.

NOTE: By default, on creating the first TCP or UDP socket the device makes a network call to acquire system IP. Use the AT+CMIP command to check for the device IP before proceeding for other socket operations. This behavior can be changed by using the AT+UPSDACFG and AT+UPSDA commands.

By setting AT+UPSDACFG=1, the AT+UPSDA command will be enabled and the default PPP start will be disabled on creating a socket using AT+USOCR.

By setting AT+UPSDACFG=1, the AT+USPDA=3 command can be used to start the PPP prior to creating a socket.

By setting AT+UPSDACFG=1, the AT+USPDA=4 command can be used to stop the PPP prior to closing a socket.

14.5 Set Socket Option +USOSO

14.5.1 Description Sets the specified standard option (type of service, local address re-use, linger time, time-to-live, etc) for the specified socket, like the BSD setsockopt routine.

Parameters must be set one by one.


Set AT+USOSO=<socket>,<level>,<opt_name>,<opt_val>[,<opt_val2>]

OK

AT+USOSO=18,6,1,1

OK


<socket> Number Socket identifier

<level> Number 0: IP Protocol <opt_name> for IP Protocol level may be:

• 2: Time-to-live <opt_val>: unsigned 8 bit value representing the TTL. Range 0-255 (default 255)

6: TCP Protocol <opt_name> for Socket level options may be:

• 1: No delay option: don’t delay send to coalesce packets; <opt_val>: Number, enables/disables “no delay” option. 1: enable, 0: disable (default 0)

• 2: Keepalive option: send keepalive probes when idle for <opt_val> milliseconds; <opt_val>: signes 32 bit Number value representing the milliseconds for “keepalive” option. Range 0-2147483647. Default value 7200000 (2 hours).

65535: Socket ( TCP Protocol Only ) <opt_name> for Socket level options may be:

• 8: Keep connections alive. <opt_val>: Number, enables/disables “keep connection alive” option. 1: enable, 0: disable (default 0)

• 128: Linger on close if data present. <opt_val>: Number, sets on/off “linger” option. 1: enable, 0: disable (default 0) <opt_val2>: signed 16 bit Number, linger time, range 0-32767. Default is 0.



of 149

14.6 Get Socket Option +USOGO

14.6.1 Description Retrieves the specified standard option (type of service, local address re-use, linger time, time-to-live, etc) for the specified socket, like the BSD getsockopt routine.


Set AT+USOGO=<socket>,<level>,<opt_name>

+USOGO: <opt_val>[,<opt_val2>]

OK

AT+USOGO =18,0,2

+USOGO:255

OK



<level> Number 0: IP Protocol <opt_name> for IP Protocol level may be:

• 2: Time-to-live . 6: TCP Protocol <opt_name> for Socket level options may be:

• 1: No delay option: don’t delay send to coalesce packets. • 2: Keepalive option: send keepalive probes when idle for <opt_val>

milliseconds. 65535: Socket ( TCP Protocol Only ) <opt_name> for Socket level options may be:

• 8: Keep connections alive. • 128: Linger on close if data present.

For values returned by the +USOGO command, refer to +USOSO description (paragraph 14.5.2).

14.7 Close Socket +USOCL

14.7.1 Description Close the specified socket, like the BSD close routine. In case of remote socket closure the user is notified via the URC (TCP only).


Set AT+USOCL=<socket> OK AT+USOCL=18

OK

URC

(TCP)

+UUSOCL: <socket> +UUSOCL: 18

NOTE: On closing the last TCP or UDP socket the device makes a network call to close the network registration. Use the AT+CMIP command to check for the device IP to be 0.0.0.0.

If we receive a +UUSOCL URC from the server, then we need to close the socket from the client side and reconnect back. Any socket operation after +UUSOCL will lead to failure except AT+USOCL.





of 149

14.8 Get Socket Error +USOER

14.8.1 Description Retrieves the last error occurred in the last socket operation, stored in the BSD standard variable error. This only applies when a socket command returns an ERROR. Not applicable if the socket command is successful.


Action AT+USOER +USOER: <socket_error>

OK

AT+USOER

+USOER: 104

OK

14.8.2 Defined Values Parameter Tye Description

<socket_error> Number Code of the last error occurred in a socket operation. The allowed values are listed in A. 2

0: no error

14.9 Connect Socket +USOCO

14.9.1 Description Establishes a peer-to-peer connection of the socket to the specified remote host on the given remote port, like the BSD connect routine. If the socket is a TCP socket, the command will actually perform the TCP negotiation (3-way handshake) to open a connection. If the socket is a UDP socket, this function will just declare the remote host address and port for later use with other socket operations (e.g. +USOWR, +USORD). This is important to note because if <socket> refers to a UDP socket, errors will not be reported prior to an attempt to write or read data on the socket.

(UDP socket) due to the UDP specific AT commands, this command should be considered obsolete and it is strongly recommended avoid using it while working with UDP sockets. The command’s functionality for UDP socket is maintained for backward compatibility only, consider using +USOST and +USORF commands instead of +USOCO with +USOWR and +USORD.


Set AT+USOCO=<socket>, <remote_addr>, <remote_port>

OK AT+USOCO=18,”98.112.156.21”,1505

OK



<remote_addr> String Remote host IP address in dotted decimal notation form (i.e. four numbers in range 0-255 separated by periods) or domain name of the remote host. Domain name limited to 1kB in length.

<remote_port> Number Remote host port, in range 1-65535



of 149

14.10 Write Socket Data +USOWR

14.10.1 Description Writes the specified amount of data to the specified socket, like the BSD write routine, and returns the number of bytes of data actually written. Applied to UDP sockets too, after a +USOCO Connect Socket command.

There are three kinds of syntax:

• Base syntax normal: writing simple strings to the socket, there are characters which are forbidden

• Base syntax HEX: writing hexadecimal strings to the socket, the string will be converted in binary data and sent to the socket.

• Binary extended syntax: mandatory for writing any character in the ASCII range [0x00, 0xFF]

(about UDP socket): due to the UDP specific AT commands, it is preferred to use the +USOST command to send data via UDP socket. +USOST command doesn’t require the usage of +USOCO before sending data.

(about TCP socket): if no network signal is available, TCP packets are queued until the network will become available again. It the TCP queue is full, the +USOWR command will return error. To get the last socket error, use the +USOER command. If the error returned is 11, it means that the queue is full.

(about UDP socket): if no network signal is available, outgoing UDP packet may be lost.

To enable the base syntax HEX mode, refer to the AT+UDCONF command description (section 20.1).


Set

(Base)

AT+USOWR=<socket>,<length>,<data> +USOWR:<socket>,<length>

OK

AT+USOWR=18,12,"Hello world!"

+USOWR:18,12

OK

Set

(Binary)

AT+USOWR=<socket>,<length>

After the “@” prompt <length> bytes of data are entered

@

+USOWR:<socket>,<length>

OK

AT+USOWR=18,16

@16 bytes of data

+USOWR:18,16

OK



<length> Number Number of data bytes to write:

• Base syntax normal mode: range 0 to 1024 • Base syntax hex mode : range 0 to 2048 • Binary extended syntax: range 0 to 1024

<data> String Data bytes to be written. Note that not all of the ASCII charset can be used.

For Base Syntax:

o Allowed ASCII characters: 0x20 (space), 0x21 and from 0x23 to 0xFF, all the alphanumeric set, symbols and extended ASCII charset from 0x80 to 0xFF

o Forbidden: The control characters from 0x00 to 0x1F (included), 0x22 character, quotation marks (")

o The value of <length> and the actual length of <data> must match



of 149

o For base syntax HEX mode, only ASCII characters 0-9, A-F and a-f are allowed. The <length> parameter must be two times the number of bytes sent.

For Binary Syntax:

o After the command is sent, the user waits for the @ prompt. When it appears the stream of bytes can be provided. After the specified amount of bytes has been sent, the system returns with OK (or ERROR). The feed process cannot be interrupted i.e. the return in the command mode can be effective only when the number of bytes provided is the declared one

o The binary extended syntax is the only way for the system to accept control characters as data; for the AT command specifications 3GPP TS 27.005 [16], characters like <CR>, <CTRL-Z>, quotation marks, etc. have a specific meaning and they cannot be used like data in the command itself. The command is so extended with a specific acceptance state identified by the @ prompt

o This feature can be successfully used when there is need to send a byte stream which belongs to a protocol that has any kind of characters in the ASCII range [0x00,0xFF]

o Binary syntax is not affected by HEX mode option

For <data> parameter not all of the ASCII charset can be used.

14.11 Socket Connection Timeout Control +USOABT

14.11.1 Description This command provides a mechanism to adjust the TCP socket connection timeout from the default to a user selected value.


Set AT+USOABT=<secs> OK AT+USOABT=30

Read AT+USOABT?

+USOABT:<secs>

OK

AT+USOABT?

+USOABT:30

OK

Test

AT+USOABT=? +USOABT:[30,60,90,120,150,180,210,240,270,300]

OK

+USOABT:[30,60,90,120,150,180,210,240,270,300]

OK


<secs> Number The selected timeout in seconds from one of these options <30,60,90,120,150,180,210,240,270,300>

NOTE: default value is 300 seconds

14.12 Send To command +USOST (UDP only)

14.12.1 Description Writes the specified amount of data to the remote address, like the BSD sendto routine, and returns the number of bytes of data actually written. It can be applied to UDP sockets only. This command allows the reuse of the same socket to send data to many different remote hosts.

There are three kinds of syntax:



of 149

• Base syntax normal: writing simple strings to the socket, there are characters which are forbidden

• Base syntax HEX: writing hexadecimal strings to the socket, the string will be converted in binary data and sent to the socket.

• Binary extended syntax: mandatory for writing any character in the ASCII range [0x00, 0xFF]

It is strongly recommended to use this command to send data while using UDP sockets. It is also recommended to avoid +USOCO usage with UDP socket.

(about UDP socket): if no network signal is available, out-going UDP packet may be lost.

To enable the base syntax HEX mode, refer to the AT+UDCONF command description (section 20.1).


Set

(Base)

AT+USOST=<socket>,<remote_ip_address>,<remote_port>,<length>,<data>

+USOST:<socket>,<length>

OK

AT+USOST=3,"151.9.34.66",449,16,"16 bytes of data"

+USOST: 3,16

OK

Set

(Binary)

AT+USOST=<socket>,<remote_ip_address>,<remote_port>,<length>

After the “@” prompt <length> bytes of data are entered

@

+USOST:<socket>,<length>

OK

AT+USOST=3,"151.9.34.66",449,16

@16 bytes of data

+USOST: 3,16

OK



<remote_ip_address> String Remote host IP address

<remote_port> Number Remote host port

<length> Number Number of data bytes to write

• Base syntax normal mode: range 0 to 1024 • Base syntax hex mode : range 0 to 2048 • Binary syntax mode: range 0 to 1024

<data> String Data bytes to be written (note that not all of the ASCII charset can be used)

For Base Syntax:

o Allowed ASCII characters: 0x20 (space), 0x21 and from 0x23 to 0xFF. Substantially all of the alphanumeric set, symbols and extended ASCII charset from 0x80 to 0xFF

o Forbidden: The control characters from 0x00 to 0x1F (included), 0x22 character, quotation marks (")

o The value of <length> and the actual length of <data> must match. o For base syntax HEX mode, only ASCII characters 0-9, A-F and a-f are allowed. The <length>

parameter must be two times the number of bytes sent.

For Binary Syntax:



of 149

o After the command is sent, the user waits for the @ prompt. When it appears the stream of bytes can be provided. After the specified amount of bytes has been sent, the system returns with OK (or ERROR). The feed process cannot be interrupted i.e. the return in the command mode can be effective only when the number of bytes provided is the declared one

o The binary extended syntax is the only way for the system to accept control characters as data; for the AT command specifications 3GPP TS 27.005 [16], characters like <CR>, <CTRL-Z>, quotation marks, etc. have a specific meaning and they cannot be used like data in the command itself. The command is so extended with a specific acceptance state identified by the @ prompt

o This feature can be successfully used when there is need to send a byte stream which belongs to a protocol that has any kind of characters in the ASCII range [0x00,0xFF]

o Binary syntax is not affected by HEX mode option

14.13 Read Socket Data +USORD

14.13.1 Description Reads the specified amount of data from the specified socket, like the BSD read routine. The URC +UUSORD: <socket>,<length> notifies that new data is available for reading, either when new data arrives or after a partial read by the user for the socket.

(about UDP socket) Due to the UDP specific AT command, it is preferred to use the +USORF command to read data from UDP socket. +USORF command doesn’t require the usage of +USOCO before reading data.

When applied to UDP active sockets if the UDP socket is not set in listening mode (see +USOLI) it won’t be possible to receive any packet if a previous write operation is not performed.

If the HEX mode is enabled (refer to +UDCONF command, section 20.1) the received data will be displayed using a hexadecimal string.


Set AT+USORD=<socket>,<length> +USORD: <socket>,<length>,<data in the ASCII [0x00,0xFF] range>

OK

AT+USORD=18,16

+USORD: 18,16,"Hello World"

OK

URC +UUSORD: <socket>,<length> +UUSORD: 18,16



<length> Number Number of data bytes

• to read stored in buffer, in range 0-1024 in the set command • read from buffer, in range 0-1024 • stored in buffer for the URC

<data> String Data bytes to be read

The returned data may be any ASCII character in the range [0x00,0xFF] i.e. control characters. The starting quotation marks shall not be taken into account like data; the first byte of data starts after the first quotation marks. Then the other characters are provided for a <length> amount. An application should rely on the <length> info to count the received number of characters (after the starting quotation marks) especially if any protocol control characters are expected.



of 149

If an application deals with letter and number characters only i.e. all of the expected characters are outside the [0x00, 0x1F] range and are not quotation marks, the AT+USORD response quotation marks can be assumed to identify the start and the end of the received data packet. Always check <length> to identify the valid data stream.

If the number of data bytes requested to be read from the buffer is bigger than the number of bytes stored in the buffer only the available amount of data bytes will be read.

When <length>= 0, the command returns the amount of data present in the buffer only for the next packet.

If the HEX mode is enabled, the length of <data> will be 2 times <length>.

14.14 Receive From command +USORF (UDP only)

14.14.1 Description Reads the specified amount of data from the specified UDP socket, like the BSD recvfrom routine. The URC +UUSORF: <socket>,<length> (or also +UUSORD: <socket>,<length>) notifies that new data is available for reading. No further URC will be issued until the host reads the data with the +USORF command from the first URC +UUSORF: <socket>,<length>. The host must read the entire length of data from the +UUSORF URC or the remaining data will be lost. The host can check if there is a pending +UUSORF URC by issuing the +USORF=<socket>,0 command. This will return the length of the data for the next URC or 0 if no further data is to be signaled with a URC

This command can be applied to UDP sockets only, and it can be used to read data after both +UUSORD and +UUSORF unsolicited indication.

It is strongly recommended to use this command to read data while using UDP sockets. It is also recommended to avoid +USOCO usage with UDP socket.

If the HEX mode is enabled (refer to +UDCONF command, section 20.1) the received data will be displayed using a hexadecimal string.


Set AT+USORF=<socket>,<length> +USORF: <socket>,<remote_ip_addr>,<remote_port>,<length>,<data in the ASCII [0x00,0xFF] range>

OK

+USORF: <socket>,<length>

OK

AT+USORF=18,16

+USORF: 18,"151.9.34.66",2222,16,"16 bytes of data"

OK

AT+USORF=18,0

+USORF: 18,16

OK

URC +UUSORF: <socket>,<length> +UUSORF: 18,16



<remote_ip_address> String Remote host IP address

<remote_port> Number Remote host port

<length> Number Number of data bytes to read, in range 0-1024

<data> String Data bytes to be read



of 149

Once the device receives the first incoming packet on an UDP socket. The URC +UUSORF:<socket ID>,<packet data length> is displayed. Any subsequent incoming packets are queued in the memory but the next URC +UUSORF is not displayed until the first packet data is read using AT+USORF=<socket id>,<packet data length>. There has to be an AT+USORF read call for every +UUSORF URC indication, this allows the next URC to be displayed.

The returned data may have any kind of ASCII character in the range [0x00,0xFF] i.e. control characters too. The starting quotation marks shall not be taken into account as data; the first byte of data starts after the first quotation marks. Then the other characters are provided for a <length> amount. At the end of the length byte stream, another quotation mark followed by <CR><LF> is provided for user convenience and visualization purposes. An application should rely on the <length> info to count the received number of characters (after the starting quotation marks) especially if any protocol control characters are expected.

If an application deals with letter and number characters only i.e. all of the expected characters are outside the [0x00, 0x1F] range and are not quotation marks, the AT+USORD response quotation marks can be assumed to identify the start and the end of the received data packet. Even in this case, it is recommended to use the <length> field to identify the valid data stream.

If the HEX mode is enabled, the length of <data> will be 2 times <length>.

14.15 Set Listening Socket +USOLI

14.15.1 Description Sets the specified socket in listening mode on the specified port of service, waiting for incoming connections (TCP).

• For TCP sockets, incoming connections will be automatically accepted and notified via the URC +UUSOLI: <socket>,<ip_address>,<port>,<listening_socket>,<local_ip_address>,<listening_port>, carrying the connected socket identifier, the remote IP address and port.

• For UDP sockets, incoming data will be notified via URC +UUSORF:<listening_socket>,<length>. To know from which remote IP address and port the data is coming from, use the AT+USORF command.


Set AT+USOLI=<listening_socket>,<port> OK

(TCP)

AT+USOLI=18,1200

OK

+UUSOLI: 19,"151.63.16.7",1403,18,"82.89.67.164",1200

(UDP) AT+USOLI=18,1182 OK

+UUSORF: 18,98

URC

(TCP)

+UUSOLI: <socket>,<ip_address>,<port>,<listening_socket>,<local_ip_address>,<listening_port>

+UUSOLI: 20,"151.63.16.7",1403,18,"82.89.67.164",200

URC

(UDP)

+UUSORF: <listening_socket>,<len> +UUSORF: 19,96



of 149



<port> Number Port of service, range 1-65535. Port numbers below 1024 are not recommended since they are usually reserved

<ip_address> String Remote host IP address

<listening_socket> Number Socket identifier specified within the AT+USOLI command, indicates on which listening socket the connection has been accepted

<local_ip_address> String TE IP address

<listening_port> Number Listening port that has accepted the connection. This port is specified within the AT+USOLI command

For an incoming UDP packet of n bytes, the read command should read all the n bytes of data in one call.

Device does not support multiple TCP connections from a single listening port.

If the TCP communication port created from the listening socket is closed by the remote host, we need to close both the communication socket AND listening socket locally. The local device can then re-open a listening socket on the same IP and port to establish a new TCP communication port.

14.15.2.1 Example:

AT+USOLI=18,1182

OK

+UUSORF: 18,98

AT+USORF=18,98

+USORF: 18,"151.9.34.66",2222,98,98 bytes of data

OK

14.16 Set socket in Direct Link mode +USODL

14.16.1 Description Set the specified socket in direct link mode with an already connected socket and waiting for incoming data and sending data. To Exit the direct link mode the user has to specify the escape sequence (+++)


Set AT+USODL=< socket> CONNECT

(UDP)

AT+USODL=18

CONNECT



USODL for UDP can only be used if USOCO is used to connect to socket rather than USOST.

In this mode no other AT commands can be executed.



of 149

On exiting this, the socket will be connected and other AT commands to send and receive data can be used on the same socket.

While the device is either sending or receiving data in direct link mode all URCs that we have set up will be buffered (unless a URC was specifically set up to not be buffered while data is active). The URCs will be sent once the device is in the DISCONNECT state.

14.17 Socket Control +USOCTL

14.17.1 Description Allows interaction with the low level socket layer.


Set AT+USOCTL=<socket>,<param_id> +UUSOCTL: <socket>,<param_id>,<param_val>[,<param_val2>]

OK

AT+USOCTL=0,2

+UUSOCTL: 0,2,38

OK



<param_id> Number Control request identifier. Possible values are:

0: query for socket type 1: query for last socket error 2: get the total amount of bytes sent from the socket 3: get the total amount of bytes received by the socket 4: query for remote peer IP address and port 10: query for TCP socket status (only TCP sockets) 11: query for TCP outgoing unacknowledged data (only TCP sockets) 5-9, 12-99: RFU

<param_val> Number / String This value may assume different means depending of <param_id>.

If <param_id> is 0, <param_val> can assume these values:

• 6 TCP socket • 17: UDP socket


• N: last socket error


• N: the total amount (in bytes) of sent (acknowledged + unacknowledged) data


• N: the total amount (in bytes) of received (read) data


• A string representing the remote peer IP address expressed in dotted decimal form


• 0: the socket is in INACTIVE status • 1: the socket is in LISTEN status • 2: the socket is in SYN_SENT status • 3: the socket is in SYN_RCVD status • 4: the socket is in ESTABILISHED status



of 149


• 5: the socket is in FIN_WAIT_1 status • 6: the socket is in FIN_WAIT_2 status • 7: the sokcet is in CLOSE_WAIT status • 8: the socket is in CLOSING status • 9: the socket is in LAST_ACK status • 10: the socket is in TIME_WAIT status


• N: the total amount of outgoing unacknowledged data

<param_val2> Number This value is present only when <param_id> is 4. It represents the remote peer IP port.

14.18 Configure Maximum Segment Size +UMSS

14.18.1 Description The +UMSS command is used to configure the maximum segment size for a minimum of 28 bytes to a maximum of 1460 bytes. The default size is 1460 bytes.


Read AT+UMSS? +UMSS: <max seg size>

OK

+UMSS: 1460

OK

Set AT+UMSS=<max seg size> OK AT+UMSS=1430

OK

Test AT+UMSS=? +UMSS: [range of valid mss values]

OK

+UMSS: [28-1460]

OK


<max seg size> Number Maximum number of bytes that can be transmitted per TCP packet.


UBX-13000621 - R10 Production Information DNS

of 149

15 DNS

15.1 Resolve Name / IP Number through DNS +UDNSRN

15.1.1 Description Translates a domain name to an IP address or an IP address to a domain name by using an available DNS.

When this command reports an error which is not a +CME ERROR, the error class and code is provided through +USOER AT command (more details in section 14.8).


Set AT+UDNSRN=<resolution_type>,<domain_ip_string>

+UDNSRN: <resolved_ip_address>

OK

+UDNSRN: < resolved_domain_name >

OK

AT+UDNSRN=0,"www.google.com"

+UDNSRN: "74.125.28.147"

OK

AT+UDNSRN=1," 74.125.28.147"

+UDNSRN: " www.google.com "

OK


<resolution_type> Number Type of resolution operation

0: domain name to IP address 1: IP address to domain name (host by name)

<domain_ip_string> String Domain name (resolution_type=0) or the IP address in (resolution_type=1) to be resolved. Domain name limited to 1kB in length.

<resolved_ip_address> String Resolved IP address corresponding to the specified domain name

<resolved_domain_name> String Resolved domain name corresponding to the provided IP address

NOTE: The DNS cache on the device can hold a maximum of 5 records for a valid TTL value period of each entry.


UBX-13000621 - R10 Production Information File system AT Commands

of 149

16 File system AT Commands

16.1 Download File +UDWNFILE

16.1.1 Description This command stores (writes) a file into the file system. The available free memory space is checked before starting the file transfer. If the file exceeds the available space an error is returned. If the file already exists it will be overwritten. No interrogation (test) is possible for this command. In case of any error, the return code will always be 100 (“unknown”) or 4 (“ERROR”). If an error occurs during the file writing, the transfer is aborted and it is up to the user to delete the file.

The maximal speed of the serial port is 230400 b/s.

The maximum available user space in the file system of FW75-C200 and LISA-C200 is 1 MB.


Set AT+UDWNFILE=<filename>,<size> >

Start transfer of file data

OK

AT+UDWNFILE=”filename”,36

>these bytes are the data of the file

OK


<filename> String File name (max. 47 characters)

<size> Number File size expressed in bytes

The stream of bytes can be entered after the “>” prompt has been provided to the user. The file transfer is terminated exactly when <size> bytes have been entered and either OK or an error message is returned. The feed process cannot be interrupted, i.e. command mode is re-entered once the user has provided the declared number of bytes.

While the device is sending data, all URCs that we have set up will be buffered (unless a URC was specifically set up to not be buffered while data is active). The URCs will be sent once all the bytes specified have been sent.

16.2 Delete File +UDELFILE

16.2.1 Description This command deletes a file from the file system.

If <filename> file is not stored in the file system the following message error will be provided: +CME ERROR: FILE NOT FOUND




of 149


Set AT+UDELFILE=<filename> OK AT+UDELFILE=”filename”

OK



16.3 Read File +URDFILE

16.3.1 Description This command retrieves a file from the file system.


Set AT+URDFILE=<filename > +URDFILE:<filename>,<size>,<data>

OK

AT+URDFILE=”filename”

+URDFILE: “filename”,36,”these bytes are the data of the file”

OK



<size> Number File size expressed in bytes

<data> Byte Stream Content of the file read

The returned file data is displayed as an ASCII string of <length> chars in the range [0x00,0xFF]. At the end of the string, <CR><LF> are provided for user convenience and visualization purposes.

Currently the typical transfer time for a 200k file is approximately less than a minute, at 115200 bauds. At lower baud rates the transfer time is longer.

16.4 List Files Information +ULSTFILE

16.4.1 Description This command retrieves a file about the FFS. Depending on the specified <param_id>, it can print:

• List of files stored into the FFS. • Remaining free FFS space expressed in bytes. • Size of the specified file expressed in bytes.

In FFS these are the file limits: • Maximum number of files that can be stored: 135 files • Maximum length of the file name: 47 characters




of 149


Set AT+ULSTFILE=[<param_id >[,<filename>]]

+ULSTFILE:[<filename1>[,<filename2>[,…..[<filenameN>]]]]

OK

Or

+ULSTFILE:<free_ffs_space>

OK

Or

+ULSTFILE:<file_size>

OK

AT+ULSTFILE=

+ULSTFILE: “filename”

OK

AT+ULSTFILE=1

+ULSTFILE:236800

OK

AT+ULSTFILE=2,”filename”

+ULSTFILE:784

OK


<param_id> Number Optional parameter. Possible values are: 0: default value, list the files 1: get free space 2: get file size, parameter <filename> is required in this case

<free_fss_space> Number Available free space on FFS in bytes

<file_size> Number Size of the file specified with parameter <filename> when <param_id> is 2

<filename> String File name


UBX-13000621 - R10 Production Information FTP

of 149

17 FTP Proprietary u-blox AT commands. FTP AT commands set can be used for sending and receiving files over the available bearer, transparently retrieving and storing them in the file system. Standard file and directory management operations on the remote FTP server are as well possible. Basically, two AT commands are necessary for an FTP client service: one AT command to configure the FTP profile, a second AT command to execute a specific FTP command. The final result of an FTP execute command will be notified through the URC +UUFTPCR whereas data will be provided through URC +UUFTPCD. When these commands report an error which is not a +CME ERROR, the error code can be queried using the +UFTPER AT command (more details in section 17.5).

17.1 FTP Control +UFTP

17.1.1 Description Sets up a parameter for FTP service, or resets a parameter to its default value. Set/reset command needs to be executed for each single <param_tag>. Read command returns the current setting of all the FTP parameters, one per line (i.e. the FTP profile). Type Syntax Response Example

Set Set Command

AT+UFTP=<param_tag>,<param_val>

Reset command

AT+UFTP=<param_tag>

OK

OK

AT+UFTP=7,21

OK

AT+UFTP=5

OK

Read AT+UFTP? +UFTP: 0,<param_val0>

+UFTP: 1,<param_val1>

….

OK

+UFTP: 0,"216.239.59.147" +UFTP: 1,"" +UFTP: 2,"username" +UFTP: 4,"account" +UFTP: 5,0 +UFTP: 6,0 +UFTP: 7,21

OK

Test AT+UFTP=? +UFTP: (list of supported <param_tag>s)

OK

+UFTP: (0-7) OK


<param_tag> Number 0: FTP server IP address <param_val> is the text string of FTP server IP address in dotted decimal notation form (e.g. 111.222.333.444)

1: FTP server name <param_val> is the text string of FTP serve name (e.g. ftp.server.com). Maximum length 128 characters

2: Username <param_val> is the user name string (maximum 30 characters) for the FTP login procedure

3: Password



of 149


<param_val> is the password text string (maximum 30 characters) for the FTP login procedure

4: Account <param_val> is the additional user account text string (maximum 30 characters) for the FTP login procedure

5: Inactivity timeout <param_val> is the inactivity timeout period in seconds, from 0 to 86400 s. 0 means no timeput (the FTP session will not be terminated in the absence of incoming traffic). The default value is 30 s

6: FTP mode <param_val> selects the FTP mode:

o 0: Active (default) o 1: Passive

7: FTP server port <param_vall> is the remote FTP server listening port, it must be a valid TCP port value:

o Number value between 1 and 65535: default value is 21

<param_val> Number/String Type and supported content depend on related <param_tag> (details are given here below). If <param_val> is not specified the value of the corresponding parameter <param_tag> is reset to default value

The response to read command does not display the <param_tag>=3 (password).

<param_tag>=0 and <param_tag>=1 are mutually exclusive. If the value for <param_tag>=0 is specified by the user, then value for <param_tag>=1 is reset or vice versa. The ‘Read’ command will always show the <param_val> for both the param_tag>s (0 and 1) against <param_tag>=0 and <param_tag>=1 will always be blank. But the user can and should use <param_tag>=1 to specify the server name for the FTP server.

Some network operators do not allow incoming connections. Due to these limitations introduced by network operators it is possible to encounter problems using FTP active mode. If the FTP active mode fails to exchange files, try the passive mode to solve the problem.

If a failure occurs at any time, issue the logout command to reset the FTP client. Otherwise behavior may not be predictable.

This command returns an error if executed before the URC UUFTPCR is received as a response to the UFTPC command.

The following param_tag's will return an error if executed while an FTP session is in progress: 0, 1, 2, 3, 4 and 7.

17.2 FTP Command +UFTPC

17.2.1 Description Triggers the FTP actions corresponding to <ftp_command> parameter. The response indicates if sending the command request to FTP process was successful or not. Final result of FTP action will be returned to the user via the URC +UUFTPCR (refer to paragraph 17.4 for the command description). As well, when data is requested by user (e.g. file or directory lists), the information is notified after reception from the FTP server via the URC +UUFTPCD (See section 17.3 for the command description). Type Syntax Response Example

Set AT+UFTPC=<ftp_command>,[<param1>,[<param2>]]

OK AT+UFTPC=3,"RENAME.tst","RENAME_TEST.tst"

OK

Test AT+UFTPC=? +UFTPC: (list of supported <param_tag>s)

OK

+UFTPC: (0-8,10-11,13-15) OK



of 149


<param1> String Content depend on related <ftp_command> (details are given below)

<param2> String Content depend on related <ftp_command> (details are given below)

<ftp_commad> Number 0: FTP logout; terminates the FTP session by performing a logout. Notice that this AT command just sends a command request to the FTP process. The final result will be notified via the URC +UUFTPCR.

• <param1>,<param2> are not allowed (do not give any value). 1: FTP login; connects to the FTP server using the parameters of current FTP profile (set via AT+UFTP command). Notice that this AT command just sends a command request to the FTP process. The FTP result will notified via the URC +UUFTPCR.

• <param1>,<param2> are not allowed (do not give any value). 2: Delete file from the FTP server. This AT command just sends a command request to the FTP process. The FTP result will notified via the URC +UUFTPCR.

• <param1> mandatory parameter; text string of the file name to be deleted from FTP host.

• <param2> parameter is not allowed (do not give any value). 3: Rename file. This AT command just sends a command request to the FTP process. The FTP result will notified via the URC +UUFTPCR .

• <param1> mandatory parameter; text string of the old file name on the FTP host, to be renamed.

• <param2> mandatory parameter; text string of the new file name. 4: Retrieve file from the FTP server. This AT command just sends a command request to the FTP process. The FTP result will notified via the URC +UUFTPCR.

• <param1> mandatory parameter; is the remote file name text string to be retrieved from the FTP host.

• <param2> mandatory parameter; is the local file name (module file system) text string to be stored in the file system.

5: Store file on the FTP server. This AT command just sends a command request to the FTP process. The FTP result will notified via the URC +UUFTPCR.

• <param1> mandatory parameter; is the local file name text string to be sent from the file system.

• <param2> mandatory parameter; is the remote file name (module file system) text string to be stored on the FTP server.

6: Retrieve a file from the FTP server using direct link mode. This command handles the initial steps of the FTP protocol for retrieving a file; after that it will establish a transparent end to end communication with the data connection TCP socket via the serial interface. After the CONNECT message, the file content will be directly sent to the serial interface. This operation may take up to 10 s because the command also handles the final steps of the FTP protocol.

• <param1> mandatory parameter; it is the remote file name to be retrieved from the FTP server.

• <param2> parameter is not allowed (do not give any value). 7: Send a file to the FTP server using the direct link mode. This command handles the initial steps of the FTP protocol for sending a file; after that it will establish a transparent end to end communication with the data connection TCP socket via the serial interface. After the CONNECT message, the user can send the file content via the serial interface. Once finished, the user must wait at least 2 s before sending the +++ sequence to switch off the direct link mode. This operation may take a few seconds because the command also handles the final steps of the FTP protocol.

• <param1> mandatory parameter; it is the remote file name to be stored in the FTP server

• <param2> parameter is not allowed (do not give any value). 8: Change working directory to the specified one. This AT command just sends a command request to the FTP process. The FTP result will notified via the URC +UUFTPCR.

• <param1> mandatory parameter; is the text string of the destination directory name on the FTP host.

• <param2> parameter is not allowed (do not give any value). 10: Create a directory on the FTP host. This AT command just sends a command request to the FTP process. The FTP result will notified via the URC +UUFTPCR.

• <param1> mandatory parameter; is the text string of the new directory name to be made on the FTP server.

• <param2> parameter is not allowed (do not give any value).



of 149


11: Remove directory from the remote FTP server. This AT command just sends a command request to the FTP process. The FTP result will notified via the URC +UUFTPCR.

• <param1> mandatory parameter; is the text string of the existing directory name to be removed from the FTP host.

• <param2> parameter is not allowed (do not give any value). 13: Information of a file or a directory. This AT command just sends a command request to the FTP process. Information of specified file or directory from the FTP server will be returned via URC +UUFTPCD. The FTP result will notified via the URC +UUFTPCR.

• <param1> optional parameter; is the text string of the path file/directory name to be listed. If not specified, the current directory list is requested.

• <param2> parameter is not allowed (do not give any value). 14: List file names in a specified directory. This AT command just sends a command request to the FTP process. List of file names received from FTP server will be returned via URC +UUFTPCD. The FTP result will notified via the URC +UUFTPCR.

• <param1> > optional parameter; is the text string of the path (file or directory) to be name listed. If not specified, the list of files names of current working directory is requested.

• <param2> parameter is not allowed (do not give any value). 15: Abort current FTP operation. This AT command will abort any previous AT command that has a pending URC. This command will not work if the URC has for the previous command has already been received.

• <param1> parameter is not allowed (do not give any value). • Note that this command should be used in conjunction with the

+USOABT, socket about timer, to prevent long wait times when a socket for FTP cannot be established.

While the device is either sending or receiving data in direct link mode (i.e +UFTPC=6 or +UFTPC=7) all URCs that have been set up will be buffered (unless a URC was specifically set up to not be buffered while data is active). The URCs will be sent once the device is in the DISCONNECT state.

17.3 FTP Unsolicited Data URC +UUFTPCD

17.3.1 Description Returns the data received from the remote FTP server in response to a specified <ftp_command> request previously sent via +UFTPC command.


URC +UUFTPCD: <ftp_command>,<ftp_data_len>,<ftp_data>

+UUFTPCD: 13,16,”16 bytes of data”


<ftp_command> Number FTP command as detailed in Defined Values paragraph 17.2.2 “File Transfer Protocol Command +UFTPC”.

<ftp_data_len> Number Amount of data in bytes.

<ftp_data> String Data available from the FTP server in the ASCII [0x00,0xFF] range. The starting quotation mark shall not be taken into account like data, the first byte of data



of 149

starts after the first quotation mark. Total number of bytes is <ftp_data_len>. At the end of the byte stream, another quotation mark is provided for user convenience and visualization purposes.

17.4 FTP Command Result URC +UUFTPCR

17.4.1 Description

The final result of the operation for an FTP command previously sent with +UFTPC is provided with this URC.


URC +UUFTPCR: <ftp_command>,<ftp_result>

+UUFTPCR: 1,1


<ftp_command> Number FTP command as detailed in Defined Values paragraph 17.2.2 “File Transfer Protocol Command +UFTPC”.

<ftp_result> Number 0: Fail 1: Success.

17.5 FTP Error +UFTPER

17.5.1 Description This command retrieves the error class and code of the last FTP operation.


Action AT+UFTPER +UFTPER: <error_class>,<error_code>

OK

+UFTPER: 0,0

OK


<error_class> Number Value of error class. Values are listed in paragraph A.1

<error_code> Number Value of class-specific error code (reply code if <error_class> is 0). The values are listed in A.1.1


UBX-13000621 - R10 Production Information HTTP

of 149

18 HTTP u-blox proprietary AT commands for HTTP service. This section describes the HTTP AT commands set that can be used for sending requests to a remote HTTP server, receiving the server response and transparently storing it in the file system. Supported methods are: HEAD, GET, DELETE, PUT, POST file and POST data.

When these commands report an error which is not a +CME ERROR, the error code can be queried using the +UHTTPER AT command (more details in section 18.4)

18.1 HTTP Control +UHTTP

18.1.1 Description Sets up the necessary parameters for HTTP service, or resets them to the default values. Up to 4 different HTTP profiles can be defined. To change the settings of a specified HTTP profile set command needs to be executed for each single <param_tag>. The get command returns the current setting of the specified parameter of HTTP profile, while the reset command resets to default values all the parameters of specified HTTP profile.


Set Set command

AT+UHTTP=<profile_id>,<param_tag>,<param_val>

Get command

AT+UHTTP=<profile_id>,<param_tag>

Reset command

AT+UHTTP=<profile_id>

OK

+UHTTP: <profile_id>, <param_tag>, <param_val>

OK

OK

AT+UHTTP=0,1,”www.moderndynamic.com”

OK

AT+UHTTP=0,1

+UHTTP: 0,1,”www.modern

dynamic.com”

OK

AT+UHTTP=0

OK

Test AT+UHTTP=? +UHTTP: (list of supported <profile_id>s),(list of supported <param_tag>s)

OK

+UHTTP: (0-3),(0-5)

OK


<profile_id> Number HTTP profile identifier, in range 0-3

<param_val> Number / String Type and supported content depend on related <param_tag> (details below). If <param_val> is not specified, the current parameter value for the corresponding <param_tag> is returned.

<param_tag> Number If <param_tag> and <param_val> are not specified, all the parameters of the corresponding HTTP <profile_id> are reset to default value.

0: HTTP server IP address • <param_val>: text string of HTTP server IP address in dotted decimal

notation form (i.e. four numbers in range 0-255 separated by periods)

http://www.moderndynamic.com/

http://www.moderndynamic.com/



of 149


1: HTTP server name • <param_val>: text string of HTTP server name (e.g.

"http.server.com") Maximum length for string is 128 characters 2: Username

• <param_val>: user name text string (maximum 30 characters) for the HTTP login procedure if authentication is used

3: Password • <param_val>: password text string (maximum 30 characters) for the

HTTP login procedure if authentication is used 4: Authentication type

• <param_val> is the HTTP authentication method (if any) o 0: No authentication (default) o 1: Basic authentication

5: HTTP server port • <param_val> Number type value of the HTTP server port to be used

in HTTP request, in range 1-65535. Default value is 80.

<param_tag>=0 and <param_tag>=1 are mutually exclusive. If <param_val> value for <param_tag>=0 is specified by user, then value for <param_tag>=1 is reset, or vice versa.

18.2 HTTP Command +UHTTPC

18.2.1 Description Triggers the HTTP action specified in <http_command> parameter, using the HTTP profile settings (previously set up by AT+UHTTP command), and corresponding to <profile_id>. The response indicates if sending the command request to HTTP process was successful or not. Final result of HTTP action will be returned to the user via the unsolicited indication +UUHTTPCR (section 18.3).


Set AT+UHTTPC=<profile_id>, <http_command>,<param1>,<param2>[,<param3>[,<param4>]]

OK AT+UHTTPC= 0,1,"/path/file.html","resp

onseFilename"

OK

Test AT+UHTTPC=? +UHTTPC: (list of supported <profile_id>s),(list of supported <http_command>s)

OK

+UHTTPC: (0-3), (0-5)

OK



<param1> String Path of HTTP server resource. Maximum length 128 characters

<param2> String Filename where the HTTP server response will be stored. If the file already exists, it will be overwritten. If <param2> is the empty string (""), the default "http_last_response_<profile_id>" filename will be used

<param3> String Content depends on related <http_command> (details below).

<param4> Number Content depends on related <http_command> (details below).

<http_command> Number 0: HEAD command; issue a HEAD request to HTTP server. Command just sends a command request to the HTTP process. The final HTTP command result will be notified via the URC +UUHTTPCR (see detailed description)

• <param3>: not allowed



of 149


• <param4>: not allowed 1: GET command; perform a GET request to HTTP server. Command just sends a command request to the HTTP process. The final HTTP command result will be notified via the URC +UUHTTPCR (see details below)

• <param3>: not allowed • <param4>: not allowed

2: DELETE command; send a DELETE request to HTTP server. Command just sends a command request to the HTTP process. The final HTTP command result will be notified via the URC +UUHTTPCR (see detailed description)

• <param3>: not allowed • <param4>: not allowed

3: PUT command; perform a PUT request to HTTP server. Command just sends a command request to the HTTP process. The final HTTP command result will be notified via the URC +UUHTTPCR (see detailed description)

• <param3>: mandatory parameter; text string of the file system filename to be sent to the HTTP server within the PUT request

• <param4>: not allowed 4: POST a file command; issue a POST request for sending a file to the HTTP server. Command just sends a command request to the HTTP process. The final HTTP command result will be notified via the URC +UUHTTPCR (see detailed description).

• <param3>: mandatory parameter; text string of the file system filename to be sent to the HTTP server with the POST request

• <param4> mandatory parameter of Number type; it is the HTTP Content-Type identifier o 1: application/x-www-form-urlencoded o 2: text/plain o 3: application/octet-stream o 4: multipart/form-data

5: POST data command; send a POST request to HTTP server using the data specified in <param3> parameter. Command just sends a command request to the HTTP process. The final HTTP command result will be notified via the URC +UUHTTPCR (see detailed description).

• <param3>: mandatory parameter; text string of the data to be sent to the HTTP server with the POST request. The data must be formatted according to the Content-Type specified in <param4> parameter.

• <param4> mandatory parameter of Number type; it is the HTTP Content-Type identifier

o 1: application/x-www-form-urlencoded

o 2: text/plain

o 3: application/octet-stream

o 4: multipart/form-data

Data string must not exceed the maximum length of 128 bytes and not all of the ASCII charset can be used. Allowed ASCII characters are: 0x20 (space), 0x21 and from 0x23 to 0xFF. Substantially all of the alphanumeric set, symbols and extended ASCII charset from 0x80 to 0xFF. The control characters from 0x00 to 0x1F (included) and the 0x22 character, quotation mark ("), are forbidden.

If <http_command>=4 (POST a file), then the module automatically adds the following HTTP header:

Content-Disposition: form-data; name="file_post"; filename=...

Where "…" is replaced by the filename specified in <param3>

18.3 HTTP Command Result URC +UUHTTPCR

18.3.1 Description

This unsolicited indication returns the final result of HTTP command AT+UHTTPC.



of 149


URC +UUHTTPCR: <profile_id>,<http_command>, <http_result>

+UUHTTPCR: 0,1,1



<http_command> Number Specifies values of <http_command> used in +UHTTPC in range 0-5

<http_result> Number 0: Fail 1: Success

18.4 HTTP Protocol Error +UHTTPER

18.4.1 Description Retrieves the error class and code of the last HTTP operation on a specified HTTP profile.


Set AT+UHTTPER=<profile_id> +UHTTPER: <profile_id>, <error_class>,<error_code>

OK

AT+UHTTPER=0

+UHTTPER=0,3,11

OK



<error_class> Number List of the allowed values is in annex A.1

<error_code> Number Value of class-specific error codes (reply code if class is 0). When <error_class>=10 (wrong HTTP API usage), allowed <error_code> values are listed in A.1.2


UBX-13000621 - R10 Production Information GNSS

of 149

19 GNSS

19.1 GNSS Power Management +UGPS

19.1.1 Description The +UGPS command switches on or off a u-blox GNSS receiver connected to the cellular module via a dedicated DDC (I2C) interface.

This command is also used to set the aiding type to be used to enhance GNSS performance, e.g. to decrease Time To First Fix (TTFF), thus allowing to calculate the position in a shorter time with higher accuracy. The following aiding types are supported:

• Automatic local aiding: the cellular module automatically uploads data such as ephemeris, almanac, last position, time, etc. from the GNSS receiver into its local memory, and restores back the GNSS receiver at next power up of the GNSS module (if data is still valid, otherwise it uses CDMA information such as country code for a rough position estimation)

• AssistNow Online: See the +UGAOP and +UGSRV command descriptions. If CellLocate® is used, the first HTTP profile will be properly configured

• AssistNow Offline: See the +UGAOF and +UGSRV command descriptions.

• AssistNow Autonomous: based on a broadcast ephemeris downloaded from the satellite (or obtained by AssistNow Online) the receiver can autonomously generate an accurate satellite orbit representation («AssistNow Autonomous data») that is usable for navigation much longer than the underlying broadcast ephemeris was intended for. This makes downloading new ephemeris or aiding data for the first fix unnecessary for subsequent start-ups of the receiver.

For a more detailed description on aiding modes and possible suggestions, refer to GPS Implementation Application Note [47].

The AssistNow Autonomous feature may be not fully supported on all Multi-GNSS receivers. For more details on AssistNow Autonomous feature see the corresponding u-blox-GNSS Receiver Description.

If using CellLocate® and HTTP commands, the HTTP profiles in the range 1-3 must be used.

It is possible to combine more than one aiding mode. To do this, use the sum of the <mode> values of the desired aiding modes (e.g.: aiding <mode>=3 means local aiding plus AssistNow Offline). It is also possible to switch from one aiding mode to another one without powering off the GNSS receiver. If the following sequence is provided (AT+UGPS=1,1 and then AT+UGPS=1,5), then the first one powers on the GNSS receiver with local aiding support, and the second command adds the AssistNow Online. After the second command, the local aiding is not restarted, therefore URC for it will not be sent again.

In the factory-programmed settings, the cellular modules configure the GNSS receiver through +UGPS AT command to not provide the NMEA sentences.

GNSS AT commands are supported by LISA-C200 from version x3S onwards.

The latest u-blox GNSS products are multi-GNSS receivers capable of receiving and processing signals from multiple Global Navigation Satellite Systems (GNSS). u-blox concurrent GNSS receivers are multi-GNSS receivers that can acquire and track satellites from more than one GNSS system at the same time, and utilize them for positioning. The <GNSS_systems> parameter configures the GNSS receiver into the required mode of operation. It is possible to combine different GNSS systems. The combinations of systems, which can be configured simultaneously depends on the receivers capability to receive several carrier frequencies. See the corresponding GNSS receiver Data Sheet for the supported GNSS systems. If the Assisted GNSS unsolicited indication is enabled, the +UUGIND URC will provide the current activated combinations of systems.



of 149


Set AT+UGPS=<mode>[,<aid_mode>[,<GNSS_system>]]]

OK AT+UGPS=1,0,1

OK

Read AT+UGPS? +UGPS : <mode>[,<aid_mode>[,<GNSS_systems>]]

OK

+UGPS: 1,0,1

OK

Test AT+UGPS=? +UGPS: (list of supported <mode>s),(list of supported <aid_mode>),(list of supported <GNSS_systems>)

OK

+UGPS: (0-1),(0-15),(1-127)

OK


<mode> Number 0: (default value): GNSS receiver powered OFF

1: GNSS receiver powered ON

<aid_mode> Number Provides the supported aiding mode; the parameter is mandatory if <mode>=1; except for <mode>=0 all these supported values can be combined together

0: (default value): No aiding

1: Automatic local aiding

2: AssistNow offline

4: AssistNow online

8: AssistNow autonomous

<GNSS_system> Number Supported GNSS types; the parameter is optional and the allowed values can be combined together. The default value is 3 (GPS+SBAS):

1: GPS

2: SBAS

4: Galileo

8: BeiDou

16: IMES (Not currently supported)

32: QZSS

64: GLONASS

To know the allowed combinations of GNSS type for <GNSS_systems> see the corresponding GNSS receiver documentation.

The parameter <GNSS_systems> is displayed in the information text response of the read command only if the connected GNSS receiver supports Multi-GNSS.

Setting AssistNow Autonomous mode will automatically enable LocalAiding.

An error message is provided in the following cases:

o <mode> and <aid_mode> values are out of range

o <mode> is set to 1 without <aid_mode> value

o Attempt to power on GNSS receiver when it is already on, even if the <aid_mode> is different

o Attempt to power off the GNSS receiver when it is already off

o The value of <aid_mode> to be set is equal to the current GNSS aiding mode

o The aiding mode is immediately changed after the first command (“+CME ERROR: GNSS aiding mode already set” if +CMEE=2)



of 149

19.2 Assisted GNSS unsolicited indication +UGIND

19.2.1 Description Enables or disables sending of URCs from MT to TE in the case of GNSS aiding operations. The <mode> parameter controls the processing of URCs specified within this command.

The URC returns the result of an assisted GNSS operation. This information is sent to all the interfaces. Unsolicited information is provided only if one or more aiding modes are enabled (for more details refer to sections 19.4 and 19.5).

There can be more than one URC +UUGIND for a single aiding operation: the +UUGIND is reported for each error. For instance, if the local aiding is enabled and there is no space left in the file system after +UGPS=0, there will be an error for every failure to write on FFS.

The commands +UGAOS=0 and +UGAOS=1 both relate to GNSS local aiding, so the unsolicited message will be +UUGIND=1,x in both cases.

Local aiding and AssistNow Autonomous will produce URC both after GNSS receiver power on and before power off, because some data are transferred from the GNSS receiver to cellular module.

URCs during GNSS receiver power down phase are generated between the power off command (+UGPS=0) and the actual switch off (OK message).


Set AT+UGIND=<mode> OK AT+UGIND=1

OK

Read AT+UGIND? +UGIND: <mode>

OK

+UGIND: 1

OK

Test AT+UGIND=? +UGIND: (list of supported <mode>’s)

OK

+UGIND: (0-1)

OK

URC Current activated GNSS system:

+UUGIND: 0,<GNSS_system>

GNSS aiding status:

+UUGIND: <aid_mode>,<result>

+UUGIND: 0,3

+UUGIND: 4,5


<mode> Number Enable/disable the URC

0 (default value): Disabled

1: Enabled

<aid_mode> Number Provides the supported aiding mode

0: No aiding

1: Automatic local aiding

2: AssistNow offline

4: AssistNow online

8: AssistNow Autonomous



of 149


<GNSS_systems> Number Current activated GNSS types; the allowed values can be combined together:

1: GPS 2: SBAS 4: Galileo 8: BeiDou 16: IMES (not supported) 32: QZSS 64: GLONASS

<result> Number 0: No error 1: Wrong URL (for AssistNow Offline) 2: HTTP error (for AssistNow Offline) 3: Create socket error (for AssistNow Online) 4: Close socket error (for AssistNow Online) 5: Write to socket error (for AssistNow Online) 6: Read from socket error (for AssistNow Online) 7: Connection/DNS error (for AssistNow Online) 8: File system error 9: Generic error 10: No answer from GPS receiver (for local aiding and AssistNow Autonomous) 11: Data collection in progress (for local aiding) 12: GPS configuration failed (for AssistNow Autonomous) 13: RTC calibration failed (for local aiding) 14: feature not supported (for AssistNow Autonomous) 15: feature partially supported (for AssistNow Autonomous) 16: authentication token missing (required for aiding for u-blox M8 and future versions)

URCs for GNSS_systems are the union of requested systems and actual available systems received by the GNSS receiver.

Setting AssistNow Autonomous mode with +UGPS will automatically enable LocalAiding. Therefore, AssistNow Autonomous mode will trigger an additional URC, +UUGIND:1,0

19.3 GNSS Profile configuration +UGPRF

19.3.1 Description The +UGPRF command configures the data flow to and from a u-blox GNSS receiver connected to the cellular module. Data flow is possible to and from the GNSS receiver in these ways:

• Via UART (via multiplexer)

• Via USB (not Supported on LISA C-200)

• Over the air to a remote host. To send data over the air, a data connection using UDP socket shall be setup automatically.

• Into a file on the cellular module. A file with GNSS data can be accessed via +ULSTFILE command. The file name is automatically chosen by the cellular module based on date and time with a further incremental number (e.g. “GPS_20091006_001”). When the file size reaches 500 kB, the file is closed and no more data is saved. It is possible to save further data by restarting the GNSS receiver (this will create a new file)

It is possible to send GNSS data to multiple destinations at the same time by summing the <GPS_I/O_configuration> values of each required destinations (e.g. if AT+UGPRF=6 the data will be sent on multiplexer and stored in a file in the file system).

The messages to be output by the u-blox GNSS receiver need to be activated separately with UBX-CFG-MSG configuration messages according to the u-blox 5 and u-blox 6 Protocol Specification [42].



of 149

The configuration of the GNSS profile must be performed only when the GNSS receiver is switched off, otherwise an error message will be displayed.

<GPS_I/O_configuration>=1(USB) and 32(RTC Sharing) are not available on LISA C-200.

After issuing an AT+UGPRF Set command, client should reset modem for the settings to take effect


Set AT+UGPRF=<GPS_I/O_configuration>[,<IP Port>,<server address string>]

OK AT+UGPRF=0

OK

Read AT+UGPRF? +UGPRF: <GPS_I/O_configuration>,<IP port>,<server address string>

OK

+UGPRF: 0,0,””

OK

Test AT+UGPRF=? +UGPRF: (list of supported <GPS_I/O_configuration>),(list of supported <IP port>),<server address string>

OK

+UGPRF: (0-63),(0-65535),”addr”

OK


<GPS_IO_configuration> Number 0 (default value): no data flow to multiplexer, file or IP address 1: GNSS data flow to and from USB (note: UBX-AID messages filtered out) 2: GNSS data flow to and from multiplexer (note: UBX-AID messages filtered out) 4: GNSS data flow saved to file (note: no filtering) 8: GNSS data flow over the air to an Internet host (note: no filtering) 16: GNSS Tx data ready feature 32: RTC sharing

<IP port> Number IP port of the server where the GNSS data are sent (default value: 0). If GNSS data flow over the air is enabled, then the parameter is mandatory, and otherwise it is forbidden.

<server address string> String Address string of the server where the GNSS data are sent (default value: “”). If GNSS data flow over the air is enabled, then the parameter is mandatory, and otherwise it is forbidden.

UBX-AID messages are not passed over the multiplexer if AssistNow Online, AssistNow Online or Local Aiding is enabled (see AT+UGPS, section 19.1).

19.4 AssistNow Online configuration +UGAOP

19.4.1 Description The +UGAOP command configures the network connection to an AssistNow Online server. Use of this command is only necessary if changes to the factory-programmed configuration are required.

AssistNow Online server is accessed with the User Datagram Protocol (UDP). The GNSS receiver shares the socket pool with the other applications. To execute AssistNow, the cellular module will try to open a new socket without dropping any open socket. If there is no socket available then the GNSS receiver will start and no aiding operation is performed. By default, the cellular module connects to u-blox’ AssistNow Online server. Authentification on u-blox’ AssistNow Online server is done automatically (without giving u-blox any information that could be used to identify the customer and/or end user); user name and passwords are not required. Access to a proxy server is possible.

Three different modes of operation are supported:



of 149

• AssistNow Online data are automatically downloaded from the server when the GNSS receiver is started up (i.e. with command +UGPS and <GPS mode>=1 and <aid_mode>=4)

• AssistNow Online data are only requested upon the reception of a +UGAOS AT command

• AssistNow Online data are kept alive. This is done by periodically (every 2 hours) accessing the AssistNow Online to keep the ephemeris alive.

Where supported, it is preferred to use the +UGSRV AT command.

If AssistNow Online is not configured with this command, then the following settings will be assumed:

o <hostname>: “eval1-cdmales.services.u-blox.com”

o <server port>: 46434

o <latency>: 1000 ms

o <mode>: 0


Set AT+UGAOP=<hostname>,<server port>,<latency>,<mode>

OK AT+UGAOP=”eval1-cdmales.services.u-blox.com”,46434,1000,0

OK

Read AT+UGAOP? +UGAOP: <hostname>,<server port>,<latency>,<mode>

OK

+UGAOP: “eval1-les.services.u-blox.com”,46434,1000,0

OK


<hostname> String Host name of the server (i.e. eval1-cdmales.services.u-blox.com); (max length 47 characters)

<server port> Number Value in the range 0 – 65535. (default value: 46434)

<latency> Number Expected network latency value from Assist now Online server to client, in seconds. Range goes from 0 to 10000 ms. (default: 1000 ms)

<mode> Number 0 (default value): AssistNow Online data is downloaded at GNSS receiver power up 1: AssistNow Online data automatically kept alive 2: Manual AssistNow Online data download

19.5 AssistNow Offline configuration +UGAOF

19.5.1 Description Configures the network connection to an AssistNow Offline server. Use of this command is only necessary if changes to the factory-programmed configuration are required.

Access to an AssistNow Offline server is done with HTTP/1.1. The GNSS receiver shares the socket pool with the other applications, to execute AssistNow Offline the cellular module will try to open a new socket without dropping any open socket, if there is no socket available then the GNSS receiver will start and no aiding operation is performed. By default, the cellular module connects to the 14 day file on the u-blox’ AssistNow Offline server.

Where supported, it is preferred to use the +UGSRV AT command.




of 149


Set AT+UGAOF=<file_url>, <reserved>, <retry timeout>, <max_retry_attempts>

OK AT+UGAOF=”http://alp.u-blox.com/current_14d.alp”,0,1,3

OK

Read AT+UGAOF? +UGAOF: <file_url>, 0, <retry timeout>, <max_retry_attempts>

OK

+UGAOF: “http://alp.u-blox.com/current_14d.alp”,0,1,3

OK


<file_url> String URL of AssistNow Offline file (maximum of 255 characters including “http://”). Allows choosing the size/validity of the file. By default, the cellular module connects to http://alp.u-blox.com/current_14d.alp

<Reserved> RFU

<Retry Timeout> Number Timeout in minutes after a failed download for the next download attempt (0 … 999) (default value: 1)

<max_retry_attempts> Number Maximum number of attempts in case of failed download (0-5); default value is 3

19.6 Aiding server configuration +UGSRV

19.6.1 Description Configures the network connection to a Multi GNSS Assistance (MGA) server. These parameters are saved in NVM and are applied at the next GNSS power cycle. The MGA server is accessed with the HTTP. The GNSS shares the socket pool with the other applications, to execute AssistNow the cellular module will try to open a new socket without dropping any opened socket, if there is no socket available then the GNSS will start and no aiding operation is performed. By default, the cellular module connects to u-blox' primary MGA server; if the connection fails then the cellular module connects to u-blox's secondary MGA server. Authorization tokens are used as a means of authorizing access to the u-blox services and for gathering anonymous statistics. To obtain a token, customers should use the form in http://www.u-blox.com/services-form.html.


Set AT+UGSRV=<mga_primary_server>,[<mga_secondary_server>],<auth_token>[,<days>[,<period>[,<resolution>[,<GNSS_types>[,<mode>[,<datatype>]]]]]]

OK AT+UGSRV="cell-live1.services.ublox.com","cell-live2.services.ublox.com","123456789abcdefghijklm",14,4,1,65,0,1

OK

Read AT+UGSRV? +UGSRV: <mga_primary_server>,<mga_secondary_server>,<auth_token>,<days>,<period>,<resolution>,<GNSS_types>,<mode>,<datatype>

OK

+UGSRV: "cell-live1.services.ublox.com","cell-live2.services.ublox.com","123456789abcdefghijklm",14,4,1,65,0,1

OK

http://alp.u-blox.com/current_14d.alp



of 149


Test AT+UGSRV=? +UGSRV: <mga_primary_server>,<mga_secondary_server>,<auth_token>,(list of supported <days>s),(list of supported <period>s),(list of supported <resolution>s),(list of supported <GNSS_types>s),(list of supported <mode>s),(list of supported <datatype>s)

OK

+UGSRV: "srv1","srv2","token",(1,2,3,5,7,10,14),(1-5),(1-3),(1,64,65),(0-2),(0-15)

OK


<mga_primary_server> String Host name of the primary u-blox M8 server; the maximum length is 255 characters. The default and factory-programmed value is "cell-live1.services.u-blox.com"

<mga_secondary_

server>

String Host name of the secondary u-blox M8 server; the maximum length is 255 characters. The default and factory-programmed value is "cell-live2.services.u-blox.com"

<auth_token> String Authentication Token for u-blox M8 server access

<days> Number The number of days into the future the Offline data for u-blox 7 and previous version should be valid for. The allowed values are: 1, 2, 3, 5, 7, 10 and 14. The default and factory programmed value is 14

<period> Number The number of weeks into the future the Offline data for u-blox M8 should be valid for. The range of the allowed values goes from 1 to 5. The default and factory-programmed value is 4

<resolution> Number The resolution of offline data for u-blox M8

1 (default and factory-programmed value): every day 2: every other day 3: every third day

<GNSS_types> Number Bitmask for combining the desired GNSS for the (offline) aiding

1: GPS 64: GLONASS

The default and factory-programmed value is all (65)

<mode> Number Mode of operation of AssistNow Online data management

0 (default and factory-programmed value): AssistNow Online data are downloaded at GNSS receiver power up 1: AssistNow Online data automatically kept alive 2: manual AssistNow Online data download

<datatype> Number Bitmask for combining the desired data types for the (online) aiding

0: time 1: position 2: ephemeris 4: almanac 8: auxiliary

The default and factory-programmed value is all (15)



of 149

19.7 GNSS Aiding request command +UGAOS

19.7.1 Description Triggers manual download of AssistNow Online and AssistNow Offline data from the configured server in case automatic AssistNow operation is not enabled (see +UGAOF for AssistNow Offline and +UGAOP for AssistNow Online). The command returns only when the received data from the server are valid or an error occurs.

The command is also used to trigger manual upload of local aiding data (e.g. ephemeris, almanac, last position, time, etc) from a u-blox GNSS receiver prior to shutting it down and to restore it into the receiver after the power up of the GNSS receiver (for more details refer to command +UGPS, section 19.1).


Set AT+UGAOS=<aid_mode> OK AT+UGAOS=0

OK

Test AT+UGAOS=? AT+UGAOS: (list of supported <aid_mode>s)

OK

+UGAOS: (0-8)

OK


<aid_mode> Number 0: Upload of local aiding data from GNSS receiver to cellular module; 1: Download of local aiding data from cellular module to GNSS receiver; 2: AssistNow Offline file download request (file loaded into cellular module); 4: AssistNow Online data download request (data loaded into GNSS receiver). This is only needed if AssistNow Online is not used with automatic operation; 8: AssistNow autonomous

Other values are reserved for future use.

19.8 Send of UBX string +UGUBX

19.8.1 Description Sends UBX protocol messages, embedded in an AT command, to a u-blox GNSS receiver. The +UGUBX command is transparent, that is the data is sent to the GNSS receiver without any check: it is up to the user to control if the UBX data is valid. The checksum in +UGUBX command string is ignored, this is calculated when data is sent to the GNSS receiver.

When the GNSS receiver is off or used for hybrid positioning the UBX string is saved in RAM and, later, passed to the GNSS receiver for TX data ready configuration when the GNSS receiver is used. This message is used only if the GNSS receiver HW is unknown (newer than the cellular module FW).


Set AT+UGUBX=<UBX String> +UGUBX: <UBX String response>

OK

AT+UGUBX=“B56206010800010600010000000017DA“

+UGUBX: „B5620501020006010F38“

OK



of 149


<UBX String> String UBX message in hexadecimal format. The messages can include spaces to simplify copy/paste from u-center separated with spaces, e.g. AT+UGUBX=”B5 62 06 01 08 00 01 06 00 01 00 00 00 00 17 DA” (this is important when copying messages from u-center). The maximum length of <UBX string> is 110 bytes (spaces included)

<UBX String response> String The response message depends by the request sent: query/poll UBX messages will return the requested data in hexadecimal format, while configuration message will return the corresponding acknowledge or not-acknowledge. Refer to UBX protocol specification [42]

If a +UGUBX command triggers multiple strings answer only a single UBX string is returned. E. g. polling GNSS Aiding Ephemeris Data (AID-EPH) is done by sending a single message to the receiver but returns 32 messages; only the first one is sent to AT interface.

With LISA C-200 modules the command can only be used when the GNSS receiver is used from the AT interface (power on by AT+UGPS=1,x).

19.9 GNSS Indications timer +UGTMR

19.9.1 Description Sets date and time format. With <time zone> parameter is possible to set the time zone value; the time and the date will be updated as the local time; the factory-programmed time zone value is 0.


Action AT+UGTMR OK AT+UGTMR

OK

Set AT+UGTMR=<time zone> OK AT+UGTMR=-1

OK

Read AT+UGTMR? +UGTMR: <time zone>

OK

+UGTMR: -1

OK

Test AT+UGTMR=? +UGTMR: (list of supported <time zone>s)

OK

+UGTMR: (-96 – 96)

OK


<time zone> Number Indicates the time zone value set by the user; the data module can provide an error message if the offset has not been calculated (default value: 0)

-96, 96: defined range

The time zone is expressed in quarters of hour.

The time is updated with the current UTC time plus the time zone and the time zone is unchanged, for example:

Command Response

AT+UGTMR=-36 OK

AT+CCLK? +CCLK: “12/05/23,21:54:21+00”



of 149

The command returns “OK” and sets the new date and time if the GNSS receiver has this information, otherwise a generic “ERROR” is returned.

19.10 Get GNSS Time and date +UGZDA

19.10.1 Description Enables/disables storing of the last value of NMEA $ZDA messages, and get the current messaging state. If <state> parameter is enabled, the last value of NMEA $ZDA messages can be retrieved with the read command even when the GNSS receiver is switched off.

The NMEA $ZDA messages are volatile.


Set AT+UGZDA=<state> OK AT+UGZDA=1

OK

Read AT+UGZDA? +UGZDA: <state>,<$ZDA msg>

OK

+UGZDA: 1,Not available

OK

+UGZDA: 0,NULL

OK

Test AT+UGZDA=? +UGZDA: (list of supported <state>s)

OK

+UGZDA: (0-1)

OK


<state> Number 0 (default value): disable the NMEA $ZDA messages 1: enable the NMEA $ZDA messages

<$ZDA msg> String NMEA $ZDA messages. If the parameter value is “Not available” then the NMEA string is enabled but this information has not been still sent to the user.

If <$ZDA msg> value is “Not Available”, check that the GNSS ZDA message is enabled. To enable it use the +UGUBX command (for further information see the UBX-CFG-MSG message in the u-blox 6 Receiver Description Including Protocol Specification [42]).

19.11 Get GNSS fix data +UGGGA

19.11.1 Description Enables/disables storing of the last value of NMEA $GGA messages, and gets the current messaging state. If <state> parameter is enabled, the last value of NMEA $GGA messages can be retrieved with the read command even when the GNSS receiver is switched off.

The NMEA $GGA messages are volatile.


Set AT+UGGGA=<state> OK AT+UGGGA=1

OK



of 149


Read AT+UGGGA? +UGGGA: <state>,<$GGA msg>

OK

+UGGGA: 1,Not available

OK

+UGGGA: 0,NULL

OK

Test AT+UGGGA=? +UGGGA: (list of supported <state>s)

OK

+UGGGA: (0-1)

OK


<state> Number 0 (default value): to disable the NMEA $GGA messages 1: to enable the NMEA $GGA messages

<$GGA msg> String NMEA $GGA messages. If the parameter value is “Not available” then the NMEA string is enabled but this information has not been still sent to the user.

If <$GGA msg> is “Not Available” check that the GNSS GGA message is enabled. To enable it use the +UGUBX command (for further information see the UBX-CFG-MSG message in the u-blox 6 Receiver Description Including Protocol Specification [42]).

19.12 Get geographic position +UGGLL

19.12.1 Description Enables/disables storing of the last value of NMEA $GLL messages, and gets the current messaging state. If <state> parameter is enabled, the last value of NMEA $GLL messages can be retrieved with the read command even when the GNSS receiver is switched off.

The NMEA $GLL messages are volatile.


Set AT+UGGLL=<state> OK AT+UGGLL=1

OK

Read AT+UGGLL? +UGGLL: <state>,<$GLL msg>

OK

+UGGLL: 1,Not available

OK

+UGGLL: 0,NULL

OK

Test AT+UGGLL=? +UGGLL: (list of supported <state>s)

OK

+UGGLL: (0-1)

OK


<state> Number 0 (default value): to disable the NMEA $GLL messages 1: to enable the NMEA $GLL messages

<$GLL msg> String NMEA $GLL messages. If the parameter value is “Not available” then the NMEA string is enabled but this information has not been still sent to the user.



of 149

If <$GLL msg> is “Not Available” check that the GNSS GLL message is enabled. To enable it use the +UGUBX command (for further information see the UBX-CFG-MSG message in the u-blox 6 Receiver Description Including Protocol Specification [42]).

19.13 Get number of GNSS satellites in view +UGGSV

19.13.1 Description Enable/disables the storing of the last value of NMEA $GSV messages, and gets the current messaging state. If <state> parameter is enabled, the last value of NMEA $GSV messages can be retrieved with the read command even when the GNSS receiver is switched off.

The NMEA $GSV messages are volatile.


Set AT+UGGSV=<state> OK AT+UGGSV=1

OK

Read AT+UGGSV? +UGGSV: <state>, <$GSV msg>

OK

+UGGSV: 1, 1,$GPGSV,3,1,11,03,67,298,22,06,88,149,29,07,06,302,,08,05,332,25*73

$GPGSV,3,2,11,09,02,334,25,14,02,141,15,10,041,43,16,46,209,16*7D

$GPGSV,3,3,11,18,48,066,35,21,26,070,35,27,80,314,25*40

$GLGSV,1,1,03,73,13,248,,74,23,298,0,75,09,348,19*51

OK

+UGGSV: 0,NULL

OK

Test AT+UGGSV=? +UGGSV: (list of supported <state>s)

OK

+UGGSV: (0-1)

OK


<state> Number 0 (default value): to disable the NMEA $GSV messages 1: to enable the NMEA $GSV messages

<$GSV msg> String NMEA $GSV messages. If the parameter value is “Not available” then the NMEA string is enabled but this information has not been still sent to the user.

If <$GSV msg> is “Not Available” check that the GNSS GSV message is enabled. To enable it use the +UGUBX command (for further information see the UBX-CFG-MSG message in the u-blox 6 Receiver Description Including Protocol Specification [42]).



of 149

19.14 Get recommended minimum GNSS data +UGRMC

19.14.1 Description Enable/disables storing of the last value of NMEA $RMC messages, and gets the current messaging state. If <state> parameter is enabled, the last value of NMEA $RMC messages can be retrieved with the read command even when the GNSS receiver is switched off.

The NMEA $RMC messages are volatile.


Set AT+UGRMC=<state> OK AT+UGRMC=1

OK

Read AT+UGRMC? +UGRMC: <state>,<$RMC msg>

OK

+UGRMC: 1,1,$GPRMC,142351.00,V,,,,,,,121213,,,N*7F

OK

+UGRMC: 0,NULL

OK

Test AT+UGRMC=? +UGRMC: (list of supported <state>s)

OK

+UGRMC: (0-1)

OK


<state> Number 0 (default value): to disable the NMEA $RMC messages 1: to enable the NMEA $RMC messages

<$RMC msg> String NMEA $RMC messages. If the parameter value is “Not available” then the NMEA string is enabled but this information has not been still sent to the user.

If <$RMC msg> is “Not Available” check that the GNSS RMC message is enabled. To enable it use the +UGUBX command (for further information see the UBX-CFG-MSG message in the u-blox 6 Receiver Description Including Protocol Specification [42]).

19.15 Get course over ground and ground speed +UGVTG

19.15.1 Description Enables/disables storing of the last value of NMEA $VTG messages, and gets know the current messaging state. If <state> parameter is enabled, the last value of NMEA $VTG messages can be retrieved with the read command even when the GNSS receiver is switched off.

The NMEA $VTG messages are volatile.


Set AT+UGVTG=<state> OK AT+UGVTG=1

OK



of 149


Read AT+UGVTG? +UGVTG: <state>,<$VTG msg>

OK

+UGVTG: 1, $GPVTG,,,,,,,,,N*30

OK

+UGVTG: 0,NULL

OK

Test AT+UGVTG=? +UGVTG: (list of supported <state>s)

OK

+UGVTG: (0-1)

OK


<state> Number 0 (default value): to disable the NMEA $VTG messages 1: to enable the NMEA $VTG messages

<$VTG msg> String NMEA $VTG messages. If the parameter value is “Not available” then the NMEA string is enabled but this information has not been still sent to the user.

If <$VTG msg> is “Not Available” check that the GNSS VTG message is enabled. To enable it use the +UGUBX command (for further information see the UBX-CFG-MSG message in the u-blox 6 Receiver Description Including Protocol Specification [42]).

19.16 Get satellite information +UGGSA

19.16.1 Description Enables/disables storing of the last value of NMEA $GSA messages, and gets the current messaging state. If <state> parameter is enabled, the last value of NMEA $GSA messages can be retrieved with the read command even when the GNSS receiver is switched off.

The NMEA $GSA messages are volatile.


Set AT+UGGSA=<state> OK AT+UGGSA=1

OK

Read AT+UGGSA? +UGGSA: <state>,<$VTG msg>

OK

+UGGSA: 1,$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30

OK

+UGGSA: 0,NULL

OK

Test AT+UGGSA=? +UGGSA: (list of supported <state>s)

OK

+UGGSA: (0-1)

OK



of 149


<state> Number 0 (default value): to disable the NMEA $GSA messages 1: to enable the NMEA $GSA messages

<$GSA msg> String NMEA $GSA messages. If the parameter value is “Not available” then the NMEA string is enabled but this information has not been still sent to the user.

If <$GSA msg> is “Not Available” check that the GNSS GSA message is enabled. To enable it use the +UGUBX command (for further information see the UBX-CFG-MSG message in the u-blox 6 Receiver Description Including Protocol Specification [42]).

19.17 Ask for localization information +ULOC

19.17.1 Description Requests cellular module to provide the location data; the location can be determined using:

• GNSS receiver • CellLocate® (location based on network cells data) • Combination of both technologies (hybrid)

The result code indicates if sending the command request to the localization information process was successful or not. The URC is issued to provide the requested information via +ULOC set command.

The GNSS interface and CellLocate® can be used at the same time: if the GNSS sensor is reserved to another interface an error message is provided (error code "+CME ERROR: GPS busy"if +CMEE=2).

It is possible to configure the Hybrid Positioning through +ULOCGNSS and +ULOCCELL AT commands even if it is running: the parameters are stored in NVM and will be applied at the next +ULOC command.

If +ULOC command is sent while a previous +ULOC activity is still in progress the previous activity is aborted, the available position is immediately output and the next +ULOC request is served.

The data connection cannot be immediately dropped at the +ULOC timeout expiration. This could lead to a delay in the expected response time.

Depending on the aiding chosen, a data connection could be required; refer to AT+UGPS command description.

If no position is available (no GNSS coverage, no network information and no previous data available) then <lat> latitude and <long> longitude will be set to '0'.

If the previous position degradated by the elapsed time satisfies the desired accuracy then the sensor '0' is reported in the answer.


Set AT+ULOC=<mode>,<sensor>,<response_type>,<timeout>,<accuracy>[,<reserved>]

OK AT+ULOC=2,3,0,120,1

OK

Read AT+ULOC? +ULOC: <mode>,<sensor>,<response_type>,<timeout>,<accuracy>,0

OK

+ULOC: 2,3,1,0,20,0

OK



of 149


Test AT+ULOC=? +ULOC: (list of supported <mode>s),(list of supported <sensor>s),(list of supported <response_type>s),(list of supported <timeout>s),(list of supported<accuracy>s),(0)

OK

+ULOC: (0-2),(0-3),(0,1,255),(1-999),(0-999999),(0)

OK

URC If <response_type>=0:

+UULOC: <date>,<time>,<lat>,<long>,<alt>,<uncertainty>

If <response_type>=1:

+UULOC: <date>,<time>,<lat>,<long>,<alt>,<uncertainty>,<speed>,<direction>,<vertical_acc>,<sensor_used>,<SV_used>,<antenna_status>,<jamming_status>


+UULOC: 13/04/2011,09:54:51.000,45.6334520,13.0618620,49,1


+UULOC: 25/09/2013,10:13:29.000,45.7140971,13.7409172,266,17,0,0,1,1,6,3,9


<mode> Number 0: reserved 1: reserved 2: single shot position

<sensor> Number Sensor selection: it is possible to combine different sensors summing <sensor> values of the selected sensors

0: use the last fix in the internal database and stop the GNSS receiver 1: use the GNSS receiver for localization 2: use CellLocate® location information

<response_type> Number Type of response

0: standard response 1: detailed response 255: reserved

<timeout> Number Timeout period in seconds (1 - 999)

<accuracy> Number Target accuracy in meters (1 - 999999)

<reserved> Number The value is ignored

<date> String GPS date(1) (DD/MM/YY) of the estimated position

<time> String GPS time(1) (hh:mm:ss.sss) of the estimated position

<lat> String Estimated latitude expressed in degrees

<long> String Estimated longitude expressed in degrees

<alt> Number Estimated altitude expressed in meters(2)

<uncertainty> Number Maximum possible error expressed in meters (0 - 20000000)

<speed> Number Speed over ground m/s(2)

<direction> Number Course over ground in degree (0 deg - 360 deg) (2)

<vertical_acc> Number Vertical accuracy expressed in meters(2)

<sensor_used> Number Sensor used for position calculation

<SV_used> Number Number of satellite used to calculate the position(2)

<antenna_status> Number Antenna status (0 - 4) (2). For more details refer to u-blox GNSS receiver protocol



of 149


specification

<jamming_status> Number Jamming status(2). For more details refer to u-blox GNSS receiver protocol specification

1. Coming either from the CellLocate® server (GPS) or the satellites (UTC)

2. only for GNSS positioning, 0 in case of CellLocate®

To enable SBAS system opportunely configure both <SBAS> and <GNSS_systems> parameters.

If a parameter is omitted, the current set value is kept.

For more details on parameter description see the corresponding u-blox-GNSS Receiver Description.

The factory-programmed value of <GNSS_systems> is 0.

19.18 Configure GNSS sensor +ULOCGNSS

19.18.1 Description Configures the GNSS sensor used with the +ULOC command.


Set AT+ULOCGNSS=<aiding>[,<psv_mode>[,<minSV>[,<minCNO>[,<ini_3d_fix>[,<staticHoldMode>[,<SBAS>[,<jamming>[,<antenna>[,<BBthreshold>[,<CWthreshold>[,<GNSS_system>[,<reserved1>[,<reserved2>]]]]]]]]]]]]]

OK AT+ULOCGNSS=15

OK

Read AT+ULOCGNSS? +ULOCGNSS: <aiding>,<psv_mode>,<minSV>,<minCNO>,<ini_3d_fix>,<staticHoldMode>,<SBAS>,<jamming>,<antenna>,<BBthreshold>,<CWthreshold>,<GNSS_system>,<reserved1>,<reserved2>

OK

+ULOCGNSS: 15,1,6,8,0,1,1,1,1,1,1,0,0,0

OK

Test AT+ULOCGNSS=? +ULOCGNSS: (list of supported <aiding>),(list of supported <psv_mode>),(list of supported <minSV>),(list of supported <minCNO>),(list of supported <ini_3d_fix>),(list of supported <staticHoldMode>),(list of supported <SBAS>),(list of supported <jamming>),(list of supported <antenna>),(list of supported <BBthreshold>),(list of supported <CWthreshold>),(list of supported <GNSS_system>),(0),(0)

OK

+ULOCGNSS: (0-15),(0-1),(3-32),(0-50),(0-1),(0-1000),(0-1),(0-1),(0-2),(0-15),(0-31),(1-127),(0),(0)

OK


<aiding> Number GNSS aiding mode configuration; it is possible the combination of different aiding modes: to enable more aiding modes it is needed to sum the <mode> value of the



of 149


interested aiding modes:

1: local aiding (including RTC sharing) 2: AssistNow Offline 4: AssistNow Online 8: AssistNow Autonomous

All the modes (15) are enabled as a factory programmed setting.

<psv_modr> Number Power Save Mode (UBX-CFG-PM2):

0 (factory-programmed value): disabled 1: enabled

<minSV> Number Minimum number of satellites for navigation (UBX-CFG-NAVX5). The range goes from 3 to 32. (factory-programmed value: 3)

<minCNO> Number Minimum satellite signal level for navigation (UBX-CFG-NAVX5). The range goes from 0 to 50. (factory-programmed value: 7)

<in_3d_fix> Number Initial Fix must be 3D flag (UBX-CFG-NAVX5):


<staticHoldMode> Number Static Hold Mode (UBX-CFG-NAV5). The range goes from 0 to 1.000 cm/s. (factory programmed value: 0)

<SBAS> Number SBAS configuration:


<jamming> Number Jamming indicator (UBX-CFG-ITFM):


<antenna> Number Antenna setting:

0 (factory-programmed value): unknown 1: passive 2: active

<BBthreshold> Number Broadband jamming detection threshold (dB) (UBX-CFG- ITFM). The range goes from 0 to 15. (factory programmed value: 0)

<CWthreshold> Number Continuous wave jamming detection threshold (dB) (UBX-CFG- ITFM). The range goes from 0 to 31. (factory programmed value: 0)

<GNSS_system> Number Supported GNSS types; the parameter is optional, the allowed values can be combined together:

1 (factory-programmed value): GPS 2: SBAS 4: Galileo 8: BeiDou 16: IMES (not supported) 32: QZSS 64: GLONASS

<reserved> Number 0 (reserved value)

<reserved> Number 0 (reserved value)



of 149

19.19 Configure cellular location sensor (CellLocate®) +ULOCCELL

19.19.1 Description Configures the Cellular location sensor (CellLocate®) used with the +ULOC command.

This command influences the amount of data exchanged with the server.


Set AT+ULOCCELL=<scan_mode>[,<reserved1>[,<reserved2>[,<reserved3>[,<reserved4>[,<reserved5>]]]]]

OK AT+ULOCCELL=0

OK

Read AT+ULOCCELL? +ULOCCELL: <scan_mode>,<reserved1>,<reserved2>,<reserved3>,<reserved4>,<reserved5>

OK

+ULOCCELL: 0,0,"","",0,0

OK

Test AT+ULOCCELL=? +ULOCCELL: (list of supported <scan_mode>s),(list of supported <reserved1>),(list of supported <reserved2>),(list of supported <reserved3>),(list of supported <reserved4>),(list of supported <reserved5>)

OK

+ULOCCELL: (0-1),(0),"","",(0),(0)

OK


<scan_mode> Number Network scan mode

0 (factory-programmed value): normal 1: deep scan

<reserved1> Number RFU

<reserved2> String RFU

<reserved3> String "" (reserved value)

<reserved4> Number 0 (reserved value)

<reserved5> Number 0 (reserved value)



of 149

19.20 Get Base Station LAT/LONG +UBSLOC

19.20.1 Description This command returns the current base stations BSID and lat/long information (if available). Currently, only Sprint base stations provide this information. In the case that no lat/long information is available, the command will return the BSID followed by two zeros.


Read AT+USBLOC? +UBSLOC: <BS_ID>,<BS_LAT>,<BS_LONG>,<BS_Current>

OK

+UBSLOC: 4631,476301,6700441,1

OK

+UBSLOC: 13571,0,0,1

OK

Test AT+ USBLOC=? +UBSLOC: <BS I D>,<BS LAT>,<BS LONG>,<BS Current?>

OK


<BS ID> Number Base station ID

<BS LAT> Number Base station latitude in units of 0.25 seconds.

<BS LONG> Number Base station longitude in units of 0.25 seconds.

<BS Current> Number 0: Last base station information not current 1: Last base station information current


UBX-13000621 - R10 Production Information Specific

of 149

20 Specific

20.1 Change data connection settings +UDCONF

20.1.1 Description This command allows changing advanced data configuration settings. It is used to enable/disable the HEX mode for sockets operation. Type Syntax Response Example

Set AT+UDCONF=<param_tag>,<param1>,[ <param2>]

OK AT+UDCONF=1,0

OK

Get AT+UDCONF=<param_tag> +UDCONF: <param_tag>,<param1> AT+UDCONF=1

+UDCONF: 1,0

OK


<param_tag> Number 1: Enable/Disable HEX mode for +USOWR, +USOST, +USORD and +USORF commands; <param1> may be:

• 0: HEX mode disabled (default) • 1: HEX mode enabled

2: UDP Direct Link packet size:

• <param1>: socket identifier • <param2>: packet size for UDP direct link (in bytes), range 100-1472,

default 1024 bytes 3: UDP Direct Link sending timer:

• <param1>: socket identifier • <param2>: sending timer timeout (in milliseconds) range 100-

120000, default 1000 ms

20.2 Start and stop tone generation +UVTS

20.2.1 Description Starts and stops DTMF tones. This command may only be used during an active voice call.


Set AT+UVTS=[<DTMF>] OK AT+UVTS= 2

OK

Test AT+UVTS=? +UVTS: (list of supported <DTMF>s)

OK

+UVTS: (0-9,#,*)

OK

When <DTMF> parameter is omitted the tone is stopped.


<DTMF> Number String of ACII characters in the set 0-9, #, *.



of 149

If the command is invoked when not in a call, an error is reported (“CME ERROR: no connection to phone” if +CMEE is set to 2).

20.3 Transmit and Receive States +UTEST

20.3.1 Description The +UTEST AT command gives the user a simple interface to set the cellular module to transmitting and receiving states ignoring cellular signaling protocol. When the +UTEST interface is activated the module is temporally set to test mode.

The usage of this command shall be restricted to controlled (shielded chamber/box) environments and for test purpose only. Improper usage of this command on real network could disturb other users and the network itself.

20.3.2 AT+UTEST=0 This command is only available in non-signaling mode. Send the AT+UTEST=0 command after terminating the testing procedure. This command allows the module to enter normal mode and closes the test interface. The module must be reset after issuing the AT+UTEST=0 command. Type Syntax Response Example

Set AT+UTEST=<Mode> OK AT+UTEST= 0

OK

Read AT+UTEST? +UTEST: <Mode>

OK

+UTEST: 0

OK

Test AT+UTEST=? +UTEST<list of supported <Mode>s)

OK

+UTEST: (0-3)

OK

20.3.3 AT+UTEST=1 This command allows the module to enter non signaling mode. All other +UTEST command modes are only available in non-signaling mode. Type Syntax Response Example

Set AT+UTEST=<Mode> OK AT+UTEST= 1

OK


OK

+UTEST: 1

OK

Test AT+UTEST=? +UTEST:(list of supported <Mode>s)

OK

+UTEST: (0-3)

OK

20.3.4 AT+UTEST=2 Measuring received power level can be done using this command syntax


Set AT+UTEST=<Mode>,<par1><par2>,<par3>

+UTEST:<par1>,<par2>,<par3>,<min>,<avg>,<max>

OK

AT+UTEST=2,32,5000,5

+UTEST : 32,5000,5,-80,-80,-80

OK


OK

+UTEST: 2

OK



of 149



OK

+UTEST: (0-3)

OK

20.3.4.1 Defined Values

Parameter Description Range Default Notes

<par1> Channel Band Class 0:

[1 - 777 , 1013 - 1023]

Band Class 1:

[25 - 1175]

32

<par2> Time 1 - 600000 1000 Time interval expressed in ms

<par3> Band Class 0-4: Reserved

5: Band Class 0

6: Band Class 1

5 Band Class 0: CDMA800

Band Class 1: CDMA1900

<min> Minimum antenna RF level estimation -30 : -110 dBm - Expressed in dBm

<avg> Average antenna RF level estimation -30 : -110 dBm - Expressed in dBm

<max> Max antenna RF level estimation -30 : -110 dBm - Expressed in dBm

20.3.4.2 Example

RX mode test command example

Command Response Description

AT+UTEST=2,32,5000,6 +UTEST:32,5000,5,-80,-80,-80

OK

The module measures the antenna RX level at RX channel 32, FTM Mode 6 (1900 MHz) for 5 s interval. After this time the module provides the response.

In the example -80,-80,-80 are the antenna RF level estimation: the numbers are just an example

AT+UTEST=2,384,1000 +UTEST:384,1000,5,-80,-80,-80

OK

The module measures the antenna RX level at RX channel 384, FTM Mode 5 (800 MHz) for 1 s interval. After this time the module provides the response.

Band Class parameter is set to 5 by default even without entering. Notice that the URC still shows the Band Class parameter as 5.

In the example -80,-80,-80 are the antenna RF level estimation: the numbers are just an example

20.3.5 AT+UTEST=3 RF signal transmission can be triggered with this command Type Syntax Response Example

Set AT+UTEST=<Mode>,<par1>,<par2>,<par3>,<par4>,<par5>

+UTEST : 3,<par1>,<par2>,<par3>,<par5>

OK

AT+UTEST=3,384,5,5,0,5000

+UTEST : 3,384,5,5,5000

OK


OK

+UTEST: 3

OK



of 149



OK

+UTEST: (0-3)

OK

20.3.5.1 Defined Values

Parameter Description Range Default Notes

<par1> Channel Band Class 0:

[1 - 777 , 1013 - 1023]

Band Class 1:

[25 - 1175]

32

<par2> RF Level -56 to 24 5 Absolute output power expressed in dBm

<par3> FTM Mode 0-4: Reserved

5: FTM Mode 0

6: FTM Mode 1

5 FTM Mode 0: CDMA800

FTM Mode 1: CDMA1900

<par4> Reserved 0 0 Reserved for future use

<par5> Time 0 - 600000 1000 Time interval expressed in ms

0: continuous transmission. In this case the command will immediately return. The command line will Band Class parameter To stop the burst sequence transmission the command AT+UTEST=1 must be provided, any other UTEST commands can be set and transmission will be stopped.

20.3.5.2 Example

TX mode test command examples

Command Response Description

AT+UTEST=3,32,5,5,0,2000 +UTEST:32,5,5,2000

OK

The module will transmit for 2 s interval at TX channel 32 with FTM Mode parameter set to 5 (CDMA800).

AT+UTEST=3,384,5,6,,5000 +UTEST:384,5,6,5000

OK

The module will transmit for 5 s interval at TX channel 384 with FTM Mode parameter set to 6 (CDMA1900).

Currently, UTEST=3 transmit maximum power out id 6dBm.

<par4> is currently reserved for future development, but use of this parameter is mandatory. We should either use the default value which is 0 or use “ , , “ meaning empty value.

After executing the UTEST commands, it is important to put the module back in signaling mode. This can be done by using AT+TEST=0 command. After that, the module has to be rebooted. After the boot up, the module will now be in Signaling Mode.

If in any case, there is an unexpected power down sequence, before AT+UTEST=0 command is issued, in that scenario AT+UTEST=0 should be issued after the module powers up in order to get the module back to signaling mode.

For more detailed information on UTEST, refer to LISA-C200 & FW75-C200 System Integration Manual [44]

20.4 Firmware Update over AT command (FOAT) +UFWUPD

20.4.1 Description This command triggers a firmware update using the Xmodem protocol.



of 149


Set AT+UFWUPD=<filetype> +UFWUPD: ONGOING

OK

AT+ UFWUPD=3

+UFWUPD: ONGOING

OK

Test AT+ UFWUPD =? + UFWUPD: <filetypes> AT+ UFWUPD =?

+ UFWUPD: (0-3)

OK


<filetype> Number 0: unsupported 1: unsupported 2: unsupported 3: CDMA binary file type

The FOAT feature on LISA-C200 modems uses standard Xmodem with checksum error checking to download firmware over UART/USB channels. The user has a 100 second window to begin the file transfer. The timeout is indicated to the user by ten ‘§’ sequences with a 10 second delay.

LISA-C200 modems support binary file type only. The +UFWUPD file type parameter should be set to 3 for binary files. The maximum file size is 1.3MB.



of 149

A Appendix 1

A.1 Networking error class The following table lists all allowed error class that can be provided by the <error_class> parameter for each AT error command (+UFTPER, +UHTTER) for FTP and HTTP. For more details on the command syntax, refer to sections 17.5 and 18.4.

<err> Meaning Resulting from the following commands

0 OK, no error occurred All

1 FTP Protocol error class +UFTP, +UFTPC, +UFTPER

3 HTTP Protocol error class +UHTTP, +UHTTPC, +UHTTER

4 Flash File System error class +UFTPC, +UFTPER, +UHTTPC, +UHTTER

5 DNS error class +UFTPC, +UFTPER, +UHTTPC, +UHTTER

6 Socket error class All

7 Dynamic Memory error All

8 Wrong FTP API usage (e.g. missing/null parameters) +UFTP, +UFTPC, +UFTPER

10 Wrong HTTP API usage (e.g. missing/null parameters) +UHTTP, +UHTTPC, +UHTTER

11 Syntax error in high layer protocol (wrong/missing/corrupted data) +UFTPC, +UFTPER, +UHTTPC, +UHTTER

12 Unspecified error All

A.1.1 FTP error codes The following table lists the available values of <error_code> parameter of the last FTP operation provided through +UFTPER AT command (for more details, refer to the AT commands description in section 17.5).


0 No error +UFTP, +UFTPC

1 User missing +UFTPC

2 Password missing +UFTPC

3 Account missing +UFTPC

4 Server missing +UFTPC

5 Directory name missing +UFTPC

6 File name missing +UFTPC

7 Null parameter +UFTP, +UFTPC

8 Unknown FTP command +UFTP, +UFTPC

9 Unknown file action +UFTPC

10 Wrong FTP state +UFTPC

11 Wrong parameter +UFTP, +UFTPC

12 Connection not established +UFTPC

13 No memory available for allocation +UFTPC, +UFTP

14 Reserved internal code +UFTPC, +UFTP



of 149


15 Length of given web server (address or hostname) too long or too short

+UFTPC, +UFTP

16 Hostname of given web server invalid +UFTPC, +UFTP

17 Address of given web server is invalid +UFTPC, +UFTP

18 Username too long or too short +UFTPC, +UFTP

19 Password too long or too short +UFTPC, +UFTP

20 Account too long or too short +UFTPC, +UFTP

21 Operation not allowed because FTP client is busy +UFTPC

22 Not possible to connect to FTP server +UFTPC

23 Error occurred in FTP request +UFTPC

24 Reserved internal code +UFTPC, +UFTP

25 FFS filename pointer is null or its length is 0 +UFTPC

26-30 Reserved internal code +UFTPC, +UFTP

31 Timeout elapsed while performing requested operation +UFTPC

32 Internal processing error +UFTPC, +UFTP

33 Not logged in +UFTPC

34 Login incorrect +UFTPC

35 File unavailable (not found or no access) +UFTPC

36 File not ready +UFTPC

37 Filename not allowed +UFTPC

38 Folder not found +UFTPC

39 Folder no access +UFTPC

40 Operation aborted by user +UFTPC

41 Permission denied +UFTPC

42 Cannot open FTP data channel +UFTPC

43 Socket invalid parameter +UFTPC

44 Invalid socket +UFTPC

45 No socket available +UFTPC

46 Cannot create socket +UFTPC

47 Cannot bind socket to network interface +UFTPC

48 Cannot resolve hostname +UFTPC

49 Cannot connect socket +UFTPC

50 Cannot get socket name +UFTPC

51 Cannot bind socket to port +UFTPC

52 Socket cannot listen +UFTPC

53 Socket cannot accept +UFTPC

54 Socket would block +UFTPC

55 Socket cannot write +UFTPC

56 Socket cannot read +UFTPC

57 Reserved internal code +UFTPC

58 No socket data to send +UFTPC



of 149


59 Socket cannot get available data +UFTPC

60 No socket data to read +UFTPC

61 Socket no response code found +UFTPC

62 Socket not connected +UFTPC

63 Cannot set secure socket +UFTPC

64 Socket cannot decode password +UFTPC

65 Socket cannot get size +UFTPC

66 FFS Invalid parameter +UFTPC

67 FFS invalid handle +UFTPC

68 FFS cannot open file +UFTPC

69 FFS cannot seek file +UFTPC

70 FFS cannot get file size +UFTPC

71 FFS cannot read +UFTPC

226 Closing data connection; requested file action successful (for example, file transfer or file abort)

+UFTPC

250 Requested file action okay, completed +UFTPC

350 Requested file action pending further information +UFTPC

421 Service not available, closing control connection +UFTPC

425 Cannot open data connection +UFTPC

426 Connection closed; transfer aborted. The command opens a data connection to perform an action, but that action is canceled, and the data connection is closed

+UFTPC

450 Requested file action not taken. File unavailable (e.g., file busy) +UFTPC

451 Requested action aborted: local error in processing +UFTPC

452 Requested action not taken. Insufficient storage space in system +UFTPC

500 Syntax error, command unrecognized, command line too long +UFTPC

501 Syntax error in parameters or arguments +UFTPC

502 Command not implemented +UFTPC

503 Bad sequence of commands +UFTPC

504 Command not implemented for that parameter +UFTPC

530 User not logged in +UFTPC

532 Need account for storing files +UFTPC

550 Requested action not taken. File unavailable, not found, not accessible

+UFTPC

552 Requested file action aborted. Exceeded storage allocation +UFTPC

553 Requested action not taken. File name not allowed +UFTPC



of 149

A.1.2 HTTP error codes The following table lists the available values of <error_code> parameter of the last HTTP operation provided through +UHTTPER AT command (for more details, refer to the AT command description in section 18.4).


0 No error +UHTTP, +UHTTPC

1 Invalid profile ID +UHTTP, +UHTTPC

2 Invalid input +UHTTP, +UHTTPC

3 Server hostname too long +UHTTP

4 Invalid server hostname +UHTTP

5 Invalid server IP address +UHTTP

6 Invalid authorization method +UHTTP

7 Server missing +UHTTPC

8 Username length exceeded +UHTTP

9 Password length exceeded +UHTTP

10 Internal error +UHTTP, +UHTTPC

11 Server connection error +UHTTPC

12 Error occurred in HTTP request +UHTTPC



15 Invalid POST data size +UHTTPC

16 Empty FFS file name +UHTTPC

17 Invalid FFS file length +UHTTPC

18 Invalid content-type specified +UHTTP, +UHTTPC




22 Connection not established +UHTTPC

A.1.3 File System Class error codes The following table lists the available values of <error_code> parameter of the last HTTP operation provided through +UFTPER, +UHTTPER AT commands if the <error_class> is 4 “Flash File System error class” (for more details, refer to the AT command description in sections 17.5 and 18.4).


2 Operation performed with success +UFTPC, +UHTTPC

3 Initialization in progress +UFTPC, +UHTTPC

4 File already opened +UFTPC, +UHTTPC

5 File not opened +UFTPC, +UHTTPC

6 File not found +UFTPC, +UHTTPC

7 File already created +UFTPC, +UHTTPC

8 Illegal id +UFTPC, +UHTTPC



of 149


9 Illegal file handle +UFTPC, +UHTTPC

10 Illegal type +UFTPC, +UHTTPC

11 Illegal mode +UFTPC, +UHTTPC

12 File range error +UFTPC, +UHTTPC

13 The operation is not possible +UFTPC, +UHTTPC

14 Write error +UFTPC, +UHTTPC

15 User id error +UFTPC, +UHTTPC

16 Internal fatal error +UFTPC, +UHTTPC

17 Memory resource error +UFTPC, +UHTTPC

18 Maximum number of files exceeded +UFTPC, +UHTTPC

19 Memory not available +UFTPC, +UHTTPC

20 Invalid filename +UFTPC, +UHTTPC

21 Streaming not enabled +UFTPC, +UHTTPC

22 Operation not allowed on static file +UFTPC, +UHTTPC

23 Memory table inconsistency +UFTPC, +UHTTPC

24 Not a factory default file +UFTPC, +UHTTPC

25 Requested memory temporary not available +UFTPC, +UHTTPC

26 Operation not allowed for a directory +UFTPC, +UHTTPC

27 Space in the directory space not available +UFTPC, +UHTTPC

28 Too many streaming files opened +UFTPC, +UHTTPC

29 Requested dynamic memory temporary not available +UFTPC, +UHTTPC

30 The user provided a NULL parameter instead of a suitable buffer +UFTPC, +UHTTPC

A.2 Internal TCP/UDP/IP stack error codes The following table lists all allowed error classes that can be provided by the internal TCP/UDP/IP stack through +USOER AT command (for more details, refer to the AT command description in section 14.8).


0 No error +USOCR, +USOSO,+USOGO, +USOCO, +USOWR, +USOST, +USORD, +USORF, +USOLI

2 ENOEN– - No such resource (internal error) +USOCR, +USOSO,+USOGO, +USOCO, +USOWR, +USOST, +USORD, +USORF, +USOLI

4 EINT– - Interrupted system call (internal error) +USOCR, +USOSO,+USOGO, +USOCO, +USOWR, +USOST, +USORD, +USORF, +USOLI

5 EI– - I/O error (internal error) +USOCR, +USOSO,+USOGO, +USOCO, +USOWR, +USOST, +USORD, +USORF, +USOLI

9 EBAD– - Bad file descriptor (internal error) +USOCR, +USOSO,+USOGO, +USOCO, +USOWR, +USOST, +USORD, +USORF, +USOLI

10 ECHIL– - No child processes (internal error) +USOCR, +USOSO,+USOGO, +USOCO, +USOWR, +USOST, +USORD, +USORF, +USOLI

11 EWOULDBLOC– - Current operation would block, try again +USOWR

12 ENOME– - Out of memory (internal error) +USOCR, +USOSO,+USOGO, +USOCO, +USOWR, +USOST, +USORD, +USORF, +USOLI



of 149


14 EFAUL– - Bad address (internal error) +USOCR, +USOSO, +USOGO, +USOCO, +USOWR, +USOST, +USORD, +USORF, +USOLI

22 EINVA– - Invalid argument +USOCR, +USOSO, +USOGO, +USOCO, +USOWR, +USOST, +USORD, +USORF, +USOLI

32 EPIP– - Broken pipe (internal error) +USOCR, +USOSO, +USOGO, +USOCO, +USOWR, +USOST, +USORD, +USORF, +USOLI

38 ENOSY– - Function not implemented +USOSO, +USOGO

92 ENOPROTOOP– - Protocol not available +USOCR

98 EADDRINUS– - Address already in use +USOLI

103 ECONNABORTE– - Software caused connection abort +USOCR, +USOSO, +USOGO, +USOCO, +USOWR, +USOST, +USORD, +USORF, +USOLI

104 ECONNRESE– - Connection reset by peer +USOCR, +USOSO, +USOGO, +USOCO, +USOWR, +USOST, +USORD, +USORF, +USOLI

105 ENOBUF– - No buffer space available +USOCR, +USOSO, +USOGO, +USOCO, +USOWR, +USOST, +USORD, +USORF, +USOLI

107 ENOTCON– - Transport endpoint is not connected +USOCR, +USOSO, +USOGO, +USOCO, +USOWR, +USOST, +USORD, +USORF, +USOLI

108 ESHUTDOW– - Cannot send after transport endpoint shutdown +USOCR, +USOSO, +USOGO, +USOCO, +USOWR, +USOST, +USORD, +USORF, +USOLI

110 ETIMEDOU– - Connection timed out +USOCO, +USOST, +USORD, +USORF

113 EHOSTUNREAC– - No route to host +USOCO, +USOWR, +USOST, +USORD, +USORF

115 EINPROGRES– - Operation now in progress +USOCR, +USOSO, +USOGO, +USOCO, +USOWR, +USOST, +USORD, +USORF, +USOLI

160 ENSRNODAT– - DNS server returned answer with no data +UDNSRN

161 ENSRFORMER– - DNS server claims query was misformatted +UDNSRN

162 ENSRSERVFAI– - DNS server returned general failure +UDNSRN

163 ENSRNOTFOUN– - Domain name not found +UDNSRN

164 ENSRNOTIM– - DNS server does not implement requested operation

+UDNSRN

165 ENSRREFUSE– - DNS server refused query +UDNSRN

166 ENSRBADQUER– - Misformatted DNS query +UDNSRN

167 ENSRBADNAM– - Misformatted domain name +UDNSRN

168 ENSRBADFAMIL– - Unsupported address family +UDNSRN

169 ENSRBADRES– - Misformatted DNS reply +UDNSRN

170 ENSRCONNREFUSE– - Could not contact DNS servers +UDNSRN

171 ENSRTIMEOU– - Timeout while contacting DNS servers +UDNSRN

172 ENSRO– - End of file +UDNSRN

173 ENSRFIL– - Error reading file +UDNSRN

174 ENSRNOME– - Out of memory +UDNSRN

175 ENSRDESTRUCTIO– - Application terminated lookup +UDNSRN

176 ENSRQUERYDOMAINTOOLON– - Domain name is too long +UDNSRN

177 ENSRCNAMELOO– - Domain name is too long +UDNSRN

200 ENETISCON– - subsystem established and available +USOCR, +USOSO, +USOGO, +USOCO, +USOWR, +USOST, +USORD, +USORF, +USOLI



of 149


201 ENETINPROGRES– - subsystem establishment in progress +USOCR, +USOSO, +USOGO, +USOCO, +USOWR, +USOST, +USORD, +USORF, +USOLI

202 ENETNONE– - network subsystem unavailable +USOCR, +USOSO, +USOGO, +USOCO, +USOWR, +USOST, +USORD, +USORF, +USOLI

203 ENETCLOSEINPROGRES– - PPP is closing +USOCR, +USOSO, +USOGO, +USOCO, +USOWR, +USOST, +USORD, +USORF, +USOLI

204 ENETEXIS– - existing net subsystem resources +USOCR, +USOSO, +USOGO, +USOCO, +USOWR, +USOST, +USORD, +USORF, +USOLI

205 ESOCKNOBUFF-- Socket buffer error - running out of buffer +USOWR, +USODL, +USOST

210 EBADAPP-- Invalid application ID +USOCR, +USOCO, +USOWR, +USODL, +USOST, +UPSDA, +USOCL, +UDNSRN

211 EMAPP-- No more applications available +USOCR, +UDNSRN, +UPSDA

212 EMSGSIZE-- The message is too large +USOWR, +USODL, +USOST

213 EMSGTRUNC-- Msg truncated, supplied buffer too small +USOCR

214 ENOADDRESS-- No address for the domain name

215 ENORECOVERY-- Irrecoverable error

216 INUSE-- The resolver is in use now +UDNSRN

217 SOCKEXIST-- There are existing sockets

218 ABORTSEND-- Abort binary mode for incoming data or voice call +USOST, +USOWR

-3 Unknown Error +USOER

A.3 Mobile Termination error result codes +CME ERROR


10 R-UIM card not inserted +CPIN

11 R-UIM PIN1 required ( R-UIM card waiting for PIN1 to be entered ) +CPIN

12 R-UIM PUK1 required ( RUIM PIN1 is blocked ) +CPIN

13 R-UIM failure ( R-UIM card is permanently blocked ) +CPIN

16 Incorrect password +CPIN

17 R-UIM PIN2 required ( R-UIM card waiting for R-UIM PIN2 to be entered )

+CPIN

18 R-UIM PUK2 required ( R-UIM PIN2 is blocked ) +CPIN

50 Invalid Parameters +CIND

80 Operation is contradiction with PIN status +CPIN

81 No password required ( No PIN or PUK required ) +CPIN

1500 Wrong GPIO identifier +UGPIOC, +UGPIOR, +UGPIOW

1501 Set GPIO default error +UGPIOC

1502 Select GPIO mode error +UGPIOC

1503 Read GPIO error +UGPIOR

1504 Write GPIO error +UGPIOW

1621 FFS initializing +UDWNFILE

1622 Write GPIO error +UGPIOW

1623 FFS initializing +UDWNFILE



of 149


1624 FFS file not found +UDWNFILE

1625 FFS file already created +UDWNFILE

1626 FFS illegal id +UDWNFILE

1627 FFS illegal file handle +UDWNFILE

1628 FFS illegal type +UDWNFILE

1629 FFS illegal mode +UDWNFILE

1630 FFS file range +UDWNFILE

1631 FFS operation not possible +UDWNFILE

1632 FFS write error +UDWNFILE

1633 FFS user id error +UDWNFILE

1634 FFS internal fatal error +UDWNFILE

1635 FFS memory resource error +UDWNFILE

1636 FFS maximum number of files exceeded +UDWNFILE

1637 FFS memory not available +UDWNFILE

1638 FFS invalid filename +UDWNFILE

1639 FFS streaming not enabled +UDWNFILE

1640 FFS operation not allowed on static file +UDWNFILE

1641 FFS memory table inconsistency +UDWNFILE

1642 FFS not a factory default file +UDWNFILE

1643 FFS requested memory temporary not available +UDWNFILE

1644 FFS operation not allowed for a directory +UDWNFILE

1645 FFS directory space not available +UDWNFILE

1646 FFS too many streaming files open +UDWNFILE

1647 FFS requested dynamic memory temporary not available +UDWNFILE

1648 FFS user provided a NULL parameter instead of a suitable buffer +UDWNFILE

1649 FFS timeout +UDWNFILE

A.4 Message service failure result codes +CMS ERROR


300 ME failure +CMGS, +CMGW

302 Operation not allowed +CNMI

303 operation not supported +CNMI, +CSMP, +CMGS, +CMGW

305 Invalid Text mode parameter +CSMP, +CMGW, +CMGS

320 memory failure +CMGR, +CMGW, +CMGL, +CMGD, +CMSS

321 invalid memory index +CMGR, +CMGW, +CMGL, +CMGD, +CMSS

322 memory full +CMGS, +CMGW

500 unknown error +CMGD, +CMGR, +CMSS



of 149

B AT Commands List

B.1 Parameters stored in non-volatile memory The following tables lists the AT commands that can be stored in the non-volatile memory with their parameters and the default values.

AT Command Description Default value Comment

+CRM Rm interface protocol 2 packet data service, Network Layer Rm interface, PPP

$MDN Mobile Directory Number 000000<last 4 digits of dec MEID>

AT$RTN=000000 can reset it to default value.

$MSID MSID 000000<last 4 digits of dec MEID>

AT$RTN=000000 can reset it to default value.

$QCMIP Mobile IP functionality Verizon: 1

Sprint: 2

– - Mobile IP preferred (default value for Verizon).

– -Mobile IP only (default value for Sprint).

$QCMIPP Mobile Profile ID Verizon: 0

Sprint: 1

$QCMIPT RFC2002bis Authentication 0 disable RFC2002bis. RFC2002 style authentication is used instead.

$QCMIPEP Enable/disable the active profile

$QCMIPNAI NAI for active profile Provided by the carrier for each account.

$QCMIPRT Reverse Tunneling 1 Reverse Tunneling ON

$QCMIPMASS MN-AAA Shared Secrets Provided by the carrier for each account.

$QCMIPMASSX MN-AAA Shared Secrets in HEX format

Provided by the carrier for each account.

$QCMIPMHSS MN-HA Shared Secrets Provided by the carrier for each account.

$QCMIPMHSSX MN-HA Shared Secrets in HEX format

Provided by the carrier for each account.

$QCMIPMHSPI MN-HA SPI Shared Secrets Provided by the carrier for each account.

$QCMIPMASPI MN-AAA SPI Shared Secrets Provided by the carrier for each account.

$ROAM Roaming status 1 Automatic mode

+UMGC Microphone Gain Path 0:

1, 8153, 16384

Path 0:

<micLna>: 1,<CodecTxGain>: 8153,<TxVloume>: 16384

+USGC Speaker Gain Path 0:

3,16384

Path 0:

<rxVolume>: 3, <codecRxGain>: 800

+USTN Sidetone Path 0:

8211

Path 0:

<CodecSTGain>: 8211

+UUBF Uplink Digital Filter Path 0:

Filter 1: 65523, 29, 65465, 363, 64113, 3080, 12442

Path 0:

Filter 1: <ho/h12>: 65523,<h1/h11>: 29,<h2/h10>: 65465,<h3/h9>: 363,<h4/h8>: 64113,<h5/h7>: 3080,<h6>: 12442

+UDBF Downlink Digital Filter Path 0:

Filter 1: 0,0,0,0,0,0,0

Path 0:

Filter 1: <h0/h12>: 0, <h1/h11>: 0, <h2/h10>: 0, <h3/h9>: 0, <h4/h8>: 0, <h5/h7>: 0, <h6>: 0



of 149

AT Command Description Default value Comment

+UHFP Hands-Free Parameters Path 0:

1, 1, 1, 1, 8192, 65535, 32613, 0, 61696, 20, 2048, 2048, 19000, 6000, 10361, 450

Path 0:

EC = 1,NS = 1,AGC = 1,AVC = 1

<rx_agc_static_gain>: 8192, <rx_agc_aig>: 65535, <tx_agc_static_gain>: 32613, <tx_agc_aig>: 0, <rx_avc_sensitivity>: 61696,

<echo_path_delay>: 20, <OutputGain>: 2048, <NLPP_gain>: 2048, <DENS_tail_alpha>: 19000, <DENS_tail_portion>: 6000, <DENS_limit_NS>: 10361, <DENS_NL_atten>: 450

+UGPIOC GPIO functionality setting 255 Default setting for <gpio1>, <gpio2>, <gpio3>, <gpio4>, <gpio5> at the first power up. All the GPIOs are in tristate.

+UPSV Power saving control 0



of 149

C Glossary 3GPP 3rd Generation Partnership Project

ADC Analog to Digital Converter

ADN Abbreviated Dialing Numbers

AMR Adaptive Multi Rate

APN Access Point Name

ASCII American Standard Code for Information Interchange

AT AT Command Interpreter Software Subsystem, or attention

BL Black List

BSD Berkley Standard Distribution

CB Cell Broadcast

CBM Cell Broadcast Message

CDMA Code Division Multiple Access

CLIP Calling Line Identification Presentation

CLIR Calling Line Identification Restriction

COLP Connected Line Identification Presentation

COLR Connected Line Identification Restriction

CM Connection Management

CPHS Common PCN Handset Specification

CR Carriage Return

CS Circuit Switch

CSD Circuit-Switched Data

CTS Clear To Send

CUG Closed User Group

DA Destination Address

DCD Data Carrier Detect

DCE Data Communication Equipment

DCM Data Connection Management

DNS Domain Name Server

DSR DSC transponder response

DTE, TE Data Terminal Equipment

DTMF Dual Tone Multi Frequency

DTR Data Terminal Ready

DUT Device Under Test

EEP EEPROM Emulation Parameters

EFPLMNwAcT Elementary File "User controlled PLMN Selector with Access Technology"

EONS Enhanced Operator Name from SIM-files EF-OPL and EF-PNN

EPD Escape Prompt Delay

ESN Electronic Serial Number

FDN Fixed Dialing Number

FOAT Firmware Over AT



of 149

FOTA Firmware Over The Air

FTP File Transfer Protocol

FW Firmware

GNSS Global Navigation Satellite System (general term that includes GPS, GLONASS, BeiDou, Galileo)

GPIO General Purpose Input Output

GPRS General Packet Radio Service

GPS Global Positioning System

GSM Global System for Mobile Communications

HDLC High Level Data Link Control

HPLMN Home PLMN

HTTP HyperText Transfer Protocol

I Information

I2S Inter IC Sound

ICCID Integrated Circuit Card ID

ICMP Internet Control Message Protocol

ICP Inter Processor Communication

IMEI International Mobile Equipment Identity

IMSI International Mobile Station Identity

IP Internet Protocol

IRA International Reference Alphabet

IRC Intermediate Result Code

ISDN Integrated Services Digital Network

ISP Internet Service Provider

L3 Layer 3

LCP Link Control Protocol

LF Line Feed

M2M Machine-To-Machine

MCC Mobile Country Code

ME Mobile Equipment

MEID Mobile Equipment IDentity

MN Mobile Network Software Subsystem

MNC Mobile Network Code

MO Mobile Originated

MS Mobile Station

MSISDN Mobile Systems International Subscriber Identity Number

MT Mobile Terminated

NID Network ID

NVM Non-Volatile Memory

NVRAM Not Volatile RAM

OLCM On Line Commands Mode

PAD Packet Assembler/Disassembler

PDP Packet Data Protocol

PDU Protocol Data Unit



of 149

PIN Personal Identification Number

PLMN Public Land Mobile Network

PPP Point-to-Point Protocol

PSD Packet-Switched Data

PUK Personal Unblocking Key

QoS Quality of Service

RAM Random Access Memory

RFU Reserved for Future Use

RI Ring Indicator

RTC Real Time Clock

RTS Request To Send

Rx Receiver

SC Service Centre

SI SIM Application Part Software Subsystem

SID System ID

SMS Short Message Service

SMSC Short Message Service Center

SMTP Simple Mail Transfer Protocol

SO Service Option

TCP Transfer Control Protocol

TE Terminal Equipment

TP Transfer layer Protocol

Tx Transmitter

TZ Time Zone

UCS2 Universal Character Set

UDP User Datagram Protocol

UI Unnumbered Information

UIH Unnumbered Information with header Check

URC Unsolicited Result Code

USIM UMTS Subscriber Identity Module

UUS1 User-to-User Signaling Supplementary Service 1


UBX-13000621 - R10 Production Information Related documents

of 149

Related documents [1] Stevens. TCP/IP Illustrated Volume1 & 2 Addison-Wesley, 1994.

[2] 3GPP TS 27.007 - Technical Specification Group Core Network and Terminals; AT command set for User Equipment (UE)

[3] 3GPP TS 22.004 - General on supplementary services

[4] GSM 02.06 - Digital cellular telecommunication system (Phase 2+); Mobile Stations (MS) features

[5] 3GPP TS 22.030 - Man-Machine Interface (MMI) of the User Equipment (UE)

[6] 3GPP TS 22.090 - Unstructured Supplementary Service Data (USSD); Stage 1

[7] 3GPP TS 23.038 - Alphabets and language-specific information

[8] 3GPP TS 23.040 - Technical realization of Short Message Service (SMS)

[9] 3GPP TS 23.040 - Technical realization of Cell Broadcast Service (CBS)

[10] 3GPP TS 23.060 - Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS); Service description

[11] 3GPP TS 24.007 - Mobile radio interface signaling layer 3; General aspects

[12] 3GPP TS 24.010 - Mobile radio interface layer 3 specification

[13] 3GPP TS 24.011 Point-to-point (PP) Short Message Service (SMS) support on mobile radio interface

[14] GSM 04.11 - Digital cellular telecommunications system (Phase 2+); Short Message Service Cell Broadcast (SMSCB) Support on Mobile Radio Interface.

[15] 3GPP TS 22.030 - Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Man-Machine Interface (MMI) of the User Equipment (UE)

[16] 3GPP TS 27.005 - Technical Specification Group Terminals; Use of Data Terminal Equipment– - Data Circuit terminating Equipment (DTE-DCE) interface for Short Message Services (SMS) and Cell Broadcast Service (CBS)

[17] 3GPP TS 27.060 - Technical Specification Group Core Network; Packet Domain; Mobile Station (MS) supporting Packet Switched Services

[18] GSM 11.11 Digital cellular telecommunications system (Phase 2+); Specification of the Subscriber Identity Module – Mobile Equipment (SIM – ME) interface

[19] 3GPP TS 31.102 - Characteristics of the Universal Subscriber Identity Module (USIM) application

[20] ITU-T Recommendation V250, 05-99.

[21] ITU-T V.25ter ITU-T V.25 ter Recommendation: Data Communications over the Telephone Network; Serial asynchronous automatic Dialing and control.

[22] ITU-T T.32 ITU-T Recommendation T.32 Asynchronous Facsimile DCE Control– - Service Class 2

[23] ISO 639 (1988) Code for the representation of names of languages

[24] ITU-T Recommendation V24, 02-2000. List of definitions for interchange circuits between Data Terminal Equipment (DTE) and Data Connection Equipment (DCE).

[25] RFC 791 - Internet Protocol

[26] 3GPP TS 05.08 Radio subsystem link control

[27] 3GPP TS 22.087 User-to-User Signaling (UUS)

[28] 3GPP TS 24.008 Mobile radio interface layer 3 specification

[29] 3GPP TS 22.022 Personalization of Mobile Equipment (ME)

[30] 3GPP TS 22.082 Call Forwarding (CF) supplementary services

[31] 3GPP TS 22.083 Call Waiting (CW) and Call Holding (HOLD)

[32] 3GPP TS 22.081 Line identification Supplementary Services- Stage 1

[33] 3GPP TS 23.081 Line identification supplementary services- Stage 2

[34] 3GPP TS 22.086 Advice of Charge (AoC) Supplementary Services


UBX-13000621 - R10 Production Information Related documents

of 149

[35] 3GPP TS 22.024 Description of Charge Advice Information (CAI)

[36] 3GPP TS 22.085 Closed User Group (CUG) Supplementary Services

[37] 3GPP TS 22.096 Name identification supplementary services

[38] 3GPP TS 04.18 Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol

[39] 3GPP TS 04.60 General Packet Radio Service (GPRS); Mobile Station (MS– - Base Station System (BSS) interface; Radio Link Control/ Medium Access Control (RLC/MAC) protocol

[40] 3GPP TS 05.02 Multiplexing and Multiple Access on the Radio Path

[41] 3GPP TS 51.014 Specification of the SIM Application Toolkit for the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface

[42] u-blox 5/6 Receiver Description including Protocol Specification, Document. No GPS-SW-09017

[43] 3GPP TS 27.010 V3.4.0 - Terminal Equipment to User Equipment (TE-UE) multiplexer protocol (Release 1999)

[44] LISA-C200 & FW75-C200 System Integration Manual Document No UBX-13000620

[45] ETSI TS 102 22“ "Smart Cards; UICC-Terminal interface; Physical and logical characteristics (Release ”)"

[46] ETSI TS 102 223 Smart cards; Card Application Toolkit (CAT)

[47] GPS Implementation Application Note, Document No GSM.G1-CS-09007

[48] 3GPP TS 25.306 UE Radio Access capabilities

[49] RFC326– - Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs

[50] RFC 792 Internet Control Message Protocol (http://tools.ietf.org/html/rfc0792)

[51] 3GPP TS 22.002 Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)

[52] 3GPP TS 22.067 enhanced Multi Level Precedence and Pre-emption service (eMLPP); Stage 1

[53] LISA-C200 Data sheet Document No UBX-13000623

For regular updates to u-blox documentation and to receive product change notifications, register on our homepage.

http://tools.ietf.org/html/rfc0792


UBX-13000621 - R10 Production Information Revision history

of 149

Revision history Revision Date Name Status / Comments

- 2-Mar-2012 grin Initial release

A 5-Jul-2012 grin Added sections 3.1, 3.18, 3.19, 4.2 –4.7, 8.7, 8.8, 12.1-12.4. Replaced section 8.3. Added sections 11, 13-17.

B 9-Jul-2012 grin Modified Audio and Socket AT Commands. Added FTP AT Commands, +USODL, +CMGR, +UDCONF, +VTD, +VTS, +UVTS, Error codes Annex. Removed AT Command ATH. Minor changes for D, +CSQ, +GMM, +CPAS, +CIND, +CMEE, +CREG, +NETPAR, +CFUN, +CSS,+CCLK, +UHWVER, +GMR, $DEBUG, +CNMI, +CIMI, +CLIP, +CPAS, DNS description, ATD, ATA.

C 3-Aug-2012 grin Fixed minor syntax errors or typos for +USOCL, +USOER, +USORF, +USORD, +USOST, +USOWR, +CLIP, ATI, +UOMASTAT, +USTN, +UHFP, +UCST, +CREG, +CIEV, +UUFTPCD, +UUFTPCR, +UUHTTTPCR

D 12- Dec-2012 smoi New commands added: +UANTR, +UAERIS, +USVC, +USOABT, +USVC, +USPM, +UPCM Audio commands section updated; Removed +OMALOG and +ICF commands Fixed minor syntax errors for +UHWVER, +CNMI, +CIMI, +IFC, +IPR, +CMER, +UCST, +CNMI, +CMGR, +CLIP, +UFTP

D1 20-Feb-2013 smoi Applicability to C200-x2S-01 added; +UPSV command added; Applicable antenna load for +UANTR command updated Last version with old document number: CDMA-2X-11002

E 25-Aug-2013 smoi New GNSS AT commands added; New UTEST AT command added; UPSV syntax changed +CHUP and +USOCTL commands added Last revision with old document number CDMA-2X-11002

R08 31-Jan-2014 utej Fixed minor syntax errors for +UDNSRN, +UPSV, +CSMP, +VTS, +CMGD, +USGC, +UTEST, +UMGC, +UANTR, +UGPIOC, +UGPIOR, +USODL, +UFTPC, +ATZ0, $QCMIPMASS, $QCMIPMHSS, Example changes for $QCMIPGETP, +UOMADM, +UOMAHFA,ATI CR-LF changes for $MDN, $MSID, $ROAM, +USVC, +CSQ, +CREG, +CMIP, +CBIP, +SERVICE, ATI, +UANTR, +UTEMP, +CFUN Removed +USOCTL command

R09 16-Apr-2014 utej 03S firmware number changed; Added temperature range to values table in section 3.17

R10 1-Oct-14 jole Added the following commands: +UPLAYFILE, +UPROVSTATE, +UFWUPD, +UPSDACFG, +UPSDA, +USORNGCFG, +URINGCFG, +UBSLOC, +UCSTRD, +CMIPIND, +UMSS, +UCLEAN, +UPACCOLC, +UIMSIDATA, +UMOBTERM, +USIDNIDPR, +UPRLWRITE, +UUSCELL. Added support for M8 GNSS. Added CellLocate® features. Added FTP direct link modes, Added FTP abort functionality. Updated and added Error codes for TCP/UDP and +CME. Added +UPSV Mode 2.


UBX-13000621 - R10 Production Information Contact

of 149

Contact For complete contact information visit us at www.u-blox.com

u-blox Offices

North, Central and South America

u-blox America, Inc.

Phone: +1 703 483 3180 E-mail: [email protected]

Regional Office West Coast:


Technical Support:


Headquarters Europe, Middle East, Africa

u-blox AG

Phone: +41 44 722 74 44 E-mail: [email protected] Support: support @u-blox.com

Asia, Australia, Pacific

u-blox Singapore Pte. Ltd.

Phone: +65 6734 3811 E-mail: [email protected] Support: [email protected]

Regional Office Australia:

Phone: +61 2 8448 2016 E-mail: [email protected] Support: [email protected]

Regional Office China (Beijing):

Phone: +86 10 68 133 545 E-mail: [email protected] Support: [email protected]

Regional Office China (Shenzhen):


Regional Office India:


Regional Office Japan:


Regional Office Korea:


Regional Office Taiwan:



mailto:[email protected]


mailto:support%[email protected]


u-blox lisa-c200 and fw75-c200

Documents