PEPPER - Events and notifications
Print
Modified on: Thu, 20 Jan, 2022 at 2:49 PM
You may receive notifications from PEPPER system or from an application.
In that case, a small sound is played and the status LEDs remain still white but blink once in a while with a colour indicating the severity of the notification.
Error and Warning notification messages are prefixed by their severity and their ID when they are said, so that you can give them to the customer support to describe more easily your problem.
- examples:
- Warning 801, my battery will soon need charging.
- Error 803, my battery is totally empty. I’m shutting down.
- Error 722, I can’t move anymore. Some of my motors are too hot in my Right Arm. Please let me rest for a while.
List of notifications
Boot process
# | Message | Tips | Severity |
---|
10 | I canceled my system update. The system image was invalid. I am still running version < x.y.z >. | The file containing the system image seems unusable, try again to retrieve the relevant system file. |  |
11 |
100 | I successfully updated my system. I am now running version < x.y.z >. | |  |
101 | I canceled my system update. The system image was not compatible with my upgrade program. I am still running version < x.y.z >. | The system image used for the update is not compatible with your robot hardware. Check what system image version supports your robot version and model, and retry with one of the supported system image version. |  |
102 | I canceled my system update. The system image was not compatible with my processor. I am still running version < x.y.z >. |
103 | I canceled my system update. The system image was not compatible with my body. I am still running version < x.y.z >. |
104 | I canceled my system update. The system image was corrupted. I am still running version < x.y.z >. | The system image is corrupted. Try downloading it again then restart the update process. |  |
105 | I canceled my system update. My current system seems corrupted. I am still running version < x.y.z >. | The update program cannot recognize your robot hardware. Some changes done on the hardware damage it. Contact the support. |  |
110 | I could not update my system. Try to update me again. | |  |
111 |
120 | I successfully completed my factory reset. All my data and settings have been reset. | |  |
200 | I couldn’t complete my factory reset. I may still have some data or settings from before. Retry a factory reset to remove all my data and settings. | Retry the update with factory reset enabled. If the problem persists, contact the support. |  |
201 |
202 |
203 | I successfully completed my factory reset. All my data and settings have been reset. | |  |
204 | I can’t access some of my data. My user partition seems corrupted. Please try to reboot me to fix the problem. | The memory space dedicated to the user is not accessible due to some hardware failure. Try to reboot the robot. If the problem persists, contact the support. |  |
205 |
214 | I can’t access some of my data. My internal partition seems corrupted. Please try to reboot me to fix the problem. | The memory space dedicated to internal usage is not accessible due to some hardware failure. Try to reboot the robot. If the problem persists, contact the support. |  |
215 |
400 | I can’t move. My current system is not compatible with my body. Retry to update me with a compatible system image. | The current system image of your robot is not compatible with your robot hardware. Check what system image version supports your robot version and model, and retry with one of the supported system image version. |  |
401 | I can’t move. My current system is way too old for my body. Retry to update me with a more recent system image. |
402 | I can’t move. My current system is way too recent for my old body. Retry to update me with a less recent system image. |
404 | I can’t move. I can’t access my body. Please try to reboot me to fix the problem. | The head does not find or recognize its body. The robot is unusable. Try to reboot to fix this. |  |
405 | I updated some of my firmwares. Please reboot me to finish the update. | Some new firmwares have been installed but will not be enabled until a reboot of the robot. Turn off the robot using the standard procedure, then start it again. If this warning occurs on every boot, it means: - either some hardware is too old and cannot be updated;
- or some hardware is broken and cannot be updated.
In either case, you should contact the support. |  |
500 | I can’t connect to the cloud services. My head identifier is missing. Please contact support. | Contact the support. |  |
501 | I can’t connect to the cloud services. My system date is wrong. Please ensure that I am connected to the Internet and reboot me to fix the problem. | Make sure your robot is connected to the Internet then restart it to update the date. |  |
600 | I’m not safe like this. Please help me sit or crouch. | The robot is not in a good position to start autonomous life. Put it in sitting or crouching position and it will start life. |  |
Diagnosis - Pepper
Battery - notifications
# | Message | Tips | Severity |
---|
800 | I can’t access my battery. Please try to reboot me to fix the problem. | If the problem persists after a reboot, contact the support. |  |
801 | My battery will soon need charging. | The battery level reached a low level. |  |
802 | My battery needs urgent charging. | The battery level reached a very low level. |  |
803 | My battery is totally empty. I’m shutting down. | The robot ran out of battery so it shut down. |  |
805 | My battery is now fully charged. | |  |
806 | I detected an unusual temperature on my battery. I’m shutting down. Please let me rest for at least 2 hours before rebooting me. | If the problem persists after 2 hours with the robot off, contact the support. |  |
810 | I failed to leave my charging station. Please help me to move away from it. | The robot is in an unknown and unsafe position. Push him away from its charging station like described in section Moving Pepper while off . |  |
Store - notifications
# | Message | Tips | Severity |
---|
830 | I have installed < Name of the applications >. | |  |
832 | I have updated < Name of the applications >. | |  |
834 | I have removed the application < Name of the applications >. | |  |
840 | I have downloaded system version < x.y.z >. Reboot me to install it. | |  |
Robot backup tool - notifications
# | Message | Tips | Severity |
---|
900 | I successfully backed up my data. | |  |
901 | I couldn’t back up my data. My system version is not compatible with this operation. Please try to update me with a more recent version and try again. | |  |
902 | I couldn’t back up my data. The files were not readable. Please try again. | |  |
903 | I couldn’t back up my data. Connection with back up application was interrupted. Please ensure that I am connected to the network and try again. | |  |
920 | I successfully restored my data. | |  |
921 | I couldn’t restore my data. My system version is not compatible with this operation. Please try to update me with a more recent version and try again. | |  |
922 | I couldn’t restore my data. The files were not writable. Please try again. | |  |
923 | I couldn’t restore my data. Connection with back up application was interrupted. Please ensure that I am connected to the network and try again. | |  |
Did you find it helpful?
Yes
No
Send feedback Sorry we couldn't be helpful. Help us improve this article with your feedback.