RSLinx - Ethernet Networks - Problems and Solutions

What are some of the issues regarding RSLinx connection to processors on an Ethernet Network?
The purpose of this technote is to compile a number of issues regarding RSLinx connection to processors on an Ethernet Network.

Problem:

• RSLinx cannot browse devices using AB_ETHIP-1 (Ethernet/IP Driver).
• However using AB_ETH-1 (Ethernet devices) Driver does work fine.
• PING is successful to the desired IP Addresses. Windows Firewall has been disabled.
• Driver AB_ETHIP-1 has been configured for '(x) Browse Local Subnet'.

Solution:

This problem can be caused by the computer having multiple network adapters.
Change Driver AB_ETHIP-1 configuration to '(x) Browse Remote Subnet'.

• IP Address: <Enter the IP address on any device which is located on the remote subnet.>
• Subnet Mask: <Enter the subnet mask of the remote subnet.>

---

Problem:

RSLinx is installed on computers that are connected on networks other than 10Base Ethernet networks, such as Token Ring and 100Base Ethernet.

Solution:

RSLinx will work with any type of TCP/IP protocol based network. RSLinx accesses the Network Interface Card in the computer through what is known as the WinSock. As long as a working TCP/IP protocol is configured on the computer, RSLinx will communicate through it out onto the network. However, the Rockwell Automation processors, at this time, are only designed to operate on 802.3 10Base Ethernet networks. If the computers are on a network other than 10Base, a bridge or a router device will be required to connect the computers on one type of network to the processors on the 10Base Ethernet network.

---

Problem:

Able to PING a processor on the other side of a router but not communicate to it.

Solution:

The processor was initially configured with Class A IP address and the router was configured to only allow message packets to Class C network addresses to be sent through. This meant that the router permitted the ping command but not any messages to route through. Once the IP address on the processor was changed to a Class C, RSLinx could communicate to it.

---

Problem:

Not able to ping processor connected to 10/100 speed 2900XL Cisco switch. RSLinx shows the processors as unrecognised devices.

Solution:

The network card was designed to operate at both 10 and 100 Megabit speeds. Since switch could operate at both 10 and 100 speeds the card switched to the fastest speed that the switch could handle. Solution is to use a Network Interface Card in the computer that will only communicate at the 10 Megabit speed.

---

Problem:

Business network traffic is causing delays or time-outs of data requested from processors on the manufacturing or plant network.

Solution:

Install an additional Network card in the computer and have it set up to address only the manufacturing/plant network.
The best solution this is to use a different subnet and IP addresses for the business and manufacturing/plant network.
This will segregate the traffic. If a router is included in the network additional routing tables will have to be configured in the router to ensure the message packets get routed properly.

---

Problem:

Attempt to use RSLinx Gateway to connect from one Ethernet network to another Ethernet network does not work.

Solution:

RSLinx does not have the capability to route from one physical Ethernet network to another at this time. An Ethernet router would be required to connect the two different networks.
NOTE:  As of RSLinx 2.20, routing from the client Ethernet network to another Ethernet network is supported through the AB_ETH drivers configured on the RSLinx Gateway.

---

Problem:

Connecting to a PLC-5 via Ethernet using the RSLinx Ethernet driver and wanting to pass thru to a different network,
such as a DH+ or DeviceNet.

Solution:

The PLC-5 hardware does not have any pass thru capability.

---

Problem:

OPC client read items from SLC-5/05 thru RSlinx OPC Server via Ethernet, but it is not stable. Ethernet/IP Driver is congiured in RSlinx.

Solution:

Use Ethernet Device Driver for RSlinx OPC Ethernet communication rather than Ethernet/IP driver.

Source : http://rockwellautomation.custhelp.com/app/answers/detail/a_id/7480/related/1