incoming SMS messages delayed 15-30 minutes

[jimk123]

hoping someone here may have seen an issue like this which is driving me crazy :(

hardware used:
Arduino Mega 2560 Rev3
https://www.botletics.com/products/sim7000-shield (using the SIM7000A version which I was told is for America)

I had previously used an Adafruit FONA shield with the Mega board with great success, it has been running in a remote location for many years at 100% uptime! I am in the USA and Adafruit is not offering a replacement that will work on a 4G LTE networks and the phone companies are turning off 3G service in my area.

I bought the botletics shield since it seemed the closest replacement to the FONA shield, it appears they cloned adafruit FONA library (the same filenames Adafruit_FONA.cpp) and have made minor changes to support the SIM7000 board.

The problem I am having is the SIM7000A shield is not receiving SMS messages reliably, it often takes 15-30 minutes to show up unless I power cycle the SIM7000A shield.

I have tried two different SIM cards, one from Ting which is the company I used for the FONA 3G board (they sent me a newer SIM card for the SIM7000A shield and also I bought a Tmobile phone number and SIM).

The code sends SMS messages twice a day fine, but does not reliably process an incoming SMS message, sometimes it will work for a few hours or even a day or two getting new messages right away, other times taking 15-30 minutes to arrive.

this is an example of the console log showing the issue:

The code is based on the botletics LTE_DEMO which is almost identical the the adafruit sample code. https://github.com/botletics/SIM7000-LT ... -IDE-Setup which appears to use the the same FONA adafruit code.


I sent a txt msg at 6:44 am, I have a timer job every 10 seconds running that calls the 'readAllSMS' routine.
note: I also tried the loop method in their example SMS_Response with the same results.

As you can see in the log it does not find any new incoming message until almost 30 minutes later (sometimes they come in immediately or if I restart the SIM7000A it will show up right away)
I also have a one minute timer running to get the time of day using the AT+CCLK command which I use to send msgs at specific hours. (fyi - for privacy I have replaced my phone number with 1234567)



06:43:37.924 -> -----------------timer pop read SMS-------------
06:43:37.958 -> ---> AT+CMGF=1
06:43:38.002 -> <--- OK
06:43:38.049 -> ---> AT+CPMS?
06:43:38.096 -> <--- +CPMS: "SM",0,30,"SM",0,30,"SM",0,30
06:43:38.096 -> readAllSMS() number of sms msgs=0
06:43:39.549 ->
06:43:39.549 -> ----------------- timer pop read clock-------------
06:43:39.596 -> ---> AT+CGREG?
06:43:39.643 -> <--- +CGREG: 0,1
06:43:39.643 -> network status (0=disc 1=connected) = 1
06:43:39.690 -> ---> AT+CCLK?
06:43:39.736 -> <--- +CCLK: "22/10/31,06:43:39-16"
06:43:39.736 -> the time is: "22/10/31,06:43:39-16"
06:43:39.736 -> found hour other than 00 - ignore
06:43:39.783 -> found hour other than 16 - ignore
06:43:39.783 -> found hour other than 08 - ignore
06:43:48.101 ->
06:43:48.101 -> -----------------timer pop read SMS-------------
06:43:48.142 -> ---> AT+CMGF=1
06:43:48.142 -> <--- OK
06:43:48.223 -> ---> AT+CPMS?
06:43:48.283 -> <--- +CPMS: "SM",0,30,"SM",0,30,"SM",0,30
06:43:48.283 -> readAllSMS() number of sms msgs=0
06:43:58.314 ->
06:43:58.314 -> -----------------timer pop read SMS-------------
06:43:58.314 -> ---> AT+CMGF=1
06:43:58.347 -> <--- OK
06:43:58.394 -> ---> AT+CPMS?
06:43:58.438 -> <--- +CPMS: "SM",0,30,"SM",0,30,"SM",0,30
06:43:58.438 -> readAllSMS() number of sms msgs=0
06:44:08.486 ->
06:44:08.486 -> -----------------timer pop read SMS-------------
06:44:08.486 -> ---> AT+CMGF=1
06:44:08.533 -> <--- OK
06:44:08.579 -> ---> AT+CPMS?
06:44:08.626 -> <--- +CPMS: "SM",0,30,"SM",0,30,"SM",0,30
06:44:08.626 -> readAllSMS() number of sms msgs=0
06:44:18.618 ->
06:44:18.618 -> -----------------timer pop read SMS-------------
06:44:18.666 -> ---> AT+CMGF=1
06:44:18.713 -> <--- OK
06:44:18.751 -> ---> AT+CPMS?
06:44:18.804 -> <--- +CPMS: "SM",0,30,"SM",0,30,"SM",0,30
06:44:18.804 -> readAllSMS() number of sms msgs=0
06:44:28.816 ->


.
. (trimmed the log for read purposes)
.



07:13:30.205 -> -----------------timer pop read SMS-------------
07:13:30.253 -> ---> AT+CMGF=1
07:13:30.253 -> <--- OK
07:13:30.611 -> ---> AT+CPMS?
07:13:30.611 -> <--- +CPMS: "SM",0,30,"SM",0,30,"SM",0,30
07:13:30.611 -> readAllSMS() number of sms msgs=0


then at 7:13:40 it finally sees the message I sent at 6:44 am "morning", notice the time stamp in the +CMGR line "22/10/31,03:44:24-28"

03:44 = 6:44 is when I sent it from my phone but it did not arrive until 7:13 am

I don't know if this is a problem with the cell phone carrier (I have tried two different carriers SIM cards, Tmobile and Ting) or the shield, or ???

07:13:40.361 ->
07:13:40.361 -> -----------------timer pop read SMS-------------
07:13:40.517 -> ---> AT+CMGF=1
07:13:40.517 -> <--- OK
07:13:40.517 -> ---> AT+CPMS?
07:13:40.554 -> <--- +CPMS: "SM",1,30,"SM",1,30,"SM",1,30
07:13:40.554 -> readAllSMS() number of sms msgs=1
07:13:40.554 ->
07:13:40.554 ->
Reading SMS #0
07:13:40.595 -> ---> AT+CMGF=1
07:13:40.595 -> <--- OK
07:13:40.642 -> ---> AT+CSDH=1
07:13:40.689 -> <--- OK
07:13:40.689 -> ---> AT+CMGR=0
07:13:40.798 -> +CMGR: "REC UNREAD","+18601234567",,"22/10/31,03:44:24-28",145,4,0,0,"+14054720056",145,8
07:13:40.862 -> Morning
07:13:40.862 -> ***** SMS #0 (8) bytes *****
07:13:40.862 -> Morning
07:13:40.862 -> *****
07:13:40.862 -> NOW DELETE SMS MSG
07:13:40.862 -> Deleting SMS #0
07:13:40.907 -> ---> AT+CMGF=1
07:13:40.907 -> <--- OK
07:13:40.955 -> ---> AT+CMGD=000
07:13:41.037 -> <--- OK
07:13:41.037 -> OK!
07:13:47.017 ->
07:13:47.017 -> ----------------- timer pop read clock-------------
07:13:47.065 -> ---> AT+CGREG?
07:13:47.100 -> <--- +CGREG: 0,1
07:13:47.100 -> network status (0=disc 1=connected) = 1
07:13:47.142 -> ---> AT+CCLK?
07:13:47.192 -> <--- +CCLK: "22/10/31,07:13:46-16"
07:13:47.192 -> the time is: "22/10/31,07:13:46-16"
07:13:47.235 -> found hour other than 00 - ignore
07:13:47.235 -> found hour other than 16 - ignore
07:13:47.235 -> found hour other than 08 - ignore
07:13:51.048 ->
07:13:51.048 -> -----------------timer pop read SMS-------------
07:13:51.082 -> ---> AT+CMGF=1
07:13:51.130 -> <--- OK
07:13:51.173 -> ---> AT+CPMS?
07:13:51.206 -> <--- +CPMS: "SM",0,30,"SM",0,30,"SM",0,30
07:13:51.206 -> readAllSMS() number of sms msgs=0
07:14:01.252 ->
07:14:01.252 -> -----------------timer pop read SMS-------------
07:14:01.300 -> ---> AT+CMGF=1
07:14:01.300 -> <--- OK
07:14:01.733 -> ---> AT+CPMS?
07:14:01.733 -> <--- +CPMS: "SM",0,30,"SM",0,30,"SM",0,30
07:14:01.733 -> readAllSMS() number of sms msgs=0
07:14:11.408 ->



two times a day at 8am and 4pm it sends me a SMS txt, this part works fine

08:00:51.283 -> -----------------timer pop read SMS-------------
08:00:51.317 -> ---> AT+CMGF=1
08:00:51.364 -> <--- OK
08:00:51.407 -> ---> AT+CPMS?
08:00:51.456 -> <--- +CPMS: "SM",0,30,"SM",0,30,"SM",0,30
08:00:51.456 -> readAllSMS() number of sms msgs=0
08:00:58.782 ->
08:00:58.782 -> ----------------- timer pop read clock-------------
08:00:59.004 -> ---> AT+CGREG?
08:00:59.004 -> <--- +CGREG: 0,1
08:00:59.004 -> network status (0=disc 1=connected) = 1
08:00:59.004 -> ---> AT+CCLK?
08:00:59.004 -> <--- +CCLK: "22/10/31,08:00:58-16"
08:00:59.004 -> the time is: "22/10/31,08:00:58-16"
08:00:59.004 -> found hour other than 00 - ignore
08:00:59.004 -> found hour other than 16 - ignore
08:00:59.004 -> The hour is 08
08:00:59.004 -> FOUND a new hour 8am
08:00:59.004 -> Send SMS to: +18601234567 message length: 13
08:00:59.004 -> message = 8am status
08:00:59.004 -> ok
08:00:59.004 -> ---> AT+CMGF=1
08:00:59.019 -> <--- OK
08:00:59.064 -> ---> AT+CMGS="+18601234567"
08:00:59.595 -> <--- >
08:00:59.688 -> SEND ^Z
08:01:00.079 -> found +CMGS in replybuffer, return true
08:01:00.126 -> ***Sent!***
08:01:01.455 ->
08:01:01.455 -> -----------------timer pop read SMS-------------
08:01:01.535 -> ---> AT+CMGF=1
08:01:01.535 -> <--- OK
08:01:01.594 -> ---> AT+CPMS?
08:01:01.641 -> <--- +CPMS: "SM",0,30,"SM",0,30,"SM",0,30
08:01:01.641 -> readAllSMS() number of sms msgs=0
08:01:11.660 ->

[Tkall]

Jim,
I seem to remember something like this happening to me. I called the provider, ting, explained the problem and IIRC, they reset something on their end. Sorry I dont recall more detail.
Tom

[jimk123]

Is this Tom?
Thanks for the info, i will call them in the morning. I did purchase a tmobile number and SIM hoping it would be better than ting but they both have the same issue. It is odd i can send msg and it will not show up for 15-30 minutes but and hour later if i send another one it comes in right away.

My phone is on att and was wondering if i bought a att sim if it might be better if both my phone and the SIM are on the same network but their plans are much more money than ting or tmobile and i only need sms.

How did you make out with your botletics SIM7000 project?
Thanks

[Tkall]

Yes, This is Tom.
I can try sending one if you want to see if there is any difference. I received the botletics device and the hologram sims and the particle devices. I have been so busy with stupid stuff that I haven't had time. The time I've had I have been dedicating to a new hobby which has really been pulling me away from things. I plan on outfitting a about 100 control panels with telemetry over the next few months. Now that will be fun. Let me know if you want me to call your device.
Tom

[jimk123]

100 devices ? Yikes that will keep you busy.
Tomorrow i was going to start keeping a log by sending a new sms msg once an hour and record which ones are received right away and what the delay is on the others. That is what is so odd here, some arrive immediately, others 15-30 minutes later.

Will let you know the results from that and will call ting and see what they say.
Thanks Tom

[rskup]

I've also run into this same maddening super "slow to receive SMS" issue with two different SIM7000G breakout boards and gave up, deciding to only buy LTE boards from now on, rather than LTE-M and/or NB-IoT boards.

However after seeing this post I dug back into the issue again, I'm now wondering if it's because (at least according to) this T-Mobile web page that does not show the SIM7000 as "certified" for their network. After opening the webpage, go down to "Manufacturers" and check "SIMCom", the 7000 is not there.

Maybe (?) whatever "handshaking" that is required for reliable SMS RX/TX between the tower and the 7000 isn't all quite there and that's why it doesn't show up in T-Mobile's certified list.

Note it shows the 7070G, 7080G, and 7090G as certified (all LTE-M/NB-IoT), and has the "Yes" after "SMS". Interesting it shows the 7600G as certified (and with the Yes after SMS) and the 7600G breakout board I have has no issues with sending/receiving SMS.

The other thing I'm now wondering is could the issue have to do with the eDRX (Extended Discontinuous Reception) ability of the 7000 and its settings, as it controls power consumption and battery life. Maybe the chip only rarely powers up the RF section to "listen" for any SMS to receive??

Anyways, just some thoughts/ideas on this issue, nothing concrete, will aim to try/test both boards again and see if I can find out anything else.

[jimk123]

Thank you for that info, i never realized the different levels between LTE , LTE-M, etc

For years i used the adafruit Fona hardware and Ting SIM cards with great success.

Curious your comment on buying only LTE boards, can you recommend any that work in the USA ? Was hoping to find a shield footprint like the fona i could continue to use with the arduino.
Thanks

[rskup]

Here's the Waveshare LTE board I'm currently using, based on the SIM7600G, along with a T-Mobile sim (their inexpensive $15/month Connect plan).

There is also this smaller Waveshare board , still based on the 7600G, would like to order that someday.

On both chips, the "-H" supposedly means higher data rate, like 150Mbps vs 10Mbps without the "-H" (but no doubt also means more power).

However if I could reliably use the SMS on a LTE-M/NB-IoT chip I'd certainly be interested, as those chips draw so little power it would be great for a gps tracker, remote applications, etc....

[jimk123]

thanks for the links, are you using this in the USA ? were you able to use the adafruit FONA library with these ? (I am not a programmer) Did this board allow you to reliably receive incoming SMS messages ?

I am running a test today sending a new SMS message every hour, so far I sent 5 messages, 4 received immediately, one took 48 minutes to arrive.
thanks !

[rskup]

Yes, am in the US. Currently that big Waveshare board is connected to a Raspberry Pi and I'm using Python to control the board. I'm not a good programmer, but early on when learning how to use the FONA 3G with the FONA library it just bugged me I didn't really know what was going on so I learned how to write sketches for the FONA 3G based off the 5320 AT Command manual and later how to code the same in Python for my other boards.

It seems that "in general" the AT commands between the 5320, 7000, and 7600, stay the same. Sometimes there's slight differences, but so far I've been able to figure things out as the AT manuals for all the boards have lots of info.

What might help you though is that it looks like Botletics has a 7500 library (which is based on the FONA library), and the AT command manual for the 7500 is actually titled, "SIM7500 SIM7600 Series AT Command Manual". And it's not like that manual is divided into two sections, so, at first glance, it would seem this Botletics library would also work for the 7600??? Maybe I'm way off on this, but thought I'd mention it anyways.

As far as "reliably receive" SMS messages quickly, I would say yes, but let me also test that today like you are throughout the day so that we have some "stats" on that.




https://github.com/botletics/SIM7500-LTE-Shield

[Tkall]

Is this Tom?
Thanks for the info, i will call them in the morning. I did purchase a tmobile number and SIM hoping it would be better than ting but they both have the same issue. It is odd i can send msg and it will not show up for 15-30 minutes but and hour later if i send another one it comes in right away.

My phone is on att and was wondering if i bought a att sim if it might be better if both my phone and the SIM are on the same network but their plans are much more money than ting or tmobile and i only need sms.

How did you make out with your botletics SIM7000 project?
Thanks

Jim,
When I tried to get Ting to send me a SIM for the Botletics, they said it would not work with their network based on the BANNED number. The forum changed my post with the word Banned. I was referring to the identification number of the cell module.

[jimk123]

rskup
thanks for the feedback, I may have to buy that board and start over. I originally started with the Ting service for the old FONA boards, and someone else here commented to call them. Most of this is over my head but maybe if I explain this is a SIM7000 LTE CAT-M1/NB-IoT device they can offer a SIM that works with it ? Not sure if that is tied to a specific type of SIM or something they can turn features on/off on their side.

I also have a Tmobile SIM card having the same delays but I have found Ting to be very responsive over the years and willing to escalate to a technical person if needed.

btw - I sent a total of 10 SMS msgs once an hour from 8am to 5pm today, 3 of them failed to deliver right away taking 10-40 minutes to arrive, the other 7 arrived immediately. Unfortunately for my application I need something highly reliable for new incoming messages. I use these on my boat to toggle deck lights on/off, air conditioning, etc. Would be very curious to see your results on the WaveShare board.

my code also sends outgoing messages twice a day at 8am and 4pm and those always work.
thanks

[Tkall]

Jim,
Did you see my comment in 11?

[jimk123]

Hi Tom
I missed that, thank you. Will be curious what they say when i call. Otherwise it looks like i have to give up on the botletics board and start over with the waveshare.

[rskup]

Hi Jim, maybe don't get the Waveshare board just yet, here's a quick test update so far....out of 16 messages sent to the Waveshare board from my regular cell phone, 12 arrived within seconds.

Three messages were not arriving and after 5 to 10 minutes I got a little curious and purposely sent a text from the Waveshare board back to my cell phone to see if the delayed messages would arrive, and they did. It seems like sending a message also somehow kicks off a check to see if there are also messages waiting. Anyways, in all three cases, immediately after sending a text from the Waveshare board, the delayed messages arrived.

In the last delayed case I decided to do nothing and just waited, and it took about 40 minutes for the message to arrive.

So, this board isn't foolproof either. Maybe in your code you should fire off a text back along the lines of "message received" to know whether anything you want to control actually got the message??

Ok, well, I'm gonna try to do some more testing and reading, maybe I'll find a way to check for messages without having to send a text.