Allen-Bradley Logix Driver - Understanding Advanced Device Status from OPC Driver Tags in Ignition

[dhananjay_vichare]

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.

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?

[Kevin.Herron]

Logix Device Status

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

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…

[Chris_Bingham]

@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.

[Chris_Bingham]

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

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.

[pturmel]

@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.

[Chris_Bingham]

@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

I've never used that, and probably never will. Though, might be straightforward to check out the details of messages therein.

[pturmel]

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.)

[dhananjay_vichare]

Hello All,

Thank you for the detailed information.