Resolving Motoman XRC External Axis Alarm 1314 on Re-Enable

Problem Overview

The Motoman XRC controller, when redeployed from a used robotic cell, frequently retains parameters from the prior integration. A common post-redeployment symptom is that an external axis appears physically connected (no controller alarm on boot, no errors on the teach pendant) but the moment the operator enters external-axis jog mode and attempts to move the axis, the controller raises Alarm 1314 and refuses motion. The teach pendant's external-axis enable lamp also blinks instead of latching steady. This article documents the root cause, diagnostic path, and verified recovery procedure for that fault on the XRC platform.

The same parameter-driven lockout applies to other Motoman controllers that descend from the XRC architecture; the Yaskawa Motoman External Axis knowledge base covers modern equivalents and is the authoritative starting point for any external-axis work on current-generation controllers such as the YRC1000 and DX200.

Affected Platform and Versions

Symptom Summary

• Controller powers up clean: no alarms on boot, no faults shown on the teach pendant status bar.
• Selecting the external axis group on the teach pendant causes the external-axis enable indicator to blink rather than latch on solid.
• Any jog command in the external axis direction immediately raises Alarm 1314.
• The job loaded in the controller is an R1-only job — the operator has not been able to attach the external axis group to the active job header.

The blinking indicator is normal under forced-axis selection when the active job does not declare the external axis group. It is informational, not a fault; the alarm is the real fault.

Root Cause Analysis

Alarm 1314 in this scenario is generated because the SV2G parameter set still reflects the configuration in which the external axis was disabled in software before the robot was removed from its original cell. The XRC implements external-axis enable/disable through a set of one-bit flags in the SV2G parameter group. When the original integrator (or decommissioning technician) removed the external axis from the system, the bit corresponding to the affected axis — by convention SV2G8 for the first external axis group — was set to 1 to mark the axis as disabled.

The axis may be electrically present (the amplifier is on, the encoder resolves, the motor is mounted) but the supervisory parameter block in CMOS has the axis bit cleared, so the controller refuses to close the servo loop and commands the amplifier to a faulted state. The amplifier will respond by raising alarm 1314 the first time it is asked to torque the disabled axis.

Three sub-causes must be ruled out before the parameter change is committed:

1. Hardware wiring: The XRC expects motor power, encoder feedback, and brake release lines to land on the assigned connector pins of the external-axis amplifier. Used robots frequently arrive with homemade or salvaged cables that differ from the Motoman print.
2. Brake release: If the holding brake is not being commanded open by the amplifier, the motor is mechanically locked and any torque request will fault.
3. Mechanical load: A damaged gearbox, seized coupling, or jammed fixture will look like a wiring fault to the amplifier.

Pre-Diagnostic: Inspect ALL.PRM Offline

Before touching the controller, export the current parameter file. On the XRC the procedure is:

1. Insert a PC card (CompactFlash) into the teach pendant PC card slot.
2. From the main menu navigate to SETUP → PARAMETER → SAVE.
3. Save the full parameter set as ALL.PRM onto the card.
4. Remove the card and read it on a PC with a text editor or a spreadsheet.

Search for the SV2G parameter block. Parameters are zero-indexed; SV2G0 is the first, and SV2G8 is the ninth. The relevant bit will read 1 if the axis is software-disabled, 0 if enabled. Confirm the rest of the SV2G block matches the expected axis configuration before editing.

Hardware Verification (Do This First)

The XRC will not honour a parameter re-enable if hardware-side faults exist. Confirm the following before the parameter write.

Power and Encoder Continuity

Cross-check the motor and encoder wiring against the print supplied by Motoman for the robot's exact configuration. The original cell's external J-box sometimes consolidates power and encoder runs into a short intermediate cable. Both that intermediate and the final drop to the amplifier must be present and pinned 1:1 — there is no polarity tolerance on resolver or serial-encoder lines.

Brake Release

With servo power OFF, the brake should be engaged (motor shaft locked). When servo power is turned ON, you should hear and feel the brake click open. If the brake does not release, the brake release leads on the motor connector are open, the 24 V supply that feeds the brake board is missing, or the brake itself has failed. A motor that cannot be manually rotated (after removing any external mechanical load) when the controller claims servo power is ON is a brake problem first, parameter problem second.

Amplifier and Motor Swap Test

The amplifier and motor may be hot-swapped with a known-good axis to isolate the fault to one side. On the XRC, this is the standard field test:

1. Power down and lock out.
2. Substitute the suspect amplifier with a known-good unit of the same model number.
3. Power up and re-test the external-axis jog.
4. If alarm persists, substitute the motor in the same way.

If both swaps still produce 1314, the fault is supervisory (the SV2G parameter) and not electrical.

Gearbox and Mechanical Load

Decouple the motor from the gearbox and try to jog the motor unloaded. A damaged gearbox or jammed fixture will present a stalled-rotor fault to the amplifier that looks identical to a wiring fault. The motor should spin freely by hand with the brake released and no alarm active.

Re-Enabling the External Axis: Parameter Procedure

Option A — CMOS.bin Restore (Preferred When Available)

If the original integrator's full system backup (CMOS.bin) is on file from when the cell was intact, restoring it is the cleanest path. The CMOS.bin contains the supervisory parameter set including SV2G. Steps:

1. Place the controller in MAINTENANCE mode and cycle servo power OFF.
2. Copy the saved CMOS.bin to a freshly formatted PC card.
3. Boot the controller and, when prompted, restore from the PC card.
4. Delete the current jobs that were created on the partial configuration.
5. Reload the current active jobs that are to be used on the recovered cell.

This path is preferred because it restores not just the SV2G bit but the full coordinated-axis timing, group definitions, and motion-tuning constants the original integrator loaded.

Option B — Edit SV2G8 Directly on the Pendant

If no CMOS.bin is available, edit the parameter under the Yaskawa level password.

1. Log in to the controller with the Yaskawa/Motoman security level required to write S2. parameters. This is typically a vendor-level password that Motoman service personnel hold and is not shipped with the controller.
2. Navigate to SETUP → PARAMETER → S2G.
3. Count eight parameters from the start of the block (parameters are zero-indexed) to reach SV2G8.
4. Set SV2G8 = 0. The axis is now flagged as enabled in supervisory software.
5. Cycle controller power to load the new supervisory image.

Option C — Edit ALL.PRM on PC, Re-import

As a last resort, the parameter can be changed by editing ALL.PRM offline on a PC and re-importing through the parameter load menu. This is more invasive than pendant edit and should only be done when the pendant security level is unknown but the PC import path is still accessible.

Selecting the External Axis Type (TURN-1 vs. TURN-2 vs. LINEAR)

For a rotary weld fixture, the axis type selected in SETUP → FUNCTION → EXTERNAL AXIS must match the physical axis.

For a single-axis rotary weld fixture, TURN-1 is the correct selection. Selecting LINEAR on a rotary axis, or vice versa, will produce coordinated-motion errors that look like alarm 1314 but originate from a different parameter block (SV2G group configuration as well as the motion definition file).

Teach Pendant LED Behaviour — What is Normal

The blinking of the external-axis enable lamp on the pendant is a forced-axis indication, not a fault. It appears when:

• The active job header does not declare an external axis group (an R1-only job is loaded).
• The operator is forcing the pendant into external-axis mode manually.

The lamp will latch solid only when an active job that includes the external axis group is loaded, or when the controller is in manual external-axis jog mode without an attached job. The blink is a status indicator of mode mismatch, not a hardware warning.

Verification Procedure

After the SV2G8 = 0 write and a controller power cycle, verify the recovery in the following order:

1. Boot the controller. Confirm no alarms on the status line.
2. Enter TEACH mode. Select the external axis group. Confirm the enable lamp latches solid (not blinking).
3. With the brake confirmed open (audible click), command a small positive jog in the external axis direction. The motor should rotate without alarm 1314.
4. Command a small negative jog. Confirm reversing direction works.
5. Command a continuous jog in both directions and observe smooth motion without stalls.
6. Reattach the mechanical load (fixture, gearbox coupling) and repeat the jog test at low speed.
7. Load or create a job that references the external axis group and run it in PLAY mode at reduced override (10%).

If alarm 1314 returns at any step, return to the hardware verification matrix and re-check the brake, then the amplifier, then the motor, then the SV2G bit value.

Troubleshooting Matrix

Safety and LOTO

Field Notes

The combination of "no alarm on boot" and "1314 on first jog" is the diagnostic signature of a software-disabled axis on the XRC. The pendant editor is the only field-safe write path; CMOS.bin restore is the cleanest. Used robots that have been re-deployed across multiple cells frequently arrive with several SV-class parameters in inconsistent states. Treat the SV2G block as a single coherent unit — if SV2G8 is wrong, verify the rest of the block before assuming a one-bit fix is sufficient.

When all else fails, the XRC has a controlled re-initialization procedure that requires Motoman service access. This is the only supported path when the vendor password and CMOS.bin are both unavailable. The Yaskawa Motoman External Axis knowledge base should be consulted for current-generation controllers and for any cross-platform migration from the XRC to a newer controller family.