Hello everyone,
New Ignition 8.1 gateway going in for the dryer line, talking to a ControlLogix 1756-L73 behind a 1756 EN2T. Added the device with the Logix driver, IP and slot 0, and it sits there Faulted. Gateway log says connection request failed, extended status 16#0100.
That EN2T already feeds two PanelView Plus 7 terminals and a FactoryTalk Historian, and there's a Kepware box for MES somewhere on the same switch, and all of those are happy.
I disabled the Windows firewall on the gateway server, deleted the device and added it again, then tried a second gateway on my laptop with the same driver, same 16#0100 both times. Browsing the EN2T with RSLinx from the laptop shows the L73 fine.
Is 16#0100 a driver version thing? Gateway's on 8.1.3x, whichever the current one is. Or is that EN2T simply full, with two PanelViews, the Historian and a Kepware box already hanging off it?
Not the driver. Before anything, how many connections does that EN2T already have open? Two terminals, a historian and a Kepware box is a lot of class 3 traffic through one module. What's the EN2T firmware and what poll rate did you set in the device?
EN2T's on 10.something, I'd have to check. Device poll is default. The Kepware box has one channel to that PLC that I know of.
Historian is subscribed to about 900 tags.
16#0100 is the extended status for connection in use or duplicate forward open. The EN2T has no room for another connection on that path. The ceiling is a couple of hundred CIP connections on that module, don't hold me to the exact number, and each HMI shortcut and driver instance chews through several.
Open the EN2T's web page, Diagnostics, Connection Manager, and look at current connections against the max it reports there. If you're at the ceiling, free some: stale shortcuts on the PanelViews, a second driver instance somebody left in Kepware, an old RSLinx OPC topic. Long term, a second EN2T in the rack for SCADA traffic.
There's a writeup on where SCADA traffic should land in a Logix rack: https://plctr.com/introduction-to-scada-systems-and-their-integration-with-plc/
Web page says 251 of 256. Found two shortcuts on one PanelView pointing at a controller that doesn't exist any more, deleted them, rebuilt the MER. Counter dropped to 245. Ignition still faults with 16#0100.
Eleven free isn't enough, I reckon the Logix driver opens more than one on a large tag set. Look at the Kepware box properly, a contractor usually leaves a duplicated channel behind. And check Kepware's connection size setting on that channel, if it's set to 4000 with unconnected fallback off it's holding more than you think.
Kepware had two channels to the same L73, one named Dryer and one named Dryer_old, both enabled, both polling. Disabled Dryer_old. Counter dropped to 223 and the Ignition device went Connected inside a minute.
So 16#0100 here was nothing more than the EN2T running out of CIP connections on that path, and killing the duplicate Kepware channel plus the two dead HMI shortcuts made room. Second EN2T is on order anyway and the SCADA is going on its own module.
Not sure why the counter only dropped 22 for a whole channel, I expected more than that. Whatever.
Thanks rsdave, scott_m.
Dryer_old. There's always a Dryer_old.