hms_support
- Actividad total 87
- Última actividad
- Miembro desde
- Siguiendo 0 usuarios
- Lo siguen 0 usuarios
- Votos 0
- Suscripciones 30
Comentarios
Actividad reciente de hms_support-
@bvorrie Is there network LAN adapter set statically in the same subnet as their eWON's LAN IP?Also, can you see the device in the ebuddy software?
-
@bvorrie Do you know if their PCs LAN adapter is set in the same subnet as their eWON LAN IP?Can they ping the PLC?
-
@bvorrie You can use eBuddy or the interface to change the LAN IP of the eWON. It does require a reboot if you do change it through the interface. If you are connecting remotely through eCatcher, y...
-
@Ryan_Nordhus Cosy 141 - DI / DO To configure the digital input, you can do this through the internet wizard as seen by our getting started video step 2 (180 seconds): https://youtu.be/viQR6U2qMHU?...
-
@sjackson Yes, if you have internet to the device and it can pass the online test (no IP conflict) then forcing TCP could (like it has) resolve your issue because the network is only allowing an op...
-
@sjackson Are you able to get an internet connection from that cable in general?If so, does the eWON pass the internet wizard test with "test online address' enabled?
-
@Julia_A_Foster_x_468 Have you ever configured the 2 rockwell devices to communicate successfully? "There's another option other than NAT 1:1. We could open up the WAN to LAN traffic completely whi...
-
@Julia_A_Foster_x_468 Your device appears to be configured correctly for NAT 1:1. If the PLCs use some sort of broadcasting or low level exchange (ARP) then that may not pass through the NAT 1:1 bu...
-
@Julia_A_Foster_x_468 You should be able use the mapped WAN IP to communicate with the PLC on the eWON's LAN. Have you changed the advanced parameters for WANITPROT and FwrdToWAN?Those values need ...
-
@Julia_A_Foster_x_468 Yes, this should work, NAT 1:1 should allow all traffic to be routed to that LAN device. WAN to LAN access should not cause IP conflicts if the WAN & LAN are in different subn...