Skip to main content
S
swolnisty4-Participant
4-Participant
April 10, 2024
Solved

Datalogger Logging Conditions Question

  • April 10, 2024
  • 1 reply
  • 4308 views

Hello, I think I need some help configuring some Datalogger Trigger settings. I have a set of tags that I wish to record during a specific operation where the frequency of the logged data should match whenever the value of a single monitor tag changes.

 

I set up a condition-based trigger where under the general settings I configured the start and stop logging conditions to reflect the specific operation during which I wish to record data, and this behaves as expected. Since I only care about logging data when the value of a single tag changes, under the Logging Conditions menu, I set the 'Log on Static Interval' field to No and 'Log on Data Change' field to Yes. I set the Monitor Item ID to the tag whose value I want to drive the data logging, set the Monitor Item Update Rate to 1000 milliseconds (I am fine with checking the monitor tag's value once a second), and make sure there is no deadband type (because I wish to log any value change).

 

And somehow, when I check my database table, I am seeing as many as 20 logged entries in row where none of the logged data other than timestamp have changed their values? Any advice would be greatly appreciated!

Best answer by SlidingDownhill

This might be easier. First one sets up the triggers and the second one uses them. Only logs one time per rising transition

SlidingDownhill_0-1712857835044.png

SlidingDownhill_1-1712857847011.png

 

 

1 reply

S
SlidingDownhill12-Amethyst
12-Amethyst
April 10, 2024

I might be off here but there can be a Start and a separate Stop trigger. Did you define a stop trigger? 

S
swolnisty4-ParticipantAuthor
4-Participant
April 10, 2024

I did define separate start and stop triggers. The datalogger DOES seem to respect these conditions, just not the 'Log on Data Change' condition.

 

Upon first glance, it didn't appear that my data was being logged at a regular interval, but when I started doing the math it actually appears that it is actually logging very consistently every 2.74 seconds.

S
SlidingDownhill12-Amethyst
12-Amethyst
April 11, 2024

What was the STOP criteria and is it being met immediately after the data changes and gets logged?

I know "Log on Data Change" should mean exactly that, but have you seen it work in the past? 

I'm just spit-balling but I thought I remembered some sort of complication around that setting. 

Terms & ConditionsCookie settingsAccessibility statement