PLC I/O Modules and HMI Displays: What I'd Check Before You Order
-
The first lesson: signal type beats module count
-
For analog signals: the ABB AI820 lesson
-
DC input modules: not all 24 V is the same
-
Output modules: relay, transistor, and the thing people forget
-
HMI display panel: the last spec is the first thing users see
-
The checklist I use now
-
When the rules don't apply
If you're about to order I/O modules of PLC systems and an HMI display panel, stop counting I/O points first. The real mistakes happen before the order—when you choose the wrong signal type, miss a power supply compatibility issue, or order the latest revision without checking the drawings. The I/O modules of PLC systems are not interchangeable commodity parts. I've wasted roughly $32,000 learning this, and most of it came from avoidable spec mismatches.
I've been handling control system upgrade orders for 8 years. I've personally made and documented 14 significant mistakes, totaling about $32,000 in rework, expedite fees, and dead-on-arrival hardware. Now I maintain the pre-order checklist for my team. This article is built from those failures.
The first lesson: signal type beats module count
It's tempting to think you can just count inputs and outputs and pick modules. But the same '8-channel analog input' can mean different wiring, isolation, and communication features depending on the module. The number of points is only the beginning. Like, a Danfoss pressure switch with a simple contact output needs a DC input module with the right wetting voltage—not just any input module. Specifying a module without checking the field device's output is the classic mistake I see in old project files (including my own).
For analog signals: the ABB AI820 lesson
If your field transmitters output 4-20 mA, you'll probably look at the ABB AI820. According to ABB's S800 I/O documentation, the AI820 is an 8-channel analog input module with HART capability, configurable for 4-20 mA signals. Here's the catch: 'HART capable' doesn't mean HART is enabled by default. You often need to configure the channel and set the filter time. I once ordered a batch of AI820 modules and assumed they'd work straight out of the box with our HART pressure transmitters. They didn't. Channel configuration was off, and we lost a day on commissioning. (That was a Monday. I remember the Monday.)
The numbers said go with the AI820 because it fit the budget and had enough channels. My gut said the delivery date looked too optimistic. I ignored it. The modules arrived three weeks late, and we had to hand-wire a temporary input to keep a test line running. That's on me.
DC input modules: not all 24 V is the same
DC input modules are the workhorses of machine control. But '24 V DC input' doesn't tell you everything. According to IEC 61131-2, digital inputs are classified by Type 1, Type 2, and Type 3. The differences matter when your sensor leaks current or your cable run is long. A Type 3 input module is usually more forgiving of leakage current from proximity sensors. If you're using a simple pressure switch contact, the module needs to supply enough wetting current to keep the contact reliable. That's not guaranteed by just matching the voltage.
Output modules: relay, transistor, and the thing people forget
Output module of PLC selection gets the same over-simplification. Relay outputs are flexible but wear out. Transistor outputs are faster but care about polarity and loads. If you're switching an inductive load—like a contactor coil—add a flyback diode or other suppression. Without it, the transistor output will fail at the worst possible moment. I know because I smoked a 16-channel DC output module that way. That was the September 2022 incident. The replacement cost wasn't huge, but the downtime was. If you've ever let the smoke out of an output module, you know that sinking feeling.
HMI display panel: the last spec is the first thing users see
You'd think an HMI display panel is a no-brainer. It's not. If you're looking at the Rockwell Automation PanelView 800 series (listed in some catalogs as Panel View 800), check the screen size, the communication driver, and the firmware revision before you order. According to Rockwell Automation's literature, the PanelView 800 family includes 4.3-inch to 10.1-inch displays. A 7-inch PanelView 800 can be perfectly fine for a small machine, but if the controller uses an uncommon protocol, the 'easy' integration can turn into a custom gateway. We once chose a PV800 for a retrofit because the panel space was tight. It worked, but only after two extra design calls and a protocol converter. That's the cost nobody puts in the budget. (Which, honestly, is the real cost.)
And for the small order point: when I was starting out, the vendors who treated my $200 orders seriously are the ones I still use for $20,000 orders. Small doesn't mean unimportant—it means potential.
The checklist I use now
After the third rejected panel drawing in Q1 2024, I created a pre-order checklist. It's not fancy:
- Signal type for every field device: contact, NPN, PNP, 4-20 mA, HART, or thermocouple.
- DC input module type (Type 1/2/3) and whether it supplies wetting current.
- Output module type, load type, and flyback protection.
- HMI display panel communication driver and firmware revision.
- Spare fuses, panel space, wire duct fill—yes, really.
There's something satisfying about a cabinet where every I/O module is labeled and the drawings match the as-built. After the chaos of a rushed retrofit, finally taking the time to do it right is the payoff.
When the rules don't apply
General advice is just general. If you're building a one-off lab setup with spare modules already in stock, you can skip half the checklist. If you're using a PLC with fixed I/O blocks, these lessons still apply but in a smaller way. And if a vendor says a module is a 'direct replacement', verify the part number and the manual. Compatible sometimes means 'it fits but the wiring is different.' (Note to self: trust no one's compatibility list without checking the drawings.)
I still write these steps down for every new module. The checklist stays in a binder next to my desk, and yes, it's saved me more than once.