Menu

Expand
Rate this page:

Quectel Modules with Super SIM

Cellular modems covered on this page

Firmware updates

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

General getting started information

Please refer to the main Knowlegdebase page for modem-independent configuration tips, in particular setting the APN.

Super SIM does not support NB-IoT.

Initialization

If you are connecting via LTE, only configure the modem’s Radio Access Technology (RAT) preference to Cat-M1. Super SIM is compatible with almost all cellular network technologies — the exception is NB-IoT, which is not supported. It is therefore important to ensure that the Quectel-specific command AT+QCFG="iotopmode" is configured to its default setting of 0 — the first numeric parameter of the command below.

AT+QCFG="iotopmode",0,1

If iotopmode is set to 1 (NB-IoT), the modem will not be able to connect to Cat-M1.

If you wish to limit comms to LTE only, i.e., disable 2G (GSM), issue AT+QCFG="nwscanmode",3,1.

That first numeric parameter value of 3 is what indicates LTE only; a value of 1 sets the modem to GSM only. The default, 0, tells the modem to select the RAT automatically. The setting is applied immediately.

Data-centric attach mode

To set the modem to force data-centric attachment — ie., do not make circuit-switched attachments — issue AT+QCFG="servicedomain",1,1.

The first numeric parameter is the mode: 1 is Packet Switch (PS) attach only).

This setting is non-volatile.

Configure the URC UART

To configure the Unsolicited Result Code (URC) serial (UART) delivery channel to uart1, issue AT+QURCCFG="urcport","uart1".

Perform a ping

To perform a ping to a remote host, issue AT+QPING=1,"<TARGET_IP_ADDRESS_OR_NAME>". This will yield, for example:

+QPING: 0,"8.8.8.8",32,93,255
+QPING: 0,"8.8.8.8",32,78,255
+QPING: 0,"8.8.8.8",32,80,255
+QPING: 0,"8.8.8.8",32,80,255
+QPING: 0,4,4,0,78,93,82

Perform an HTTP GET

To issue an HTTP GET request using the built-in HTTP client, run the following commands:

  1. Set the PDP context ID: AT+QHTTPCFG="contextid",1
  2. Enable output of HTTP response headers: AT+QHTTPCFG="responseheader",1
  3. Activate the PDP context: AT+QIACT=1
  4. Set the target URL: AT+QHTTPURL=21
    This sets the modem to receive, prompted by the output CONNECT. The first parameter is the number of bytes the modem should expect to receive: it will end input after receiving this number of characters. The value of 21 comes from the URL below. The URL you provide must include the protocol, ie. http://.
  5. Upon CONNECT, enter the URL. For example: http://ifconfig.co/ip
  6. Issue a GET request: AT+QHTTPGET
  7. View the request: AT+QHTTPREAD

The request will look like this:

HTTP/1.1 200 OK
Date: Sat, 28 Nov 2020 18:38:52 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 15
Connection: keep-alive
Set-Cookie: __cfduid=d33c30006be23245591d83133631425031606588732; expires=Mon, 28-Dec-20 18:38:52 GMT; path=/; domain=.ifconfig.co; HttpOnly; SameSite=Lax
Strict-Transport-Security: max-age=15768000; includeSubdomains; preload
CF-Cache-Status: DYNAMIC
cf-request-id: 06b1bfaa91000025ed8fa46000000001
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report?s=8eYWG5vobibOeI8xWFxNSGJpELSCSthW9aAclBXw3esKOGBsYPT4izdckGI2kpOW%2BA7KOhi3OFk%2FLUab3RpQvKu5EYYWLD%2B2fSxV4Q%3D%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"report_to":"cf-nel","max_age":604800}
Server: cloudflare
CF-RAY: 5f96355748c225ed-IAD

99.84.181.20

OK
+QHTTPREAD: 0

This example uses a service that returns the IP address of the requester.

If you need to provide extra HTTP request headers, such Authorization: Basic <API_KEY>, or a custom header required by your server, issue AT+QHTTPCFG="requestheader",1 to tell the modem to use the custom header that you will provide when you make each request. You must create a full HTTP request header separated from your request body by <CR><LF> characters. Whether you make a POST or a GET request, include a byte-count parameter that totals the header plus the body (POST request) or header alone (GET request). For example, AT+QHTTPGET=60,512 for a 512-byte header (including the end-of-header <CR><LF>). The 60 is a timeout. This defaults to 60 seconds but must be included if a second parameter is also present.

You can check the status of a PDP context with AT+QIACT?. If activatated, this will return the context ID; 0 or 1 whether the context is inactive or active; 1 or 2 whether the context is using IPv4 or IPv6; and the device’s IP address.

Perform an HTTPS GET

To issue an HTTPS GET request using the EG21-G’s built-in HTTP client, follow the same procedure outlined above but with extra steps to configure SSL.

  1. Set the PDP context ID: AT+QHTTPCFG="contextid",1
  2. Enable output of HTTP response headers: AT+QHTTPCFG="responseheader",1
  3. Activate the PDP context if it is not already active: AT+QIACT=1
  4. Select the SSL context ID for this PDP context ID: AT+QHTTPCFG="sslctxid",1
  5. Set the SSL version. Choose TLS 1.2: AT+QSSLCFG="sslversion",1,3
  6. Set the SSL cipher suite. Choose all types: AT+QSSLCFG="ciphersuite",1,0xFFFF
  7. For testing, set the SSL verification level to 0, i.e., no CA certificate is required: AT+QSSLCFG="seclevel"=0
  8. Set the target URL: AT+QHTTPURL=70
    This sets the modem to receive, prompted by the output CONNECT. The parameter is the number of bytes the modem should expect to receive: it will end input after receiving this number of characters. The value of 70 comes from the URL below. The URL you provide must include the protocol, ie. https://.
  9. Upon receiving CONNECT, enter the URL. For example: https://twilio-cms-prod.s3.amazonaws.com/documents/super-sim-test.json
  10. Issue a GET request: AT+QHTTPGET
  11. View the response: AT+QHTTPREAD

The request will look something like this:

HTTP/1.1 200 OK
Date: Thu, 19 May 2022 10:23:25 GMT
Last-Modified: Thu, 19 May 2022 10:05:25 GMT
Accept-Ranges: bytes
Content-Type: application/json
Server: AmazonS3
Content-Length: 128

{
   "userId": 1,
   "id": 5,
   "title": "laboriosam mollitia et enim quasi adipisci quia provident illum",
   "completed": false                                                                                                                         }
OK

+QHTTPREAD: 0

Perform an HTTP(S) POST

Sending data from the modem to an Internet-hosted API follows the paths outlined above for the HTTP and HTTPS protocols: call AT+QHTTPOST instead of AT+QHTTPGET.

Optionally, the QHTTPOST command takes a parameter indicating the amount of data you are sending. The modem uses this to read that number of bytes via the UART over which your application is communicating with it. If you are providing a custom HTTP request header, remember to include its length too.

Low-power modes

While the BG95 and 96 support low-power modes for eDRX and PSM, support for these features will vary by visited network and location. The commands to enable for each of these are:

AT+CEDRXS
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

You can learn more about implementing these modes in our low-power usage documentation.

Known issues

The BG95 and BG96 will connect to 2G if they are unable to connect to Cat-M1 and 2G has not been disabled. Unfortunately, if Cat-M1 coverage is restored, or the device moves into an area where Cat-M1 is available, the modem will nonetheless continue to connect to 2G. This is because Quectel modems favor the most recently used RAT when they reconnect, and this value is persisted in non-volatile memory.

To avoid this issue, you can use the following AT command in your application to clear the stored RAT by resetting the modem’s RAT searching sequence:

AT+QCFG="nwscanseq",020103,1

The parameter 020103 represents the RAT sequence: 02 is Cat-M1, 01 is GSM, and 03 is NB-IoT. Super SIM is not compatible with NB-IoT, so this is placed last.

The final 1 forces the sequence to be applied immediately, avoiding the need to reboot the modem. Leave this parameter off, or set it to 0, to impose the new sequence on the next power cycle.

Additional resources

BG96 AT Commands Manual Quectel sign-in required
BG95, BG77, and BG600L Series AT Commands Manual Quectel sign-in required

EG21-G Cat-1, GSM

Initialization

If you wish to limit communications to LTE only, i.e., to disable 2G (GSM), issue this command:

AT+QCFG="nwscanmode",3

This setting will be applied immediately.

Data-centric attach mode

To instruct the modem to initiate data-centric attachments only — ie., not to make voice-oriented circuit-switched attachments too, which is the default — issue:

AT+QCFG="servicedomain",1

This setting will be applied immediately.

Configure the URC UART

To configure the Unsolicited Result Code (URC) serial (UART) delivery channel to uart1, issue AT+QURCCFG="urcport","uart1".

Perform a ping

To perform a ping to a remote host, issue AT+QPING=1,"<TARGET_IP_ADDRESS_OR_NAME>". This will yield, for example:

+QPING: 0,"8.8.8.8",32,172,255
+QPING: 0,"8.8.8.8",32,212,255
+QPING: 0,"8.8.8.8",32,376,255
+QPING: 0,"8.8.8.8",32,174,255
+QPING: 0,4,4,0,172,376,233

Perform an HTTP GET

To issue an HTTP GET request using the built-in HTTP client, run the following commands:

  1. Set the PDP context ID: AT+QHTTPCFG="contextid",1
  2. Enable output of HTTP response headers: AT+QHTTPCFG="responseheader",1
  3. Activate the PDP context: AT+QIACT=1
  4. Set the target URL: AT+QHTTPURL=21
    This sets the modem to receive, prompted by the output CONNECT. The first parameter is the number of bytes the modem should expect to receive: it will end input after receiving this number of characters. The URL you provide must include the protocol, ie. http://.
  5. Upon CONNECT, enter the URL. For example: http://ifconfig.co/ip
  6. Issue a GET request: AT+QHTTPGET
  7. View the request: AT+QHTTPREAD

The request will look like this:

HTTP/1.1 200 OK
Date: Sat, 28 Nov 2020 18:38:52 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 15
Connection: keep-alive
Set-Cookie: __cfduid=d33c30006be23245591d83133631425031606588732; expires=Mon, 28-Dec-20 18:38:52 GMT; path=/; domain=.ifconfig.co; HttpOnly; SameSite=Lax
Strict-Transport-Security: max-age=15768000; includeSubdomains; preload
CF-Cache-Status: DYNAMIC
cf-request-id: 06b1bfaa91000025ed8fa46000000001
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report?s=8eYWG5vobibOeI8xWFxNSGJpELSCSthW9aAclBXw3esKOGBsYPT4izdckGI2kpOW%2BA7KOhi3OFk%2FLUab3RpQvKu5EYYWLD%2B2fSxV4Q%3D%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"report_to":"cf-nel","max_age":604800}
Server: cloudflare
CF-RAY: 5f96355748c225ed-IAD

99.84.181.20

OK
+QHTTPREAD: 0

This example uses a service that returns the IP address of the requester.

If you need to provide extra HTTP request headers, such Authorization: Basic <API_KEY>, or a custom header required by your server, issue AT+QHTTPCFG="requestheader",1 to tell the modem to use the custom header that you will provide when you make each request. You must create a full HTTP request header separated from your request body by <CR><LF> characters. Whether you make a POST or a GET request, include a byte-count parameter that totals the header plus the body (POST request) or header alone (GET request). For example, AT+QHTTPGET=60,512 for a 512-byte header (including the end-of-header <CR><LF>). The 60 is a timeout. This defaults to 60 seconds but must be included if a second parameter is also present.

You can check the status of a PDP context with AT+QIACT?. If activatated, this will return the context ID; 0 or 1 whether the context is inactive or active; 1 or 2 whether the context is using IPv4 or IPv6; and the device’s IP address.

Perform an HTTPS GET

To issue an HTTPS GET request using the EG21-G’s built-in HTTP client, follow the same procedure outlined above but with extra steps to configure SSL.

  1. Set the PDP context ID: AT+QHTTPCFG="contextid",1
  2. Enable output of HTTP response headers: AT+QHTTPCFG="responseheader",1
  3. Activate the PDP context if it is not already active: AT+QIACT=1
  4. Select the SSL context ID for this PDP context ID: AT+QHTTPCFG="sslctxid",1
  5. Set the SSL version. Choose TLS 1.2: AT+QSSLCFG="sslversion",1,3
  6. Set the SSL cipher suite. Choose all types: AT+QSSLCFG="ciphersuite",1,0xFFFF
  7. For testing, set the SSL verification level to 0, i.e., no CA certificate is required: AT+QSSLCFG="seclevel"=0
  8. Set the target URL: AT+QHTTPURL=70
    This sets the modem to receive, prompted by the output CONNECT. The parameter is the number of bytes the modem should expect to receive: it will end input after receiving this number of characters. The value of 70 comes from the URL below. The URL you provide must include the protocol, ie. https://.
  9. Upon receiving CONNECT, enter the URL. For example: https://twilio-cms-prod.s3.amazonaws.com/documents/super-sim-test.json
  10. Issue a GET request: AT+QHTTPGET
  11. View the response: AT+QHTTPREAD

The request will look something like this:

HTTP/1.1 200 OK
Date: Thu, 19 May 2022 10:23:25 GMT
Last-Modified: Thu, 19 May 2022 10:05:25 GMT
Accept-Ranges: bytes
Content-Type: application/json
Server: AmazonS3
Content-Length: 128

{
   "userId": 1,
   "id": 5,
   "title": "laboriosam mollitia et enim quasi adipisci quia provident illum",
   "completed": false                                                                                                                         }
OK

+QHTTPREAD: 0

Perform an HTTP(S) POST

Sending data from the modem to an Internet-hosted API follows the paths outlined above for the HTTP and HTTPS protocols: call AT+QHTTPOST instead of AT+QHTTPGET.

Optionally, the QHTTPOST command takes a parameter indicating the amount of data you are sending. The modem uses this to read that number of bytes via the UART over which your application is communicating with it. If you are providing a custom HTTP request header, remember to include its length too.

Low-power modes

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

AT+CEDRXS
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

You can learn more about implementing these modes in our low-power usage documentation.

Additional resources

EG21-G AT Commands Manual Quectel sign-in required

EG25-G Cat-4, GSM

Initialization

If you wish to limit communications to LTE only, i.e., to disable 2G (GSM), issue this command:

AT+QCFG="nwscanmode",3

This setting will be applied immediately.

Data-centric attach mode

To instruct the modem to initiate data-centric attachments only — ie., not to make voice-oriented circuit-switched attachments too, which is the default — issue:

AT+QCFG="servicedomain",1

This setting will be applied immediately.

Configure the URC UART

To configure the Unsolicited Result Code (URC) serial (UART) delivery channel to uart1, issue AT+QURCCFG="urcport","uart1".

Perform a ping

To perform a ping to a remote host, issue AT+QPING=1,"<TARGET_IP_ADDRESS_OR_NAME>". This will yield, for example:

+QPING: 0,"8.8.8.8",32,167,255
+QPING: 0,"8.8.8.8",32,162,255
+QPING: 0,"8.8.8.8",32,164,255
+QPING: 0,"8.8.8.8",32,162,255
+QPING: 0,4,4,0,162,167,163

Perform an HTTP GET

To issue an HTTP GET request using the built-in HTTP client, run the following commands:

  1. Set the PDP context ID: AT+QHTTPCFG="contextid",1
  2. Enable output of HTTP response headers: AT+QHTTPCFG="responseheader",1
  3. Activate the PDP context: AT+QIACT=1
  4. Set the target URL: AT+QHTTPURL=21
    This sets the modem to receive, prompted by the output CONNECT. The first parameter is the number of bytes the modem should expect to receive: it will end input after receiving this number of characters. The URL you provide must include the protocol, ie. http://.
  5. Upon CONNECT, enter the URL. For example: http://ifconfig.co/ip
  6. Issue a GET request: AT+QHTTPGET
  7. View the request: AT+QHTTPREAD

The request will look like this:

HTTP/1.1 200 OK
Date: Fri, 20 May 2022 08:52:56 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 13
Connection: keep-alive
CF-Cache-Status: DYNAMIC
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=9fl%2B3t%2FRMhY2tMyWQDFAIM1mfFem0zLc7aONeXJ%2Fg4a%2FJPKFl%2BeGYElL5zwwuxi7%2BIfqx}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Server: cloudflare
CF-RAY: 70e3d6ceb8cc5b17-IAD
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

44.204.32.40

OK

+QHTTPREAD: 0

This example uses a service that returns the IP address of the requester.

If you need to provide extra HTTP request headers, such Authorization: Basic <API_KEY>, or a custom header required by your server, issue AT+QHTTPCFG="requestheader",1 to tell the modem to use the custom header that you will provide when you make each request. You must create a full HTTP request header separated from your request body by <CR><LF> characters. Whether you make a POST or a GET request, include a byte-count parameter that totals the header plus the body (POST request) or header alone (GET request). For example, AT+QHTTPGET=60,512 for a 512-byte header (including the end-of-header <CR><LF>). The 60 is a timeout. This defaults to 60 seconds but must be included if a second parameter is also present.

You can check the status of a PDP context with AT+QIACT?. If activatated, this will return the context ID; 0 or 1 whether the context is inactive or active; 1 or 2 whether the context is using IPv4 or IPv6; and the device’s IP address.

Perform an HTTPS GET

To issue an HTTPS GET request using the EG25-G’s built-in HTTP client, follow the same procedure outlined above but with extra steps to configure SSL.

  1. Set the PDP context ID: AT+QHTTPCFG="contextid",1
  2. Enable output of HTTP response headers: AT+QHTTPCFG="responseheader",1
  3. Activate the PDP context if it is not already active: AT+QIACT=1
  4. Select the SSL context ID for this PDP context ID: AT+QHTTPCFG="sslctxid",1
  5. Set the SSL version. Choose TLS 1.2: AT+QSSLCFG="sslversion",1,3
  6. Set the SSL cipher suite. Choose all types: AT+QSSLCFG="ciphersuite",1,0xFFFF
  7. For testing, set the SSL verification level to 0, i.e., no CA certificate is required: AT+QSSLCFG="seclevel"=0
  8. Set the target URL: AT+QHTTPURL=70
    This sets the modem to receive, prompted by the output CONNECT. The parameter is the number of bytes the modem should expect to receive: it will end input after receiving this number of characters. The value of 70 comes from the URL below. The URL you provide must include the protocol, ie. https://.
  9. Upon receiving CONNECT, enter the URL. For example: https://twilio-cms-prod.s3.amazonaws.com/documents/super-sim-test.json
  10. Issue a GET request: AT+QHTTPGET
  11. View the response: AT+QHTTPREAD

The request will look something like this:

HTTP/1.1 200 OK
Date: Thu, 19 May 2022 10:23:25 GMT
Last-Modified: Thu, 19 May 2022 10:05:25 GMT
Accept-Ranges: bytes
Content-Type: application/json
Server: AmazonS3
Content-Length: 128

{
   "userId": 1,
   "id": 5,
   "title": "laboriosam mollitia et enim quasi adipisci quia provident illum",
   "completed": false                                                                                                                         }
OK

+QHTTPREAD: 0

Perform an HTTP(S) POST

Sending data from the modem to an Internet-hosted API follows the paths outlined above for the HTTP and HTTPS protocols: call AT+QHTTPOST instead of AT+QHTTPGET.

Optionally, the QHTTPOST command takes a parameter indicating the amount of data you are sending. The modem uses this to read that number of bytes via the UART over which your application is communicating with it. If you are providing a custom HTTP request header, remember to include its length too.

Low-power modes

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

AT+CEDRXS
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

You can learn more about implementing these modes in our low-power usage documentation.

Additional resources

EG25-G AT Commands Manual Quectel sign-in required

Rate this page:

Need some help?

We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.

Thank you for your feedback!

Please select the reason(s) for your feedback. The additional information you provide helps us improve our documentation:

Sending your feedback...
🎉 Thank you for your feedback!
Something went wrong. Please try again.

Thanks for your feedback!

Refer us and get $10 in 3 simple steps!

Step 1

Get link

Get a free personal referral link here

Step 2

Give $10

Your user signs up and upgrade using link

Step 3

Get $10

1,250 free SMSes
OR 1,000 free voice mins
OR 12,000 chats
OR more