AGIBOT G2 · Wheeled Humanoid

Onboard intelligence, fully documented.

Best for industrial warehouse work — high-precision swerve-drive wheels that favor stability wherever stairs aren't involved, a folding torso for extended reach, and arms built for high-precision, force-feedback manipulation.

1225–1795 mm / 185 kgHeight (folding torso) & weight
26 DOFNeck, waist, arms, chassis
Hot-swap battery1652 Wh · ≈4h endurance
2× Mid-360 LiDAR+ stereo, 3× fisheye & RGBD cams
5 kg per armRated payload, torque-sensed
2 onboard compute boards500 & 2070 TOPS/TFLOPS-class
4-wheel swerve driveAckermann, lateral & in-place rotation
Loading 3D model…
  · genie_robot · simplified for browser
Wheeled
Platform
26
Driven Joints
ROS 2 Kilted
Middleware
IP42
Protection
AGIBOT
Manufacturer
Startup Guide

From power-on to the browser cockpit

G2 is wheeled, not bipedal — there's no crane-supported standing-up sequence like the legged platforms. Power on, then choose how to operate it.

01

Power on

Press the Power Button on the robot's back. Two hot-swappable batteries carry it independently of mains power; the 7 torso light indicators flow while booting and settle to a steady theme-colour white once ready (≈1 min). The Emergency Stop button next to it cuts joint power immediately and independently of software, whichever control path you're using.

Step 02 — choose how to operate
02A
AGIBOT native · no Illeon software

Wireless Terminal & App

Pair the handheld wireless terminal or the mobile app over the same network as the robot for locomotion, the built-in voice/expression interaction system, and factory-level diagnostics — entirely on AGIBOT's own stack.

Manufacturer appVoice & expressions
02B
Illeon layer

Webserver

Browse to the robot's IP at port 9000 once it's on your network. The full ROS 2 stack — webserver, joint bridge, dual-LiDAR bridge, arm-IK and chassis bridge — is installed as systemd units and comes up on its own at boot, the same "just power on and browse" experience as the rest of the fleet.

ROS 2 KiltedBrowser cockpitAutostarts on boot
Then, either way
03

Power off / E-stop

Normal shutdown via the Power On/Off button. Soft E-Stop is available from software for a faster, remote-triggerable stop; the physical Hard E-Stop button cuts joint power directly and is the more reliable of the two — use it whenever in doubt.

Full procedure and safety warnings: AGIBOT G2 User Manual.

Why Illeon

The same ROS 2 + webserver layer as the rest of the fleet

Illeon is AGIBOT's German distributor. G2 runs a port of the same webserver software stack as the A2 Ultra and X2, adapted for a wheeled humanoid with its own native gdk_msgs ROS 2 interface — one contract, one point of contact, no separate SDK integration to figure out yourself.

Movement & Chassis Drive

Dual Drive / Strafe joysticks over the 4-wheel swerve chassis — Ackermann steering, lateral movement and in-place rotation. Two independent safety gates (a transfer-enable switch and a latched E-Stop, checked on every command) have to agree before anything reaches the wheels.

webserver/cmd_velg2-chassis-bridgeE-Stop latched

Joint & Arm Control

22 driven joints — 5-DOF waist, 3-DOF head and dual 7-DOF arms — addressable directly or through Cartesian IK over the onboard websocket. Three real hardware control modes: joint position, Cartesian impedance, and joint impedance for compliant, drag-teachable motion.

g2-arm-ikIK :9001Impedance modes

3D LiDAR & Live View

Both onboard Mid-360 LiDARs are merged into a single live point cloud in the robot's own base_link frame and streamed into the same 3D view as the URDF model — the model itself tracks the robot's real joint state in real time, not a static pose.

g2-platform/gdk/lidar/pointsLive /joint_states

Diagnostics & Monitoring

Every ROS 2 module the platform depends on runs as its own systemd unit with a live status readout in the Robot Modules page, alongside per-joint position/velocity/effort telemetry.

systemdRobot ModulesJoint telemetry

Engineering & Custom Hardware

Need an end-effector, sensor, or capability the robot doesn't ship with? Our engineering team integrates custom hardware directly into the platform — mechanically, electrically, and in the ROS 2 stack.

Custom grippersSensor integrationMechanical + ROS 2

Camera streaming, SLAM/navigation and voice/AI chat are still being brought up on this platform — get in touch for the current status on any of them.

Resources

Manuals, robot description & compliance

Everything needed to operate the G2 safely or bring its model into your own tooling. The SDK package below is AGIBOT-confidential and shared under NDA — click it to sign in or request access.

AGIBOT G2 User Manual

PDF · AGIBOT Innovation (Shanghai) · v0.22

The manufacturer's own G2 manual: precautions & safety, hardware overview, power on/off, E-Stop, teleoperation connection, wireless terminal & app, and maintenance-bay interfaces — straight from AGIBOT.

Download PDF

G2 Robot Description (URDF)

genie_robot ROS 2 package

Two variants: simplified is exactly the decimated, recolored URDF + meshes the viewer above renders (~7 MB). Full is AGIBOT's own unmodified genie_robot package — URDF, full-resolution visual & collision meshes, RViz config and package.xml (~43 MB). Note: the chassis base body ships with no visual mesh in AGIBOT's own file — wheels, arms, head and waist are all present.

Certificates

CE, radio equipment & battery cell (UL2580 / IEC 62133-2) certification

CE Declaration of Conformity, Radio Equipment examination certificate, Service Robot certificate, and UL2580 / IEC 62133-2 lithium-ion battery cell test reports & certificates of compliance.

Download certificates (.zip)

G2 Confidential SDK Package

AGIBOT GDK Development Manual, SDK reference (v2.1.0) & force-control preview · NDA required

Shared with named customers under NDA only. Click download to sign in if you already have portal access, or request it — we'll review and follow up.

Already have portal access to something else? Sign in directly.

Support

If something goes wrong

Three tiers, in order — we start at the fastest and only escalate as far as the problem actually requires.

1
Customer-activated

Remote access via VPN

Most issues get diagnosed and fixed without anyone leaving their desk — but only once you switch it on. The robot's VPN link back to us is off by default; we have no standing access to a customer's robot, and it's activated on your side to stay clear of data-protection obligations. Once enabled, we connect in over VPN — or through a client device on-site if the robot itself can't reach us — and debug it directly.

2

Recovery box

If the robot's own networking is the problem, we ship a preconfigured recovery box to site. Plug it in and it opens a tunnel back to us — the same remote access as Tier 1, without needing IT support on your end.

3

Depot repair in Germany

For hardware damage or anything that needs hands-on work, send the unit back to us. Repairs happen in-house in Germany for a fast turnaround — no routing through the manufacturer.

Not sure which tier fits? Just reach out — support@illeon.de — and we'll triage it.

Need a hand?

We're here for the whole deployment

Fleet rollout, a new use case, or a question about a specific webserver module — the Illeon team can help.

support@illeon.de