COPS=2 routine sending ERROR / COPS=0,2 very long | Telit Cinterion IoT Developer Community
September 28, 2018 - 11:31am, 3507 views
Hello,
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 ?
Best regards,
Pascal
Hello,
Automatic network registration is a default mode after SIM PIN authentication has completed and "+PBREADY" is thrown. May I ask how sending AT+COPS=2 and AT+COPS=0 is expected to help in your scenario? So you send 'AT+COPS=2' just after "+PBREADY'? And the ERROR reply is always thrown in case of some devices?
The network registration time depends on the network conditions, location, antenna etc. Do you test this in the same place always? Are the long registration ***** observed in some special conditions/locations or maybe it is random?
As for the firmware there is an update available.
Regards,
Bartłomiej
Hi,
Please send AT+CMEE=2 and AT&W in the initialization to get the relevant error message in clear text form.
Do you have min. 100ms delay between each AT+COPS=2 tries?
If you are using ASC0 or 1, for lower speeds than 9600 baud the delay is higher (300ms for 1200 baud).
Have you tested the signal strength with AT^SMONI?
Best regards,
Antero
Antero Markkula
Communication and Mechatronics
Enkom Active Oy – www.enkom-active.fi
Upseerinkatu 3 A, 02600 Espoo, Finland
Mobile: +358 400 411368
Office: +358 10 204 0000
Fax: +358 10 204 0010
E-mail: antero.markkula@enkom-active.fi
Hello,
Yes indeed, the devices are in automatic mode at startup, and with our previous firmware.
Unfortunately, few batches (up to 300 units) were sent in Italy and Belgium (we are in France) for installation and commercial test. We lost 30% of the products, the 70% found the roaming operator without difficulties.
Back in France, the 30% faulty products began to transmit again... made the
During on field testing in Belgium with these products, the only solution found to force the operator search was the one described in the first message. "Field testing" includes debug at the hotel and customer office, and on field testing.
Still few products with this problematic behavior (few dozen on a 10k units produced this year). This occurs mostly all the time for few devices.
I perform the test at my office, the "GSM conditions" are quite good.
Sequence is as follow :
I use ASC0, at 115200bds. Steps 2 and 3 were added after the field test in Belgium.
Note : If failed, step 4 is really long.
This week I may verify signal strenght (usually 14-16 at my office ) / change the antenna on these specific products.
Best regards,
Pascal
Hello,
While testing the failing devices, please make sure that they are tested in the same place with the same SIM cards, settings, antennas etc. Please compare the configurations (AT^SCFG?, AT&V), reset to factory settings on start, compare the firmware versions (ATI1 replies), stickers for any differences, add some diagnostic commands like AT+COPS?, AT+CREG?, AT^SMONI, AT+CSQ. You can also check the available networks with AT+COPS=? Do the devices never register without your special procedure with network deregistration or is the long time the only problem here? Do the modules finally register to 3G or 2G?
Regards,
Bartłomiej