IMDTouchKnowledge BaseShop main store

Troubleshooting

Fixing Weintek HMI to Mitsubishi FX PLC Communication

HMI and touchscreens Published 9 min read

Short answer

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.

On this page
  1. Why does my Weintek HMI show a communication error with an FX PLC?
  2. Is a 1 m cable too short for the HMI to PLC link?
  3. Which COM port on the HMI and which port on the FX PLC am I using?
  4. How do I check the cable against the Weintek connection guide?
  5. What device settings must the HMI project use for an FX PLC?
  6. When does the FX PLC need communication parameters in GX Developer?
  7. Why do low addresses respond while higher ones stay dead?
  8. Why can't I switch an X input on from the HMI button?
  9. Questions asked

When a Weintek panel such as an MT6070iH 2WK, an MT506-type or a TK6071iP boots, draws every screen and then shows a communication error against an FX0N, FX1N, FX2N or FX3 CPU, the cause in the reported cases was the cable, not the panel and not the project. Work the checks in order: identify the exact port pair, buzz the cable against the Weintek PLC Connection Guide, match the HMI device settings, and only then touch PLC-side parameters, which the programming port does not need. A 1 m cable is electrically fine; never rebuild it for length.

Why does my Weintek HMI show a communication error with an FX PLC? #

Because the cable pinout does not match the exact pair of ports in use: in the reported cases the panel, the driver and the settings were right, and the conductors simply landed on the wrong pins for that port combination.

The pattern repeats across the field cases: an MT6070iH 2WK against an FX1N, an MT510S against an FX0N and a TK6071iP against an FX2N all failed the same way, with objects pointing at the PLC showing errors or staying blank. One engineer spent a month swapping one conductor at a time and never got a link, which is the trap: random swaps never answer the real question of which port sits on each end and which signal standard each port speaks.

Work the sections in order, because each one closes a branch before the next opens. The error text the panel itself displays (PLC no response, cable disconnected) has its own HMI-side causes, covered in Fixing RS-232 Cable Disconnected Errors on a Replacement HMI.

No. A 1 m cable sits well inside every limit that applies here: EIA/TIA-232 permits about 15 m at 9600 baud, and a signal crosses one metre thousands of times faster than a single bit lasts, so length is never the fault on this link.

The arithmetic, so the matter stays closed:

  • Signals in data cable travel at roughly 2 × 10⁸ m/s, so 1 m takes 1 m ÷ (2 × 10⁸ m/s) = 5 ns.
  • At 9600 baud, one bit lasts 1 ÷ 9600 baud = 104 µs.
  • The propagation delay is therefore 104 µs ÷ 5 ns ≈ 1/20,800 of one bit, which no serial port can see.

The real ceiling is capacitance, not distance: EIA/TIA-232 caps the total load at 2500 pF, and typical data cable runs 50 to 150 pF per metre, so even 15 m lands at 750 pF to 2250 pF, just inside the standard. A 1 m cable at 50 to 150 pF is nowhere near any limit. Decision: keep the cable you have, and rebuild it only for pinout.

Which COM port on the HMI and which port on the FX PLC am I using? #

Identify both before touching wire: on many Weintek models one COM connector carries RS-232 on one pin set and RS-485 on another, while the PLC side is either the round programming port or an RS-232 or RS-485 adapter board, and every pair has its own pinout.

What you are plugged into What it means for the link What still has to be done
FX programming port (small round connector) Direct HMI-to-PLC cable; no PLC-side parameters exist for it Match the HMI device settings to the format the guide lists
RS-232 adapter board on the PLC RS-232 pinout on both ends Set the port format in GX Developer, then mirror it in the HMI
RS-485 adapter board on the PLC RS-485 pinout on both ends Same as the RS-232 board, plus station numbers if more than one node hangs on the line
One HMI COM connector with two pin sets The pin set must match the interface chosen in the HMI device settings Decide the interface first, then wire to its pins

The matching rule is absolute: an RS-232 pin set talks to an RS-232 port, an RS-485 pin set to an RS-485 port. A cable built for the wrong pair will never link, however many conductors you swap. Mind the CPU generation too: on newer FX3G units the front port over RS-422 has its own failure mode that reports the PLC as off, treated separately in FX3G front port RS-422 HMI connection that reports PLC off.

How do I check the cable against the Weintek connection guide? #

Buzz it out with a multimeter in continuity mode, pin by pin, against the diagram for your exact HMI COM port and FX series in the Weintek PLC Connection Guide, never against a PC programming cable and never against a generic diagram.

  1. Write down the HMI model, the COM port number in use and the connector on the panel; the pin numbering of those connectors is published in Weintek's separate HMI pin assignment tables.
  2. Open the Mitsubishi FX section of the PLC Connection Guide and take the diagram for your CPU series and that port, because the serial pin assignments vary between HMI models.
  3. Buzz every conductor end to end and write down which pin lands on which.
  4. Compare each pair with the diagram, fix every mismatch, and retest before changing any software setting.

Two traps are documented in the field:

  • A PC programming cable is not an HMI cable. The SC09-type cable suggested in one case has its own converter inside and is wired for a computer's serial port, and it did not link even on a site whose other machines run the same panel and PLC pair. Decision: never use it between panel and PLC.
  • A running machine's cable can disagree with the guide. One engineer measured the link between an FX3 CPU and an MT506-type panel on a working machine, found the pinout unrelated to the diagrams he had, rebuilt to the measured pinout, and the link came up. Decision: when a working machine of the same family exists, buzz its cable and trust the one that runs.

The cable that moves the project between your PC and the panel is a third, separate pinout with its own failure modes, covered in How to Upload an HMI Program Without the Right Cable Pinout.

What device settings must the HMI project use for an FX PLC? #

Set four things in the Device (PLC) properties and download the project afterwards: the Mitsubishi FX driver entry matching your CPU, the interface you actually wired, the COM port the cable occupies, and the serial format the PLC port runs.

  • PLC type: FX0N, FX1N, FX2N and FX3 CPUs fall under the FX driver family, so read the exact device list in your EasyBuilder version before choosing.
  • Interface: RS-232, or RS-485 with the correct two-wire or four-wire choice, matching the pins you wired.
  • COM port: the number of the connector the cable is actually plugged into.
  • Serial format: on the programming port, the values the connection guide lists for your series; on an adapter board, whatever you wrote into the PLC parameters.

A setting edited in the project does nothing until the project is downloaded to the panel. Decision rule: on the programming port with the guide's values entered, a dead link is wiring, so go back to the cable section; on an adapter board, finish the PLC side first.

When does the FX PLC need communication parameters in GX Developer? #

Only when the cable lands on an RS-232 or RS-485 adapter board: those ports have no fixed format, so the PLC stays silent unless the PLC Parameter communication settings match the HMI, while the programming port needs nothing written to it at all.

In GX Developer, open the PLC Parameter section and enter the communication settings for the RS-232 or RS-485 port exactly as the connection guide's Mitsubishi FX section shows them: transmission speed, data bits, parity, stop bits and the station number. Write the parameters to the PLC, then cycle PLC power or switch the PLC through STOP and RUN so they take effect, and mirror every one of those values in the HMI device settings. A mismatch in any single value produces the same symptom as a broken cable: no response at all.

One caution: write parameters to a PLC with the machine stopped, because a changed port setting can disturb anything already using that port.

Why do low addresses respond while higher ones stay dead? #

When M0 to M10 answer and nothing above them does, the cable, the ports and the serial format are proven good, and the remaining fault sits in a station or address-range setting in the HMI device properties, so compare the HMI station number with the PLC's.

The reported fix for this symptom came from a Delta link: bits M0 to M10 worked and the rest did not until the HMI station address was set to 255, although the Delta documentation stated 0. That value belongs to that Delta setup; whether an FX link behaves the same way is untested, so do not set a station value on an FX programming-port link unless the guide asks for one. The diagnostic is the part worth keeping: a partial response clears the whole electrical chain.

Symptom Most likely cause What to change
Nothing responds at all Wrong pinout, wrong port pair, mismatched serial format The cable and settings sections above
Low addresses work, high ones dead Station or address-range setting HMI station number against the PLC's setting
Reads work, a write to an X fails X is a physical input the PLC refreshes every scan Use an M coil, next section
Timeouts come and go Connector seating, shield and termination Reseat connectors, check the shield drain wire

When values do update but crawl, the failure has moved off the cable and into polling and load, which Why an HMI Freezes or Updates Slowly Over Serial covers for this stage.

Why can't I switch an X input on from the HMI button? #

Because the PLC refreshes X devices from the physical input terminals every scan, so a write from the panel is overwritten within one scan cycle; point the button at an M coil instead and let the program use that coil where you wanted the input.

Concretely: set the button's write address to an M coil such as M100, download, then place a normally open contact of M100 in parallel with (or in place of) X1's contact in the PLC program, so the button and the real input drive the same rung. The HMI never owns an X device; if you must simulate an input during commissioning, do it at the terminal or with the programming software on the PC side, never from the screen.

Questions asked

Do I need a station number in the HMI when it uses the FX programming port?

No. The programming port is a single point-to-point link and takes no station assignment, and an FX0N has no station setting to miss. Station numbers only matter on an RS-485 multi-drop line with more than one PLC, where the value in the HMI device settings must equal the one the PLC port is set to.

How far can the cable run if the panel has to sit away from the cabinet?

On RS-232 keep inside the EIA/TIA-232 load limit, which works out to roughly 15 m at 9600 baud with typical cable. On RS-485 the standard allows up to 1200 m, so distance is almost never the constraint on an FX link; if a long run misbehaves, suspect termination and the shield, not the metres.

The same panel and PLC models work on another machine, so why will they not link on mine?

Because the pinout is only valid for the exact port pair, and two machines with identical models can use different ports: one may hang off the programming port, the other off an adapter board, and the panel side can present RS-232 and RS-485 on different pins of the same connector. Buzz the working machine's cable and copy it.

Can one Weintek panel serve several FX PLCs?

Yes, over RS-485. On a multi-drop line one panel can poll several FX CPUs when each adapter board carries its own unique station number and the HMI project addresses each station. Over the programming port it is strictly one panel to one PLC, because that port is a dedicated point-to-point connection with no addressing.

Keep reading

  • How-to

    Editing a Delta DOP HMI project without breaking PLC comms

    Downloading a revised project to a Delta DOP panel replaces only the panel's project; the PLC program and its port configuration are untouched. The link survives because the driver and serial parameters are stored separately in each device and a revision leaves them matching. Record both sides first, then prove read and write after the download.

    HMI and touchscreens

  • Explainer

    Why HMI simulation cannot talk to a simulated PLC

    EasyBuilder's PC simulation communicates with a real PLC, but SimuLab runs a LogicLab program without any communications service, so two PC simulators never exchange data. Integrated testing needs at least one physical CPU module; until then, test the screens and the controller logic separately.

    HMI and touchscreens

  • How-to

    Set a Premium PLC Clock From a Magelis HMI Over Unitelway

    In Vijeo Designer, open the Unitelway equipment in the I/O Manager, add a Dialogue Table with start address %SW50 and the Configure the PLC clock function, and clear the Include editor project option before transfer, because packaging the editor project is what aborts the download with an abnormal program termination. Keep the editable project on the engineering workstation and verify the PLC clock with its own read.

    HMI and touchscreens