CX-Programmer CPM2C-S100-DRT Compatibility Version Requirements

Overview of CX-Programmer and CPM2C-S100-DRT Compatibility

The Omron CPM2C-S100-DRT is a compact CPU module from the CPM2C series equipped with a DeviceNet slave interface (the DRT suffix denotes the DeviceNet remote terminal variant). Programming this CPU requires CX-Programmer, the IEC 61131-3 compliant ladder and structured text development environment for the entire Omron PLC portfolio. A common engineering question concerns the minimum CX-Programmer version capable of recognizing and downloading projects to a CPM2C-S100-DRT.

CX-Programmer V2.0 does not support the CPM2C family. Device-tree entries, CPU type definitions, and instruction set tables for the CPM2C were not introduced until CX-Programmer V2.1. Users holding V2.0 media must therefore either obtain a V2.1 (or later) installer, migrate to the standalone Junior edition at V3.0, or purchase the integrated CX-One automation software suite from Omron.

For shop-floor engineers acquiring a used CPM2C-S100-DRT, the version constraint is the first compatibility gate. The wrong installer produces a "CPU type not supported" dialog, a missing entry in the device-type pulldown, or an offline simulation mismatch that blocks the project transfer step.

CX-Programmer Version Support Matrix for CPM2C

The following matrix summarizes which CX-Programmer versions can create, edit, transfer, and monitor a CPM2C-S100-DRT project. Always validate against the exact build (e.g., V3.0.0.12 vs. V3.0.0.18) on a non-production workstation before committing to a fleet upgrade.

Identifying a Used CPM2C-S100-DRT

Before installing any software, confirm the physical part. The label on the CPU faceplate reads the catalog number and the firmware/ROM version suffix (commonly -V1). The full ordering nomenclature breaks down as follows:

• CPM2C – Compact CPU family (DIN-rail or panel-mount, 24 VDC supply)
• S – Standard I/O count (10 inputs / 6 outputs for the base unit)
• 100 – Program capacity indicator (within the S-body offering)
• DRT – DeviceNet slave (remote I/O) communications interface

Verify the part against the Omron CX-Programmer product page device-support list, which is updated with every CX-One release. If a unit is labeled CPM2C-S100C-DRT (with the trailing C suffix), the CPU uses a different connector family but the same CX-Programmer version rules apply.

Part Numbers and Licensing for CX-Programmer

Omron has restructured CX-Programmer distribution over the product's lifetime. The relevant catalog numbers for a CPM2C-S100-DRT user are:

For a single-CPU, single-engineer deployment centered on a CPM2C-S100-DRT, the Junior SKU (WS02-CXPC1-EJR-V3.0) is generally the lowest-cost route. CX-One becomes attractive only when additional Omron tools (CX-Designer for NS-series HMIs, CX-Motion, CX-Drive, CX-Process, or CX-Integrator for DeviceNet commissioning) are also required.

Why V2.0 Cannot Program the CPM2C-S100-DRT

CX-Programmer V2.0 was released before the CPM2C's market introduction. The installer contains:

• A CPU Type registry tree populated only with CPM1, CPM1A, CPM2A (partial), SRM1, and CQM1/CQM1H entries.
• Instruction libraries that lack the CPM2C-specific expanded instructions (e.g., TXDU, RXDU, PMCR, and the DeviceNet-related DRTU block).
• No DeviceNet configuration plug-in; the DRT suffix cannot be selected, and the associated EDS import path does not exist.

Attempting to start a new project with V2.0 and selecting "CPM2C-S100-DRT" in the device-type dialog results in one of two failure modes:

1. The CPU type is absent from the pulldown, forcing the user to choose a generic CPM2A template, which then fails the parameter check at download time.
2. An attempted project import from a CPM2C source produces an "Unknown CPU type" exception in CXPMAIN.exe before the project tree is rendered.

Both outcomes are correctable only by upgrading to V2.1 or later, or by uninstalling V2.0 entirely and installing a fresh V3.0/V4.0/CX-One package.

Recommended Path: Migrating from V2.0 to a Supported Version

Engineers holding a V2.0 license have three pragmatic paths, in order of increasing capability and cost.

Path A – Junior V3.0 (Lowest Cost)

1. Contact the local Omron representative or authorized distributor and request the WS02-CXPC1-EJR-V3.0 media kit. The Junior SKU is a paid but inexpensive license, not a free upgrade.
2. Uninstall CX-Programmer V2.0 (control-panel removal) to avoid COM-registration conflicts between versions.
3. Install Junior V3.0. The device tree now lists CPM2C, CPM2C-S, and CPM2C-S100-DRT.
4. Create the project, select the correct CPU type, and configure the DeviceNet node address to match the DRT hardware DIP-switch setting (default 0, range 0–63).
5. Connect via the CPM2C's peripheral (RS-232C) port or via the CPM2C-CN111 USB-serial adapter and transfer the program.

Path B – Full CX-One (Longest Support)

1. Purchase CX-One (single-seat license, e.g., CX-ONE-AL01C-E for the latest release).
2. Run the suite installer; select at minimum CX-Programmer, CX-Integrator, and DeviceNet EDS Manager.
3. Open CX-Programmer from the CX-One launcher; create a new CPM2C project.
4. Use CX-Integrator to commission the DeviceNet network: scan the network, add the CPM2C-S100-DRT EDS file, and configure the expected I/O assembly (Poll or Bit-Strobe).
5. Save the integrated project, then transfer from CX-Programmer.

Path C – Find a Used V2.1 License

For shops that only need to read an existing CPM2C program from a used CPU, a V2.1 (or higher) license can be transferred from another engineer's workstation. Omron no longer produces V2.1 media, so the only practical sources are surplus license keys or corporate media libraries. Validate the license key against the Omron License Manager before relying on it.

Step-by-Step: First Program Transfer to CPM2C-S100-DRT

Once a supported CX-Programmer is installed, follow this sequence to confirm end-to-end functionality.

1. Power and ground the CPU. Apply 24 VDC to the RUN/STOP/power terminals; the PWR LED should illuminate solid green and the ERR/ALM LED should be off.
2. Set the DeviceNet node address. Use the two rotary DIP switches on the front face (MAC ID 0–63). The factory default is 63 (0x3F).
3. Set the baud rate. All nodes on a DeviceNet segment must match: 125 kbps (default), 250 kbps, or 500 kbps. Configure via the same DIP block or via software.
4. Connect the programming cable. Use the CQM1-CIF02 (peripheral-to-RS-232) on the CPM2C peripheral port, or CPM2C-CN111 for USB on a modern PC. CX-Programmer will auto-detect the CPU when the Auto Online button is pressed.
5. Create a new project. File → New → Device Type: CPM2C-S100-DRT; Network Type: Toolbus; CPU Name: descriptive string.
6. Write a minimal rung. Insert LD 0.00 and OUT 10.00 to confirm a round-trip download and online monitor.
7. Transfer to CPU. PLC → Transfer → To PLC. Watch for the success dialog and verify the program is in RUN mode.
8. Monitor online. Toggle input 0.00; output 10.00 should follow. Force inputs/outputs only as a diagnostic test; remove all forces before production release.

Verification: Confirming the Active CX-Programmer Version

After installation, verify the build in two ways.

1. Help → About CX-Programmer. The splash and Help dialog report the major.minor build (e.g., "V3.0.0.18"). Confirm this against the table above.
2. Device-type pulldown. In a new project, click the device-type field. The presence of CPM2C-S100-DRT (not just CPM2C) is the definitive proof that the DeviceNet EDS file is registered.

If the pulldown shows CPM2C but not the -DRT variant, the EDS plug-in did not register. Reinstall the DeviceNet manager component (CX-Integrator) and reboot.

Troubleshooting Common Version-Related Errors

CX-One Integration Considerations

Modern Omron development environments bundle CX-Programmer inside CX-One. If a shop later expands beyond the CPM2C-S100-DRT to CJ2, CP1E, NJ/NX, or NS-series HMI, migrating to CX-One unifies:

• CX-Programmer – PLC ladder/structured text
• CX-Integrator – DeviceNet, CompoNet, and EtherNet/IP network configuration (replaces the older CX-ConfiguratorFDT)
• CX-Designer – NS/NSJ HMI screen development
• CX-Motion – Motion controller programming
• CX-Drive – Inverter and servo parameterization
• CX-Process – Process-control loop configuration
• CX-Thermo – Temperature-controller setup

A CX-One single-seat license installed on a workstation can be used to program legacy CPM2C-S100-DRT CPUs without acquiring a separate Junior license, provided the workstation also retains a valid CX-Programmer license activation.

Backup and Project Compatibility Notes

CX-Programmer project files (.cxp) are version-tagged. Once a project is saved on V2.1 or later, it can be re-opened by the same major.minor version or any newer build. There is no formal "save-down" utility, so a project authored in V4.0 cannot be opened in V2.1. The recommended discipline for long-term archives is to keep the most recent CX-Programmer installer media and license key in the same safe as the .cxp files.

Symbol table CSV exports and PLC memory dump files (UM/IO/SR/AR/T/C/DM/HR) are forward-compatible across all versions and remain the most resilient archive format for engineering continuity.

Field-Commissioning Checklist for a Used CPM2C-S100-DRT

1. Verify catalog number CPM2C-S100-DRT on the faceplate; record firmware/ROM suffix.
2. Confirm host PC has CX-Programmer V2.1 minimum, ideally V3.0 Junior or CX-One.
3. Inspect battery: CPM2C has no battery-backed RAM; the program is in flash. Date-code sticker is informational only.
4. Check that all terminal screws are torqued to 0.5 N·m; loose terminals on the DRT connector are the most common cause of intermittent DeviceNet bus-off conditions.
5. Record DIP-switch settings: MAC ID, baud rate, and "Hold/Clear" for outputs in program-stop mode.
6. Perform a clean transfer of a known-good test program and validate each input and output in online monitor mode.
7. Document the installed CX-Programmer version (Help → About) and the .cxp file hash for the project. Store both in the maintenance log.

Standards and Reference Documentation

The CPM2C-S100-DRT DeviceNet interface conforms to the Common Industrial Protocol (CIP) Volume 5 adaptation for DeviceNet, defined in ODVA publications. The peripheral programming port follows Omron's proprietary Toolbus/Host Link protocol (default 9 600 bps, 7-E-2 for the CPM2C). When commissioning, retain the latest ODVA DeviceNet Specification revision on the engineering workstation for CIP message-format questions; CX-Programmer abstracts most of the wire-level details, but custom explicit-message handling on the CPU still requires raw CIP familiarity.