Agibot X2 Ultra
X2 Ultra Support & Developer Center
Everything you need to unbox, operate, maintain, and build on the AgiBot X2 Ultra humanoid robot — from first power-on to SDK development.
Unit Reference
Confirm your unit's exact configuration on the label inside the battery compartment before referencing procedures below.
Safety Guide
Read this section in full before powering on the robot for the first time. The X2 Ultra is a dynamic, self-balancing machine with significant mass and joint torque.
Never place hands, cables, or clothing near joint assemblies while the robot is powered. Joints can move without warning during balance corrections, even when the robot appears idle.
Operating environment
- Clear a safe zone. Maintain at least 2–3 m of clearance in all directions during operation, testing, and development. Keep children and pets outside the zone at all times.
- Use flat, non-slip flooring. Avoid loose rugs, cables on the floor, wet surfaces, and stairs until you are fully familiar with the robot's locomotion behavior.
- Check temperature and moisture. Operate indoors within the temperature range stated on your unit's spec sheet. The X2 Ultra is not waterproof — keep it away from liquids.
- Have the E-stop ready. Keep the remote/emergency stop within reach whenever the robot is standing. Know the soft-stop and hard-stop procedures before your first session.
Battery and charging safety
- Use original equipment only. Charge only with the supplied charger and battery packs. Third-party chargers void the warranty and pose a fire risk.
- Never charge unattended overnight or near flammable materials. Charge on a hard, non-flammable surface.
- Inspect before every charge. Do not charge a battery that is swollen, damaged, or has been dropped. Contact support for replacement.
- Storage. For storage over 2 weeks, keep batteries at roughly 50–60% charge in a cool, dry place.
Lithium battery packs are classified as dangerous goods for air freight. If you ship the robot internationally, batteries may require separate documentation and certified packaging. Contact support before arranging transport.
Quick Start
From crate to first steps in five stages. Allow 45–60 minutes for first-time setup, including a full initial charge check.
- Unbox and inspect. Remove the robot from its transport crate with two people. Check the frame, joint covers, and hands for shipping damage. Photograph any damage before proceeding and report it within 48 hours.
- Install and charge the battery. Seat the battery pack until it clicks, then connect the charger. Wait until the indicator shows a full charge before the first power-on.
- Power on in a supported posture. Place the robot in its designated startup posture (seated/crouched per the printed quick-start card), then press and hold the power button until the status LED cycles. Do not touch the robot during its self-check and stand-up sequence.
- Pair the remote and app. Power on the remote controller, then connect the companion app to the robot's Wi-Fi hotspot or your local network. Confirm firmware is up to date before first operation.
- Run first motions in a clear area. Begin with in-place balance and slow walking in the safe zone. Keep a hand on the E-stop. Only progress to faster gaits and whole-body motions once basic control is familiar.
Record your robot's serial number and firmware version now — both are required for support tickets, warranty claims, and SDK license activation.
Operation Guide
Day-to-day operation: control modes, status indicators, and recovery procedures.
Control modes
| Mode | Input | Typical use |
|---|---|---|
| Remote control | Handheld controller | Manual driving, demos, positioning |
| App control | Companion mobile app | Status monitoring, preset motions, firmware updates |
| Autonomous | Onboard perception | Navigation and task routines (where enabled) |
| Developer | SDK / API over network | Custom applications, research, integration |
Status LED reference
| Indicator | Meaning | Action |
|---|---|---|
| Steady green | Ready / normal operation | None |
| Pulsing blue | Pairing or update in progress | Do not power off |
| Flashing amber | Low battery or thermal warning | Return to base, allow cooldown or charge |
| Flashing red | Fault / protective stop | Clear the area, check the app fault log |
LED patterns can vary by firmware version — treat the companion app's fault log as the source of truth.
If the robot falls
- Trigger a soft stop from the remote before approaching. Confirm the joints have de-energized.
- Inspect visually for cracked covers, loose cables, or debris in joints before restarting.
- Use the recovery routine. Where supported by firmware, run the get-up routine from the remote rather than lifting the robot manually. If manual lifting is required, use two people and lift by the frame points shown in the manual — never by the arms or head.
Maintenance & Care
A small amount of routine care significantly extends service life and protects your warranty.
| Interval | Task |
|---|---|
| Every session | Visual check of joints, covers, hands, and feet; confirm no error codes in the app log. |
| Weekly | Wipe exterior with a dry or slightly damp cloth (never solvents); check foot soles for wear and embedded debris. |
| Monthly | Check firmware for updates; inspect battery contacts; verify remote controller battery and pairing. |
| Quarterly | Full-charge battery health check via the app; review joint calibration; back up any custom SDK configurations. |
There are no user-serviceable parts inside the torso, head, or joint assemblies. Opening these voids the warranty. All internal service is performed by authorized technicians.
Firmware updates
Install firmware updates through the companion app while the robot is on the charger, in a stable posture, with at least 50% battery. Never power off during an update. Release notes are published with each version — review them before updating units used in production or development.
Developer & SDK
The X2 Ultra exposes a developer interface for motion control, perception data, and task programming over a network connection.
Development setup
- Prepare a host machine. A Linux workstation (Ubuntu 20.04+ recommended) on the same network as the robot. Wired Ethernet is strongly recommended for low-latency control loops.
- Obtain SDK access. Request SDK credentials with your robot's serial number. You will receive the SDK package, API reference, and example projects.
- Connect and verify. Confirm the host can reach the robot's IP, then run the supplied "hello robot" example to read joint states before sending any motion commands.
- Develop against simulation first. Where a simulator build is provided, validate new behaviors in simulation before deploying to hardware.
Typical control flow
# Pseudocode — see the API reference shipped with your SDK package robot = x2.connect("192.168.1.120") state = robot.get_state() # joint positions, IMU, battery robot.set_mode("developer") # take low-level control robot.walk(vx=0.3, vy=0.0, yaw=0.0) # velocity command (m/s, rad/s) robot.stop() # always end sessions with a stop
Custom motion code bypasses some built-in safeguards. Always test with the robot in a harness or with generous clearance, keep the E-stop in hand, and rate-limit your first commands.
Interfaces at a glance
| Interface | Purpose |
|---|---|
state | Read joint positions, velocities, IMU, battery, temperatures |
locomotion | High-level gait and velocity commands |
manipulation | Arm and hand control, grasp primitives |
perception | Camera and depth streams, detection outputs |
system | Mode switching, logs, firmware info, soft stop |
Interface names above are illustrative — consult the API reference for your SDK version for exact modules and message definitions.
Frequently Asked Questions
Q01The robot won't power on. What should I check first?
Confirm the battery is fully seated (you should hear a click) and charged above the minimum threshold. Try the power button hold again for the full duration. If the status LED never lights, remove and reseat the battery, then attempt a charge cycle. If it still fails, open a support ticket with your serial number.
Q02The app can't find the robot on the network.
Verify the robot and your phone/host are on the same network or that you have joined the robot's hotspot. Corporate networks with client isolation frequently block discovery — a dedicated router or hotspot is the most reliable setup. Rebooting the robot re-broadcasts its discovery signal.
Q03How long does the battery last, and can I buy spares?
Runtime depends heavily on gait, payload, and terrain — continuous walking consumes far more than standing or manipulation tasks. Spare battery packs are available as accessories and swap in seconds; most commercial operators run a two-pack rotation.
Q04Can I run my own code on the robot?
Yes — the developer interface supports custom applications for locomotion, manipulation, and perception. See X2U-05 Developer & SDK for setup. SDK access requires registration with your unit's serial number.
Q05The robot stopped mid-operation with a flashing red LED.
This indicates a protective stop — typically from a fall detection, thermal limit, or communication loss. Check the fault log in the app for the specific code, allow the unit to cool if a thermal fault is shown, and restart from the standard startup posture. Recurring faults with the same code should be reported to support.
Q06Can the robot be shipped internationally?
Yes, but lithium batteries are regulated as dangerous goods for air transport and destination countries may have their own compliance requirements (electrical safety, radio certification, customs documentation). Contact our team before arranging international shipment so paperwork and packaging are handled correctly.