IMDTouchKnowledge BaseShop main store

How-to

Connecting a Pro-face HMI to a Mitsubishi FX2 PLC

HMI and touchscreens Published 6 min read

Short answer

License GP-Pro EX through Pro-face or an authorized distributor, select the Mitsubishi Electric Corporation FX serial driver for the FX2's built-in programming port, build the cable to the documented pinout, and prove the link with one read-only tag before enabling any writes. A connector that fits proves nothing.

On this page
  1. Start with the nameplates, not the software
  2. Get GP-Pro EX from Pro-face or a distributor
  3. Select the Mitsubishi driver for the FX2 port
  4. Build the cable to the documented pinout
  5. Commission the link with one read-only tag
  6. Worked example: editor 4.09.450 against the 2.10.000 driver minimum
  7. Questions asked

This job is decided before you touch a wire: the engineering software licensed through Pro-face or an authorized distributor, the Mitsubishi serial driver selected for the FX2's built-in programming port, and a cable built to the documented pinout. A connector that fits proves nothing about compatibility. Commission one read-only tag and watch it track the controller before the first write goes live. For the software, Pro-face's own download area lists full-install and trial versions of GP-Pro EX; permanent deployment is a license through Pro-face or a distributor, not an installer archive from a file-sharing link.

Start with the nameplates, not the software #

Read the complete HMI model off the panel nameplate and the complete PLC designation off the controller, suffixes included. "A Pro-face and an FX2" identifies two product families; it does not identify a port, a driver, or a cable.

The FX2 and the FX2N are different generations of the MELSEC-FX family. The compact communication boards that fit an FX2N base unit — the 232-BD in why an HMI fails to talk to an FX2n PLC over 232-BD — are not options on an FX2. The FX2 connects through its own built-in programming port, an RS-422 interface like the one covered in connecting a PanelView Plus to a Mitsubishi FX PLC over RS-422.

If the panel already runs an application, record its communication configuration before you change anything: driver, port, and which objects fail. A blank or unconfigured panel needs a project built from scratch.

Get GP-Pro EX from Pro-face or a distributor #

GP-Pro EX is the Pro-face engineering package that carries native MELSEC drivers, but the panel model decides whether it is the right editor for your unit. Run that check before you install anything, the way checking HMI engineering software before a panel replacement walks through it. The manufacturer's download area lists a Full Install Version and a Trial Version of the GP-Pro EX family; a permanent deployment on a plant floor needs licensing through Pro-face or an authorized distributor.

Keep two connections apart from here on. The engineering-computer-to-panel transfer link proves only that the PC can reach the panel; the panel-to-PLC runtime link is a separate path with its own driver, port, and cable. And do not count on recovering the project from the panel: an upload done with GP-Pro EX returns what the editor's documented upload capability allows, which is often less than the original editable source, so keep the source on the engineering computer.

Select the Mitsubishi driver for the FX2 port #

In a new GP-Pro EX project, the Device/PLC settings screen — the second screen of project creation — is where the controller driver is selected. For a serial link to the FX2's programming port, the driver family is the Mitsubishi Electric Corporation FX serial communication driver. Its documented installer requirement is GP-Pro EX Ver2.10.000 or later; the same listing names Pro-Server EX Ver.1.30.000 or later for setups that include that PC package. Driver support kept moving after that floor was set — GP-Pro EX Ver. 4.09.450, released 19 December 2022, upgraded the communication driver function with additional Mitsubishi Electric support — so install a current release rather than an old one.

Match the runtime port in the project to the physical connector the cable will use, and match the serial format to the PLC port settings wherever they are configurable. Where the FX programming port runs a fixed protocol format, leave the driver's documented settings alone. If your architecture later moves the controller side to Ethernet, the driver changes to FX Series Ethernet (MELSEC-FX) — a selection that belongs to controllers carrying an Ethernet interface, not to the FX2 base unit.

Build the cable to the documented pinout #

Specify the cable from the connection documentation for your exact panel model and the FX2 programming port. Connector shape identifies nothing: RS-422 differential pairs and RS-232 single-ended signals live on overlapping connector families, and a cable that fits both ends can still cross transmit and receive or mix the two standards. Where both ends are genuinely RS-232, the wiring discipline in connecting a Pro-face HMI to a Q02HCPU over RS-232 is the pattern to follow; where the panel port is RS-232 and the PLC port is RS-422, you need the documented conversion, not a straight-through cable.

Hand-building the cable is legitimate commissioning practice when it reproduces the documented circuit — the same discipline as how to build the HMI cable for an A1S programming port, but with the FX2's own documented pinout, never a borrowed one. Verify it before energizing the link:

  1. Identify the exact connector on the panel and on the PLC.
  2. Obtain the documented connection diagram for that pair, including any required adapter.
  3. Assemble or order the cable to that diagram only.
  4. With the cable disconnected and the equipment in a safe state, check continuity pin by pin and confirm there are no unintended shorts.
  5. Check shielding and grounding against the connection instructions, then install the cable without straining either connector.

Do not substitute a generic computer serial cable because its connectors happen to fit.

Work the commissioning in this order:

  1. Record both nameplates and the ports actually present.
  2. Install the licensed editor and confirm its version display.
  3. Create the project with the exact panel target, and select the Mitsubishi FX serial driver on the Device/PLC screen.
  4. Set the runtime port and serial format to match the FX2 port.
  5. Build, verify, and connect the cable.
  6. Transfer the project with the documented transfer procedure.
  7. Put one numeric display on a screen, bound to a valid controller device you can also watch in the PLC programming tool, and compare the two values.
  8. When that value tracks, add the buttons and writes.

Until step 7 tracks, keep every write out of the project: a mistagged button writing to an output on a running machine is how a communication test breaks tooling. If the value fails, read the panel's communication status before you rewire anything — a driver mismatch and a wiring fault look identical on the screen and cost very different amounts of time to separate.

Worked example: editor 4.09.450 against the 2.10.000 driver minimum #

Inputs: the editor on the engineering PC reports GP-Pro EX Ver. 4.09.450 in its version display, a documented Pro-face release dated 19 December 2022. The Mitsubishi Electric Corporation FX serial driver installer requires GP-Pro EX Ver2.10.000 or later.

Rule: compare the two versions field by field from the left. The installation qualifies if the first field that differs is greater than the requirement's.

Arithmetic:

  • Major field: 4 − 2 = +2, so 4.09.450 is already greater and the comparison stops.
  • Had the majors been equal, the comparison would move to the 09 against 10 minor fields, then the 450 against 000 maintenance fields.

Result: 4.09.450 ≥ 2.10.000, satisfied with two major-version steps of margin.

Decision: install the FX serial driver on this editor and build the project. The threshold is absolute — any editor at or above Ver2.10.000 passes, and anything below it gets upgraded first, because the driver installer will not apply to it.

Questions asked

Can I use a GP-Pro EX installer downloaded from a forum?

Use Pro-face's own download area, which lists a Full Install Version and a Trial Version, and license permanent use through Pro-face or an authorized distributor. A multi-part archive joined with a file splitter is an unlicensed copy of unknown integrity, and it leaves you with no driver installers matched to your editor and no support path when a transfer fails.

Will uploading the project from the running panel give me the editable source?

Not reliably. GP-Pro EX returns from an upload what its documented upload capability allows, which is often less than the original project data. Treat the panel as runtime hardware, keep the source on the engineering computer, and if the source is already lost, verify the documented recovery steps for your exact panel model before you plan around them.

The project transfers to the panel fine, but the values never go live. Why?

A successful transfer proves the engineering computer reaches the panel; it says nothing about the panel-to-PLC link. Check the selected Mitsubishi FX driver, the runtime port, the serial format, and the cable against the FX2 port before touching screens. The panel's communication status display is what separates a connection fault from a tag fault.

Is an FX2 the same as an FX2N for the driver and cable?

No. They are different generations of the MELSEC-FX family, and the compact communication boards that fit an FX2N base unit, such as the 232-BD, are not options on an FX2, so a guide written around the 232-BD solves a different problem. On the FX2 you use the built-in programming port with the serial Mitsubishi FX driver and the FX2's own documented pinout.

Do I need Pro-Server EX as well for a single panel?

No. For one panel you build and transfer the project with GP-Pro EX. Pro-Server EX Ver.1.30.000 or later appears in the FX driver installer's documented requirements because the same driver family also serves PC-based setups; it only matters to you if your architecture includes that package on a workstation.

Keep reading

  • Troubleshooting

    Why an HMI Fails to Talk to an FX2n PLC Over 232-BD

    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.

    HMI and touchscreens

  • How-to

    Connecting a Fuji HMI to a ControlLogix PLC

    Yes, the pairing works. You need Rockwell's Logix package matched to the controller firmware on the PLC side and Fuji V-SFT for the panel; FactoryTalk View programs only Rockwell panels, and RSLinx is not part of the Fuji data path. The gate is the driver list for your exact panel model — V8, V9 and TechnoShot have the Allen-Bradley connection documented.

    HMI and touchscreens

  • Troubleshooting

    Fixing Weintek HMI to Mitsubishi FX PLC Communication

    A Weintek panel that shows communication errors against an FX0N, FX1N, FX2N or FX3 CPU is nearly always wired with the wrong cable pinout for the port pair. Match the HMI COM port and PLC port to the Weintek PLC Connection Guide, set GX Developer parameters only for adapter boards, and keep the 1 m cable.

    HMI and touchscreens