Running an industrial wheeled humanoid robot on a material pickup run: how to keep logs

Last week a client asked me whether a wheeled humanoid robot could go into the workshop to pick and deliver materials. My first reaction wasn't about how fast it could carry things — it was whether, after carrying them, it could explain clearly why it took that route and why it grabbed that box. I spent a few years in AI underwriting, and explainability and regulatory considerations are just as unavoidable in hardware execution.

This Humanoid industrial wheeled humanoid robot, used for fixed-route bin transfer, is workable; but don't expect it to do flexible grasping on day one. The wheeled chassis is very stable, and the end-effector payload I measured is on the order of 15 kg, covering most small-part bins in a workshop. I hear the company raised a $152 million Series A and has orders for a thousand units on hand, which shows people really are putting money into trying industrial scenarios.

Below is my complete process from power-on to exporting an execution log. Newbies can follow along.

First, understand its four-layer brain. Humanoid describes its robot intelligence stack as four layers, from System 3 down to System 0. System 0 handles joints and motors, System 1 handles how the wheels move, System 2 handles how this one robot completes tasks, and System 3 sits on top, like a foreman, taking jobs from the client's warehouse system and distributing them to the robots below. Normally the only thing you operate is System 3 — you don't touch the three layers underneath.

Step one, power on and connect to the network.

1. Long-press the power button on the side of the chassis for three seconds; the indicator goes from red to green.

2. Open the scheduling app on the tablet and log in with an admin account. The first time you go in, an empty list pops up saying "No bound devices."

3. Enter the number on the body and tap Bind. The robot appears in the list with status Standby.

Expected result: both arms retract, the wheels do a slight self-check once, and the screen shows Standby.

Step two, create a task.

1. Tap New Task, select type Bin Transfer.

2. Enter start point A03 Loading Position, end point B11 Assembly Station. These two names must be marked on the workshop map first; if they aren't, the dropdown list will be empty.

3. Save. The task enters the queue with status Pending Dispatch.

Step three, teach the route.

The wheeled chassis can't handle stairs, and it can't handle thresholds either. The first time I ran it, it got stuck on a cable tray — the robot stopped in place, probing back and forth repeatedly, and the log filled with a string of obstacle-avoidance records.

1. Tap Teach, push the robot through the path you want it to take.

2. Press Mark Point once at each turn.

3. When done, tap Close Route. The system replays it once; if it can get through, save it.

Step four, do a test run.

Tap Dispatch. The robot starts from the standby position, stops steadily at A03, the arm reaches down, grips the bin, lifts to a safe height, follows the route to B11, and sets it down. The whole process takes two or three minutes depending on route length.

Step five, export the log.

This step is the easiest to skip. Tap Task Records, select the one you just ran, and tap Export. You'll get a file with timestamps recording when the task was received, when it reached the start point, when the gripper closed, how many times it avoided obstacles, and when it finished. This is what auditors look at.

The pitfalls are mainly in these three places.

Pitfall	Symptom	How to fix
Bump in the floor	Stops in place, probing repeatedly	Route around cable trays and thresholds
Payload exceeded	Grips then drops it, throws an error	Keep single items under 15 kg
Broken log chain	Timestamps don't match, auditors won't accept it	Sync the system time once before running

One more thing: after dispatching a task, you need to see the Complete receipt — don't just walk away when you see "Dispatched." If it breaks in the middle, the log is broken.

Hang two robots under the same System 3 and you can see how the foreman distributes work. Wire the exported logs into your own risk-control or audit system and you can do automated comparison.