I’m not a PLC programmer. Not an automation engineer. I’m the office administrator who orders the parts, manages the vendors, and—more than once—has had to explain why production line X is down.
When I took over purchasing for our maintenance department in 2022, I inherited a simple rule: "Always buy original Mitsubishi parts." Easy enough. But in early 2024, with pressure from finance to cut costs, I decided to test that rule. Specifically, on Mitsubishi PLC compatible batteries.
Here’s the thing: the risk with a PLC battery isn’t fire or explosion. It’s downtime. A dead battery means lost programs, corrupted data, and a frantic call to your local Mitsubishi PLC programming training provider to come reload everything.
This is a comparison of two approaches: the OEM path and the compatible path. I’ll walk you through three dimensions—cost, reliability, and the hidden costs of failure—based on our real experience.
Let’s start with the easy one. An original Mitsubishi PLC battery (ER3 or ER6 series, depending on your Q or FX unit) runs about $18 to $30 from authorized distributors. A compatible version? You can find them for $4 to $8 on industrial supply sites.
On paper, I saved $180 on our first bulk order of 30 units. Finance was happy. That’s the kind of saving that gets noticed.
But—and this is the part my spreadsheet couldn’t show—the compatible batteries had a much wider variance in initial voltage. We tested ten out of the box. Two were at 3.2V (acceptable), six were at 3.4V (good), and two were at 2.8V (borderline). The OEM batteries? All 3.6V, consistent, every time.
Not ideal, but workable, I thought. A low-voltage battery still works, right? It lasts a bit less. That’s fine.
Fast forward 8 months. We had replaced batteries across 22 PLC units—mostly Mitsubishi FX5U and Q-series controllers. The OEM batch from the previous year had zero failures. Zero. The compatible batch? We had three failures in 8 months.
One failure was a battery that died completely within 4 months. On a Friday. The line went down, the program was lost, and we had to call in a contractor for emergency reprogramming. That single incident cost us $1,200 in service fees—not to mention the lost production time.
Another failure caused intermittent memory errors. The control panel LED lights flickered strangely, but the diagnostics were inconclusive. A technician spent 3 hours troubleshooting before swapping the battery solved it.
Let me rephrase that: we saved $180 on the initial order. We spent over $1,400 on consequences. Penny wise, pound foolish.
Now, here’s a dimension that’s harder to quantify but matters even more: peace of mind.
After the Friday failure, our maintenance manager didn’t trust the compatible batteries anymore. Every time a line went down for even a minor fault, the first question was: "Is the battery dead again?" That doubt erodes confidence in your equipment.
I’m not a reliability engineer, so I can’t speak to the exact failure modes. What I can tell you from a procurement perspective is this: the cost of checking and rechecking is real. We spent time testing batteries that we never had to test before. We kept emergency stock of OEM batteries anyway, just in case.
The net result? We didn’t save anything. We just shifted the risk onto our own team.
Here’s my honest take, based on our experience:
For non-critical applications—like office equipment or test benches—compatible batteries are probably fine. But for the heart of your automation system? I’ve learned the hard way that the cheapest option often isn’t.
Oh, and about that Mitsubishi PLC programming training we had to schedule after the crash: it was excellent, but I would have preferred not to need it under those circumstances.