Troubleshooting
Why an HMI Fails to Talk to an FX2n PLC Over 232-BD
Short answer
Moving a value into D8120 only sets the serial format — the link still fails on a wrong driver, an inactive PLC configuration or a miswired cable. Set the format once, through the PLC parameter settings in GX Works or GX Developer or one deliberate D8120 write, match the driver's framing at both ends, then prove the FX2N-232-BD cable pin by pin, in that order.
On this page
Your Pro-face HMI stays silent on an FX2n link through an FX2N-232-BD option board because moving a value into D8120 configures only the serial format. It does nothing for a wrong HMI driver, a configuration that is not actually active in the CPU, or a cable wired to the wrong pins — and the baud rate it changes is one of six things that must agree. Work the fault in this order: confirm the GP-Pro EX driver covers the FX2N-232-BD connection, make exactly one format active at the PLC — either the PLC parameter settings in GX Works or GX Developer, or one deliberate D8120 write — then prove the cable pin by pin.
Check the driver before D8120 #
Open the HMI project in GP-Pro EX and read what is actually selected. In the Device/PLC settings the manufacturer must be Mitsubishi Electric Corporation and the controller the FX Series CPU entry, with the port and interface pointing at the serial path the cable really uses. Then open the driver's connection documentation — Pro-face publishes driver notes and cable diagrams per PLC and per option board — and confirm that exact combination is covered.
RS-232 only moves bits. The driver decides the request format the FX2n must answer, so matching baud rates cannot make the PLC interpret a request built on the wrong protocol. Record from the driver notes:
- the driver and controller selection
- the required PLC communication mode
- the required framing: baud rate, data length, parity, stop bits
- the cable diagram number for the FX2N-232-BD
- any handshake lines that diagram requires
If the notes describe a different connector or interface than the one wired, correct the driver or the path first. Nothing downstream compensates for that.
Make one format active at the PLC #
The FX2n gives you two documented routes to the same setting. The communication format lives in special data register D8120, and the FX communication manual's rule is to set that register to match the external equipment — the HMI side dictates the value. You can load it from ladder logic, or you can enter the communication settings as PLC parameters in GX Works or GX Developer and download them with the project.
A link that stays dead after values were moved to D8120 almost always has a configuration that never reached the CPU or two configurations fighting each other:
- Read the PLC parameter settings back from the connected PLC, not from the offline project.
- Cross-reference D8120 in the program: list every instruction that writes it and the condition that executes each one.
- Monitor D8120 online while the machine runs through its startup conditions. The value on screen once it is running is the format the port is using.
If the downloaded parameters disagree with the driver's requirement, correct and download again. If a rung overwrites them, delete the write or make it load the identical value once, deliberately, before communication starts. Re-downloading parameters while a conflicting write stays active wastes the download.
Worked example: decode the value you are writing #
D8120 is not a baud-rate number; it is a packed 16-bit word. Take a documented one — Advantech's Mitsubishi FX2N driver configuration manual gives E086 hex for its WebAccess driver on an RS-485 board — and decode it:
- Hex E086: E = 1110, 0 = 0000, 8 = 1000, 6 = 0110
- Binary: 1110 0000 1000 0110
- Decimal: 14 × 4096 + 8 × 16 + 6 = 57344 + 128 + 6 = 57478
Each field of those sixteen bits selects one element — baud rate, data length, parity, stop bits, protocol mode, handshake — so one wrong digit changes the port completely while the link still looks connected. It also means values do not transfer between vendors: E086 belongs to that vendor's RS-485 setup, not to a Pro-face RS-232 link over an FX2N-232-BD. Take the value stated in the Pro-face FX connection documentation for the FX2N-232-BD cable diagram and enter that same word, in one place.
Match six settings, then test #
Put the HMI's serial settings beside the PLC's effective settings and compare all six:
- communication mode or protocol
- baud rate
- data length
- parity
- stop bits
- handshake lines where the cable diagram requires them
Baud rate is only bit timing. At 9600 baud a 10-bit character takes 10 ÷ 9600 s = 1.04 ms, so a parity or data-length mismatch corrupts every frame about a millisecond after it leaves the panel: the line toggles, a scope shows activity, and the PLC discards every request. Correct any mismatch at whichever end is easier and retest before replacing hardware. If the settings now match and the driver covers the board, the remaining suspect is the copper.
Prove the cable pin by pin #
The Pro-face FX connection documentation carries a cable diagram for the FX2N-232-BD, listed as cable diagram 10, and limits that cable to 15 m or less. Pull the board's connector drawing from the FX2N-232-BD User's Guide, and read the connector-view convention on both drawings before trusting pin numbers — a mirrored drawing produces a cable that looks correct and lands every signal on the wrong terminal. Pin assignments on the HMI side vary between models, so a cable proven on a different panel is not evidence.
Power down, isolate the cable, and measure continuity on each required connection: transmitter to the opposite receiver, signal ground end to end, and any handshake pair the diagram shows. Check for unintended shorts and include adapters and terminal blocks in the path. The same method is laid out for DH-485 wiring on an HMI replacement RS-232 pin map. If continuity disagrees with the drawings, repair the cable and retest with the verified settings; replacing the option board first leaves this fault untouched.
Apply one configuration and test one value #
- Save the HMI and PLC projects so every later change is identifiable.
- Select the documented driver, controller, port and serial settings in GP-Pro EX.
- Enter the matching format in the PLC parameter settings and download to the connected CPU.
- Remove or align any program write to D8120 so a single route sets the format.
- Cycle power on the PLC and restart the HMI runtime so the new format loads.
- Test one read-only value with a known state — a counter you can watch change in the PLC monitor — with the other HMI requests reduced.
If that value updates, restore the full screen set; a tag that still fails is an addressing or device-type problem, not communication. If it does not, capture the HMI's communication diagnostic and the PLC's parameter readback before changing anything else, one variable at a time. With settings proven and a timeout remaining, the sequence in fixing an HMI PLC communication timeout over serial narrows the remaining causes.
Symptom quick reference #
| Symptom | Most likely cause | Next move |
|---|---|---|
| Nothing updates from the first screen | Wrong driver, wrong port selection, or a format never active in the CPU | Verify driver coverage, read parameters back from the PLC |
| Changing the baud rate changed nothing | Mode, framing or cable still wrong | Compare all six settings, then continuity |
| Works at startup, dies later | A rung overwrites D8120 after parameters load | Cross-reference and monitor D8120 |
| Some values update, others fail | Device type or address errors on those tags | Test failing tags against forced values |
| Intermittent dropouts | Connector movement, interference, or a run near the limit | Re-seat terminations, measure the installed run |
Questions asked
Which driver do I select in GP-Pro EX for an FX2n?
In the Device/PLC settings choose Mitsubishi Electric Corporation, then the FX Series CPU entry that matches your connection path. If the panel exposes more than one serial port, make sure the driver's port assignment points at the physical connector the cable occupies, and confirm the driver notes list the FX2N-232-BD with its cable diagram before configuring anything on the PLC side.
Is E086 the right D8120 value for this connection?
No. E086 hex — 57478 decimal — is the value one vendor documented for its own driver running against an RS-485 communication board, not a Pro-face RS-232 link. The correct word comes from the Pro-face FX connection documentation for the FX2N-232-BD cable diagram. Transplanting another manual's number leaves format fields wrong and the link dead with no fault at the port itself.
How long can the cable to the FX2N-232-BD be?
The Pro-face connection document caps the FX2N-232-BD cable at 15 m or less. If the installed run approaches that limit, shorten it rather than chasing intermittent dropouts, and route it away from drive output cables and other switching noise sources.
Can I reuse an FX serial cable from another HMI?
Not without proving it. Pin assignments on the HMI side vary between models, so a cable proven on one panel can be miswired on the next. Check continuity against the two drawings for your exact pair — the HMI's cable diagram and the board's connector drawing — before powering the link.
Some screens update and others show errors — is the port still at fault?
No. Once a single read-only value updates reliably, the driver, format and cable are proven. Failures limited to specific tags point at device types, address ranges or access settings on those tags. Force a known value in the PLC monitor and test the failing tag against it instead of reopening the port configuration.