- Support portal
- Evaluation Kits and partner products
u-blox Support
- Product documentation
Documentation
- About
- Sustainability
- Partners and Alliances
- Contact
About u-blox
- Investor relations
Investor relations
The parameter settings of some commands can be stored in the profiles available in the memory module.
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 command | Description | AT interface configuration sharing | Factory-programmed value / Remarks |
---|---|---|---|
DCD status | No | 1 (DCD enabled) | |
DTR status | No | 1 (DTR enabled) | |
Flow control status | No |
| |
EPS Network registration status reporting | Yes |
| |
EPS Network registration status reporting | No |
| |
Mobile termination error reporting | Yes |
| |
Preferred message format | Yes |
| |
Network error code reporting | No | 0 (URC reporting disabled) | |
New message indication | Yes |
| |
Operator selection | Yes |
| |
Preferred message storage | No |
| |
Network registration status reporting | Yes |
| |
Service center address | No |
| |
Cell broadcast message types | No |
| |
Select message service | No |
| |
Select character set configuration | No |
| |
Select message service | No |
| |
Show text mode parameters | No |
| |
Time zone reporting | Yes |
| |
DTE-DCE character framing | No |
| |
DTE-DCE local flow control | No |
| |
Baud rate | No |
| |
Signal quality change reporting control | No | 0 (event reporting disabled), 0 (report all events, when enabled) | |
Power saving control | Yes |
| |
Enables or disables URCs to be sent when the module enters and exits deep-sleep modes | No | "SLEEP1":0, "SLEEP2":0, "HIBNATE":0 | |
Serial interfaces configuration | Yes |
| |
Multiple URCs reporting | No | Reporting disabled for all the considered URCs | |
Echo status | No | 1 (echo enabled) | |
Result code suppression | No | 0 (DCE transmits result codes) | |
Automatic answer | No | ||
DCE response format | No | 1 (Verbose response text) |
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 command | Description | Factory-programmed value / Comment |
---|---|---|
Echo status |
| |
DCD status |
| |
DTR status |
| |
Flow control status |
| |
CIoT optimization configuration | ||
Clock | ||
eDRX setting |
| |
UE modes of operation for EPS |
| |
PDP context definition | ||
Define EPS quality of service |
| |
Initial PDP context activation | ||
Operator selection |
| |
Preferred message storage |
| |
Power Saving Mode setting |
| |
Service center address |
| |
Connection status signalling |
| |
Select character set configuration |
| |
Set greeting text |
| |
Select message service |
| |
Select message service |
| |
New message indication |
| |
Time zone reporting |
| |
Automatic time zone update |
| |
Baud rate |
| |
Band configuration |
| |
Frequency / Cell Lock | 0 (disabled cell/frequency locks) | |
Bearer Independent Protocol status indication | 0 (BIP status indication disabled)
| |
Uplink user data plane configuration |
| |
Default CID and preferred protocol type configuration | 1 (<cid>), 0 (IPv4) | |
SIM hot insertion detection | 0 (disabled) | |
Integrity check on test networks configuration |
| |
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) |
Restore factory configuration | 0 (no FS factory restore), 0 (no NVM factory restore) | |
FOTA reporting | ||
GPIO functionality setting |
| |
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) | |
Localization information request status unsolicited indication |
| |
LwM2M client activation/deactivation | ||
LwM2M reporting | ||
MAC QoS inactivity timer(s) |
| |
MNO profile configuration |
| |
NAS timers configuration |
| |
Set network adapter parameters |
| |
Controls the data path for the network adapter |
| |
NVM RAM mode management |
| |
Power saving control |
| |
USIM simulator and PS configuration | "REL": 13 (UE release 13), "PWC": 3 (UE power class 3) | |
Deep-sleep mode indication | 0 (deep-sleep mode URC disabled) | |
RING line handling | 0 (feature disabled (RING line is only asserted on incoming call and incoming SMS)) | |
Radio Policy Manager (RPM) configuration |
| |
Radio Policy Manager (RPM) parameters configuration |
| |
(U)SIM initialization status reporting | 0 (URC +UUSIMSTAT disabled) | |
Serial interfaces configuration |
| |
Antenna dynamic tuner | Antenna dynamic tuner control: 0 (disabled) | |
UART baud rate and flow control NVM management |
| |
URC reporting behavior configuration |
| |
USB profiles configuration | ||
Configures USB capability to allow module to enter sleep state | 0 (usb_allow_sleep), 0 (usb_min_allowed_sleep) | |
Automatic answer | ||
DCE response format |
|
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:
Write the run-time configuration (if changed) of the AT commands listed in Parameters stored in profiles to the NVM by means of the AT&W command (e.g. AT&W0)
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.
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.
Category | Estimated maximum time to get response | Commands |
---|---|---|
Power off |
| |
Set module functionality |
| |
Call control |
| |
Dial |
| |
Data connection commands |
| |
Network commands |
| |
Network commands | < 10 s | |
Network commands | < 5 s | |
Signal quality change reporting control | < 5 s | |
Security |
| |
Delete all SMSes | < 55 s | |
Send SMS |
| |
SMS acknowledgement to MT |
| |
Inline send message | < 60 s | |
SMS list message | < 10 s | |
Preferred message storage | < 10 s | |
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 |
| |
PDP context modification |
| |
Restore configuration | < 5 s | |
End user test (antenna dynamic tuner control) | < 5 s | |
GPIO commands | < 10 s | |
Internet suite (socket connect) |
| |
Internet suite (socket connect with SSL) |
| |
Internet suite (socket write) |
| |
Internet suite (UDP socket write) |
| |
Internet suite (socket closure) |
| |
Internet suite |
| |
Resolve name/IP number through DNS |
| |
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 | |
MQTT command |
| |
SNTP Command | < 45 s |
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) |
---|---|---|---|---|
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) | |
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) | |
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) | |
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) | |
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.