IMDTouchKnowledge BaseShop main store

How-to

Configure the FX5U MC Protocol side for WinCC RT Advanced

HMI and touchscreens Published 5 min read

Short answer

Configure the FX5U side in GX Works3 as one SLMP connection in the CPU's Ethernet settings: protocol SLMP, UDP transport, local port 5002 — the destination port the WinCC RT Advanced Mitsubishi MC Protocol driver sends to. Download the settings, then prove one device-address tag live before restoring the full project.

On this page
  1. What the WinCC driver expects on the FX5U
  2. The four settings that must agree
  3. Worked example: confirm both ends share a subnet
  4. Configure the FX5U endpoint in GX Works3
  5. Prove the link with one live read
  6. UDP, TCP, or Modbus TCP
  7. Questions asked

On the FX5U, the WinCC RT Advanced connection lands on one SLMP connection in the CPU's Ethernet settings, configured in GX Works3: protocol SLMP, UDP transport, local port 5002 — the number the Siemens-side instructions assign as the destination port. Nothing you build in the WinCC project configures that endpoint for you. Set it once, download it, and prove one tag live before the rest of the project depends on it.

What the WinCC driver expects on the FX5U #

WinCC RT Advanced reaches Mitsubishi controllers through its Mitsubishi driver, which speaks MC Protocol. Mitsubishi's own name for the same request and response messaging on Ethernet is SLMP, and the MELSEC iQ-F FX5 User's Manual (SLMP) documents the PLC side of that service. For the connection described in the Siemens-side instructions the transport is UDP and the assigned destination port is 5002, so the FX5U must have a service listening on that port.

Two variants sit next to this. An MC over TCP/IP driver variant also exists; a report on Siemens' support portal describes an FX5U that only communicated after the latest update for the installed WinCC version was applied, so treat driver availability as a property of your installed version and its updates, and read the driver list there before committing to TCP. The FX5U also runs Modbus TCP, which only helps if the HMI side actually speaks Modbus.

Decision: follow the documented setup — MC Protocol over UDP on port 5002 — unless the driver list in your installed WinCC names MC over TCP/IP and you have a reason to need a transport session.

The four settings that must agree #

Read the WinCC connection properties first and build the PLC side to match them, not the other way round. Every MC Protocol link is four matched values:

Setting WinCC RT Advanced side FX5U side
Protocol Mitsubishi MC Protocol driver SLMP connection, protocol SLMP
Transport UDP UDP
Address Destination IP, e.g. 192.168.10.31 CPU IP address, same value
Port Destination port 5002 Local port 5002

One distinction saves an hour: the FX5U setting matches the HMI's destination port. The reply travels back to the PC's source port, which WinCC chooses per session, so nothing on the PLC needs to know it.

Worked example: confirm both ends share a subnet #

Illustrative addresses — substitute your plant values. The runtime PC is 192.168.10.20 with mask 255.255.255.0, and the FX5U is set to 192.168.10.31 with the same mask.

  • 192.168.10.20 AND 255.255.255.0 = 192.168.10.0
  • 192.168.10.31 AND 255.255.255.0 = 192.168.10.0

Both hosts compute the same network, 192.168.10.0, so the PC delivers the UDP datagrams for port 5002 straight to the PLC with no router involved. Now the failure case: an FX5U still carrying 192.168.1.31 gives 192.168.1.31 AND 255.255.255.0 = 192.168.1.0, which does not equal 192.168.10.0. The request goes to a default gateway that may not exist, and the symptom is a request that leaves the PC and never comes back.

Configure the FX5U endpoint in GX Works3 #

  1. Open the FX5U project in MELSOFT GX Works3; the FX5 CPU parameters hold its Ethernet settings.
  2. In those Ethernet settings, set the CPU IP address and subnet mask to the values you proved in the subnet check.
  3. Add or edit the SLMP connection there: protocol SLMP, open transport UDP, port number 5002.
  4. Write the settings to the PLC and confirm the online values equal the project values — schedule the write as an agreed interruption, because a parameter write to a running CPU can disturb the machine it controls.
  5. In the WinCC connection, select the Mitsubishi MC Protocol driver with transport UDP, the FX5U address as destination IP, and destination port 5002.
  6. Create one test tag on a device you can watch change, such as an input byte or a running counter — not an output or a setpoint.
  7. Start the runtime, read that tag, and only then restore the rest of the project.

Prove the single tag live before you reload the screens, the way testing HMI simulation against a live PLC separates screen faults from connection faults. Capture packets at the runtime PC filtered on UDP port 5002 and the PLC address, then read the outcome:

  • No request leaves the PC: the fault is HMI-side — the connection is inactive, the tag belongs to another connection, or the running project is not the one you edited.
  • A request leaves and nothing returns: the fault is the PLC endpoint or the path. Compare the online Ethernet configuration with the downloaded project; for an FX5U that refuses other clients too, start where a GOT comm error on a direct FX5U Ethernet link starts, at the PLC's online settings rather than at the client. Re-run the subnet arithmetic and permit UDP between the PC and the PLC in both directions on any firewall between them.
  • A reply returns carrying an error: the PLC is alive and answering. Decode the returned status against the SLMP manual and check the device range and format you requested.
  • A good reply returns but the tag still faults: compare the tag's data type and length with the device you addressed.

UDP, TCP, or Modbus TCP #

Choose UDP on 5002 when you follow the documented Siemens-side setup; that is the default this article configures and the one with the fewest moving parts. Choose TCP only when the driver list in your installed WinCC offers MC over TCP/IP and you want transport-level delivery handling; then set the FX5U SLMP connection to TCP on the same agreed port and re-prove one tag. Choose Modbus TCP only when the plant standard demands it or other clients already speak Modbus to that PLC: it is a different service with a different address mapping, every WinCC tag is re-addressed, and an SLMP endpoint never answers a Modbus request. No mix is valid — a UDP socket does not receive a TCP session, and neither service answers the other's protocol.

Questions asked

Is port 5002 mandatory for an FX5U to WinCC RT Advanced link?

No. 5002 is the destination port the Siemens-side instructions assign for this MC Protocol connection, so for that setup the FX5U must listen on 5002. If your WinCC project uses a different destination port, set the FX5U local port to that number instead. The rule is only that the PLC's local port equals the HMI's destination port; the number itself is free within the valid UDP range.

Why does ping succeed while WinCC reports a connection error?

Ping uses ICMP, a different protocol from the UDP datagrams the MC driver sends, and UDP opens no session — WinCC only knows the link works when a valid SLMP response returns inside its timeout. A PLC can answer ping all day while its SLMP connection is closed, set to the other transport, or listening on the wrong port.

Do global labels need external device access enabled for this link?

Not for tags addressed to devices such as D or M registers, which is how an FX5U link is normally built in WinCC. The external-device-access allowance on global labels matters when a client requests labels by name. Enable it per label only if your driver reads named labels; device-address tags work without it.

What is the difference between MC Protocol and SLMP on the FX5U?

Two names for the same Mitsubishi request and response messaging: MC Protocol is the HMI-vendor name, SLMP is Mitsubishi's name for it on Ethernet. The difference you can touch is the frame — SLMP messages ride frames such as 3E, documented byte by byte in the FX5 SLMP manual. WinCC's driver assembles the frames itself, so you only meet 3E when scripting raw requests or decoding a capture.

Keep reading

  • Troubleshooting

    Why EasyBuilder Asks for a Tag CSV for a Mitsubishi Q PLC

    EasyBuilder asks for a tag CSV because the selected Mitsubishi driver is the label-based one, and GX Developer cannot export labels in that format - its converter refuses label-based projects. Switch the project to the Q-series Ethernet driver and address D, X and Y devices directly, with no CSV at all. If you want symbolic names, open the Q project in GX Works2 and export the label CSV from there.

    HMI and touchscreens

  • 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

  • Troubleshooting

    Why rebuilt HMI runtime files show #### for PLC tags

    Hashes on every tag after transferring a rebuilt WinCC Runtime Advanced project are a display symptom, not a communication code. Restore the working runtime files as a baseline, add an alarm view showing buffered System alarms, and branch on the message text: connection establishment, TLS certificates and clocks, hidden project pairing, or single-field formatting.

    HMI and touchscreens