What the 0x000036 alarm means

A commanded Cartesian move demanded a joint speed above the axis limit; the controller rejects the motion. This fault ranks high in our JAKA Zu / JAKA Pro cobots (APP) service records, and the first site inspection usually finds the source.

Most common causes

  • Move passes near a wrist or elbow singularity
  • TCP speed set too high for the posture change
  • Blend radius too tight at a corner
Field note: The first cause shows up most on real machines, so verify it before you go further.

Step-by-step field fix

  1. Re-teach the path to avoid the singular posture
  2. Lower TCP speed on the failing segment
  3. Open the blend radius or add a via point
  4. Use joint-space moves for large reorientations
  5. Dry-run at low override to confirm
Safety first: For JAKA 0x000036, 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. The self-serviceable action is Re-teach the path to avoid the singular posture; anything past that falls under the arm working envelope and needs a certified engineer.

How we diagnose motion alarms on site

JAKA 0x000036 belongs to the motion & path family. On JAKA 0x000036 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 0x000036 at the pendant and app alarm pages; codes are hexadecimal with a 0x prefix.

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

First check whether JAKA 0x000036 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 0x000036 (Joint Overspeed); written by the Henghuan repair team, updated 2026-10-01.

Not sure? Don't force it — contact an engineer

Send the alarm code, the robot model and a description of what was happening at the alarm. Our engineers handle JAKA 0x000036 every day, and remote diagnosis by phone/video is free.

Get a Free Remote Diagnosis See Repair Services

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

Related Motion & Path alarms

0x000037 — Position Deviation Too Large
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 0x000036 alarm mean?

A commanded Cartesian move demanded a joint speed above the axis limit; the controller rejects the motion. This fault ranks high in our JAKA Zu / JAKA Pro cobots (APP) service records, and the first site inspection usually finds the source. JAKA 0x000036 sits in the motion & path family; on our work orders the highest-frequency trigger for this code is "Move passes near a wrist or elbow singularity".

QCan I clear a JAKA 0x000036 alarm myself?

Whether JAKA 0x000036 clears on its own depends on the outcome of "Re-teach the path to avoid the singular posture". Finish the flow with "Dry-run at low override to confirm" to confirm JAKA 0x000036 - do not skip it. If that step is clean, the second most frequent cause on JAKA 0x000036 is "TCP speed set too high for the posture change". Do not chase takt through a repeating JAKA 0x000036. Left alone, motion & path faults tend to graduate from repairable to must-replace.

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

The commonest causes we see on JAKA 0x000036 are "Move passes near a wrist or elbow singularity, TCP speed set too high for the posture change, Blend radius too tight at a corner", so we stock the van against those. For JAKA 0x000036 specifically, we carry mechanical and configuration items: grease, limit switches, drag-chain segments, encoder cables and the parameter sheets for common reducers. For JAKA 0x000036, motion alarms can often be narrowed remotely first, so an on-site visit is not always immediate. Before we roll, tell us what JAKA 0x000036 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 content on JAKA 0x000036 was written by Henghuan Robotics service engineers from hands-on repair experience. Alarm descriptions are our own reference summary and may differ by controller or software version — defer to JAKA documentation, or contact us to confirm. Henghuan is an independent service provider with no affiliation or endorsement by JAKA.