# Allen-Bradley Logix Driver (not Legacy) **URL:** \ **Category:** Ignition\ **Created:** [May 27, 2022, 5:11pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-not-legacy/60134 "2022-05-27T17:11:35Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![jshannon](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jshannon/32/81937_2.png) [@jshannon](https://forum.inductiveautomation.com/u/jshannon)\ **Post date:** [May 27, 2022, 5:11pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-not-legacy/60134/1 "2022-05-27T17:11:35Z")
I’ve been trying to find a way to find out status information on allen bradley logix processors without having to go into each processor and use a GSV. The default diagnostics tags within ignition actually show some information including processor status. The “Status” tag long integer actually correlates to GSV instruction data within a processor. I want to hijack the driver and grab “Audit” information like forces and program changes. If the driver is grabbing status there should be a way to grab audit information. This is the table that correlates the status long integer in ignition to actual Allen Bradley information: ![41256-01](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/f/af4b3dbd573737852f7f40030ca8aee6c930c687.png) ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [May 27, 2022, 5:25pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-not-legacy/60134/2 "2022-05-27T17:25:27Z")
The diagnostics you’re talking about actually come from reading the CIP IdentityObject, a standard object available in any CIP product, and not from any ability of the driver to execute GSV instructions or equivalent. That Rockwell puts the same status value into the IdentityObject status member is just a convenient coincidence. If the information your looking for is available via a documented Class Id, Instance Id, and Attribute Id, then it might be something the driver could be modified to obtain as a feature, but you’re not going to “trick” it into reading anything like that. ---
**Author:** ![jshannon](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jshannon/32/81937_2.png) [@jshannon](https://forum.inductiveautomation.com/u/jshannon)\ **Post date:** [May 27, 2022, 5:44pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-not-legacy/60134/3 "2022-05-27T17:44:49Z")
Thank you Kevin, that is interesting. The information I am looking for looks like this: ![CIP GSV](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/1/b1904aab8d3e09528825361c69edaa7df66ba033.png) Again, I appreciate the help. ---
**Author:** ![jshannon](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jshannon/32/81937_2.png) [@jshannon](https://forum.inductiveautomation.com/u/jshannon)\ **Post date:** [May 27, 2022, 5:46pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-not-legacy/60134/4 "2022-05-27T17:46:20Z")
Did they just swap “ID” with “Name”? Hopefully since it is a “CIP Generic” message it may be standard. ---
**Author:** ![jshannon](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jshannon/32/81937_2.png) [@jshannon](https://forum.inductiveautomation.com/u/jshannon)\ **Post date:** [May 27, 2022, 6:08pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-not-legacy/60134/5 "2022-05-27T18:08:23Z")
Basically I am trying to find out if changes have been made to the program and if any forces are installed. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [May 27, 2022, 6:10pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-not-legacy/60134/6 "2022-05-27T18:10:13Z")
Consider using a message instruction in the PLC to pull this into a tag Ignition can read (on some interval). ---
**Author:** ![jshannon](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jshannon/32/81937_2.png) [@jshannon](https://forum.inductiveautomation.com/u/jshannon)\ **Post date:** [May 27, 2022, 6:56pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-not-legacy/60134/7 "2022-05-27T18:56:53Z")
I was looking at that too Phil but I didn’t want to have to set up every processor throughout the company. I was hoping to use something in python to grab status. I’ve checked out the pycomm3 module but still a little leery about it. I may just make an aoi to make it easier to import into each processor. I was reading into that through another question someone had posted years back. ---
**Author:** ![jshannon](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jshannon/32/81937_2.png) [@jshannon](https://forum.inductiveautomation.com/u/jshannon)\ **Post date:** [May 27, 2022, 7:00pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-not-legacy/60134/8 "2022-05-27T19:00:41Z")
Could also use a generic cip message to grab the information from another processor. Would be pretty cool and interesting if ignition could send generic cip messages. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [May 27, 2022, 7:13pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-not-legacy/60134/9 "2022-05-27T19:13:58Z")
> [@jshannon](#): > > Would be pretty cool and interesting if ignition could send generic cip messages. Well, yes, it _ **IS** _ pretty cool. > [@Snappy user interfaces with the Ethernet/IP Module](https://forum.inductiveautomation.com/t/snappy-user-interfaces-with-the-ethernet-ip-module/12617): > > Automation Professionals [Ethernet/IP Class1 Communications Module](https://www.automation-pros.com/modulesales.html) has been in beta for a few months with no recent issues. A release to production use is approaching soon and I thought I’d share a test project and its matching PLC code I’ve been using to exercise the module’s base features. In the simplest setup, this driver presents a virtual I/O chassis to to the outside world, populated with up to 100 virtual I/O modules – I/O modules that also appear to be ControlLogix processors with user… > [@Ethernet/IP I/O Module](https://forum.inductiveautomation.com/t/ethernet-ip-i-o-module/12362): > > Automation Professionals is pleased to announce the public beta for its latest module in the showcase: [Ethernet/IP Class 1 Communications](https://inductiveautomation.com/moduleshowcase/module/automation-professionals-llc-ethernetip-class-1-communications):[quote]Provides I/O Scanning and I/O Emulation on top of partial emulation of a Logix processor (Controller Tags and User-Defined data types). Use robust, low latency UDP packets to communicate with Logix processors as one or more I/O modules (passive slave mode), and with a variety of Ethernet/IP I/O modules as an I/O scanner (active master mode). With the Co… Buried in the above module (premium version) is the ability to construct properly-encoded CIP requests and decode the responses. The scripting is, unfortunately, somewhat difficult to work with and poorly documented. /: A major upgrade that will simplify your use-case is in the works. I was hoping to release a beta in Q1, but that plan hit some rocks. (A refactoring of +42k -25k LOC, so far.) The refactor is to support a whole bunch of client features, including class/instance/attribute access. I'm regression testing a big chunk of it right now. (: ---
**Author:** ![jshannon](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jshannon/32/81937_2.png) [@jshannon](https://forum.inductiveautomation.com/u/jshannon)\ **Post date:** [May 27, 2022, 7:36pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-not-legacy/60134/10 "2022-05-27T19:36:21Z")
Phenomenal Phil. I was checking out your module btw. And I was confused but confusion is in my dna. I will remain patient for the new release. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [May 9, 2023, 7:07pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-not-legacy/60134/11 "2023-05-09T19:07:32Z")
Huh. It's been a year since that rosy timeline. But direct support for CIP attributes is now available as a beta: > [@Automation Professionals' EtherNet/IP Communication Suite V2](https://forum.inductiveautomation.com/t/automation-professionals-ethernet-ip-communication-suite-v2/68190/88): > > Automation Professionals is pleased to announce beta availability of the next significant feature of this driver: Arbitrary CIP attribute read/subscribe/write support via class+instance+attribute ID codes. If you have various devices in your facility that expose useful information this way (drives and servos...), the desired information can be read via class 3 messaging as part of the new Client driver. Note that I/O assembly buffers are attributes, and are therefore accessible with this new … ---
**Author:** ![jshannon](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jshannon/32/81937_2.png) [@jshannon](https://forum.inductiveautomation.com/u/jshannon)\ **Post date:** [May 10, 2023, 6:29pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-not-legacy/60134/12 "2023-05-10T18:29:55Z")
Interesting