Get the Revo 3 SDK
Revo 3 SDK v2.x uses the Manager / Hand object model and provides Python, C ABI, and C++ interfaces. It covers discovery, connection management, motion, state and touch data, configuration, calibration, and firmware maintenance.
This page applies only to Revo 3. Revo 1 and Revo 2 use their own independent SDK packages; do not treat those version numbers as Revo 3 SDK v2.x versions.
The public Revo 3 example repository is brainco-revo3-sdk, while the Python wheel package is bc-revo3-sdk.
Start here
| Goal | Page |
|---|---|
| Understand the v2.x scope and object model | Revo 3 SDK v2.x overview |
| Install Python or prepare C/C++ | Installation and environment |
| Connect and run the first read-only check | Quick Start |
| Find APIs by capability domain | API navigation |
| Look up exact signatures, fields, and enums | Complete API manual |
| Upgrade module-level 1.x code | Migrate from 1.x to 2.x |
What changed in 2.x
Python 2.x does not export modbus_open(), DeviceContext, or module-level revo3_set_*() domain operations. Create a Manager, connect to obtain a Hand, and use the capability objects exposed by that hand:
Manager
└── Hand
├── motion
├── state
├── touch
├── health
├── config
├── calibration
└── maintenancePython and C++ object methods omit the revo3_ prefix. Public C ABI symbols retain it.
Revo 3 SDK v2.x resources
- Public example repository
brainco-revo3-sdk(dev branch) - Python wheel package:
bc-revo3-sdk - Revo 3 SDK v2.0.0 complete API manual
- Download and installation
- Quick Start and example entry points
Use BrainCo's official release channels for Revo 3 SDK v2.x packages. Use the installation page for Python wheels, and obtain the C/C++ libraries and accompanying example package from BrainCo technical support.
Register addresses and transport encodings are not part of the SDK API. See the communication protocol only when integrating without the SDK.