COPS=2 routine sending ERROR / COPS=0,2 very long | Thales IoT Developer Community
September 28, 2018 - 11:31am, 2095 views
During our product installation, to force automatic network selection, and as roaming helper, I force network deregistration after modem start ("+PBREADY received and AT+CPIN validated). Then, I force automatic operator selection.
I use EHS6, mainly ARN0.51.
For a few percent of the production, AT+COPS=2 replies several ***** "ERROR" (my firmware tries 4 *****). What can be the causes of such answer ?
After these 4 tries, my firmware gives up, and send AT+COPS=0,2 to automatically select a network.
This last command could be really long (near 2 minutes) or 10s, in "lab" conditions. Does someone know the maximum execution time ?