Appendix: AT Commands List

Parameters stored in profiles

The parameter settings of some commands can be stored in the profiles available in the memory module.

To store and display these profiles, see the AT&W and AT&V commands description.

Some AT commands have a unique configuration for all the AT interfaces while for other AT commands it is possible to set a different configuration for each AT interface: the “AT interface configuration sharing” column in the next table provides this information. Some AT command interfaces have a dynamic activation, which means they are not statically activated at boot time (MUX AT channel is activated when the MUX protocol is established, USB AT channel is activated if/when the USB cable is plugged-in, deactivated when it is removed). Since the activation reloads the AT command profile from NVM for the activated interface, the shared “AT interface configurations” could be overwritten. It is suggested to reconfigure them at the requested value if an AT command interface is dynamically activated.

Since each AT interface has its own configuration in RAM and NVM, AT configuration sharing is an exceptional condition. See Storing of AT commands setting

The following table lists the AT commands which setting can be stored in the profiles with their parameters as well as the factory-programmed values.

AT commandDescriptionAT interface configuration sharingFactory-programmed value / Remarks

&C

DCD status

No

1 (DCD enabled)

&D

DTR status

No

1 (DTR enabled)

&K

Flow control status

No

  • The command setting is stored in the NVM

+CEREG

EPS Network registration status reporting

Yes

  • 0 (network registration URC disabled)

+CGEREP

EPS Network registration status reporting

No

  • 0 (event reporting disabled), 0 (buffer cleared when switching mode)

+CMEE

Mobile termination error reporting

Yes

  • 1 (error result code enabled and numeric values used)

+CMGF

Preferred message format

Yes

  • 1 (format of messages in Text mode)

+CNEC

Network error code reporting

No

0 (URC reporting disabled)

+CNMI

New message indication

Yes

  • 1 (discard indication and reject new received message URCs when MT-DTE link is reserved)

  • 0 (no SMS-DELIVER indications are routed to the TE)

  • 0 (no CBM indications to the DTE)

  • 0 (no SMS-STATUS-REPORTs are routed to the DTE)

  • 0 (MT buffer of URCs defined within this command is flushed to the DTE when >mode< 1…​3 is entered)

  • The command setting is stored in the NVM

+COPS

Operator selection

Yes

  • The command setting is stored in the NVM

+CPMS

Preferred message storage

No

  • The command setting is stored in the NVM

+CREG

Network registration status reporting

Yes

  • 0 (network registration URC disabled)

+CSCA

Service center address

No

  • The command setting is stored in the NVM.

+CSCB

Cell broadcast message types

No

  • 0 <mode>, "" <mids>, "" <dcss>

+CSMP

Select message service

No

  • The command setting is stored in the NVM

+CSCS

Select character set configuration

No

  • The command setting is not stored in the profile

+CSMS

Select message service

No

  • 0 <service>

+CSDH

Show text mode parameters

No

  • 0 <show>

+CTZR

Time zone reporting

Yes

  • 0 (disable the time zone change event reporting)

+ICF

DTE-DCE character framing

No

  • 3, 1 (framing format: 8 data 1 stop, no parity)

  • The command settings is stored in the NVM

+IFC

DTE-DCE local flow control

No

  • 2 (<DCE_by_DTE> on circuit 106 (CTS)), 2 (<DTE_by_DCE> on circuit 105 (RTS))

  • The command settings is stored in the NVM

+IPR

Baud rate

No

  • 115200 (115200 b/s)

  • The command settings is stored in the NVM

+UCESQS

Signal quality change reporting control

No

0 (event reporting disabled), 0 (report all events, when enabled)

+UPSV

Power saving control

Yes

  • The command setting is stored in the NVM

+USLPURC

Enables or disables URCs to be sent when the module enters and exits deep-sleep modes

No

"SLEEP1":0, "SLEEP2":0, "HIBNATE":0

+USIO

Serial interfaces configuration

Yes

  • The command setting is stored in the NVM

+UURCSTAT

Multiple URCs reporting

No

Reporting disabled for all the considered URCs

E

Echo status

No

1 (echo enabled)

Q

Result code suppression

No

0 (DCE transmits result codes)

S0

Automatic answer

No

V

DCE response format

No

1 (Verbose response text)

Parameters stored in non volatile memory

The following table lists the AT commands which setting can be stored in the non volatile memory with their parameters and the factory-programmed values.

AT commandDescriptionFactory-programmed value / Comment

E

Echo status

  • The command setting is stored in the personal profile

&C

DCD status

  • The command setting is stored in the personal profile

&D

DTR status

  • The command setting is stored in the personal profile

&K

Flow control status

  • 3 (RTS/CTS DTE flow control enabled)

+CCIOTOPT

CIoT optimization configuration

+CCLK

Clock

+CEDRXS

eDRX setting

  • 0 (use of eDRX disabled), 4 (LTE), "0011", "0001"

+CEMODE

UE modes of operation for EPS

  • 2 (CS/PS mode 2 of operation; "data centric")

+CGDCONT

PDP context definition

+CGEQOS

Define EPS quality of service

  • all contexts are undefined

+CIPCA

Initial PDP context activation

+COPS

Operator selection

  • 0 <mode>, "" <oper>

+CPMS

Preferred message storage

  • <mem1>, <mem2> and <mem3> are set to "ME"

+CPSMS

Power Saving Mode setting

  • <mode>=0 (PSM disabled), <Requested_Periodic_TAU>="00110100", <Requested_Active_Time>= "00100101"

+CSCA

Service center address

  • service center address is read from SIM and populated in NVM

+CSCON

Connection status signalling

  • The command setting is stored in the personal profile

+CSCS

Select character set configuration

  • "IRA" (International Reference Alphabet)

+CSGT

Set greeting text

  • 1 (greeting text enabled), "+UUSTATUS: READY"

+CSMP

Select message service

  • 17 <fo>, 167 <vp>, 0 <pid>, 0 <dcs>

+CSMS

Select message service

  • The command setting is stored in the personal profile

+CNMI

New message indication

  • 1 <mode>, 2 <mt>, 0 <bm>, 0 <ds>, 0 <bfr>

+CTZR

Time zone reporting

  • 0 (disable the time zone change event reporting)

+CTZU

Automatic time zone update

  • 1 (automatic time zone via NITZ enabled)

+IPR

Baud rate

  • 115200 (115200 b/s)

+UBANDCONF

Band configuration

  • LEXI-R10401D-00B - 2, 4, 5, 12, 13, 66, 71

  • LEXI-R10801D-00B - 1, 3, 5, 7, 8, 20, 28

+UFREQLOCK

Frequency / Cell Lock

0 (disabled cell/frequency locks)

+UBIP

Bearer Independent Protocol status indication

0 (BIP status indication disabled)

  • The command setting is stored in the personal profile

+UDCONF=9

Uplink user data plane configuration

  • The AT command setting is volatile

+UDCONF=19

Default CID and preferred protocol type configuration

1 (<cid>), 0 (IPv4)

+UDCONF=50

SIM hot insertion detection

0 (disabled)

+UDCONF=81

Integrity check on test networks configuration

  • 1 (integrity check on test networks enabled)

+UDCONF=101

Discarding configuration for TCP packets not fitting windows size

1 (discard enabled)

+UDCONF=121

Disable the deep cells scan for database feeding in AssistNow Online operation

0 (deep cells scan enabled)

+UFACTORY

Restore factory configuration

0 (no FS factory restore), 0 (no NVM factory restore)

+UFOTASTAT

FOTA reporting

+UGPIOC

GPIO functionality setting

  • GPIO1: 255, GPIO2: 255, GPIO3: 255, GPIO4: 255, GPIO5: 255, GPIO6: 255, I2S_WA: 255, I2S_TXD: 255, I2S_CLK: 255, I2S_RXD: 255

+UGSRV

Aiding server configuration

"cell-live1.services.u-blox.com" (primary MGA server), "cell-live2.services.u-blox.com" (secondary MGA server), 14 (Number of days for validation of Offline data), 4 (Number of weeks for validation of Offline data), 1 (Resolution of offline data for MGA), 65 (Desired GNSS for the (offline) aiding: GPS and GLONASS), 0 (AssistNow Online data are downloaded at GNSS receiver power up), 15 (all the desired data types for the (online) aiding are set), 1 (PDP context identifier)

+ULOCIND

Localization information request status unsolicited indication

  • The command setting is not stored in the NVM

+ULWM2M

LwM2M client activation/deactivation

+ULWM2MSTAT

LwM2M reporting

+UMACQOSTMR

MAC QoS inactivity timer(s)

  • The command setting is not stored in the NVM.

+UMNOPROF

MNO profile configuration

  • 90 (Global)

+UNASTCFG

NAS timers configuration

  • T3482 timer configuration (+UNASTCFG=1)

    • 8 (T3482 timer value: 8 s)

    • 5 (PDN connectivity request attempts)

  • T3492 timer configuration (+UNASTCFG=2)

    • 6 (T3492 timer value: 6 s)

    • 5 (PDN disconnect request attempts)

+UNETCFG

Set network adapter parameters

  • networking mode configuration("nat")

    • 0 (NAT is disabled (bridge mode))

  • ppp authentication rule ("pppauthselect")

    • 0 (PPP dial-up authentication parameters are predefined)

+UNETDEVCTL

Controls the data path for the network adapter

  • Binding option

    • 0 (no binding)

  • cid

    • 0 (invalid cid)

  • URC reporting

    • 0 (URC disabled)

  • Activation state

    • 0 (not activated)

+UNVMCFG

NVM RAM mode management

  • NVM RAM mode management

    • 0 ("generic" class mode)

    • 0 ("gnss" class mode)

    • 0 ("aonnvm" class mode)

    • 0 ("aonnvmbckp" class mode)

  • NVM URC management

    • 0 ("urc" setting)

+UPSV

Power saving control

  • 0 (power saving disabled)

+UPSCONFIG

USIM simulator and PS configuration

"REL": 13 (UE release 13), "PWC": 3 (UE power class 3)

+UPSMR

Deep-sleep mode indication

0 (deep-sleep mode URC disabled)

+URING

RING line handling

0 (feature disabled (RING line is only asserted on incoming call and incoming SMS))

+URPMCONF

Radio Policy Manager (RPM) configuration

  • <PLMN> list: "901.40","276.01","232.03","232.07","230.01","219.01","262.01","202.01","216.30","294.01","297.02","220.04","204.16","204.20","260.02","226.03","226.06","231.02","262.06","999.01"

+URPMPARAM

Radio Policy Manager (RPM) parameters configuration

  • <rpmflag>: 0

  • <N1>: 1

  • <T1>: 60 (minutes)

  • <T1_ext>: 48 (hours)

  • <F1>: 60

  • <F2>: 30

  • <F3>: 60

  • <F4>: 30

  • <isOmParamsValid>: 1 (Operational management functionality enabled)

  • <CBR1>: 0

  • <CR1>: 0

  • <CPDP1>: 0

  • <LR1>: 0

  • <LR2>: 0

  • <LR3>: 0

+USIMSTAT

(U)SIM initialization status reporting

0 (URC +UUSIMSTAT disabled)

+USIO

Serial interfaces configuration

  • 0 (AT command on 9-wire UART, USB1 and USB3, diagnostic log on USB2, no AUX UART)

+UATUN

Antenna dynamic tuner

Antenna dynamic tuner control: 0 (disabled)

+UUARTCONF

UART baud rate and flow control NVM management

  • LEXI-R10

    • 0 (main UART interface): 115200 (115200 b/s), 3 (RTS/CTS DTE flow control enabled)

    • 1 (auxiliary UART interface): 115200 (115200 b/s), 3 (RTS/CTS DTE flow control enabled)

+UURCCFG

URC reporting behavior configuration

  • LEXI-R10

    • <config_item>= 0: The command setting is not saved in the NVM

    • <config_item>= 1: 1 (URC deferring enabled)

+UUSBCONF

USB profiles configuration

+UUSBSLPCONF

Configures USB capability to allow module to enter sleep state

0 (usb_allow_sleep), 0 (usb_min_allowed_sleep)

S0

Automatic answer

V

DCE response format

  • The command setting is stored in the personal profile

Saving AT commands configuration

The following procedure can be used to store the AT commands configuration of each AT interface for the AT commands listed in Parameters stored in profiles:

The following procedure can be used to store the AT commands configuration for the AT commands listed in Parameters stored in non volatile memory:

  • Since the permanent saving of the NVM content is achieved by a low priority process, it can be delayed by other module activities as network procedures, call management, and so on. To be sure to effectively save the run-time configuration of the commands listed in Parameters stored in non volatile memory, it is advisable to switch off or reboot the module with +CPWROFF or +CFUN=15 or +CFUN=16 AT commands.

Estimated maximum command response time

After having sent a command to a u-blox cellular module, the time to obtain a result code depends on the SIM and the network. Immediate response is possible, if the command does not interact with either the SIM or the network.

The following table reports the maximum time to get the result code for the AT commands, which are grouped by categories.

CategoryEstimated maximum time to get responseCommands

Power off

  • 5 s

+CPWROFF

Set module functionality

  • 25 s

+CFUN

Call control

  • Up to 50 seconds

A,H,+CHUP,+CSVM

Dial

  • Up to 50 seconds

D,D*,D>,DL

Data connection commands

  • Up to 45 seconds

+CGATT,+CGDATA,+UCGOPS,+UCSDA,+UPSDA

Network commands

  • Up to 60 s

+COPS,+UCFSCAN

Network commands

< 10 s

+URAT,+URATSCAN,+UMACQOSTMR

Network commands

< 5 s

+UCONNREL,+UFPLMNDEL

Signal quality change reporting control

< 5 s

+UCESQS

Security

  • Up to 3 minutes

  • 5 s

+CLCK,+CPWD

Delete all SMSes

< 55 s

+CMGD

Send SMS

  • 60 s (calculated from prompt ">")

+CMGS,+CMGC,+CMSS,+UCMGS,+UCMGS3GPP2

SMS acknowledgement to MT

  • 30 s

+CNMA

Inline send message

< 60 s

+USMSSEND

SMS list message

< 10 s

+CMGL,+UCMGL

Preferred message storage

< 10 s

+CPMS

SIM management

< 10 s

+CACM,+CAMM,+CAOC,+CMGW,+UCMGW,+CMGR,+UCMGP,+UCMGR,+CNUM,+CPIN,+CPINR,+CPOL,+CPUC,+CR,+CRES,+CRSM,+CSCA,+CSCB,+CSMP

PDP context activation and deactivation

  • Up to 45 seconds

+CGACT

PDP context modification

  • Up to 45 seconds

+CGCMOD

Restore configuration

< 5 s

+UFACTORY

End user test (antenna dynamic tuner control)

< 5 s

+UATUN

GPIO commands

< 10 s

+UGPIOC,+UGPIOR,+UGPIOW

Internet suite (socket connect)

  • < 70 s

+USOCO

Internet suite (socket connect with SSL)

  • < 70 s

+USOSEC

Internet suite (socket write)

  • < 60 s

+USOWR

Internet suite (UDP socket write)

  • < 60 s

+USOST

Internet suite (socket closure)

  • 5 s

+USOCL

Internet suite

  • 15 s

+USMTPC,+USMTPM,+USODL,+USOLI,+USORD,+USORF

Resolve name/IP number through DNS

  • < 1 s

+UDNSRN

GNSS commands

< 10 s (except +UGPS for which timeout is according to the performed operation)

+UGAOS,+UGGGA,+UGGLL,+UGGSA,+UGGSV,+UGPS,+UGRMC,+UGTMR,+UGUBX,+UGVTG,+UGZDA,+ULOC

Wi-Fi scan configuration

< 255 s

+UWIFISCAN

MQTT command

  • immediate

+UMQTTC

SNTP Command

< 45 s

+USNTP

Multiple AT command interfaces

u-blox cellular modules support multiple AT command interfaces, that means a certain number of virtual or physical channels that work as described in Definitions.

Each interface maintains its own run-time AT commands configuration (AT command profile), which can be different among the interfaces.

At the module start-up, since there is only a set of the profiles (not one for each interface), all the interfaces are configured in the same way (AT commands configuration for the commands in the profile is the same for all the interfaces). Subsequently, each interface can change its run-time AT profile (stored in RAM). The commands AT&W, AT&V manage this run-time AT commands configuration for the interface where they are issued.

The USB interface implements multiple AT command interfaces. Unlike the other physical interfaces (e.g. UART, SPI), AT command interfaces over USB only exist when the module is connected to DTE by USB. If the USB connection between the module and the DTE is interrupted (e.g. by USB cable removal), all the AT command interfaces running on it are destroyed. This has two main consequences:

  • Any data connection (both circuit switched and packet switched) established over an AT command interface associated to the USB interface is released.

  • Whenever the USB connection between the module and the DTE is re-established, the AT command interfaces running on it are created, and for each of these interfaces the AT command profile is reloaded from NVM and applied.

The reload of the AT command profile from the NVM also results in the re-application of the +UPSV setting, which is a shared “AT interface configuration”. This must be kept in mind, since the change could have impacts on the communication over the UART interface.

As mentioned in Definitions, generally there is not difference in the execution of an AT command among the interfaces. But, there are some exceptions due to interface restrictions. In particular, the differences relate to AT commands that configure the DCE-DTE interface.

table_title provides the major differences.

AT command

UART / AUX UART (where available)

Multiplexer

USB (where available)

SPI (where available)

&K

Effective

When it returns OK (the configuration is allowed), it is effective

When it returns OK (the configuration is allowed), it is not effective (only change the value in the AT command profile)

When it returns OK (the configuration is allowed), it is not effective (only change the value in the AT command profile)

+ICF

Effective

Returns OK, but it is not effective (only change the value in the AT command profile)

Returns OK, but it is not effective (only change the value in the AT command profile)

Returns OK, but it is not effective (only change the value in the AT command profile)

+IFC

Effective

When it returns OK (the configuration is allowed), it is effective

When it returns OK (the configuration is allowed), it is not effective (only change the value in the AT command profile)

When it returns OK (the configuration is allowed), it is not effective (only change the value in the AT command profile)

+IPR

Effective

Returns OK, but it is not effective (only change the value in the AT command profile)

Returns OK, but it is not effective (only change the value in the AT command profile)

Returns OK, but it is not effective (only change the value in the AT command profile)

+UPSV

Effective

Returns OK, but it changes UART setting

Returns OK, but it changes UART setting

Returns OK, but it changes UART setting

Interface comparison

When using two or more AT interfaces, the following points shall be considered:

  • Since each AT interface has its own AT configuration stored in NVM, it is not needed to re-configure the AT interface at each module start-up (for the settings that are persistent and if each AT interface requires different settings). This can be done once, before using the AT&W command on each AT interface to store the configuration.

  • +UPSV setting is applied in the same way regardless the AT interface where it is issued. In particular, the configured <Timeout> value is global and valid for every AT interface.

  • Multiple direct link connections are not allowed. When considering the number of active direct links, take into account also the connection established by the +USODL AT command, the UHTTP direct link mode (see parameters http_command=6 and http_command=7 in +UHTTPC command), the UMQTT binary mode (see parameter op_code=9 in +UMQTTC to publish a binary message to a topic), the +USOWR AT command for binary mode and the +FREAD AT command.