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 one of the faults our repair team handles on Dobot Magician / MG400 / M1 / CR (DobotStudio) systems — the cause is usually identifiable within the first on-site inspection.

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 find most often on real machines. Check it before you go 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: never bypass safety circuits or force contactors closed. If the alarm involves E-stop chains, brakes or drive power, and you are not a trained robot technician, contact a professional — wrong moves here can cost you a robot or an injury.

Still stuck? Get an engineer on the phone — right now

Tell us the alarm code, the robot model and what was happening when the alarm came up. Our engineers run these diagnostics every day, and remote diagnosis by phone or video call is free.

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
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. In field practice it belongs to the system & program family of faults.

QCan I clear a Dobot 0x15 alarm myself?

Sometimes. Work through the step-by-step checks on this page — the first listed cause is what we find most often in the field. If the alarm returns after two attempts, or the fault involves power, brakes or safety circuits, stop and call a qualified robot service engineer.

QHow fast can a Henghuan engineer help?

On-site response in the Pearl River Delta within 30 minutes to 3 hours, across mainland China in 1-3 business days, and worldwide within 2-5 business days. Remote diagnosis by phone/WhatsApp/video is available immediately.

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 Dobot documentation or contact us. Henghuan is an independent service provider, not affiliated with or endorsed by Dobot.