Setting up the Rainbow Robotics RB-Y1 wheeled humanoid takes roughly 2.5 hours and four phases: unbox the 131 kg robot in a sturdy, level space (≥4 m × 4 m), charge the 3‑hour battery fully, connect via Ethernet/Wi‑Fi (assign your PC a static IP in the robot’s subnet, typically 192.168.1.x or 10.42.0.x; check manual), then update to the latest firmware, run IMU/arm calibration, and perform a guarded first drive. Always locate the emergency stop before power‑on.
Table of Contents - Before You Start: Safety & Space Requirements - What You’ll Need: Tools, Space & Time - Step 1 — Unboxing & Physical Inspection - Step 2 — Battery Installation & Charging - Step 3 — Powering On & First Boot - Step 4 — Network Configuration (Wi‑Fi vs Ethernet) - Step 5 — App / Remote Control Binding - Step 6 — Firmware Update & Security Hardening - Step 7 — SDK / ROS Setup (Advanced) - Step 8 — Calibration & First Movement - Defining Success: Minimum / Full / Advanced - Common Setup Mistakes & Fixes - Frequently Asked Questions - About the Author / How We Tested
## Before You Start: Safety & Space Requirements Critical: The RB‑Y1 is a heavy (131 kg) industrial‑grade wheeled humanoid. It is not a toy — an uncontrolled 131 kg platform at 5.4 km/h can cause serious injury or property damage.
- Exclusion zone: mark a minimum 4 m × 4 m area on a flat, level, and hard floor (concrete or industrial epoxy; avoid carpet, uneven tiles). No people, pets, or fragile objects inside while the robot is powered.
- Emergency stop: both the onboard red button and the wireless E‑Stop (if supplied) must be tested before first motion. The E‑Stop should be on your person during all initial tests.
- Floor load: the robot’s weight plus its rolling point‑loads require a floor rated for at least 300 kg/m² over its caster footprint — check building specs.
- Wheel chocks or soft stops: place chocks at the boundaries of the exclusion zone so the robot cannot roll into walls if it misbehaves.
- No overhead hazards: the RB‑Y1 stands 161 cm tall; ensure no low‑hanging lights or shelves are in the workspace.
- Suspension not needed: unlike legged robots, the RB‑Y1 is stable on its wheels; no hanging or suspension rig is required.
> First‑time rule: operate the base only in “joint‑by‑joint” or low‑speed (<0.5 km/h) mode until you are confident the E‑Stop works and the calibration is correct.
## What You’ll Need: Tools, Space & Time
Tools & Supplies
- The RB‑Y1 crate and original packaging (you need the lifting handles)
- A pallet jack or fork‑lift rated for ≥150 kg — the robot ships on a pallet
- The supplied charger (100‑240 V AC, likely 24 V/25 A; verify with manual)
- A sturdy Ethernet cable (Cat 6) and a laptop with an RJ‑45 port or USB‑Ethernet adapter
- Your laptop running Ubuntu 22.04 or Windows 10/11 with Rainbow Robotics’ RobotManager software installed
- A magnetic spirit level (optional, for checking flatness)
- Small flashlight, a set of hex keys (M3–M6), and a torque wrench (as needed for arm mounts)
Space & Environment
- Minimum clear floor: 4 m × 4 m, flat, polished concrete
- Ambient temperature 10–35 °C, humidity 20–80 % non‑condensing
- Good lighting so you can see the robot’s indicator LEDs
Time Estimates (first‑time user)
| Phase | Approximate Time |
|---|---|
| Unbox & inspection | 20–30 min |
| Battery install & full charge | 60–90 min (assuming discharged battery) |
| Power‑on, network, binding | 30 min |
| Firmware update & security | 20 min |
| SDK/ROS install (optional) | 30–45 min |
| Calibration & cautious first drive | 30 min |
| Total (parallel charging possible) | ~2.5 hours |
## Step 1 — Unboxing & Physical Inspection
- Move the pallet to your prepared exclusion zone using a fork‑lift or pallet jack.
- Remove the outer cardboard and strapping. Keep all packaging for future transport.
- With at least two people, slide the robot out of the crate using the built‑in rolling ramps or lift it evenly — never tilt more than 10°.
- Inspect for transit damage:
- Check the two 7‑DOF arms for any obvious dents, loose joints.
- Verify the head pan‑tilt moves freely (unpowered) and no cables are pinched.
- Inspect the four Mecanum or omni‑wheels for debris.
- Look at all connector panels; nothing should be loose.
- Locate the emergency‑stop button on the upper rear panel and ensure it is in the depressed (off) position before doing anything else.
## Step 2 — Battery Installation & Charging
The RB‑Y1 uses a large lithium‑based battery pack (3 hours runtime). Often it ships already installed, but follow the manual to confirm.
- To install (if separate): open the rear battery bay, slide the pack onto the guide rails, and press firmly until the connector locks with a click.
- Charging: connect the supplied charger to the port on the rear panel (usually a 3‑pin military‑style connector). Plug into mains; a red LED indicates charging, green when full.
- Charge fully before first use — approximately 1.5 hours from empty, but leave it on the charger until the indicator turns green.
- Do not charge unattended and keep the charger away from flammable materials.
## Step 3 — Powering On & First Boot
- Double‑check that the emergency stop is pressed (off).
- If the robot has a key switch, insert the key and turn to “ON”.
- Release the emergency stop by twisting it clockwise; it should pop outward.
- Press the main power button (usually a green illuminated button). You should hear a relay click and see status LEDs illuminate.
- The robot’s internal PC will boot; wait approximately 60–90 seconds until the status LED transitions from blinking blue to steady cyan. During boot, the wheels may twitch slightly — this is normal.
- If the robot does not boot, press the emergency stop, wait 30 seconds, and try again. If the battery is critically low, charge for at least 30 minutes first.
## Step 4 — Network Configuration (Wi‑Fi vs Ethernet)
The RB‑Y1’s internal computer is typically accessible via Ethernet. Verify the exact IP from the user manual; many Rainbow Robotics systems default to 192.168.1.10 (or 10.42.0.10). Below are generic directions — consult the manual for precise values.
- Wired (recommended for initial setup):
- Connect an Ethernet cable between the robot’s LAN port and your laptop (or a switch on the same subnet).
- On your laptop, set a static IP address in the same subnet, e.g.
192.168.1.100(mask 255.255.255.0, gateway blank) — avoid the robot’s IP. - Test with
ping 192.168.1.10. If no reply, check cable, firewall, and that the robot’s network service has started (it may take 30 s after boot).
- Wi‑Fi (if available):
- Connect to the robot’s hotspot (SSID often
RB-Y1-XXXX). The password is usually printed on a label inside the battery bay. - The robot’s IP will be the gateway (often 192.168.50.1). Set your laptop to obtain an IP automatically or use the subnet provided.
- Comparison:
| Feature | Ethernet | Wi‑Fi |
|---|---|---|
| Latency | <1 ms | 5–15 ms |
| Throughput | 1 Gbps | ~100 Mbps |
| Reliability | Stable | Interference risk |
| Use case | Development, ROS, heavy teleop | Quick app control, diagnostics |
## Step 5 — App / Remote Control Binding
- Download the Rainbow Robotics mobile app (iOS/Android) or the Windows‑based RobotManager from the official site.
- With the robot on and network accessible, launch the app and search for devices on the local network. The RB‑Y1 should appear with its serial number.
- Select it and enter the default PIN (often
0000or1234; change it later). The app will bind and show battery, joint angles, and sensor data. - If binding fails, verify that your phone/laptop is on the same subnet as the robot and that multicast traffic is allowed.
## Step 6 — Firmware Update & Security Hardening
- Check current firmware: in the RobotManager, go to “System Info” and note the firmware version. Visit the Rainbow Robotics download portal to see the latest version.
- Update if needed: download the firmware image (.swu, .bin, etc.) and use the “Firmware Update” wizard in RobotManager. The robot will reboot; do not interrupt power.
- Security hardening (critical):
- Change the default password for the robot’s system user (often
rbrobotoradmin). Use a strong, unique password. - Disable any unused network services (e.g., Telnet, HTTP without SSL) via the web configuration interface.
- Disable the Wi‑Fi hotspot when not in use, or hide its SSID and use WPA3 if supported.
- Keep firewall enabled and restrict incoming connections to your development PC’s IP only.
- Regularly check the Rainbow Robotics security advisory page for patches — although no public CVEs exist yet for the RB‑Y1, updating promptly is your best defence.
## Step 7 — SDK / ROS Setup (Advanced)
Rainbow Robotics provides a Python/C++ SDK and a ROS package. The following is a generic installation; adjust exact version numbers as per the official GitHub rainbowrobotics organization.
Prerequisites
- Development PC: Ubuntu 22.04 (recommended), ROS 2 Humble
git,cmake,python3-colcon-common-extensions, and the appropriatelibrealsensepackages for any camera.
Install the SDK (Python example)
mkdir -p ~/rainbow_ws/src && cd ~/rainbow_ws/src
git clone https://github.com/rainbowrobotics/rb_y1_sdk.git -b main
git clone https://github.com/rainbowrobotics/rb_y1_description.git
cd ~/rainbow_ws
rosdep install --from-paths src --ignore-src -r -y
colcon build --symlink-install
echo "source ~/rainbow_ws/install/setup.bash" >> ~/.bashrc
Verify connection
After building, source the workspace and run: ``bash export ROS_DOMAIN_ID=0 # or match robot ros2 run rb_y1_sdk joint_states_subscriber ` If you see real joint angles, the robot’s control node is communicating. If not, triple‑check: - IP routing and the ROS_MASTER_URI/ROS_IP` settings. - That the robot’s internal ROS bridge node is running (it should start automatically after boot). - Firewall does not block the ROS DDS ports (default UDP on 7400–7500).
## Step 8 — Calibration & First Movement
- IMU calibration: place the robot on a perfectly level surface. In RobotManager, start the IMU calibration routine. The robot must remain motionless for ~20 seconds.
- Arm joint calibration: both arms may need a home‑position calibration. Use the app to move each joint slowly to its mechanical zero, then press “Set Home”. Some units auto‑detect home via limit sensors — follow the on‑screen guidance.
- Wheel‑encoder check: lift the robot slightly (use a low‑profile dolly) so wheels can spin freely. In diagnostic mode, command a low‑speed forward command and verify all wheels rotate in the correct direction and speed.
- First guarded motion:
- Place chocks 0.5 m in front and behind all wheels.
- Ensure the E‑Stop is held by a second person.
- In the app, switch to “Low‑Speed Joint Control” mode.
- Gently move the base forward 10 cm at a time. If the robot veers or a wheel locks, stop and recalibrate the encoders.
- Repeat with rotation and arm movements.
Once these checks pass, you can gradually increase speed and complexity.
## Defining Success: Minimum / Full / Advanced
| Tier | Definition |
|---|---|
| Minimum viable | Robot powers on, connects to the app, wheels turn, and each arm joint responds to low‑level command — no autonomous movement yet. |
| Full operational | Firmware updated, network secured, IMU/arms calibrated, teleoperated driving and manipulation work reliably within the safety zone. |
| Advanced | SDK/ROS installed, custom motion planning node runs, autonomous pick‑and‑place or navigation tasks execute without human intervention. |
## Common Setup Mistakes & Fixes
| Symptom | Root Cause | Fix |
|---|---|---|
| Robot won’t power on | Battery disconnected or emergency stop pressed | Check battery latch, release E‑Stop, ensure key switch (if any) is ON. Charge if low. |
| No ping to robot | PC not on the correct subnet or wrong port | Set static IP in the robot’s subnet; try both Ethernet ports. Confirm LED activity. |
| App cannot bind | Different Wi‑Fi network or multicast blocked | Use the robot’s hotspot SSID or the same wired subnet; disable VPN/firewall temporarily. |
| ROS nodes can’t find robot | ROS_DOMAIN_ID mismatch or wrong DDS configuration | Set ROS_DOMAIN_ID equal to the robot’s (usually 0); check ROS_LOCALHOST_ONLY=0. Verify DDS vendor (CycloneDDS is typical). |
| Wheels spin in opposite directions | Motor phase reversed from factory | Run the motor‑check diagnostic in RobotManager; may require contacting support. |
| Arm joints “hum” but don’t move | Joint brake still engaged or servo not enabled | In the SDK/App, send an “enable servo” command before sending a position. Check brake release signal. |
| Robot drifts when stationary | IMU not calibrated or floor slope >1° | Re‑calibrate IMU on a confirmed level surface. Use a spirit level. |
| Overcurrent error on first motion | Collision with chocks or binding in wheel | Remove obstructions; check that all wheels turn freely by hand. Lower acceleration limits. |
| Firmware update fails | Corrupt download or interrupted power | Re‑download the firmware file, ensure stable power, and retry. Use a UPS. |
| No camera feed | Camera USB disconnected or driver missing | Reseat all USB 3.0 cables; install librealsense and ensure the video4linux device appears in lsusb. |

Komentari