Event and state notifications¶
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 color indicating the severity of the notification.
| Status LEDs is ... | Severity | |
|---|---|---|
Steady White light, cut by a brief blinking in ... |
Green  |
Pepper gives you some feed-back by an Info notification about an ongoing action. |
Yellow  |
Warning notification occurs when an issue requires your attention and/or action. Pepper is still usable but, it may either run in a degraded mode in which some features may be not available or it may soon become unusable if you don’t solve the problem. |
|
Red  |
Error notification occurs when one or all functionality(ies) of Pepper become unusable. Try to solve the problem using the tips. If the problem persists, contact the customer support and provide them with the error ID. For further details, see: Contacting customer support for Pepper. |
|
Tips:
- 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.
- To ask Pepper to read the notification, see: Requesting technical information.
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:
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¶
| # | Message | Tips | Severity |
|---|---|---|---|
| 710 | I can’t move anymore. I detected an error on <X> of my vital devices: <list of devices>. Please try to reboot me to fix the problem. | This will have an impact on your robot, see Diagnosis effect. If the problem persists after a reboot, contact the support. |
|
| 711 | I detected an error on <X> of my devices: <list of devices>. Please try to reboot me to fix the problem. | |
|
| 712 | I detected a system error: one of my software does not run properly. Please try to reboot me to fix the problem. | If the problem persists after a reboot, contact the support. |
|
| 713 | I can’t move anymore. I detected an error on <X> of my vital devices: <list of devices>. Please try to reboot me to fix the problem. | This will have an impact on your robot, see Diagnosis effect. If the problem persists after a reboot, contact the support. |
|
| 714 | I detected an error on <X> of my devices: <list of devices>. Please try to reboot me to fix the problem. | |
|
| 720 | Some of my motors are getting hot in my <chainName wheel or sensor>. I will need to rest soon. | Robot motors are getting hot or are already too hot to be able to move. Put the robot in crouch and unstiffened and wait for few tens of minutes to let its motors cool down before you can use it again. | |
| 721 | A part of my body cannot move anymore. Some of my motors are too hot in my <limbName>. Please let me rest for a while. |
||
| 722 | I can’t move anymore. Some of my motors are too hot in my <limbName>. Please let me rest for a while. | |
|
| 723 | Some of my motors are getting hot in my <chainName wheel or sensor>. I will need to rest soon. | |
|
| 724 | Some of my motors are too hot in my <limbName>. Please let me rest for a while. | ||
| 725 | My memory seems full. Please reboot me to fix the problem. | Robot RAM is full. Reboot the robot. | |
| 726 | My memory seems full. Please remove some applications or data to make some room. | Robot user partition is full. Remove some applications or some data. | |
| 730 | My head processor is getting hot. I will need to rest soon. | Robot head processor is getting or is already too hot. Shut down the robot for few tens of minutes. | |
| 731 | My head processor is too hot. Please let me rest for a while. | |
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. See: Charging the battery. | |
| 802 | My battery needs urgent charging. | The battery level reached a very low level. See: Charging the battery. | |
| 803 | My battery is totally empty. I’m shutting down. | The robot ran out of battery so it shut down. See: Charging the battery. | |
| 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. | |
