[email protected]
Member
Hello, and thanks for providing these forums and taking the time to help us out.
I have a bunch of different Logix5000 and SLC 500 based PLCs hooked up to a plant's IT network.
When using a laptop with a RsLinx Ethernet/IP driver to browse the entire network it happens to crash two pieces of identical equipment in the facility which are both Logix5000 based.
The local equipment in question consists of a 9300-ENA for the uplink which goes to a 2 layer managed switch which then distributes to the PLC, an ASCII Gateway, and about 16 sonic welder ethernet gateways from Schneider Electric(http://motion.schneider-electric.com/products/ethernet_gateway.html).
As soon as I expand to see the contents of the Ethernet/IP driver in RSLinx, both of these machine's Schneider Ethernet Gateways for controlling the sonic welders, crash. The ethernet port communication light on the Sonic Welder Gateways goes from almost a steady green to a periodic pulse and the HMI reports the sonic points being offline. In order to fix the problem I have to ensure the Ethernet/IP driver is no longer browsing the network and the machine's power needs to be cycled.
The only thing I can think of that I may be doing incorrectly is that I am selecting the network adapter and IP address that was assigned to me by the DHCP server in the plant when setting up the Ethernet/IP driver and these sonic welding machines may be at a different third octet then the address that DHCP is assigning me.
If I plug directly into the machine's 2 layer managed switch and browse the network with the same driver,and the laptop's Ethernet adapter settings happen to be left on assign an ip address automatically, and I browse the Ethernet/IP driver contents it will crash the sonic welder gateways. If I manually assign it a local IP address I can communicate to the entire local network in the cabinet without a crash.
I can see how most of the connectivity guides suggest to browse a remote subnet if necessary with the Ethernet/IP driver in order to work properly but if IT has my network divided in such a way, must I always go and cross reference which subnet the devices I want to connect to are on and have to manually set this up before browsing to avoid a crash? No other equipment in the facility is affected as far as I can tell from the simple expansion of the driver in RSLinx.
Thanks guys!
I have a bunch of different Logix5000 and SLC 500 based PLCs hooked up to a plant's IT network.
When using a laptop with a RsLinx Ethernet/IP driver to browse the entire network it happens to crash two pieces of identical equipment in the facility which are both Logix5000 based.
The local equipment in question consists of a 9300-ENA for the uplink which goes to a 2 layer managed switch which then distributes to the PLC, an ASCII Gateway, and about 16 sonic welder ethernet gateways from Schneider Electric(http://motion.schneider-electric.com/products/ethernet_gateway.html).
As soon as I expand to see the contents of the Ethernet/IP driver in RSLinx, both of these machine's Schneider Ethernet Gateways for controlling the sonic welders, crash. The ethernet port communication light on the Sonic Welder Gateways goes from almost a steady green to a periodic pulse and the HMI reports the sonic points being offline. In order to fix the problem I have to ensure the Ethernet/IP driver is no longer browsing the network and the machine's power needs to be cycled.
The only thing I can think of that I may be doing incorrectly is that I am selecting the network adapter and IP address that was assigned to me by the DHCP server in the plant when setting up the Ethernet/IP driver and these sonic welding machines may be at a different third octet then the address that DHCP is assigning me.
If I plug directly into the machine's 2 layer managed switch and browse the network with the same driver,and the laptop's Ethernet adapter settings happen to be left on assign an ip address automatically, and I browse the Ethernet/IP driver contents it will crash the sonic welder gateways. If I manually assign it a local IP address I can communicate to the entire local network in the cabinet without a crash.
I can see how most of the connectivity guides suggest to browse a remote subnet if necessary with the Ethernet/IP driver in order to work properly but if IT has my network divided in such a way, must I always go and cross reference which subnet the devices I want to connect to are on and have to manually set this up before browsing to avoid a crash? No other equipment in the facility is affected as far as I can tell from the simple expansion of the driver in RSLinx.
Thanks guys!