IMDTouchKnowledge BaseShop main store

Troubleshooting

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

HMI and touchscreens Published 7 min read

Short answer

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.

On this page
  1. What the PLC-off message actually reports
  2. The front port is 8-pin MiniDIN four-wire RS-422, not RS-232
  3. The driver connection decides the protocol
  4. CH0 on the PLC is not a COM number on the HMI
  5. Worked example: conductor count for a direct GP-4301TM to FX3G-40M front-port cable
  6. Wire to the documented diagram, then measure
  7. The decision for each finding
  8. Questions asked

Connect the GP-4301TM straight to the FX3G-40M front connector and the link works, with no FX-232, FX-485 or FX-422 module in the circuit, provided three things match. That front port is an 8-pin MiniDIN carrying four-wire RS-422, it is CH0, and it answers only the Mitsubishi programming protocol, never MC Protocol. A project that sets RS-232, or picks a driver connection that speaks MC Protocol, produces exactly the symptom on screen: cable disconnected or PLC off while the PLC sits powered in RUN. Work the checks below in order: electrical interface first, driver connection variant second, documented cable diagram third. Termination resistors come last, and on this short point-to-point link they usually do not come at all.

What the PLC-off message actually reports #

The disconnected or PLC-off banner is the HMI driver reporting that no valid reply arrived inside its timeout. It cannot tell an unpowered PLC apart from an electrical mismatch, a wrong protocol or a broken cable; all four look identical on screen, so the banner is not evidence about PLC power. Confirm power and RUN at the PLC itself, then place the fault in one class:

  • Every object bound to the connection fails: the electrical interface, the driver connection or the cable is wrong. Continue below.
  • Only some objects fail while others on the same connection update: the fault sits in those objects' device assignment or tag address, and no rewiring or termination will touch it.
  • The failure began the moment a project was downloaded or a terminal was swapped: suspect the new project's settings first.

A replaced terminal can produce the identical banner for purely electrical reasons, as worked through in Fixing RS-232 Cable Disconnected Errors on a Replacement HMI.

The front port is 8-pin MiniDIN four-wire RS-422, not RS-232 #

The first correction is the connector description. The FX3G-40M front connector is an 8-pin MiniDIN; the FX-series peripheral documentation describes the RS-422 connection with a MiniDIN 8-pin connector on the PLC side, and that same socket is where the SC09 programming converter lead plugs in. There is no 9-pin circular connector on this port, and a DB9 shell found anywhere in the path describes only a connector shape, never the electrical standard or the pin assignments.

Four-wire RS-422 means the PLC drives one differential pair and listens on a second, so both ends need true differential drivers and receivers. Two consequences follow:

  • Setting the HMI serial interface to RS-232 cannot match this port. RS-232 and RS-422 use different signaling, and passive pin reassignment does not convert one into the other.
  • Selecting an RS-422 option in software does not make an RS-232-only port electrically capable.

Read the terminal's hardware interface documentation and the selected driver's required-interface note together, and identify which physical serial interface on the GP-4301TM actually supports four-wire RS-422. If one does, move on to the driver. If none does, the choice is a converter that genuinely converts the electrical standard, or different operator hardware; where the decision is to replace the terminal with a PC-based operator station rather than adapt it, industrial panel PCs are the category to compare.

The driver connection decides the protocol #

A matching electrical interface is necessary but not sufficient; the front port also insists on its own application protocol. It answers only the Mitsubishi programming protocol. The FX3S/FX3G/FX3GC/FX3U/FX3UC series documentation (JY997D26201) lists the serial protocol modes, the programming port's entry being Programming Port Protocol, with Computer Link and N:N Network appearing as the separate modes used by other port settings. MC Protocol frames, in any format, draw no answer from CH0, which produces the same disconnected banner as a wiring fault.

In GP-Pro EX, open the Device/PLC help and find the Mitsubishi CPU Direct driver. Check the supported controller list, select the connection description for the CPU's built-in peripheral port, and read its required HMI interface, communication settings and cable diagram as one specification. A Mitsubishi entry somewhere in the driver list is not enough; the connection variant determines the frames the terminal sends.

Decision: if the selected connection uses MC Protocol, change it to the programming-port connection before any cable work. The FX series serial communication manual (JY992D69901, covering RS-232C, RS-485 and RS-422) documents what the expansion ports accept, and the driver's supported-controller list names the connection that matches one of them.

CH0 on the PLC is not a COM number on the HMI #

The front port is CH0 and its protocol is fixed. The serial parameter screens visible on the PLC side belong to extension ports; editing them cannot affect a cable that lands on the front MiniDIN, so leave them out of this fault entirely.

On the terminal, the COM selection identifies which physical serial interface the driver drives. The correct value is simply the COM entry that the terminal's hardware documentation maps to the connector you actually wired. There is no COM number that mirrors CH0, and choosing one by analogy is not a selection method. Trace the cable to the terminal connector, read that interface's designation in the terminal documentation, set the COM selection to match, and rerun the communication check.

Worked example: conductor count for a direct GP-4301TM to FX3G-40M front-port cable #

The inputs, with their sources:

  • Four-wire RS-422 on the PLC front port, meaning two differential pairs and therefore four signal conductors: from the front-port description in this fault and the FX-series RS-422 configuration diagram.
  • One signal-ground conductor running with the pairs: the published FX RS-422 wiring diagram lists ground conductors alongside the four signal lines.
  • The lead on the bench: a leftover RS-232-style cable with three cores, one transmit, one receive, one ground, which is what the project's old RS-232 setting implies.

The rule in words: a four-wire RS-422 link needs two conductors per differential pair, one pair in each direction, plus the signal reference. Cores needed = transmit pair + receive pair + signal ground.

The arithmetic: 2 + 2 + 1 = 5 cores minimum. The RS-232-style lead offers 3 cores. 5 - 3 = 2 conductors short.

The result: a three-core cable cannot carry this link. The two differential pairs need four dedicated conductors before any ground is counted, and a lead that carries one conductor per direction has nothing to build the second pair from.

The decision: below five cores, the direct front-port connection is impossible regardless of pin mapping. Rebuild on at least five cores, four signal plus signal ground, shielded over all of them, and map them from the driver's diagram. If the existing lead has three cores, the cable is the fault, and no PLC setting repairs it.

Wire to the documented diagram, then measure #

The FX-series documentation presents the RS-422 connection as a wiring diagram from the PLC terminals to the cable connector, and the Device/PLC help supplies the diagram for the exact driver connection selected. Use those, in this sequence:

  1. Open the cable diagram for the selected CPU Direct connection together with the actual HMI interface, and mark the viewing direction of both connectors; mating-face and solder-side views reverse the apparent pin numbering.
  2. With both units isolated from supply, run a continuity check from every documented PLC signal to its stated destination on the HMI connector.
  3. Check for unintended shorts between cores, and confirm the shield and the signal ground land where the diagram terminates them.
  4. Verify pair polarity end to end. A swapped pair passes a continuity test yet defeats reception, because the differential receiver sees a difference across the wrong conductors.

Termination has its place, and this is not it. The absence of FX-232, FX-485 or FX-422 modules does not create a termination requirement. Termination is a transmission-line measure for long runs, sized to the cable's characteristic impedance wherever a diagram calls for it, and the driver's cable diagram is the only place that specifies any resistor for this connection; on a bench-length point-to-point lead it specifies none. The FX3G-422-BD board exists to add an RS-422 peripheral port for a second device, not to make the front port usable.

The same four-wire discipline on the related FX3GE port is covered in FX3GE RS422 to HMI wiring fix for no response.

The decision for each finding #

Finding on the bench What it means Decision
HMI serial set to RS-232 against the 8-pin MiniDIN port Electrical interface mismatch Select the RS-422 CPU Direct connection on a terminal interface that supports four-wire RS-422
Driver connection variant speaks MC Protocol A protocol CH0 ignores Change to the programming-protocol connection before touching the cable
Cable has three cores Two conductors short of the five the link needs Rebuild on four signal cores plus signal ground, mapped from the driver diagram
PLC extension-port parameters edited Settings aimed at the wrong port Leave them; CH0's protocol is fixed and those screens do not touch it
Only some HMI objects fail Tag address or device binding fault Correct the object's assignment; wiring and termination are not involved
Every object fails with the PLC powered and in RUN Interface, driver or cable Work interface, then driver connection, then cable, in that order

Run in that order, the link comes up through the front port with no expansion module and no added resistors. The fix lives in the HMI project and the cable, not in the PLC's extension-port settings.

Questions asked

Can the FX3G front port be switched to RS-232 in software?

No. The front connector is fixed as four-wire RS-422 and no PLC parameter, option switch or download changes its electrical standard. Changing baud rates in the HMI project cannot fix an electrical mismatch either, because the frames never reach a receiver that can read them. The correction is always on the HMI side: a serial interface with true differential drivers plus the driver connection that uses the programming protocol.

Which protocol does the front port speak, and where do the others run?

The front port answers only the programming protocol; the series documentation lists its mode as Programming Port Protocol. Protocols such as Computer Link run on communication expansion ports fitted in the option slot, for example the RS-422 FX3G-422-BD board, set from serial parameters that never touch CH0. If your driver speaks only a protocol CH0 ignores, move that link to an expansion port instead of fighting the front one.

Do termination resistors belong on the direct front-port cable?

Not for this fault, and adding them will not clear the banner. Termination resistors are a long-line measure, sized to the cable's characteristic impedance, typically 100 to 120 ohms for twisted pair, and they belong only where the driver's cable diagram shows them. On a bench-length point-to-point lead the diagram specifies none. If resistors are fitted and the disconnected banner stays, the cause is the interface, the driver connection or the conductor count, not missing termination.

Can the programming cable and the HMI share the front port?

Not through a splitter. CH0 is a single programming interface with no documented multidrop arrangement, and two devices driving or listening on it at once corrupt both sessions. Plug the programming lead in while commissioning, swap to the HMI cable to run, or fit a communication expansion board so the permanent HMI link gets a port of its own.

Keep reading

  • Troubleshooting

    FX3GE RS422 to HMI wiring fix for no response

    Wire HMI COM1 receive to the FX3GE transmit pair, the HMI transmit pair to the PLC receive pair with matching polarity, and land signal ground on PLC pin 5. The failed map had the transmit pair reversed and ground on pin 3; the crossed, polarity-matched map with ground on pin 5 restored communication.

    HMI and touchscreens

  • Troubleshooting

    Why an HMI Freezes or Updates Slowly Over Serial

    A panel-wide freeze or slow updates over serial is a link fault — driver, PLC port, wiring, or startup timing — not a screen-object fault. Test the two field-proven fixes first: a 10-second startup delay before the first poll, and a port set to four-wire RS-422 at 19,200 baud. Fix an isolated stale tag separately, by address and data type.

    HMI and touchscreens

  • Troubleshooting

    Why One PLC to Two HMIs Fails Over RS-422 Multilink

    A 1:1 serial test proves one cable and one framing set; it cannot prove a shared n:1 multilink. Fix two HMIs on one RS-422 trunk by running the multilink driver entry on both panels, giving each a unique link identity, matching every serial parameter, and terminating only the trunk ends. The documented limit is 16 displays, so two panels are a configuration problem, never a capacity one.

    Industrial networks

Programming a Fatek PLC Through a Weintek HMI Ethernet Link