# Notecard could not connect after a while with external SIM card
**URL:** https://discuss.blues.com/t/notecard-could-not-connect-after-a-while-with-external-sim-card/3271
**Category:** Uncategorized
**Tags:** cellular-coverage
**Created:** [August 29, 2025, 12:43pm UTC](https://discuss.blues.com/t/notecard-could-not-connect-after-a-while-with-external-sim-card/3271 "2025-08-29T12:43:58Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Laurent](https://discuss.blues.com/u/Laurent)
#### Post date: [August 29, 2025, 12:43pm UTC](https://discuss.blues.com/t/notecard-could-not-connect-after-a-while-with-external-sim-card/3271/1 "2025-08-29T12:43:58Z")
On a Global Notecard, we use an external SIM card as the customer is in UAE (not support by notecard), so it works with the local provider (roaming).
It works fine for a while and then disconnect and could not connect anymore, here the response of the SIM provider:
_I noticed that both devices are using 2G, which is mostly shut down for Etisalat in the United Arab Emirates._
_Is it possible to check if devices are compatible with other radio access, like 3G or 4G?_
I wonder WHY the nodecard is using 2G? Do we miss something (I am not an expert but Notecard is able to use other access)
What should we do?
---
### Author:  [@RobLauer](https://discuss.blues.com/u/RobLauer)
#### Post date: [August 29, 2025, 2:03pm UTC](https://discuss.blues.com/t/notecard-could-not-connect-after-a-while-with-external-sim-card/3271/2 "2025-08-29T14:03:30Z")
Hi @Laurent ,
This is difficult to fully diagnose without a trace log from the device. If you have direct access to the device, please [generate a trace using these instructions](https://dev.blues.io/guides-and-tutorials/notecard-guides/using-notecard-trace-mode/#using-notecard-trace-mode) while the Notecard is trying to connect (as best you can).
If you don’t have direct access to the device, you can try adding the `_log` [reserved environment variable](https://dev.blues.io/guides-and-tutorials/notecard-guides/understanding-environment-variables/#reserved-environment-variables) with a value of `modem` to the device, and the next time it syncs and then starts a new session, you should see a `_log.qo` event with relevant debugging information.
Also, using the [card.wireless API](https://dev.blues.io/api-reference/notecard-api/card-requests/latest/) you can issue a command like this to force LTE-M (assuming that is what you want to use):
```auto
{
"req": "card.wireless",
"mode": "m"
}
```
Thanks,
Rob
---
### Author:  [@Laurent](https://discuss.blues.com/u/Laurent)
#### Post date: [September 1, 2025, 12:01pm UTC](https://discuss.blues.com/t/notecard-could-not-connect-after-a-while-with-external-sim-card/3271/3 "2025-09-01T12:01:53Z")
Thanks, as the devices are on customer, difficult to debug throw usb… I will try to set the \_log variable and see on next issue.
However, I could not explain why some use the 2G and other the 4G, is there a rules on the notecard to try first the 2G network (that is the less power consuming) ? We do not set any “mode” in the card.wireless query! Should you recommend to add one to avoid any connection to 2G?
Thank you for your support.
---
### Author:  [@RobLauer](https://discuss.blues.com/u/RobLauer)
#### Post date: [September 2, 2025, 4:33pm UTC](https://discuss.blues.com/t/notecard-could-not-connect-after-a-while-with-external-sim-card/3271/4 "2025-09-02T16:33:35Z")
Hi @Laurent,
Yes, if you want to force LTE-M for instance and avoid any kind of failover to 2G I would use the command provided above. The Notecard should only be using 2G as a last ditch failover though, so if LTE-M connectivity is spotty, that could explain it.
Rob