value

Integer: 0..127. Set the command line editing character to this value. The recommended default value is 8, i.e. the ‘Backspace’ character (BS, IA5 0/8).

value

Integer: 0..127. Set command line termination character to this value. The mandatory default value is 13, or ‘Carriage Return’ (CR, IA5 0/13).

value

Integer: 0 or 1.

Note:

The recommended default value is 1.

Table 2. value

Value	Description
0	DCE transmits limited headers, trailers and numeric text.
1	DCE transmits full headers, trailers and verbose response text.

value

Integer: 0 or 1.

Note:

The default value is 0, i.e. DCE does not echo characters.

Table 3. value

Value	Description
0	DCE does not echo characters during command state and online command state.
1	DCE echoes characters during command state and online command state.

enable

Integer: 0 or 1. Enable (1) or disable (0) the smart terminal. The default value is 1.

value

Integer: 0..127. Set response formatting character to this value. The recommended default value is 10, i.e. the Line Feed character (LF, IA5 0/10).

value

Integer: 0 or 1.

Note:

The recommended default value is 0.

Table 4. value

Value	Description
0	DCE transmits result codes.
1	Result codes are not transmitted.

charset

String.

CAUTION:

Only the ‘GSM’, ‘UCS2’, ‘UTF-8’ and ‘IRA’ types are supported.

Table 5. chset

Value	Description
‘GSM’	GSM 7 bit default alphabet (3GPP TS 23.038 [25]); this setting is not compatible with software flow control (XON/XOFF). Note: If MT is using GSM 7 bit default alphabet, its characters shall be padded with 8th bit (zero) before converting them to hexadecimal numbers (i.e. no SMS style packing of 7 bit alphabet).
‘HEX’	Character strings consist only of hexadecimal numbers from 00 to FF; e.g. ‘032FE6’ equals three 8-bit characters with decimal values 3, 47 and 230; no conversions to the original MT character set are attempted.
‘IRA’	International reference alphabet (see ITU T Recommendation T.50 [13]).
‘PCCPxxx’	IBM PC Code Page xxx
‘PCDN’	IBM PC Danish/Norwegian character set
‘UCS2’	16-bit coded Unicode character set (see ISO/IEC10646 [32]); UCS2 character strings are converted to hexadecimal numbers ranging from 0000 to FFFF; e.g. ‘004100620063’ equals three 16-bit characters with decimal values 65, 98 and 99.
‘UTF-8’	Byte (8-bit) based variable length encoding of Unicode (see RFC 3629 [69]); UTF-8 encodes each Unicode character as a variable number of bytes, where the number of bytes depends on the character code point. The input format must be a stream of bytes. It must not be converted to hexadecimal numbers as in ‘HEX’ or ‘UCS2’. This character set requires an 8-bit TA – TE interface.
‘8859-n’	ISO 8859-n Latin (1 ≤ n ≤ 6) character set
‘8859-C’	ISO 8859 Latin/Cyrillic character set
‘8859-A’	ISO 8859 Latin/Arabic character set
‘8859-G’	ISO 8859 Latin/Greek character set
‘8859-H’	ISO 8859 Latin/Hebrew character set

n

Integer. Enables or disables reporting of unsolicited result code +CCIOTOPTI.

Table 6. n

Value	Description
0	Disable reporting
1	Enable reporting
3	Disable reporting and reset the parameters for CIoT EPS optimisation to the default values.

supported_UE_opt

Integer: 0, 1, 2 or 3. Indicates the UE's support for CIoT EPS optimisations.

Note:

1 is the only supported choice in the current software release.

Table 7. supported_UE_opt

Value	Description
0	No support.
1	Support for control plane CIoT EPS optimisation.
2	Support for user plane CIoT EPS optimisation. (Not supported)
3	Support for both control plane CIoT EPS optimisation and user plane CIoT EPS optimisation. (Not supported)

preferred_UE_opt

Integer: 0, 1 or 2. Indicates the UE's preference for CIoT EPS optimisations.

Note:

1 is the only supported choice in the current software release.

Table 8. preferred_UE_opt

Value	Description
0	No preference.
1	Preference for control plane CIoT EPS optimisation.
2	Preference for user plane CIoT EPS optimisation. (Not supported.)

supported_Network_opt

Integer: 0, 1, 2 or 3. Indicates the Network support for CIoT EPS optimisations.

Note:

1 is the only supported choice in the current software release.

Table 9. reporting

Value	Description
0	No support.
1	Support for control plane CIoT EPS optimisation.
2	Support for user plane CIoT EPS optimisation. (Not supported.)
3	Support for both control plane CIoT EPS optimisation and user plane CIoT EPS optimisation. (Not supported.)

reporting

Integer: 0 or 1. Enable or disable reporting.

Table 10. reporting

Value	Description
0	Disable reporting of MT control plane data.
1	Enable reporting of MT control plane data by the unsolicited result code +CRTDCP.

cid

Integer. A numeric parameter which specifies a particular PDP context or EPS bearer context definition. The <cid> parameter is local to the TE-MT interface and identifies the PDP or EPS bearer contexts which have been setup via AT command (see the AT+CGDCONT and AT+CGDSCONT commands).

cpdata_length

Integer. Size of the <cpdata> information element in bytes. 0 when there are no data to transmit.

cpdata

Byte string. User data container contents (refer to 3GPP TS 24.301 [83] sub-clause 9.9.4.24). When there is no data to transmit, the <cpdata> must be empty (""). This parameter must not be converted as defined by the AT+CSCS command. The coding format of the user data container and the maximum length of <cpdata> are implementation specific.

• Is expected to be completed with this uplink data transfer; or
• Is expected be completed with the next received downlink data.

cid

Integer. A numeric parameter which specifies a particular PDP context or EPS bearer context definition. The <cid> parameter is local to the TE-MT interface and identifies the PDP or EPS bearer contexts which have been setup via AT command (see the AT+CGDCONT and Define Secondary PDP Context: AT+CGDSCONT commands).

cpdata_length

Integer. <cpdata> length in bytes. 0 if there are no data to transmit.

cpdata

Byte string. User data container contents (refer to 3GPP TS 24.301 [83] sub-clause 9.9.4.24). When there is no data to transmit, the <cpdata> must be empty (""). This parameter must not be converted as defined by the Select TE Character Set: AT+CSCS command. The coding format of the user data container and the maximum length of <cpdata> are implementation specific.

RAI

Integer: 0, 1 or 2. Value of the Release Assistance Indication, Release 13. Refer to 3GPP TS 24.301 [83] sub-clause 9.9.4.25.

Table 11. RAI

Value	Description
0	No information
1	No further uplink or downlink data transmissions are expected
2	Only a single downlink data transmission is expected

type_of_user_data

Integer: 0 or 1. Regular or exception data.

Table 12. type_of_user_data

Value	Description
0	Regular data
1	Exception data

serial

String (max. 64 characters). Device serial number.

imeisv

String. IMEISV (International Mobile station Equipment Identity and Software Version number). Refer to 3GPP TS 23.003 [7], sub-clause 6.2.2. The 16 digits of IMEISV are composed of Type Allocation Code (TAC) (8 digits), Serial Number (SNR) (6 digits) and the software version (SVN) (2 digits). The character set used is specified using the command Select TE Character Set: AT+CSCS.

ue_version

String. The module’s software version.

lr_version

String. Identical to <ue_version> with the build number added.

hwversion

String. The module’s hardware version.

lasermarking

String. The laser marking as engraved on the module’s top casing.

ATI
SEQUANS Communications
GM02S
UE8.2.2.1
OK
ATI1
UE8.2.2.1
LR8.2.2.1-63473

ATI2
SERIAL: G2Q2106160008013
IMEISV: 0157700008800111
OK

IMSI

String (without double quotes). International Mobile Subscriber Identity.

manufacturer

String. The total number of characters, including line terminators, in the information text shall not exceed 2,048 characters. Text must not contain either ‘0<S3>’ or ‘OK<S3>’. Here, <S3> represents the value of the command line termination character. See Command Line Termination Character: ATS3

model

String. The total number of characters, including line terminators, in the information text must not exceed 2048 characters. Text must not contain the sequence 0<S3> or OK<S3>. Here <S3> represents the value of the command line termination character. See ATS3.

snt

Integer: 0, 1, 2 or 3. Serial number type requested.

Table 13. snt

Value	Description
0	returns <sn>
1	returns the IMEI (International Mobile station Equipment Identity)
2	returns the IMEISV (International Mobile station Equipment Identity and Software Version number)
3	returns the SVN (Software Version Number)

sn

String. One or more lines of information text determined by the MT manufacturer. Typically, the text will consist of a single line containing the IMEI number of the MT, but manufacturers may elect to provide more information if desired. The total number of characters, including line terminators, in the information text must not exceed 2048 characters. Text must not contain the sequence 0<CR> or OK<CR>

imei

String in decimal format. IMEI: refer to 3GPP TS 23.003 [7], sub-clause 6.2.1. IMEI is composed of: the Type Allocation Code (TAC) (8 digits), the Serial Number (SNR) (6 digits) and the Check Digit (CD) (1 digit). Character set used in <imei> is specified using the command Select TE Character Set: AT+CSCS.

imeisv

String in decimal format. IMEISV: refer to 3GPP TS 23.003 [7], sub-clause 6.2.2. The 16 digits of IMEISV are composed of: the Type Allocation Code (TAC) (8 digits), the Serial Number (SNR) (6 digits) as per ETSI 3GPP TS 27.007 version 12.10.0 Release 12 23 ETSI TS 12 007 V12.10.0 (2015-10) and the software version (SVN) (2 digits). Character set used in <imeisv> is specified using the command Select TE Character Set: AT+CSCS.

svn

String in decimal format. Current SVN which is a part of IMEISV; refer 3GPP TS 23.003 [7], sub-clause 6.2.2. This allows identifying different software versions of a given mobile. Character set used in <svn> is specified using the command Select TE Character Set: AT+CSCS.

Note:

The default value <snt>=0 returns the information text <sn> without he command name prefix, so as to keep backward compatibility. All other values of <snt> return the information text including the command name prefix.

• To get <sn> which returns IMEI of the MT

  AT+CGSN 
  490154203237518
  OK

• To get <imei> which returns IMEI of the MT

  AT+CGSN=1 
  +CGSN: "490154203237518" 
  OK

revision

String. The total number of characters, including line terminators, in the information text must not exceed 2048 characters. Text must not contain the sequence 0<CR> or OK<CR>

time

See parameter time in Clock: AT+CCLK

If the <recurr> parameter is used, then the <time> parameter must not contain a date.

n, n1, n2

Integer. Index of the alarm; default is manufacturer specific.

type

Integer. Type of the alarm (e.g. sound, volume, LED); values and default are manufacturer specific.

text

String. Text to be displayed when alarm goes off; maximum length <tlength>; values and default are manufacturer specific.

tlength

Integer. Maximum length of <text>.

recurr

String. Day(s) of the week for the alarm in one of the following formats (values and default are manufacturer specific).

Table 14. recurr

Value	Description
0	Alarm goes off every day.
1..7	Sets a recurrent alarm for one or more days of the week. The digits 1 to 7 corresponds to the days of the week, Monday (1) to Sunday (7). The string "1,2,3,4,5" sets an alarm every weekday.

rlength

Integer. Maximum length of <recurr>.

silent

Integer: 0 or 1. Specify whether the alarm is silent or not.

Table 15. silent

Value	Description
0	The alarm is not silent
1	The alarm is silent and its only effect is to send a +CALV URC

autoconnect

Integer: 0 or 1. Autoconnect Mode.

Table 16. autoconnect

Value	Description
0	Autoconnect is disabled.
1	Autoconnect is enabled.

forceautoconnect

Integer: 0 or 1. Force autoconnect Mode.

Table 17. forceautoconnect

Value	Description
0	ForceAutoconnect if disabled, the Autoconnect is overriden to 0 in case of "3gpp-conformance", "verizon-conformance"
1	ForceAutoconnect is enabled.

AT+SQNAUTOCONNECT=1 
OK

AT+SQNAUTOCONNECT? 
+SQNAUTOCONNECT: 1 
OK

• If the measured voltage goes below <threshold>, then the +SQNVMONS notification is issued
• After three seconds, if module is still below the threshold and <mode> is set to 2 or 4, the device sends a new URC (+SQNVMONS: <mode>,10,<voltage>) and triggers an emergency shutdown procedure.

mode

Integer: 0..4. Voltage monitoring mode:

Table 18. mode

Value	Description
0	Default value, voltage monitoring disabled.
1	Voltage monitoring activated only during active mode. +SQNVMONS URC activated.
2	Voltage monitoring activated only during active mode. +SQNVMONS URC activated. Automatic emergency shutdown enabled 3 s after the first +SQNVMONS URC is sent.
3	Voltage monitoring activated during active mode and deep sleep mode. +SQNVMONS URC activated.
4	Voltage monitoring activated during active mode and deep sleep mode. +SQNVMONS URC activated. Automatic emergency shutdown enabled 3 s after the first +SQNVMONS URC is sent.

threshold

Integer: 22..55. Low voltage threshold in tenths of volts. The default value is 25 (i.e. 2.5 V).

status

Integer: 0, 1 or 10. Voltage monitoring status.

Table 19. status

Value	Description
0	Above threshold.
1	Below threshold.
10	Below threshold, shutdown procedure started.

voltage

Integer 22..55. Current VBAT voltage in tenths of volts.

period

Integer. Time between two VBAT measurements. Default is 30 s.

time

String. Format is "yy/MM/dd,hh:mm:ss+zz", where characters indicate year (two last digits), month, day, hour, minutes, seconds and the ‘GMT offset’, computed as the difference in quarters of an hour, between the local legal time and GMT; range is -96...+96). E.g. 6th of May 1994, 10:10:00 PM GMT+2 hours equals to "94/05/06,22:10:00+08"

ctm

String. Operator Mode.

Table 20. ctm

Value	Description	Applicable RATs
"standard"	Standard 3GGP mode.	all
"3gpp-conformance"	Standard 3GGP mode to pass GCF tests.	all
"verizon"	Verizon’s requirements and specific settings mode.	all
"att"	ATT’s requirements and specific settings mode.	LTE-M
"tmo"	T Mobile’s requirements and specific settings mode.	LTE-M
"telstra"	Telstra’s requirements and specific settings mode.	all
"kddi"	KDDI’s requirements and specific settings mode.	LTE-M
"docomo"	Docomo’s requirements and specific settings mode.	LTE-M

RAT

Integer: 1 or 2. Radio Access Technology. 1: LTE-M; 2: NB-IoT.

AT+SQNCTM="3gpp-conformance" 
OK 
AT^RESET

AT+SQNCTM? 
+SQNCTM: 3gpp-conformance
OK

format

Integer: 0..6. Number of bits in the data bits, the presence of a parity bit, and the number of stop bits in the start-stop frame. Default value is 3.

Note:

The semantics of this command are derived from ITU-T Rec. V.58.

Table 21. format

Value	Description
0	Autodetect
1	8 Data ; 2 Stop
2	8 Data ; 1 Parity ; 1 Stop
3 (default)	8 Data ; 1 Stop
4	7 Data ; 2 Stop
5	7 Data ; 1 Parity ; 1 Stop
6	7 Data ; 1 Stop

parity

Integer: 0..3. Parity bit generation and verification, if present. Default value is 3.

Table 22. parity

Value	Description
0	Odd
1	Even
2	Mark
3 (default)	Space

• Read syntax

  AT+ICF?
  +ICF: 3,3

  for the recommended defaults.
• Test syntax

  AT+ICF=?
  +ICF: (0-6),(0-3)

  for all defined values.

• <DCE_by_DTE>, which specifies the method to be used by the DTE to control the flow of received data from the DCE;
• <DTE_by_DCE>, which specifies the method to be used by the DCE to control the flow of transmitted data from the DTE.

DCE_by_DTE

Integer: 0 or 2. Method to be used by the DTE to control the flow of received data from the DCE. Recommended default value is 2.

Note:

The semantics of this command are derived from ITU-T Rec. V.58.

Table 23. DCE_by_DTE

Value	Description
0	None
2	Circuit 133 (Ready for Receiving)

DTE_by_DCE

Integer: 0, 1 or 2. Specifies the method to be used by the DCE to control the flow of transmitted data from the DTE. Recommended default value is 2.

Table 24. DTE_by_DCE

Value	Description
0	None
1	DC1/DC3 on circuit 104 (not supported)
2	Circuit 106 (Clear to Send/Ready for Sending)
3 to 12	Reserved for future standardisation
Other	Reserved for manufacturer-specific use

• Read syntax

  +IFC?
  +IFC:2,2

  for the recommended defaults.
• Test syntax

  +IFC=?
  +IFC:(0,2),(0-2)

  for all defined values.

n

Integer: Index of the alarm to reset; default is manufacturer specific.

enable

Integer: 0 or 1. Activate or deactivate LwM2M:

Table 25. enable

Value
0	Disable LwM2M.
1	Enable LwM2M.

rate

The value specified shall be the rate in bits per second at which the DTE-DCE interface should operate, e.g., "19200" or "115200". The rates supported by a particular DCE are manufacturer-specific; however, the AT+IPR parameter should permit the setting of any rate supported by the DCE during online operation. Rates which include a non-integral number of bits per second should be truncated to the next lower integer (e.g., 134.5 bit/s should be specified as 134; 45.45 bit/s should be specified as 45).

Note:

0 (automatic detection) or unspecified values are not currently supported.

persistence

Integer: 0 or 1.

Table 26. persistence

Value	Description
0	Disabled. The AT+IPR settings are lost at reboot
1	Enabled (default). The AT+IPR settings are kept at reboot

• Read syntax:

  AT+IPR?

  The DCE transmits a string of information text to the DTE, consisting of +IPR: <rate>.
  • +IPR: 0 if set for automatic rate detection.
  • +IPR: 9600 if set to 9600 bit/s.
• Test syntax:

  AT+IPR=?

  The DCE transmits one or two strings of information text to the DTE, consisting of +IPR: (list of supported autodetectable <rate> values)[,(list of fixed-only <rate> values)], for example +IPR: (0,300,1200,2400,4800,9600),(19200,38400,57600) if the DCE can auto-detect up to 9600 bit/s and can support three additional higher fixed rates.

• Setting GPIOs as outputs with a given value.
• Setting GPIOs as inputs and reading their value.

gpio

String. Name of the GPIO as defined in the product’s data sheet.

direction

String. Either "input" or "output".

polarity

String.

Table 27. polarity

Value	Meaning
"normal"	A ‘high’ logic level corresponds to a ‘high’ voltage input/output.
"inversed"	A ‘high’ logic level corresponds to a ‘low‘ voltage input/output and vice-versa.

Attention:

The second value is ‘inversed’ with a ‘s’ and NOT ‘inverted’ with a ‘t’.

value

String.

Table 28. value

Value
"low"	GPIO logic value is ‘low’.
"high"	GPIO logic value is ‘high’.

AT+SQNGPIO="gpio1"
gpio1: normal output high
OK

AT+SQNGPIO="gpio25"
gpio25: inversed input low
OK

• Host Device Unique ID
• Host Device Manufacturer
• Host Device Model
• Host Device Software Version

• When in operational or screening mode:
  • The read command displays all host device identity resources except for the ‘Host Device Unique ID’ which will be hidden (Null value).
  • The write command returns ERROR. Configuration change is forbidden in this mode.

huid

String. Host Device Unique ID string. Printable characters only. Max length: 64 chars.

hman

String. Host Device Manufacturer. Printable characters only. Max length: 64 chars.

hmod

String. Host Device Model. Printable characters only. Max length: 64 chars.

hsw

String. Host Device Software Version. Printable characters only. Max length: 64 chars.

pid

Integer: 0 or 1. Portfolio instance ID. Default value is 0.

• In operational mode:

  AT+ODIS? 
  +ODIS: 0,0, <--- null value (not in manufacturing mode) 
  +ODIS: 0,1,HMAN0 
  +ODIS: 0,2,HMOD0 
  +ODIS: 0,3,HSW0 
  +ODIS: 1,0, <--- null value (not in manufacturing mode) 
  +ODIS: 1,1,HMAN1 
  +ODIS: 1,2,HMOD1 
  +ODIS: 1,3,HSW1 
  OK 
  AT+ODIS=0,"MyID","MyManufacturer","MyModel","MySW" 
  ERROR

latency

Integer: 0..10000 (default: 5000). Maximum wake-up latency in milliseconds. The module enters the deepest power saving mode compatible with the required wake-up time. Configuring a maximum latency below the suspend wake-up time (about 4 seconds) typically prevents the module to sleep.

mode

Integer: 0, 1 or 2. RING line behaviour for signalling URCs, both when the interface is idle and reserved, i.e. while busy on AT command execution or data transmission. This functionality serves to fine-tune the conditions under which the ME signals service request to the TE.

Table 30. mode

Value	Description
0	URCs are not indicated by a RING line.
1	(default): URCs are indicated by an activated ring line on the same interface where the URC appears. If URC is presented on AT channel mapped to UART0, then RING line will be activated. If URC happen on an AT channel not mapped to UART0, then the RING line is unaffected.
2	All URCs are indicated by the RING line of the UART0 interface, irrespective of their origin.

events

Integer: 0..3. Event.

Table 31. events

Value	Description
0	No RING activation
1	RING activation triggered by general URC events
2	RING activation triggered by data events
3	(default): RING activation triggered by general URC events and data.

timout

Integer: 100..5000 (Default: 1000). RING line active duration in milliseconds.

This parameter determines how long the RING line is activated to indicate a URC or pending data. No value means no change.

• Read configuration:

  AT+SQNRICFG? 
  +SQNRICFG: 1,3,1000 
  OK
                          

• Write default configuration and read again:

  AT+SQNRICFG 
  OK 
  AT+SQNRICFG? 
  +SQNRICFG: 2,3,1000 
  OK
                      

• Write other configuration and read again:

  AT+SQNRICFG=0,0 
  OK 
  AT+SQNRICFG? 
  +SQNRICFG: 0,0,1000 
  OK
                      

• AT+SQNSNVR="certificate"[,<index>[,<mode>]]

  This command dumps all the certificates stored in the system. According to the value of <mode>, the command displays either the first 8 bytes and the last 8 bytes of the certificates, separated by [...] (this is the defaut if <mode> is absent), or the SHA-1 hash of the DER formatted certificates.

  If <index> is provided, only the certificate at <index> is displayed. ERROR is reported if the entry is empty.

  If <index> is not provided, all defined certificates are displayed, one per line.

• AT+SQNSNVR="privatekey"[,<index>[,<mode>]]

  This command dumps all the private keys stored in the system. According to the value of <mode>, the command displays either the first 8 bytes and the last 8 bytes of the private keys, separated by [...] (this is the defaut if <mode> is absent), or the SHA-1 hash of the DER formatted private keys.

  If <index> is provided, only the private key at <index> is displayed. ERROR is reported if the entry is empty.

  If <index> is not provided, all defined private keys are displayed, one per line.

• AT+SQNSNVR="strid"[,<index>]

  Deprecated. Do not use.

type

String: Type of data.

"certificate": Certificate data.

"privatekey": Private key data.

index

Integer: 0..19. Certificate index.

mode

Integer: 0 or 1. Private key representation:

• 0: Partial PEM representation (full content is hidden for security reasons).
• 1: SHA-1 hash of the DER formatted private key.

issuer

String: Certificate issuer (Entity that verified the information and issued the certificate).

serial-number

String: Certificate serial number.

subject

String: Certificate subject (person or entity identified).

valid-from

String: Certificate inception date.

valid-to

String: Certificate expiration date.

signature-algorithm

String: Certificate signature algorithm.

signature

String: Certificate signature.

thumbprint-algorithm

String: Certificate thumbprint algorithm (hash algorithm).

thumbprint

String: SHA1 hash value of the certificate in PEM form.

• Read certificate at index 3

  AT+SQNSNVR="certificate",3
  
  +SQNSNVR: 
  "certificate",3,"/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert Global Root CA",
  "0000000000000000","/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert Global Root CA",
  "06/11/10 00:00:00","31/11/10 00:00:00","sha1RSA",
  "00000000000000[…]0000","sha1","4418290c0af661843b28c70f4eb728f4cc462960"

• Read all certificates:
  Note:

  All certificate data is not displayed in the example below. Shortened sections are identified by ‘[…]’.

  AT+SQNSNVR="certificate" 
  +SQNSNVR: "certificate",0,
  "/C=US/O=VeriSign, Inc./OU=VeriSign Trust Network/OU=(c) 2006 VeriSign, Inc.
   - For authorized use only/CN=VeriSign Class 3 Public Primary Certification Authority - G5",
  "0000(...)00000",
  "/C=US/O=VeriSign, Inc./OU=VeriSign Trust Network/OU=(c) 2006 VeriSign, Inc.
   - For authorized use only/CN=VeriSign Class 3 Public Primary Certification Authority - G5",
  "06/11/08 00:00:00","36/07/16 23:59:59","sha1RSA","0000(…)0000","sha1",
  "b054ec81256dc47f1f0360e38fe30d6ccba35424" 
  +SQNSNVR: "certificate",1,
  "/OU=Amazon Web Services O=Amazon.com Inc. L=Seattle ST=Washington C=US",
  "0000000(...)0000000000",
  "/CN=AWS IoT Certificate","18/01/03 07:06:00","49/12/31 23:59:59",
  "sha256RSA","000000(…)0000","sha1","f6bb69bdc40afedb840e6854749db37c74501e6b" 
  OK

• read a single private key:

  AT+SQNSNVR="privatekey",2
  +SQNSNVR: 1,"-----BEGIN RSA PRIVATE KEY----- 
  MIIFQTCC [...] 4PsJYGw= 
  -----END RSA PRIVATE KEY-----

mode

0 or 1. Configures the LTE LED mode. This setting persists at reboot.

Table 32. mode

Value	Description
0 (default)	Blink mode Off. The LED is switched off.
1	Blink mode On. The LED will blink according to the system state.

value

Integer: 0.

Table 33. value

Value	Description
0	Set parameters to factory defaults.
Other	Reserved for manufacturer proprietary use.

• 0: Extreme low temperature range: below <extremeLow>
• 1: Low temperature range: from <extremeLow> to <warningLow>.
• 2: Operational range: from <warningLow> to <warningHigh>.
• 3: High temperature range: from <warningHigh> to <extremeHigh>.
• 4: Extreme high temperature range: above <extremeHigh>.

• When the modules enters a new thermal operation range, the +SQNTMONS notification is issued.
• To avoid fluctuations, a non-configurable hysteresis of ± 2 °C is applied to the raw temperature.
• Operating in low or high temperature ranges is still safe.

mode

Integer: 0, 1 or 2. Temperature monitoring mode.

Table 34. mode

Value	Description
0	Default value. Temperature monitoring disabled.
1	Temperature monitoring activated with +SQNTMONS URC activated.
2	Temperature monitoring activated with +SQNTMONS URC activated and automatic emergency shut-down enabled.

extremeLow

Integer: -100..100. Extreme low temperature threshold in °C. Default value is -40.

warningLow

Integer: -100..100. Warning low temperature threshold in °C. Default value is -30.

warningHigh

Integer: -100..100. Warning high temperature threshold in °C. Default value is 80.

extremeHigh

Integer: -100..100. Extreme high temperature threshold in °C. Default value is 90.

status

Integer. Temperature monitoring status:

Table 35. status

Value	Description
-2	Below extreme low temperature limit.
-1	Below low temperature limit.
0	Normal operating temperature.
1	Above high temperature alert limit.
2	Above extreme high temperature limit.
10	Extreme temperature timer expired, shut-down procedure started.

temperature

Integer. Current board temperature in Celsius.

AT+SQNTMON=? 
+SQNTMON: (0-2),(-100-100),(-100-100),(-100-100),(-100-100) 
OK

• In <mode>=0, power saving is disabled. UART0, UART1, UART2 interfaces are permanently activated and the module never enters sleep mode.
• In <mode>=1, power saving is activated. UART0 interface is activated with sleep mode support (RTS0 line). UART1 and UART2 interfaces do not interfere on module power saving behaviour. The module does not enter sleep mode as long as the RTS0 line state is low.
  Note:

  In <mode>=1, in order to ignore RTS1 line, it is necessary to disable the wakeRTS1 signal during product manufacturing using AT+SQNHWCFG="wakeRTS1","disable”. Please refer to the GM02S Module Manufacturing Guide for futher information.
• In <mode>=2, power saving is activated. UART0/UART1/UART2 interfaces are activated with sleep mode support (RTS0/1/2 lines) whenever applicable (hardware flow control supported and activated on UART interface). The module does not sleep until all RTS lines are high.

• If the RTS line state is set to OFF, the power saving mode is allowed.
• If the RTS line state is set to ON, the module exits from power saving mode.

• When no activity is detected on the UART, the CTS line will be set to OFF state (driven high level) <timeout> milliseconds (100 ms to 10 s, default 5 s) after the last sent character, then the module goes into sleep mode as soon as the DTE set the RTS line to OFF state (driver high level).
• When the module is in sleep mode, it can be waken-up by driving the RTS0 line (<mode>=1 or 2) or one of RTS1/2 lines (<mode>=2) to ON state (low level). After RTS0/1/2 assertion (RTS line set ON state, e.g. pin set to low level), and module waken-up, CTS line signals will change to ON state (low level), stating UART interfaces are ready to operate.

• UART sleep mode support requires that CTS/RTS flow control be configured both on the UE side and the DTE side.
• If <mode>=1 or 2 the DTE can start sending data to the module without risk of data loss after having asserted the UART RTS line.
• Factory default is <mode>=2, <timeout>=5000 ms.

mode

Integer: 0, 1 or 2. UART power saving mode.

Table 36. mode

Value	Description
0	Power saving is disabled. UART0, UART1, UART2 interfaces are permanently activated and the module never enters sleep mode.
1	Default value. Power saving is activated. UART0 interface is activated with sleep mode support. The module’s power state is controlled by the RTS0 line
2 (default)	Power saving is activated. UART0/UART1/UART2 interfaces are activated with sleep mode support whenever applicable (HW flow control activated). The module power state is controlled by the RTS0, RTS1 and RTS2 lines.

timeout

Integer: 100..10000 (default: 5000). Inactivity time-out in milliseconds. In sleep modes (<mode>=1 or 2), this is the guard period during which no character should be received on UART before module entering in sleep mode. This parameter is ignored if the power saving mode is disabled (<mode>=0).

• ATE
• ATV
• ATQ
• AT&C
• AT&D
• AT&S
• ATS3
• ATS4
• AT+IFC
• AT+ICF
• AT+IPR

profile

Integer: 0. Only 0 is supported.

• AT+SQNSNVW="certificate",<index>,<size>

  The form with "certificate" writes a single certificate, or several concatenated certificates, in the non volatile memory. Once the operation is completed, public certificates are immediately available for all client secured IP connection (Device Initiated Upgrade: AT+SQNSUPGRADE, Secured socket). For secured sockets in server mode, the certificate <index> must be used to assign private certificate to the secure server.

  An <index> must be provided for the system to identify the certificate (or bundle thereof) in future operations (delete, etc.)

  The <size> parameter gives the size in bytes of the certificate to upload: after the command is issued, the user must provide the certificate size in bytes using the PEM (Privacy-enhanced Electronic Mail) format. Once <size> bytes have been received, the operation is automatically completed. If the certificate is successfully uploaded and verified, the response is OK. If the upload fails for some reason, then an error code is reported. Maximum <size> for certificates is 8 kB.

  Writing a zero byte certificate at ID <index> deletes the certificate stored at that index. Attempting to delete a non-existent certificat returns ERROR.

• AT+SQNSNVW="privatekey",<index>,<size>

  This form of the command writes a private key in PEM format to the non-volatile memory. Maximum <size> for private keys is 2 kB.

  Note:

  Password encrypted private RSA keys are not supported.

  Note:

  The MQTT broker can provide certificates and private keys files with <CR><LF> (Carriage Return and Line Feed) endings. The parameter <size>, however, must not take the <CR> characters into account. To remove the <CR>s, use the following command on UNIX: cat file_with_cr | tr -d \015 > no_cr_file
• AT+SQNSNVW="strid",<index>,<size>

  Deprecated. Do not use.

type

String: Type of data.

"certificate": Certificate data.

"privatekey": Private key.

"strid": Generic string.

index

Integer: 0..19. Certificate, private key or string index.

CAUTION:

Indexes 0 to 4 and 7 to 10 are reserved for Sequans’s internal use. Do not change their contents.

size

Integer: Size in bytes of the certificate, private key or string to upload. A '0' value removes the corresponding entry. See above for individual limits.

Important:

The NVRAM has a maximum user capacity of 200 kB. Any attempt to store new data beyond that limit fails with ERROR.

• Certificate upload at index 5:

  AT+SQNSNVW="certificate",5,1346 
  -----BEGIN CERTIFICATE----- 
  MIIDXTCCAkWgAwIBAgIJAJC1[…]j3tCx2IUXVqRs5mlSbvA== 
  -----END CERTIFICATE----- 
  OK

• Delete certificate at index 5:

  AT+SQNSNVW="certificate",5,0 
  OK

• Upload client private key with keyid 6:

  $ AT+SQNSNVW="privatekey",6,1675 
  > -----BEGIN RSA PRIVATE KEY----- 
  ... 
  -----END RSA PRIVATE KEY----- 
  OK

firmware_url

String. URL (compliant with RFC1738) of the firmware (protocol://user:password@host:port/path):

• URL where to fetch the source (max. 4096 chars): <firmware_url> = "http(s)://…" or "ftp(s)://…"

This command supports FTP(S) and HTTP(S) protocols, in addition to direct file fetching.

reboot

Integer: 0 or 1.

Table 37. reboot

Value	Description
0	No reboot after the firmware is downloaded. The user must reboot the device to activate the new firmware
1	Default value. Reboot is triggered after the firmware is installed

Note:

Due to current software implementation, the module will trigger a delayed software update when resuming operation from deep sleep mode (as opposed to mere sleep mode)

report_progress

Integer: 0..100.

Table 38. report_progress

Value	Description
0	Default value. Don’t report download progress
1..100	report download progress using +SQNSUPGRADE: "downloading", <percent_downloaded> URC.

command

Integer: 0..4

Table 39. command

Value	Description
0	Default value. Synchronous upgrade.
1	Asynchronous upgrade. The command launches the upgrade and returns immediately OK if upgrade is started correctly or CME ERROR (see below for specific error codes). The command report upgrade progress with +SQNSUPGRADE URC.
2	Cancel upgrade. Cancels the upgrade if any has started or does nothing, then returns OK. In case of a network initiated firmware upgrade, the network is notified with an upgrade cancelled error code.
3	Suspend upgrade (asynchronous mode only). This command can be used to download the code in several chunks. The downloaded chunk is saved into non-volatile memory.
4	Resume upgrade. This is used in conjunction with the entry above to resume downloading after its suspension.

spId

Integer: 0..6. Security profile number (see AT+SQNSPCFG command) for https download

If the firmware is downloaded over a secure connection, SSL/TLS properties settings should be provided through a secure profile managed by AT+SQNSPCFG. In such a scenario, the user should clearly identify which configuration to use by adding the mandatory <spId> parameter. Any attempt to open a secure connection without a valid security profile will fail.

upgrade_state

String.

Table 40. upgrade_state

Value	Description
"cancelled"	The upgrade has been cancelled.
"connecting"	The device is currently waiting for the connection to be established.
"downloading"	Report the downloading progress. This state is followed with <percent_downloaded>. This information is displayed only if <report_progress> has not been set to 0.
"suspend"	Download has been paused, waiting for a resume command.
"idle"	No upgrade is ongoing.
"installed"	The upgraded is installed and will be effective after the next reboot.
“available”	A new firmware is available for download (network initiated firmware upgrade only).
“rebooting”	This notification is sent just before the device reboot which finalises the system upgrade.

percent_downloaded

Integer: 0..100. Percentage of image downloaded.

AT+SQNSUPGRADE? 
+SQNSUPGRADE: "idle" 
OK

• Trigger periodic (modem initiated) or on demand (device initiate) FOTA checks.
• Receive FOTA activity progress indications.

• Bootstrap information: URL, security material (PSK identify, PSK Secret, etc.).
• APN to be used for all communications with the FOTA server(s).

• ‘automatic’ mode (default mode):
  • The FOTA client operates in the background, doing periodic checks, upgrade package download and installation as described in the LWM2M specification (including a module final reboot necessary to complete the upgrade procedure) whenever required, independently of the user application.

• <report_state>: specifies FOTA client state change indication (+SQNFOTA) reporting level.
• <report_download>: specifies software upgrade package download progress indication reporting percentage step.

• <fota_timer_sec>: modem initiated FOTA check period (based on OMA registration lifetime resource value /1/x/1 for particular DM server). If the value is provided, the command relies on server-defined registration lifetime obtained during onboarding process.
  Note:

  This timer is volatile, and can be reset by the server at any time. If that happens, the URC notification communicates the new value. The read command AT+SQNFOTACFG? reports both requested and current values.
• <download_to_sec> Integer 60..65535. Download timeout in seconds (optional).
  • OUTBAND FOTA only: Maximum time in seconds allowed for the software package download. This timeout is typically useful to prevent sluggish downloads due to slow network or cellular connection going down during operation. The timer must be consistent with the estimated network speed capability to avoid aborting valid but slow operations. In case of timeout during an upgrade file data transfer and if the download protocol supports resume function (HTTP/HTTPS), the download will resume at the next FOTA timer or the next device download request. If the parameter is omitted, the download resume logic is applied.

upg_profile

String. Upgrade service profile name.

• Maximum length is 32 characters
• When upgrade service is provided by a device management service, the profile name shall reference a valid device management configuration profile (see AT+SQNDMCFG).

mode

Integer: 0 (Automatic Mode Only).

• 0 (default): Automatic mode with FOTA client activity managed in background without user intervention.

report_state

Integer: 0, 1 or 2. FOTA client state change indication (+SQNFOTA) reporting level.

• 0: Notification disabled
• 1: state change reporting enabled
• 2(default) : state change and intermediate error reporting enabled

report_download

Integer: 0..100. Specifies software upgrade package download progress indication reporting percentage step.

• 0 (default): do not report download progress indication
• 1..100: download progress indication reported at each configured percentage step

fota_timer_sec

Integer: 60..32000000. FOTA periodic timer (optional).

• FOTA client periodic timer used to trigger FOTA check or resume a paused FOTA activity.
• This value is volatile and can be changed at any time by the server. The read command will display both the requested value and the value currently in use. If the value is omitted, the client will use the value provided by the server.

download_to_sec

Integer: 60..65535. Download timeout in seconds (optional).

• OUTBAND FOTA only: Maximum time in seconds allowed for the software package download. This timeout is typically useful to prevent infinite download due to slow network or cellular connection going down during operation. Timer shall be set consistently with estimated network speed capability to avoid aborting perfectly normal but slow operations. In case of timeout expiration during upgrade file data transfer and if download protocol supports resume function (HTTP/ HTTPS), download will be resumed next FOTA timer or next device download request.

certificateID

Integer: 11..19. Certificate index to be used for the authentication on FOTA repository server (certificate previously stored using AT+SQNSNVW="certificate" command).

• Activate the service (one-off operation after each factory reset) in manual mode (= device initiated mode)
• Start/stop the service to enable FOTA check and firmware upgrade with authorisation to execute:
  • Periodic (modem initiated) FOTA check (see AT+SQNFOTACFG <fota_timer_sec> parameter).
  • On-demand (device initiated) FOTA check.
  • Network initiated FOTA triggered by FOTA server using underlying upgrade service (ex: LWM2M SMS registration update).
• Initiate a manual check (device initiated FOTA check).
• Authorise/resume/cancel FOTA critical steps (download, installation) execution in manual (interactive) mode (see FOTA Client Configuration: AT+SQNFOTACFG).

• Declare the device (FOTA client) existence to FOTA server
• Provision the device (FOTA client) with unique credentials, security material and commercial server URL provided by FOTA bootstrap server.

• The periodic check can be disabled by using the ‘stop’ subcommand (<action>=3)
  Notice:

  When periodic check is enabled, the FOTA check schedule takes the FOTA activation date (activationDate) as a time reference and follows a simple rule (Note: FOTA service start time not used to build FOTA check schedule): checkDaten = activationDate + n * <fota_timer_sec>.

• Upgrade package available (<state>=5)
  • The FOTA client is waiting for the download to start.
  • Use AT+SQNFOTA with ‘download start/resume’ subcommand (<action>=5) to continue.
• Download timeout (<state>=5, <event>=4)
  • The FOTA client is waiting for the download to resume.
  • Use AT+SQNFOTA with ‘Download’ subcommand (<action>=5) to continue.
• Download complete (<state>=6)
  • The FOTA client is waiting for the installation to start.
  • Use AT+SQNFOTA with ‘install’ subcommand (<action>=6) to continue.

• Before starting/resuming the download or during the download (<state>=5).
• After the download is complete (<state>=6).

• ‘Inactive’: the FOTA service is not operational.
  • The FOTA client is waiting for activation before the FOTA service can be used.
  • The only possible user action is ‘Activate’.
• ‘Onboarding’: the FOTA service activation is in progress.
  • The FOTA client provisioning is ongoing.
  • After the provisioning completes, the FOTA client is activated and enters the ‘idle’ state. If the provisioning fails, the FOTA client returns to the ‘inactive’ state.
  • The onboarding session cannot be aborted.
• ‘Stopped’: the FOTA service is activated but not running (the LWM2M client is in the ‘de-registered’ protocol state).
  • This is the default FOTA client state after service activation
  • The only possible user action is ‘Start’.
• ‘Idle’: the FOTA client is running but idle (no activity in progress).
  • This is the default FOTA client state after service activation. The device is waiting for the next FOTA check session triggered by the FOTA timer, a device-initiated request (AT command) or a FOTA server request.
  • The only possible user actions are ‘Check’ and ‘Stop’.
• ‘Checking’: the software upgrade package availability check is in progress.
  • In this state, the FOTA client tries to connect to the FOTA server to check for software upgrade package availability. If an upgrade is available, the FOTA client moves automatically to the ‘downloading’ state. Otherwise it goes back to the ‘idle’ state.
  • The FOTA check session cannot be cancelled.
• ‘Downloading’: the software upgrade package download is pending or in progress.
  • The FOTA client enters this state from the ‘checking’ state as soon as a software upgrade package is detected, requesting a download operation. The FOTA client remains in that state until the downloading process is terminated (successfully or not).
  • If download progress indications are enabled (see FOTA Client Configuration: AT+SQNFOTACFG <report_download> parameter), the user application receives progress indications as specified.
  • After the download is complete and successful, the FOTA client moves to ‘downloaded’ state.
  • In case of a cancel request (<action>=7) or a download failure, the FOTA client aborts the FOTA procedure, deletes the partially downloaded upgrade package and optionally reports the error to the FOTA server.
  • In manual mode, the user application must monitor the +SQNFOTA notifications to start/resume the download as needed using the download subcommand (<action>=5).
  • During the download operation, the user application may use the radio interface for its own needs in parallel but must not do any modem reconfiguration that could break radio connectivity, or a download timeout can result.
• ‘Downloaded’: the module is ready for installation.
  • The FOTA client enters this state after the upgrade file is confirmed to be entirely available and stored in non-volatile memory.
  • This state is transient and the FOTA client moves immediately to ‘updating’ without possibility to reject or delay the upgrade, unless in manual mode.
  • In manual mode, the FOTA client waits for installation start command (<action>=6) before moving to the ‘updating’ state. If it receives a ‘cancel’ subcommand (<action>=7) during this wait period, the FOTA client aborts FOTA procedure, removes the downloaded upgrade package, and optionally report the status to FOTA server.
  • Following the ‘downloaded’ state entry notification, the user application must immediately suspend its activity with the modem, save key volatile data, stop peripherals and prepare for module reboot which completes the system update.
• ‘Updating’: the software upgrade package installation is in progress.
  • In this state, the FOTA client performs a software upgrade package verification (integrity and authentication), then proceed with its installation. The FOTA client remains in that state until the installation process is complete.
  • After the installation is complete (whatever the final status), the FOTA client removes the locally stored software upgrade package.
  • If the installation has succeeded, FOTA client transitions to ‘installed’ state. Otherwise (verification failure or installation error) the module aborts the operation and optionally reports status to the FOTA server.
  • This update phase cannot be cancelled.
• ‘Installed’: The module update has been successfully completed.
  • The FOTA client enters this state only after successful installation.
  • This is a transient state, and the FOTA client returns automatically to the ‘idle’ state

action

Integer 1..7

Control command.

• 1: "Activate"
• 2: "Start"
• 3: "Stop"
• 4: "Check" (device initiated)
• 5: "Download" (start/resume)
• 6: "Install"
• 7: "Cancel"

state

Integer 0..8

FOTA client state.

• 0: "Inactive". The FOTA service is not operational, waiting for activation command.
• 1: "Onboarding". The FOTA service activation is in progress.
• 2: "Stopped". The FOTA service is activated but not running.
• 3: "Idle": The FOTA client is running but idle (no activity in progress).
• 4: "Checking". The software upgrade package availability check in progress.
• 5: "Downloading". The software upgrade package download is pending or in progress.
• 6: "Downloaded". The module is ready for installation.
• 7: "Updating". The software upgrade package installation is in progress.
• 8: "Installed". The module update is complete and successful.

event

Integer 0..10

FOTA event.

• 0: Connection timeout.
• 1: Provisioning timeout.
• 2: Activation failure (no more retries).
• 3: Download in progress
• 4: Download timeout (download in pause if resume supported and max reties not reached).
• 5: Download failure (no more retries).
• 6: Upgraded package integrity failure.
• 7: Upgraded package authentication failure.
• 8: Installation failure.
• 9: Operation cancelled.
• 10: Operation aborted (following a "stop" action)

dl_percent

Integer 0..100

FOTA download progress status in percents.

• 550: "Invalid configuration parameters"
• 551: "MT not registered and not searching"
• 552: "MT searching for network"
• 553: "MT out of coverage"
• 555: "Unknown network error"
• 601: "FOTA client already activated"
• 602 "FOTA client activation already in progress"
• 603 "FOTA client not activated"
• 604 "FOTA client stopped"
• 605 "FOTA client invalid request"
• 606: " Software upgrade already in progress"

reportStage

Integer

Table 42. reportStage

Value	Description
0	Default value. Do not report any upgrade status.
1	Activate upgrade status main step reporting (see <upgrade_state> values of +SQNSUPGRADE URC)

reportProgress

Integer

Table 43. reportProgress

Value	Description
0	Default value. Do not report download progress
1..100	Report download progress using +SQNSUPGRADE: "downloading", <percent_downloaded> URC.

AT+SQNSUPGRADECFG=? 
+SQNSUPGRADECFG: 0,(0-1),(0-100) 
OK 
AT+SQNSUPGRADECFG? 
+SQNSUPGRADECFG: 0,0,0 
OK 
AT+SQNSUPGRADECFG=0,1,1 
OK 
AT+SQNSUPGRADECFG? 
+SQNSUPGRADECFG: 0,1,1 
OK

temperature

Measured temperature in °C. Precision is one tenth of degree.

err

Error list:

• NA: Temperature is not available on this model
• ONGOING: Measurement is under way

adc

String. Name of the ADC channel input. Please refer to the device’s data sheet.

voltage

Integer: 0..1800. Voltage at the specified ADC channel input in mV.