If you're picking a PLC platform, start with support, not specs. Here's why.
Look, I'm not an automation engineer. I'm the person who actually buys the PLCs and the training courses and the cables. When I took over purchasing in 2020 for our 40-person systems integration firm, I figured all PLCs were more or less equal. Open the software, write some ladder logic, get the machine running. Turns out, the real differentiator isn't the maximum pulse output frequency—it's whether someone can actually help you when you're stuck.
The conventional wisdom is to pick a PLC based on specs: scan speed, I/O count, pulse output. My experience with 50+ orders across 8 vendors suggests otherwise. Support and programmer familiarity matter more. That's why we standardized on Omron PLCs—specifically the NX and NJ series—not because they're perfect on paper, but because the ecosystem around them makes our engineers lives easier. And a happy engineer means fewer rush orders for me.
The support argument in practice
We had a project last Q4 where a programmer was struggling with the basic programming logic of an Omron PLC—specifically, how to structure a state machine in ladder. Everything I'd read said online forums would have answers. In practice, the Omron distributor's technical line got us sorted in 20 minutes. Not ideal, but workable. That 20-minute call saved us a week of trial and error.
I manage relationships with about 8 vendors for different needs. Some of them are great on price but terrible when something goes wrong. The one who couldn't provide proper invoicing cost us $2,400 in rejected expenses. The one who delivered wrong cables? That made me look bad to my VP when the integration was delayed. With Omron, the ordering process is straightforward (their distributor network is solid), but more importantly, the technical support is included. It's not a separate line you have to pay for.
What about the specs? Pulse output, programming, and training
Obviously specs matter. When someone searches "Omron PLC maximum pulse output frequency" they want to know if the CP1H can handle a 100kHz encoder. According to Omron's own datasheets (OMRON CP Series catalog, 2024), the CP1H can output 4-axis pulse output at 1MHz max (single-phase). The NJ series goes even higher. But spec sheets don't tell you the whole story.
The basic programming logic of Omron PLCs is standard IEC 61131-3 languages—ladder, structured text, function block. Our engineers learned primarily through the Omron PLC training classes. There's a real satisfaction in having a structured program instead of a mess of tangled rungs.
Why I value training over raw specs
Here's the thing: a PLC with amazing pulse output is useless if your team doesn't know how to use it effectively. When we started using the NJ series, we enrolled our team in Omron's basic and advanced programming workshops. That training cut our project setup time by about 30%. Not because the NJ is inherently easier to program (it's more powerful but more complex), because we stopped guessing and started doing things correctly from day one.
We also order a lot of PLC cables and modules. The Sysmac software is free for basic use, but the cable set and module configs can get expensive. I've learned to always order a spare cable—always. A lesson learned the hard way after a cable broke during a site install and we had to overnight a replacement for $80 shipping. That hurt.
Hot tub control panels? Not our thing—but the logic is similar
One weird thing about our role: we handle vendor inquiries for all sorts of equipment. Someone once asked if our Omron PLCs could be used as a hot tub control panel. Technically, yes—a PLC can control heaters, pumps, and sensors. But you'd be better off with a dedicated spa pack controller. Just because you can doesn't mean you should. The boundary is clear: PLCs are for industrial logic control, not consumer appliances. But it's a fun example of how the basic programming logic is universal.
Real talk: The AI buzz and the multimeter
I see a lot of noise about "free AI commercial generators" and AI in PLC programming. Maybe someday. Right now, our engineers still rely on basic electrical diagnostics—like knowing how to use a multimeter to test voltage across a sensor input. All the AI in the world won't tell you if that 24V DC power supply is actually delivering the right voltage. According to Fluke's multimeter guide, you measure voltage between the common (COM) and V terminal, set to DC volts, and look for 24V ±10%. That's a skill, not a prompt.
Small orders matter too
We're not a huge company. When I started, some vendors treated my small orders—$200 worth of cables and a training manual—like they were a bother. The suppliers who took those orders seriously? I still use them for $20,000 orders now.
Omron's distributor network works well for small orders. We buy through a regional integrator who handles the custom programming and support. The key is finding a distributor who treats you fairly regardless of order size. We recently ordered just five modules and a cable set for a proof-of-concept—not a single complaint about minimums. That's rare. Most distributors want a $500 minimum. This particular distributor? No issues.
Small doesn't mean unimportant—it means potential. I'm not suggesting they discount prices for small orders. But the service level should be consistent. That's the test of a good supplier.
Bottom line: What I'd do differently
If I were starting over, I would:
1. Spend more time vetting distributor support before committing to a platform.
2. Invest in training early—it pays for itself.
3. Order spare cables on every PO—especially for custom lengths.
4. Use a multimeter to verify voltage before blaming the PLC for a sensor fault.
5. Ignore the hype around AI automation tools for now—they're not reliable enough for production control.
This was accurate as of early 2025. The PLC market changes fast (especially firmware updates and software versions). Verify current specs and pricing before committing to a purchase. And if you're searching for "how to use a multimeter to test voltage" from scratch, start with a Fluke guide—not random YouTube tutorials.
Between you and me, the best part of finally getting our vendor process systematized: no more 3am worry sessions about whether the order will arrive on time. That's the real win.
