Troubleshooting
Connecting a Pro-face HMI to a Q02HCPU Over RS-232
Short answer
A Pro-face HMI and a Mitsubishi Q02HCPU communicate over RS-232 only when four things match: the Q-series driver in the HMI project, the exact port used (CPU or module), the cable wiring from both manuals, and identical serial settings on both ends. Verify all four from the documentation before changing any configuration.
On this page
- Which manuals cover a Pro-face to Q02HCPU RS-232 link?
- Which Mitsubishi driver does the HMI project need?
- Does the cable go to the CPU port or a communication module?
- How do I get the RS-232 cable wiring right?
- Which serial settings have to match on both ends?
- How do I tell a cable fault from a driver mismatch?
- Why does the link come up but show wrong values?
- Questions asked
A Pro-face GP3600 and a Mitsubishi Q02HCPU talk over RS-232 only when four things match: the Mitsubishi Q-series driver selected in the HMI project, the exact serial port the cable lands on, the cable wiring from both manufacturers' diagrams, and serial settings that are identical on both ends. Get all four right and the link comes up; miss one and you get timeouts or dead tags. Pro-face is the HMI manufacturer here, so its support site — not the PLC vendor's — supplies the panel-side drivers and cable drawings. Pull two documents before changing a single setting.
Which manuals cover a Pro-face to Q02HCPU RS-232 link? #
Two documents decide this job: the Pro-face connection guide for its Mitsubishi Q-series driver, and the Mitsubishi manual for the exact RS-232 port you will use — the port built into the Q02HCPU or the port on a separately installed communication module.
On the Pro-face side, the support site groups these under Communication Drivers, one entry per controller family, each carrying the installer, the connection guide and the cable drawings. That entry must tell you three things for your panel:
- that the Mitsubishi Q-series serial driver exists for the GP3600's generation (GP-Pro EX supports the GP3000 series the GP3600 belongs to),
- which serial connector of the panel the connection uses,
- the cable diagram and the serial settings the driver expects.
On the Mitsubishi side, the manual for your exact configuration must tell you:
- which RS-232 ports physically exist — the CPU's own and any communication module fitted,
- which protocols each port can run and where its parameters are set,
- the pin assignment of each connector.
Read the full designation off the HMI nameplate before fetching documentation; the suffix letters identify the variant the manuals must match.
Which Mitsubishi driver does the HMI project need? #
The Q-series CPU driver — Pro-face's driver list names it "Mitsubishi Electric Corporation Q" — installed with GP-Pro EX Ver. 2.10.000 or later; the QnA direct driver and the QnU Ethernet driver are for other CPUs and other ports.
In the project, the selection lives in the controller setup, under the Mitsubishi Q-series serial entry. Three neighbors in that driver list are traps for this job:
- "Mitsubishi Electric Corporation QnA Series CPU Direct Driver" targets the older QnA CPUs.
- "Mitsubishi Electric Corporation Q Series QnU CPU Ethernet Driver" targets built-in Ethernet ports on QnU CPUs.
- A USB or Ethernet selection inherited from another project will search a port you are not wired to.
The symptom of a wrong driver is total: every tag shows a communication error from the first scan, with a perfect cable attached.
Does the cable go to the CPU port or a communication module? #
Decide before you wire anything, because the choice changes the Mitsubishi manual, the cable diagram and the settings page: the Q02HCPU's built-in RS-232 port and an add-in serial communication module are two different configurations.
If the panel uses the CPU's port, that port's protocol and parameters are set in the PLC's serial settings, and the cable follows the CPU manual's diagram. If a serial communication module is fitted, its parameters are configured for that module and its connector has its own pin assignment — never assume the CPU-port settings or cable apply. Record which port the previous arrangement used: a cable that worked on the old panel proves nothing once the link moves to another port, and the port you configured is not always the port you plugged into.
How do I get the RS-232 cable wiring right? #
Build or buy to the two drawings: the Pro-face driver manual's cable diagram for the Q-series connection and the Mitsubishi port manual's pin assignment, checked signal by signal across both.
Check four things on that diagram pair before soldering or ordering:
- where the panel's transmit pin lands on the PLC connector — crossed to the PLC's receive, unless one side crosses internally,
- the signal ground connection between both ends,
- the pin numbering read from the viewing direction the drawing uses; numbering read from the wrong side of a connector swaps signals silently,
- any handshake pins the diagram shows tied, crossed or looped.
Pro-face also sells prefabricated Mitsubishi cables: the accessory line is documented at 500 mm and covers Q, A, FX and Omron PLCs for the GP4000 series; for a GP3600, use the GP3000-series accessory list and match the part to the exact port. Inspect or rewire with the equipment powered down as its instructions require — never swap wires on a live link to hunt for the pairing.
Which serial settings have to match on both ends? #
All of them, one for one: transmission speed, data bits, parity, stop bits, station number and the port's protocol selection — the driver manual's values entered exactly on both devices, with nothing left at a remembered default.
Record both sides of every line before changing anything:
- transmission speed in bit/s, identical on both ends,
- data bits, parity and stop bits,
- the station or PLC number the driver addresses and the number the port answers as,
- the protocol the port runs — the Q-series CPU driver speaks the Mitsubishi MC protocol, so the port's protocol selection and its format options must equal the driver manual's stated values.
One wrong value behaves exactly like a broken cable at the line level: silence. Correct a mismatch only after writing down the current values on both sides, so a change that makes things worse can be reversed.
How do I tell a cable fault from a driver mismatch? #
Test in the order the signal travels — driver, settings, cable, port — because a driver or settings mismatch never completes a single character exchange, while a wiring fault passes nothing or fails when the connector moves.
Work the four match points in that order:
- Driver: the project's controller setup names the Q-series CPU driver and the serial port you are wired to.
- Settings: both settings pages side by side, every line of the list above.
- Cable: with power off, the wiring against both diagrams, then confirm the plug is in the port you configured — CPU port versus module is the classic miss.
- Diagnostics: the HMI's communication status screen and the PLC side's transmit/receive indicators or diagnostic counters separate "no traffic" from "traffic, no valid replies".
| Match point | Where it is fixed | Fault signature |
|---|---|---|
| Driver in the HMI project | Project controller setup | Timeouts from the first scan, good cable notwithstanding |
| Serial parameters | HMI driver settings and PLC port settings | Line silence; diagnostics show no valid replies |
| Cable wiring | Both manufacturers' diagrams | No traffic, or drops when the connector is touched |
| Port selection | HMI port setup and physical connection | The configured port is not the wired port |
Put numbers on "should work". An illustrative one-word poll on a link set to 19 200 bit/s, 8 data bits, even parity, 1 stop bit carries 11 bits per character (1 start + 8 data + 1 parity + 1 stop). A request of about 10 characters plus a reply of about 8 characters is 18 characters × 11 bits = 198 bits, which takes 198 ÷ 19 200 bit/s ≈ 0.010 s of line time — about 10 ms, before the PLC's scan adds its response time. A healthy link refreshes in tens of milliseconds; a timeout counted in seconds means no reply exists at all, and that is a driver, settings or wiring fault, never a link that is too slow.
The same signal-path order applies to Mitsubishi's compact CPUs — see why an HMI fails to talk to an FX2n PLC over 232-BD — and once the link runs but drops, the retry and timeout values are covered in fixing HMI PLC communication timeout over serial.
Why does the link come up but show wrong values? #
When the driver, cable and settings are proven, wrong numbers are an HMI-project fault: check each screen object's device type and address against the devices the PLC program actually uses.
Start with one value you can verify independently — a register you can watch online on the PLC side — and compare it with the panel. Confirm the data type and length the object reads; a 32-bit value read as 16 bits wraps every time the high word changes. If every value on the panel is wrong by the same offset, the fault is the driver's base or offset setting, not the cable. If the values are right but late, the causes live in why an HMI freezes or updates slowly over serial. Write down the driver, the port, the cable part or drawing number and the matched settings, so the next maintainer does not re-derive them.
Questions asked
Can the Q02HCPU's built-in RS-232 port serve the HMI and the programming software at the same time?
No. The port runs whatever single protocol the PLC serial parameters assign to it. When it is set to the protocol the Pro-face Q-series driver speaks, it is no longer your programming connection. If the machine still needs regular serial programming access, add a serial communication module for the panel and leave the CPU port to the programming tool.
Which GP-Pro EX version does the Mitsubishi Q-series driver require?
Pro-face documents GP-Pro EX Ver. 2.10.000 or later as the software requirement for that driver installer, and Pro-Server EX Ver. 1.30.000 or later where the PC-side package is also used. If an older engineering setup cannot install the driver, update the software instead of substituting the QnA or Ethernet driver from the same list.
Will the Mitsubishi cable from our FX panels also fit the Q02HCPU?
Only if the port matches, not just the connector. Pro-face's prefabricated Mitsubishi cable line covers Q, A and FX series in one accessory family — a 500 mm GP4000-series version is documented — but the pinout is drawn per PLC port. Check the Q02HCPU port's diagram, and for a GP3600 use the GP3000-series accessory list.
Is a null-modem or straight-through cable needed between the HMI and the CPU?
Whichever the two diagrams add up to. Read the pin numbering of both connectors in the manuals and follow where transmit on one end must land on the other. Some port pairs cross transmit and receive internally, which cancels the crossing a null modem would add. Build to the drawing and label the cable.
The HMI reports timeouts after a few seconds — could the link simply be too slow?
No. At 19 200 bit/s the line time for a one-word read is about 10 ms, so seconds of silence mean no reply is coming back at all. Work driver, then settings, then cable and port — in that order — before suspecting speed.