CME Error:Operation not allowed | Telit Cinterion IoT Developer Community
September 14, 2015 - 2:24pm, 19260 views
Hello,
I am using http POST to upload data to a server. The modem used is BGS2-W.
My device is uploading data periodically to the server. Sometimes while setting the content length parameter, I get CME error:3 (Operation not allowed). I retry the upload after 2 minutes. But I keep on getting the same response. The only way to get out of this situation is to reboot the modem using AT+CFUN=1,1. On rebooting, the upload starts normally again.
I checked for the internet connection and service profile, but they seem to be as per what I have set. The AT+CEER command returns no error (all 0s).
The response to AT1 command:
Cinterion
BGS2-W
REVISION 02.000
The AT command log:
20150912T180002 INFO Modem:AT^SCKS?
20150912T180002 INFO Modem:^SCKS: 0,1
20150912T180002 INFO Modem:AT+CREG?
20150912T180002 INFO Modem:+CREG: 0,1
20150912T180002 INFO Modem:AT^SISS=0,hcContLen,6229
20150912T180002 INFO Modem:+CME ERROR: 3
What could be the reason for continuous CME errors? What happens on setting the content length. Does the modem allocate some memory and is it not able to allocate memory and hence is failing? Is it possible to query the memory status?
Thanks and Regards,
Kalyani Kulkarni
Hello,
Please provide ATI1 response to verify the details about the firmware version you are using.
Is there any rule when the problem happens: after some time of application running or it doesn't matter.
Do you connect to the same address or change it each time.
Regards,
Bartłomiej
Hello,
The ATI1 response is:
Cinterion
BGS2-W
REVISION 02.000
I use the same address each time. This scenario has happened only once. I was not able to reproduce this.
Thanks and Regards,
Kalyani Kulkarni
Hello,
This problem seems a little bit similar to your other problem with "Socket not connected".
But if it has happened only once it could be hard to diagnose the reason.
The ATI1 command should also display "A-REVISION" which would give us the full information about the firmware version on the module.
Regards,
Bartłomiej
Hello,
The response to ATI1 command is:
Hello,
This error occurred before on setting the content length. How about this time - there was always 8kB - did you always set the same amount or there was different scenario?
I'd say that maybe it would be better not to open and close the socket for each 8Kb but this should also be possible.
There is no rule for CME ERROR, it can happen in some error situation. It would happen if you would try to configure the connection which is currently open. The same is for socket error - there may be many reasons connected with socket and network communication.
You have the latest official software version for revision 2.
However you could try to upgrade to revision 3. I can send you the firmware and the document.
You could also try to test with another network operator.
Regards,
Bartłomiej
Hello,
Thanks for your reply. The second time the CME error occurred while setting the content length. The content length is *** 8Kb, but it is variable in each iteration. Basically I have a file system and I read upto 8Kb from files and upload. I do not keep the connection open as the data that would have to be reuploaded if there is any error would be limited.
I have a question:
Before opening the connection using SISO command, I do not check for SICI and SISI command. Is it necessary to check whether the connection state is Down and service state is Allocated before using SISO command? Would this be a reason for the modem to sometimes go into this indeterminate state where it does not recover? Moreover the GPRS connection has a inactivity timeout which is 20sec default. So if I upload second packet within 20sec, the connection is still up. Would this be a problem?
Another observation:
On getting any error, I have printed out the outcome of AT^SICI and AT^SISI. In the socket not connected case, the connection state (response from AT^SICI) indicates that it is Down (0), but still the Local IP address is not 0.0.0.0. Does thtat indicate any problem?
Thanks and Regards,
Kalyani Kulkarni
Hello,
For testing you can check SICI and SISI replies before each connection just to make sure that the connection and service are in the proper condition.
You could also try to delete all the configuration and set everything again when the problem happens - just for test again.
If only the modem restart helps in recovering from that state there may be some problem inside which is not connected with improper connection configuration or handling. That's why I suggested testing with revision 3.
I don't think that SICI reply means anything bad here.
Regards,
Bartłomiej