# Logix Driver - Detect Edits in the PLC **URL:** \ **Category:** Ignition\ **Created:** [November 12, 2020, 8:47pm UTC](https://forum.inductiveautomation.com/t/logix-driver-detect-edits-in-the-plc/40601 "2020-11-12T20:47:40Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![GreggCavazos](https://avatars.discourse-cdn.com/v4/letter/g/90db22/32.png) [@GreggCavazos](https://forum.inductiveautomation.com/u/GreggCavazos)\ **Post date:** [November 12, 2020, 8:47pm UTC](https://forum.inductiveautomation.com/t/logix-driver-detect-edits-in-the-plc/40601/1 "2020-11-12T20:47:40Z")
I noticed when someone performs a change in the PLC we get a notification in the logs. Is there a way to read that "version" and push it to a tag? > CompactLogixDriver 12Nov2020 14:43:11 [@@@@] Updating tagManager with edit version 23040 with 918 tags ---
**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:** [November 12, 2020, 8:53pm UTC](https://forum.inductiveautomation.com/t/logix-driver-detect-edits-in-the-plc/40601/2 "2020-11-12T20:53:47Z")
Pretty sure this is already available in the diagnostics at `[Diagnostics]/Device/EditNumber`. Only for the legacy ControlLogix/CompactLogix drivers. ---
**Author:** ![GreggCavazos](https://avatars.discourse-cdn.com/v4/letter/g/90db22/32.png) [@GreggCavazos](https://forum.inductiveautomation.com/u/GreggCavazos)\ **Post date:** [November 12, 2020, 8:59pm UTC](https://forum.inductiveautomation.com/t/logix-driver-detect-edits-in-the-plc/40601/3 "2020-11-12T20:59:25Z")
You are right, I missed that > [@Kevin.Herron](#): > > Only for the legacy ControlLogix/CompactLogix drivers. Is there a way to get it for the non-Legacy ones? ---
**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:** [November 12, 2020, 9:05pm UTC](https://forum.inductiveautomation.com/t/logix-driver-detect-edits-in-the-plc/40601/4 "2020-11-12T21:05:23Z")
> [@GreggCavazos](#): > > Is there a way to get it for the non-Legacy ones? No, the newer driver reads 5 un-named attributes as specified by 1756-pm020 to determine if a re-browse is necessary but does not assign any meaning to them or expose them because their definition is not documented. ---
**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:** [November 12, 2020, 9:47pm UTC](https://forum.inductiveautomation.com/t/logix-driver-detect-edits-in-the-plc/40601/5 "2020-11-12T21:47:41Z")
I’ve studied (experimented) and can share what I determined: The unnamed attributes of class 0xAC that signal a change are 1-4 & 10. Attribute #1 is a 16-bit tag edit count. In my testing, it starts over at zero after a program download. Attribute #2 is also 16-bit, but I never saw its value be anything but 1. Attributes #3 and #4 are oddly-encoded timestamps of download finish and start (respectively). They are 32-bit unix epoch timestamps times 1024, yielding millisecond-ish precision but uncertain year. Attribute #10 is the ACD file creation timestamp encoded/truncated the same way. I also noted that Attribute #8 is another timestamp, updating with program edits, offline or online, fwiw. ---
**Author:** ![dan.venema](https://avatars.discourse-cdn.com/v4/letter/d/ce7236/32.png) [@dan.venema](https://forum.inductiveautomation.com/u/dan.venema)\ **Post date:** [November 18, 2020, 8:44pm UTC](https://forum.inductiveautomation.com/t/logix-driver-detect-edits-in-the-plc/40601/6 "2020-11-18T20:44:18Z")
I you’re able to make changes to the PLC, you could use a GSV instruction to read [the audit value attribute of the controller object](https://literature.rockwellautomation.com/idc/groups/literature/documents/rm/1756-rm003_-en-p.pdf#%5B%7B%22num%22%3A738%2C%22gen%22%3A0%7D%2C%7B%22name%22%3A%22XYZ%22%7D%2C45%2C745%2C0%5D) into a PLC tag, then read that with ignition. ---
**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:** [August 4, 2022, 11:15pm UTC](https://forum.inductiveautomation.com/t/logix-driver-detect-edits-in-the-plc/40601/7 "2022-08-04T23:15:46Z")
Dan, by any chance have you been able to make any sense out of the AuditValue information. That number increments whenever a change occurs as long as changes to detect are enabled. The number does not correspond to anything that I can find. ---
**Author:** ![dan.venema](https://avatars.discourse-cdn.com/v4/letter/d/ce7236/32.png) [@dan.venema](https://forum.inductiveautomation.com/u/dan.venema)\ **Post date:** [August 5, 2022, 2:29pm UTC](https://forum.inductiveautomation.com/t/logix-driver-detect-edits-in-the-plc/40601/8 "2022-08-05T14:29:18Z")
My understanding is that the audit value is some kind of hash code generated from the contents of the program. I don’t think there’s any way to determine the number of edits from the value itself. You would have to track the historical value of the tag and count the number of changes. If you’re looking for a counter that increments, you might be better off using the (undocumented) values @pturmel explained above.