Please refer to the main Knowledgebase page for modem-independent configuration tips.
Super SIM does not support NB-IoT.
Update your R5's firmware to version 3.15 or above for use with Super SIM. You can check the installed version with AT+GMR
. Please see the R5's AT commands manual to learn how to update the module.
The SARA-R5 supports LTE Cat-M1 and NB-IoT in bands 1, 2, 3, 4, 5, 8, 12, 13, 18, 19, 20, 25, 26, 28, 66, 71, and 85. Super SIM is compatible with Cat-M1 but not NB-IoT. It's therefore important to ensure that your SARA-R5 is set to operate only using Cat-M1.
SARA-R5 supports the use of only a single RAT at a time, so if Cat-M1 is selected and no suitable network is available, the module will not attempt to connect using NB-IoT. Consequently, if you have set the module to use NB-IoT, it will never connect until Cat-M1 is set as the favored RAT.
By default, all current SARA-R5 variants prioritize Cat-M1, but you can set this manually by issuing the command AT+URAT
and specifying the value 7. You should apply the value using the following command sequence:
1AT+CFUN=02AT+URAT=73AT+CFUN=16
The value 16
in the last command tells the modem to reboot and persist the specified RAT value.
The following commands can be used to establish a PDP context once the APN has been set as shown on the Knowledgebase overview page:
1AT+CGACT=1,12AT+UPSD=0,0,03AT+UPSD=0,100,14AT+UPSDA=0,3
Line two must match the PDP type set in the AT+CGDCONT
command. For example, the latter includes "IP"
to select IPv4, so the final parameter of AT+UPSD=0,0,0
must also indicate IPv4, i.e., 0
.
Line three maps the module's internal packet-switched data (PSD) profile, 0
, to the PDP context ID, 1
, set with the AT+CGDCONT
command as shown on the Knowledgebase overview page.
Line four activates PSD profile 0.
Issue AT+UPING=<TARGET_IP_ADDRESS_OR_NAME>
. This will yield, for example:
1AT+UPING="8.8.8.8"2OK34+UUPING: 1,32,"dns.google","8.8.8.8",109,11055+UUPING: 2,32,"dns.google","8.8.8.8",109,2716+UUPING: 3,32,"dns.google","8.8.8.8",109,2387+UUPING: 4,32,"dns.google","8.8.8.8",109,216
To perform an HTTP GET
using the built-in HTTP client:
AT+UHTTP=0
.
AT+UHTTP=0,1,"api.ipify.org"
.
GET
request using profile 0 and store the result in the file test.ffs
: AT+UHTTPC=0,1,"/","test.ffs"
.
+UUHTTPCR: 0,1,1
.
Now you can read the file containing the response from the server by requesting the file test.ffs
for profile 0. Do so by issuing AT+URDFILE="test.ffs"
. This will yield:
1+URDFILE: "test.ffs",178,"HTTP/1.1 200 OK2Server: Cowboy3Connection: close4Content-Type: text/plain5Vary: Origin6Date: Mon, 14 Mar 2022 11:54:03 GMT7Content-Length: 118Via: 1.1 vegur9103.239.194.9"11OK
This example uses a service that returns the IP address of the requester.
The SARA-R5 supports eDRX and PSM for low-power operation. The commands to enable each of these are, respectively:
1AT+CEDRXS=12AT+CPSMS=1
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.
None at this time.
Super SIM does not support NB-IoT.
You must only configure the modem's Radio Access Technology (RAT) preference for Cat-M1 when connecting via LTE. To apply this setting, issue AT+URAT=7
.
First de-register from the network, set UMNOPROF
to 0
, and then restart the module:
1AT+COPS=22AT+UMNOPROF=03AT+CFUN=15
When the module comes back, select the correct RAT:
1AT+URAT=72AT+CFUN=15
If you are using the SARA-R410M-02B variant, you are in the US, and you are experiencing exceptionally long (50 minutes) attachment times, u-blox recommends setting UMNOPROF
to 100
rather than 0
. MNO profile 100 is defined as "standard Europe", but u-blox says this the best generic configuration for this variant.
To set the SARA-R4 to force data-centric attachment, issue AT+CEMODE=2
.
The parameter's value is as follows:
0 = PS mode 2: EPS only, data centric 1 = CS/PS mode 1: voice centric 2 = CS/PS mode 2: data centric 3 = PS mode 1: EPS only, voice centric
This setting is non-volatile.
To perform an HTTP GET
using the built-in HTTP client:
AT+CGDCONT=1,"IP","super"
.
AT+UHTTP=0
.
AT+UHTTP=0,1,"api.ipify.org"
.
AT+UHTTP=0,5,443
.
AT+UHTTP=0,6,1
.
GET
request and store the result in the file test.ffs
: AT+UHTTPC=0,1,"/","test.ffs"
.
+UUHTTPCR: 0,1,1
.
Now you can request the file containing the response from the server by issuing AT+URDFILE="test.ffs"
. This will yield:
1+URDFILE: "http_last_response_0",179,"HTTP/1.1 200 OK2Server: Cowboy3Connection: close4Content-Type: text/plain5Vary: Origin6Date: Tue, 05 Jan 2021 18:31:02 GMT7Content-Length: 128Via: 1.1 vegur9103.86.104.174"11OK
This example uses a service that returns the IP address of the requester.
The SARA-R4 supports eDRX and PSM for low-power operation. The commands to enable each of these are, respectively:
1AT+CEDRXS=12AT+CPSMS=1
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 use of a PIN-protected SIM card and PSM is not supported on the SARA-R410M. If the SIM has a PIN set, the module will not enter PSM.
None at this time.
First, configure the APN with AT+CGDCONT=1,"IP","super"
.
Next, bring up the initial PDP context — this is required for both the ping and HTTP GET
examples, below:
1
:
AT+CGATT?
.
AT+UPSD=0,1,"super"
.
AT+UPSDA=0,1
.
AT+UPSDA=0,3
.
+UUPSDA: 0,"100.64.80.24"
.
AT+UPSND=0,8
.
+UPSND: 0,8,1
. The final parameter of the response will be
1
if the GPRS connection is up.
AT+UPSND=0,0
.
+UPSND: 0,0,"100.64.80.24"
.
Issue AT+UPING="8.8.8.8"
. This will yield:
1+UUPING: 1,32,"dns.google","8.8.8.8",111,952+UUPING: 2,32,"dns.google","8.8.8.8",111,1013+UUPING: 3,32,"dns.google","8.8.8.8",111,884+UUPING: 4,32,"dns.google","8.8.8.8",111,95
To perform an HTTP GET
using the built-in HTTP client:
AT+UHTTP=0
.
AT+UHTTP=0,1,"api.ipify.org"
.
AT+UHTTP=0,5,443
.
AT+UHTTP=0,6,1
.
GET
request and store the result in the default filename for profile 0: AT+UHTTPC=0,1,"/",""
.
+UUHTTPCR: 0,1,1
. The modem will respond with:
+UUHTTPCR: 0,1,1
— the final parameter of this response indicates success (
1
) or failure (
0
).
Now you can read the file containing the response from the server by requesting the file with the default name for profile 0, "http_last_response_0"
. Do so by issuing AT+URDFILE="http_last_response_0"
. This will yield:
1+URDFILE: "http_last_response_0",180,"HTTP/1.1 200 OK2Server: Cowboy3Connection: close4Content-Type: text/plain5Vary: Origin6Date: Tue, 05 Jan 2021 20:54:44 GMT7Content-Length: 138Via: 1.1 vegur91054.81.145.161"11OK
This step uses a service that returns the IP address of the requester.
None at this time.