Unitree Go2 Repair: Joints, Battery & Calibration

Unitree Go2 quadruped diagnosis

Unitree Go2 is a quadruped robot, not a DJI drone. Its four product variants, 12 joint actuators, battery and charger, posture control, App and OTA state, camera and LiDAR options require a robot-specific intake. This guide removes the old drone template and unsupported repair prices. It begins with the customer's concern, keeps the robot safely supported, and turns observed behavior into known and unknown findings before repair, calibration or replacement is approved.

Quick answer

Support the robot, identify the exact variant, and separate joint, posture, power and software evidence

Record the exact Unitree Go2 AIR, PRO, X or EDU configuration, battery, charger, controller, App/firmware state, installed computing and sensor options, event and precise symptom. Keep the robot powered down and mechanically supported when a joint, leg, battery or structure may be unsafe. Exact chip, actuator-board or price findings can be published when the exact model, board revision and case-level evidence support them; no drone ESC, gimbal or DJI battery template belongs in this diagnosis.

What evidence should be captured before the customer acts?

Evidence layer	What to record	Why it changes the decision
Exact configuration	Go2 variant, serial, battery, charger, controller, App, firmware and installed options	Prevents AIR, PRO, X and EDU capabilities being mixed
Event and posture	Fall, collision, load, surface, command, gait, affected leg and first warning	Separates mechanical loading from software or sensor behavior
Joint evidence	Standing geometry, joint sound, heat, resistance, repeatability and safe unloaded behavior	Keeps actuator, linkage, structure and control branches distinct
Power and data	Battery indicators, charger, runtime change, App connection, OTA history, logs and sensor view	Separates supply, communication, firmware and perception layers
Decision record	Known and unknown findings, exact board revision, parts provenance and acceptance plan	Lets the customer approve a defined robot repair rather than a guessed module

How does repair-bench experience map the fault domains?

Bench domain	What the experience establishes	Responsible use
Structure and joints	Feet, links, fasteners, covers, 12 joint actuators, alignment and load history	The robot is supported before movement is requested
Posture and motion	Standing, crouching, gait, calibration state, affected axis and controlled comparison	Calibration is not used to hide mechanical damage
Power	Battery, charger, contacts, temperature, startup and shutdown behavior	A no-start symptom does not identify a battery or controller board alone
App, OTA and perception	Connection, firmware history, camera or LiDAR view, warnings and option set	Variant, software and physical sensor evidence remain separate
Acceptance	Power, thermal stability, joint motion, posture, control, perception and low-risk walking	The customer's complete robot workflow is demonstrated progressively

Why must the exact Unitree Go2 variant be identified first?

Go2 is sold in AIR, PRO, X and EDU configurations with differences in control, computing, sensing and accessories. Photograph the serial and variant, battery, charger, controller, installed camera or LiDAR, computing module and any added payload. Record the App-reported device and firmware state. A feature shown on one configuration is not automatically present on another, and a repair quote must not assume the highest-spec hardware.

Official Unitree product and App material establishes the supported configuration and user-visible operations. Internal conclusions require the observed robot. Reboot Hub records the exact board revision when an approved diagnosis reaches it and may publish a chip, actuator-board or case price when the exact model and case-level evidence travel with that conclusion. Known and unknown findings remain separate so the customer can see what has actually been proved.

Unitree Go2 quadruped robot variant battery charger controller and serial documented at repair intake — Preserve the exact kit, condition and event history before a part-level conclusion is proposed.

What should happen when a Go2 leg or joint behaves abnormally?

Stop dynamic movement and support the robot so it cannot fall or unexpectedly load a person. Record the affected leg and joint, command, surface, payload, sound, temperature, visible alignment and whether the behavior began after a fall or collision. Compare left and right geometry without forcing a resistant joint. Do not continue walking tests when a link, foot, fastener, cover or actuator may be damaged.

A joint symptom can involve structure, fasteners, linkage, actuator, encoder, local electronics, cabling, posture state or command. The diagnosis moves from safe external evidence to an approved unloaded comparison and only then to deeper inspection. It does not call every sound a motor failure or use calibration to mask mechanical binding. Parts provenance and the relevant revision belong in writing before replacement or board work.

When is calibration appropriate, and when should it stop?

Unitree provides supported calibration through its Go2 App and tutorials. Calibration belongs after exact configuration, safe structure, battery condition and a reproducible posture symptom are established. Record the starting stance, surface, App version, firmware, warning and result. Use a clear area with the robot supported according to the official procedure, and stop if a joint binds, overheats, moves unexpectedly or cannot hold a safe posture.

A successful calibration can resolve a state or reference issue; it cannot repair cracked structure, worn gearing, damaged bearings, wiring or an actuator fault. A failed calibration is evidence, not a component diagnosis. Reboot Hub states whether the process completed, what changed and what remains unknown. That protects the customer from repeated calibration attempts that create more motion on a mechanically unsafe robot.

Unitree Go2 quadruped robot feet links covers and 12 joint actuators inspected while safely supported — Camera and gimbal evidence must stay attached to the exact model and optical path.

How should startup, battery and charging problems be separated?

Record the exact battery and charger, indicators, storage history, temperature, contacts, physical condition and the sequence during startup or charging. Keep swelling, leakage, impact, unusual heat and odor as immediate stop-use evidence. A known-good supported comparison may bound the charger, battery or robot-side path only when it can be performed safely.

A no-start or early shutdown can involve the battery, charger, contacts, power distribution, controller or software state. The customer receives the observed layer and remaining unknowns rather than a fixed module price. Exact cells, chips or boards are named only from the exact Go2 configuration, board revision and case-level evidence. Battery opening, improvised charging and unauthorized protection changes do not belong in a public guide.

What do App, controller or OTA problems actually prove?

Record the App version, account and region context where relevant, controller type, connection method, firmware versions, OTA timing, network environment, warnings and whether local posture control still functions. A missing video or LiDAR view, failed update and complete robot disconnect are different symptoms. Preserve logs and screenshots before resets or further updates.

The diagnosis separates phone or network, controller, robot communication, firmware and physical sensor paths. Supported update and reset actions are considered only after the battery and structure are safe. Reboot Hub does not use unauthorized firmware or region workarounds. The written finding explains which supported configuration reproduced the issue and what could not be verified.

Unitree Go2 quadruped robot App OTA posture LiDAR camera and power evidence reviewed separately — System evidence separates power, sensing, link and propulsion before a scope is approved.

How should LiDAR, camera and obstacle behavior be diagnosed?

Identify the installed sensor options and variant before expecting a feature. Inspect accessible windows for dirt, scratches, moisture and impact. Record the App view, lighting, obstacle geometry, surface, movement mode and exact warning. Camera or LiDAR data loss can belong to the sensor, connection, computing option, power, firmware or App path, and those layers require separate evidence.

Do not aim the robot into a risky obstacle merely to reproduce a complaint. Begin stationary, then use a controlled low-risk area only after structure and posture gates pass. A repaired or calibrated sensor is not a guarantee of autonomous safety. Acceptance describes the tested environment and observed result, while the customer retains supervision and mission responsibility.

When is Go2 repair more responsible than replacement?

Repair is stronger when the affected joint, power, control or perception domain can be bounded, compatible parts provenance is available and staged tests can prove the intended use. Replacement or a broader module path becomes more credible when structural damage crosses several legs, liquid or heat exposure is broad, the exact configuration cannot be restored, or safe acceptance cannot demonstrate the required behavior.

Reboot Hub starts from the customer's perspective: intended work, deadline, payload, environment, data or development needs, and every concern that must be removed. We document the exact robot, included equipment, condition, known and unknown findings, written terms and acceptance evidence. The product path is an exact documented Unitree option, not an unrelated drone collection.

Unitree Go2 quadruped robot staged for joint posture control perception and low-risk walking acceptance — Return-to-service evidence advances from safe observations to controlled operational acceptance.

What must a Unitree Go2 quote and acceptance prove?

The quote names the exact Go2 variant and options, observed event, relevant board revision where established, parts provenance, approved scope, timing and stop conditions. The normal workshop target is 1-3 business days after quote approval, subject to scope, parts and testing. Approved work has a 30-day repair warranty; a qualifying complete product follows the separate 180-day product warranty.

Acceptance advances from power and thermal stability to supported posture, each affected joint, controlled gait, App/controller communication, camera or LiDAR evidence and the customer's required low-risk workflow. The handover records completed tests and remaining observations. It proves a defined result for the exact robot instead of promising every terrain, payload or autonomous behavior.