Rakuda2 controllers
The controllers that drive the Rakuda2 follower. Which one runs is chosen with the launch options of .roboloom/rakuda2/config.yaml. What all controllers share is in Controllers.
| Controller | Input | Options | Status |
|---|---|---|---|
| Leader | Rakuda-mini (leader) |
none | Hardware-verified |
| Gravity-compensated leader | Rakuda-mini (leader) |
gravity |
Hardware-verified |
| Policy | a policy | policy |
Hardware-verified |
| Policy with interventions | a policy and the Rakuda-mini | policy, policy_teleop |
Hardware-verified |
| Pika Sense and IK | a Pika Sense per arm | pika |
In development |
| Force feedback | Rakuda-mini (leader) |
gravity, bilateral |
Mock only (paused; Rakuda2) |
flowchart LR
L["leader<br/>Rakuda-mini"] --> J["controller<br/>type: joint"]
P["policy"] --> C["policy<br/>type: policy"]
S["Pika Sense ×2"] --> K["controller<br/>type: parts + pose_ik"]
J --> F["follower<br/>Rakuda2"]
C --> F
K --> F
Leader
Hardware-verified
The configuration with no option enabled. Each leader joint maps to the follower joint of the same name. The leader's arms, torso and head have the torque off; the trigger is controlled as a spring (law: spring).
# nodes/controller.yaml (excerpt)
type: joint
input: leader
followers: [follower]
alignment_tolerance: 300
max_speed: 2048
command_deadline_ms: 100
input_timeout_ms: 150
couplings: []
- Align the leader with the follower before starting. While
aligning, a start is refused and the joint difference is shown. - Locking leader joints (
law: position) and the torso-yaw compensation (couplings) are Mock only. - Settings in detail: Leader. Steps: Rakuda2: teleoperated collection.
Gravity-compensated leader
Hardware-verified
The option gravity replaces the leader node nodes/leader.yaml with nodes/leader_gravity.yaml. The controller is still joint. Both arms run the gravity_comp control law with the identified gravity model, travel and tuning values.
uv run roboloom run --with gravity
- Loading is refused until the measurements (
calibrate-joints,measure-travel,identify-gravity,tune-gravity) are done. Steps: Rakuda2: gravity compensation. - It cannot be combined with
policy.
Policy
Hardware-verified
The option policy removes the leader and the controller and adds controllers.policy. roboloom infer turns it on by itself.
# nodes/policy.yaml (excerpt)
type: policy
followers: [follower]
factory: roboloom.policy:hold # keeps the arms where they are; replace with your policy
kwargs: {}
observe: [camera] # with the digit option, digit_left and digit_right can be added; [] for state only
rate_hz: 15
action_horizon: 8
max_speed: {follower: 1024}
command_deadline_ms: 300
uv run roboloom infer --seconds 20 --policy my_lab.policies:load
- Observation and action are the 17 joints in counts (Observation and action).
- Shared description: Policy (controller), Running a policy. Steps: Rakuda2: from collection to inference.
Policy with interventions
Hardware-verified
The option policy_teleop adds the leader back to policy, so the leader can drive the follower before and during an episode.
# nodes/policy_teleop.yaml
extends: policy.yaml
teleop: [controller.yaml] # the joint controller the leader drives through
uv run roboloom run --with policy,policy_teleop
- Rows a person drove have
action.intervention1. The dataset name gets-eval-teleop. - Shared description: Teleoperation and interventions. Steps: Rakuda2: evaluating with interventions.
Pika Sense and IK
In development
The option pika drives each arm and gripper with its own Pika Sense through inverse kinematics, instead of the leader. Checked with mock devices only.
# nodes/controller_pika.yaml
type: parts
followers: [follower]
command_deadline_ms: 100
parts: [pika_right.yaml, pika_left.yaml] # each one type: pose_ik
uv run roboloom run --with pika --mock
- The joint map, zero points and gripper map are all first guesses. What to check before hardware is in Rakuda2 with Pika Sense and IK.
- Shared description: Pika Sense and IK.