Pepper/Nao robots are referred to as a device where a particular device is compromised of sensors and actuators. Unlike working with laptops/computers, one does not need to run specific drivers for sensors and actuators in order to communicate with the SIC framework, but instead only one particular software by the name robot-installer, which is in a JAR format.
Sensors and actuators
...
Microphone
...
Speakers
...
The following pages will provide a detailed list of sensors and actuators for Pepper and Nao robots:
Dependencies
There are no external dependencies to operate this set of devices except when one wishes to test and operate the device through a laptop. In order to do so, please run robot-installer makes this possible. For more details please refer to the section, How to use.
How to use
The robot-installer automatically launches a microphone, speaker, robot body, camera, and browser device. A robot’s identifier is generated based on the robot's MAC address, and should thus always be unique and consistent. The following steps will result in a successful connection between your laptop and robot:
Connect to the same WiFi as the Pepper/Nao Robot. Pepper’s tablet can have a separate WiFi connection from the robot itself; Pepper’s tablet settings can be opened by using the button in the program. The tablet page can also be reloaded using the second button.
To then connect to a Pepper or Nao for use with the SIC framework (see Local Installation), run the ‘robot-installer.jar’ (found in the cbsr-local folder of the docker repo) by either double-clicking on it, launching ‘run-robot-installer.bat’ (Windows) or launching ‘run-robot-installer.sh’ (Linux/Mac). For this, you need to have Java 8 or later installed on your machine.
Complete the initial dialog (just press OK), click Connect on the top-left, and follow the prompts (default Nao password: ‘nao’, default Pepper password: ‘pepper’).
You can inspect the log output of the various processes running on the robot using the different tabs. When done, click Disconnect (always do this to prevent lingering processes).
Limitations
There are no limitations, in context to the interaction with SIC framework, observed so far.