With Event Logging, the input signal is monitored continuously and data is stored when the input changes significantly or when an interval amount of time has passed.
You must wade through the normal data to find the exceptional data (or lack thereof) that you are interested in seeing. You can also end up with a lot of redundant data that is considered "normal" and not of interest. This often means that it is desirable to sample the signal as fast as possible so you "don t miss anything." The problem with this approach is you need a large storage place for the fast data sampling that is taking place. Typically, the goal of a data logger is to sample an input signal at a rate sufficient enough to be able to track something of interest that you expect to be contained within the signal. Differences between Event Logging and Data Logger Event logging attempts to reduce the amount of stored data to only that which is necessary to capture the normal and/or abnormal behavior of the signal.
#Flukeview forms windows 10 Pc
This can be done for a number of different meters (including the 89-IV and 189), and the event capture being done by the PC (with the option of having it performed on the 189/89-IV meters as well.) This technical note explains the enhancements to the event logging functionality incorporated into FlukeView Forms interactive logging, beginning with version 1.5 of FlukeView Forms. Beginning with FlukeView Forms version 1.5, can now interactively log events directly from a meter to the PC, in real time, with the meter connected to the PC during the logging session. This approach monitors the signal and records the highest, lowest, and average values and the start and end times of the period over which the values are essentially the same. 1 FlukeView Forms Technical Note Fluke developed an Event Logging function allowing the Fluke 89-IV and the Fluke 189 models to profile the behavior of a signal over time without requiring a great deal of memory to record redundant data.