CX-One Installation Upgrading from CX-Programmer v5

Overview

Omron's CX-One integrates the full portfolio of OMRON support software into one installer using one license: CX-Programmer, CX-Server, CX-Designer, CX-Simulator, CX-Drive, CX-Motion, CX-Process, CX-Thermo, CX-FLnet, CX-Profibus, and CX-Integrator. Installation media is shipped under catalog numbers such as CXONE-ALDLC-E (multilingual site DVD for Europe), CXONE-AL01C-E (single-seat DVD), and the CXONE-AL__C_E_UP SKU family used for upgrade kits issued to existing owners. The official procedure is documented in the CX-One Setup Manual W444-E1.

This guide consolidates two issues repeatedly encountered in the field when migrating from a standalone CX-Programmer v5 install to a full CX-One deployment:

1. Whether to clean-install or perform an in-place upgrade over CX-Programmer v5/CX-Server.
2. CX-One v1.1 silently disabling the Ethernet service of FinsGateway 2003, breaking the CJ1M-CPU22 pass-through path through an NS-series Touchpanel.

Both problems are tractable; the second is documented and reproducible, and the corrective procedure restores routed programming without full reinstallation of the PLC project.

Prerequisites

CX-One Component Architecture and Catalogue Mapping

CX-One ships a complete tool-chain that replaces single-purpose CD installs. Knowing the mapping matters because the installer toggles which registration keys and COM+ services get overwritten on top of legacy CX-Programmer v5 files.

The CX-One Ver.4 Update Information page lists the minimum component versions: Sysmac Studio (bundled), CX-Motion Pro Ver.1.43 or higher, CX-Drive Ver.2.92 or higher. If you cross-grade between v3.x and v4.x media, the v4 update is applied after the base CX-One DVD install completes.

Decision Matrix: Clean Install vs In-Place Upgrade

Both paths are supported by the installer; the correct choice depends on whether legacy CX-Server or FinsGateway 2003 is in active use on the host machine.

Step-by-Step: Performing the CX-One Installation

1. Insert the CX-One DVD (or mount the ISO). The SETUP.EXE autoruns.
2. Choose Install / Reinstall CX-One.
3. Accept the license agreement; supply the Product Key printed on the sleeve of the DVD case.
4. Select Custom Install to deselect components you do not need (this reduces disk consumption and shortens install time from ~45 min to ~20 min).
5. When prompted for Existing Components Detected, choose Replace / Upgrade to overwrite CX-Programmer v5 with the bundled CX-One equivalent. Choose Keep only if you have a documented reason to retain v5 (none for routine deployments).
6. Monitor the install screen for the dialog Configuring FinsGateway Service. This is where CX-One 1.1 overwrites the FinsGateway 2003 Ethernet driver. Do not skip this step. It is mandatory for proper comm architecture.
7. When install completes, do not reboot immediately. Proceed directly to the verification procedure below if your site depends on FinsGateway 2003 routing.
8. After verification, reboot. The installer registers FinsGateway, CX-Server, and CX-Net as auto-start Windows services.

Troubleshooting: FinsGateway 2003 Ethernet Service Disabled by CX-One 1.1

Problem Description

After installing CX-One v1.1 over a host previously running FinsGateway 2003, the Ethernet service of FinsGateway stops. The result is that routing from an Ethernet-attached PC to a serial-attached PLC through an NS Touchpanel fails. A typical layout is:

PC ---Ethernet--- NS Touchpanel (NS15/NS12/NS10) --- RS-232C Port A --- CJ1M-CPU22
             ^                                                           ^
             |                                                           |
       IP: 192.168.250.10                                       CPU serial port

The NS Touchpanel acts as a pass-through gateway. CX-Programmer opens an Ethernet socket to the NS (UDP 9600), and the NS passes the FINS message out Port A as ToolBus/RS-232C frames to the CJ1M-CPU22. Without the FinsGateway Ethernet service on the host, the CX-Server routing layer cannot dispatch FINS responses back to CX-Programmer.

Root Cause

CX-One 1.1 installs a newer FinsGateway service component (file FgwEther.dll, version ≥ 1.5) but, on hosts where FinsGateway 2003 was previously installed, it disables rather than migrates the Ethernet-driver registration. The behavior was confirmed reproducible on Windows XP SP3 with FinsGateway 2003 (build 2.7.0.1) prior to the CX-One install. Service status observed post-install:

Solution

Re-register the FinsGateway 2003 Ethernet service. Two viable procedures exist; choose the one that matches your site.

Method A — Reinstall FinsGateway 2003 Service Component

1. Open Control Panel → Add/Remove Programs (Windows XP) or Programs and Features (Windows 7/10).
2. Select FinsGateway 2003; choose Repair if offered, else Uninstall.
3. If uninstalled, re-run the original FinsGateway 2003 installer (or run the silent repair: msiexec /fa FinsGateway2003.msi) using the same product key.
4. Reboot.
5. Confirm FinsGateway Ethernet Service is Started and Startup Type is Automatic.

Method B — Re-enable the Existing Service

1. Open services.msc.
2. Locate FinsGateway Ethernet Service.
3. Set Startup type to Automatic; click Start; click Apply.
4. If the Start button fails with error 1053, re-register the COM+ application: at an admin command prompt run FgwEther /RegServer followed by net start "FinsGateway Ethernet Service".
5. Reboot and verify the service stays Started after reboot.

Verification

1. From the host, open CX-Programmer → PLC → Auto Online → Direct Online with the network type Ethernet (FINS/UDP).
2. Confirm the CJ1M-CPU22 is detected through the NS Touchpanel IP address (e.g. 192.168.250.10).
3. Poll the PLC. A typical handshake round-trip is < 80 ms on a 100 Mbit LAN with no other routing hops.
4. Download a small W0.00 = 1 test rung to confirm read/write two-way communication, not just passive connection.
5. Run CX-Net → Route Table and confirm route (Network 0, Node 0) → (Network 0, Node [NS IP]) is defined with the unit number 0 (default).

NS Touchpanel Pass-Through Routing Deep Dive

Cabling and Port A Settings

The NS Touchpanel's Port A is an RS-232C D-sub 9-pin male connector. To pass-through to a CJ1M-CPU22:

Use Omron's XW2Z-200S-CV (2 m) or XW2Z-500S-CV (5 m) pre-built cable; do not home-wire the shield.

CX-Designer Configuration to Enable Pass-Through

1. Open the NS project in CX-Designer v3.x (bundled with CX-One).
2. Select NS → System Settings → Ethernet → Port Settings and assign an IP in the PLC subnet (192.168.250.10 / 255.255.255.0 default).
3. Select Comm. Settings → Serial Port A and set Baud = 19,200 bps, Data 7, Parity Even, Stop 2, Protocol = ToolBus to match the CJ1M-CPU22 default Host Link settings. Switch to FINS protocol only if the application mixes NS ↔ PLC + remote CJ1M-CPU22 routing in the same network.
4. Under System Settings → Comm. Settings → Pass-Through, enable Allow pass-through CX-Programmer; assign the FINS source network number from the host PC (typically 0) and unit 0.
5. Save and transfer the project to the NS. Power-cycle once so the new pass-through table is committed.

CX-One / CX-Programmer v5 Version Compatibility Matrix

If you are installing CX-One 1.1 and need FinsGateway 2003, the safest sequence is to immediately apply the v1.2 service update, which migrates rather than disables the Ethernet service.

Network and Firewall Configuration

FINS/UDP default port is 9600; FINS/TCP is 9600; CX-Server routing uses UDP 9999. On Windows Firewall add these inbound exceptions or disable the firewall on a controlled engineering subnet during pass-through work:

netsh advfirewall firewall add rule name="FINS/UDP" dir=in action=allow protocol=UDP localport=9600
netsh advfirewall firewall add rule name="FINS/TCP" dir=in action=allow protocol=TCP localport=9600
netsh advfirewall firewall add rule name="CX-Server" dir=in action=allow protocol=UDP localport=9999

FINS network number and node must match. For a single-network single-PLC bench: Network = 0, Node = IP last octet if all devices are on the same subnet. For multi-segment configurations use CX-Net → Routing Table Editor.

License and AutoUpdate Management

CX-One uses OMRON's AutoUpdate utility to deliver maintenance releases free of charge. The CX-One product page and the European CX-One product page document that the suite is on online AutoUpdate. To configure:

1. Launch CX-One AutoUpdate from the Start menu.
2. Enter the Product Key when prompted. Activation is stored in %PROGRAMDATA%\OMRON\CX-One\licenses\ as a per-seat entitlement.
3. Click Check for Updates; accept any maintenance updates for installed components only.
4. Schedule updates to occur after hours when CX-One components are not actively driving a runtime project.

Field-Commissioning Checklist

1. Confirm CX-One installs without error; record install log at C:\OMRON\CX-One\Logs\Install.log.
2. Verify FinsGateway Ethernet Service is started; restore via Method A or B if stopped.
3. Ping the NS Touchpanel from the host: ping 192.168.250.10 -n 4. Round-trip time should be < 5 ms on a clean engineering subnet.
4. Open CX-Programmer, go Direct Online → Ethernet (FINS/UDP); confirm the CJ1M-CPU22 is found.
5. Download a 1-rung test program; verify it executes by reading back W0.00.
6. Update the FINS routing in CX-Net, save and export to .fr2 file for the next engineer.
7. Document the CX-One build, CX-Programmer build, CX-Server build, and FinsGateway service version in the site's software baseline register.

Related Procedure Summary