From FX to R Series: A Quality Inspector's FAQ on Choosing & Using Mitsubishi PLCs

You've Got PLC Questions. I've Got (Hopefully) Helpful Answers.

I'm a quality compliance manager at an industrial automation distributor. Every year, I review roughly 200+ unique PLC-related items—from FX3U modules to Q series racks—before they reach our customers. I've rejected about 12% of first deliveries in 2025 due to spec mismatches, documentation errors, or packaging that wouldn't survive shipping. So, yeah, I've seen a fair share of what works and what doesn't.

This FAQ is my attempt to put some of that experience into simple answers for the questions I get most often from engineers and maintenance teams about Mitsubishi PLCs. No fluff, just what I've learned the hard way (and sometimes the expensive way).

1. FX3U, FX5U, Q, R... Which Mitsubishi PLC Series Should I Choose?

This is the #1 question I field, and the honest answer is: it depends on your application and your team's comfort level. I'll break it down how I break it down for our customers in our annual training sessions.

For basic machines, standalone processes, or retrofitting older equipment:

FX Series (FX3U, FX5U): These are your workhorses for smaller to mid-sized applications. The FX5U is the modern evolution, with Ethernet built-in and support for more memory (up to 80k steps). It's a no-brainer for new, simpler machines where you don't need a massive rack of I/O.
(In my 2023 Q4 audit, we saw a 40% increase in FX5U orders over FX3U—engineers are liking the integrated networking.)

For large-scale, high-speed, or redundant control systems:

Q Series: The long-time standard for complex manufacturing lines. Rock solid, huge range of special function modules (motion, positioning, temperature control). If your machine has 200+ I/O points, Q is probably your answer. The downside? It's older technology. The base units are bigger, and some modules are getting harder to source.
R Series: This is Mitsubishi's high-end, next-gen platform. Faster processing, multi-CPU capabilities (think running safety, motion, and standard logic on one rack), and a ton of built-in security features. It's the best choice if you're designing a brand-new, high-value machine that needs to last 10+ years and be connected to an IIoT network. But it's way more expensive than an FX5U.

My personal decision rule (roughly 80% of the time): If your project has less than 128 I/O and no complex motion, go FX5U. If it's big, legacy, or needs specific Q-series modules you already own, stick with Q. If you're building from scratch and want the best tech available with a larger budget, go R series. (In my opinion, skipping FX5U for a Q series on a 64-I/O project is overkill—and a waste of panel space.)

2. I'm a Beginner. What's the Best Way to Start Learning Mitsubishi PLC Programming?

Great question. I see a lot of new trainees try to jump straight into the deep end with an advanced manual and end up frustrated. Here's the path I recommend based on what's worked for our field service team:

Get the Free Software First. Download GX Works3 (or the older GX Works2 for FX3U/Q series). Mitsubishi offers trial versions, and the base software isn't expensive. Don't buy a PLC yet—learn to write and simulate logic on your PC.
Learn Ladder Logic Fundamentals. You don't need to know Structured Text (SCL) or Function Block Diagrams (FBD) on day one. Ladder logic is the universal language of PLCs. Focus on: contacts, coils, timers (TON/TOF), and counters (CTU/CTD). I recommend the "Mitsubishi PLC Programming Manual" (it's dense, but the examples are gold).
Build a Simple Project. Think “Start/Stop a Motor” or “Count Bottles on a Conveyor.” This forces you to understand addressing (X for inputs, Y for outputs, M for internal relays, D for data registers). (Seriously, 90% of newbie mistakes I see are on addressing—saving a program with an output assigned to a physically impossible terminal.)
Buy a Starter Kit. Once you can simulate, get an FX5U-32MR/ES starter kit with some pushbuttons and LEDs. Wire it up. See the program run in real time. The difference between simulation and physical hardware is massive—and that's where the real learning happens.

"I knew I should have spent more time on addressing fundamentals before jumping into a complex project. Skipped the basics because 'it's just numbers.' That was the one time it mattered—I mapped M10 to a safety relay, and the whole system shut down during commissioning. Rookie mistake, and a $600 lesson in overtime."
— Personal note from my first year as a field tech.

3. What's the Most Common Software or Programming Mistake You See?

Without a doubt: incorrect or missing I/O assignment at the setup stage. In our 2024 Q1 audit, fully 18% of the first-time program submissions we reviewed had a physical I/O map that didn't match the actual hardware layout.

It looks like this:

An engineer writes a program in GX Works3, using X0-X7 for inputs on an FX5U.
They physically connect a start button to input X6—but the program expects that function on X10 (because they added a new safety input module later and didn't re-address the map).
Result: The machine runs, but the start button does nothing. It's a 20-minute fix, but it wastes 2 hours of commission time tracing wires.

How to avoid it: Always, always, always finalize your hardware configuration (make a .csv file from the PLC's module list) before writing a single line of logic. Then, lock the I/O comments in the software. I now require this for every $18,000+ project we ship.

4. Should I Use Structured Text (SCL) or Ladder Logic for My Mitsubishi PLC?

This is one of those debates where people get very passionate. But from a practical, maintenance-friendly standpoint: use ladder logic for the main control flow. SCL (Structured Control Language) is powerful for data handling, complex math, and algorithm development (say, PID loops or advanced diagnostics). But if your plant electrician is going to be troubleshooting this machine at 2 AM on a Saturday, they need ladder logic to understand the logic at a glance.

My rule of thumb:

Ladder: Safety circuits, sequence control, manual/auto modes, interlocking.
SCL: Data conversion, statistical calculations, recipe management, complex shift registers.

If you bury all your logic in SCL functions (which you can do), be prepared to write very detailed comments. I've rejected programs where the SCL was uncommented and the engineer had left 6 months earlier.

5. What About PLC Training? Do You Offer It, and What Should I Look For?

Yes, we offer Mitsubishi Electric PLC training, both in-person at our facility and on-site at your plant. But the question I get a lot is: “Should I just watch YouTube videos?”

YouTube is great for a high-level overview. But there's a reason professional training sticks:

Structured curriculum. You learn in an order that builds on itself—hardware identification → wiring → software → logic → debugging → advanced functions. On YouTube, you'll learn random things in random order.
Hands-on hardware. You're not just watching a screen; you're wiring up an actual FX5U and watching LEDs respond. (I've had trainees in our class say, “Oh, so THAT's what the 'Input LED' actually means when it's flickering!”—something you don't get from a video.)
Q&A in real time. When you hit a snag (“Why is my timer not resetting?”), the instructor can look at your screen and fix it in 30 seconds. That's a 3-hour YouTube rabbit hole avoided.

If you're choosing a training provider, ask these questions first:

Is it certified by Mitsubishi Electric? (Yes, ours is.)
Does it include a PLC and cables? (It should, or you're just watching.)
What's the duration? A good intro course is 3-4 days. Anything less than 2 days is likely a sales pitch, not training.

6. I Tried to Program a Counter, But It Syntax-Locked. Why?

Ah, the dreaded syntax lock in GX Works3. This happens when you're writing in LD (Ladder Diagram) mode and hit a line that the software can't parse as a valid ladder element. It's most common with:

Using a D register incorrectly. Example: LD D0 instead of LD X0 for a contact. The software sees a data register as a value, not a contact, and throws a red cross.
Missing operand. You typed “LD” but forgot the operand address. The syntax checker blocks you.
Using a label that doesn't exist. You wrote “MOV D100 D200”, but D200 is already assigned to a special function module (like an analog input block). GX Works3 will tell you “Device already used.”

Quick fix: Press F7 (Ladder Insert) or check your device usage list. Syntax locks are annoying, but they've saved me from downloading a bad program more times than I can count. (Honestly, I'd rather have a syntax lock than a runtime error that stops production.)

7. I Need to Replace a Q Series Module That's End-of-Life. What Are My Options?

This happens more often than you'd think. Mitsubishi has phased out several Q series modules (like some older QJ71 communication modules). Here's your decision tree:

Check if an R series equivalent exists. The R series often has drop-in replacements for Q series modules with better specs. You might need to adjust your base unit and software configuration, but it's usually a cleaner path than trying to find NOS (New Old Stock) Q modules.
Source from a used market. Some distributors (we're one of them) buy back used Q modules and test them. This is a cost-effective option if your whole system stays on Q series and you just need a functional replacement for a critical line.
Check the official datasheet. Mitsubishi publishes end-of-life notices with last-order dates and recommended successors. Google “[Module Part Number] EOL notice Mitsubishi” and you'll find a PDF. I always recommend keeping a copy of this in your machine's documentation folder.

My rule: If you're depending on a Q series module that is discontinued, buy one spare now. We've seen lead times for discontinued parts get absurdly long—some customers have waited 12 weeks for a module that used to ship in two days.

Final Thought (Promise, It's Short)

I hope this helped clear up some of the questions you probably have on your mind. The best advice I can give from behind my desk: invest in the training and the setup. A good start (right series, proper hardware config, solid software) will save you a ton of headaches later. And if you get stuck, don't just Google—ask someone who's done it before. We're here to help.