What the 60001 alarm means

The running robot program hit an execution error — invalid instruction argument, missing point, or failed subroutine. Codes 6xxxx are program/task-level events. We fix this ROKAE xCore (XB / CR / NB series) fault almost daily, and one round of on-site checks usually confirms what is going on.

Most common causes

  • Taught point deleted but still referenced
  • Variable out of range for the instruction
  • Subroutine missing or renamed
  • I/O wait with no timeout
Field note: We have tallied real cases: the first cause tops the list, so start your diagnosis there.

Step-by-step field fix

  1. Note the line number shown with the error
  2. Fix the referenced point, variable, or call
  3. Add timeouts to I/O waits
  4. Single-step through the failing section
  5. Regression-test the program at low speed
Safety first: For ROKAE 60001, the risk on this family is not injury but data: lose the program, parameters and calibration data and weeks of teaching work start over. The self-serviceable action is Note the line number shown with the error; anything past that falls under program and calibration data and needs a certified engineer.

How we diagnose system alarms on site

ROKAE 60001 belongs to the system & program family. On ROKAE 60001 the failing stage is xCore controller software / ROKAE SDK (ROKAE xCore controller) on the ROKAE xCore controller - the software layer: corrupted program or parameter files, boot failures, version mismatch, memory and storage media. We start reading ROKAE 60001 at the pendant alarm list; codes segment as 1xxxx / 5xxxx / 6xxxx.

The chain involved in ROKAE 60001 runs: storage media (CF / flash / disk) -> system software and firmware -> parameters and calibration data -> user programs -> runtime.

If ROKAE 60001 comes with slower boots, think media: The CF card, flash or disk inside a controller has a finite life, and heavy log writing shortens it. Ageing media usually announces itself in stages: occasional read/write errors, then slow boots, then a failure to boot at all. The nasty part is that the data may already be damaged. We bring the system up from recovery media first, then salvage user programs and parameters; everything salvaged is stored in two copies, and we set the customer up with a standing backup habit afterwards.

Field notes on this page cover ROKAE 60001 (Program Execution Error); 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 ROKAE 60001 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 System & Program alarms

50001 — xCore Controller System Error
Same family: this code belongs to the System & program alarms family - the page collects all System & program-family codes we have handled, with the common inspection order and spares.
Other brands: we also keep field-fix libraries for Dobot · FANUC · KUKA and more — see the complete alarm code hub.

Frequently asked questions

QWhat does the ROKAE 60001 alarm mean?

The running robot program hit an execution error — invalid instruction argument, missing point, or failed subroutine. Codes 6xxxx are program/task-level events. We fix this ROKAE xCore (XB / CR / NB series) fault almost daily, and one round of on-site checks usually confirms what is going on. ROKAE 60001 sits in the system & program family; on our work orders the highest-frequency trigger for this code is "Taught point deleted but still referenced".

QCan I clear a ROKAE 60001 alarm myself?

Whether ROKAE 60001 clears on its own depends on the outcome of "Note the line number shown with the error". Finish the flow with "Regression-test the program at low speed" to confirm ROKAE 60001 - do not skip it. If that step is clean, the second most frequent cause on ROKAE 60001 is "Variable out of range for the instruction". Do not chase takt through a repeating ROKAE 60001. Left alone, system & program faults tend to graduate from repairable to must-replace.

QWhen you handle ROKAE 60001, will my programs and frames get lost?

The commonest causes we see on ROKAE 60001 are "Taught point deleted but still referenced, Variable out of range for the instruction, Subroutine missing or renamed", so we stock the van against those. For ROKAE 60001 specifically, we carry recovery media and common storage media, but on this family the backup matters more than the spare. For ROKAE 60001, on system alarms the first move is backup; we can walk the customer through preserving data remotely before anything else. Before we roll, tell us what ROKAE 60001 shows on the pendant alarm list; codes segment as 1xxxx / 5xxxx / 6xxxx and what the machine was doing - phone or video triage is free.

The content on ROKAE 60001 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 ROKAE documentation, or contact us to confirm. Henghuan is an independent service provider with no affiliation or endorsement by ROKAE.