Omron PLC FAQ: 7 Questions Engineers Ask (Answered by a Quality Inspector)

If you're researching Omron PLCs, you've probably hit the same questions I hear from customers and engineers every week. I review PLC-based control panels before they ship—somewhere around 200 a year, give or take—and I've rejected about 12% of first-time builds in 2024 for I/O undersizing, wrong output modules, and bad enclosure design. Here are the questions that actually come up, answered straight.

What's the difference between Omron's NX, NJ, CJ, and CP series?

Think of them as tiers, not competing products:

• CP1L / CP1H – compact controllers for straightforward machine logic. Great for relay replacement and small standalone equipment.
• CJ – the modular mid-range workhorse. Massive installed base, plenty of I/O and communication modules, and a lot of engineers already know how to program it.
• NJ – adds integrated motion control. If you're running servos and need coordinated movement, this is where it starts to make sense.
• NX – Omron's newer platform. Merges logic, motion, safety, and networking in a way the older lines weren't designed for.

Which one do you pick? It depends on the machine, not the brochure. Once, an engineer spec'd an NJ for a job that needed basic relay logic—complete overkill, and the price showed it. I've also seen a CP1L squeezed into a project that truly needed CJ's I/O capacity. At least, that's been my experience with retrofits over the last few years.

Is the Omron CJ PLC series still worth buying, or should I move to NX?

If you're maintaining existing equipment, CJ is still a reasonable choice in 2025. The installed base is massive, replacement modules are easy to source, and chances are someone on your team already has the software and the experience. And pricing is predictable: a CJ2M CPU with a modest I/O configuration runs roughly $1,200–$1,800 based on distributor quotes we collected in early 2025. Verify current pricing, though—PLC prices move around.

If you're designing a brand-new machine with serious motion and safety requirements, NX gives you more headroom. What most people don't realize is that "newer" doesn't automatically mean "better for your situation." I had a customer spend three weeks porting a CJ program to NX, then switch back because the machine hadn't changed, the cost didn't justify it, and the CJ was already proven on their line.

That said, NX is where Omron is investing. If you're starting fresh and expect the machine to evolve, it's worth the learning curve.

Can an Omron PLC replace a Kenmore control panel or other appliance board?

Technically, yes. A PLC can run the logic for a washing machine, dryer, oven, or similar appliance. You wire the buttons and sensors as inputs, the valves, motors, and heaters as outputs, write the sequence, and you're done.

But should you? For a $75 replacement part, almost never. The PLC itself costs more than that—before you add relays, an HMI, an enclosure, and your programming time. If it's a straight part swap, order the Kenmore control panel replacement and move on.

Where a PLC genuinely makes sense: when the appliance function is part of a larger automated system, or when the OEM board keeps failing because the original design was marginal. We replaced a wash-down station controller in a food plant that was eating relays every few weeks. One CP1L with solid-state outputs fixed it, and it's been running for two years. Total cost, including labor, was less than what they'd spent on replacement relays alone.

Can I build a pellet stove control panel with a PLC?

Yes—and people do. A pellet stove needs ignition sequencing, auger feed timing, temperature monitoring, and airflow control. A compact CP1L handles all of that without breaking a sweat.

But here's something I see missed all the time: safety interlocks. A pellet stove can overfire, overheat, or lose draft in the exhaust path. If your program doesn't watch those conditions and shut down the fuel feed fast enough, you're building a liability. The system needs to fail safe, and in most regions it needs to meet recognized approval standards.

Don't grab a wiring diagram off a forum and expect it to pass any kind of review. I've rejected every DIY stove controller I've seen where the builder skipped the hardwired safety circuit because "the software handles it." Software can crash. A hardwired interlock doesn't.

Glow plug vs spark plug: which makes sense for automated ignition?

People expect a single correct answer here. There isn't one, because the right choice depends on the fuel and the ignition profile you need.

Glow plugs heat up gradually and stay hot long enough to start a sustained burn. That's why you see them in diesel engines and pellet stoves—the ignition source lingers until the flame stabilizes.

Spark plugs deliver an instant, high-voltage spark, but it's not sustained. They work well in gas-fired systems where you need one clean ignition event and the burner does the rest.

For a pellet stove, a glow plug is usually the right call because solid fuel needs prolonged heat to catch. For a gas burner, a spark igniter is simpler and more reliable. Either way, the PLC just sends the signal—you need the correct output stage and driver to match your ignition source. People think the decision comes down to the plug. Actually, it comes down to the whole output circuit and what the fuel type demands.

What software do I need to program an Omron PLC?

Omron's CJ and CP series use CX-Programmer. The NX and NJ family uses Sysmac Studio. If you're working with both generations, you'll have both packages installed.

CX-Programmer is mature, stable, and there's decades of example code floating around. Sysmac Studio is more modern—better motion integration, more capable tag-based programming—but it takes some getting used to if you've spent years in classic ladder logic.

Omron offers training classes for both. If I remember correctly, they run two to three days, but don't quote me on that—it's been a while since I looked at the schedule. If you're self-taught, the online examples and forums are enough to get started, but structured training saves you from the expensive mistakes. I've seen "self-taught" programs that worked fine, and a few that nearly cooked a motor.

What do I actually check before approving a PLC build?

If I'm signing off on a panel, I look at four things:

1. I/O count with spare capacity. I won't approve a build with zero free inputs or outputs. Field changes happen. I want at least 10% spare.
2. Output drive capability. A transistor output is not a relay output. I rejected a batch this year where inductive loads were wired to outputs rated for half the current they'd draw.
3. Environmental specs. Is the PLC rated for the actual cabinet temperature? We had 40 controllers headed for outdoor enclosures in Arizona. The spec said 55°C max, but we measured 61°C inside the enclosure on a hot day. Back to the drawing board.
4. Approvals and markings. UL, CE, or whatever your market requires. Non-negotiable.

If you're buying or building a PLC system, ask for these details up front. It saves everyone a headache later—and it's the difference between a panel that ships and a panel that gets rejected.

There's something satisfying about a clean approval: wiring correct, specs matched, documentation solid, ready for the customer's floor. That's the outcome worth designing around.