RSLinx shows the processors as unrecognised devices. Not able to ping processor connected to 10/100 speed 2900XL Cisco switch. Once the IP address on the processor was changed to a Class C, RSLinx could communicate to it. This meant that the router permitted the ping command but not any messages to route through. 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. 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.Īble to PING a processor on the other side of a router but not communicate to it. However, the Rockwell Automation processors, at this time, are only designed to operate on 802.3 10Base Ethernet networks. As long as a working TCP/IP protocol is configured on the computer, RSLinx will communicate through it out onto the network. RSLinx accesses the Network Interface Card in the computer through what is known as the WinSock. RSLinx will work with any type of TCP/IP protocol based network. RSLinx is installed on computers that are connected on networks other than 10Base Ethernet networks, such as Token Ring and 100Base Ethernet.
RSLINX CLASSIC INHIBIT CONNECTION DRIVER
This problem can be caused by the computer having multiple network adapters.Ĭhange Driver AB_ETHIP-1 configuration to ' (x) Browse Remote Subnet'. Driver AB_ETHIP-1 has been configured for ' (x) Browse Local Subnet'.PING is successful to the desired IP Addresses.However using AB_ETH-1 (Ethernet devices) Driver does work fine.RSLinx cannot browse devices using AB_ETHIP-1 (Ethernet/IP Driver).The purpose of this technote is to compile a number of issues regarding RSLinx connection to processors on an Ethernet Network. Has anyone dealt with this scenario before? It's almost like Classic waited a few seconds before providing data to the OPC client where as FTGateway has nothing connected so defaults to "0, Bad, Out of Service".What are some of the issues regarding RSLinx connection to processors on an Ethernet Network?
Something must be different in the way initial values are handled between Classic and FT Gateway. So basically it looks like everything tripped off for a few seconds. If I use FT Gateway, I can troubleshoot but if I flip servers it logs a "0", Bad Quality, Out of Service for every single tag for a bit until it gets the initial value from the PLC. But at least when I flip servers (to redundant one) it doesn't log a "0" and flag the quality as "Bad, Out of Service" for the new initial value. If I use RSLinx Classic Gateway I can't easily troubleshoot (due to service mode) and the performance isn't quite as good as FT Gateway.
RSLINX CLASSIC INHIBIT CONNECTION SOFTWARE
Software in between the controller and the ABB PLCConnect server is either RSLinx Classic Gateway or FactoryTalk Gateway w/ RSLinx Enterprise.
0 kommentar(er)
