CQM1 CPU11 Output Failure: LED Diagnostics and Address Conflicts

Problem Overview

The Omron CQM1-CPU11 is a compact modular PLC from the now-discontinued CQM1 series that remains in service across many legacy machine cells. The most common field complaint on the CQM1-CPU11 is that outputs refuse to energise even when the program logic commands them ON. The root cause is split between two distinct failure domains: (1) the output module itself has failed (open transistor, blown triac, welded relay contact), or (2) the application program is forcing the same output OFF on a second rung, producing a coil-conflict condition that CX-Programmer allows through with only a warning. Both failures look identical from the control cabinet because the output device never sees voltage, so a structured diagnostic path is required.

This reference consolidates the LED-indication method, the Channel 100 output address map, the FORCE ON / SET distinction in CX-Programmer, the duplicate-coil warning behaviour, and the recommended replacement strategy when the output card is confirmed dead. It draws on the official CQM1 Operation Manual (W226-E1-7) and the CQM1H Programming Manual (W364) for addressing rules, indicator semantics, and instruction set behaviour.

CQM1-CPU11 Hardware Architecture

The CQM1-CPU11 is a member of the CQM1 family, which uses a backplane-mounted CPU with separately-orderable I/O modules. The CPU has no fixed I/O; all inputs and outputs reside on dedicated modules seated to the right of the CPU. Relevant constraints for this troubleshooting reference:

Because I/O modules are slotted, every output point has a fixed location in the IR (Internal Relay) area, beginning at word 100 (Channel 100) for the first output module and incrementing for each subsequent module. Failing to address outputs at the correct channel is the single most common programming cause of "no output" symptoms.

Output Address Mapping — Channel 100 and Beyond

Omron IR addressing uses the format Channel.Bit. For the first output module on a CQM1-CPU11 rack, the eight physical output terminals correspond to IR 100.00 through IR 100.07:

• Output terminal 0 → 100.00
• Output terminal 1 → 100.01
• Output terminal 2 → 100.02
• Output terminal 3 → 100.03
• Output terminal 4 → 100.04
• Output terminal 5 → 100.05
• Output terminal 6 → 100.06
• Output terminal 7 → 100.07

The next output module increments to 101.00–101.07, and so on. This convention is documented in the CQM1 Operation Manual under the I/O allocation section. If your project uses addresses such as 010.00 or 200.00, you have addressed the wrong area entirely and the CPU will never drive the physical terminals regardless of ladder state.

LED Indicator Diagnostics

Each output module on the CQM1 has an LED per point directly above its removable terminal block. The LED is driven from the same output driver stage that switches the load. The diagnostic logic is therefore simple and authoritative:

The single most decisive check is: if the LED is ON but the output terminal shows 0 V, the module is dead and must be replaced. No programming change will recover a failed output driver. Conversely, if the LED never lights under any condition, the problem is upstream — either in the CPU logic or in the addressing.

FORCE ON Versus SET in CX-Programmer

When the LED is OFF and you want to bypass the program to confirm the module responds, CX-Programmer offers two operations that look similar but behave differently:

The correct diagnostic move is to right-click the output address in CX-Programmer and select Force → On. If the LED still does not illuminate, the module is dead. If the LED illuminates and the terminal voltage appears, the module is functional and your program logic is the culprit. Always release all forces before returning the machine to production; persistent forces survive a STOP/RUN transition but are cleared by a full power cycle.

Duplicate Output (Coil) Conflict Detection

The single most insidious programming cause of "no output" on the CQM1-CPU11 is a duplicate coil — the same IR address (e.g., 100.01) used as the output of two or more OUT/OUTNOT instructions in different rungs. Unlike many modern controllers that reject duplicate coils at compile time, CX-Programmer will compile and download a program with duplicate coils, emitting only a yellow warning triangle in the message window.

The execution model is "last rung wins." Each scan, the CPU executes the ladder from top to bottom. If Rung 1 turns 100.01 ON and Rung 5 turns the same 100.01 OFF, the scan ends with 100.01 OFF regardless of Rung 1's logic. This produces the field symptom: "My ladder says the output should be on, but the LED stays off."

To detect this in CX-Programmer:

1. Open the project and select Edit → Find Duplicated Outputs (or use the cross-reference tool View → Cross-Reference).
2. Filter on the suspect IR address, for example 100.01.
3. Inspect every occurrence. Each duplicate should either be removed, changed to a different IR word, or wrapped with an interlock so it cannot run simultaneously.

A typical wrong/right pair appears as:

(WRONG)                              (RIGHT)
Rung 1:  --[ START ]--( 100.01 )    Rung 1:  --[ START ]--( W0.01 )
Rung 5:  --[ STOP  ]--( 100.01 )    Rung 2:  --[ STOP  ]--( W0.01 )
                                       Rung 3:  --[ W0.01 ]-( 100.01 )

The right-hand version uses a work bit W0.01 to resolve the rung-level OR logic, then drives the physical output on a single dedicated rung. This eliminates the duplicate coil and the warning.

Output Module Failure Modes

CQM1 output modules are available in three switch technologies. Each has a characteristic failure signature:

Per the CQM1 Operation Manual alarm output (ALM) section, an output module detecting an over-current or shorted-load condition will latch the ALM bit ON and switch all outputs off as a protection measure. If a sudden loss of all outputs on a single module occurred after a field wiring event, check the ALM bit in IR before assuming hardware death.

Replacement and Migration Strategy

The CQM1 series is no longer in production, and Omron's recommended migration path is to the CP1 series (CP1E / CP1L / CP1H) or to the CJ2M. Field-proven conversion steps:

1. Confirm the failed output module's catalog number (e.g., CQM1-OD212).
2. Order an equivalent CP1 expansion I/O module or convert the rack to a CP1L with built-in outputs.
3. Use CX-Programmer's CP1 support to import the CQM1 program and remap IR 100.x to CP1 CIO 100.x — the addressing is deliberately compatible to ease migration.
4. Re-test all outputs with FORCE ON before placing the machine back in service.

If a like-for-like CQM1 module is still available from stock, the swap is mechanical (slide the module out, seat the new one, no firmware change required). The CQM1H programming manual (W364) confirms that module hot-swap is not supported — power down the CPU before replacing an I/O card.

Verification Procedure

After applying any corrective action — program edit, force release, or module swap — run this sequence to confirm the fix:

1. Clear all forces. From CX-Programmer: Force → Clear All Forces. Confirm the message "All forces cleared" appears.
2. Place CPU in MONITOR mode. Press MODE until MONITOR LED lights, or use the programming software dropdown.
3. Cycle the suspected rung. Toggle the input condition and observe the output address in the watch window. The bit should track the input 1:1 with one scan-time delay.
4. Measure terminal voltage. With a multimeter on the output terminal referenced to COM, the voltage should swing from 0 V (off) to rated supply (on) within one scan.
5. Repeat for adjacent points. A single failed point on a multi-point module does not justify a full module replacement if you can re-route the load to a spare point — provided the spare exists and is addressed correctly.
6. Download and save. Store the verified program on a memory card or to disk; older CQM1 CPUs lose the program if the backup battery is removed.

Troubleshooting Matrix

Commissioning Best Practices

• Maintain a printed I/O map next to the cabinet showing every IR address, its function, and its channel. Most "dead output" tickets originate in undocumented re-wiring.
• Enable CX-Programmer's Cross-Reference Report on every save. A duplicate coil appears as a multi-row entry and can be caught before download.
• Use work bits (W area) for internal logic and reserve IR 100.x strictly for physical outputs. This convention eliminates accidental duplicate coils at the output layer.
• Label every force operation in the program comment field. Forces are invisible in the printed ladder and become a maintenance liability months later.
• Replace the CPU backup battery on a fixed schedule (typical 5-year life at 25 °C). A dead battery clears the program on power removal and forces a re-download that may subtly change I/O behaviour.

Frequently Asked Questions