March 19, 2020 - 11:27am, 5189 views
Hi, where can I download the Windows Executable to upgrade my MC55i-W modules to version v01301c ?I am starting from version v01301.
And how about the network registration - does it also take so long? If the devices are in roaming maybe the SIM owner has changed the roaming partners, for instance terminated the contract with one of them.
No. Network registration(CREG) takes about 10-14sec(from MC55 is powered on). And GPRS registration normally takes about the same time. Its only the first time after "whatever happened" it can take up to 14 minutes. Once it got past that "first" GPRS registration its back to 10-14sec registration time again.
In our design The MC55 is normally powered off. And only powered on once a day to send in data, then it's power off again. This takes about 30-60sec. No settings are saved in the MC55. Run the same AT commands every time.
Don't think the roaming has much to do with it since the SIM brand and network is more or less the same company(in this country).
Could you specify what you mean by "Once it got past that "first" GPRS registration its back to 10-14sec registration time again."? So what is the first registration - new SIM card or something else? And when it finally registers it is always 10-14 seconds in next days? Or the problem comes back again in some time?
So the short version is something like this.
1. Unit is working(GPRS reg 10-14 sec). for x years.
2. Unit fails to connect. no GPRS registration(timeout). Made >25 retries/restarts to connect.
3. I disable the timeout on the Unit that stopped working and wait until it gets GPRS registered. takes 14 minutes.
4. Unit is working again (GPRS reg 10-14 sec).
This has been repeated/tested on about 10 units. and the GPRS registratiion time has been almost exactly 14 minutes every time.
With "first" registration i mean step 3.
So far the problem has not come back....
As a precaution, i made a software with a 20 minutes timeout for next time.
But it does not help much if the units do not connect so i can update the software.
That doesn't sound promising. It seems that more digging on the operator side might be needed. BTW have you done any debug on site? Do you have any logs from such device? Are the devices moving?
All debug is done on site. Because if we move the device to the office for example. The problem is gone.
We have also tried switching SIMs . SIM from a "working" device is put in the non working device. Device works again. Switching back to original SIM. Device works.
So if we change SIM, move Device(new Cell ID!?) or disable timeout(wait for 14 minutes).
The device is back to normal. For me this feels like a operator problem.
Yes i have log with communication and time stamps.
Any suggestions on at-commands/tests that we can do to get more information from the MC55.
So we can figure why/what is happening?
So this happens only in some locations of the same local operator.
You could register some URCs to monitor the network (if serving network or cell ID changes, GPRS events reporting etc.) AT+CREG=2, AT+CGREG=1, AT+CGEREP=2, AT^SMONG=1,20 (possible period: 1-100) and periodically send AT^MONI, AT+CSQ, AT^SMONC.
It was the operator making updates in the net that caused the problem.
i have an older version of the firmware. Can anyone point me to the 01.301 version?
In general the firmware is not available for download unless you have access to our extranet resources. You can contact your distributor or local Thales M2M sales. What FW version do you have?
© 2013-2022 THALES DIS AIS Deutschland GmbH