Mitsubishi PLC Specification Guide: A 6-Point Checklist Before You Order

I'm a quality compliance manager at an industrial controls supplier. I review around 1,500 unique part numbers a year—PLCs, relays, drives, contactors—before they reach customers. In Q1 2026, I rejected about 6% of first shipments because of missing suffixes, wrong firmware, or sloppy spec sheets. That's 6% that had to go back, get reworked, or at minimum get an uncomfortable phone call.

This checklist is the one I run through before I approve an order. Use it when you're buying a Mitsubishi PLC, putting together a BOM for an OEM panel, or sourcing bulk relays and VFDs in the same order. It's not a replacement for the official Mitsubishi manual. It's a filter to catch the stuff that turns a two-week delivery into a six-week detour.

One more thing: this is just as useful for distributors as it is for end users. A wrong item on a customer order costs you labor, freight, and credibility. The fix is the same—verify before you commit.

The 6-Point Mitsubishi PLC Specification Guide

Six checks. Do them in order. And don't skip the third one—that's the one most people miss.

1. Pin down the series and CPU model first

"Mitsubishi PLC" on a line item tells your supplier nothing. The series determines the software, the I/O selection, and the communication options. Start with the MELSEC family: iQ-R, iQ-F, Q, L, or FX. Then get the CPU model—for example, R04CPU, FX5U, Q03UDV, or L02CPU. Without that, every other decision is built on sand.

Also decide whether you need a standard PLC or a safety PLC. The two have different architectures, different part numbers, and different programming requirements. If someone tells you the safety version is basically the same, they have a different risk tolerance than you do.

2. Read the full part number, not just the photo

Mitsubishi part numbers carry a lot. A suffix can mean the difference between relay outputs and transistor outputs, between AC and DC power, between built-in Ethernet and no comms. I've seen a PO that listed "FX5U-32MT" and assumed the rest. The vendor could ship something close but not exactly what the machine needed.

Don't rely on a photo either. Photos are often stock images. Get the exact part number from the datasheet and put it on the PO. If the vendor asks for clarification, that's a good sign. If they don't care, that's a bad sign.

3. Confirm the Mitsubishi PLC software and firmware before you commit

This is the step that costs people the most time. The hardware can be perfect, but if your programming tool doesn't support the CPU, the project stops. The Mitsubishi PLC software environment is split around two main packages: GX Works3 for iQ-R and iQ-F series, and GX Works2 for Q, L, and FX series. If you're on an older system, there's GX Developer, but that's legacy—don't plan a new project around it.

Both GX Works2 and GX Works3 follow the IEC 61131-3 standard for PLC programming languages, so you'll see ladder, structured text, function blocks, and sequential function charts. But the project file formats and CPU support are different. GX Works3 cannot open a GX Works2 project with a simple "Open" command. It takes conversion work, and conversion work is where scope creep hides.

Firmware is the other half. A CPU ships with a firmware revision, and that revision can be updated. If you're building ten machines, you want all ten CPUs to have the same firmware. Otherwise, one machine updates fine and the other doesn't—then the spare program behaves differently. (Yes, this happens.)

Ask the supplier for the firmware revision in writing. It takes five minutes and saves a call to tech support later.

4. Check environment, mounting, and power supply

Open the datasheet for the exact CPU and look at the electrical specs. 24VDC or 100-240VAC? Relay or transistor outputs? IP20 panel mount or something with a wider temperature range? These are not options you can upgrade later with a new module. They're basic physical constraints.

"IP20" is common for panel-mount PLCs, but if the cabinet sits in a washdown area, the IP rating of the whole enclosure matters more than the PLC. And if the power supply is wrong, the CPU won't work no matter how clean your program is.

Mounting also matters. Is the PLC on a DIN rail or mounted with screws? Is it vertical or horizontal? Heat affects CPU performance. If the cabinet is sealed and hot, a PLC rated for 0–55°C might still need a fan. Don't argue with the datasheet on this one—it's not personal, it's thermal.

5. Cross-check the I/O plan module-by-module

List every input and output your machine needs, then map it to a module. Count channels, not modules. A 16-channel input module and an 8-channel module can look identical from the front. The wrong module is an expensive discovery at panel testing time.

Don't forget analog inputs, high-speed counters, and safety functions. Mixing standard and safety I/O at the spec stage is extremely common—and dangerous to find later. Also think about spare I/O. If the job calls for 14 inputs and 9 outputs, adding 15% spare capacity costs a little now and saves a lot during commissioning.

6. Apply the same discipline to bulk relays and OEM VFDs

Most orders for industrial controls aren't just a PLC. There's usually a row of relays, a VFD or two, contactors, thermal overloads. And that's where the checklist starts to break down, because people treat bulk items as "basic."

Bulk relay orders need the same part number verification. Check the coil voltage—24VDC vs 110VAC matters. Check the contact rating and the terminal type. A relay that's right for one panel can be completely wrong for another. If you're ordering a thousand relays, a 1% spec error means 10 wrong relays. Actually, it usually means 1,000 wrong relays, because you don't notice until they're all installed.

VFD OEM orders are similar. Drives come with firmware, parameter settings, and sometimes a custom pre-set profile. Ask whether the drives ship with factory defaults or with your requested parameters loaded. If they ship with defaults, your commissioning time goes up. If they ship with custom settings, make sure the settings are the ones you actually approve. Also, check the date code if you're mixing an existing machine inventory. A drive with different firmware can behave differently in a master-slave setup.

Here's something vendors won't tell you: a quote that lists only a brand and series leaves room for interpretation. The more detail you put on the PO, the less room there is for someone to make a "reasonable" substitution you didn't ask for.

Common Mistakes I See on Spec Sheets

Even when people use a checklist, they still miss a few things.

• Missing the suffix. The first part of the part number is not the complete product. If you stop there, you're gambling.
• Forgetting the software license. GX Works2 and GX Works3 are not free. If you're adding a new engineer, include the license in the budget and the lead time.
• Ignoring firmware revisions. Same model number, different firmware, different behavior. It's a real issue, not a technicality.
• Assuming bulk means "lower spec." Bulk relays and OEM VFDs should meet the same specifications as single units. If a vendor offers "bulk pricing" on a product that has no datasheet, run. Actually, don't run—ask for the datasheet first, then run.

The Bottom Line

People think checking specs takes time away from getting the order placed. Actually, it's the opposite. A 5-minute check before you hit send is the cheapest insurance you'll get in industrial controls.

5 minutes of verification beats 5 days of correction.

Looking back, I should have caught the firmware mismatch on that batch of CPUs. At the time, the model number matched perfectly, so we assumed the revision was fine. It wasn't. The exchange took two weeks—or rather, three, counting the freight return. If we had put the firmware revision on the PO, it would've been a non-issue.

Use the checklist. Make your supplier write down the exact part number, software version, and firmware revision. It's not overkill. It's how you prevent the rework that eats your margin.