Mitsubishi PLC training — GX Works, FX / Q / iQ-R

Mitsubishi is the controller you will meet on a Gauteng automotive component plant, an injection-moulding hall in Pinetown, or a small Asian-built OEM machine that arrived in a sea container with a Japanese wiring schedule and a panel-door HMI that boots in two languages. If you are starting Mitsubishi PLC training in 2026 and you want a practical view of what to learn, in what order, and which marketing slides to ignore, this is the page. We program FX5U, Q-series and iQ-R daily, we run GX Works2 and GX Works3 side-by-side on the same engineering laptop, and we are not a Mitsubishi Electric Automation reseller. We are an independent training site that thinks the partner courseware is mispriced for self-funded learners and that most of the YouTube alternatives skip the parts that matter when you are standing in front of a real Q03UDV with a fault light blinking.

Where Mitsubishi shows up in SA

The Mitsubishi install base in South Africa is concentrated and specific. Automotive component plants — the tier-1 and tier-2 suppliers that feed the German and Asian assemblers — run a lot of Mitsubishi on smaller cells, mostly because the parent companies in Japan and Korea standardised on it decades ago and the local plants inherited the platform. Plastics processing is the second cluster: injection moulding, blow moulding and extrusion lines built by Asian OEMs ship with FX-series controllers in the cabinet far more often than they ship with anything else. Semiconductor packaging and small electronics assembly is a niche-but-real third cluster, again driven by Japanese OEM machine-build standards.

Where you will not see Mitsubishi much is the heavy-process side of the country. Petrochem leans Siemens and Honeywell, water utilities lean Siemens and Modicon, mining beneficiation is mostly Siemens with pockets of Allen-Bradley. The bottling and packaging halls of FMCG lean Allen-Bradley, particularly in the Western Cape. Mitsubishi sits in the gaps. That is not a small market — it is several thousand controllers across the country, with strong concentrations in Gauteng auto-components and KwaZulu-Natal plastics — but it is a brand you will earn a living on by being one of a smaller pool of competent people, rather than by competing with hundreds of Siemens-trained engineers for the same Eastern Cape interview.

A practical implication for a learner choosing a brand. If you live near a cluster of automotive tier suppliers or a plastics processing town, Mitsubishi will pay your rent. If you are a generalist looking for the broadest job market across the country, learn Siemens or Allen-Bradley first and pick up Mitsubishi as a second brand once you have caught the smell of a fault loop. Most working programmers in SA who run Mitsubishi day-to-day are also fluent in at least one of the two larger brands, because the integrators that hire them work across all three.

The hardware family

Mitsubishi sells a deeper range of controllers than most engineers realise, and the local install base is a snapshot of about thirty years of product evolution. You only need a small subset to be useful on the work that actually exists in South Africa.

FX series. The compact line. The older FX1N, FX2N and FX3U are still everywhere on plastics machines, conveyor sections and standalone OEM skids — the FX3U-32M, FX3U-48M, FX3U-64M and FX3U-80M are common model numbers in panels built between roughly 2008 and 2018. The current generation is FX5U: FX5U-32MT/ES, FX5U-64MT/ES, FX5U-80MT/ES, with the suffix capturing transistor-or-relay output and AC-or-DC supply. FX5U sits on a different IDE story to its predecessors, which we will get to in a moment. The whole FX line is brick-style: CPU and I/O in a single body, with extension blocks that clip onto the right-hand side. No backplane, no chassis, no rack power supplies — just a DIN-rail module and a 24 V DC feed.

Q series. The mid-range modular line that defined Mitsubishi for two decades. Q03UDV, Q04UDV, Q06UDV, Q13UDV, Q26UDV are the high-spec UDV-suffix CPUs you will see on serious automotive cells. The earlier QnH (Q02H, Q06H, Q12H, Q25H) and QnUDE (Q03UDE, Q04UDEH, Q06UDEH) families are still on plenty of brownfield panels. Q-series sits in a backplane chassis (Q33B for three slots, Q35B for five, Q38B for eight, Q312B for twelve) with a separate power supply (Q61P, Q62P, Q63P, Q64P) and dedicated I/O cards (QX41, QX80 for inputs, QY41P, QY80 for outputs, Q64AD for analogue input, Q62DA-N for analogue output).

iQ-R series. The current high-performance line. R04CPU, R08CPU, R16CPU, R32CPU, R120CPU on the standard side, with R04ENCPU, R08ENCPU, R16ENCPU, R32ENCPU, R120ENCPU on the network-integrated side that has the Ethernet port baked into the CPU body. iQ-R sits in a base unit (R33B, R35B, R38B, R312B) with a dedicated power supply (R61P, R62P, R63P, R64P) and a new generation of I/O cards (RX41C4, RY41NT2P, R60AD4, R60DA4). The platform is the modern story for new greenfield installs and for replacement of ageing Q-series cabinets.

iQ-F series. The iQ-F is essentially a re-badging of the FX5U into the iQ branding family — same hardware, same engineering software story. The naming is confusing on purpose because Mitsubishi is trying to unify their marketing around the iQ name while keeping the FX5U product code on the body. Treat them as the same thing.

L series. The forgotten middle child. L02CPU, L06CPU, L26CPU. Modular like Q-series but cheaper, aimed at smaller systems where Q-series was overspec and FX-series was underspec. The platform was discontinued for new sales in 2022 and replaced by iQ-F at the low end and iQ-R at the high end, but you will still find L-series on panels built between 2014 and 2020.

Networks. CC-Link IE Field is the Mitsubishi answer to Profinet on the Siemens side and EtherNet/IP on the Rockwell side. It is a real-time industrial Ethernet protocol, technically excellent, and almost entirely a Mitsubishi-only ecosystem. CC-Link IE Field Basic is the cut-down version that runs on standard Ethernet hardware. CC-Link (the older, non-IE version) is a serial fieldbus that you will still see on older Q-series cabinets — slower, simpler, and good enough for a string of remote I/O drops on a conveyor. SLMP, the Mitsubishi application-layer protocol, is what an HMI or a PC speaks to talk to a controller, and it is what any third-party HMI driver actually uses under the hood.

GX Works2 vs GX Works3

This is where the Mitsubishi engineering experience gets messy. The current state of the engineering software is a split: GX Works2 supports the Q-series, the QnA-series and the FX1/2/3 families, and GX Works3 is the IDE for iQ-R, iQ-F and FX5U. The two products do not overlap. If your client sites run a mix — and most SA integrators do — you install both, and you get used to switching context.

Most SA shops still run GX Works2 daily because the Q-series install base is not going anywhere. There is an honest opinion you should carry into your first job: GX Works2 isn't dead because the Q-series install base in SA isn't shrinking for another decade. The hardware is reliable, the cabinets are paid for, the spares are stocked, and the cost of a controller swap-out to iQ-R is in the order of R200 000 to R600 000 per panel before downtime. Plants do not do that voluntarily. They wait until a CPU dies and there is no replacement on the shelf, and even then half of them buy a refurb Q03UDV from a local stockist instead of upgrading.

GX Works3 is a better IDE. It is built on a more modern Windows codebase, the project file format is XML-based and friendlier to version control, the navigator pane behaves more like a modern tree view, and the tag database is structurally closer to a Studio 5000 controller-scoped tag table than the GX Works2 device-memory model. If you are starting Mitsubishi work today and your shop is buying iQ-R for new builds, you will spend most of your time in GX Works3 and you will be glad of it. Pricing for both products is in the same range as the competitor IDEs — order of USD 1,500 to USD 4,500 per seat depending on tier and whether you bundle GX Simulator2.

GX Developer is the legacy IDE you will occasionally meet. It predates GX Works2, supports the older A-series and earlier Q-series CPUs, and is still installed on the engineering laptops at sites with very old panels. It runs on Windows XP-vintage compatibility and modern Windows 11 installs are awkward — you will probably end up running it inside a virtual machine, the same way Allen-Bradley shops still run RSLogix 500 in a VM for MicroLogix support. Mitsubishi's product page for the engineering software family sits at mitsubishielectric.com/fa/products/cnt/plcgx/index.html.

Languages and addressing

Mitsubishi supports the IEC 61131-3 family on the iQ-R, iQ-F and FX5U platforms — ladder diagram, structured text, function block diagram with embedded ladder, and sequential function chart. The IEC standard itself is the cross-vendor reference for language semantics: iec.ch/standards/iec-61131-3. The older Q-series and FX-series are functionally limited — Q-series in GX Works2 supports LD, ST, SFC and a Mitsubishi-specific MELSAP-L sequence chart, while FX3U is mostly LD-only with some FBD bolted on top.

The addressing model is the part that catches programmers crossing over from Siemens or Allen-Bradley. Mitsubishi uses a letter-and-number device-memory scheme that goes back to the original A-series and was carried forward through every subsequent generation. The core letters are X for input bits, Y for output bits, M for auxiliary memory bits, D for data registers (16-bit by default, paired for 32-bit), T for timers and C for counters. There are more — B, W, R, ZR, SD, SM, L, S, V, Z — but those six are the ones you will use ninety percent of the time.

The catch on Mitsubishi is that timer and counter numbering is allocated, not symbolic. On the older Q-series and FX platforms, you write T0, T1, T2 as actual addresses, and you have to keep track of which timer numbers are in use across the whole project. There is no "give me a fresh timer instance" the way you have on a Siemens IEC TON or a Rockwell TIMER tag. You allocate T0 to T199 to one task, T200 to T255 to another, and you write a memory map in a spreadsheet to keep track. This is a real fault source on inherited projects: a contractor adds a new piece of code, picks T47 because it looks free, and three months later a maintenance fitter realises the conveyor stop timer is sometimes resetting the dryer cycle because two pieces of unrelated code share the same timer number. GX Works3 on iQ-R has a friendlier symbolic-tag layer on top, but the underlying device memory still works the same way.

A small ladder-and-ST snippet showing addressing. A start-stop motor with a thermal overload, written for an FX5U in GX Works3 syntax — sealed-in start X0, stop X1, overload X2, output Y0, an internal seal-in coil M0, and a run-hours counter using a 1-second timer T0:

(* sealed-in start with overload *)
M0 := (X0 OR M0) AND NOT X1 AND NOT X2;
Y0 := M0;
(* hours-run counter, 1 sec base via T0 *)
IF M0 THEN
    T0(IN := TRUE, PT := T#1S);
    IF T0.Q THEN
        D100 := D100 + 1;   (* seconds running *)
    END_IF;
END_IF;

That is the same pattern you would write on a Siemens S7-1200 or a Logix CompactLogix, with different addresses on the front and a different timer-instance story underneath. If you can read that snippet without getting confused by the M0 versus Y0 versus T0 letter scheme, you are most of the way through Mitsubishi PLC training already.

GX Simulator2 — the official simulator

Mitsubishi ships GX Simulator2 bundled with GX Works2 and GX Works3, free with the engineering software once you have a licence. The simulator runs a Mitsubishi controller as a Windows process, accepts your project download from the IDE, and lets you single-step, force device values, watch the device-memory window and trigger inputs by clicking a virtual switch. It is decent. It is not as feature-complete as the IDE side — the network simulation is partial (CC-Link IE Field is partially modelled, CC-Link is not), the I/O scan timing is faster than a real controller, and certain instructions on the iQ-R high-end CPU behave subtly differently to the real hardware on edge cases.

For a learner, GX Simulator2 is what you should be aiming for once you have access to GX Works. The catch is that GX Works itself is a paid-licence install, the trial period is short (usually 30 days), and the official Mitsubishi training organisation is the gatekeeper to the cheaper learning licences. Until you have an employer paying for the IDE, the simulator is out of reach. That is the gap our browser simulator fills.

Where our browser simulator fits

We are not GX Simulator2. We do not pretend to be. We give you something different and complementary. Our simulator runs in a browser tab, with no installation, on any laptop or Chromebook with a current Chrome or Firefox. The scan engine matches IEC 61131-3 semantics — rung-by-rung evaluation, instance data persistence on function block calls, deterministic timer behaviour, and the same race conditions you would see on a real controller when scan order matters.

What you get from us is ladder logic reflexes, IEC 61131-3 semantics, and pattern fluency. You will still need to learn GX Works specifically — the project tree, the Parameter / Program / Device Comment / Device Memory split, the difference between a scan task and a low-speed task on iQ-R, the device-memory allocation discipline that Mitsubishi forces on you, and the CC-Link IE Field configuration story for distributed I/O. We do not replace that. We build the underlying programming brain so the Mitsubishi-specific layer takes weeks instead of months. By the time you sit in front of GX Works for the first time, you already know how a TON behaves when the rung goes false mid-timing, how a sealed-in start-stop reads on the input scan, and what an SR latch does when set and reset rungs fight on the same scan. You can mentally translate the M0 aux bit on a Mitsubishi rung to the M0.0 flag on a Siemens rung to the Conveyor.Run tag on a Rockwell rung — and that translation skill is what makes a multi-brand integrator hireable.

The wiring track and sensor school bridge the gap. The wiring track shows you a labelled QX41 input card and walks you through wiring a 24 V DC sourcing sensor, a dry-contact pushbutton, and a 4-20 mA transmitter through a Q64AD analogue channel. The sensor school covers the 22 sensor types most common on local automotive component and plastics plants, with the engineering-unit scaling you would set inside a Mitsubishi function block.

Cert path

Mitsubishi has a serious factory automation training organisation in Asia and Europe, with formal credentials that mean something in a Japanese or German interview. The South African presence is via Mitsubishi Electric Automation (Pty) Ltd and a small partner network of authorised distributors. There is a Johannesburg office and KZN representation, and the partner courses are delivered in English out of a Midrand training facility for the most part.

A typical Mitsubishi partner course in SA runs four to five days, costs in the range of R15 000 to R30 000, and covers either GX Works2 fundamentals on Q-series, GX Works3 fundamentals on iQ-R, or GX Works3 with FX5U for the smaller-machine market. The lab racks are real hardware. The instructors are working application engineers, often with twenty-plus years on the platform. The certificate is partner-issued, which means it carries weight inside the Mitsubishi integrator world but does not have the same brand recognition as a Siemens SCE Programmer cert or a Rockwell CCAP outside that world.

The honest take. The Mitsubishi partner courses are excellent if your employer is paying. They are reasonable value for self-funded learners compared to the equivalent Rockwell course (which can cost twice as much), and the smaller cohort size means you actually get one-on-one time with the instructor at the lab racks. For a self-funded learner who wants a vendor-neutral cert that travels internationally, the ISA CCST (Certified Control Systems Technician) remains the better self-funded option. CCST is recognised by employers everywhere from Saudi Arabia to Australia, the exam is around USD 600, and it is brand-agnostic. Build the reflexes on our browser simulator first, sit a partner course when an employer is funding it, and pursue CCST if you want a portable credential that is not tied to one vendor's marketing budget. There is a useful overview of Mitsubishi's automation product line history at en.wikipedia.org/wiki/Mitsubishi_Electric for context.

Deep dives on Mitsubishi

The brand pillar above is the overview. The pages below are the topic-by-topic deep reads for someone who has chosen Mitsubishi as their primary platform and wants the specifics. Each is a single-topic page with worked GX Works3 examples and the kind of detail you only learn after a few sites.

1. Mitsubishi GX Works3 function blocks: building reusable logic — the function-block page, with instance handling and the wrap-your-pattern reasoning.
2. Mitsubishi iQ-R vs iQ-F: rack-based vs compact platform pick — the platform-pick page for greenfield projects and machine-builder quotes.
3. Mitsubishi GOT screen design: tags, scripts, and recipes — the GOT2000 HMI side, with the tag-import flow and the script editor that bites newcomers.

Where you'd work with Mitsubishi

Mitsubishi job density in South Africa lines up with automotive assembly and the F&B processing belt — the brand carries a meaningful share of the automotive line-side work because so much of the assembly tooling on local lines was specified out of Japan in the first place. Six city pages cover the regions where GX Works is the platform a panel shop quotes first.

On the Highveld — Joburg and Pretoria — both lean Mitsubishi for parts of their automotive footprint. Mitsubishi PLC training in Johannesburg is the page for the light automation and small-machine work in and around the East Rand industrial belt, while Mitsubishi PLC training in Pretoria is the page for the Tshwane Automotive SEZ, where iQ-F controllers turn up on the smaller line-side jigs and conveyors.

Down on the coast, Mitsubishi PLC training in Cape Town covers the Western Cape automotive components builders, Mitsubishi PLC training in Port Elizabeth is the page for the auto-component feeders into Coega and the Uitenhage assembly lines, and Mitsubishi PLC training in Durban is the page for the Toyota assembly footprint in Prospecton.

In the Free State, Mitsubishi PLC training in Bloemfontein is the page for the regional F&B and agri-processing sites where iQ-F sits on dairy, beverage and grain-handling jobs.

What we don't claim

This page is going to be honest about what we are and aren't. We are not a Mitsubishi-authorised training provider. We have no commercial relationship with Mitsubishi Electric or Mitsubishi Electric Automation (Pty) Ltd. We do not represent the official partner network, we do not issue partner-equivalent certificates, and we do not have access to Mitsubishi proprietary courseware. Our completion certificates are course-level only and have no regulatory standing — not in South Africa and not internationally. We are not SAQA-registered and we are not nationally accredited. We have not pursued QCTO accreditation and we are not MerSETA-accredited either.

What we are: an independent simulator and curriculum that helps you build the reflexes you need before you spend partner-course money or sit a CCST exam. The formal vendor cert is a separate purchase from a separate vendor. We are honest brokers. If you specifically need a SETA-aligned learnership for B-BBEE skills development reasons, we are not the right product. If you want GX-Works-ready reflexes without a paid IDE licence up-front, we are exactly the right product.

How to start

Five steps. Sandbox first — open the simulator, drag a contact and a coil, write your name across the screen in rungs. Then a start-stop with the Mitsubishi addressing equivalence in your head — write the classic three-wire control with a sealed-in start, a stop button, and an output coil, and consciously translate the simulator's address scheme to a Mitsubishi X0 / Y0 / M0 view as you go. Treat M0 as the equivalent of a Siemens M0.0 flag or an Allen-Bradley Motor.Run_Internal aux tag — same role, different syntax. Then a sealed-in motor with overload — add a thermal overload contact and learn what a "field check" interlock pattern looks like before you write one on a real Q-series project. Then a small sequencer using SFC — five-step injection-moulding cycle, with timer behaviour and step-transition logic that maps directly to MELSAP-L steps in GX Works2 and to SFC steps in GX Works3. Then a device-memory map exercise — allocate T0 through T19 to a fictional cell, write down which timer is which, and feel for the first time what the Mitsubishi memory-allocation discipline costs.

Free tier first — no credit card. Spend a weekend on the sandbox and the first few lessons. If the format works, move to Basic at $12 a month. Most learners reach the start of the brand-specific Mitsubishi content in three to four weeks of part-time practice.