A previous application is installed and running on the factory floor.
HMI screens communicating with ladder logic, starting & stopping pumps and machine functions.
Digital and Analog I/O values coming to the HMI screen OK.
I can make changes to the screens and download to the HMI successfully.
With EasyRemoteI/O I can view the modules, scan them, and see live values on my laptop just as they appear on the HMI.
But when I open Codesys ladder and try to login, I get an error message:
“No connection to the device. Please rescan your network”.
Pretty sure the IP addresses are all OK, laptop communicates with HMI, laptop communicated with IRETN module, and the ladder logic communicates with I/O.
Is this asking for a rescan of the I/O with Easy Remote I/O?
I can do this but not sure it is the problem. If it is needed, how do I give the Codesys a “fresh look” at the **.eriop file from Easy Remote I/O?
Thanks in advance for your help.
Another thought I had is to create a “New Project” file in the laptop and then just upload the Codesys app that is in there running.
If I create a new project, what type should I select. I picked the simplest format (I thought) but it still would not login to the online logic that was running.
I guess my “new” project must have enough structure to make a connection to the logic running in the HMI. What type should I use?
Regards, Mike Clifford
Hi @mike_c_56,
This message indicates that the Codesys gateway cannot connect with the Weintek’s built-in Codesys. In order to connect with Codesys your PC must be connected to LAN 1 on the HMI or LAN 2 while “Codesys login” is enabled. When you have time, please review the instructions below and advise if you are able to connect with Codesys using this method.
- Connect your PC to the HMI’s LAN 2 port and follow the instructions to enable “Codesys login” as shown within 6:10 - 8:18 of this tutorial: Link
Note: The location of the “CODESYS login” function may vary by device type and firmware. The three possible locations of this option are shown below.
-
Note: The “CODESYS login” option may reside within the “Network” settings menu: Tutorial.
-
Note: The “CODESYS login” option may reside within the “CODESYS” settings menu under the “Modify Ethernet(LAN1)” option: Tutorial.
-
Note: The “CODESYS login” option may reside within the “CODESYS” settings menu within the web server. Here is a link to a post in which we demonstrate how to access the HMI’s webserver: Link.
-
Within the Codesys project tree, double click “Device (Weintek Built-in CODESYS”:
-
Select the “Gateway” and click “Add Device…”:
Note: If the “Device” tab appears as depicted below, please enter the HMI’s LAN 2 IP within the entry box on the far right and click the [Enter] key. After which, you may skip steps 4 - 6 as they will not apply.
-
Within the following menu, enter the IP address of the HMI’s LAN 2 port:
-
The HMI will append to the Gateway instance:
-
While the HMI is selected, click on the “Set Active Path…” button:
-
When finished, it should now be possible to login to Codesys.
Thanks Brendon, I will check the “Enable Codesys Login” setting.
My devices are connected thru a simple ethernet switch.
Below are sample connections and my specific machine wiring diagram.
Do these look OK to you? I will check the Settings when at the plant.
@mike_c_56,
Those settings appear to be fine, please let us know if you are able to connect with this device when at the plant.
Brendon, problem resolved. The “Enable Codesys Login” was off. I dont believe anyone turned it off. Plant personnel had not been into the HMI. However, when we first powered up the unit, we had an I/O alarm because one of the analog modules had no 24vdc connected.
This condition showed an alarm in EasyRemoteI/O.
Is it possible this condition caused the “Enable Codesys Login” to be switched off by the system??
To resolve this we wired 24vdc to analog module and switched the “EnableCodesyLogin” back on and the laptop connected immediately. Thanks for your help.
@mike_c_56,
Sorry for the delay, the “Codesys Login” feature will not be disabled by alarms that originate from connected IO. This feature can only be altered within the HMI’s settings menu or the webserver.
