CME ERROR: 60 description

HL7800-M - what is “+CME ERROR: 60” description? I can’t find in my “AT Commands Interface Guide”, 8.1.

Error was added in version 9.0
60: Internal system failure

This error is still not documented in version 13 of the RC76XX AT commands document 41113566.
(I would add that the description doesn’t give much of a clue as to what is going wrong)

Hi @chris6,

Welcome to our community!

  • What command did you send on RC76 resulting in error +CME ERROR: 60?
  • Please specify which version of RC76 you are using and what firmware it is running.
  • Please provide AT command log containing information about RC76, along with the steps you took that led to the error.
ATI9
AT!IMPREF?
...
AT commands you have executed
...

Thanks,

Log 1.txt (5.8 MB)
The primary point of my post was to point out that this error is not documented in the list of CME errors in the AT, but since you have asked, I’ve uploaded a (large) log which includes the incident.

Our appliance sends a UDP packet containing telemetry data at regular intervals, and resets everything if a failure occurs

The module was reset at line 27693, and came up on 2G (see below)
There was a successful KUDPSEND at line 27969
It switched to 4G at line 28409, then did several successful SENDs
Back o 2G on 34090
It then chugs along happily doing a KUDPSEND, the last successful one being at 186200
The next UDPSEND is at line 187398
The CME ERROR is at line 187402, and was in response to a AT+KUDPSEND command.

At the time, I was stress testing our product with low battery (about 3.5V) and low signal (running in a biscuit tin with a 50 ohm terminator instead of an antenna). This is probably why it was running on 2G (lower frequency, better penetration of biscuit tin lid gaps)

At the time the module was running Rev 9, but I have since updated to Rev 10, so I can no longer get a valid AT!IMPREF? result from that board.

Hi @chris6,

Based on the logs you provided, I’m not sure which specific model of RC76 you are using.
I have checked with my internal team, and we found one issue related to +CME ERROR: 60 that has been raised and fixed in Release 11.
You can wait until Release 11 is published on the source page and recheck.
Or, if you want a faster resolution, you can send an email to technical support at support@sierrawireless.com for further assistance.

Thanks,

Hi jerdung,
Thank you for your response and for the information that an issue has
been found.
We use the 7620-1 version of the RC76.
I will test Release 11 when it is avaiable.

In the mean time, I’ve modified our firmware as suggested by another
forum member to basically tear down the UDP and the CNX and bring it up
again at the first sign of trouble.

I then did a rather brutal test with one of our boards with the antenna
replaced with a 50R terminator, and the whole thing in a biscuit tin!

Having made the firmware modificaitions as suggested, the recovery
software behaved as inended with our device storing up messages while
the link is not avialable, and sending them reasonably soon after I took
the lid off the enclosure :wink:

So I’m happy that I have a work around, but remain unhappy that the
Sierra product has un-documented CME errors.

Chris