What the 0x15 alarm means

A JUMP-mode motion was commanded with an invalid Height parameter — per the Dobot ALARM description, Height was set below zero. The move is rejected. This is a fault we handle frequently on Dobot Magician / MG400 / M1 / CR (DobotStudio) systems — in most cases we can pin down the root cause on the first site visit.

Most common causes

  • JUMP Height set to a negative value
  • Height parameter left at an uninitialized value
  • Variable feeding the JUMP height computed negative
  • Unit confusion between mm and inches in a converted program
Field note: The first item on this list is what we hit most often on real machines — clear that one before going deeper.

Step-by-step field fix

  1. Open the JUMP instruction and set Height to a valid positive value
  2. Check any variable or expression feeding the height
  3. Confirm units are consistent across the program
  4. Save the point and re-teach if necessary
  5. Run the clear-alarm script in DobotStudio and re-test
Safety first: For Dobot 0x15, the risk on this family is not injury but data: lose the program, parameters and calibration data and weeks of teaching work start over. On site you may carry out the first step yourself: Open the JUMP instruction and set Height to a valid positive value. Beyond that it is program and calibration data work - leave it to a professional.

How we diagnose system alarms on site

Dobot 0x15 belongs to the system & program family. On Dobot 0x15 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 0x15 at DobotStudio / app alarm messages; error codes are hexadecimal with a 0x prefix.

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

JUMP Height set to a negative value on Dobot 0x15 often traces to a version combination: A solid share of system alarms comes from mismatched version sets: controller firmware upgraded while pendant software, drive configuration or a vision option stayed behind, so boot-time validation fails. Another flavour is a swapped main board or storage media whose system image carries hardware configuration that no longer matches reality. We line up firmware version, software version, option list and actual hardware config and find the one that disagrees. No hardware needed - but the matching recovery media is.

Field notes on this page cover Dobot 0x15 (JUMP Parameter Error); written by the Henghuan repair team, updated 2026-10-01.

Can't clear it yourself? Contact us for remote diagnosis

Tell us the alarm code, the model and what the machine was doing when the alarm appeared. Dobot 0x15 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 System & Program alarms

0x13 — Duplicate Data — Planned Points Repeated
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 0x15 alarm mean?

A JUMP-mode motion was commanded with an invalid Height parameter — per the Dobot ALARM description, Height was set below zero. The move is rejected. This is a fault we handle frequently on Dobot Magician / MG400 / M1 / CR (DobotStudio) systems — in most cases we can pin down the root cause on the first site visit. Dobot 0x15 sits in the system & program family; on our work orders the highest-frequency trigger for this code is "JUMP Height set to a negative value".

QCan I clear a Dobot 0x15 alarm myself?

Whether Dobot 0x15 clears on its own depends on the outcome of "Open the JUMP instruction and set Height to a valid positive value". Finish the flow with "Run the clear-alarm script in DobotStudio and re-test" to confirm Dobot 0x15 - do not skip it. If that step is clean, the second most frequent cause on Dobot 0x15 is "Height parameter left at an uninitialized value". Two attempts and still there means stop: Dobot 0x15 involves program and calibration data, and running Dobot 0x15 on can turn a repairable fault into a replacement.

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

The commonest causes we see on Dobot 0x15 are "JUMP Height set to a negative value, Height parameter left at an uninitialized value, Variable feeding the JUMP height computed negative", so we stock the van against those. For Dobot 0x15 specifically, we carry recovery media and common storage media, but on this family the backup matters more than the spare. For Dobot 0x15, 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 0x15 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 0x15 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.