Both NAO and Pepper can be programmed to respond to a variety of stimuli, or programmed to engage in back and forth conversations. This is not a default behavior however, and your NAO or Pepper will not respond to any conversation until you teach it how to.
One easy way to do this is to install something called “Basic Channels” from the Aldebaran Cloud store. Basic Channels is a packaged set of dialog programs that makes the robot conversational right away.
If your NAO or Pepper used to respond to you and recently stopped, it is possible that the volume of the robot has been turned down so low that its answers are inaudible. It is also possible that a microphone is malfunctioning in the head. If you believe this to be the case, Contact Support.
Student devices lose the connection. Nothing will connect. The app freezes when I press "play". We've seen it all and found the solution!
If you are experiencing a problem with the Expeditions 2.0 program, the very first thing to check is that your teacher device is running the most up to date version. You can find the version number by opening the app and checking the bottom left corner of the Browse page. The most current version of the teacher app is 2.40. If you need to update the app, Contact Support.
If you are having trouble resetting your Tour Creator password, Contact Support.
There are two problems you might experience when creating tours in Tour Creator:
I created a project in Tour Creator but it isn’t showing up on the tablet.
"My Tours" has an unpublished project even though I selected “Publish” in Tour Creator.
Both of these problems stem from the Tour Creator login email address and the Expeditions 2.0 Activation Code.
This post has the solution for the following problems:
When I open Expeditions 2.0, I can’t see all of the headings on the left side.
Expeditions 2.0 is not displaying correctly.
Parts of Expeditions 2.0 are missing
If the menu on the left side of Expeditions 2.0 does not go all the way down to “Settings”, you may need to change your display settings.
If you push Pepper's chest button and nothing happens, don't panic. In almost every case an unresponsive Pepper is caused by one of two things: a depleted battery or the emergency stop button. Both can be checked easily.
Error 713: I can’t move anymore. I detected an error on n of my vital devices: [list n devices].
NAO does not finish booting up.
In rare cases, after a NAOqi update or factory reset, NAO will get “stuck” during its boot process and will never finish booting up. If you have been waiting (and waiting, and waiting) for NAO to finish booting up, there is probably a solution. This problem can usually be identified by the ear LEDs or the chest button LED.
Does my NAO have a battery problem?
As long as the battery is inside the NAO, it is delivering a small amount of electricity to the robot, even while shut down. If the NAO sits for a long time unused, the battery can become so depleted that it can no longer be charged.
If you suspect this is the case for your battery, here are some of the telltale signs:
If you conclude that you need a new battery, head to https://www.robotlab.com/store/battery to purchase a new one.
There are two common reasons a NAO will not stand up. One of them can be fixed by the customer with a computer and the other requires shipping the NAO for service.
Rather than try to distinguish between the two cases, it is easier to simply attempt the intervention and test the result. Your NAO will need to be connected to a WIFI network or hardwired to your computer, and you will need to SSH into the NAO. We use the program PuTTY for this purpose, but you can also use a Command Prompt.
This post can help if you are experiencing a problem such as:
-My NAO robot won't speak to me.
-My NAO robot won't say anything.
-My NAO robot stopped making sound.
If you’re unable to find an answer on our website, fill out the form below to start a ticket. We normally aim to respond to all emails within a few days.