I have an SVRX with CoDeSys activated and running, and the CoDeSys runtime is communicating with 2 other external 3rd party CoDeSys PLCs. This all is working well. The issue I’m having is when I use Easy Access to connect to the SVRX (which I can do successfully), I attempt to pass through the IP addresses of the 3rd party CoDeSys IP addresses, but I can’t take them online, it gives me a device hardware error saying the hardware target is incorrect, and it appears like the CoDeSys gateway is seeing the Weintek SVRX CoDeSys device description instead of the 3rd party PLC, despite using the downstream (passed through) PLC IP address. Is there an issue when using EasyAccess to pass through a CoDeSys eth port to other CoDeSys devices? Is this a limitation of Easy Access or the CoDeSys gateway?
The system itself is working great, it’s only my ability to remotely connect over Easy Access that is having issues I have not seen before. Below is a rough sketch of the system layout for clarity.
Hi @kcoiner,
The pass-through feature only works via the HMI’s LAN port. It is not compatible with the CODESYS LAN port. So, to achieve passthrough you will need to connect the HMI’s LAN 2 port to the 3rd-party CODESYS PLCs as well. The image below is an example:
1 Like
Understood, that explains my problem!
Will the passthrough have any issues if LAN2 is DHCP while the CoDeSys/LAN1 and all of the machine network devices are on fixed IP addresses on a different subnet? ex:
DHCP assigns SVRX LAN2 to 192.168.0.5
SVRX LAN1 is 192.168.1.31
Other devices on the switch are at 192.168.1.■■■
Can EA pass through the devices at 192.168.1.■■■ even though it’s “looking” via the SVRX LAN2 port set on the “192.168.0” subnet?
The HMI’s LAN2 port will need to be on the same subnet via proper subnetting techniques to reach the 3rd party CODESYS devices. If you are using a 255.255.255.0 subnet, you will need to change the IP to 192.168.1._. However, a subnet mask of 255.255.254.0 should allow the LAN 2 port to reach those devices without modifying the IP.
The pass-through feature was designed to enable users to access a PLC that is communicating with an HMI via a device driver like the “CODESYS V3 (Ethernet)” driver for the purpose of monitoring or updating the PLC program. However, in networks with strict security measures or complex routing, this feature may not function as intended.
1 Like
Perfect, I think that makes sense. I’ll test it out! I believe the network will end up greatly simplified, there are no advanced routing rules, the firewall between the SVR and the Weintek VPN server has already been setup to allow communications and tested successfully. There is nothing between the SVR and the other devices, so I suspect once we get both SVR ports going to my unmanaged switch that also has the other CoDeSys devices on it, EA passthrough SHOULD be able to passthrough anything (with proper subnet mask setting!)
As always, I appreciate your helpful and speedy responses!
1 Like
