Selection guide
Selecting between Omron CP1, CJ, NX and NJ PLC controllers
Short answer
Choose by architecture: a CP1 for compact machines that fit its built-in I/O, a CJ for modular I/O and special-function expansion, an NX where the machine needs an EtherCAT motion master with safety options like the NX-SL3, and an NJ where multi-core processing carries complex coordinated machines. CJ programs are rewritten, not converted, onto the Sysmac platform, so the installed base matters.
On this page
- The four-way split at family level
- CP1: the whole controller is the CPU
- CJ: modular scale, module by module
- NX: motion, networks and safety on one platform
- NJ: multi-core scale for complex machines
- Migration is a rewrite, not a conversion
- Repair the installed base, select for new machines
- Worked example: a cartoner with three servo axes
- Decision by case
- Questions asked
Pick the family by architecture, not by familiarity. The CP1 is a compact controller with its I/O built into the CPU, and it takes the machine that fits that count. The CJ is the modular family: you assemble the CPU, I/O, special-function and communication modules to the size the machine needs. The NX and NJ are Sysmac machine controllers that combine sequential control with EtherCAT motion — NX at single-machine scale with safety options such as the NX-SL3, NJ with multi-core processing for complex coordinated machines. Every capability below is family-level; the number that closes your order is confirmed per CPU in Omron's documentation.
The four-way split at family level #
The split follows what the controller is, before any model number exists. One language note first: across the portfolio the programming languages are the IEC 61131-3 set — ladder diagram, function block diagram, structured text — so language support is rarely the divider between these families. Architecture is.
| Family | Architecture | Motion | Networks | Choose it when |
|---|---|---|---|---|
| CP1 | Compact controller; digital I/O, analog options and communication ports built into the CPU | No integrated multi-axis motion; machine sequencing | Communication ports on the CPU | The machine fits the built-in I/O count |
| CJ | Modular: CPU plus I/O, special-function and communication modules | Positioning through special-function modules | Communication added as modules | Point counts grow past a brick and CJ spares are already stocked |
| NX | Sysmac machine automation controllers, including the NX102, plus the NX-SL3 safety controller | EtherCAT motion master integrated with sequential control | EtherCAT with EtherNet/IP integration | Coordinated axes, network integration and safety on one platform |
| NJ | Flagship machine controllers with multi-core processors | Integrated motion at platform scale | EtherCAT and high-speed networking | The machine's coordination and data load needs processing headroom |
The per-CPU numbers that decide a boundary — built-in point count, expansion limit, axis count — are datasheet items for the exact model you shortlist.
CP1: the whole controller is the CPU #
The CP1 family puts digital I/O, analog channels and communication ports on the CPU itself, and that is the entire argument for it: one part, wired, programmed, done. Size the machine against the built-in point count first; the per-model expansion limit and the analog channel count are datasheet numbers, and when the machine outgrows them you have crossed into CJ territory rather than stretched the CP1.
There is no integrated multi-axis motion here. Where a compact machine reads an encoder or counts fast pulses, the high-speed counter inputs do that work — if an encoder input is what is sizing your choice, the setup is walked through in configuring a CP1H high-speed counter for an encoder input.
CJ: modular scale, module by module #
The CJ family is a CPU with a row of I/O, special-function and communication modules behind it, so the machine's point count sets the configuration. Its motion answer is the special-function module — position-control hardware added where an axis is needed — which suits independent axes and an installed base that already stocks the modules.
That module answer is also the boundary. Coordinated multi-axis motion on EtherCAT is not something a CJ grows into; that capability lives in the Sysmac families. So the CJ decision is: modular I/O scale, module-based positioning, and standardization on spares you already run. A new machine whose specification says coordinated axes goes straight past CJ to NX or NJ.
NX: motion, networks and safety on one platform #
The NX family is where machine automation starts: controllers such as the NX102 combine sequential control and motion on one EtherCAT network, with EtherNet/IP integration to the equipment around them. Omron positions the line around safety, accurate motion and transparent control — in practice, one engineering environment, one motion network, and diagnostics you can see.
Safety belongs in this family too: the NX-SL3 is a modular safety controller that adapts to the machine type and size. One line on it: the controller is a component — the machine's safety function earns its PL under ISO 13849-1 or its SIL under IEC 61508 through design and validation, and those two ratings are separate.
When the machine controller must exchange EtherNet/IP data with a controller or slave from another vendor, the tag-data-link work is its own task — the failure modes are covered in fixing a TwinCAT EtherNet/IP slave connection from an Omron PLC.
NJ: multi-core scale for complex machines #
The NJ is the flagship side of the same platform: multi-core processors, integrated motion control and high-speed networking, built for machines whose coordination load — many axes, vision results, data handling — is the constraint. The feature overlap with NX is deliberate; the decision is load. A single machine with a handful of axes is NX work. A line section whose processing load limits the control is the NJ case.
Migration is a rewrite, not a conversion #
NJ and NX controllers are engineered in Sysmac Studio, and a CJ program does not carry across. The CJ PID instruction and the Sysmac PID function block are not parameter-compatible, so each loop is rebuilt and retuned and the sequential logic is re-authored. A CJ-to-Sysmac move is re-engineering with full retest, and it belongs in a revamp plan, not in a repair.
Repair the installed base, select for new machines #
These are different decisions. A dead CPU in a running machine gets the same model back in the slot, because the program, wiring and spares are built around it. Family selection — this whole article — applies when the machine is new or the revamp is planned. Mixing the two turns a swap into a project.
Worked example: a cartoner with three servo axes #
Illustrative inputs: a cartoning machine brings 38 digital inputs, 24 digital outputs, 4 analog inputs at 4-20 mA, 2 analog outputs, 3 servo axes (feeder, product conveyor, knife roll), and one guard-door safety function.
The arithmetic:
- 38 + 24 = 62 digital points
- 4 + 2 = 6 analog channels
- 62 + 6 = 68 wired I/O points, plus 3 EtherCAT axes and 1 safety function
The decision walk: three coordinated axes make the controller the EtherCAT motion master, which removes CP1 (built-in-I/O machine) and CJ (module-based positioning, no integrated EtherCAT master at family level). That leaves NX against NJ, and 68 points, 3 axes and one safety function is single-machine scale: an NX-class controller — the NX102 is the documented example — with the guard function on an NX-SL3 safety controller on the same platform. The NJ's multi-core headroom is capacity this machine does not load.
What would move it: double the axes to 6 and add a vision system streaming inspection results into the controller, and the processing-load argument sends the same machine to the NJ. The axis-count and remote-I/O maxima for a given model are datasheet numbers; this decision rests on the architecture split, not on those limits.
Decision by case #
Illustrative cases, decided:
- 40 digital points, one analog input, no motion, tight panel: CP1 — the CPU is the whole controller.
- 250-point process skid, temperature control in special-function modules, a storeroom already holding CJ spares: CJ — modular scale and standardization win.
- 3-axis servo machine with a guard-door safety function: an NX-class machine controller with the NX-SL3.
- A line section with dozens of coordinated axes, vision data and heavy coordination: an NJ multi-core controller.
Wire the decision to the machine's architecture and the migration cost you are willing to carry, then close the per-CPU numbers — point count, expansion limit, axis count, safety rating — against the datasheet for the exact model before you order.
Questions asked
Is there a utility that converts a CJ program to NJ or NX?
No. The path into Sysmac Studio is a rewrite: the CJ PID instruction and the Sysmac PID function block do not share parameters, so every loop is rebuilt and retuned, and the sequential logic is re-entered as IEC 61131-3 function blocks. Schedule it as re-engineering with full retest time, not as a file conversion you do in an afternoon.
Which family do I choose when the machine needs a safety function?
The NX-SL3 is the family's modular safety controller; it scales to the machine type and size and runs alongside the machine controller rather than replacing it. Two checks before you commit: confirm the safety rating of the exact unit against its own documentation, and remember that SIL and PL are separate ratings, so a controller specified to one does not automatically satisfy the other.
Should I replace a failed CP1 with an NX controller?
Not as a repair. A failed CPU in a running machine gets the same model back in the slot, because the program, the wiring and the HMI tags are authored around it. Changing families mid-repair converts a swap into a project with new engineering software, rewritten logic and re-qualification. Apply family selection to new machines and planned revamps only.
Does the NJ replace the NX?
No, the overlap is deliberate. Both are Sysmac machine controllers combining sequential control, EtherCAT motion and EtherNet/IP integration. Pick an NX-class controller for a single machine with a handful of axes, and move to the NJ when the multi-core processing load, such as many coordinated axes plus vision data, is what limits the control.
Can a CP1 or CJ machine grow into servo coordination later?
Not by adding a module to the same program. CJ does positioning through special-function modules, which suits independent axes; coordinated multi-axis motion on EtherCAT belongs to the NX and NJ controllers. Plan that growth at family-selection time, because moving later means a rewrite in Sysmac Studio, not an upgrade you bolt on.