IMDHMIControls LibraryShop main store

Selection guide

Selecting a Mitsubishi MELSEC PLC family for your application

PLC programming Published 7 min read

Short answer

Start with MELSEC iQ-F for new compact machines and iQ-R for new modular systems. For an installed FX3, L or Q system, match the CPU, I/O and network requirements and check the exact model’s availability and migration path before ordering.

On this page
  1. Match the task class to the family
  2. The compact end: FX, iQ-F and L
  3. The large end: Q and iQ-R
  4. Safety functions in the controller
  5. Networks, software and retention
  6. Worked example: an eight-axis filling line
  7. The decision by machine class
  8. Verify before you order
  9. Questions asked

For a new machine, start with iQ-F for compact control and iQ-R for a modular system, coordinated motion or a controller-based safety design. On an installed machine, the model on the nameplate matters first. FX3, L and Q systems can have different expansion, programming and replacement requirements even when their I/O counts are similar. Close either decision on the exact CPU, modules, firmware and lifecycle.

Match the task class to the family #

Mitsubishi Electric’s selection guide separates compact and modular families. Use the functional comparison for sizing, then check the manufacturer’s discontinuation bulletins for the exact CPU and each expansion module.

Family Built for Choose it when Settle before ordering
MELSEC iQ-R High-performance control: multi-core CPUs, coordinated motion, high-speed networking Axis synchronization and processing headroom set the scan budget Core count, supported axis count and port count on the exact CPU
MELSEC iQ-F Compact controllers for small-to-mid applications The machine fits one compact chassis with expansion Expansion and axis limits for the exact CPU
MELSEC iQ-R safety iQ-R CPUs with built-in safety functions and safety communication Guard and E-stop functions execute in the controller Safety I/O mix and validation to your required PL or SIL
MELSEC Q Installed modular systems A replacement or retrofit needs to retain specific Q hardware Exact CPU availability, rack, power budget and migration options
MELSEC L Installed compact modular systems A retrofit needs to retain the L-series module layout Exact model lifecycle, modules and migration path
MELSEC FX3 Installed compact machines A repair needs to retain existing wiring or project logic FX3 model lifecycle, I/O match and iQ-F migration options

Read that table as a shortlist, not a sign-off. Each row commits at family level; the last column is where the decision actually closes, on the exact CPU and module.

The compact end: FX, iQ-F and L #

For an installed FX3 machine, identify the CPU, extension modules and terminal types before selecting a replacement. Mitsubishi Electric has published a discontinuation notice for specified FX3U, FX3UC and extension models. For a new small machine, iQ-F includes compact models such as the FX5S and FX5UJ.

FX5U and FX5UC are iQ-F CPUs. Compare the exact model’s communications, I/O, motion and data-logging features. Check the cabinet drawing and wiring clearances against the chosen CPU and modules.

MELSEC L uses modular I/O and function modules. Mitsubishi Electric’s FA-A-0466 bulletin lists affected L-series CPUs, power supplies, I/O and other models. On an L-series repair, check the part numbers in the bulletin and compare a needs-matched iQ-R or iQ-F migration before locking in the cabinet design.

Count I/O and axes first. Then compare terminal types, available modules and the engineering software needed to move the existing project. For a compact new machine, pick the iQ-F model whose documented expansion and communications cover those requirements.

The large end: Q and iQ-R #

Q is a modular line built around racks of I/O, function and communication modules. On an installed Q system, inventory everything the replacement must retain. Mitsubishi Electric’s FA-A-0418 bulletin gives an October 30, 2026 production discontinuation date for specific Q CPUs and lists QnUDVCPU or iQ-R alternatives where applicable.

iQ-R is the high-performance line: multi-core CPUs, coordinated motion and high-speed networking, built for machines whose scan budget is set by axis synchronization rather than I/O count.

For a new machine with synchronized motion, start with iQ-R and verify the axis count and motion hardware. When retaining Q hardware, read how Q series PLC addressing works for I/O and analog modules before allocating the I/O map. On the supervisory side, getting Citect SCADA talking to a Mitsubishi iQ-R PLC walks through the driver path.

Safety functions in the controller #

Mitsubishi Electric lists IEC 61508 SIL 3 and ISO 13849-1 PL e for the specified iQ-R Safety CPU system. SIL and PL belong to different standards. Verify the exact CPU and safety function module, then assess and validate each machine safety function under the applicable standard.

For existing MELSEC-QS or MELSEC-WS installations, use the exact safety controller’s documents and verify its lifecycle separately.

The CPU rating covers the platform, not your machine: every safety function, from guard switch to final contactor, still has to be designed and validated to the PL or SIL the risk assessment demands.

Networks, software and retention #

Ethernet plus fieldbus protocols, with Modbus, PROFIBUS and CC-Link among those named, are portfolio-level capabilities of the MELSEC range. Portfolio is the operative word: confirm the protocol on the exact CPU or communication module before the network design is frozen.

The MELSEC engineering software carries simulation, debugging, graphical configuration and maintenance functions across the families, which is what lets one maintenance team support several of them without retraining per machine.

One retention detail is easy to miss at selection time: across iQ-F and iQ-R CPUs, latch memory is either battery-backed or battery-less. Know difference between battery-backed and battery-less latch memory before fixing the part number, because it decides whether battery replacement becomes a scheduled maintenance item.

Worked example: an eight-axis filling line #

Illustrative example, with the arithmetic shown so you can re-run it on your own machine. The machine: a rotary filling line with 8 servo axes cam-synchronized to a master axis, 260 I/O points across 4 remote stations on Ethernet, guard-door and E-stop functions executed in the controller, and Modbus TCP served upward. The logging runs on an industrial mini PC mounted beside the controller as the line's data logger. The software on that node is its own decision, treated in selecting SCADA software for mixed PLCs and SQL logging.

Weight the requirements by what dominates the machine: motion 35, I/O scale 25, safety 20, networks and logging 20, for 100 in total. Score each family 1 to 5 per criterion from its stated positioning, multiply weight by score and sum; the maximum is 500.

Family Motion (35) I/O scale (25) Safety (20) Networks (20) Total
FX 1 1 1 2 120
iQ-F 3 3 1 4 280
L 2 2 1 2 180
Q 4 5 2 3 365
iQ-R 5 4 3 4 415
iQ-R safety CPU 5 4 5 4 455

Arithmetic for the winner: 35 × 5 + 25 × 4 + 20 × 5 + 20 × 4 = 175 + 100 + 100 + 80 = 455 of 500. For the runner-up: 35 × 4 + 25 × 5 + 20 × 2 + 20 × 3 = 140 + 125 + 40 + 60 = 365.

The scores reflect the example’s assumptions about module variety, motion and safety configuration. Use the vendor’s specifications for any shortlist. For a new machine, remove models with incompatible or unavailable hardware before scoring them.

Decision: shortlist the iQ-R safety configuration for the example at 455 of 500. Confirm the complete safety system first, then verify the CPU, motion modules, supported network topology and availability. The score measures fit for this example.

The decision by machine class #

  • New standalone machine with modest I/O and no synchronized motion: shortlist a compact iQ-F CPU.
  • Compact machine with communications, motion or data handling: verify the exact iQ-F model’s expansion and interfaces.
  • Existing FX3 or L machine: match the hardware and project conversion requirements before choosing a replacement.
  • Existing Q machine: check the installed modules, exact replacement status and iQ-R migration options.
  • Synchronized multi-axis motion under a tight scan budget: iQ-R.
  • Controller-based safety: check the certified iQ-R safety configuration against the required function and validation plan.

Verify before you order #

  • I/O, expansion and axis limits for the exact CPU, not the family's best case.
  • That every special-function module on your list exists for the chosen chassis.
  • The engineering software version that supports the CPU, with simulation and debugging for your language mix.
  • Network ports and protocol support on the exact CPU or module.
  • Latch-memory retention, battery or battery-less, at part-number level.
  • For a safety CPU, validation of each safety function to your required PL or SIL.

Family first, part number second: the first decision sets the architecture, the second proves it.

Questions asked

Is the iQ-F series enough to replace a Q series controller on a mid-size machine?

Often, yes. Add up the I/O points, special-function modules and motion axes the machine actually uses; if they fit inside the iQ-F expansion limit and the motion is a few independent axes rather than synchronized groups, iQ-F is the right-sized choice and saves chassis and engineering overhead. If the build needs modules that only exist in the Q catalog, or I/O keeps growing, stay with Q. The deciding document is the iQ-F expansion and module list for the exact CPU, read against your I/O schedule.

When should a new machine get iQ-R instead of Q?

Give it iQ-R when coordinated motion across several axes, multi-core processing headroom or high-speed network synchronization sets the scan budget, because that is the line iQ-R is built for. Give it Q when the machine is I/O-large but motion-simple, or when the plant already runs Q: a new Q CPU shares spares, modules and the maintenance knowledge your technicians already have, which usually outweighs a performance margin the machine will never use.

What safety ratings do the iQ-R safety CPUs carry?

The documented ratings are SIL 3 to IEC 61508 and PL e to EN/ISO 13849-1. If your machine's risk assessment calls for PL d or SIL 2, the platform sits a step above it; what it does not do is finish the job for you. Each safety function, from guard switch to final contactor, still has to be calculated and validated to that target before the machine runs.

Can I mix MELSEC families on one line?

Yes, and it is normal: an iQ-R line controller coordinating iQ-F or FX station controllers is a workable pattern where machine classes differ, and the families interconnect over the Ethernet-based networks named in the portfolio. Two rules keep it healthy: pick the family per machine, not per preference, and standardize the inter-controller network and tag scheme up front so a mixed line still behaves like one system when you troubleshoot it.

Do iQ-F and iQ-R CPUs need a battery for retentive memory?

It depends on the exact CPU: across the iQ-F and iQ-R range, latch memory is either battery-backed or battery-less, and the choice changes your maintenance list, since a battery is a scheduled replacement item and a battery-less CPU removes that task. Decide at ordering time with the CPU specification in front of you, because this is a detail people discover only when a machine loses its counters after a power cut.

Corrections

  • : Corrected the FX5U family, separated new machine choices from installed-base replacements and clarified the published safety ratings.

Keep reading

  • Selection guide

    How to choose an S7 PLC family for a machine

    For a new machine, pick the S7-1200 when the job is standalone control with modest I/O and one or two axes, and the S7-1500 when you need coordinated motion, controller-integrated safety, a fast scan or a large I/O count. Use S7-300 and S7-400 only to extend plants that already run them. Program both current families in TIA Portal.

    PLC programming

  • Selection guide

    How to size an S7-400 CPU against a PLC-5/40 scan time

    No S7-400 CPU maps one-to-one to a PLC-5/40 by instruction timing, and none needs to: every CPU from the 414 upward is faster on logic execution. Select on memory, I/O and communications capacity, then accept the choice only when the translated program's measured worst-case cycle lands at or below two-thirds of the measured PLC-5/40 scan.

    PLC programming

  • Comparison

    How ControlLogix and S7-400 PLC architectures differ

    A ControlLogix application maps onto an S7-400 only at the requirements level. ControlLogix runs tasks that contain programs and routines on symbolic tags; the S7-400 runs organization blocks that call FBs and FCs against data blocks, mixing symbolic and absolute addressing. Match execution behavior, data ownership and I/O timing — never translate instruction names.

    PLC programming