ELS61 Manual network selection - very very slow | Thales IoT Developer Community
August 30, 2018 - 4:58pm, 2436 views
Hello
I've got a algorithm for my platform which scans the available bands and picks out a network based on it's signal strength. I have a roaming SIM that will use all major UK networks.
When my platform has made its choice it tells the modem to camp on the selected network (AT+COPS=4,2,"23420"), but the modem takes a very long time to respond with CME ERROR 3. (operation not allowed). I've tried other networks and get the same response, sometimes CME ERROR 256, too.
Repeat attempts also fail - as seen in the log.
I've attached a log of the modem start up sequence. The log shows that it takes over 7 minutes for the modem to respond successfully, and on the logged occasion it has selected a different network (which is acceptable, since the command allows it).
My question is, why is the AT+COPS=4...... command not available? And why for such a long period of time?
Is there something I can do to improve the performance?
ATI returns:
Cinterion
ELS61-E
REVISION 01.000
OK
[Thu Aug 30 15:26:37.313 2018] ^SYSLOADING [Thu Aug 30 15:26:39.621 2018] ^SYSSTART [Thu Aug 30 15:26:39.841 2018] AT^SPOW=2,5000,3 [Thu Aug 30 15:26:40.289 2018] OK [Thu Aug 30 15:26:41.639 2018] ATE0 [Thu Aug 30 15:26:41.674 2018] OK [Thu Aug 30 15:27:02.464 2018] +PBREADY [Thu Aug 30 15:27:02.650 2018] AT+CGMM [Thu Aug 30 15:27:02.672 2018] ELS61-E [Thu Aug 30 15:27:02.672 2018] OK [Thu Aug 30 15:27:03.111 2018] AT+CCID? [Thu Aug 30 15:27:03.149 2018] +CCID: 8944501410147193243 [Thu Aug 30 15:27:03.149 2018] OK [Thu Aug 30 15:27:03.589 2018] AT+GSN [Thu Aug 30 15:27:03.611 2018] 353251080864723 [Thu Aug 30 15:27:03.627 2018] OK [Thu Aug 30 15:27:04.050 2018] AT^SPOW=2,5000,3 [Thu Aug 30 15:27:04.088 2018] OK [Thu Aug 30 15:27:05.435 2018] AT^SCFG="Radio/Band/2G","0x14" [Thu Aug 30 15:27:07.845 2018] ^SCFG: "Radio/Band/2G","0x00000014" [Thu Aug 30 15:27:07.861 2018] OK [Thu Aug 30 15:27:08.284 2018] AT^SCFG="Radio/Band/4G","0x8080085" [Thu Aug 30 15:27:08.338 2018] ^SCFG: "Radio/Band/4G","0x08080085" [Thu Aug 30 15:27:08.338 2018] OK [Thu Aug 30 15:27:08.762 2018] AT+COPS=2 [Thu Aug 30 15:27:09.914 2018] OK [Thu Aug 30 15:27:10.242 2018] AT^SGCONF=0,0,8,8,1 [Thu Aug 30 15:27:10.281 2018] OK [Thu Aug 30 15:27:10.608 2018] AT^SXRAT=3 [Thu Aug 30 15:27:10.663 2018] OK [Thu Aug 30 15:27:10.990 2018] AT^SCFG="Radio/Band/4G","0x4" [Thu Aug 30 15:27:11.028 2018] ^SCFG: "Radio/Band/4G","0x00000004" [Thu Aug 30 15:27:11.044 2018] OK [Thu Aug 30 15:27:11.468 2018] AT+COPS=2 [Thu Aug 30 15:27:11.506 2018] OK [Thu Aug 30 15:27:11.850 2018] AT^SNMON="INS",2 [Thu Aug 30 15:27:11.873 2018] ^SNMON: "INS",0,"0x00000004",0 [Thu Aug 30 15:27:11.873 2018] ^SNMON: "INS",0,"0x00000010",0 [Thu Aug 30 15:27:11.905 2018] ^SNMON: "INS",0,"0x00000001",7 [Thu Aug 30 15:27:16.599 2018] ^SNMON: "INS",0,"0x00000004",7,"06A9C01","2C8A","23430",1667,388,20,20,-111,-13 [Thu Aug 30 15:27:16.632 2018] ^SNMON: "INS",0,"0x00000004",7,"00C1001","0867","23420",1392,43,15,15,-106,-11 [Thu Aug 30 15:27:16.648 2018] ^SNMON: "INS",0,"0x00000004",7,"00C1000","0867","23420",1392,87,15,--,-110,-14 [Thu Aug 30 15:27:16.664 2018] ^SNMON: "INS",0,"0x00000080",7 [Thu Aug 30 15:27:16.679 2018] ^SNMON: "INS",0,"0x00080000",7 [Thu Aug 30 15:27:16.679 2018] ^SNMON: "INS",0,"0x08000000",7 [Thu Aug 30 15:27:16.695 2018] OK [Thu Aug 30 15:27:16.990 2018] AT^SNMON="INS",2 [Thu Aug 30 15:27:17.014 2018] ^SNMON: "INS",0,"0x00000004",0 [Thu Aug 30 15:27:17.030 2018] ^SNMON: "INS",0,"0x00000001",7 [Thu Aug 30 15:27:17.030 2018] ^SNMON: "INS",0,"0x00000010",0 [Thu Aug 30 15:27:20.754 2018] ^SNMON: "INS",0,"0x00000004",7,"00C1001","0867","23420",1392,43,15,15,-107,-12 [Thu Aug 30 15:27:20.786 2018] ^SNMON: "INS",0,"0x00000004",7,"06A9C01","2C8A","23430",1667,388,20,20,-113,-13 [Thu Aug 30 15:27:20.802 2018] ^SNMON: "INS",0,"0x00000004",7,"06A9C00","2C8A","23430",1667,387,20,--,-114,-15 [Thu Aug 30 15:27:20.818 2018] ^SNMON: "INS",0,"0x00000080",7 [Thu Aug 30 15:27:20.834 2018] ^SNMON: "INS",0,"0x00080000",7 [Thu Aug 30 15:27:20.834 2018] ^SNMON: "INS",0,"0x08000000",7 [Thu Aug 30 15:27:20.850 2018] OK [Thu Aug 30 15:27:21.145 2018] AT+COPS=? [Thu Aug 30 15:27:23.016 2018] +COPS: (1,"3 UK","3 UK","23420",7),(3,"","","23432",7),(1,"EE","EE","23430",7) [Thu Aug 30 15:27:23.047 2018] OK [Thu Aug 30 15:27:23.453 2018] AT^SXRAT=5,3 [Thu Aug 30 15:27:23.493 2018] OK [Thu Aug 30 15:27:23.835 2018] AT^SCFG="Radio/Band/4G","0x8080085" [Thu Aug 30 15:27:23.875 2018] ^SCFG: "Radio/Band/4G","0x08080085" [Thu Aug 30 15:27:23.891 2018] OK [Thu Aug 30 15:27:24.313 2018] AT^SCFG="Radio/Band/2G","0x14" [Thu Aug 30 15:27:24.369 2018] ^SCFG: "Radio/Band/2G","0x00000014" [Thu Aug 30 15:27:24.385 2018] OK [Thu Aug 30 15:27:24.806 2018] AT+COPS=4,2,"23420" [Thu Aug 30 15:28:35.414 2018] +CME ERROR: 3 [Thu Aug 30 15:28:44.741 2018] AT+COPS=4,2,"23420" [Thu Aug 30 15:29:56.727 2018] +CME ERROR: 3 [Thu Aug 30 15:30:02.750 2018] AT+COPS=4,2,"23420" [Thu Aug 30 15:31:35.789 2018] +CME ERROR: 3 [Thu Aug 30 15:31:44.746 2018] AT+COPS=4,2,"23420" [Thu Aug 30 15:32:52.786 2018] +CME ERROR: 3 [Thu Aug 30 15:33:02.739 2018] AT+COPS=4,2,"23420" [Thu Aug 30 15:34:17.140 2018] +CME ERROR: 3 [Thu Aug 30 15:34:26.732 2018] AT+COPS=4,2,"23420" [Thu Aug 30 15:35:39.901 2018] OK [Thu Aug 30 15:35:40.222 2018] AT+CREG? [Thu Aug 30 15:35:40.236 2018] +CREG: 0,5 [Thu Aug 30 15:35:40.236 2018] OK [Thu Aug 30 15:35:40.684 2018] AT+COPS? [Thu Aug 30 15:35:40.698 2018] +COPS: 0,2,"23410",0 [Thu Aug 30 15:35:40.714 2018] OK [Thu Aug 30 15:35:41.161 2018] AT+CREG? [Thu Aug 30 15:35:41.175 2018] +CREG: 0,5 [Thu Aug 30 15:35:41.175 2018] OK
I've attached the log file.
(Edited: I had included a file that had more info than was needed - sorry)
Thanks in advance for any assistance.
Steve
Hello,
Could you check the detailed firmware version with ATI1 command?
I have tried the similar scenario but wasn't able to reproduce such problem.
I can see that you narrow down the bands before the network scan, then extend the bands, allow also 2G and try to register to the network that according to COPS reply is available. But in the effect the module is registered to some other network when it finally manages to register. Is it the same effect if you try AT+COPS=1,... ?
Is this scenario reproducible, does it happen always? Have you also tried it manually? And what happens when you let the module register automatically - are there any problems, can it register to the network that you try to select explicitly?
Regards,
Bartłomiej
Hi Bartlomiej
Thanks for your response.
Yes, it happens like this every time - with slight variations.
The constants are that it takes a very long time to responds to the AT+COPS=4,2...... command. Sometimes it succeeds, often it fails with an "ERROR" or a CME ERROR 3 or 256, and often when it succeeds it fails to connect to the chosen network (I presume that this is just an issue with the network being too weak or over-capacity).
AT+COPS=1,... responds quite quickly, but the result is very similar: CME ERROR 3, 112 or 256.
AT+COPS=0 typically fails too, with a CME 100
ATI1 returns:
Cinterion
ELS61-E
REVISION 01.000
A-REVISION 00.014.00
I've been running the AT+COPS tests without the initial cell scan and band switching, the failure is the same.
Thanks again.
Steve
Hi,
I see you are using SPOW. Could you do retest with AT^SPOW=1,0,0?
Next set all required radio bands: "Radio/Band/2G","0x00000014" and "Radio/Band/4G","0x00080085".
After that set AT^SXRAT=3,3.
Next first try to use AT+COPS=2 -> AT+COPS=0
If it will works next you can try to use AT+COPS=2 -> AT+COPS=1,2.... And at the end if everythink will be correct try AT+COPS=4,2
AT^SPOW could somehow add that big delay. AT+COPS=4 works in that way it try to connect manually to your specified network base or if it won't works it will set for automatic. Like first try COPS=1 or if it won't work module will try COPS=0.
Can you give logs with your test. The last sentense is quite interesting. So after writing PIN (if it's required) you only try to use AT+COPS=0 and there is failure?
Could you do test with setting SXRAT=3 for onlu LTE and next set 0 for GSM. And see what happend?
Regards
Krzysztof
Hi Krzysztof & Bartlomiej
We've found the cause of the problem. We have a batch of suspect 4G SIMs combined with a batch of faulty antenna cables.
Thanks for your assistance.
Regards
Steve