![]() |
|
| ||||||||
|
| ||||||||
|
| ||||||||
| ||||||||
| Quick Help
Select an object to be tracked, then select other unassigned objects as the destination for the results. Select when or how often the tracking should be reset. The "When logged" selection for reset means when logged to any file. Therefore, trend values should only be logged to a single file if "When logged" is selected for reset. All result values for a given tracked object are reset upon logging of any one of the result values if "When logged" is selected for reset. However, all of the resets will wait until the entire log record has been compiled for the given log cycle so that no partial results are logged. The data logging that results in the "When logged" reset is defined on the Advanced->Data Logger->Data Pointspage. The trend data is updated periodically at the period given. This period is subdivided into the number of slices given. A sliding window average of this number of slices is maintained, and this filtered value is processed as the trend data. Thus the minimum data value will be the lowest average of N slices over any given Period of time, and the maximum data value will be the highest average of N slices over any given Period of time. The Flash check box indicates where you would like the data to be stored which is used to generate the trend graph when the "Graph" link is clicked on the System->Data->Trend Datapage. This sliding window records the last 250 points logged at the rate specified by Period on this page. If you are logging data slowly over a long time period, you may prefer Flash to avoid losing data in a power outage. If you are logging data over a shorter period, it is preferable to use RAM (do not check Flash) because Flash has a finite life measured in write cycles. If you were to log to Flash at a frequent rate, you may shorten the life of the product. | ||||||||