# Allen-Bradley Logix Driver - Understanding Advanced Device Status from OPC Driver Tags in Ignition **URL:** \ **Category:** Ignition\ **Tags:** ignition81, vision\ **Created:** [February 21, 2025, 12:25pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-understanding-advanced-device-status-from-opc-driver-tags-in-ignition/102689 "2025-02-21T12:25:54Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![dhananjay\_vichare](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dhananjay_vichare/32/74712_2.png) [@dhananjay\_vichare](https://forum.inductiveautomation.com/u/dhananjay_vichare)\ **Post date:** [February 21, 2025, 12:25pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-understanding-advanced-device-status-from-opc-driver-tags-in-ignition/102689/1 "2025-02-21T12:25:54Z")
I am looking for more information regarding **Advanced Device Status** from OPC driver tags. I have referred to the Ignition documentation but couldn't find detailed information on **OPC UA Drivers - Root Diagnostics Tags**. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/b/9bccc506f50486287823a704469648d6f9f05f7f.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/0/d011103286ee9dcc75befa866c53c12f0b0e07d2.png) I have observed changes in the **Status** tag value while downloading the PLC program: - **12,400** : Appears during PLC program download. - **12,656** : Indicates the PLC is in **Program Mode**. - **12,640** : Indicates the PLC is in **Run Mode**. I believe that **12,400** represents an active PLC program download. However, I am looking for official documentation or confirmation on this. My goal is to track if someone is downloading the PLC program during the **night shift (third shift)**, which might result in overwriting the default values in the PLC and causing incorrect reports in the **first shift**. **System details:** - **PLC:** 1756-L71 - **Driver:** Allen-Bradley Logix Driver - **Ignition Version:** 8.1 (Vision) Could someone point me to where I can find detailed documentation on the **Status** tag values, or confirm if my understanding is correct? ---
**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:** [February 21, 2025, 1:45pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-understanding-advanced-device-status-from-opc-driver-tags-in-ignition/102689/2 "2025-02-21T13:45:05Z")
> [@Logix Device Status](https://forum.inductiveautomation.com/t/logix-device-status/24103/4): > > The CIP Spec has some generic definitions for the bits in that word in Volume 3, table 5A-2.3 and table 5A-2.4, and requires that the reserved/vendor bits there, if used, be declared in the device’s EDS file. Bit 0: "Owned". Not applicable to a processor, I would think. Bit 1: Reserved. Bit 2: "Configured". Probably always true except when at factory default. Bit 3: Reserved. Bits 4-7: 4-bit integer extended status code: 0: Self test/unknown 1: Firmware updating 2: Any Faulted I/O co… > [@Logix Device Status](https://forum.inductiveautomation.com/t/logix-device-status/24103/5): > > The following worked for me based on AB documentation of the status word. I created expression tags looking at the status word. Key Switch position. // Bits 12-13 represent key switch position. // Mask and shift right to positions 0-1. // Value - Description // 0 - Undefined // 1 - Run // 2 - Program // 3 - Remote ({[.]Status} & 12288)\>\>12 Processor Mode // Bits 4-7 represent processor mode. // Mask and shift right to positions 0-1. // Value - Description // 0 - Reserved… ---
**Author:** ![Chris\_Bingham](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@Chris\_Bingham](https://forum.inductiveautomation.com/u/Chris_Bingham)\ **Post date:** [February 21, 2025, 2:31pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-understanding-advanced-device-status-from-opc-driver-tags-in-ignition/102689/3 "2025-02-21T14:31:28Z")
> [@dhananjay\_vichare](#): > > My goal is to track if someone is downloading the PLC program Is it an option to add a GSV to the program - which would request the current audit value from the controller and store it to a tag - then read by Ignition? While that hash will increment during online (proper) edits, you might be able to build a more complete picture with the addition of the controller status bits as detailed in @Kevin.Herron's post (processor in program mode w/ new hash seconds later...). Depending on controller version, there should be a detailed audit log stored on the controller. The log contains an entry for nearly every action performed (by whom, and when) by a user of Logix software. Changes logged include going online, saving project, going offline, rung changes, comment changes, tag value changes, etc. ---
**Author:** ![Chris\_Bingham](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@Chris\_Bingham](https://forum.inductiveautomation.com/u/Chris_Bingham)\ **Post date:** [February 21, 2025, 2:43pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-understanding-advanced-device-status-from-opc-driver-tags-in-ignition/102689/4 "2025-02-21T14:43:51Z")
Here's a link to Rockwell Literature - Controller Logging: [https://literature.rockwellautomation.com/idc/groups/literature/documents/pm/1756-pm015\_-en-p.pdf#page=25](https://literature.rockwellautomation.com/idc/groups/literature/documents/pm/1756-pm015_-en-p.pdf#page=25) I would avoid writing anything to SD card on a scheduled basis. Read/write to the card only when necessary. Optionally, purchase FT AssetCentre, and store the audit log to SQL & send e-mails when a change is made. ---
**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:** [February 21, 2025, 2:44pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-understanding-advanced-device-status-from-opc-driver-tags-in-ignition/102689/5 "2025-02-21T14:44:14Z")
> [@Chris\_Bingham](#): > > add a GSV to the program If you know the class/instance/attribute codes for any of those, you can poll them with my alternate driver. Regardless of PLC mode. ---
**Author:** ![Chris\_Bingham](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@Chris\_Bingham](https://forum.inductiveautomation.com/u/Chris_Bingham)\ **Post date:** [February 21, 2025, 2:50pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-understanding-advanced-device-status-from-opc-driver-tags-in-ignition/102689/6 "2025-02-21T14:50:50Z")
> [@pturmel](#): > > class/instance/attribute codes There's a PlantPAx AOI that is intended to monitor changes on a remote controller. > The Logix Change Detector (raP\_Dvc\_LgxChangeDet) > Add-On Instruction monitors another Logix controller on > the network and checks for changes that impact > operation. Changes that can be monitored include > downloads, online edits, I/O forcing, and controller mode > changes. [https://literature.rockwellautomation.com/idc/groups/literature/documents/rm/proces-rm200\_-en-p.pdf#page=15](https://literature.rockwellautomation.com/idc/groups/literature/documents/rm/proces-rm200_-en-p.pdf#page=15) I've never used that, and probably never will. Though, might be straightforward to check out the details of messages therein. ---
**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:** [February 21, 2025, 3:45pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-understanding-advanced-device-status-from-opc-driver-tags-in-ignition/102689/7 "2025-02-21T15:45:24Z")
It would have to be a PlantPax v4 instruction, unsealed, for me to study it. PlantPax v5 uses instructions built into 5380 and 5580 firmware. (Those instructions have non-readable members, too, so are utterly impossible to use with busy comms.) ---
**Author:** ![dhananjay\_vichare](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dhananjay_vichare/32/74712_2.png) [@dhananjay\_vichare](https://forum.inductiveautomation.com/u/dhananjay_vichare)\ **Post date:** [February 24, 2025, 1:03pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-understanding-advanced-device-status-from-opc-driver-tags-in-ignition/102689/8 "2025-02-24T13:03:02Z")
Hello All, Thank you for the detailed information.