LogoLogo
ProductsDevelopersAPI ReferenceContact Us
Super SIM
Super SIM
  • Super SIM
  • Super SIM's Available Networks
  • Super SIM’s Multi-IMSI Applet
  • Over-the-Air Updates
  • Get Started with Super SIM
    • Overview
    • Get Started with Super SIM, the Raspberry Pi 4 and the Waveshare 4G Hat
    • Get Started with Super SIM, the Raspberry Pi 4 and the Sixfab Base Hat
    • Get Started with Data Comms and the Raspberry Pi Pico
    • Get Started with Super SIM SMS Commands and the Raspberry Pi 4
    • Get Started with Super SIM SMS Commands and the Raspberry Pi Pico
    • Get Started with Super SIM IP Commands and the Raspberry Pi
    • Get Started with Super SIM IP Commands and the Raspberry Pi Pico
    • Get Started with Super SIM eSIM Profiles for eUICCs
    • Get Started with Super SIM Connection Events
  • How To
    • How to Set a Device’s APN for Super SIM
    • How to Enable Device Roaming for Super SIM
    • How to Determine Whether a Device Contains a Super SIM
    • How to Set up iPhones for Super SIM
    • How to Determine a Super SIM’s Status
    • How to Use Console Bulk Actions to Update Multiple Super SIMs
    • How to Download Bulk Super SIM Data
    • How to Use Super SIM Fleets and Network Access Profiles
    • How to Understand the Settings on your SIM
      • Base Settings Package
    • How and Why You Can Set Super SIM’s Network Attach Priority List
    • How to Set Up and Use a Super SIM VPN
    • How to Configure AWS for a Super SIM VPN
    • How to Make and Take IoT VoIP Calls via Super SIM
    • How to Use Super SIM Connection Events
    • How to use Super SIM eSIM Profiles
    • How to Monitor Super SIM Connection Events using AWS ElasticSearch and Kibana
    • How to Use OpenAPI Clients with Super SIM
  • Into Production
    • Prepare for Production Deployments with Super SIM
    • Super SIM Datasheet
    • Super SIM Network Timeouts
  • Works with Super SIM
    • Works with Super SIM: Quectel BG95
    • Works with Super SIM: Quectel EG21-G
    • Works with Super SIM: Quectel EG25-G
    • Works with Super SIM: Thales Cinterion EXS62-W
    • Works with Super SIM: u-blox SARA-R5
  • Cellular Module Knowledgebase
    • Overview
    • About AT Commands
    • Nordic Modules with Super SIM
    • Quectel Modules with Super SIM
    • Quectel Modules with the KORE Narrowband SIM
    • Simcom Modules with Super SIM
    • Telit Modules with Super SIM
    • Thales Cinterion Modules with Super SIM
    • U-blox Modules with Super SIM
    • Cellular IoT Terminology
    • Low-power Optimization for Cellular Modules
    • Four Best Practices for Cellular Module Registration
    • How to Determine Good Cellular Signal Strength
    • How Super SIM Devices Connect to Cell Networks
  • Super SIM API
On this page
  • Cellular modules covered on this page
  • Super SIM
  • Firmware updates
  • General getting started information
  • BG96 NB-IoT
  • Initialization
  • Operator selection
  • Low-power modes
  • Known issues

Was this helpful?

  1. Cellular Module Knowledgebase

Nordic Modules with Super SIM

PreviousAbout AT CommandsNextQuectel Modules with Super SIM

Last updated 5 months ago

Was this helpful?

Cellular modules covered on this page


Super SIM

If you are looking for information related to using Quectel modules with Super SIM, please see .


Firmware updates

Firmware updates for Quectel cellular modules are typically available through Quectel support. Please reach out to your Quectel representative or for assistance with firmware updates.


General getting started information

Please refer to the main Knowlegdebase page for .


BG96 NB-IoT

Initialization

Modifying the following parameters can have an adverse affect on connection times immediately following their execution. They restart the network scanning process even if the newly set value is the same as the previously set value. This restart can also discard the cellular modem's affinity to the previously connected network, causing the modem to scan all visible networks again.

We recommend querying the values of these parameters in your initialization code and only setting values when changes are needed. This will help ensure the correct configuration is being used and allow the modem's connection process to proceed normally if the correct values are already set.

Operator selection

Calling AT+COPS redundantly can adversely affect connection times. We recommend using automatic operator selection: AT+COPS=0.

Calling AT+COPS=0 when the operator mode is already set to automatic can cause the modem to perform a user re-selection process. This will disconnect from the current/previously connected network and restart the connection process.

Similarly, using AT+COPS=2 to temporarily deregister from the network will result in the current/last connected network to be disregarded upon returning to a registered state and require a scan of available networks. If your application needs to deregister from the network for power reasons, we recommend you consider using AT+CFUN=0 and AT+CFUN=1 to accomplish a similar result without the loss of the previously connected network information.

Low-power modes

While the BG96 supports low-power modes for eDRX and PSM, support for these features will vary by visited network and location. The commands for each of these settings are:

  • eDRX: AT+CEDRXS

  • PSM: AT+CPSMS

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 with the modem local. To disable all power saving, send:

AT+CEDRXS=0 AT+CPSMS=0

Known issues

1. DNS servers may not be provided by the network with the Twilio Narrowband SIM

Modem firmware versions prior to BG96MAR03A06M1G may not receive valid DNS servers upon connection. Affected versions include, but are not limited to, BG96MAR02A06M1G and BG96MAR02A07M1G.

This issue does not impact GSM connections maintained by the Narrowband SIM.

This issue can be observed by connecting to the network and executing the following commands, noting the 0.0.0.0 DNS addresses:

AT+QICSGP=1,1,"iot.nb"
OK
AT+QIACT=1
OK
AT+QIACT?
+QIACT: 1,1,1,"x.x.x.x"
OK
AT+QIDNSCFG=1
+QIDNSCFG: 1,"0.0.0.0","0.0.0.0"
OK

Attempts to resolve a host name to an address will fail:

AT+QIDNSGIP=1,"www.twilio.com"
OK

+QIURC: "dnsgip",565

Recommended solution Update the BG96's firmware to version BG96MAR03A06M1G or above.

Workaround Provide DNS servers manually after connection with the following command:

AT+QIDNSCFG=1,"8.8.8.8","8.8.4.4"

This example uses Google's DNS servers, but you can use the DNS service of your choice.

KORE can be made accessible by setting iotopmode to 1: AT+QCFG="iotopmode",1,1.

You can learn more about implementing these modes in .

Narrowband
our low-power usage documentation
this document
Quectel Support
modem-independent configuration tips
BG96