Resolving CPM2A Expansion Function FCS Upload Error

Problem Overview

The Omron CPM2A series PLC rejects user program uploads that contain the FCS (Frame Checksum) expansion instruction with an alarm message of the form "Problems with the expansion functions" or "Expansion Instruction Error". The upload appears to complete but the FCS function code is not stored in the PLC's expansion instruction set, so any logic that references FCS in the ladder program will not execute correctly at runtime, or will generate a fatal instruction error on the first scan.

This is one of the most common CPM2A/CPM2C upload problems reported by field engineers and is caused by a single, easily-overlooked configuration switch in the Startup tab of the CX-Programmer PLC Settings dialog. The default factory state of this switch is "Protect", which blocks any attempt to change the expansion instruction assignments at upload time.

Affected Hardware and Firmware

The failure mode is documented for the following Omron PLC families that share the CPM2A expansion instruction architecture:

• Omron CPM2A (all CPU types: 20/30/40/60 I/O)
• Omron CPM2C (compact block style)
• Omron SRM1(-V2) (Slave Rack Master, V2 series)
• Omron CPM1A (where expansion instructions are supported)

All firmware revisions are affected. The behavior is defined by the boot-time check on bit/word DM 6600 bits controlling expansion instruction write protection and is not firmware-version dependent. Refer to the CPM1/CPM1A/CPM2A/CPM2C/SRM1 Programming Manual (W353) section 2-10 for the canonical definition.

Root Cause Analysis

The CPM2A stores the user's expansion instruction set in a separate non-volatile area from the main ladder program. The PLC will only accept a new expansion instruction set on upload if two conditions are both true:

1. The PLC is in PROGRAM mode at the moment of upload (not MONITOR or RUN).
2. The PLC Setup word controlling expansion instruction write protection allows the write.

The default Startup setting in CX-Programmer for the parameter Expansion Instructions is Protect. With this value selected, the CPM2A boot code writes the default (factory) expansion instruction set into RAM and locks the expansion instruction slots. Subsequent upload attempts appear to complete, but the FCS code is silently dropped because the destination slot is read-only. The result is a program that references an instruction code the PLC does not know, and either executes as FCS(180) no-op or faults with an undefined instruction error.

Diagnostic Indicators

Before applying the fix, confirm the issue using any of these indicators:

• CX-Programmer dialog during upload: "The program was transferred, but there were problems with the expansion functions".
• PLC ERR/ALM LED is OFF (no fatal) but the FCS rung reads Function code error online.
• Cross-referencing the expansion instruction set in CX-Programmer shows FCS not assigned to any function code (typically 0-255 range, default FCS lives at @FCS(180) or as user-assigned).
• Compared with the project offline: the Expansion Instructions tab shows FCS mapped offline but reads blank or "default" online after upload.

Solution Procedure

The fix is a five-step sequence. Skipping any step (most commonly the power cycle) returns the PLC to the original fault state.

Step 1: Place the PLC in PROGRAM Mode

Using the physical mode switch on the CPM2A CPU or the CX-Programner online "Mode" toolbar button, change the operating mode to PROGRAM. The PLC will not accept expansion instruction changes in MONITOR or RUN. The mode key position is the source of truth; software mode changes are gated by the same switch on most CPM2A units.

Step 2: Open PLC Settings and Navigate to the Startup Tab

In CX-Programmer (versions 3.x, 4.x, 5.x, and 9.x supported):

1. Double-click Settings in the project tree.
2. Select the Startup tab (sometimes labeled Power On or Startup Setting depending on CX-Programmer revision).
3. Locate the Expansion Instructions pull-down on the left side of the dialog.

Step 3: Change Expansion Instructions to "User Settings"

The pull-down has three values in the CPM2A family:

Select User Settings and click Transfer to PLC from the PLC menu (or OK followed by the standard online transfer workflow). The transfer must succeed before the program transfer; otherwise the expansion instruction area remains locked.

Step 4: Upload the Program (Ladder + Expansion Instructions)

With the PLC still in PROGRAM mode, perform the normal ladder program upload. CX-Programmer will now write the expansion instruction set first and the ladder program second. The "problems with the expansion functions" alarm should not appear. Verify the transfer log shows the expansion instruction set was written.

Step 5: Power Cycle the PLC

This is the step most often missed. The CPM2A only commits the new expansion instruction set to its non-volatile execution area on a power-on reset, not on a mode change or on the transfer event. Procedure:

1. Disconnect the power supply to the CPM2A.
2. Wait at least 5 seconds for the internal hold-up capacitor to discharge (the RUN LED must extinguish).
3. Restore power.
4. Observe the boot sequence: PWR LED on, RUN LED on, no ERR/ALM LED.

After the power cycle, the FCS instruction will be active in the expansion instruction set and any rungs using FCS(180) will execute.

Verification

After the power cycle, confirm the fix with these checks:

1. In CX-Programmer, go online and select Edit → Expansion Instructions. Confirm that FCS is shown as assigned to its function code (typically 180 for FCS, displayed with the @-modifier symbol if the differential version is used).
2. Force or trigger the rung containing FCS(180) and watch the result word update correctly. FCS computes a frame checksum on the source word range S through S+N-1 using the algorithm defined in the Programming Manual.
3. Cycle power one more time and re-verify: the expansion instruction set should persist across POR once it has been written via the User Settings path.

Technical Reference: CPM2A Expansion Instruction Architecture

Expansion instructions are optional instruction codes that the CPM2A loads from a separate memory area. Up to 18 expansion instruction slots are available in the CPM2A, and 12 in the CPM1A, in the function code range 0-255 (excluding the standard instruction range). Each slot can be assigned to one of the following expansion instructions per the CPM1/CPM1A/CPM2A/CPM2C/SRM1 Programming Manual (W353):

FCS is the most frequently needed expansion instruction in serial communication projects (calculating checksums for Modbus RTU frames, custom protocols, etc.), so it is the most common one to trigger the upload error described in this article. The same five-step fix applies to any expansion instruction in the table.

FCS Instruction Parameters

The FCS(180) instruction computes an 8-bit two's-complement checksum on a contiguous range of words. From the Programming Manual:

Control word layout:

• Bits 00-07: number of words N (01-255 decimal, 00 = 256)
• Bit 13: 0 = EXCLUSIVE-OR checksum (XOR folding, default for Modbus), 1 = two's-complement checksum (Omron legacy mode)
• Bit 14: 0 = result is rotated right by 1 bit, 1 = result is not rotated (matches Modbus RTU LRC/CRC8 conventions)
• Bit 15: 0 = continue, 1 = clear carry/error flag

For Modbus RTU, the standard settings are: bit 13 = 0, bit 14 = 0, bit 15 = 1, and the resulting byte is appended to the frame low-byte first.

Related CX-Programmer Settings That Interact With This Issue

Workarounds and Alternatives

If the Startup tab remains locked (for example, on a PLC with a forgotten password on PLC Setup, or in a machine where the integrator left the project in Protect mode), the following workarounds are field-proven:

1. Compute the checksum in ladder without FCS: a sequence of XORW instructions followed by a final AND with 00FF produces an identical result to FCS in EXCLUSIVE-OR mode. This avoids the expansion instruction entirely and is portable across all CPM2A units without the Startup setting.
2. Compute the checksum in the SCADA/HMI: push the raw frame bytes up to the host and append the checksum there. This is the cleanest fix for Modbus RTU masters that already have a CRC engine on the host side.
3. Replace the CPM2A with a CP1E or CP1H: the CP1E/CP1H series have FCS as a standard instruction, not an expansion instruction, so the upload protection issue does not exist. This is the recommended path for new designs or for any retrofit where the Startup tab is inaccessible.

Troubleshooting Matrix

Frequently Asked Questions