What the 0x000037 alarm means

The difference between commanded and actual joint position exceeded the limit; the controller stops to protect mechanics and product. This is a routine repair in our workshop for JAKA Zu / JAKA Pro cobots (APP) systems, and we normally pin it down during the first site check.

Most common causes

  • Obstruction or collision in the path
  • Payload above rating
  • Joint brake dragging
  • Encoder feedback intermittent
Field note: Begin with the first item in the list; it has a far higher on-machine occurrence rate than the others.

Step-by-step field fix

  1. Clear the path and inspect for damage
  2. Correct the payload data
  3. Check the joint brake release
  4. Watch the deviation value in diagnostics during a slow jog
  5. Recalibrate the joint after the cause is fixed
Safety first: For JAKA 0x000037, 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 Clear the path and inspect for damage; the arm working envelope handling is not a DIY job.

How we diagnose motion alarms on site

JAKA 0x000037 belongs to the motion & path family. On JAKA 0x000037 the failing stage is joint-integrated drive modules on the JAKA collaborative robot cabinet - the gap between command and execution: trajectory planning, joint limits, singularities, following error and mechanical resistance. We start reading JAKA 0x000037 at the pendant and app alarm pages; codes are hexadecimal with a 0x prefix.

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

First check whether JAKA 0x000037 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 JAKA 0x000037 (Position Deviation Too Large); written by the Henghuan repair team, updated 2026-10-01.

If you can't fix it, reach our engineers directly

Give us the alarm code, robot model and the action at the moment of the alarm, and our engineers can give you a quick read — phone or 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

0x000036 — Joint 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 AUBO · ROKAE · Dobot and more — see the complete alarm code hub.

Frequently asked questions

QWhat does the JAKA 0x000037 alarm mean?

The difference between commanded and actual joint position exceeded the limit; the controller stops to protect mechanics and product. This is a routine repair in our workshop for JAKA Zu / JAKA Pro cobots (APP) systems, and we normally pin it down during the first site check. JAKA 0x000037 sits in the motion & path family; on our work orders the highest-frequency trigger for this code is "Obstruction or collision in the path".

QCan I clear a JAKA 0x000037 alarm myself?

Whether JAKA 0x000037 clears on its own depends on the outcome of "Clear the path and inspect for damage". Finish the flow with "Recalibrate the joint after the cause is fixed" to confirm JAKA 0x000037 - do not skip it. If that step is clean, the second most frequent cause on JAKA 0x000037 is "Payload above rating". If JAKA 0x000037 returns after two clears, or the checks point at Obstruction or collision in the path, stop the cell and call a professional robot repair engineer.

QFor motion alarms like JAKA 0x000037, can you triage remotely first?

The commonest causes we see on JAKA 0x000037 are "Obstruction or collision in the path, Payload above rating, Joint brake dragging", so we stock the van against those. For JAKA 0x000037 specifically, we carry mechanical and configuration items: grease, limit switches, drag-chain segments, encoder cables and the parameter sheets for common reducers. For JAKA 0x000037, motion alarms can often be narrowed remotely first, so an on-site visit is not always immediate. Before we roll, tell us what JAKA 0x000037 shows on the pendant and app alarm pages; codes are hexadecimal with a 0x prefix and what the machine was doing - phone or video triage is free.

The notes on JAKA 0x000037 were summarized by the Henghuan Robotics repair team from on-site service. The alarm interpretation is our empirical summary for troubleshooting reference and may vary by controller and software version — please check JAKA documentation or contact us with questions. Henghuan is an independent service provider, not affiliated with or endorsed by JAKA.