Examples¶
Each example can be run in a separate terminal while the driver is active:
source install/setup.bash
ros2 run rby1_examples <example_name>
Example |
Command |
Description |
|---|---|---|
|
|
Full power lifecycle: Power ON/OFF, Servo ON/OFF |
|
|
Continuously prints state monitor (Motor state, brakes, battery, etc) |
|
|
Continuously prints tool flange data |
|
|
Prints per-component joint positions in real time |
|
|
Enables/Disable gravity compensation mode |
|
|
Moves all joints to 0 rad simultaneously |
|
|
Sends Ready Pose with joint_position(right), joint_impedance(left) |
|
|
Sends Ready Pose and moves the arms to a target Cartesian pose with cartesian_position(right), cartesian_impedance(left) |
|
|
Simultaneous joint + Cartesian control per body part |
|
|
Streams a pre-computed trajectory via standard FollowJointTrajectory action |
|
|
Demonstrates action cancel and |
|
|
Drives the mobile base via |
|
|
Alternates Zero/Ready poses using regular joint commands over persistent stream with varying wait intervals |
|
|
use collision value in robot.state, Demonstrates that when collision happens, robot automatically moves retreat to initial safe pose. |
[!IMPORTANT] Two ways to stop control commands (see Example : 11_cancel_control):
Action cancel — Cancels only the current action goal. The stream remains open, so subsequent commands can continue immediately.
cancel_controlservice — Immediately stops all control commands and forcibly closes the stream for safety.⚠️ If you are using stream-based control (e.g.,
cmd_vel, Example 13), callingcancel_controlwill also shut down the stream.
You will need to re-open the stream (/stream_control state: true) before sending further commands.
If you only want to pause or cancel a specific motion while keeping the stream alive, use the action cancel instead (see Example 13).If an issue arises, please check the Troubleshooting & Known Issues section to see if there is any relevant information.
[!NOTE] Simulator Limitation: Battery voltage, FT sensor, and IMU data read as
0.0in simulation (no physical hardware). Tool flange topics: Requirespublish_tool_flange_state: trueindriver_parameters.yaml.