PLS62 Regular PDP context deactivation | Thales IoT Developer Community
September 27, 2019 - 9:35am, 2870 views
Hi all,
I have a question about the PLS62 module, when trying to activate WWAN internet connection using AT^SWWAN=1,1,1 the modem responses with ERROR.
When fetching the AT+CEER I get:
+CEER: "SM deactivation",136,"Regular PDP context deactivation"
I do not understand this error and it's not eplained in the manual what this could mean.
Does anyone here know whats the problem with my PDP context?
Thanks,
Rudger.
Hello,
Please issue AT+CEER=0 before the test to clear the old errors. Please also send AT+CMEE=2 before to see ERROR replies descriptions if available.
Please check AT+CGDCONT reply to verify if CID1 is configured, check if the module is registered to the network, AT+CGPADDR and AT+CGACT? replies. Is any other data connection used? Does it happen all the time?
Regards,
Bartłomiej
No it doesn't happen all of the time, and normally we reset the modem and try again and it works.
But we want to know why? Can you explain what the error means? Cause I'm unable to find this anywhere.
In the case it fails we do the following:
Hello,
So the scenario is that the module is powered on and the connection attempt is made. In case of fail there is a reboot and it usually succeeds? Can you state how frequently the problem occurs? Is the device always in the same place or is it moving?
The CEER category is 'SM deactivation' and does not contain any error - so it might be related '+CGEV: NW DETACH' (detach by network) you get before trying SWWAN or maybe it's related to later SWWAN attempt. Anyway it doesn't seem to contain any valubale information for this problem. It is hard to say why there is this failure without analyzing network logs. If this problem happens frequently and you have the feeling that it might be caused by the module malfunction I suggest to report it to Gemalto support - getting traces from the module would be required to see the communication between the modle and network.
Regards,
Bartłomiej
Hi,
Your timing is a little off here; you are trying to start the WWAN interface when the module is inthe middle of doing some kind of network cell reselection or RaT change-over: