What the 0x31 alarm means

Joint 2 speed exceeded the motor maximum during Cartesian motion; the controller trips to protect the axis. This fault ranks high in our Dobot Magician / MG400 / M1 / CR (DobotStudio) service records, and the first site inspection usually finds the source.

Most common causes

  • TCP speed too high for the posture, over-driving joint 2
  • Path near a singularity that spins joint 2
  • Aggressive acceleration on vertical moves
  • Override left high from an earlier program section
Field note: The first cause shows up most on real machines, so verify it before you go further.

Step-by-step field fix

  1. Reduce the Cartesian speed on the failing segment
  2. Re-plan the path to avoid the near-singular posture
  3. Soften acceleration on vertical moves
  4. Verify the override value
  5. Clear the alarm in DobotStudio and re-run slowly
Safety first: For Dobot 0x31, this alarm family points at arm motion control: after a reset the arm can move unexpectedly, and anyone inside the working envelope is at strike and pinch risk. What you can check yourself first is Reduce the Cartesian speed on the failing segment; the arm working envelope handling is not a DIY job.

How we diagnose motion alarms on site

Dobot 0x31 belongs to the motion & path family. On Dobot 0x31 the failing stage is joint-integrated drive modules (collaborative models dominate) on the Dobot controllers (CR / MG / Nova series companions) - the gap between command and execution: trajectory planning, joint limits, singularities, following error and mechanical resistance. We start reading Dobot 0x31 at DobotStudio / app alarm messages; error codes are hexadecimal with a 0x prefix.

The chain involved in Dobot 0x31 runs: program command -> trajectory planner -> joint targets -> servo execution -> actual position feedback -> deviation compare.

First check whether Dobot 0x31 only appears at one pose - A six-axis arm near wrist extension or near axis-5 zero has a Jacobian approaching singularity: tiny tool moves demand huge joint rates, and the controller either reports following error or the arm snaps through. When the report is alarms at one position and clean on another path, suspect the singular region first. The fix is not raising speed limits but routing around it: move the part, add an intermediate point, or pass the region in joint interpolation.

Field notes on this page cover Dobot 0x31 (Joint 2 Overspeed); written by the Henghuan repair team, updated 2026-10-01.

No luck? Hand it to the team that fixes this daily

Tell us these three: alarm code, robot model, and the operating condition at the alarm. Dobot 0x31 is a diagnosis our engineers do daily, and phone/video remote diagnosis is free.

Get a Free Remote Diagnosis See Repair Services

Hotline: +86-20-39029800 · WhatsApp: +86-188-1886-2860

Related Motion & Path alarms

0x20 — Inverse Kinematics Singularity 0x21 — Inverse Kinematics No Solution — Out of Workspace 0x22 — Inverse Kinematics Over Joint Limit 0x30 — Joint 1 Overspeed 0x32 — Joint 3 Overspeed 0x33 — Joint 4 Overspeed
Same family: this code belongs to the Motion & path alarms family - the page collects all Motion & path-family codes we have handled, with the common inspection order and spares.
Other brands: we also keep field-fix libraries for FANUC · KUKA · ABB and more — see the complete alarm code hub.

Frequently asked questions

QWhat does the Dobot 0x31 alarm mean?

Joint 2 speed exceeded the motor maximum during Cartesian motion; the controller trips to protect the axis. This fault ranks high in our Dobot Magician / MG400 / M1 / CR (DobotStudio) service records, and the first site inspection usually finds the source. Dobot 0x31 sits in the motion & path family; on our work orders the highest-frequency trigger for this code is "TCP speed too high for the posture, over-driving joint 2".

QCan I clear a Dobot 0x31 alarm myself?

Whether Dobot 0x31 clears on its own depends on the outcome of "Reduce the Cartesian speed on the failing segment". Finish the flow with "Clear the alarm in DobotStudio and re-run slowly" to confirm Dobot 0x31 - do not skip it. If that step is clean, the second most frequent cause on Dobot 0x31 is "Path near a singularity that spins joint 2". When Dobot 0x31 keeps coming back it is not a one-off trigger - especially if Clear the alarm in DobotStudio and re-run slowly is where you get stuck. Do not keep producing through Dobot 0x31.

QFor motion alarms like Dobot 0x31, can you triage remotely first?

The commonest causes we see on Dobot 0x31 are "TCP speed too high for the posture, over-driving joint 2, Path near a singularity that spins joint 2, Aggressive acceleration on vertical moves", so we stock the van against those. For Dobot 0x31 specifically, we carry mechanical and configuration items: grease, limit switches, drag-chain segments, encoder cables and the parameter sheets for common reducers. For Dobot 0x31, motion alarms can often be narrowed remotely first, so an on-site visit is not always immediate. Before we roll, tell us what Dobot 0x31 shows on DobotStudio / app alarm messages; error codes are hexadecimal with a 0x prefix and what the machine was doing - phone or video triage is free.

This page on Dobot 0x31 was written by the Henghuan Robotics repair team from field service experience. Alarm descriptions are our own summary for troubleshooting reference and may vary by controller and software version — when in doubt, check your Dobot documentation or contact us. Henghuan is an independent service provider, not affiliated with or endorsed by Dobot.