What the 30001 alarm means

The collision-detection function sensed unexpected external force and stopped the robot. Codes 3xxxx are runtime protective events. On a cobot this is a protective stop, not a damage report. We fix this AUBO i-series / C-series (ARCS SDK) fault almost daily, and one round of on-site checks usually confirms what is going on.

Most common causes

  • Contact with a person, fixture, or workpiece
  • Sensitivity set too high for the process
  • Wrong payload/tool data skewing the force model
  • Snagged external cables or hoses
Field note: We have tallied real cases: the first cause tops the list, so start your diagnosis there.

Step-by-step field fix

  1. Clear the contact and inspect for damage
  2. Verify tool weight and center of gravity
  3. Tune collision sensitivity only as the process requires
  4. Re-route external cabling
  5. Restart from a safe position
Safety first: For AUBO 30001, 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 contact and inspect 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

AUBO 30001 belongs to the safety chain & e-stop family. On AUBO 30001 the failing stage is collaborative safety (collision detection, speed limits, force and current monitoring) on the AUBO collaborative robot controller - continuity of one series loop: e-stop buttons, door switches, light curtains, safety relays and the enabling device. We start reading AUBO 30001 at the pendant alarm list and SDK / ARCS return codes; 1xxxx joint level, 2xxxx / 3xxxx safety and communication.

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

On AUBO 30001 (field clue usually Contact with a person, fixture, or workpiece) we have one hard rule: On this family we have a hard rule: no bypassing the safety loop, no forcing contactors closed, ever. Some sites jumper the door switch to keep running - that removes the entire protection function, and when something happens there is no protective action and no defensible account of responsibility. We have seen a crush injury caused by exactly that jumper, so we would rather wait for parts than do it. If a customer has already jumpered it, we restore the circuit first and then diagnose the real fault.

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

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

Send the alarm code, the robot model and a description of what was happening at the alarm. Our engineers handle AUBO 30001 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 Safety Chain & E-Stop alarms

20002 — Safety Configuration Error 30002 — Emergency Stop Active
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 ROKAE · Dobot · FANUC and more — see the complete alarm code hub.

Frequently asked questions

QWhat does the AUBO 30001 alarm mean?

The collision-detection function sensed unexpected external force and stopped the robot. Codes 3xxxx are runtime protective events. On a cobot this is a protective stop, not a damage report. We fix this AUBO i-series / C-series (ARCS SDK) fault almost daily, and one round of on-site checks usually confirms what is going on. AUBO 30001 sits in the safety chain & e-stop family; on our work orders the highest-frequency trigger for this code is "Contact with a person, fixture, or workpiece".

QCan I clear a AUBO 30001 alarm myself?

Whether AUBO 30001 clears on its own depends on the outcome of "Clear the contact and inspect for damage". Finish the flow with "Restart from a safe position" to confirm AUBO 30001 - do not skip it. If that step is clean, the second most frequent cause on AUBO 30001 is "Sensitivity set too high for the process". After clearing AUBO 30001, watch it for one shift. A second trip means stop and let an engineer arrive with the right test gear for the e-stop chain and safety circuit.

QA safety-chain fault like AUBO 30001 stops the line - how fast can you be here?

The commonest causes we see on AUBO 30001 are "Contact with a person, fixture, or workpiece, Sensitivity set too high for the process, Wrong payload/tool data skewing the force model", so we stock the van against those. For AUBO 30001 specifically, we stock along the loop: safety relays, common door switches, e-stop buttons, light-curtain pairs and terminal blocks. For AUBO 30001, 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 AUBO 30001 shows on the pendant alarm list and SDK / ARCS return codes; 1xxxx joint level, 2xxxx / 3xxxx safety and communication and what the machine was doing - phone or video triage is free.

The notes on AUBO 30001 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 AUBO documentation or contact us with questions. Henghuan is an independent service provider, not affiliated with or endorsed by AUBO.