MKR GSM 1400 hangs!

zeroone · May 18, 2019, 5:09pm

Hello,
i always got a hanging problem at the MKR GSM 1400, i tried by power off-on the system, or trying to move the SIM little forward/ backward / left / or right within its place when the system is off, sometimes it worked and sometimes it is not.

the gsm access check was at the setup:

  while (!connected) {
    if (gsmAccess.begin(PINNUMBER) == GSM_READY) {
      connected = true;
    } else {
      Serial.println("Not connected");
      delay(1000);
    }

.
now I moved the gsm access to check at the loop and also activate the debug as follows:

#include <MKRGSM.h>

#include "arduino_secrets.h" 
const char PINNUMBER[] = SECRET_PINNUMBER;
// initialize the library instance
GSM gsmAccess=1;
GSM_SMS sms;
bool connected = false;

void setup() 
{
  Serial.begin(9600);
  while (!Serial)
  {
    ;
  }
}

void loop()
{
  Serial.println("SMS Messages Sender");
  if (!connected)
  {
    if (gsmAccess.begin(PINNUMBER) == GSM_READY) connected = true;
  }
  else
  {
    Serial.println("Not connected");
    delay(15000);
  }
}

and also hangs but I attached the logs.

notes:

the SIM is working normally, i have tested it at SIM800c and also a phone.
i have tested the at different GSM 1400 MKR devices.
it seems there is a problem at the GSM library, yesterday i have downloaded an update for the library but the same problem

any suggesstions?

thanks

MKR1400DebugLogs.txt (11.9 KB)

pert · May 18, 2019, 5:12pm

Do you have a 1500 mAh or higher LiPo battery connected to your MKR GSM 1400?

zeroone · May 18, 2019, 5:14pm

pert:
Do you have a 1500 mAh or higher LiPo battery connected to your MKR GSM 1400?

no, just with USB power and also a VIN 5 V 2 A

zeroone · May 18, 2019, 11:03pm

I have an update:
I have tried another SIM from another provider and it is worked fine, I have attached an image for both SIMs.
my question, does it matter the SIM structure for Ublox modem of the MKR GSM 1400?

thanks

zeroone · May 22, 2019, 5:42pm

Hello,
after I have contacted Arduino support, they have informed:

Its a known issue of hangs because with the current hardware and software revision, the minimum reachable current consumption is 20mA (the level transistor consumes ~10mA each in every condition). However, we are working to achieve the best performances.

and also:

The MKR GSM 1400 board hangs time to time and its a known issue. I am talking generally on the MKR GSM 1400 board issue.
We are waiting for the answer to this issue.

they will do a refund for the products.
I hope to be solved quickly, so there is a new hardware version for the MKR GSM 1400!

PhysicsUofRAUI · June 8, 2019, 6:40pm

I am having this issue as well. Is it known to be a software issue or is it a hardware issue?

Cheers,

pert · June 8, 2019, 8:17pm

Based on your description, I can't say for sure if it's relevant to your problem, but you might read these recommendations on the use of the MKR GSM 1400 from the Arduino developers and see if it can be helpful to you:

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!

devyani · June 27, 2019, 4:42am

I'm having the same hang issue. Is this issue solved?

PhysicsUofRAUI · July 22, 2019, 3:52pm

PhysicsUofRAUI:
I am having this issue as well. Is it known to be a software issue or is it a hardware issue?

Cheers,

My problem went away after I added an antenna. This was the antenna I used https://www.amazon.ca/gp/product/B00N4YMMTG/ref=ppx_yo_dt_b_asin_title_o05_s00?ie=UTF8&psc=1

kickouille · July 26, 2019, 4:12pm

PhysicsUofRAUI,

Are you saying you didn't have any antenna connected?

As a general rule, always has a load like an an antenna connected to an RF system, else all power is reflected back to the chip and may fry it.

Concerning this hanging issue, I did also a lot of troubleshooting, and noticed I was always stuck at:
gsmAccess.begin(PINNUMBER)

By default, it is in sychronous mode, meaning that ones we enter this method, it will wait for a connection to the carrier. If none happens, it wil indefinitely stay in there.
If you want to have control on this or eventually execute something else while it is loking at the carrier, then go in asynchronous mode, and methos will return after every check.

This is documented here.

LTE-M and NB-IoT coverage in my area is bad, I was hitting my head on the walls before realizing this, and though I was having SW or HW issues...

Topic		Replies	Views
hanging at gsmAccess.begin() MKRGSM1400	5	2338	May 7, 2021
MKR GSM1400 hangs up in GSM_READY REQUEST Networking, Protocols, and Devices	4	158	November 17, 2023
read SIM problem MKRGSM1400	2	2576	May 7, 2021
MKRGSM 1400 Hanging Timeout MKRGSM1400	2	1209	November 18, 2022
gsmAccess fails MKRGSM1400	3	1729	May 7, 2021

MKR GSM 1400 hangs!

Related Topics