Issues with m2m roaming card - What are my debugging options? | Thales IoT Developer Community
August 19, 2019 - 4:25pm, 3541 views
Hello,
I use a PLS8-E with an embedded Linux device. When I use a regular german post paid SIM, I have no problems registering with the network at all. Also, reconnections after lost coverage work perfectly fine.
When I use a pre paid m2m roaming card (it roams by default to offer all of Europe, vendor is Datamobile), it happens fairly often that the modem is not started properly after booting. It also happens that I loose connection permanently after a temporary loss of coverage.
When the modem does not come up properly, it fails in this step:
execute: PLS8 /etc/modems/service|/etc/modems/roaming
Which is either:
cat /etc/modems/roaming
ABORT BUSY
ABORT ERROR
'' AT+CREG?
'+CREG: 0,5'
or:
cat /etc/modems/service
ABORT BUSY
ABORT ERROR
'' AT+CREG?
'+CREG: 0,1'
I assume that the device does offer information on the issue it has occured, but I do not know what my debugging options are here. I just see that it has failed and that subsequently pppd will not be started due to the failure. How can I obtain more information on what is happening here?
Thanks. BR.
Hello,
I have obtained a copy of the update program now. Update went fine on Linux. Did not manage to get an update running on Windows despite all devices being enumerated.
The problem persists after update to 3.017 (confirmed via ATI1).
CEER outputs I came across were:
+CEER: Requested service option not subscribed
+CEER: No Suitable cells in tracking area
+CEER: No cause information available
+CEER: EMM attach failed
Any ideas?
I have further noticed the following: In rare cases, the modem will not be enumerated during soft system reboot. Any hints what this could cause would be appreciated. However, I consider it a different matter.
Sincerely
Hello,
As for the firmware update you should be using the modem port for this - maybe that's the reason. Please also check if gWinSwup has created any log file in it's folder - maybe there'll be some more information.
As for the error codes - EMM attach failed and no suitable cells in tracking area could probably mean some problems with network quality - did you manage to get SMONI after the successfull registration? Have you possibly tried T Mobile or O2 SIMs? Please also send AT+COPS=? to scan the available networks. You may try the manual registration if your network is available. And how about RAT - maybe this problem depends on the radio access technology - have you tried to select RAT? Please see AT+COPS command for more.
Regards,
Bartłomiej