# SMS problems with Digi LTE-M / NB-IoT

**URL:** <https://forums.digi.com/t/sms-problems-with-digi-lte-m-nb-iot/21660>\
**Category:** XBee - Cellular\
**Tags:** micropython, xbee-cellular\
**Created:** [August 12, 2020, 12:11am UTC](https://forums.digi.com/t/sms-problems-with-digi-lte-m-nb-iot/21660 "2020-08-12T00:11:47Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![juha.autioniemi](https://avatars.discourse-cdn.com/v4/letter/j/6de8d8/32.png) [@juha.autioniemi](https://forums.digi.com/u/juha.autioniemi)\
**Post date:** [August 12, 2020, 12:11am UTC](https://forums.digi.com/t/sms-problems-with-digi-lte-m-nb-iot/21660/1 "2020-08-12T00:11:47Z")

</div>

I am trying to send SMS with Digi LTE-M / NB-IoT module. It is working with some modules. But there are problems with newer firmware.

Working module configuration is for example:

XBee LTE-M / NB-IoT firmware 11410 or firmware 11411  
Modem firmware L0.0.00.00.05.06 [Feb 03 2018 13:00:41]

With newest firmware 11415 and modem firmware L0.0.00.00.05.08,A.02.04 sending SMS always end up to timeout, also receiving SMS does not work.

All firmware versions can register to network and data connection with TCP is working.

Python code, i tried:

\>\>\> import network  
\>\>\> cellular = network.Cellular()  
\>\>\> cellular.sms\_send(“+35840\*\*\*\*\*\*\*”,“test”)  
Traceback (most recent call last):  
File “”, line 1, in  
OSError: [Errno 7110] ETIMEDOUT

What could be the problem?

---

<div class="post-metadata">

**Author:** ![mvut](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.digi.com/mvut/32/31_2.png) [@mvut](https://forums.digi.com/u/mvut)\
**Post date:** [August 13, 2020, 8:53am UTC](https://forums.digi.com/t/sms-problems-with-digi-lte-m-nb-iot/21660/2 "2020-08-13T08:53:54Z")

</div>

This is something that you should send an email to [tech.support@digi.com](mailto:tech.support@digi.com) over.

---

<div class="post-metadata">

**Author:** ![TomCollins](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.digi.com/tomcollins/32/37_2.png) [@TomCollins](https://forums.digi.com/u/TomCollins)\
**Post date:** [August 16, 2020, 9:02pm UTC](https://forums.digi.com/t/sms-problems-with-digi-lte-m-nb-iot/21660/3 "2020-08-16T21:02:40Z")

</div>

Does your SIM card/dataplan include SMS service? Does ATPH report a phone number? If you send an SMS to that number, can you receive it in MicroPython?

---

<div class="post-metadata">

**Author:** ![juha.autioniemi](https://avatars.discourse-cdn.com/v4/letter/j/6de8d8/32.png) [@juha.autioniemi](https://forums.digi.com/u/juha.autioniemi)\
**Post date:** [August 17, 2020, 1:59am UTC](https://forums.digi.com/t/sms-problems-with-digi-lte-m-nb-iot/21660/4 "2020-08-17T01:59:04Z")

</div>

Yes and XBee cellular with older firmwares (XBee & Modem) can send and receive SMS in Micropython, but XBee with newest can´t. ATPH reports a phone number in any firmware combination I have tested.

---

<div class="post-metadata">

**Author:** ![juha.autioniemi](https://avatars.discourse-cdn.com/v4/letter/j/6de8d8/32.png) [@juha.autioniemi](https://forums.digi.com/u/juha.autioniemi)\
**Post date:** [August 17, 2020, 1:59am UTC](https://forums.digi.com/t/sms-problems-with-digi-lte-m-nb-iot/21660/5 "2020-08-17T01:59:39Z")

</div>

Thanks, I have contacted tech support.

---

<div class="post-metadata">

**Author:** ![Craigus861](https://avatars.discourse-cdn.com/v4/letter/c/b5a626/32.png) [@Craigus861](https://forums.digi.com/u/Craigus861)\
**Post date:** [November 3, 2020, 8:29am UTC](https://forums.digi.com/t/sms-problems-with-digi-lte-m-nb-iot/21660/6 "2020-11-03T08:29:42Z")

</div>

I am Having the same issue with SMS although I get the EIO Error. Was your issue resolved?

---

<div class="post-metadata">

**Author:** ![juha.autioniemi](https://avatars.discourse-cdn.com/v4/letter/j/6de8d8/32.png) [@juha.autioniemi](https://forums.digi.com/u/juha.autioniemi)\
**Post date:** [November 3, 2020, 8:42am UTC](https://forums.digi.com/t/sms-problems-with-digi-lte-m-nb-iot/21660/7 "2020-11-03T08:42:31Z")

</div>

Original issue is not solved yet. I got some new steps to solve issue from tech support just a while ago, but I didnt have time to test those steps yet.

Temporarily solution in my case to get my project up and running was to update XBee firmware to 11415 and modem firmware to L0.0.00.00.05.08,A.02.04 and then I manually downgraded modem firmware to L0.0.00.00.05.06 while XBee firmware stayed at 11415.

The problem causing EIO error could be something else though.

---

<div class="post-metadata">

**Author:** ![Craigus861](https://avatars.discourse-cdn.com/v4/letter/c/b5a626/32.png) [@Craigus861](https://forums.digi.com/u/Craigus861)\
**Post date:** [November 5, 2020, 9:05am UTC](https://forums.digi.com/t/sms-problems-with-digi-lte-m-nb-iot/21660/8 "2020-11-05T09:05:35Z")

</div>

That’s interesting. Seems they might be thinking its an issue with the cellular component. I have a XB3-C-A2-UT-001 RevK here with 11413 as it was out of the box. I will try SMS on that device. The one that I am having issues with I updated to 11415 and cellular component updated to L0.0.00.00.05.08,A.02.04 before testing SMS functionality.

---

<div class="post-metadata">

**Author:** ![juha.autioniemi](https://avatars.discourse-cdn.com/v4/letter/j/6de8d8/32.png) [@juha.autioniemi](https://forums.digi.com/u/juha.autioniemi)\
**Post date:** [November 5, 2020, 9:14am UTC](https://forums.digi.com/t/sms-problems-with-digi-lte-m-nb-iot/21660/9 "2020-11-05T09:14:06Z")

</div>

That does sound like same problem that I had (now its had) because I got it sorted out with tech support. Problem is solved for me by sending AT+USVCDOMAIN=2 command directly to the modem and then AT+CWPROFF after that wait about 20 seconds and reboot. I used USB-direct mode and XBIB-CU-TH dev board to send commands to cellular modem with ublox m-center software. I guess bypass mode could also be used, but seems like it is deprecated.

---

<div class="post-metadata">

**Author:** ![Craigus861](https://avatars.discourse-cdn.com/v4/letter/c/b5a626/32.png) [@Craigus861](https://forums.digi.com/u/Craigus861)\
**Post date:** [November 6, 2020, 8:38am UTC](https://forums.digi.com/t/sms-problems-with-digi-lte-m-nb-iot/21660/10 "2020-11-06T08:38:15Z")

</div>

That’s great news. Did you revert the u-blox firmware back to L0.0.00.00.05.08,A.02.04 before issuing the AT commands?  
Also does the issue return after power cycling the device? Some modem devices require a write to memory command after changing settings to make them permanent.

---

<div class="post-metadata">

**Author:** ![juha.autioniemi](https://avatars.discourse-cdn.com/v4/letter/j/6de8d8/32.png) [@juha.autioniemi](https://forums.digi.com/u/juha.autioniemi)\
**Post date:** [November 6, 2020, 9:05am UTC](https://forums.digi.com/t/sms-problems-with-digi-lte-m-nb-iot/21660/11 "2020-11-06T09:05:00Z")

</div>

I updated both xbee and modem firmwares to latest and then sent AT commands. AT+CPWROFF (corrected now) seems to save modem settings to nvram before reset. Settings are preserved after reboot - I didnt check by AT command but everything is working after reboot.
