I'm having issues connecting to a CompactLogix processor. It is set up as a dual IP, and we've confirmed that it is configured as such. It is not on any kind of back-plane, so there shouldn't be any need for a 'path' identification. Has anyone else had issues connecting to this gen CompactLogix? We are connecting through Port A2. I can ping the IP address via the command prompt, but it will not connect using the driver. This is the first time I haven't been able to connect to a processor when I am able to ping it. The controller is a 5069-L320ERMS3 running V34.11. I've been using the 'Logix' driver for v21+, but I have also tried the 'ControlLogix' and 'CompactLogix' drivers for pre v21 with no luck.
There's a number of references here in the forum to people using a 5069-L320, so it's not some fundamental incompatibility. Usually the issue is with getting the path right for routing through an L320 with its dual ports, but that's not the case here.
The 0x0311 extended status we're getting from the device is defined as:
PORT NOT AVAILABLE
A Port specified in a Port Segment is Not Available or does not exist.
The implicit connection path here is 1,0 (backplane, slot 0), so perhaps there's some additional configuration that needs to be done to allow this port to be used...
On the 5069 platform, the A1 port is the Enterprise port, so Ignition needs to be connected to that port (This is the port closest to the front of the unit.)
Any local networks such as drives and remote racks should be connected to the A2 (Local) Port.
From the User Manual (pg 118):
Dual-IP Mode
Dual-IP mode lets you connect ports A1 and A2 to separate networks. In this mode, port A1 can connect to an enterprise-level network or a device-level network. Port A2 can only connect to a device-level network.
Hmmm. I'll have to test in my lab, but this shouldn't be a problem. The "device" layer only omits DNS request capability.
Consider trying my alternate driver, and specifying no route path at all. I've encountered CompactLogix devices that did not like the "1, 0" path that IA's native drivers insist on using.
I have multiple CompactLogix controllers connected, all using the A1 port, no issues. All using the native IA driver.
Not discrediting what you’ve seen, it’s entirely possible I just haven’t seen it. The only time I’ve had an issue was when I was plugged into the A2 port by mistake.
