# Can't Connect to a Mitsubishi FX3GE **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [April 17, 2026, 9:50am UTC](https://forum.inductiveautomation.com/t/cant-connect-to-a-mitsubishi-fx3ge/115136 "2026-04-17T09:50:01Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![valon\_beka](https://avatars.discourse-cdn.com/v4/letter/v/ecb155/32.png) [@valon\_beka](https://forum.inductiveautomation.com/u/valon_beka)\ **Post date:** [April 17, 2026, 9:50am UTC](https://forum.inductiveautomation.com/t/cant-connect-to-a-mitsubishi-fx3ge/115136/1 "2026-04-17T09:50:01Z")
Hi everyone, I’m having trouble reconnecting to a Mitsubishi FX3GE PLC. The connection status is stuck at **ReconnectWait** (see screenshot), and I can’t seem to get it back online. A bit of background: - This setup was working a couple of months ago and ran fine for about a week. - During that time, data was successfully logged to the database. - Since then, the connection stopped working without any changes to the setup (no config changes, network changes, or updates). What I’m seeing now: - All tags show **Bad** quality. - Deleting and recreating tags didn’t help. - I’ve tried adding a new TCP port configuration. - Restarted the PLC and the system. - Still stuck in ReconnectWait with no data coming through. Additional info: - Communication **does work in System2000** , where I can still see live tag values. - There is **no SLMP option available** in the driver settings (as shown in the screenshot). At this point I’m not sure if it’s a driver issue, communication setting, or something else entirely. Has anyone experienced something similar or knows what might cause this? Any suggestions would be appreciated. Thanks in advance! ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/7/077ec99f1cf808045daf9259bec365ab13979624.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/a/aa579b0d7894868ddadf6396a96330f9d1c9ae98.png) ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [April 17, 2026, 11:19am UTC](https://forum.inductiveautomation.com/t/cant-connect-to-a-mitsubishi-fx3ge/115136/2 "2026-04-17T11:19:42Z")
ReconnectWait simply means that the connection is rejected every time Ignition actually tries to connect. If it never shows "Connecting..." that typically means each attempt is affirmatively rejected--usually by a firewall. You should run wireshark on your gateway with a capture filter of your target IP address. This will show you exactly what is happening, and you can get your IT involved. ---
**Author:** ![valon\_beka](https://avatars.discourse-cdn.com/v4/letter/v/ecb155/32.png) [@valon\_beka](https://forum.inductiveautomation.com/u/valon_beka)\ **Post date:** [April 17, 2026, 11:33am UTC](https://forum.inductiveautomation.com/t/cant-connect-to-a-mitsubishi-fx3ge/115136/3 "2026-04-17T11:33:10Z")
Hi, Thank you for replay, on powershell in gateway I can ping the PLC using Test-NetConnection and on the port 1287, I get TcpTestSucceded: True IT looked into it and can't see anything wrong from their side, we do have other PLC's connected and work fine, Also this worked for a week in same gateway and nothing has changed since! Also after a while I get "Connected" Message on gateway, but then if i go edit and just save without changing anything it's still stuck at ReconnectWait. so that Connected doesn't seem "real" ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [April 17, 2026, 11:36am UTC](https://forum.inductiveautomation.com/t/cant-connect-to-a-mitsubishi-fx3ge/115136/4 "2026-04-17T11:36:02Z")
> [@valon\_beka](#): > > worked for a week in same gateway and nothing has changed I find this hard to believe. You just haven't found it. Run wireshark in the gateway. Look at actual packets and responses. Consider changing the port number on both ends. It is possible something else is occupying it.