SARA-R4 / SARA-N4 AT Commands Manual - MultiTech

SARA-R4/N4 seriesSize-optimized LTE Cat M1 / NB1 / GPRS modulesAT Commands ManualAbstractDescription of standard and proprietary AT commands used with u-bloxcellular modules.www.u-blox.comUBX-17003787 - R13

SARA-R4/N4 series - AT Commands ManualDocument InformationTitleSARA-R4/N4 seriesSubtitleSize-optimized LTE Cat M1 / NB1 / GPRS modulesDocument typeAT Commands ManualDocument numberUBX-17003787Revision and dateR1324-Jun-2019Disclosure restrictionu-blox reserves all rights to this document and the information contained herein. Products, names, logos and designsdescribed herein may in whole or in part be subject to intellectual property rights. Reproduction, use, modification ordisclosure to third parties of this document or any part thereof without the express permission of u-blox is strictlyprohibited.The information contained herein is provided “as is” and u-blox assumes no liability for the use of the information. Nowarranty, either express or implied, is given, including but not limited, with respect to the accuracy, correctness, reliabilityand fitness for a particular purpose of the information. This document may be revised by u-blox at any time. For mostrecent documents, visit www.u-blox.com.Copyright 2018, u-blox AGu-blox is a registered trademark of u-blox Holding AG in the EU and other countries.UBX-17003787 - R13Page 2 of 326

SARA-R4/N4 series - AT Commands ManualPrefaceApplicable productsThis document applies to the following products:NameSARA-R404MType numberSARA-R404M-00B-00Modem versionK0.0.00.00.07.06Application versionN.A.PCN 07A.02.14A02.09UBX-19016568UBX-18057459How to use this ManualThe u-blox Cellular Modules AT Commands Manual provides the necessary information to successfully designin and configure the applicable u-blox cellular modules.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.Summary tableThe summary table on the top of each command section is a quick reference for the user.command nameModulesTOBY-L2 MPCI-L2LISA-U110 LISA-U120 LISA-U130 LISA-U2LEON-G1 SARA-G3SyntaxPIN requiredSettings saved Can be abortedAttributesfullNoNoNoResponse time-Error reference-It is composed of two sections: Modules: lists all the modules that support the command. The modules are grouped in rows by cellularstandard (i.e. L for LTE high data rate (Cat 3 and above), R for LTE low data rate (Cat 1 and below), Ufor UMTS/HSPA, G for GSM/GPRS, N for NB-IoT (LTE Cat NB1 / LTE Cat NB2)). In each row the modulesare grouped by: form factor (i.e. SARA, LISA), platform technology (e.g. SARA-G), platform generation(e.g. SARA-G3), product name (e.g. SARA-G350) and ordering code (e.g. SARA-G350-00S). In example: if'LISA-U2' is reported, the command applies to all the modules having LISA form factor, second chipsetversion provided with any release of firmware. Attributeso Syntax- full: the command syntax is fully compatible among all the products listed in the "Modules" section- partial: the products support different syntaxes (usually backward compatible with respect toprevious cellular standards)o PIN required- Yes: it is necessary to insert the PIN before the set and/or read command executionUBX-17003787 - R13PrefacePage 3 of 326

SARA-R4/N4 series - AT Commands Manual- No: the PIN insertion is not needed to execute the commando Settings saved- Profile: the command setting can be saved in a personal profile as specified in Chapter 1.2- NVM: the command setting is saved in the non-volatile memory as specified in Chapter 1.2- OP: the command setting can be overwritten by the Mobile Network Operator (MNO) profile set withthe UMNOPROF AT command (if supported)- No: the current command setting is volatile and cannot be savedo Can be aborted- Yes: the command execution can be aborted if a character is sent to the DCE during the commandexecution- No: the command cannot be aborted during the command executiono Response time: estimated maximum time to get the final result code for the AT command execution.More precisely, the command response time measures the time from the complete acquisition of thecommand line to the issuing of the command result code. This kind of response time is generally lowerthan the time measured by the application on the DTE, because the issuing of the command on theDTE is influenced by the AT interface characteristics (e.g. the synchronous/asynchronous transfer type,the selected baudrate, etc.), by power saving and flow control, which introduce a variable latency in thecommand acquisition by the DCE.For example, the maximum expected response time shall be extended if the communication with themodule is carried out on a MUX virtual port, because in this case the command line and the result codeare transferred via a specific protocol running on the physical port, that might introduce additionalcommunication delay due to framing and retransmissions.Similarly, the maximum expected response time of AT commands accessing the SIM shall be extendedif the module is using a remote SIM card via SAP instead of the local SIM card.If the response time for a command is left blank (actually "-"), it is an "immediate" response. It meansthat the command is executed without asynchronous requests to the protocol stack or the internalapplications, which usually require time to be answered: the command execution is synchronous(implying that no long blocking processing is done) and lasts a negligible time (the command responseis issued by the module in typically less than 10 ms, and in any case less than 1 s).The response time shall be extended if the issued AT command triggers a service that cannot be servedimmediately due to concurrent access to the same service or resource via AT commands issued on adifferent communication port or from internal applications; typical examples are registration commandsand SIM access, that can be also autonomously triggered by the module (e.g. auto-COPS) and cantherefore postpone the execution of the AT commands issued by the user.o Error reference: reference to the error result codes listed in the Appendix AThe attributes listed in the summary table apply by default to all u-blox modules supporting the specificAT command. If a u-blox module or module series does not comply to the default behavior, the exception ishighlighted in Chapter 1.2 for the saving of settings, in Chapter 1.1.6 for the abortability, and in a product specificnote in the AT command description for the PIN check.u-blox Technical DocumentationAs part of our commitment to customer support, u-blox maintains an extensive volume of technicaldocumentation for our products. In addition to our product-specific technical data sheets, the followingmanuals are available to assist u-blox customers in product design and development.AT Commands Manual: This document provides the description of the AT commands supported by u-bloxcellular modules.System Integration Manual: This document describes u-blox cellular modules from the hardware and thesoftware point of view. It provides hardware design guidelines for the optimal integration of the cellular modulein the application device and it provides information on how to set up production and final product tests onapplication devices integrating the cellular module.Application Notes: These documents provide guidelines and information on specific u-blox cellular modulehardware or software topics. For some guidelines when developing applications for LTE Cat M1 technologies, see the SARA-R4 / SARA-N4Application Development Guide [167].UBX-17003787 - R13PrefacePage 4 of 326

SARA-R4/N4 series - AT Commands Manual For some guidelines when developing applications for NB-IoT technologies, see the NB-IoT ApplicationDevelopment Guide [168]. For more examples of typical scenarios when developing application for LTE Cat 4, LTE Cat 1, UMTS/HSPAand GSM/GPRS technologies, see the AT Commands Examples Application Note [166].See Related documents for application notes related to your cellular module.QuestionsIf you have any questions about u-blox Cellular Hardware Integration, please: Read this manual carefully Contact our information service on our homepage www.u-blox.com Read the questions and answers on our FAQ databaseTechnical SupportWorldwide WebOur website (www.u-blox.com) is a rich pool of information. Product information, technical documents andhelpful FAQ can be accessed 24h a day.By E-mailIf you have technical problems or cannot find the required information in the provided documents, contactthe nearest of the Technical Support offices by email. Use our service pool email addresses rather than anypersonal email address of our staff. This makes sure that your request is processed as soon as possible. Youwill find the contact details at the end of the document.Helpful Information when Contacting Technical SupportWhen contacting Technical Support please have the following information ready: Module type (e.g. SARA-G350-00S-00) and firmware version (e.g. 08.49) Module configuration Clear description of your question or the problem A short description of the application Your complete contact detailsUBX-17003787 - R13PrefacePage 5 of 326

SARA-R4/N4 series - AT Commands ManualContents1AT command settings.111.11.21.31.42General operation.162.12.23Multiplexing mode CMUX. 24.135Start up and initialization. 16AT commands types. 17IPC - Inter Processor Communication.193.14Definitions. 11Storing of AT commands setting. 14S-parameters.15 UDCONF AT command. 15Manufacturer identification CGMI.21Manufacturer identification GMI.21Model identification CGMM.21Model identification GMM.22Firmware version identification CGMR. 22Firmware version identification GMR. 23IMEI identification CGSN.23IMEI identification GSN. 24Identification information I. 24TE character set configuration CSCS. 25International mobile subscriber identification CIMI.26Card identification CCID. 26Repeat last command A/. 27Mobile equipment control and status.285.1 Module switch off CPWROFF. 285.2 Set module functionality CFUN. 285.3 Indicator control CIND. 305.4 Configuration of indicator control UCIND. 315.5 Mobile termination event reporting CMER. 325.6 Clock CCLK.345.7 Set greeting text CSGT. 345.8 Automatic time zone update CTZU. 355.9 Report mobile termination error CMEE. 366Call control.376.16.26.37Dial command D. 37Call answer A. 38Hook control H. 38Network service. 397.17.27.37.47.57.67.77.87.97.10Subscriber number CNUM.39Signal quality CSQ. 39Extended signal quality CESQ. 41Operator selection COPS.42Radio Access Technology (RAT) selection URAT.44Network registration status CREG. 46Network selection control PACSP. 48Channel and network environment description UCGED. 49Edit Verizon wireless APN table VZWAPNE. 54Read RSRP values VZWRSRP. 55UBX-17003787 - R13ContentsPage 6 of 326

SARA-R4/N4 series - AT Commands Manual7.11 Read RSRQ values VZWRSRQ. 567.12 Signalling connection status CSCON.567.13 eDRX setting CEDRXS. 577.14 eDRX read dynamic parameters CEDRXRDP. 587.15 Set MNO profile UMNOPROF. 597.16 Band selection bitmask UBANDMASK. 617.17 Device service domain configuration USVCDOMAIN. 628Security. 648.18.28.39Short Messages Service. .159.169.179.189.199.209.219.229.2310Enter PIN CPIN. 64Facility lock CLCK. 65Change password CPWD. 66Introduction.68Select message service CSMS. 68Preferred message storage CPMS. 69Preferred message format CMGF. 70Save settings CSAS. 71Restore settings CRES.71New message indication CNMI.

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 avail