State, Event and Pulse Recorders, although similar, each serve very different purposes in meeting the needs of a specific application.
This application note will discuss the difference between the three different types of units and provide some insight into practical applications to help the user choose the right product for their application.
The State Recorder records a time-stamped value whenever the state of the signal changes over a period of time. This is useful when the user needs to be able to collect data on an event duration.
If the user is monitoring traffic through a door, the State Recorder would take a data point:
The State Recorder records the data points to indicate how long a door was open; that is, the data collected tells the user that a change in the state of the door occurred:
The user can then calculate that the door was open for a period of 5 seconds.
However, it should be noted that if the leading edge of a state change occurs between position 0 and position 1, it will be recorded as taking place at position 1.
The State Recorder samples the state of the input at fixed intervals. In order for a state change to be recorded, the change must be present at the time it is sampled. If more than one transition occurs between position 0 and position 1, only the state of the input at the time of the sample will be recorded. In short, the sample period must be set to less than the minimum time required for the input signal to rise and fall. If the change in state does not persist long enough to be active at the time of sampling, it will be missed.
If it takes 30 seconds for a garage door to open and close, the time period should be set to less than 30 seconds to ensure the state change is not missed.
Another example of an application for the State recorder is the monitoring of a furnace or pump turning on and off, both of which have a long enough state change to be captured by the State Recorder.
The Event Recorder records a single direction time-stamped data point when an event takes place within a fixed reading interval. This is useful when the user needs to be able to collect data on when an event occurred but does not need to know the duration of the event.
If the user is monitoring the traffic flow through a door, the Event Recorder will take a data point recording:
Unlike the State recorder, it does not provide the data points that would indicate how long the door was open. The Event Recorder can track the number of times the door was open but not how long the door was open.
Data from the Event Recorder tells the User event occurred:
Thus, the user can track the number of times the door was opened but not how long the door was open each time.
The Event Recorder has a resolution of one second. This means that the device has the ability to record an event every second. unlike the State Recorder, the Event Recorder does not require a persistent signal. The Event Recorder will trigger on the leading edge of the signal transition.
However, it should be noted that:
If a data point occurs between position 0 and position 1, it will be recorded as having taken place at position 1.
If more than one data point occurs between position 0 and position 1, only a single data point will be recorded.
Another common application for an Event Recorder is monitoring tipping-bucket rain gauges. The Event recorder will record data when the bucket tips and the contact is closed. It is unlikely that the bucket on the rain gauge will tip more than once per second, therefore the Event Recorder will not miss recording any data points.
Pulse data loggers record the number of pulses that happen over a period of time. Unlike the State or Event Recorder, the device does not time-stamp each pulse but rather groups together or bins the number of pulses according to the time period they occurred in.
If the user is monitoring traffic through a door, the Pulse Recorder will log the number of times the door was opened during each interval:
The Pulse Recorder does not record information about the duration that the door is open. The Pulse Recorder is most useful when you need the ability to collect rapid pulses that are too fast for the Event or State. It offers a more efficient way to collect information from a source which produces pulses at a constant rate. By binning the data without recording a time-stamp, the Pulse Recorder uses less memory than the Event or State.
Using the data collected in the above example, the user can calculate additional data such as:
The Pulse Recorder requires a signal of at least 1ms duration and at least 10ms between the leading edge of each pulse to be counted. If these conditions are met, then every pulse will be logged up to almost 4.3 million pulses per time interval.
Conversely, a pulse may not be recorded if it is less than 1ms or if more than one pulse occurs within a 10ms period. If the latter happens, further data points may not be recorded until 10ms after the first pulse.
A common application for the Pulse Recorder is to measure the flow rate or total volume of a pipeline. The Pulse Recorder collects pulses generated by a flow meter and uses that information to calculate the number of gallons per minute. The flow meter produces a pulse that is to rapid too be collected by the Event or State, yet can easily be binned by the Pulse Recorder. The important data here is not the exact time when the pulse took place, but rather the number of pulses in a time interval.
© 2022 Dalotech LLC