What the 0x000035 alarm means

The collision-detection function sensed an unexpected external force and stopped the robot. On a cobot this is a protective stop, not a fault — but repeated events mean something is in the path. Our engineers run into this alarm every week on JAKA Zu / JAKA Pro cobots (APP) controllers, and a single on-site inspection usually identifies the problem.

Most common causes

  • Robot arm contacted a person, fixture, or workpiece
  • Sensitivity set too high for the process (false triggers)
  • Payload or tool data wrong, skewing the force model
  • Cable or hose snagging on the cell
Field note: In our repair stats the first cause has the highest hit rate, so confirm it first before digging further.

Step-by-step field fix

  1. Clear the obstruction and check for damage
  2. Verify tool weight and center of gravity in the APP
  3. Adjust collision sensitivity only if the process requires it — never defeat it
  4. Re-route external cables so they cannot snag
  5. Restart the program from a safe position
Safety first: For JAKA 0x000035, this alarm is the safety circuit itself: jumpering a door switch or forcing a contactor removes the protection entirely - no protective action when something happens, and no defensible account of responsibility. The self-serviceable action is Clear the obstruction and check for damage; anything past that falls under the e-stop chain and safety circuit and needs a certified engineer.

How we diagnose safety-chain faults on site

JAKA 0x000035 belongs to the safety chain & e-stop family. On JAKA 0x000035 the failing stage is collaborative safety (collision detection, safe limits, force control) on the JAKA collaborative robot cabinet - continuity of one series loop: e-stop buttons, door switches, light curtains, safety relays and the enabling device. We start reading JAKA 0x000035 at the pendant and app alarm pages; codes are hexadecimal with a 0x prefix.

The chain involved in JAKA 0x000035 runs: e-stop / door / curtain -> safety relay (dual channel) -> controller safety input -> motor-off and brake apply.

On JAKA 0x000035 the field usually reports Robot arm contacted a person, fixture, or workpiece, but the check that matters is not continuity: The point of a safety loop is not whether it conducts but whether both channels conduct together. The relay compares channels; if one opens tens of milliseconds early it latches as a channel fault. The commonest causes are plain: oxidised door-switch contacts raising contact resistance, or one loose terminal. We measure segment by segment - pendant e-stop, panel e-stop, external e-stop, safety door - and lock onto whichever segment reads differently on the two channels.

Field notes on this page cover JAKA 0x000035 (Collision Detected); written by the Henghuan repair team, updated 2026-10-01.

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

Share the alarm code, machine model and the operating condition at the moment of the alarm. Our engineers are highly experienced with JAKA 0x000035, and remote diagnosis (phone/video) is completely free.

Get a Free Remote Diagnosis See Repair Services

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

Related Safety Chain & E-Stop alarms

0x0F0102 — Emergency Stop Active 0x0F0103 — Safety I/O Configuration Error
Same family: this code belongs to the Safety chain & e-stop alarms family - the page collects all Safety chain & e-stop-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 0x000035 alarm mean?

The collision-detection function sensed an unexpected external force and stopped the robot. On a cobot this is a protective stop, not a fault — but repeated events mean something is in the path. Our engineers run into this alarm every week on JAKA Zu / JAKA Pro cobots (APP) controllers, and a single on-site inspection usually identifies the problem. JAKA 0x000035 sits in the safety chain & e-stop family; on our work orders the highest-frequency trigger for this code is "Robot arm contacted a person, fixture, or workpiece".

QCan I clear a JAKA 0x000035 alarm myself?

Whether JAKA 0x000035 clears on its own depends on the outcome of "Clear the obstruction and check for damage". Finish the flow with "Restart the program from a safe position" to confirm JAKA 0x000035 - do not skip it. If that step is clean, the second most frequent cause on JAKA 0x000035 is "Sensitivity set too high for the process (false triggers)". Two attempts and still there means stop: JAKA 0x000035 involves the e-stop chain and safety circuit, and running JAKA 0x000035 on can turn a repairable fault into a replacement.

QA safety-chain fault like JAKA 0x000035 stops the line - how fast can you be here?

The commonest causes we see on JAKA 0x000035 are "Robot arm contacted a person, fixture, or workpiece, Sensitivity set too high for the process (false triggers), Payload or tool data wrong, skewing the force model", so we stock the van against those. For JAKA 0x000035 specifically, we stock along the loop: safety relays, common door switches, e-stop buttons, light-curtain pairs and terminal blocks. For JAKA 0x000035, a safety-chain fault stops the whole line, so we rank it top priority and pre-triage by phone: door switch, e-stop or relay. Before we roll, tell us what JAKA 0x000035 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 0x000035 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 JAKA documentation or contact us. Henghuan is an independent service provider, not affiliated with or endorsed by JAKA.