Flexy 205 to FX3U

Hi All.

Please bare with me, I’m quite new to all this and learning as i go along.

I’ve got a project which involves connecting a Mitsubishi FX3U to an EWON Flexy 205, creating the tags and eventually on to a SCADA system (Indusoft Web Studio).

I’ve fitted the EWON Flexy 205, changed IP address to match the company IP and can now access it of the WiFi network using the IP address.

I’m having an problem trying to get the PLC to talk to the EWON. I’ve set it up as much as i can in I/O servers. The PLC has a IP of 192.168.100.2 (previously set up by the company who installed it).

On the EWON, its asking for a port number to add after the IP address. Ive done some looking around online and it say port 5001 is default but im sill getting the RED ! in health when i look at values.

My I/O Server string is as follows: FX3UCPU,TCP,192.168.100.2,5001

Although it will not talk to the FX3U as no values show up after added an X1 for example.

Anyone help please?

Thank you.

Can you try port 5000 instead of 5001?

What is the Ewon’s LAN IP? I want to make sure the Ewon and PLC are in the same subnet, so if the PLC is using 192.168.100.2, the Ewon will probably need an address starting with 192.168.100.X as well.

Can you capture a support backup from the Flexy so we can check the logs and configuration? You can download one from the web interface under Diagnostic → Files Transfer by clicking “Support files” at the top right.

Hi Hugh,

I found the issue. The FX3U wasnt set up for melsec protocol. After setting this up, all is working fine.

Although i now have another issue.

The EWON looses connection to PLC every day. The values health shows RED ! on all values but a simple reboot of the EWON fixes this.

Is it possible set a scheduled reboot every day at 5am before production starts?

I think the cause of this is because the PLC does a reset on the counters every day and it appears to upset the EWON for whatever reason.

Thanks.

Ashley.

Heres a log:

07/08/2023 05:42:39 -22602 System Booting, FWR: 14.6s0 (14.6), SN: 2318-****-24 [EF0000] elog

04/08/2023 23:28:36 26804 stdios-Device ENTERS slow poll mode (MELSEC - Address ) mimcsrv

04/08/2023 07:39:31 -22602 System Booting, FWR: 14.6s0 (14.6), SN: 2318-****-24 [EF0000] elog

03/08/2023 11:11:47 26804 stdios-Device ENTERS slow poll mode (MELSEC - Address ) mimcsrv

03/08/2023 11:01:24 -22602 System Booting, FWR: 14.6s0 (14.6), SN: 2318-****-24 [EF0000] elog

03/08/2023 01:36:36 26804 stdios-Device ENTERS slow poll mode (MELSEC - Address ) mimcsrv

02/08/2023 09:08:23 -22602 System Booting, FWR: 14.6s0 (14.6), SN: 2318-****-24 [EF0000] elog

02/08/2023 08:28:39 26804 stdios-Device ENTERS slow poll mode (MELSEC - Address ) mimcsrv

02/08/2023 06:39:49 -22602 System Booting, FWR: 14.6s0 (14.6), SN: 2318-****-24 [EF0000]

Yes, on a Flexy you can very easily schedule a reboot every day using the BASIC IDE. In the Flexy’s web interface, navigate to Setup → Basic IDE, then enter the code below. Make sure Autorun is checked under the Run menu up top, then start the script with the script execution button to the top right. This will reboot the Flexy every morning at 5:00 local time, and Autorun will ensure the script starts automatically after the device boots.

ONDATE 1, "0 5 * * *", "REBOOT"

This code uses cron syntax to trigger the REBOOT command every day at 5:00 am. You can read more in RG-0006-01-EN - Programming Reference Guide

Thank you very much.

I guess changing the 5 to a 6 in the script means it will restart at 6am instead?

Is there a way to trigger the reboot on a plc input? E.G if a button is pushed in production, it will trigger a reboot of the device.

I’ve found that when a certain machine is stopped during non-production hours, this is when it resets the counters on PLC and kicks the EWON out. If i can make the EWON do a reboot when the machine is started, i think this will work fine. The reason being, if the machine isn’t stopped and started before 5am, the counters wont reset and if this isn’t done before the EWON reboot then it will require another reboot afterwards.

Thank you.

Another issue I’m having is the EWON wont read values from the extension I/O module on PLC. I have 3 extension I/O modules in total but the EWON wont read of any of them, only the main PLC.

E.G X055 is reading fine but X143 wont read at all. I’ve tried putting a 0 or two after the X like X0143 or X00143 but nothing. There is defiantly tags on X143 as i have the PLC ladder diagram and also the HMI design which show the tags.

Please see photo attached.

Thank you.

Yes, you can configure that as well. Suppose you have a tag called Button on the Ewon that’s polling from some input on the PLC. It has a value of 0 if not pushed and 1 if it is. You can set up BASIC to react to this tag like so:

ONCHANGE "Button", "IF Button@ = 1 THEN REBOOT"

What this does is execute the code in the second set of quotes whenever the value of Button changes. The code checks if the value of Button is 1, and if so, it sends the command REBOOT.

For the tag polling issue, can you try navigating to Tags → IO Servers → General → Global Settings, then checking “Disable Tags in Error” under Advanced Parameters? Tags are generally polled in batches, which means that a bad tag address for one tag can block many others from polling. This setting disables bad tags so you can isolate which ones are truly bad.

If they’re still not working, do the I/O modules have the same network number and PC number as the PLC itself? These are set in the topic settings, so you may need to configure other topics with the I/O modules’ settings.

You can read more about configuring polling using the MELSEC I/O server in AUG-0088-00 - Poll data from Mitsubishi PLC using Ethernet protocol

Thank you Hugh.

Im still getting the slow poll issue sometimes and have to manually restart the EWON.

How do make the EWON automatically reboot if it comes up with this error?

17/08/2023 06:16:53
26804
stdios-Device ENTERS slow poll mode (MELSEC - Address )


The I/O modules i assume have the same network number. Where do i find the topic settings?

Thank you.

Ashley.