Good_Overload results in excessive historian logging

Ignition
1

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

2

Two possibilities right off the top:

  • Make expression tags with forceQuality() to strip out the bad quality, and historize those instead.

  • Fix the overload on the drivers involved.

2 Likes
3

Ok, forceQuality() seems like a good solution. I will test this. Thanks Phill !