Melsec TCP connection issues
Hi,
I have two Flexy 205's that have recently started frequently rebooting, followed by issues communicating with our FX5U Mitsubishi PLCs. I can see in the event logs that they line up with the following:
System Booting, FWR: 14.5s1 (14.5), SN: 2238-0791-24 [EF0000]
Reboot reason: Watchdog in process (pppl)
After the reboot, the tag values do not update unless I reset the PLC remotely, which restores the connection.
What could be causing this and how do I go about resolving it?
-
Hi Masayoshi Kuwabara,
Are you currently using any scripts, such as Basic Programming or Java Programming, on your Flexy device?
Sometimes, something (like for ex the cyclic section) in the script can overwhelm the Flexy and potentially trigger watchdog reboots. To rule this out, you might try disabling the scripts or removing any Java code temporarily to see if this resolves the issue, helping to determine if it’s related to custom programming.
Alternatively, does the reboot only occur when accessing the Flexy’s webpage, especially on the Tags page? If so, adjusting the auto-refresh rate might help. The default rate is one second, but increasing it to 10 or 20 seconds can give the Flexy more time to process values and prevent overloading.
One thing that caught my attention is that you mentioned two Flexys experiencing reboots. Are you using a backup of one Flexy on the other? Typically, this shouldn’t cause reboots—at most, it could result in disconnections if not set up correctly if i remember correctly. Could you confirm if you've run the Talk2M wizard properly on the device using the backup? When using a Flexy backup, it’s essential to run the Talk2M wizard on the second device to ensure it connects as a new, unique entry in Talk2M.
I hope this helps. If the issue persists, we can proceed with creating a support ticket for further investigation.
Best regards,
i.A. Franziska Gültig
0
Please sign in to leave a comment.
Comments
1 comment