Mitsubishi PLC Acceptance Checklist: 6 Steps Before You Approve the System

If you're about to accept a new Mitsubishi PLC system—or getting one back from repair—don't sign the paperwork until you've run a verification pass. In my role as a quality compliance manager at an industrial automation company, I review roughly 200 PLC deliveries every year. I've rejected about 12% of first submissions in 2024 alone. The reasons are almost always avoidable: wrong module, broken clip, dead battery, missing certificate.

This checklist is for anyone who accepts control systems: maintenance leads, controls engineers, and procurement people who need to verify deliverables before releasing payment. It works for the FX5U series, Q series, R series, even legacy A series systems—really, any Mitsubishi PLC worth installing. It takes about 45 minutes per cabinet. It's time well spent.

Step 1: Verify Part Numbers Against the Purchase Order

Obvious, right? You'd be surprised how often this step gets skipped—and how often it matters.

Check each module's rating plate against what you actually ordered. A colleague of mine once received a batch of twelve Q series modules where the vendor substituted one model number. The system powered up fine, but the replacement module had different I/O characteristics. The problem surfaced only after production started, when the machine began misbehaving intermittently. Two weeks of troubleshooting before someone compared the part numbers.

What to check:

• CPU module: verify the exact model. For example, in the PLC Mitsubishi FX5U lineup, the FX5U-32MT/ES and FX5U-32MR/ES look almost identical, but the first has transistor outputs and the second has relay outputs.
• Power supply module: confirm input voltage (100–240VAC vs. 24VDC).
• I/O modules: count channels, confirm sink/source configuration.
• Serial numbers: photograph every rating plate. Tedious, but you'll need them for warranty claims.

Step 2: Physical Inspection

Look at every module. Not for aesthetics—look for evidence of rough handling or improper storage.

Check for:

• Cracked DIN rail clips, which are extremely common in transit
• Bent terminal block pins, especially on FX5U units where connectors ship loose
• Discoloration on PCB edges, which signals moisture exposure
• Loose terminal screws on the power supply

A 2023 incident comes to mind. We received a rack of modules that looked fine from the outside—packaging intact, no visible damage. When we rack-mounted them, two DIN rail latches were sheared off. The vendor argued it was "within shipping tolerance." It wasn't. (Surprise, surprise.) Those modules went back, and the replacement set added two weeks to the timeline.

Step 3: Bench Power-Up Test (Multimeter Required)

Before connecting anything to your machine, do a bench power-up test. This is where the multimeter earns its keep.

How to check a PLC power supply with a multimeter—same method I'd use for any DC system:

1. Set the meter to DC volts.
2. Measure the power supply output at the terminals. A 24VDC supply should read between 23.0 and 25.2VDC.
3. Put a load on it (some indicator lamps or relay coils) and measure again. If voltage sags more than 5%, the supply is undersized or failing.
4. Now check the PLC's internal battery. Most Mitsubishi PLC CPUs use a lithium cell for RAM backup. A fresh cell reads about 3.0V; if you're below 2.8V, replace it now. Don't trust the low-battery LED alone—it only triggers at a certain threshold, and you want margin.

This is also how to tell if a car battery is bad with a multimeter: check the resting voltage first, and if it's below 12.4V it's suspect. Then observe the voltage under load—if it drops below 10V during cranking, the battery is done. Same principle, different equipment. A component can show a healthy open-circuit voltage and still collapse the moment it has to deliver current.

The battery check is one of those steps everyone skips until it bites them. In early 2022, I skipped it on a Q series CPU because we were rushing to close out a project. The unit sat on a shelf for three months before installation. When we finally powered it up, the program was gone—the backup battery had died in storage. Rewriting that program cost us roughly $3,000 in engineering time. A 90-second check would have caught it.

Step 4: I/O Verification

Once the PLC is powered up, verify every input and output channel. It's the most time-consuming part, but it's where latent faults surface.

Method:

1. Using GX Works3 (for FX5U and R series) or GX Works2 (for Q series), force each input channel on and off.
2. Confirm the input module's LED responds accordingly.
3. Do the same for outputs: force each one, then confirm both the LED indication and the actual voltage at the terminal with your multimeter.
4. Check sensor power terminals for 24VDC.

If you're working without a fully wired test rig, at minimum verify continuity from field wiring to the module terminals. This catches the classic mistake where the schematic says pin 4 goes to the sensor, but the wire actually lands on pin 5.

Step 5: Program and Parameter Validation

Connect via the programming port and check three things:

• Firmware version. Confirm the CPU firmware matches what your project expects. FX5U units from different production periods may run firmware that behaves differently in edge cases.
• Parameter settings. Verify IP addresses, baud rates, and communication settings against the design documentation. A wrong IP address on an FX5U won't stop the PLC from running—it just silently breaks your HMI connection.
• Program checksum. Compare the checksum of the program stored in the PLC against the checksum in your source file. If they differ, someone loaded a different program than intended, or the program is corrupted.

What most people don't realize is that a PLC can pass every hardware test and still have a corrupted program. The CPU doesn't always flag it—the error LED stays dark, outputs behave normally, until one day the machine does something completely unexpected. The checksum comparison is the only reliable way to confirm what's actually loaded.

Step 6: Documentation and Warranty Registration

Collect everything before you file the paperwork:

• Declaration of conformity (CE/UL) for each module
• Operation manuals (downloadable from Mitsubishi Electric's site if not included)
• Commissioning report signed by whoever installed the system
• Warranty registration for each serial number

Here's something I've learned the hard way: warranty claims that should be approved get denied on procedural grounds when serial numbers aren't registered. And if you financed the purchase through an equipment financing arm like Mitsubishi Corporation Finance PLC, the acceptance documents and serial number registration often become part of the financing agreement. Missing paperwork on the front end means delayed claims, delayed asset registration, and unnecessary friction.

Register first. Ask questions later.

Common Mistakes to Avoid

A few hard-won lessons from my years in quality:

1. Skipping the bench test. Every time I've skipped it (and I've done it more times than I'd like to say), something surfaced during installation that could have been caught in 20 minutes on the bench.
2. Trusting the vendor's test report. I'm not accusing vendors of dishonesty. Their test conditions just aren't your conditions. Your grounding, your wiring, your interference sources. Verify for yourself.
3. Comparing quotes on unit price alone. The cheapest supplier might save you $200 per module, but one delayed delivery or a quality issue requiring return shipping erases that savings quickly. In my experience, the lowest quote has ended up costing more in about half the projects I've managed. Look at the total cost: spare parts availability, technical support responsiveness, logistics reliability, and the price of downtime if the system fails.
4. Forgetting the UPS battery. If your control panel relies on a lithium UPS battery backup, test it under load during acceptance. A UPS with a dead battery gives you zero protection. The LED stays green because the unit receives input power, but the battery won't carry anything when the supply dips. I saw exactly this on a packing line in 2024: the UPS indicator looked fine, a load test exposed a completely dead battery, and the line stopped for 40 minutes during a brief outage.

One more note: the same disciplines extend beyond PLCs. If you're responsible for peripheral equipment—camera systems, sensors, even a battery charger for camera gear on the production floor—the verification principles are identical: part number, physical condition, power test, load test, documentation. The equipment changes; the checklist doesn't.