FX2N PLC Hardware Composition: 2026 Field Guide & FX5U Cross-Reference

Mitsubishi · FX Series · Engineering Notes · 2026-06

By KOEED Editorial · 2026-06-30 · 8 min read · Engineering Notes

The Mitsubishi FX2N series PLC remains one of the most widely deployed small controllers ever shipped — and in 2026 it is also one of the most frequently asked-about legacy systems on KOEED’s RFQ desk. This guide walks through the FX2N hardware composition (CPU, power supply, I/O, special-function modules, backplane bus) and maps every block to its modern FX5U / iQ-F successor so maintenance engineers can plan replacements without re-engineering the whole panel.

AI Summary

• FX2N is a modular Mitsubishi small PLC: base unit + expansion modules on a high-speed backplane bus.
• Five building blocks: CPU, power supply, I/O modules, special-function modules, and the backplane.
• FX2N entered EOL phase years ago; 2026 RFQs focus on replacements and FX5U / iQ-F migration.
• FX5U is the direct modern successor — same form-factor philosophy, Ethernet built in, faster scan.
• KOEED still sources FX2N spare parts alongside FX5U stock; send BOM for cross-reference.

Quick brief: FX2N = legacy Mitsubishi modular PLC (CPU + PSU + I/O + special modules + bus); 2026 buyers usually pair it with FX5U / iQ-F replacements.

What changed since 2024

The original 2024 article on the FX2N hardware composition was a static reference written for engineers maintaining installed bases. The 2026 update reflects three shifts we see in real RFQs landing at Moritta@KOEED.COM:

• EOL inventory is thinner. Mitsubishi’s MELSEC-FX legacy channel stopped accepting new orders for several FX2N- expansion SKUs in 2025. Refurbished and overstock channels are now the primary supply for FX2N parts.
• FX5U / iQ-F is the default successor. Almost every FX2N-to-modern migration brief we write in 2026 lands on the FX5U CPU family with compatible FX5 expansion modules — not on FX3U, which itself is moving toward mature phase.
• Field wiring rarely needs re-do. FX5U keeps the same terminal layout philosophy as FX2N / FX3U, so most panels can swap the CPU and keep I/O wiring intact. That is the single biggest cost saver we see in 2026 retrofit quotes.

FX2N hardware composition at a glance

The FX2N is a compact, modular small PLC. Every FX2N system is built from the same five building blocks, regardless of how many I/O points it ends up with on the panel door:

1. Base unit — houses the CPU, the power supply, and a fixed count of onboard digital I/O.
2. CPU — executes the user program; scan time, instruction set, and memory size determine controller class.
3. Power supply unit — converts incoming AC (or 24 V DC on DC-powered bases) into the low-voltage rails the modules need.
4. I/O modules — digital inputs/outputs, analog inputs/outputs, relay or transistor output variants.
5. Special-function modules — high-speed counters, positioning, communication, analog signal conditioning.

The base unit and expansion modules talk to each other over the backplane bus, which also carries power to the add-on modules — so you do not have to run a separate 24 V wire to each block.

Block 1 — CPU

The CPU is the heart of any FX2N. It runs the user program (ladder logic, instruction list, or structured text written in GX Developer or GX Works2), holds the program memory and retentive data, and arbitrates communication with HMI / SCADA over the built-in RS-422 port or an optional communication module.

FX2N CPUs you will still see in 2026 RFQs include FX2N-16MR, FX2N-32MR, FX2N-48MR, FX2N-64MR, FX2N-80MR, and FX2N-128MR. The suffix matters: MR = relay outputs, MT = transistor outputs, MS = triac (AC) outputs. Picking the wrong suffix is the most common replacement error we see.

Block 2 — Power supply unit

The FX2N power supply is sized to feed the base unit plus all connected expansion modules. AC-input bases accept 100–240 V AC; DC-input bases accept 24 V DC. Internally, the PSU generates the 5 V and 24 V rails the digital and analog modules need.

Modern equivalent: FX5U bases accept the same 100–240 V AC input range and add a service-power 24 V output on the terminal block — that small detail alone removes a separate 24 V power supply in many retrofits.

Block 3 — Digital and analog I/O modules

The FX2N family ships with onboard I/O (typically 16, 32, or 48 points) plus a catalog of expansion blocks. Onboard I/O is what gets wired directly to the panel; expansion blocks are added to the right of the base unit on the backplane connector.

FX2N Block	Function	2026 Status
FX2N-16EX / -16EYR	16-point digital input / relay output expansion	EOL — refurb / overstock only
FX2N-32ER	16 DI + 16 DO relay in one block	EOL — limited stock
FX2N-4AD / -4DA	4-channel analog input / output	Migrate to FX5-4AD / FX5-4DA
FX2N-2LC	2-loop PID temperature control	Migrate to FX5-4LC
FX2N-1PG	Single-axis positioning pulse output	Migrate to FX5-1PG or FX5-20PG
FX2N-232IF / -485IF	Serial communication block	Migrate to FX5-232IF / FX5-485IF

Block 4 — Special-function modules

Special-function modules are where FX2N scales beyond simple discrete I/O. They sit on the same backplane connector as I/O expansions and add capabilities the base CPU cannot deliver on its own: high-speed counting (for encoder feedback), positioning (for stepper / servo pulse trains), analog signal conditioning, and fieldbus bridging.

The defining feature of the FX2N — and the reason it stayed in service so long — is that you can mix several special-function modules on a single base without breaking scan time. A typical 2026 RFQ we still see is an FX2N-48MR base plus an FX2N-1PG positioning block plus an FX2N-4AD for a load-cell feedback loop.

Block 5 — Backplane bus

The backplane connector on the right side of the FX2N base carries both data and power to the expansion modules. You click a module onto the DIN rail, slide it into the connector, and lock it down — no separate 24 V wiring per block. The bus bandwidth is the limiting factor on how many high-speed special-function modules you can stack; for most FX2N applications (under ~6 expansions) the bus is not the bottleneck.

FX2N vs FX5U — the 2026 cross-reference

For a maintenance engineer planning a retrofit, the practical question is: which modern block replaces which legacy block? The mapping below is what we use when we cross-reference an FX2N BOM at KOEED.

FX2N Block	FX5U Equivalent	Migration Note
FX2N-32MR base	FX5U-32MR/ES	Wiring footprint identical
FX2N-48MR base	FX5U-64MR/ES + FX5-8EX/8EYR expansion	Add Ethernet on the base
FX2N-4AD	FX5-4AD	Channel count same, resolution 14→16 bit
FX2N-1PG	FX5-1PG or FX5-20PG	Add Ethernet-based motion option
FX2N-232IF	Built-in RS-485 on FX5U + FX5-232IF	Often the block is no longer needed
FX2N-485IF	Built-in RS-485 + Ethernet on FX5U	Modbus TCP replaces serial where possible

What still runs on FX2N in 2026

FX2N is not “gone” — it is in a long tail. Across our 2026 RFQs, three verticals still ship and service FX2N-based machinery:

• Textile and packaging lines in South and Southeast Asia — installed in the late 1990s and 2000s, still running 16–24 hours a day.
• Water-treatment skid builders in the Middle East — FX2N-32MR plus an FX2N-4AD is a very common compact panel recipe.
• Refurbished machine exporters in Europe — they need genuine FX2N spares to re-certify equipment for end customers.

If you maintain any of these, the FX2N hardware composition still matters — but pair every maintenance RFQ with a “what is the modern replacement?” note so you can plan a phased swap before the legacy channel runs dry.

Field wiring that survives a CPU swap

The single biggest reason FX5U is the recommended successor is wiring compatibility. Across the FX2N → FX5U retrofit projects we have shipped parts for in 2026:

• Power terminals — same L/N/PE layout on AC bases; 24 V DC bases accept the same supply.
• Input terminals — same S/S terminal arrangement for sink/source selection on the 24 V DC inputs.
• Output terminals — relay-output FX5U bases reuse the same COM/NO/NC layout; transistor-output bases use the same +/- pairs, but verify load type before swapping.
• Expansion connector — physically identical, so old FX2N expansions can stay on the bus while you migrate the CPU (verify firmware compatibility per project).

Programming tool shift — GX Developer to GX Works3

FX2N programs are written in GX Developer. FX5U programs are written in GX Works3. Mitsubishi does not provide a perfect automated converter — most projects require manual cleanup of instruction set differences, addressing shifts, and the move from file-based to label-based programming. Plan for a programming hour budget that is roughly 1.5× the original GX Developer time.

Common pitfalls when sourcing FX2N parts in 2026

1. “Compatible” clones are not identical. Third-party FX2N-compatible bases exist; some work, some have scan-time drift. We do not stock them.
2. Firmware revision matters for analog modules. An FX2N-4AD with firmware older than 2.0 can produce 1–2 LSB offset errors. Specify firmware revision when ordering.
3. Battery-backed RAM is aging out. Many FX2N CPUs in the field have never had the CR2450 battery replaced; if the program disappears after a power cycle, that is the first thing to swap.
4. Suffix mismatch on output type. See the Warning callout above — this is the most common returns reason.

Internal links — related on the KOEED blog

• Mitsubishi FX3U to FX5U migration notes — the bridge generation that 2026 retrofits usually skip, but sometimes need.
• Mitsubishi MELSEC collection — full FX / Q / iQ-R / MR-J / GOT range in stock.
• PLC Error Code Database — look up Mitsubishi FX2N / FX5U fault codes by CPU model.
• PLC Hex to Float Converter — for FX5U analog scaling work.
• AI Diagnostic Tool — paste a fault code, get an FX2N / FX5U remediation path.
• Daily PLC News — Mitsubishi restock and firmware updates as they land.

Frequently asked questions

Is the Mitsubishi FX2N still in production?

No. The FX2N entered EOL phase several years ago; new-build units are no longer shipped through normal channels. KOEED sources FX2N spares via overstock, refurbished, and tested-removed-from-service stock — all quoted through Moritta@KOEED.COM.

What is the modern replacement for an FX2N-32MR?

The FX5U-32MR/ES from the iQ-F family is the direct successor: 16 DI / 16 DO relay, built-in Ethernet, RS-485, and the same wiring footprint. For larger I/O counts, move to FX5U-64MR/ES or stack FX5-8EX / FX5-8EYR expansions on the right.

Can I keep my existing FX2N program when migrating to FX5U?

Not directly. FX2N programs are written in GX Developer and use file-based addressing; FX5U programs use GX Works3 with label-based addressing. Mitsubishi does not ship a 1:1 converter; expect manual cleanup of I/O mapping and any FX2N-specific instructions.

What is the difference between FX2N-MR and FX2N-MT output suffixes?

MR = relay outputs (dry contacts, slow, universal load). MT = transistor outputs (sink or source, fast, DC-only). Substituting one for the other without re-wiring can damage the load or the module.

How many expansion modules can an FX2N base unit support?

Up to 8 special-function blocks plus several discrete I/O expansions, limited by the 256 I/O point ceiling of the FX2N CPU and the available 5 V current on the backplane. Practical FX2N installations in 2026 typically run 4–6 expansion modules.

Can KOEED cross-reference an FX2N BOM against FX5U equivalents?

Yes. Send the FX2N BOM (CPU, expansions, special-function modules) to Moritta@KOEED.COM and we return a side-by-side quote listing active FX2N stock alongside FX5U replacements within 24 hours.