Have you ever used an **** Flexy for remote programming and maintenance of a Codesys-based controller? Our customer has chosen to use an **** Flexy instead of the native remote access functionality of our hardware. They have set up an eCatcher login profile for me, allowing me to successfully connect to the ****. While I am able to ping the IP addresses of our HMI and controller, I am unable to log in to the controller. However, I can access the HMI graphics using VNC. After reviewing a ***** Technical Support Document, it was recommended to enable the “BroadcastForwarder” parameter in the comcfg.txt file and activate the “PLC Discovery”, which our customer has already done. We are currently using CodeSys v3.5.10.5, with Gateway-1 set to "IP-Address: localhost" and "Port: 1217" in the Comms Settings. Despite manually entering the IP address of the device, CodeSys displays a "No Device is responding..." message. One consideration is whether the IP address for Gateway-1 should be "localhost" or the WAN/LAN IP of the ****. I have tried both options without success. Any suggestions or tips on what to investigate next would be appreciated. Thank you, Martin
For clarification, the acronym assigned by the Forum should be "e.w.o.n."
If you encounter a bug in the SP10 version of the gateway, simply install a newer version of the editor to resolve the issue. It's important to maintain your project at SP10 to prevent any library errors, or select 'don't update' when opening. Additionally, you won't be able to 'scan for devices'; instead, you must manually enter the PLC's IP address for connectivity. This troubleshooting tip can help maintain smooth operations and avoid technical setbacks.
Thank you for the information regarding the Gateway issue in SP10, @paraffin power. I have multiple versions of CodeSys installed (v3.5.13.30 and v3.5.17.0) and have tried opening my project and a new project in both versions, but I am still unable to connect to our controller through the e.w.o.n. I always enter the Controller's IP Address directly and do not use the Scan for Devices feature. Do you know of any specific settings in the e.w.o.n that I should review or adjust?
I utilize Service Pack 10 through Service Pack 17 for my system configuration. Although my gateway is currently set at Service Pack 17, I have also found it to function well at Service Pack 13. I am using a remote-access gateway that is similar to Ewon and have not experienced any issues. Is there any possibility that Ewon blocks certain ports?
Are you able to send a ping to check its connectivity?
Hey Martin, I faced a similar issue with **** Flexy before. It turned out to be a firewall problem. The firewall in the **** blocked the communication port of the controller. But the moment I opened the port in the firewall settings of the ****, everything worked fine. Also, for the Gateway-1, I used the LAN IP of the ****. Perhaps you could give it another shot with these considerations? Keep me posted on your progress!
Hi Martin, based on your description, it appears you've covered quite a bit of ground in troubleshooting. When using an eWON device as in your case, it's essential to have the correct gateway IP address. Generally, "localhost" refers to the device itself where the gateway service is running, but if there seems to be communication issues, adjusting this setting could be useful. You might try using the LAN IP of the **** as your Gateway-1 address instead of "localhost", and also check to ensure any firewalls aren't blocking communication. Alternatively, you might want to try using a different communication driver in Codesys. If the problem persists, it may be helpful to reach out directly to **** customer support. They tend to be quite responsive and might have encountered similar issues before.
Hey Martin, I faced a similar issue while using my **** Flexy with Codesys. What I realized was that my company's network security protocols weren't compatible and were causing the issue. You might want to check that your Codesys is configured to use the correct subnet that’s been assigned to your **** Flexy and the LAN devices. Additionally, ensure that the "Enable Broadcast Forwarder" option is activated in eCatcher or the **** Flexy web interface. This will essentially allow eCatcher to pass through the PLC discovery broadcast messages. If none of these work, consider reaching out to the Codesys support team, they were really helpful with my issue. Also, "localhost" means the device you are running it on, so you should rather enter the IP address of the **** Flexy. Keep troubleshooting, I hope this is of some help!
Hi Martin, it sounds like you're in a bit of a pickle! Since you're able to access the HMI but not the controller, you might want to double-check the firewall settings on both the Flexy and the controller. Sometimes, network communications can get blocked if the right ports aren’t open. Additionally, ensure that the CodeSys version you’re using is fully compatible with the controller’s firmware—minor version differences can occasionally lead to connection issues. Finally, if you haven't already, consider looking into enabling logging on CodeSys to see if there are any error messages that could give you a better insight into what's going wrong. Hope this helps!
Hey Martin! It sounds like you're making good progress, but I can see how frustrating those connection issues can be. Since you’ve already verified the BroadcastForwarder and the Discovery settings, double-check that the firewall settings on both the Flexy and the network don’t block the necessary ports for CodeSys communication. Also, ensure that the Codesys service is running properly on your controller. As for the Gateway-1 IP, it typically should be set to the local IP of the controller rather than "localhost" unless you’re working directly on the device itself. Maybe enabling some logging or diagnostics in the Flexy could provide more insight into where the connection is failing. Good luck, and keep us posted!
Hey Martin, it sounds frustrating that you're having trouble logging into the controller. From my experience, I think it's worth double-checking the firewall settings both on the Flexy and the Codesys controller. Sometimes, packets can be blocked, leading to connectivity issues. Also, make sure that the correct routing is set up on the Flexy to forward traffic to your controller’s LAN IP, since using "localhost" might not work as expected in a remote setup. If you haven't already, resetting the connection settings and power cycling the devices can sometimes help clear up lingering issues too. Good luck!
âś… Work Order Management
âś… Asset Tracking
âś… Preventive Maintenance
âś… Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: To troubleshoot connectivity issues, ensure that the "BroadcastForwarder" parameter is enabled in the comcfg.txt file, activate "PLC Discovery," and verify the settings such as Gateway-1 IP address. Consider checking if the correct IP address (localhost or WAN/LAN IP of the ) is set in the configuration.
Answer: If you encounter the "No Device is responding..." message in CodeSys, double-check the settings in CodeSys (such as Gateway-1 configuration) and ensure proper network connectivity between your devices. Verify that the IP address entered matches the actual IP address of the device.
Answer: If you can access HMI graphics using VNC but face issues logging in to the controller, focus on troubleshooting the connectivity and configuration settings specific to remote access and controller login. Review the Flexy's settings, network configurations, and CodeSys parameters to ensure proper communication between devices.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.