What the 0x13 alarm means

In ARC or JUMP_MOVL mode the planned points are duplicated, so the trajectory cannot be constructed. Documented in the official Dobot ALARM description: the alarm is set when an ARC has repeated points or a JUMP_MOVL start equals its end. This is a high-frequency ticket for our Dobot repair team, and on Magician / MG400 / M1 / CR (DobotStudio) systems one inspection usually identifies the fault.

Most common causes

  • ARC mode: two or three of the taught points are identical, so no circle can be fitted
  • JUMP_MOVL mode: start point equals end point with no translation segment
  • Copy-pasted points in the program without re-teaching
  • A vision or offset routine writing the same value to two points
Field note: The top-listed cause has the highest hit rate, so checking it first narrows things down fast.

Step-by-step field fix

  1. Check the taught points for duplicates and re-teach distinct positions
  2. Verify any offset/vision calculations that feed the points
  3. Save the corrected points
  4. In DobotStudio, run the clear-alarm script from the script control module
  5. Re-run the motion at low speed to confirm
Safety first: For Dobot 0x13, the risk on this family is not injury but data: lose the program, parameters and calibration data and weeks of teaching work start over. What you can check yourself first is Check the taught points for duplicates and re-teach distinct positions; program and calibration data handling is not a DIY job.

How we diagnose system alarms on site

Dobot 0x13 belongs to the system & program family. On Dobot 0x13 the failing stage is DobotStudio Pro / Dobot SDK (Dobot controllers (CR / MG / Nova series companions)) on the Dobot controllers (CR / MG / Nova series companions) - the software layer: corrupted program or parameter files, boot failures, version mismatch, memory and storage media. We start reading Dobot 0x13 at DobotStudio / app alarm messages; error codes are hexadecimal with a 0x prefix.

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

Dobot 0x13 is a system-family alarm, and our iron rule is: On system alarms we have an iron rule: however urgent the customer is, we take a complete backup first - programs, parameters, calibration data, tool and work-object frames, all of it. The reason is arithmetic: losing the live state here usually means weeks of teaching done again, which costs far more than a few hours of downtime. Only after the backup do we decide restart, restore or reinstall. If the storage media is already throwing errors we pull the data read-only first.

Field notes on this page cover Dobot 0x13 (Duplicate Data — Planned Points Repeated); written by the Henghuan repair team, updated 2026-10-01.

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

Share the alarm code, machine model and the operating condition at the moment of the alarm. Our engineers are highly experienced with Dobot 0x13, 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 System & Program alarms

0x15 — JUMP Parameter 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 FANUC · KUKA · ABB and more — see the complete alarm code hub.

Frequently asked questions

QWhat does the Dobot 0x13 alarm mean?

In ARC or JUMP_MOVL mode the planned points are duplicated, so the trajectory cannot be constructed. Documented in the official Dobot ALARM description: the alarm is set when an ARC has repeated points or a JUMP_MOVL start equals its end. This is a high-frequency ticket for our Dobot repair team, and on Magician / MG400 / M1 / CR (DobotStudio) systems one inspection usually identifies the fault. Dobot 0x13 sits in the system & program family; on our work orders the highest-frequency trigger for this code is "ARC mode: two or three of the taught points are identical, so no circle can be fitted".

QCan I clear a Dobot 0x13 alarm myself?

Whether Dobot 0x13 clears on its own depends on the outcome of "Check the taught points for duplicates and re-teach distinct positions". Finish the flow with "Re-run the motion at low speed to confirm" to confirm Dobot 0x13 - do not skip it. If that step is clean, the second most frequent cause on Dobot 0x13 is "JUMP_MOVL mode: start point equals end point with no translation segment". When Dobot 0x13 keeps coming back it is not a one-off trigger - especially if Re-run the motion at low speed to confirm is where you get stuck. Do not keep producing through Dobot 0x13.

QWhen you handle Dobot 0x13, will my programs and frames get lost?

The commonest causes we see on Dobot 0x13 are "ARC mode: two or three of the taught points are identical, so no circle can be fitted, JUMP_MOVL mode: start point equals end point with no translation segment, Copy-pasted points in the program without re-teaching", so we stock the van against those. For Dobot 0x13 specifically, we carry recovery media and common storage media, but on this family the backup matters more than the spare. For Dobot 0x13, 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 Dobot 0x13 shows on DobotStudio / app alarm messages; error codes are hexadecimal with a 0x prefix and what the machine was doing - phone or video triage is free.

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