I have an issue where my boolean tags are keep getting logged even while they have the same value. Massivly filling the database with unwanted data. what setting is recomend for a boolean to only log when it acualty changes value. this is what i have tried/used deadband style: discrete deadband …

Are the examples you show back-to-back, or were there points in between? I'm wondering if it's logging based on quality, bouncing between good/bad? Edit, geez... I completely missed your comment about quality, yes, quality will affect when a point is stored.

It is back to back directly from the database (only filterd on tagid). I expect its a quality thing (editted the post)

So its logging between good and good? is there a setting somwhere to nuke this beheviour?

Ok, this works for 99% of my tags that where expression tags already. now only to find a way to do the remaing tags that are are OPC tags. (without recreating them). It realy shoul have a tickbox "fuck off quality"

Inductive Automation Forum

Configure boolean tag history

Ignition

ignition81

jlandwerlen June 28, 2024, 12:32pm 5

Good_Overload results in excessive historian logging Ignition

Hi, We are experiencing troubles with a customer that has excessive historian logging. I suspect the main reason are some tags who flip to Good_Overload("Sampling has slowed down due to resource limitations.") Quality and then back to GOOD quality. I suspect this issues a historian change and makes the historian log this in our database. Strangly enough the log entry has status code 192. Is there a way to avoid this excessive logging? Thank you, Thijs Ignition Platform 8.1.12

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled