IMDTouchKnowledge BaseShop main store

How-to

Connecting a PanelView Plus to a Mitsubishi FX PLC over RS-422

HMI and touchscreens Published 8 min read

Short answer

No passive adapter connects them: the PanelView Plus port is RS-232 and the FX programming port is RS-422, so use the Mitsubishi FX programming cable, whose housing contains the converter. Confirm the FX serial driver exists in the terminal runtime, then set the shortcut to 9600 baud, 7 data bits, even parity, 1 stop bit, station 0.

On this page
  1. Can a pin-to-pin adapter connect the 9-pin PanelView Plus port to the FX round port?
  2. Which cable replaces the adapter you were about to make?
  3. Does the PanelView Plus runtime have a driver for the FX protocol?
  4. What serial settings does the PanelView Plus shortcut need?
  5. How do you commission the link step by step?
  6. Why does the link stay dead, read garbage, or time out?
  7. What FX traps hide in the tag database and the port itself?
  8. Questions asked

No pin-to-pin adapter will join these two ports: the PanelView Plus serial port is RS-232 on a 9-pin D-sub, the FX round programming port is RS-422 on an 8-pin mini-DIN, and they differ at the electrical layer, not just the connector. The fix is the Mitsubishi FX programming cable, whose housing already contains the converter, plus one driver check and one set of serial parameters before anything is downloaded. This guide gives the cable decision, the settings, an eight-step commissioning procedure, and the fault pattern for when the link stays dark.

Can a pin-to-pin adapter connect the 9-pin PanelView Plus port to the FX round port? #

No — a passive pin-to-pin adapter cannot work, because the PanelView Plus port is RS-232, single-ended against signal ground, while the FX programming port is RS-422, differential across paired conductors, so the two need active conversion.

RS-232 swings one conductor against signal ground; RS-422 drives balanced pairs. Wire the 9-pin D-sub to the 8-pin mini-DIN straight through and you get silence or garbage framing, never a stable link. The different connector shells are the least of the problem.

Before ordering anything, read the CPU nameplate and the installed boards. Some FX CPUs and communication boards expose a separate RS-232 channel on a 9-pin connector; if the machine has one, the conversion question disappears and a plain serial cable serves. The round mini-DIN is the RS-422 programming port — that side always needs conversion.

Which cable replaces the adapter you were about to make? #

Use the Mitsubishi FX programming cable of the SC-09 class, which carries the RS-422-to-RS-232 converter inside its housing, between the PanelView Plus RS-232 port and the FX 8-pin mini-DIN programming port.

It is the shortest path with the fewest parts to specify, and it is the cable already qualified against that mini-DIN pinout, which removes a custom pigtail from the bill of materials. The one specification to verify before committing is power: port-powered converters of this class draw their operating current from the RS-232 handshake lines DTR and RTS, and at least one of those lines must be asserted. If the terminal leaves both deasserted, the converter stays unpowered and the link is dead.

If the handshake demand cannot be met, fit a standalone converter with its own external supply — do not fall back to a passive adapter under any circumstance. If you build the converter cable yourself, the pinout discipline is the same one that saves you when uploading an HMI program without the right cable pinout: one swapped pair and the port frames errors forever.

Route Where conversion happens What goes wrong when misapplied
Mitsubishi programming cable (SC-09 class) between the PanelView Plus RS-232 port and the FX mini-DIN Inside the cable housing Converter unpowered because the terminal deasserts DTR and RTS
FX communication board adding an RS-232 channel, straight 9-pin cable Nowhere — both ends are RS-232 PLC serial parameters never written, so the port stays in programming mode
Protocol gateway converting FX serial to EtherNet/IP Inside the gateway Tag map drifts from the HMI after a PLC edit

Whichever route you take, the terminal still has to speak the FX protocol — which is the next check, not a wiring job.

Does the PanelView Plus runtime have a driver for the FX protocol? #

Confirm it before wiring anything: FactoryTalk View Machine Edition runtimes do not ship every third-party serial driver, so open the communication setup on the terminal and verify a Mitsubishi FX serial driver is actually installed.

Media conversion is the easy half of this job. The FX programming port speaks Mitsubishi's own serial protocol, and the runtime has to answer in kind. A base install does not carry every third-party serial driver, so the check belongs at the start, in the same setup screens where shortcuts are created. If the driver is absent, take the gateway route by default: no amount of correct wiring makes an absent driver poll.

What serial settings does the PanelView Plus shortcut need? #

Set the shortcut to the FX programming-port defaults: 9600 baud, 7 data bits, even parity, 1 stop bit, with station number 0 on a point-to-point link — and match the PLC serial parameters instead if someone has edited them.

Worked example: at 9600 bit/s with 7 data bits, even parity and 1 stop bit, one character on the wire is 1 start + 7 data + 1 parity + 1 stop = 10 bits. 10 bits ÷ 9600 bit/s = 1.04 ms per character. Entering 8 data bits with no parity also produces a 10-bit frame, which is why the link "almost" works: the receiver samples the parity bit as the eighth data bit, every character code shifts, and short frames occasionally pass while long ones fail. Parity mistakes of exactly this kind are the subject of why even and odd parity settings fail a serial poll, and the mechanism transfers straight to this link.

If the PLC parameters were changed in the project, read them back with the programming software and enter those values in the shortcut instead of the defaults.

Prove the PLC end first with a laptop, then move the same cable to the terminal, create the shortcut, and verify with one numeric display bound to a D register you force from the programming software — eight steps in total.

  1. Confirm the FX CPU model and any installed communication board, and record whether an RS-232 channel exists separately from the mini-DIN programming port.
  2. Open the terminal's communication setup and confirm the Mitsubishi FX serial driver is installed. If it is not, stop here and take the gateway route.
  3. Prove the PLC end independently: connect a laptop through the same programming cable and go online with GX Works or GX Developer. Do not continue until you can read the program — one step proves cable, converter and PLC port together.
  4. Move the cable to the PanelView Plus RS-232 port. If the converter needs handshake power the terminal will not supply, fit an externally powered converter with its own 24 V feed.
  5. Create the serial shortcut and enter the parameters from the section above — the FX defaults unless the PLC project says otherwise.
  6. Set station number 0 for the point-to-point programming-port link.
  7. Build one test screen with a single numeric display bound to a D register you can force from the programming software. One safety note: force values only with the machine in a state where a changed register cannot command motion or an output.
  8. Download, run, change the register from the laptop, and confirm the display follows. At sign-off, force the register through its full range once more and watch the terminal track every value.

Isolate in that order: total silence means converter power first, continuous framing errors mean swapped RS-422 pairs, and intermittent timeouts mean the data-bit and parity settings — each fault has one dominant cause on this conversion.

No activity at all: meter the converter supply, or the handshake lines on a cable-powered unit. A dead converter and an absent driver look identical from the terminal, and on other panels the same dead-link symptom is the one behind fixing RS-232 cable disconnected errors on a replacement HMI.

Activity but no valid response: swap the RS-422 differential pairs. Reversed pair polarity is the most common wiring fault on this conversion, and it produces continuous framing errors rather than silence. If the terminal flatly reports the PLC as off, the fault is on the PLC side of the converter — the FX front-port RS-422 connection that reports the PLC off covers where that answer gets lost.

Intermittent reads, timeouts under load: check data bits and parity against the PLC parameters. Seven-even is easy to enter as eight-none, and the failure is exactly the half-passing pattern described above.

Clean reads, wrong values: check device addressing syntax in the tag database — that is the octal trap below.

What FX traps hide in the tag database and the port itself? #

Two: X and Y devices are numbered in octal — X8 and X9 do not exist — and the programming port is single-master, so a laptop going online drops every screen on the terminal.

Worked example: a 16-point FX input card occupies X0–X7 and X10–X17, that is 8 + 8 = 16 points. In octal, decimal 8 is written 1 × 8 + 0 = X10, and decimal 15 is 1 × 8 + 7 = X17. A tag list generated by counting 0 to 15 in decimal names X8 at the ninth input and misses every group boundary after it. Regenerate the list in octal before download.

The mini-DIN is a single-master channel: once the terminal polls it, a laptop cannot take the same port, and a technician who unplugs the HMI to go online blanks every screen on the machine. Where online access matters, fit an FX communication board that gives the HMI its own RS-232 channel and leave the programming port free.

Keep the RS-232 leg short — under about three metres — and put any long run on the RS-422 side, which tolerates distance. Route the serial cable away from VFD output conductors and contactor coils; differential signalling protects the RS-422 leg and does nothing for the RS-232 segment.

Questions asked

Will a USB-SC09 cable work with the PanelView Plus instead?

No. The USB-SC09 family puts a USB plug at the computer end for laptops, and the PanelView Plus exposes a 9-pin RS-232 D-sub, so you need the RS-232-ended version of the programming cable, whose built-in converter already handles the electrical layer.

The FX has an FX1N-422-BD board fitted. Does that remove the converter?

No. That board adds a second connector of the same RS-422 programming-port kind, so it gives you a spare connection point, not an RS-232 channel. You still need conversion to reach the PanelView Plus, and the board does not by itself make the link multi-master.

Where should the converter sit on a long run between the cabinet and the machine?

At the PanelView Plus end, so the short leg is RS-232 and the long run is RS-422, the differential side that tolerates distance. Keep the RS-232 leg under about three metres, and route the whole cable away from VFD output conductors and contactor coils.

Can two HMIs share the FX programming port this way?

No. The round programming port is a single-master, point-to-point channel; once the PanelView Plus polls it, nothing else can take the same port. Sharing requires an FX communication expansion set up for multidrop, which is a different design with its own addressing and termination decisions, not a second cable on the same connector.

Keep reading

  • How-to

    Connecting an XBTGT HMI to an M241 PLC over Modbus TCP

    Delete the Generic Modbus TCP slave from the M241 device tree and activate the Modbus server on the controller's Ethernet interface instead — that slave makes the M241 a client, so both devices poll and neither answers. Then map Vijeo Designer driver address 40001 to PLC word %MW0, keep TCP port 502 open between panel and controller, and shift the address map by one word if a test read lands one register off.

    HMI and touchscreens

  • Troubleshooting

    Reaching an Inaccessible NS Touchscreen From CX-Designer

    Neither a straight-through nor a crossover female-to-female adapter can make the installed PLC-to-NS cable serve a PC, because the PC's signal ground sits on pin 5 while the NS expects it on pin 9. Transfer through the PLC — with the NS on the CPU serial port, not an SCU — is the route that needs no rear access; USB (lot 0325, or system software 6.0 and later) or a cable wired 2-2, 3-3, 5-9, 7-5, 8-4 covers the one-visit cases.

    HMI and touchscreens

  • Troubleshooting

    FX3G front port RS-422 HMI connection that reports PLC off

    The FX3G-40M front port is an 8-pin MiniDIN, four-wire RS-422 interface that runs CH0 on the Mitsubishi programming protocol only. An HMI set to RS-232 or to an MC Protocol driver shows cable disconnected or PLC off even with the PLC powered. Match the electrical interface, the driver connection variant and the documented cable diagram, and the link comes up without expansion modules or added resistors.

    HMI and touchscreens