Introduction
Introduction
RobotOS is developed based on the Android platform and provides a set of SDKs for android apk. Users can use RobotService.jar to develop android applications on the robot. All models running RobotOS support the SDK.
SDK release log
| version | date | description | GreetBot | Mini | Lucki | DeliverBot | BigScreenBot |
|---|---|---|---|---|---|---|---|
| V1.1.1 | 2021/3/2 | – | V6.2 and above | V6.2 and above | V6.2 and above | – | – |
Concepts you need to know
- Application authorization:Only when the app is successfully connected to RobotOS and the app interface is displayed on the front end, the app can be successfully authorized to use the SDK. When the app interface returns to the background, the app is immediately suspended.
- Application is suspended:The robot will encounter some system events, such as emergency stop, low battery, OTA, hardware abnormality, etc. When these system events occur, RobotOS will take over the business, and the business apk in the foreground will be suspended. Since the onsuspend event is received, the business apk no longer has the ability to use the api
- Application resume suspension:Corresponding to the suspension event, when the system event disappears, RobotOS will return business control to the current app, and the current apk will resume the ability to use RobotApi
FAQ
- Calling api returns resource usage conflictFor the api related to hardware usage provided in the SDK, when two interfaces are used to operate the same device at the same time, resource use conflicts will occur. For example, when a robot is navigating, the left turn and right turn api cannot be used at the same time.
- apk call api does not take effectYou need to make sure the apk is authorized, and the apk is called up using RobotOS Home.Like the video below:
If you want to start an apk when you turn on the robot, you can set “default boot app” in the robot settings(Settings — Other Settings — Boot apps).