MKR GSM 1400 unreliable

kickouille · July 11, 2019, 9:18pm

Hi guys,

I am not able to get my MKR GSM 1400 running for a long period of time.

Context:

Board: MKR GSM 1400
2400 mAh LiPo connected
Dipole antenna
Swisscom Multi Device SIM card
Sketch: GPC_IoT_Core_GSM from Arduino Cloud Provider Examples
arduino_secrets.h configured as it should, everything else is out of the box
all libraries bords used in this context are up to date
Configuration on Google Cloud IoT Core is done

The board connects to the network and successfully connects Cloud IoT Core.
Messages published by the board are received by IoT Core.
Messages published by IoT Core are received by the board.

And after some time everything stops. The board need to be reset, and then it will reconnect.
The cycle goes on and on.
I'm looking after setting up a critical remote system, and as you may imagine, this is far from being ideal currently.

I attach the debug output. The last breath before dying is:

10:27:16.864 -> +USORD: 0,0,""
10:27:16.864 -> 
10:27:16.864 -> OK
10:27:16.908 -> AT+USORD=0,512

10:27:17.044 -> +USORD: 0,0,""
10:27:17.044 -> 
10:27:17.044 -> OK
10:27:17.044 -> AT+USORD=0,512

10:27:17.138 -> +USORD: 0,2,"D000"
10:27:17.138 -> 
10:27:17.138 -> OK
10:27:17.138 -> AT+USORD=0,512
Attempting to connect to MQTT broker: mqtt.googleapis.com

And then, nothing, stuck forever until next reset.

There is anoter successful reconnectin prior to that one:

10:25:22.113 -> +USORD: 0,0,""
10:25:22.113 -> 
10:25:22.113 -> OK
10:25:22.113 -> AT+USOCL=0

10:25:22.113 -> OK
10:25:22.113 -> Attempting to connect to MQTT broker: mqtt.googleapis.com 
10:25:22.113 -> AT+CCLK?

10:25:22.113 -> +CCLK: "19/07/10,10:25:17+08"
10:25:22.113 -> 
10:25:22.113 -> OK
10:25:22.113 -> AT+USOCR=6

10:25:22.113 -> +USOCR: 0
10:25:22.113 -> 
10:25:22.113 -> OK
10:25:22.113 -> AT+USOSEC=0,1,0

10:25:22.113 -> OK
10:25:22.113 -> AT+USECPRF=0,0,1

10:25:22.113 -> OK
10:25:22.113 -> AT+USOCO=0,"mqtt.googleapis.com",8883

10:25:22.113 -> OK

I noticed that it is happening each time on the second attempt to reconnect.

I didn't go too deep in the code for the moment, but did anybody encountered the same issue, or have any existing reference relating this behaviour?

Could anybody try to reproduce this?

Versions as I'm writing and testing:
Arduino SAMD board: 1.8.3
Arduino_JSON library: 0.1.0
ArduinoMqttClient library: 0.1.3

Regards

GSM1400hangs.txt (140 KB)

kickouille · July 11, 2019, 9:56pm

Quick update:

Exact same behaviour with an Hologram.io SIM card connecting to Sunrise in Switzerland.

So, problem doesn't come from the SIM nor the Provider nor the coverage.

I also attach the debug output.

Regards

GSM1400hangsHologram.txt (65.7 KB)

pert · July 12, 2019, 12:01am

Hi. I haven't closely studied your issue, but you should check out this information to see if it's relevant:

github.com/arduino-libraries/MKRGSM

MKRGSM library not reliable

opened 08:24PM - 20 Nov 18 UTC

alanoatwork

type: imperfection

I've posted this before, but I'll try again. My code is pretty simple. I check f…or SMS messages and then reply back using Hologram's network. I'm using the latest MKRGSM library 1.3.1. I also have a 1400 mAhr lithium battery connected so I'm confident that I don't have a hardware issue related to modem current. Here's my code: ``` #include <MKRGSM.h> const char PINNUMBER[] = " "; const char GPRS_APN[] = "hologram"; const char GPRS_LOGIN[] = " "; const char GPRS_PASSWORD[] = " "; String HOLOGRAM_DEVICE_KEY = "********"; String HOLOGRAM_TOPIC = "_SOCKETAPI_"; GSMClient client; GPRS gprs; GSM gsm(1); // Enable debug GSM_SMS sms; GSMScanner scan; char server[] = "cloudsocket.hologram.io"; int port = 9999; boolean isSMSAvailable = false; char sms_message[145]; void setup() { Serial.begin(115200); //while(!Serial); scan.begin(); connectGSM(); } void connectGSM() { boolean connected = false; while (!connected) { Serial.println("Begin GSM Access"); if ((gsm.begin() == GSM_READY) && (gprs.attachGPRS(GPRS_APN, GPRS_LOGIN, GPRS_PASSWORD) == GPRS_READY)) { connected = true; Serial.println("GSM Access Success"); Serial.println(scan.getCurrentCarrier()); } else { Serial.println("Not connected"); delay(1000); } } } void loop() { if(Serial.available()) { char c = Serial.read(); if(c == 'e') MODEM.debug(); if(c == 'd') MODEM.noDebug(); } // Get any new incoming txt messages int c; if (sms.available()) { int i = 0; while ((c = sms.read()) != -1) { sms_message[i++] = (char)c; } sms_message[i] = '\0'; // Terminate message isSMSAvailable = true; sms.flush(); } if(gsm.isAccessAlive()) { if(gprs.status() != GPRS_READY) { if(gprs.attachGPRS(GPRS_APN, GPRS_LOGIN, GPRS_PASSWORD) == GPRS_READY) Serial.println("GPRS ready!"); else Serial.println("GRPS not ready!"); } } else { Serial.println("Reconnect to GSM..."); connectGSM(); } // Send message back through hologram if(isSMSAvailable) { isSMSAvailable = false; if (client.connect(server, port)) { client.print("{\"k\":\"" + HOLOGRAM_DEVICE_KEY + "\",\"d\":\""); client.print(sms_message); client.println("\",\"t\":\""+HOLOGRAM_TOPIC+"\"}"); client.stop(); } else { MODEM.send("AT+USOER"); } } delay(1000); }` ``` It takes anywhere from a few days to a week or more to exhibit the problem. My logs typically look like this, where the incoming SMS message, "Jdjd", gets received and then repeated back to me via Hologram's network. ``` OK AT+CMGL="REC UNREAD" +CMGL: 19,"REC UNREAD","+19495472010",,"18/11/14,03:53:24+00" Jdjd OK AT+CMGD=19 OK AT+CREG? +CREG: 0,5 OK AT+USOCR=6 +USOCR: 0 OK AT+USOCO=0,"cloudsocket.hologram.io",9999 OK AT+USOWR=0,21,"7B226B223A22433E383375242B57222C2264223A22" +USOWR: 0,21 OK AT+USOWR=0,4,"4A646A64" +USOWR: 0,4 OK AT+USOWR=0,20,"222C2274223A225F534F434B45544150495F227D" +USOWR: 0,20 OK AT+USOWR=0,2,"0D0A" +USOWR: 0,2 OK AT+USOCL=0 OK AT+CMGL="REC UNREAD" OK AT+CREG? +CREG: 0,5` ``` However, after a week or so this happens: ``` `OK AT+CMGL="REC UNREAD" +CMGL: 19,"REC UNREAD","+19495472010",,"18/11/20,19:51:00+00" JDJDJ OK AT+CMGD=19 OK AT+CREG? +CREG: 0,5 OK AT+USOCR=6 +USOCR: 0 OK AT+USOCO=0,"cloudsocket.hologram.io",9999 ERROR +UUSOCL: 0 AT+USOCL=0 ERROR AT+CMGL="REC UNREAD" OK AT+CREG? +CREG: 0,5 OK AT+CMGL="REC UNREAD" OK AT+CREG? +CREG: 0,5 ```` From then on, the library is never able to recover. Any help would be greatly appreciated. The code I submitted is a stripped down version of my application. I've been wanting to release my application using the MKRGSM board but I've been haunted by this issue. I see there's some asynchronous options that aren't well documented and I'm reluctant to use this approach - besides, shouldn't this library be rock solid as documented!

kickouille · July 13, 2019, 10:41am

Hi pert,

I did see this GitHub issue prior to my post, however based on following comment I thought it was not applicable to my case:

github.com/arduino-libraries/MKRGSM

MKRGSM library not reliable

opened 08:24PM - 20 Nov 18 UTC

alanoatwork

type: imperfection

I've posted this before, but I'll try again. My code is pretty simple. I check f…or SMS messages and then reply back using Hologram's network. I'm using the latest MKRGSM library 1.3.1. I also have a 1400 mAhr lithium battery connected so I'm confident that I don't have a hardware issue related to modem current. Here's my code: ``` #include <MKRGSM.h> const char PINNUMBER[] = " "; const char GPRS_APN[] = "hologram"; const char GPRS_LOGIN[] = " "; const char GPRS_PASSWORD[] = " "; String HOLOGRAM_DEVICE_KEY = "********"; String HOLOGRAM_TOPIC = "_SOCKETAPI_"; GSMClient client; GPRS gprs; GSM gsm(1); // Enable debug GSM_SMS sms; GSMScanner scan; char server[] = "cloudsocket.hologram.io"; int port = 9999; boolean isSMSAvailable = false; char sms_message[145]; void setup() { Serial.begin(115200); //while(!Serial); scan.begin(); connectGSM(); } void connectGSM() { boolean connected = false; while (!connected) { Serial.println("Begin GSM Access"); if ((gsm.begin() == GSM_READY) && (gprs.attachGPRS(GPRS_APN, GPRS_LOGIN, GPRS_PASSWORD) == GPRS_READY)) { connected = true; Serial.println("GSM Access Success"); Serial.println(scan.getCurrentCarrier()); } else { Serial.println("Not connected"); delay(1000); } } } void loop() { if(Serial.available()) { char c = Serial.read(); if(c == 'e') MODEM.debug(); if(c == 'd') MODEM.noDebug(); } // Get any new incoming txt messages int c; if (sms.available()) { int i = 0; while ((c = sms.read()) != -1) { sms_message[i++] = (char)c; } sms_message[i] = '\0'; // Terminate message isSMSAvailable = true; sms.flush(); } if(gsm.isAccessAlive()) { if(gprs.status() != GPRS_READY) { if(gprs.attachGPRS(GPRS_APN, GPRS_LOGIN, GPRS_PASSWORD) == GPRS_READY) Serial.println("GPRS ready!"); else Serial.println("GRPS not ready!"); } } else { Serial.println("Reconnect to GSM..."); connectGSM(); } // Send message back through hologram if(isSMSAvailable) { isSMSAvailable = false; if (client.connect(server, port)) { client.print("{\"k\":\"" + HOLOGRAM_DEVICE_KEY + "\",\"d\":\""); client.print(sms_message); client.println("\",\"t\":\""+HOLOGRAM_TOPIC+"\"}"); client.stop(); } else { MODEM.send("AT+USOER"); } } delay(1000); }` ``` It takes anywhere from a few days to a week or more to exhibit the problem. My logs typically look like this, where the incoming SMS message, "Jdjd", gets received and then repeated back to me via Hologram's network. ``` OK AT+CMGL="REC UNREAD" +CMGL: 19,"REC UNREAD","+19495472010",,"18/11/14,03:53:24+00" Jdjd OK AT+CMGD=19 OK AT+CREG? +CREG: 0,5 OK AT+USOCR=6 +USOCR: 0 OK AT+USOCO=0,"cloudsocket.hologram.io",9999 OK AT+USOWR=0,21,"7B226B223A22433E383375242B57222C2264223A22" +USOWR: 0,21 OK AT+USOWR=0,4,"4A646A64" +USOWR: 0,4 OK AT+USOWR=0,20,"222C2274223A225F534F434B45544150495F227D" +USOWR: 0,20 OK AT+USOWR=0,2,"0D0A" +USOWR: 0,2 OK AT+USOCL=0 OK AT+CMGL="REC UNREAD" OK AT+CREG? +CREG: 0,5` ``` However, after a week or so this happens: ``` `OK AT+CMGL="REC UNREAD" +CMGL: 19,"REC UNREAD","+19495472010",,"18/11/20,19:51:00+00" JDJDJ OK AT+CMGD=19 OK AT+CREG? +CREG: 0,5 OK AT+USOCR=6 +USOCR: 0 OK AT+USOCO=0,"cloudsocket.hologram.io",9999 ERROR +UUSOCL: 0 AT+USOCL=0 ERROR AT+CMGL="REC UNREAD" OK AT+CREG? +CREG: 0,5 OK AT+CMGL="REC UNREAD" OK AT+CREG? +CREG: 0,5 ```` From then on, the library is never able to recover. Any help would be greatly appreciated. The code I submitted is a stripped down version of my application. I've been wanting to release my application using the MKRGSM board but I've been haunted by this issue. I see there's some asynchronous options that aren't well documented and I'm reluctant to use this approach - besides, shouldn't this library be rock solid as documented!

Indeed I am not using VIN and have a 1s 3.7V 2400mAh LiPo constantly connected capable of delivering 20C continuous, 40C peaks.
In addition I'm connecting in 3G, not 2G

And using the USB port as charging source.

Is this setup problematic needing some changes or should it be ok?

Thing I believe is a bit weird is that I have been able to have this setup run for about 1 day at the beginning, then it went down to half a day, then 1 or 2 hours, and now it only works for less than 5 minutes before being stuck, needing a good reset.

k4hvd · July 13, 2019, 11:14pm

Are you using MKRGSM Library? Which version?

kickouille · July 14, 2019, 12:56pm

Hi k4hvd,

Yes, MKRGSM library version is 1.4.2.

Quick update, I have been able to make my board work in the long run following Arduino IoT Cloud Google Sheets Integration project.

It uses the same libraries, MKRGSM, ArduinoMqttClient as the out of the box GCP_IoT_Core_GSM coming from Arduino Cloud Providers Example "lib".
Note that I'm encoutering similar bad behaviours with my MKRNB 1500.

So the problem certainly comes from the example code, where connections to GSM/NB networks and MQTT client are not handled properly.

What do you think?

Here is the code which is 6 months old now, I'm surprised that nobody encountered similar issues.

k4hvd · July 14, 2019, 7:45pm

Have you tried to set the timeouts?

mqtt
.setKeepAliveInterval
.setConnectionTimeout

MKRGSM's

gsmaccess
.setTimeout
gprs
.setTimeout

kickouille · July 18, 2019, 12:38pm

Hello,

I got the board working with with the Arduino IoT Cloud, stable in the long run.
So I took inspiration on the code, especially GSMConnectionManager.cpp and I have been able to get a stable connection took.
I would recommend for anybody using this board and the MKRNB to take a look at this code, as it is very well done, in a non blocking way.

Regards

Topic		Replies	Views
MKR1400 very unstable! MKR GSM 1400	2	4212	May 7, 2021
DON'T buy this mkrgsm 1400 MKR GSM 1400	2	3046	May 7, 2021
MKR GSM 1400 Phone-enabled Garage Opener Issues General Guidance	21	676	March 20, 2024
Problems getting the MKR 1400 to work MKR GSM 1400	6	4978	May 7, 2021
MKR GSM 1400 Wont connect to Arduino Cloud GSM Shield	7	11298	May 6, 2021

MKR GSM 1400 unreliable

Related topics