Troubleshooting
Fixing a GOT Comm Error on a Direct FX5U Ethernet Link
Short answer
The GOT comm error on a direct link is a settings mismatch: the GT Designer3 controller IP, subnet and MELSOFT TCP/IP port must match the FX5U built-in Ethernet module parameters, which take effect only after you write them and power-cycle the PLC. The GT Simulator3 PLC-type error is separate: set the controller type to the FX5U entry, not the generic FX entry, and start the PLC simulation before the screen simulation.
On this page
- Why does the GOT show a comm error on a direct FX5U Ethernet link?
- Does the GT2104-PMBD have an Ethernet port for this connection?
- Which IP address and port settings must match on both sides?
- How do I write and activate the FX5U Ethernet parameters?
- Why does GT Simulator3 say the PLC type is different from the setting?
- Do I start the PLC simulation or the screen simulation first?
- How do I verify the comm error is actually cleared?
- What still breaks the link after the settings match?
- Questions asked
If your GT2104-PMBD shows a comm error the moment it powers up against an FX5U over a direct Ethernet cable, the hardware is almost certainly fine: the GOT project's controller settings and the FX5U's built-in Ethernet parameters disagree. Match three values — the PLC's IP address, the subnet mask and the MELSOFT TCP/IP port — on both screens, write the FX5U parameters, power-cycle the PLC, and download the GOT project with its communication settings. The GT Simulator3 message that the PLC type of the project is different from the setting is a second, separate fault: the GT Designer3 controller type is on the generic FX entry instead of the FX5U entry. Fix the link first, then the simulator.
Why does the GOT show a comm error on a direct FX5U Ethernet link? #
Because the two ends disagree about the network: the GOT project's controller IP address, subnet mask or MELSOFT TCP/IP port number does not match the FX5U built-in Ethernet module parameters, or those parameters were written but the PLC was never power-cycled.
On a two-device cable there is no switch, no DHCP and no gateway to paper over a wrong number: the GOT's driver opens a TCP connection to the address and port typed into GT Designer3, and when the PLC is not at that address and port the driver reports a communication error and the banner stays up. Work in this order: confirm the terminal actually has an Ethernet port, compare the two setting screens side by side, write and power-cycle the PLC, then download the GOT project. A comm error that appears only after minutes of clean operation is not this fault; that is the intermittent-loss diagnosis further down.
Does the GT2104-PMBD have an Ethernet port for this connection? #
Yes: Mitsubishi Electric's GT2104-PMBD data sheet lists one Ethernet port and one RS-422/485 channel, with ETHERNET and MODBUS as network options, so a direct RJ45 link to the FX5U's built-in Ethernet port is supported hardware.
Rule out hardware before touching parameters, because no setting can add a port the unit does not have. The GOT2000 family spans variants with different interface sets, so if your terminal is any other model, read its own data sheet first. For the GT2104-PMBD, run an ordinary RJ45 patch cable from the FX5U's built-in Ethernet connector to the GOT's Ethernet port — a direct cable is the normal bench arrangement for two devices. Power both units and look at the link LEDs: a lit LED on both ends proves the cable and the ports, and moves the whole fault into the settings.
Which IP address and port settings must match on both sides? #
Three values must agree: the PLC's IP address and subnet mask in the FX5U built-in Ethernet module parameters, the MELSOFT TCP/IP port number in the same tree, and the GOT-side controller IP plus port in GT Designer3, with the GOT on a unique address in the same subnet.
The GOT dials the PLC, so the controller IP in GT Designer3 is the PLC's address, never the GOT's own. Read the port from the FX5U's MELSOFT connection parameter instead of guessing; whatever number that screen shows, type exactly that number into the GT Designer3 controller setting. The GOT's own address goes into the GOT IP Address and Subnet Mask fields of its communication setting, in the same subnet with a different host address — two stations answering one address corrupts a link in ways that look random.
Worked example (illustrative numbers — read the real ones from your parameter screens): the FX5U shows IP address 192.168.3.19 with subnet mask 255.255.255.0. Give the GOT 192.168.3.50 with the same mask. AND each address with the mask to get its network number: 192.168.3.19 AND 255.255.255.0 = 192.168.3.0, and 192.168.3.50 AND 255.255.255.0 = 192.168.3.0. Equal network numbers, so a direct cable carries the traffic. Set the GOT to 192.168.4.50 instead and its network number becomes 192.168.4.0; each end now believes the peer is remote, a two-device cable has no gateway, and the comm error survives every rewrite of the port.
If you want every screen in order, the FX5U-to-GOT2000 Ethernet configuration walkthrough covers this exact PLC-and-terminal pair step by step.
How do I write and activate the FX5U Ethernet parameters? #
Set the values in the GX Works3 module parameter tree for the built-in Ethernet port, write them to the PLC, then power-cycle the PLC: FX5U built-in Ethernet parameters only take effect after the CPU restarts with the new settings.
- In GX Works3, open the FX5U module parameters and set the built-in Ethernet port's IP address and subnet mask.
- Note the TCP port number of the MELSOFT connection in the same tree, or set it deliberately if it is blank.
- Write the parameters to the PLC. GX Works3 stops the CPU to write them.
- Power-cycle the PLC. Safety note: the write stops the FX5U and the power cycle restarts it, so confirm the machine is in a safe, stopped state before you write — never bounce a PLC that is holding a live process.
- In GT Designer3, open the controller communication setting, select the MELSOFT TCP/IP driver on the Ethernet channel, and enter the PLC's IP address and port.
- Enter the GOT's own IP address and subnet mask on the same screen.
- Download the project to the GOT with its communication interface settings included — screens alone leave the old connection data in the terminal.
Skipping the power cycle is the classic miss: the PC shows the new address and port while the CPU still runs on the old ones, so the GOT errors against settings that look correct on the screen. Re-write after every change and cycle again.
Why does GT Simulator3 say the PLC type is different from the setting? #
The GT Designer3 project's controller type disagrees with the PLC project the simulator is loading: it was set to the generic FX entry when the project was created, and GT Simulator3 compares that entry against the FX5U CPU in the GX Works3 project and refuses to start.
This fault has nothing to do with the network — the simulator never opens an Ethernet connection. The generic FX entry looks like the only logical choice when you scan the controller list quickly, but it is exactly what the mismatch message is complaining about. Open the controller setting in GT Designer3, move the PLC type from the generic FX entry to the entry that names your CPU, the FX5U, and leave the channel pointed at Ethernet. Check the other half of the comparison too: the GX Works3 project must be created for the CPU you actually use, an FX5U-32MR/ES for instance, because a project built for a different CPU fails the same check.
Do I start the PLC simulation or the screen simulation first? #
Start the GX Works3 PLC simulation first and launch the GT Designer3 screen simulation only once the simulated CPU is running: the screen project connects to the simulated PLC like it would connect to real hardware, so the target must already exist.
There are two working routes. Route one: start the simulation from GX Works3, wait until the simulated PLC is in RUN, then start the screen simulation from GT Designer3 and it attaches to the simulated CPU. Route two: set up the GT Simulator3 project yourself, select the PLC project file you want it to load, and give it the same FX5U controller type you set in the GT Designer3 project. Route one is the fast path for a bench test; route two is better when you want the simulator to own the connection. Once the simulated screens behave, the next honest test is testing an HMI simulation against a live PLC, because no simulator reproduces driver timing and wiring.
How do I verify the comm error is actually cleared? #
The error clears within a few seconds of GOT startup, and the proof is a device you drive from both ends: change a value in the GX Works3 device monitor and watch it move on the GOT, then operate a GOT switch and watch the PLC device change.
Use a spare register or bit for this test, not an output that drives the machine. A lit link LED on both RJ45 connectors with a persistent comm error means the physical layer is fine and a setting is still wrong, so go back to the two screens and confirm the power cycle actually happened after the last write. A link that runs for minutes and then drops is a different problem entirely, and it follows the intermittent HMI-to-PLC Ethernet comms hang diagnosis.
What still breaks the link after the settings match? #
Most leftovers are process slips: the PLC was never power-cycled after the write, the GOT project went down without its communication settings, the two ends share one IP address, or the wrong controller type survived in a copied project.
Before you escalate anything, tick every line of this checklist:
- Your exact GOT variant shows an Ethernet port in its data sheet.
- The PLC IP address, subnet mask and MELSOFT TCP/IP port were read from the FX5U parameter screen, not from memory.
- The GT Designer3 controller setting holds the PLC's address, the same port and the FX5U controller type.
- The GOT's own address sits in the same subnet with a different host address.
- Parameters were written and the PLC power-cycled after the last change.
- The GOT project was downloaded with its communication interface settings.
- Link LEDs are lit on both RJ45 connectors.
- One device value moves in both directions.
Every line ticks and the GOT still reports a comm error, the fault lies outside the settings — take the configuration to the manufacturer's support channel.
Questions asked
Can I keep my laptop on the same link while the GOT talks to the FX5U?
Yes, through an Ethernet switch. A direct cable suits a two-device bench, but a laptop, the PLC and the GOT need a small switch between them. Put all three stations in the same subnet with different host addresses, for example 192.168.3.11 for the laptop, 192.168.3.19 for the FX5U and 192.168.3.50 for the GOT, and keep the port numbers as configured. GX Works3 online monitoring and the GOT connection then run alongside each other.
Does the same setup work over Modbus TCP instead of the MELSOFT driver?
The network rule is identical: both ends need addresses in one subnet and the GOT must target the PLC's address. Only the driver changes. Select the Modbus TCP driver in the GT Designer3 controller setting instead of the MELSOFT driver, enable the matching service in the FX5U built-in Ethernet parameters, and address GOT objects by Modbus register number mapped to FX5U devices rather than by direct device names. The GT2104-PMBD data sheet lists MODBUS among its network options, so the small terminal supports it.
What should I have ready before contacting Mitsubishi Electric support?
Work through the checklist first, then collect the GOT model and its OS version, the GT Designer3 and GX Works3 versions, screenshots of the FX5U Ethernet module parameters and of the GT Designer3 controller setting, and a note of whether the link LEDs light on both RJ45 connectors. With those items a support engineer can read the entire configuration without another round of questions.
Why does my screen work in simulation but show a comm error on the real GOT?
GT Simulator3 emulates the PLC, so the screen never opens a physical Ethernet connection and a wrong IP address, subnet or port cannot fail there. The mismatch only shows up when real hardware opens the driver. Treat a clean simulation as proof of screen behavior only, then confirm the FX5U parameters were written and the PLC power-cycled before judging the hardware link.