PLS8-E unable to update apn table | Telit Cinterion IoT Developer Community
September 9, 2022 - 2:13pm, 829 views
Hello,
I'm using two kind of PLS8-E, rel. 3 with 3.017 firmware and rel.4 with 4.004 formware.
On both types I observe problem with at+cgdcont command.
Test sequence is:
at+cmee=2
at+cmee=2
ok
at+cgdcont=1,"IP","***" (*** is my client apn name)
at+cgdcont=1,"IP","***"
error
at+cmee=2
at+cmee=2
ok
at+cgdcont?
at+cgdcont?
+cme error: unknown
ok
Probably I have reached the limit of write ***** to the same apn table. Devices constantly switch between operators and work in 24/7 mode.
Is there any method to investigate internal modem issue deeper than using +cmee=2?
Hello,
It is strange that even reading attempt gets the error result. Is the module registered when this happens? Have you tried to deregister or enter airplane mode and then check? Does it help or you have to reboot? Please try to check the module state when this happens like network registration or any other activity.
Anyway you might need tracing tools from Qualcomm .
Regards,
Bartłomiej
Module is registered in home network.
Packet domain is not available, module can't attach (before crash worked fine).
SMS are not possible, only pure voice call works.
Module was restarted many *****, sequence +cfun=0 and +cfun=1 doesn't help.
I played with ^scfg="Radio/Band" without effects, now is 2928787,1 all bands.
Moreover, I have more than twenty units crashed in the same way and about the same date after more than year of proper work. One additional, one big difference between regular use and my application: SIM card is served form external device, a lot of cards can be used to compare behavior in selected network. I tried to use PS domain with many different SIM cards, ffor all situation is the same.
Can the module damage the structure of internal files while reading an atypical SIM card?
So this problem started in a certain moment in time and before that it was all fine? Are all the devices in the same region or same operator's network? Maybe it is somehow also related to the operator.
If I understand right rebooting (even cutting off the power and starting again?) does not help. The most strange thing here is that you can't read CGDCONT configuration. You should be able to do it in any mode and even without a SIM card. So, that could suggest some memory problem, especially if it does not disappear after the reboot. Was your application frequently changing this setting? How frequently? This value is stored to the non-volatile memory. Is it possible that the power is frequently cut during such operations?
Please check also AT^SCFG?, AT+CFUN?, ATI1 for reference.
But if you still can't read AT+CGDCONT? I'd report it to your distributor or Thales support system.
Regards,
Bartłomiej
Hello,
I'm in possession od several units sent back by my customer.
In my application SIM1 is an external (remote served), SIM2 is a local holder.
In normal situation SIM1 (external is used), I checked conf as follow:
^SCFG: "SIM/CS","SIM_1"
after that I switched to local SIM:
at^SCFG="SIM/CS","SIM_2"
^SCFG: "SIM/CS","SIM_2"
OK
and observe modem crash:
^EXIT modem crash: fs_efs2.c:1644:Assertion vp->p.inode.nlink > 0 failed
Power down/ power up restarted the modem.
I was able to set proper apn and run PS:
OK
at^swwan=1,1
OK
at^smoni
^SMONI: 2G,5,-90,260,01,2AFC,13DA,--,--,0,2,E,5,3,6,-93,0,--
OK
at^swwan=0,1
OK
Attemp to switch back to SIM1 ends as follow:
at^SCFG="SIM/CS","SIM_1"
^SCFG: "SIM/CS","SIM_1"
OK
^EXIT modem crash: fs_efs2.c:1644:Assertion vp->p.inode.nlink > 0 failed
Hello,
In such a case you need to report it to the Thales support system or your distributor - to analyze it further there will be a need to extract more crash related data from the module. Maybe there is some memory **********.
Regards,
Bartłomiej