Portenta CAT.M1/NB IoT GNSS Shield connecting failure

[brinata]

Hello,

I'm using the Portenta CAT.M1/NB IoT GNSS Shield with the EDGE CONTROL board.

if the application fails the initial connection process because the signal strength is low or because the general latency of the GSM network, the GSM library in not able to reconnect: when I try to run the GSM.begin() again, the application program stop working after receiving the "^SYSSTART" string from the modem:

The board was not able to register to the network...
[000270[INFO][CELL]: AT TX ( 2): AT
[000270[INFO][CELL]: AT TX ( 1):
[000303[INFO][CELL]: AT RX ( 2):
[000303[INFO][CELL]: AT RX (11): ^SYSSTART
[000304[INFO][CELL]: AT RX ( 2):
[000304[INFO][CELL]: AT RX ( 6): +CIEV:
[000304[INFO][CELL]: AT RX (14): prov,0,"fallb
[000304[INFO][CELL]: AT RX ( 7): 3gpp"

The only way to re-start is reset the board.

I'm using the mbed 4.1.15

to simulate the problem I forced the following retry table in the GSM.h file:

const uint16_t _retry_timeout[3] = {1, 2, 4};

Please help me because I can't reset the whole application program to re-start the connectivity ....

GSMClient.txt
sketch_yaml.txt

[pennam]

@brinata I think I was able to reproduce your issue and I've proposed a fix in #975 . The PR needs to be used with some other changes in the Arduino_ConnectionHandler arduino-libraries/Arduino_ConnectionHandler#131

Do you mind give it a spin on your hardware?

Thanks

[brinata]

I've made some test, with these results:

moduel non connected yet

setting the timeout value at 1000 ms and calling the shutdown(), it seems that the library is able to re-try the connection procedure with success

module already connected

if you call the GSM.disconnect() function, then the library is not able to recover its initial state and the only way to re-initialize the Gsm Interface is reboot the cpu

[pennam]

module already connected

if you call the GSM.disconnect() function, then the library is not able to recover its initial state and the only way to re-initialize the Gsm Interface is reboot the cpu

@brinata can you share the sketch to reproduce this scenario?

[pennam]

@brinata also make sure to call GSM.end() after GSM.disconnect() and before the new GSMbegin() retry.

[brinata]

here the sketch GSMClient.txt

please note that:
if you run the GSM.begin() with reset = false and you don't call the _device->shutdown() it works
I've modified the end function as follow:
void arduino::GSMClass::end() {
if(_device) {
_device->shutdown();
_device->get_at_handler()->set_urc_handler("^SYSSTART", nullptr);
}
}
because the SYSSTART handler tries to close all the sockets after reboot, locking the modem: cancelling the ^SYSSTART handler the modem is not locket any more, but the connection is still missing ....

... please help

[pennam]

Hi @brinata
I was able to reproduce the issue and found a fix.
I've rebased #975 on the main branch included your suggestion to disable ^SYSSTART urc on shutdown and added the fix that allows reconnections.

I've also updated the connectionHandler PR arduino-libraries/Arduino_ConnectionHandler#131 including a test sketch that is doing the following:

• connects to the network
• make recurring http requests while connected
• disconnect from the network after 60s
• wait 60s before connecting again to the network and restart http requests

[brinata]

Hi Pennam,

Was you able to verify if the GSM library works when an "Asynchronous" disconnection happens ? for instance, when the account credit is expired or when the signal strenght is poor ?

Moreover, very often Network operators allow the connection with no account credit, even if the connection will not work....

how is it possibile to check these condition ?

As writtend in the CINTERION dos, About the ^SYSSTART, I suggest to use it to generate an event that signals the modem startup.

for the shutdown , reset, and re-start , the manual suggest the software fast shutdown command AT^SMSO="fast" to power off the module and the AT+CFUN=1,1 to reset it

About Hardware reset, the docs say:

Warning:
Use the EMERG_RST line only when, due to serious problems, the software is not responding
for more than 5 seconds. Pulling the EMERG_RST line causes the loss of all information
stored in the volatile memory. Therefore, this procedure is intended only for use in case of
emergency, e.g. if Cinterion® TX62/TX82 does not respond, if reset or shutdown via AT
command fails.

[pennam]

Hi @brinata,
I've updated #975 and arduino-libraries/Arduino_ConnectionHandler#131 to address your requests.

• Emergency reset is disabled by default, and no more triggered each time begin() fuction is called. I've addad a bit of logic to the ConnectionHandler in order to trigger a modem hardware reset if network registration fails, but this is not mandatory and can be removed.

• shutdown function does not call anymore AT+CFUN=0. it just reset the internal cellular state machine, so ^SYSSTART is not triggered anymore each time begin is called. I've also restored the ^SYSTART URC and to be safe I've reduced the AT timeout in the SYSSTART handler to avoid to get stuck closing the sockets and trigger the watchdog.

• I've added GSM.off() to send AT^SMSO="fast" and GSM.reset() to send AT+CFUN=1,1. This two functions should be called always after GSM.end()

Was you able to verify if the GSM library works when an "Asynchronous" disconnection happens ? for instance, when the account credit is expired or when the signal strenght is poor ?

I've made some test about this disconnecting the antenna from the modem. As soon as the modem detects there is no network the +CGEV: NW DET urc is triggered and the network status is updated. You can check this condition from the application calling GSM.isConnected() like is done in the connectionHandler.

Moreover, very often Network operators allow the connection with no account credit, even if the connection will not work.... how is it possibile to check these condition ?

In this condition GSM.isConnected() is returning true, but the sockets will timeout. I've added the GSM.ping(...) function and added a check inside the connectionHandler before the transition to the CONNECTED state. If the modem is attached to the network, but there is no connectivity it will stay in the DISCONNECTED state.