# Tag Historian , Keep Duplicate values

**URL:** <https://forum.inductiveautomation.com/t/tag-historian-keep-duplicate-values/14774>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [July 12, 2017, 7:35pm UTC](https://forum.inductiveautomation.com/t/tag-historian-keep-duplicate-values/14774 "2017-07-12T19:35:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dtompkins](https://avatars.discourse-cdn.com/v4/letter/d/a6a055/32.png) [@dtompkins](https://forum.inductiveautomation.com/u/dtompkins)\
**Post date:** [July 12, 2017, 7:35pm UTC](https://forum.inductiveautomation.com/t/tag-historian-keep-duplicate-values/14774/1 "2017-07-12T19:35:25Z")

</div>

I am logging machine cycle times using the historian. I have the historian set up to log on change. However, I also need to collect successive duplicate values (e.g. 65,64, **67,67** ,66,67). Currently, the historian is filtering these out. Is there a way turn that feature off? I need the successive values to make my statistics work out. If I need to abandon the historian and use the Bridge then that’s ok.

---

<div class="post-metadata">

**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:** [July 12, 2017, 8:34pm UTC](https://forum.inductiveautomation.com/t/tag-historian-keep-duplicate-values/14774/2 "2017-07-12T20:34:48Z")

</div>

Well, logging “on change” when the value doesn’t change doesn’t make a lot of sense. (-:  
What you are after is to log “previous cycle duration” when the cycle is complete. The Bridge can do this – trigger on one item to record something else (or several somethings). Consider using a cycle odometer as your “on change” trigger in a Transaction Group.