4 thoughts on “+CME ERROR: phone failure (AUTOBND)”
We are using a UC864-G and sometimes at startup we are receiving the follow error after sending AT#AUTOBND=2
"+CME ERROR: phone failure"
What does this error code mean? Here’s a log of our startup.
ATE0
ATE0 OK
AT#SELINT=2
OK
AT+CMEE=2
OK
AT&K=0
OK
AT+COPS=0
OK
AT#AUTOBND=2
+CME ERROR: phone failure
Thanks!
Maybe issuing autobnd right at startup interferes with the registration, if you need this at startup isn’t better to have it automatic with AUTOBND=1?
So we need to set AUTOBND after network registration?
Brice
You don’t have to set AUTOBND at each restart!
The values set by following commands are automatically stored in NVM, without issuing any storing command and independently from the profile (unique values), and are automatically restored at startup:
We use cookies to enhance your browsing experience and help us improve our websites. To improve our website, we carefully select third parties that use cookies to allow us to serve specific content and achieve the purposes set out in our cookie policy. For more information on how to make adjustments through your browser to the cookies being used on your device, please click Find Out More link. By closing this banner or continuing to browse our website, you agree to our use of such cookies. FIND OUT MORE
We are using a UC864-G and sometimes at startup we are receiving the follow error after sending AT#AUTOBND=2
"+CME ERROR: phone failure"
What does this error code mean? Here’s a log of our startup.
Thanks!
Maybe issuing autobnd right at startup interferes with the registration, if you need this at startup isn’t better to have it automatic with AUTOBND=1?
So we need to set AUTOBND after network registration?
Brice
You don’t have to set AUTOBND at each restart!