How-to
How to Build the HMI Cable for an A1S Programming Port
Short answer
Build the GP2301S-to-A1SCPU-S1 programming-port cable from three documents — the HMI connector table, the driver's connection diagram and the CPU port drawing — reconciled into one wiring sheet by pin number, signal name and viewing direction. Ring out every path before power, then prove one read-only value before any operator command. A connector that fits is not compatibility.
On this page
- What cable does a GP2301S need for the A1SCPU-S1 programming port?
- Which documents define the actual pin layout?
- How do you turn the connector drawings into a wiring sheet?
- What communication settings must match before testing?
- How do you verify the cable before you connect it?
- How do you prove the HMI displays a real PLC value?
- What if the HMI still reports the PLC offline?
- Questions asked
You build this cable on paper before you cut wire. Three documents define the GP2301S-to-A1SCPU-S1 programming-port link: the GP2300/2301 hardware manual's connector table, the Device/PLC connection manual's diagram for this CPU port, and the Mitsubishi drawing of that port. Reconcile their pin numbers, signal names and viewing directions into one wiring sheet, ring out every path with both ends unplugged, then prove one read-only value before any operator command goes live. A connector that fits proves nothing: on both ends, the pinout comes from the documents for the exact models in your cabinet.
What cable does a GP2301S need for the A1SCPU-S1 programming port? #
Either the manufacturer's documented cable for this HMI-to-CPU pairing, or a custom cable whose complete wiring you can check line by line against the driver's connection diagram — those are the two acceptable answers, and a cable that fits is not one of them.
Start at the project, not the soldering iron. The HMI needs a driver that supports the A1SCPU family through the CPU's programming port: a controller name in a selection list tells you the family is supported, while the connection instructions tell you which physical port and which electrical interface the driver actually uses. The GP2300/GP2301 documentation describes the serial ports as 9-pin D-sub connectors; confirm the pin table for your exact model in the connector section before ordering parts.
| Setting or reference | Where to check | What it decides |
|---|---|---|
| HMI model | Nameplate and project hardware selection | Which hardware manual and connector table apply |
| CPU model | CPU nameplate and driver support list | Which driver entry is legitimate |
| Programming-port connection | Driver connection instructions | Which CPU port the cable serves |
| HMI communication port | Project communication settings | Which HMI connector the driver uses |
Which documents define the actual pin layout? #
Three documents define it: the HMI hardware manual's connector table, the Device/PLC connection manual's cable diagram for the A1SCPU programming port, and the Mitsubishi CPU manual's port drawing; a file name or a fitting connector alone proves nothing.
Each answers a different question, and none substitutes for another:
- The HMI hardware manual states what the GP2301S exposes on each pin. For this family that is the GP2300/GP2301 Series User Manual, distributed on the manufacturer's support site under the download file name gp2300_mm21_eng_pdfc.pdf. Check the cover and applicable-model list against your unit: a file name identifies a manual, it is not a wiring specification.
- The Device/PLC connection manual states how the driver wants those signals arranged, including deliberate pin-to-pin links and any adapter. For the GP-PRO/PB III for Windows editor, that manual is distributed under the download file name Manual_gpwplc_ma.pdf; locate the A1SCPU programming-port entry inside it.
- The Mitsubishi AnS CPU manual states what the programming port presents, in the port's own connector drawing with its own viewing direction.
For the assembled result on this exact pairing, a GP2301S to A1SCPU-S1 cable pinout is published; use it to cross-check your finished sheet, not to skip the documents that generate it.
How do you turn the connector drawings into a wiring sheet? #
You reconcile them signal by signal: every connection gets one row carrying the HMI pin and signal, the PLC pin and signal, and any deliberate link, with the viewing direction of each drawing noted before a single wire is cut.
- From the GP2300/2301 connector table, record the pin numbers, signal names and viewing direction of the HMI port the driver uses.
- From the Mitsubishi CPU manual, record the same three facts for the programming port.
- From the driver's cable diagram, record each connection by signal function, plus deliberate links and any required adapter or converter.
- Map every signal to both pin numbers on a single row, keeping each drawing's viewing direction in front of you while you solder — a drawing read from the wrong side mirrors every pin position.
- Add shield and signal-return treatment exactly as the installation instructions state; the shield is not the signal reference unless the documents say so.
| Wiring-sheet field | Where it comes from | What it prevents |
|---|---|---|
| HMI pin and signal | HMI connector table | Using a layout from the wrong HMI port |
| CPU pin and signal | CPU programming-port drawing | Applying another controller's assignment |
| Viewing direction | Caption on each drawing | Mirroring pin positions during assembly |
| Deliberate links and control signals | Driver cable diagram | Omitting a connection the driver needs |
| Shield and reference treatment | Installation instructions | Confusing the shield with the signal return |
| Adapter or converter | Driver connection arrangement | Substituting a passive cable where conversion is required |
Join no unidentified pins, ever. A serial connector can carry functions beyond communication, and an undocumented link can put voltage where a receiver does not expect it. The same document-first method, worked from the HMI end, is how you upload an HMI program without the right cable pinout when the programming cable is the missing piece.
What communication settings must match before testing? #
The HMI driver must sit on the exact port the connection diagram names, with the rate, data format, parity, stop bits and station addressing the driver instructions state — some programming-port connections fix these, so read them rather than tune them.
Enter the driver's values verbatim. Where the settings are adjustable, set them to the documented numbers; where the connection fixes them, copy them from the documentation instead of hunting for an adjustment that does not exist. An HMI can expose more than one serial connector, and the diagram names the one that works. Then transfer the project and confirm the running project is the one you transferred.
The gate to the first live test: driver on the documented port, documented settings entered, verified cable seated at both ends.
How do you verify the cable before you connect it? #
With both ends unplugged and the cabinet powered down, you ring out every specified path and check every pin pair for unintended shorts; the count is fixed by your wiring sheet, and any mismatch sends the cable back to the bench.
Continuity first: each row of the sheet must read low resistance from the HMI pin to the CPU pin it names, deliberate links included. Then shorts: every other pair of pins in use must read open.
Illustrative worked example — suppose your sheet has 6 connections, all on distinct pins at both ends, and the driver diagram joins two of those pins at the HMI end as a deliberate link. Continuity checks: 6 connections + 1 link = 7. Short checks at the HMI end: 6 pins in use give 6 × 5 / 2 = 15 pairs, of which 1 is the deliberate link that must read short, leaving 14 that must read open. Short checks at the CPU end: another 6 × 5 / 2 = 15 pairs, all open. Total before power: 7 + 14 + 15 = 36 measurements, and one unexpected reading sends the cable back.
If your arrangement lands wires on screw terminals, torque them properly: Mitsubishi's FX-family serial communication manual documents 0.5 to 0.8 N·m (5 to 8 kgf·cm) as terminal tightening torque. That number is for terminal blocks — a D-sub hood screw goes snug, not torqued to a serial-wiring spec.
How do you prove the HMI displays a real PLC value? #
Bind one read-only display to a known controller value you can watch change without commanding motion, and read the same address in the PLC programming software as the independent check; the two must track each other before operator commands go in.
Create exactly one object: a read-only numeric display on a value the PLC updates on its own — a cycle counter or a heartbeat bit toggled in logic. Watch it change at the HMI while the same address shows in the programming software. A value that is wrong while communication is healthy is an address, data-format or binding problem in the project, not a cable fault; fix it in the editor, not at the connector. Only when the read-only proof passes do you add write objects, one at a time, in a machine state where an incorrect command cannot move anything.
What if the HMI still reports the PLC offline? #
Read the diagnostics scope first: a device-wide fault points at the port, the interface arrangement, the cable or the controller settings, while a fault on one object points at that object's address or access type — that split decides which end you work.
Record the exact message before touching anything. A device-wide fault lives in one of four places — the selected HMI port, the interface arrangement, the cable, or the controller side covering power, mode and settings — and that is the cheapest order to check them in. A fault confined to one object while the rest of the screen is alive is that object's address or supported access type. On newer Mitsubishi CPUs the same symptom on a front port has its own documented causes, worked through in FX3G front port RS-422 HMI connection that reports PLC off.
Questions asked
Can I copy the pinout from another GP2000 model or another Mitsubishi CPU?
No. Pin assignments belong to the port, not to the connector shape, so a plug that fits can still carry different signals or a different viewing convention. The GP2301S connector table and the A1SCPU-S1 programming-port drawing are the only valid sources for this cable. Where any two documents disagree, the connector tables and the driver diagram outrank anything remembered from another machine.
Where do I get the connection manuals for this legacy pairing?
From the manufacturer's support site or its distributors. The GP2300/GP2301 Series User Manual is distributed under the download file name gp2300_mm21_eng_pdfc.pdf, and the Device/PLC Connection Manual for the GP-PRO/PB III for Windows editor under the file name Manual_gpwplc_ma.pdf. Both state their applicable models on the cover, so verify your unit is listed before building from them.
Do I need a converter between the HMI and the programming port?
Only if the driver's connection diagram shows one. If the documented arrangement for the A1SCPU programming port is a direct cable, build the direct cable; if it names an adapter or converter, that unit is part of the specification and a passive cable cannot replace it. The diagram makes this decision, not a comparison of connector shapes on the bench.
Can two HMIs share one A1S programming port?
No. A CPU programming port carries one master. Two HMIs on a split cable contend for the same port and neither stays reliable. A second HMI belongs on the multi-drop arrangement documented for that CPU family on its communication modules, not on a Y-cable at the programming port.