Dobot Magician — Alarms & Studio Connection

Dobot · beginner · 15 min

A Dobot Magician turns its indicator red when an alarm is active — out-of-workspace, joint overspeed, a sensor read fault or an MCU/FPGA init failure. Learn what each means, how to Clear Alarms in Dobot Studio, and how to fix a Studio connection that won't open.

ℹ️ On a Dobot Magician the alarm icon is white = no alarm, red = alarm, and while an alarm is active the end/joint indicator turns red. Fix the cause first, then click Clear Alarms in Dobot Studio — clearing without fixing just brings it back.

How the Magician shows an alarm

The Dobot Magician uses a simple colour code: the alarm icon is white when there is no alarm and red when there is one, and if the arm is still powered while an alarm is active, the end indicator light turns red. So a red end-light is your cue that the controller has logged an alarm you need to read in Dobot Studio.

Common alarm causes

The Magician's alarm list covers both motion-logic and hardware faults. The ones you'll meet most:

• Motion out of workspace — a commanded move is outside the reachable envelope, causing an inverse-kinematics (inverse resolve) alarm. Re-teach the point inside the workspace.
• Joint overspeed (e.g. Joint 1 overspeed) — the motion asked a joint to move faster than allowed. Reduce speed/acceleration or smooth the path.
• Angle sensor value cannot be read correctly — a feedback read fault. Power the arm off and on; if the angle sensor then reads correctly, the alarm resets.
• MCU–FPGA communication fails during initialization — an internal comms fault at startup; reset the controller and if the communication succeeds the alarm resets automatically.

Clear the alarm the right way

After you've resolved the underlying cause, in Dobot Studio click Clear Alarms to clear it. The order matters: fix first (move back into the workspace, lower the speed, power-cycle for a sensor read fault), then Clear Alarms — otherwise it re-triggers immediately.

When Dobot Studio won't connect

If Studio can't reach the robot at all:

1. Check the USB connection — reseat it and try a different cable (a charge-only or flaky cable is a common cause).
2. Update Dobot Studio and reinstall the drivers.
3. Restart Dobot Studio and try connecting again.
4. If the unit is unresponsive/bricked, the firmware can be re-burned with the vendor Mcuisp utility as a last resort.

Step-by-step

1. Red end-light? Open Dobot Studio and read the alarm.
2. Out of workspace / overspeed? Re-teach inside reach or lower speed/accel.
3. Sensor read / MCU-FPGA fault? Power-cycle / reset; it resets when the read/comms succeed.
4. Clear Alarms in Studio once the cause is fixed.
5. Studio won't connect? New USB cable → update Studio + drivers → restart.

Never do this

Don't repeatedly Clear Alarms on an out-of-workspace or overspeed fault without changing the program — you're commanding a move the arm can't safely make. Fix the taught point or the speed so the motion is valid.