Resolving Yaskawa DX200 "Operation Prohibited by External Device" with Alarm 0530

When a Motoman DX200 controller is paired with a milling machine or other external cell controller, the operator typically transitions between Teach mode for setup and Remote mode for unattended production. The controller enforces a strict authority hierarchy at each key-switch position, and the alarm banner "Operation prohibited by External Device" — frequently accompanied by alarm 0530 "Start Reservation Mode" — is the controller's way of refusing a start request issued from the wrong authority level. This reference walks through the cause, the diagnostic procedure, and the two field-proven solution paths that restore external start capability without external pushbuttons, plus the fieldbus and safety considerations every integrator must address before commissioning.

Problem Definition

On a DX200 linked to a milling machine, the reported symptoms are consistent across most installations where no external pushbutton station is wired:

• Teach mode operates normally. The operator can energize the servos, jog all axes, edit and run jobs at reduced override, and recover from faults.
• Rotating the key to Remote mode causes the servo contactor to drop immediately. The pendant displays "Operation prohibited by External Device" for several seconds.
• Pressing the green start button on the standard programming pendant while in Remote re-triggers the same banner, often followed by alarm 0530 "Start Reservation Mode."
• Rotating the key to the middle (Play) position allows the operator to press SERVO ON READY and bring the servo contactor back up, but pressing start still raises 0530.
• The fault clears when the controller is returned to Teach mode.
• No external hardware pushbuttons, E-stops, or operator pendants are present in the cell other than the standard Yaskawa remote interface, yet the controller still expects an external start authority when the key is in Remote.

The behavior is not a hardware fault. It is the DX200 enforcing two coupled safety policies — mode-dependent authority and the optional Reserved Start handshake — exactly as designed. The fix is configuration, not replacement.

Root Cause: Authority and Handshake

Key switch authority

The DX200 programming pendant exposes a three-position key switch that selects between three independent startup authority models. The controller does not allow seamless handoff of authority mid-cycle; each transition opens the servo contactor and re-evaluates who is allowed to bring it back up.

When the operator rotates the key from any position to Remote, the controller drops the servo contactor immediately and stops honoring the pendant's SERVO ON READY button as a valid request. From that moment onward, the controller is listening for an external Servo On signal on a universal input assigned in SETUP, and — if the Reserved Start function is enabled — for an additional handshake pulse on a separate UI before the green button (or any external start command) will be accepted.

Reserved Start function

Reserved Start is a DX200 safety feature designed for cells where the external device (PLC, milling machine, cell controller) must explicitly grant the robot permission to start a cycle. The function has two settings in SETUP → FUNCTION ENABLE → RESERVED START:

When PERMIT is active but no external pulse arrives, or the pulse arrives on the wrong input, or the wiring is floating, the controller raises alarm 0530 "Start Reservation Mode" and refuses the cycle.

External device permission model

"Operation prohibited by External Device" is the controller's generic refusal banner whenever a start request is issued from an authority the controller does not recognize for the current mode. The banner is intentionally generic so that the same message covers missing Reserved Start, missing Servo On, and a number of related handshake failures.

Affected Configurations and Prerequisites

The patterns covered here apply to any DX200 controller that drives an external cell, including:

• DX200 paired with a milling machine, lathe, press, or other CNC peripheral where the peripheral is the cell master.
• DX200 in a multi-robot cell where a higher-level PLC coordinates starts.
• DX200 with Ethernet/IP, Profibus, or DeviceNet fieldbus options where the start command and handshake are carried over the network rather than through hard-wired UIs.
• DX200 in any application that switches to Remote mode for unattended production but lacks a physical pushbutton station.

Installations where the robot is the cell master and the operator drives production directly from the pendant should not be using Remote mode at all; they should remain in Play.

Prerequisites

1. The teach pendant is available and the operator is logged in at Maintenance or higher. The SETUP menu is hidden under Operator and protected under Maintenance. Passwords are configured in SETUP → USER ID.
2. The controller is in Teach mode and the program is stopped. Editing safety-related parameters while the controller is in Play or Remote is not supported.
3. The current parameter values have been captured. The standard Motoman backup utility writes a complete parameter snapshot to USB or CompactFlash; save it before any change.
4. The site risk assessment permits the new mode of operation. Disabling Reserved Start or relaxing external authority may affect the cell's compliance posture under ISO 10218 / ANSI / CE; verify with the safety officer before changing values.
5. All E-stops, gate interlocks, and deadman circuits are closed. An open safety circuit will block servo re-energize before Reserved Start is even evaluated.

Diagnostic Procedure

1. Confirm Teach mode is healthy. From the pendant, run a short job at 10% override. If Teach works end-to-end, motion, I/O, and program logic are not contributors.
2. Capture the active alarm. Press SELECT on the pendant alarm banner and note the four-digit code. 0530 confirms a Reserved Start timeout. Other codes (4107, 4110, 4604, 4630, and the 4750 family) indicate different faults and must be cleared before Reserved Start can be evaluated.
3. Reproduce the fault in Play. Rotate the key to the middle (Play) position, press SERVO ON READY, and press the green button. If 0530 also raises in Play, Reserved Start is the cause. If Play starts cleanly but Remote raises 0530, the cause is mode-dependent authority combined with a missing external handshake.
4. Read the current Reserved Start assignment. From the pendant, navigate SETUP → FUNCTION ENABLE → RESERVED START. Note whether the function is PERMIT or PROHIBIT. If PERMIT, navigate SETUP → RES. START (CNCT) and note which UI is mapped, the active logic level, and the reservation window.
5. Verify the physical input. If a UI is mapped, monitor it with the pendant I/O monitor or via the Motoman communications SDK while toggling the external device. A floating input that never reaches the assigned logic level is the single most common root cause when no pushbutton is wired.
6. Check fieldbus status if applicable. For Ethernet/IP, Profibus, or DeviceNet integrations, open the fieldbus diagnostic page and confirm the connection is active and no watchdog has tripped.
7. Verify security level. Attempt to enter SETUP. If the menu is dimmed or the save prompt is rejected, the current user is below Maintenance. Switch user level before continuing.

Solution A — Disable Reserved Start

Use this path when the cell has no external start signal and the operator must be able to issue starts from the pendant even in Remote mode.

1. Rotate the key to Teach and stop the program.
2. From the main menu, choose SETUP. Enter the safety password if prompted.
3. Navigate SETUP → FUNCTION ENABLE → RESERVED START.
4. Toggle the field from PERMIT to PROHIBIT.
5. Press ENTER and confirm the save prompt.
6. Power-cycle the controller so the new value is read at boot. Some DX200 firmware revisions cache FUNCTION ENABLE values across power cycles; a reboot is the only reliable way to confirm the change is live.
7. Return to the main menu and rotate the key to Remote.
8. Press the pendant SERVO ON READY button (which is still honored in Remote in this configuration) and verify the servo contactor closes.
9. Press the green button. The cycle should start without "Operation prohibited by External Device" or 0530.

Solution B — Configure External Handshake

Use this path when an external device (milling machine, PLC, or cell controller) must be the sole authority for starting the robot in Remote mode.

1. Select a free universal input on the DX200 I/O board. Document the input number (for example UI 11 on a typical DX200 mainboard).
2. Wire a dry contact from the external device between the chosen UI terminal and the 0 V (COM) reference. The contact should close only when the external controller is ready to start the robot and should remain closed for the duration of the handshake.
3. From the pendant, SETUP → FUNCTION ENABLE → RESERVED START → PERMIT.
4. SETUP → RES. START (CNCT). Select the input number assigned in step 1. Set the active logic to match the wiring (typically N.O., active HIGH).
5. Set the reservation window. The default is several seconds; reduce it if the cell requires a tight handshake or extend it if the external device has long handshake latency.
6. Save and power-cycle.
7. Test the handshake: pulse the wired input, then press start within the reservation window. The job should execute. Out-of-window pulses should raise 0530 as designed.

Reference wiring example

Fieldbus Integration

When the external device communicates with the DX200 over Ethernet/IP, Profibus, or DeviceNet, Reserved Start can be carried as a virtual bit in the fieldbus assembly rather than as a hard-wired UI. The configuration steps are the same — SETUP → FUNCTION ENABLE → RESERVED START → PERMIT — but the input assignment uses a fieldbus-mapped register instead of a physical UI.

Ethernet/IP

On a DX200 with the Ethernet/IP option enabled, the typical Reserved Start mapping uses an input bit in the Standard Input Assembly. The integrator must:

• Confirm the Ethernet/IP option is licensed and visible in SETUP → OPTION FUNCTION.
• Map the Reserved Start UI to the fieldbus bit through the assembly configuration tool.
• Verify the PLC is writing the bit before issuing the start command.
• Monitor the fieldbus connection state in the pendant's Ethernet/IP diagnostic page; a watchdog trip will mask the handshake as a 0530 timeout.

Profibus and DeviceNet

The same principle applies to Profibus and DeviceNet integrations. The controller will surface a fieldbus communication fault (typically a separate alarm number) before or alongside 0530 if the network is down, which is a useful diagnostic discriminator.

Mode Sequencing Reference

Common Pitfalls

• Pseudo input confusion. Toggling pseudo inputs (the menu that simulates I/O states for offline program development) does not satisfy the Reserved Start handshake. Reserved Start requires a real or hard-mapped input.
• Security level too low. SETUP entries are read-only under Operator. The change must be made under Maintenance or higher.
• E-stop chain still open. An open external E-stop, gate interlock, or deadman will block servo re-energize before Reserved Start is even evaluated. Clear those faults first.
• Step-vs-start mismatch. If the job was paused mid-cycle, DX200 expects a Resume, not a fresh Start. The 0530 may mask a Step-Resume mismatch after the program was interrupted.
• Fieldbus heartbeat lost. When Ethernet/IP, Profibus, or DeviceNet is the carrier for the start command, a watchdog trip can look identical to a Reserved Start fault. Check the fieldbus diagnostic page before changing I/O wiring.
• Wrong UI assigned. Mapping the Reserved Start UI to an input that is physically tied to another function (such as an interlock or cycle-stop) will create intermittent faults that are difficult to diagnose. Always verify the UI is free and unused.
• Reservation window too short. If the external device has scan-time latency, the UI pulse may arrive after the controller's window has expired. Increase the window in SETUP → RES. START (CNCT).
• Power-cycle forgotten. Some DX200 firmware revisions cache FUNCTION ENABLE values. Always reboot after changing safety-related settings.
• Mode-switched mid-cycle. Rotating the key during a running cycle drops the servo and raises a banner that resembles 0530. Wait for the cycle to complete or perform a controlled hold before changing modes.
• Old firmware assumption. Menu layouts and default values change between DX200 firmware revisions. Verify the menu path against the revision actually installed on the controller, not against screenshots from a different revision.

Verification and Related Alarms

1. From Teach, run a known-good program at 10% override and confirm a clean cycle.
2. Switch to Play. Confirm the servo can be re-energized and the green button starts the job without alarms.
3. Switch to Remote. Confirm the servo re-energizes through the chosen path (Solution A: pendant; Solution B: external Servo On). Initiate the start through the chosen path (Solution A: green button; Solution B: external handshake then green button). Confirm no 0530 and no "Operation prohibited by External Device" banner.
4. Power-cycle the controller and re-test Remote to verify the change persists.
5. Back up the controller image with the standard Motoman backup utility after every successful change.
6. Document the change in the cell's safety file, including before/after parameter values and the date and engineer of record.
7. Re-run the cell's risk assessment to confirm the new mode of operation does not introduce an unacceptable hazard.

Related alarms

Reference Documentation

The key-switch authority model and the Reserved Start behavior are documented in the DX200 Instructions manual, in the "Notes for Safe Operation" section. The manual classifies the relevant warnings, mandates, and prohibitions for remote operation and should be consulted for any cell where external start authority is being modified.

Yaskawa Motoman DX200 Instructions Manual (PDF)

FAQ