What the 0x00003A alarm means

The joint failed to complete its homing or zero-calibration routine, so absolute position is not trusted. We have built up many handled cases of this JAKA Zu / JAKA Pro cobots (APP) alarm, and usually the first on-site inspection tells us what is wrong.

Most common causes

  • Joint moved during the homing routine
  • Encoder battery or memory data lost
  • Mechanical stop shifted after a crash
  • Calibration procedure not followed exactly
Field note: Confirm or rule out the first cause first — it is the situation we encounter most.

Step-by-step field fix

  1. Keep the arm still and repeat the homing routine
  2. Follow the APP calibration steps exactly per joint
  3. Check for mechanical damage if the arm was crashed
  4. Re-teach critical program points after recalibration
  5. Contact service if homing fails repeatedly on the same joint
Safety first: For JAKA 0x00003a, zero mastering usually needs brakes released to move axes onto datum - an unsupported vertical axis can drop during that move. What you can check yourself first is Keep the arm still and repeat the homing routine; axis drop once brakes are released handling is not a DIY job. On JAKA 0x00003a: backing up programs, points and tool/work frames yourself first is fine; the mastering itself needs released brakes and fixtures, so it is engineer work on site.

How we diagnose calibration alarms on site

JAKA 0x00003a belongs to the calibration & measuring board family. On JAKA 0x00003a the failing stage is dual joint encoders on the JAKA collaborative robot cabinet - measurement and calibration data: zero mastering, measuring-board acquisition, tool and work-object frames and data consistency. We start reading JAKA 0x00003a at the pendant and app alarm pages; codes are hexadecimal with a 0x prefix.

The chain involved in JAKA 0x00003a runs: measuring board acquisition -> zero / position data -> tool and work frames -> program points -> actual motion accuracy.

After re-mastering JAKA 0x00003a, success on screen is not delivery: After a fresh zero master, success on screen is not delivery - verification is mandatory. A small zero offset gets amplified by arm length into visible tool error, and the customer discovers it when points no longer land. We run repeat-positioning tests on a fixed reference after mastering, then spot-check real production points. If deviation is out of tolerance we re-examine the mastering datum itself - sometimes the fault is not the mastering run but the reference surface or fixture used during it.

Field notes on this page cover JAKA 0x00003a (Homing / Calibration Failed); written by the Henghuan repair team, updated 2026-10-01.

Can't find the cause? One call can pinpoint it

Tell us the alarm code, the model and what the machine was doing when the alarm appeared. JAKA 0x00003a is an everyday diagnosis for our engineers, and remote diagnosis (phone or video) costs nothing.

Get a Free Remote Diagnosis See Repair Services

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

Related Calibration & SMB alarms

0x000030 — Controller Temperature Too High 0x000031 — Bus Voltage Abnormal 0x000032 — Motor Overcurrent 0x000033 — Encoder Fault 0x000034 — Motor Overtemperature 0x000035 — Collision Detected
Same family: this code belongs to the Calibration & measuring board alarms family - the page collects all Calibration & measuring board-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 0x00003a alarm mean?

The joint failed to complete its homing or zero-calibration routine, so absolute position is not trusted. We have built up many handled cases of this JAKA Zu / JAKA Pro cobots (APP) alarm, and usually the first on-site inspection tells us what is wrong. JAKA 0x00003a sits in the calibration & measuring board family; on our work orders the highest-frequency trigger for this code is "Joint moved during the homing routine".

QCan I clear a JAKA 0x00003a alarm myself?

Whether JAKA 0x00003a clears on its own depends on the outcome of "Keep the arm still and repeat the homing routine". Finish the flow with "Contact service if homing fails repeatedly on the same joint" to confirm JAKA 0x00003a - do not skip it. If that step is clean, the second most frequent cause on JAKA 0x00003a is "Encoder battery or memory data lost". After clearing JAKA 0x00003a, watch it for one shift. A second trip means stop and let an engineer arrive with the right test gear for axis drop once brakes are released.

QWhen you handle JAKA 0x00003a, will my programs and frames get lost?

The commonest causes we see on JAKA 0x00003a are "Joint moved during the homing routine, Encoder battery or memory data lost, Mechanical stop shifted after a crash", so we stock the van against those. For JAKA 0x00003a specifically, we bring the brand's measuring-board type data, mastering fixtures and dial indicators; the backup matters more than the spare. For JAKA 0x00003a, on calibration alarms we back up programs and points first, master second, and verify precision before handover. Before we roll, tell us what JAKA 0x00003a 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.

This page on JAKA 0x00003a was compiled from actual repair records of the Henghuan Robotics repair team. Alarm notes are our own summary for troubleshooting reference only and may vary with controller and software version — please consult JAKA documentation or contact us if in doubt. Henghuan is an independent service provider, not affiliated with or endorsed by JAKA.