Unitree Support

Unitree Support: Help for Quadruped and Humanoid Platforms

Unitree platforms, including the Go series quadrupeds, the B series industrial quadrupeds, and the G and H series humanoids, are widely used by developers, universities, integrators, and enterprise teams. This support section gathers practical resources for owners and operators of these machines: setup walkthroughs, firmware and app guidance, battery and charging advice, controller pairing help, and structured troubleshooting references.

The aim is to help you resolve common questions quickly and to prepare better support requests when an issue needs direct assistance. Most operational problems with these platforms trace back to a small set of causes, such as battery state, firmware mismatches, network configuration, or controller binding, and the resources here are organized around exactly those areas.

Topics Covered in This Section

• Initial setup: Unboxing checks, battery installation and first charge, app installation, and first power-on sequences.
• Controllers and connectivity: Pairing handheld controllers, connecting over Wi-Fi, and understanding the platform's network modes.
• Firmware and software: Recommended update practices, app version alignment, and what to verify before and after updates.
• Batteries and charging: Charging routines, storage recommendations, and signs that a battery pack needs attention.
• Developer resources: Pointers for SDK access, joint control, perception interfaces, and simulation workflows on supported models.
• Troubleshooting: Step-by-step checks for startup failures, connection drops, unexpected posture behavior, and error indications.

Good Practices for Unitree Owners

A few habits keep these platforms reliable. Charge and store batteries according to the recommended procedures, and avoid leaving packs fully depleted for long periods. Keep the robot firmware and the companion app in compatible versions, updating both in the recommended order. Operate within the environmental limits described for your model, particularly regarding surfaces, moisture, and temperature. Before developer experimentation, confirm the robot behaves normally in standard mode so that software issues can be separated from hardware ones. Finally, record firmware versions and recent changes; this history is the single most useful input when troubleshooting.

When to Contact Support

If a guide does not resolve your issue, prepare a short report before reaching out: the model and serial details, firmware and app versions, battery state, a description of the behavior, and any recent changes such as updates or added payloads. Photos or short videos of the behavior are often decisive. Submitting this information with your inquiry through the site allows the support process to start with diagnosis rather than data collection.

Pricing and Availability

Support content in this section is informational. Where an issue leads to a purchase, such as replacement batteries, chargers, controllers, spare parts, or accessories for a Unitree platform, pricing is provided on a request-for-quote basis. Send an inquiry through the relevant product page with your model details, and a specialist can confirm compatibility, availability, and a tailored quotation.

Frequently Asked Questions

My robot will not power on. What should I check first?

Verify the battery is charged and fully seated, confirm the charger works with another outlet, and follow the documented power-on sequence for your model. Battery state is the most common cause of startup issues.

How should I handle firmware updates?

Update with a well-charged battery, a stable connection, and matching app versions, following the documented order for your model. Avoid interrupting an update in progress, and verify basic operation afterward.

Can I add third-party payloads or sensors?

Many models expose mounting points and interfaces for payloads. Check the mass limits and interface specifications for your specific platform, and introduce additions one at a time to simplify troubleshooting.

What details make a support request faster to resolve?

Model and serial information, firmware and app versions, a clear description of symptoms, recent changes, and a short video of the behavior. Complete reports typically cut resolution time significantly.