Mitsubishi A-Series to iQ-R Migration Guide
Overview of migrating Mitsubishi MELSEC A-series PLCs to the iQ-R platform. Covers software conversion (GX Works2/3), hardware changes, network migration (MELSECNET to CC-Link IE), and common pitfalls.
Mitsubishi A-Series to iQ-R Migration Guide
The Mitsubishi MELSEC A-series has been a workhorse in Asian manufacturing for decades — particularly in automotive and semiconductor production. With A-series hardware long discontinued, migration to the iQ-R platform (or Q-series as intermediate step) is essential.
Migration Path
The typical path is A-series → Q-series → iQ-R, though direct A→iQ-R migration is possible with GX Works3.
| Component | A-Series | Q-Series (Intermediate) | iQ-R (Target) |
|---|---|---|---|
| CPU | A1SHCPU, A2SHCPU | Q06HCPU, Q26HCPU | R120CPU, R08CPU |
| Software | GX Developer / GPPA | GX Works2 | GX Works3 |
| Network | MELSECNET/10 | MELSECNET/H, CC-Link | CC-Link IE Field, Ethernet |
| I/O | A1SX41, A1SY41 | QX41, QY41 | RX41C2, RY41C2 |
Software Conversion
Use GX Works2 (for A→Q) or GX Works3 (for A→iQ-R):
- Open A-series program in GX Developer
- Export as GX Works2-compatible project
- In GX Works2: Project → Convert → Select target Q/iQ-R CPU
- Review and fix conversion errors
What converts automatically: Ladder logic, basic instructions, timer/counter structures, comments.
What requires manual work:
- System flags (SM400, SM401) — addresses may differ between platforms
- Special function modules — different module numbers and configuration
- MELSECNET communication — must be reconfigured for CC-Link IE
- Interrupt program organization — different OB structure
Key Differences
| Feature | A-Series | iQ-R |
|---|---|---|
| Scan speed | ~100ns/instruction | 0.98ns/instruction (100× faster) |
| Memory | 60K steps max | 800K steps |
| IEC 61131-3 | Partial (Ladder, IL) | Full (ST, FBD, SFC added) |
| Safety | Separate safety system | Integrated SIL3/PLe |
| Cybersecurity | None | Built-in firewall, IP filtering |
Frequently Asked Questions
Can I keep my MELSECNET/10 network?
Q-series supports MELSECNET/H which is backward-compatible with MELSECNET/10 via gateway modules. iQ-R uses CC-Link IE Field natively — a gateway is needed for legacy networks.
Is there a direct conversion tool for A→iQ-R?
GX Works3 can import Q-series projects. For A-series, convert to Q first using GX Works2, then import into GX Works3 for iQ-R.
Analyze your Mitsubishi code →
Maintained by PLCcheck.ai. Not affiliated with Mitsubishi Electric Corporation.
Related Articles
Schneider Modicon to M580: Migration Overview
Overview of migrating Schneider Electric Modicon Quantum and Premium PLCs to the M580 ePAC. Covers the Unity M580 Application Converter (UMAC), hardware mapping, and EcoFit modernization services.
8 min read
migration-guideCross-Platform PLC Migration: Siemens to Allen-Bradley
What to expect when migrating between Siemens S7 and Allen-Bradley ControlLogix. No automatic conversion exists — this guide covers the manual approach, key differences, and planning.
8 min read
migration-guideRSLogix 500 to Studio 5000: Program Conversion Guide
Detailed guide to the software conversion process from RSLogix 500 to Studio 5000 Logix Designer. Covers the Logix Designer Export tool, Project Migrator, file preparation, and post-conversion cleanup.
8 min read
Analyze your PLC code with AI
PLCcheck Pro explains, documents, optimizes, and migrates PLC code — automatically.
Try PLCcheck Pro →Not affiliated with Siemens AG. S5, S7, STEP 5, STEP 7, and TIA Portal are trademarks of Siemens AG.