Vector errors, status codes and no sound
Vector may occasionally experience internal errors that he displays on his screen. These error codes are uncommon and usually nothing to worry about. They simply mean Vector has encountered an internal issue and needs to reboot.
Note: If Vector experiences these errors multiple times per day or always shows an error after rebooting, then please contact us at: support@anki.bot.
You may see any of the following. This list is not inclusive:
- 898
- 899
- 981
- 915
- 917
- 980
For a full list of error codes, please see the following article: Vector Status Codes
Vector will attempt to restart by himself. Please wait approx. 30 seconds for him to initiate the restart. If he does not restart by himself, then please follow these steps:
- Press Vector's back button for 5 seconds to turn Vector off.
- If his screen and back lights turn off, wait ten seconds, then tap his back button again to boot him back up. If this does not work, move to Step 2.
- Take Vector off of the charger and set him next to it. Allow Vector's battery to run down.
- Note: This may take up to two hours, but will not damage Vector's battery. Vector shuts down before he reaches a completely dead battery to help protect against damage.
- Place Vector back on the charger and give him about 45 seconds to boot back up to his normal self!
- If you see this error again shortly after Vector boots, please follow the steps in the article Performing a Firmware Recovery Reset
Vector error and status codes
Vector will occasionally display an error code (also known as a Status Code) on his screen.
This article was made possible by a combination of internal documentation but also by the work of Randall Maas and his Vector Technical Reference Manual. ANKI wishes to thank Randall for his dedication to the Vector Technical Reference Manual, which is a fantastic resource.
- 800 - 999
- If any of these Status Codes consistently appear, there could possibly be a hardware issue with Vector. Startup into Recovery Mode, Clear User Data, and use the Vector app to Reinstall Vector’s OS.
- 700 - 705
- These are issues triggered by the reading of an internal sensor. A good example would be Vector operating in a room that was too hot.
- 200 - 219
- If any of these Status Codes appear, they involve Software Updates or the Recovery process. Typically, retrying the Update will fix the issue unless there is a fundamentally more complex issue involved.
- 1 - 10
- These codes belong to a core Vector service that runs all of Vector’s other services. Most of these codes will never appear on Vector’s display.
Error Code Table
| Error Code | Code Description | Explanation |
| 1 | Switchboard: unknown status | Should never happen. |
| 2 | Switchboard: OTA in progress | An Over-The-Air update is currently in progress. |
| 3 | Switchboard: OTA completed | An Over-The-Air Update has completed successfully. |
| 4 | Switchboard: rebooting | The robot is rebooting. |
| 5 | Switchboard: Other OTA error | An unknown error occurred with an Over-The-Update. |
| 10 | OS: Unknown system error |
|
| 200 | Unexpected .tar contents |
|
| 201 | Unhandled manifest version or feature |
|
| 202 | Boot Control HAL failure |
|
| 203 | Could not open URL |
The URL for the link was invalid (check the link and make sure you can download the OTA on your local machine from the same link) |
| 204 | URL not a TAR file | The URL used to initiate an update pointed to an incorrect filetype. Check the link. |
| 205 | Decompressor error | The .tar/.ota file could not be unpacked- could happen if the .ota file is corrupted. Reboot the robot and try again. |
| 206 | Block error |
|
| 207 | Imgdiff error | Delta payload error |
| 208 | I/O error |
|
| 209 | Signature validation error |
|
| 210 | Decryption error | Encryption scheme is not supported. |
| 211 | Wrong base version | Vector's current version doesn't match what is expected for this delta update |
| 212 | Subprocess exception | The decompression engine had an unexpected, undefined error. |
| 213 | Wrong serial number | The processor serial number (QSN) is not correct for the robot that the image is being applied to. |
| 214 | Dev / Prod mismatch | Development Vectors can’t install production OTA software, and production Vectors can’t install development OTA software (make sure that you are applying the correct image to Vector).
|
| 215 | Socket Timeout (network stall) | OTA transfer failed, due to timeout. (There may be poor network connectivity)
|
| 216 | Downgrade not allowed |
|
| 217 |
|
|
| 218 |
|
|
| 219 | Other Exception | Other unexpected, undefined error while transferring OTA file.
|
|
|
||
| // | Hardware Issues |
|
| 990 | DISPLAY_FAILURE | The screen could not be detected / initialized (The LCD display is not communicating properly with the processor.) |
| 981 | CAMERA_STOPPED |
|
| 980 | CAMERA_FAILURE |
|
| 970 | WIFI_HW_FAILURE | The Wi-Fi radio antenna could not be detected / initialized. |
| 960 | IMU_FAILUR | The IMU ( Inertial Measurement Unit) could not be detected / initialized. |
|
|
||
| // | Vector OS Process Issues |
|
| 923 | NO_CLOUD_PROCESS | Vic-cloud failed to start or stopped unexpectedly. |
| 921 | NO_GATEWAY | Vic-gateway was unable to start or crashed
|
| 920 | VIC_GATEWAY_CERT | Vic-gateway-cert was unable to generate a x509 certificate for vic-gateway |
| 919 | SYSTEMD | Systemd is not working properly
|
| 917 | NO_ROBOT_COMMS |
|
| 916 | NO_ROBOT_PROCESS |
|
| 915 | NO_ENGINE_COMMS | Vic-engine stopped responding
|
| 914 | NO_ENGINE_PROCESS | Vic-engine stopped unexpectedly. |
| 913 | NO_SWITCHBOARD | Vic-switchboard stopped unexpectedly. |
| 911 | AUDIO_FAILURE | The audio engine stopped unexpectedly or failed to start on boot. |
| 909 | STOP_BOOT_ANIM_FAILED | The boot animation process failed or was unable to start. |
| // | Hardware Issues | |
| 899 | NO_BODY |
|
| 898 | SPINE_SELECT_TIMEOUT |
|
| // | External Sensor Issues | |
| 895 | TOUCH_SENSOR | The back touch sensor failed during power-on self test or during runtime. |
| 894 | TOF | TOF (Time-Of-Flight) sensor failed to initialize or stopped working. |
| 893 | CLIFF_BL | The back left cliff sensor failed to initialize or stopped working. |
| 892 | CLIFF_BR | The back right cliff sensor failed to initialize or stopped working. |
| 891 | CLIFF_FL | The front left cliff sensor failed to initialize or stopped working. |
| 890 | CLIFF_FR | The front right cliff sensor failed to initialize or stopped working. |
| // | Microphone Issues | |
| 873 | MIC_BL | Back left microphone failed to initialize / send data. |
| 872 | MIC_BR | Back right microphone failed to initialize / send data. |
| 871 | MIC_FL | Front left microphone failed to initialize / send data. |
| 870 | MIC_FR | Front right microphone failed to initialize / send data. |
| // | Cloud Errors | |
| 852 | CLOUD_READ_ESN | There is a problem reading the cloud electronic serial number. |
| 851 | CLOUD_TOKEN_STORE | There is a problem with the cloud token store. |
| 850 | CLOUD_CERT | There is a problem with the cloud certificate. |
| // | Manufacturing Issues | |
| 840 | NO_CAMERA_CALIB | The camera is not calibrated. |
| // | Vector OS Process Issues | |
| 801 | DFU_FAILED | The process to update the cube firmware failed. |
| 800 | NO_ANIM_PROCESS | Vic-anim was unable to start or crashed. |
| // | Internal Sensor Derived Issues | |
| 705 | SHUTDOWN_BATTERY_CRITICAL_TEMP | The robot shut down because the battery was too hot to operate safely. |
| 702 | SHUTDOWN_BATTERY_CRITICAL_VOLT | The robot was shut down because the battery voltage was too low. |
| 701 | SHUTDOWN_GYRO_NOT_CALIBRATING | The gyroscope sensor values were out of normal range or the gyroscope failed (it wasn’t able to calibrate), so the robot shut down. |
| 700 | SHUTDOWN_BUTTON | Normal shutdown due to the button being pressed. |
No sound from Vector
If you're not hearing any sounds from Vector, please:
- Reboot Vector
- Adjust the volume on Vector. To do this: open the Vector app > tap Settings. If the volume is already on med or high, adjust it anyway to reset the volume
