In March 2022, I approved a bill of materials for a 14-station packaging line. The brand was right. The Omron PLC family was right. The specific model was not. Nobody caught it until we were terminating wires and realized the CPU couldn't output the high-speed pulse the servo needed. Six weeks of programming and wiring were already done. The machine could not run.
My first instinct was to blame the Omron PLC programming software. I rewrote the sequence, changed the timing logic, and ran it in simulation. The software was not the problem. The controller wasn't either. I was.
I'm a controls engineer who has handled automation component orders for eight years. I've personally made and documented 14 significant mistakes totaling roughly $32,000 in wasted budget. Now I maintain our team's checklist so the next person doesn't repeat them. This one was the most preventable.
The Problem I Thought I Had
At the time, I thought the problem was programming. The sequence kept locking up. The timing loop didn't match the mechanical cycle. I convinced myself that if I just found the right instruction or the right subroutine, the machine would behave.
What I didn't want to admit was that I had chosen the controller from memory. 'Omron PLC' is not one product. It's a family of families — CP1, CJ2, NX, NJ — and they are not interchangeable. The model on the drawing looked familiar. The model on the shelf looked identical. The spec sheets told a different story.
According to Omron's published selection documentation (omron.com), some PLC CPU models support pulse output up to 6 MHz. Some don't. The word 'some' is doing a lot of work there. I needed 6 MHz. I ordered a CPU with a lower pulse output. It was that simple.
The Problem Behind the Problem
Let's be honest about the real issue: I was overconfident. I knew I should verify the pulse output specification before ordering. But I thought, 'what are the odds?' The odds caught up with me when the machine builder tested the first axis and got no motion.
The deeper problem was that I was in a hurry. The project was late before I touched it. So I skipped the final spec review because 'it's basically the same as last time.' It wasn't. $4,200 mistake.
I also made a communication mistake that still embarrasses me. I told the distributor I needed a standard Omron PLC. They heard 'the most common budget model.' We both used the same word and meant different things. We discovered this when the wrong CPU arrived. (Note to self: define 'standard' on the purchase order, not in the hallway.)
Looking back, I should have opened the datasheet before I opened the programming software. At the time, the family name seemed like enough. It wasn't.
The timer specification I ignored
In the same project, I ordered a timer module without checking the timer specifications. The repeat accuracy didn't meet the machine's cycle-time requirement. The number was in the datasheet, on a page I never opened. We had to steal a timer from another project to keep moving. The original sat in a drawer.
Timer specifications look boring. That's exactly why they bite. Repeat accuracy, supply voltage tolerance, output switching capacity, ambient temperature range — each one is a chance for a mismatch.
What It Actually Cost Me
Direct cost: $4,200 in rewiring, a replacement CPU, and expedited freight. Indirect cost: one unhappy client, two internal meetings, and a credibility hit.
I can quote the numbers because I documented them. In 2017, my first year, I ordered by part number without checking expansion module compatibility. That cost $890 and a one-week delay. In September 2022, the pulse output mistake cost $4,200. In Q1 2024, after a third client rejection on an I/O list, I finally created the pre-check list we use today.
The numbers said the budget CPU would save us $300. My gut said spend the extra money on the correct pulse output model. I went with the numbers. My gut was right. The $300 would have been invisible in the final quote. Instead, the mistake cost $4,200.
The client never sees the brand on the controller. They see whether the machine worked and whether their deadline was met.
That's brand image. It's worth the extra time.
The Short Version of the Fix
If you're about to specify an Omron PLC, do these four things before you open the Omron PLC programming software:
- Confirm the exact CPU model against the motion requirement. If you need high-speed pulse output, verify the output frequency on that specific model. The family name doesn't guarantee the spec.
- Read the timer specifications as if your deadline depends on it. Because it does.
- Put 'standard model' in writing with the distributor. Same words, different meanings is expensive.
- Treat the contactor supplier like a partner, not a price list. More below.
Looking back, I should have done all of this before the PO. I didn't.
What to look for in a contactor supplier
If you're buying contactors, don't compare only unit prices. Ask for datasheets, batch traceability, and a returns policy. Ask how quickly they answer technical questions before the order. A supplier who disappears after the PO is a supplier you can't afford.
The lowest quoted price is not always the lowest total cost. Total cost includes your time, the delay, and the conversation with a client who had to wait. Quality is the part of the brand that doesn't get photographed.
I still use Omron PLCs. The difference is that now I spend twenty minutes confirming specs instead of six weeks fixing them. (That's the whole lesson, disguised as a checklist.)
