8 Items found
How to use logs in Android Studio to develop QiSDK application on Pepper robot - The aim of this tutorial is to give a quick overview of logging in the Android Studio environment. As a live example to put logs into practice, we will also focus on the application lifecycle in the QiSDK context which is based on Android lifecycle.
Sending Slack messages by voice thanks to Pepper - What if Pepper could help you increase your productivity at work? By linking the robot to a Slack channel, we will be able to send and receive messages by voice control thanks to Pepper.
Kotlin and the KDoc documentation - At SoftBank Robotics, we use Kotlin to develop the QiSDK API for Pepper robots and most libraries and applications. In this article, we will introduce Kotlin and the KDoc, explain why we made that choice and how to make a smooth transition from Java to Kotlin.
Linking Pepper to a web API using android's Retrofit client - Learning about API use and how to link them to Pepper, we will grant the robot access to the Nager.date API, an online service containing data about the upcoming holidays worldwide. The goal of the app we will create would be for Pepper to answer to related questions such as: “Pepper, is today a holiday in Japan?”.
Controlling a Philips hue lamp with a simple robotic app - Light up your living room just by greeting Pepper when coming home thanks to IoT (Internet of Things). There is a large variety of connected objects such as lamps, boilers, presence sensors, radiators and much more you can try to connect to your Pepper. You could imagine Pepper being the interface to your home’s devices and control them.Let’s connect Pepper to a Philips Hue lamp in the first place.
Pepper (NAOqi 2.5) And Pepper QiSDK: a paradigm shift with product versions still available - How to choose between Pepper (NAOqi 2.5) And Pepper QiSDK? On the one hand, NAOqi 2.5 is a flexible Python-based development platform for advanced robotics programs, and on the other hand, the QiSDK is a stable Android-based solution for interactive and market-fit use cases. Let's check these points more closely.