Please refer to the main Knowlegdebase page for modem-independent configuration tips.
Super SIM does not support NB-IoT.
Only configure the modem's Radio Access Technology (RAT) preference for Cat-M1. To do so, issue AT^SXRAT=7,7
.
The first parameter is the RAT to connect to immediately. The second is the preferred RAT on re-connection.
A value of 8
indicates NB-IoT, and 10
indicates Cat-M1/NB-IoT dual mode. Do not use 8
, and we strongly recommend that you do not select 10
. This is the default and so you should always command the module to favor Cat-M1. This prevents the modem from spending time attempting to attach to NB-IoT networks, if any are nearby, only to be rejected.
To set the EXS62-W to force data-centric attachment, issue:
1AT+CEMODE=22AT+CFUN=1,1
The CEMODE
parameter's value is as follows:
0
= PS mode 2: EPS only, data centric
2
= CS/PS mode 2: data centric
This setting is non-volatile and implemented when the modem is reset.
AT+CGDCONT=1,"IP","super"
.
AT^SICA=1,1
.
The first parameter of AT^SICA
is the required action: 1
for enable, 0
for disable. The second parameter is the ID of the PDP context to be used to host the connection — it should match the value used in the AT+CGDCONT
command.
Check the device's IP address with AT+CGPADDR=1
.
To perform a ping to a remote host after bringing up a connection as described above, issue AT^SISX=Ping,1,"8.8.8.8",5,5000
. This will yield:
1^SISX: "Ping",1,1,"8.8.8.8",5462^SISX: "Ping",1,1,"8.8.8.8",5153^SISX: "Ping",1,1,"8.8.8.8",4574^SISX: "Ping",1,1,"8.8.8.8",4435^SISX: "Ping",1,1,"8.8.8.8",3756^SISX: "Ping",2,1,5,5,0,07^SISX: "Ping",3,1,375,546,4678OK
AT^SICS=1,"dns1","8.8.8.8"
AT^SICA=1,1
Configure the HTTP operation's Internet service profile. This is referenced by its ID, in the range 0-9:
AT^SISS=0,srvtype,"http"
AT^SISS=0,conid,"1"
AT^SISS=0,address,"http://ifconfig.co/ip"
Note
You can specify HTTP by including the protocol as a URL prefix, or by adding
:80
to indicate the required port.
AT^SISS=0,cmd,"get"
AT^SISO=0
The modem will attempt to make the request. You may see these URCs as the response is processed:
1^SIS: 0,0,2200,"Http connect 172.67.133.228:80"2^SIS: 0,0,2201,"HTTP/1.1 200 OK"3^SIS: 0,0,2201,"Content-Length: 13"4^SISR: 0,1
AT^SISR=0,13
You will see:
1^SISR: 0,13244.204.32.143OK
^SISR: 0,2
. This indicates that all the available data has been read. If you don't see this — perhaps the response's content length was much larger and you only read a portion of it — continue to issue
AT^SISR=0,<NUMBER_OF_BYTES_TO_READ>
commands until all the data has been read — i.e., you receive
^SISR: 0,2
AT^SISC=0
If you need to provide extra request headers, such Authorization: Basic <API_KEY>
or a custom header required by your server, issue AT^SISS=0,hcprop,"<HEADERS>"
when you are configuring your Internet service profile.
Pass each header in the form <key>: <value>
. Multiple headers can be included by separating them with the sequence \0d\0a
. Don't add a separator after the last header and ensure your headers string is 255 bytes or less.
Tip If you wish to include a User-Agent
header, don't add it to your headers string but instead supply it to the module with AT^SISS=0,hcuseragent,"<USER_AGENT>"
. This will make room in the modem's header store for other headers.
AT^SSECUA="CertStore/TLS/PreconfigureCerts"
AT^SICS=1,"dns1","8.8.8.8"
AT^SICA=1,1
Configure the operation's Internet service profile:
AT^SISS=1,srvtype,"http"
AT^SISS=1,conid,"1"
AT^SISS=1,address,"https://jsonplaceholder.typicode.com/todos/1"
Note
You can specify HTTPS by including the protocol as a URL prefix, or by adding
:443
to indicate the required port.
AT^SISS=1,cmd,"get"
AT^SISO=1
The connection will be attempted. You will see these URCs:
1^SIS: 1,0,2200,"Http connect 172.67.131.170:443"2^SIS: 1,0,2201,"HTTP/1.1 200 OK"3^SIS: 1,0,2201,"Content-Length: 83"4^SISR: 1,1
AT^SISR=1,83
You will see:
1^SISR: 1,832{3"userId": 1,4"id": 1,5"title": "delectus aut autem",6"completed": false7}8OK
^SISR: 1,2
, which indicates that all the available data has been read. If you don't see this — perhaps the content length was much larger and you only read a portion of it — continue to issue
AT^SISR=1,<NUMBER_OF_BYTES_TO_READ>
commands until all the data is read — i.e., you receive
^SISR: 1,2
AT^SISC=1
Sending data from the modem via an Internet-hosted API follows the paths outlined above for the HTTP and HTTPS protocols. You call AT^SISS=0,cmd,"post"
instead of AT^SISS=0,cmd,"get"
.
The EXS62-W provides a way to load up a small amount (1-255 bytes) of body data: issue AT^SISS=0,hccontent,"<DATA_AS_STRING>"
and AT^SISS=0,hccontlen,0
.
If the size of the data you wish to send is greater than 255 bytes, set the size with AT^SISS=0,hccontlen,<SIZE_IN_BYTES>
and then upload data to the module after opening the Internet service with AT^SISO=0
. Issue AT^SISW=0,<CHUNK_SIZE>
to trigger the modem to input the data over the UART. Up to 1500 bytes can be sent to the modem at a time, and each chunk will be sent out as they are received from your application.
The EXS62-W supports the eDRX and PSM low-power modes. The commands to enable each of these are:
1AT+CEDRXS=12AT+CPSMS=1
See also AT^SEDRXS
in the EXS62-W AT Commands Manual for further eDRX settings, and AT+CEDRXRDP
to read dynamic eDRX parameters.
Using these features, but especially PSM, can make the modem inaccessible to the terminal during its sleep time. It's best to experiment with these features locally. To disable all power saving, send:
1AT+CEDRXS=02AT+CPSMS=0
You can learn more about implementing these modes in our low-power usage documentation.
The EXS62-W does not support AT+CCID
to retrieve the SIM's ICCID. Instead, issue AT^SIND?
and look for the line commencing ^SIND: iccid,0
.
• EXS62-W AT Commands Manual Thales sign-in required