Genlink-DCP: Local Trending Setup

(See your user notes for this page.)
 Local trending means that a selected set of data is logged in the controller's memory ("local" to the controller) at predefined regular intervals for later viewing. Genlink is the mechanism to view the data and to set up the trending parameters. There is a physical limit to the amount of data that can be stored locally and this depends upon how many variables are being trended. Local trending limits this to six variables. You must decide whether you want local or remote trending depending upon the speed of sampling versus the amount of data you want to store. As a rule, the fastest local trending interval is 0.2ms - 4ms as opposed to Remote Trending which will be around 100ms. The maximum amount of data you can store locally is limited to 1000 readings.

  1. Buffer Size
  2. Trending Interval
  3. Triggering
  4. Stopping

Buffer Size

1000 readings equates to:

Interval Parameters Buffer Capacity
0.1 sec. 1 100 sec.
0.1 sec. 6 16.6 sec.
1 hour 1 40 days
1 hour 6 7 days

Trending Interval

To set up local trending, first select "local" from the form and enter a trending interval in floating point format (i.e. 0.1 = 100ms, 0.01 = 10ms, 1 = 1 second, etc.). Next use the "Active when" window to determine if trending should take place only if the engine is running, not running, or all the time. Now you need to set up the trigger conditions to determine when to start trending.

Triggering

Select a channel to use to trigger the trending. Select N/A if you just want to collect data with no conditions. Once you have selected a channel, its reading will be compared to that channels event setpoint using the event comparison type. The trigger condition will then either be set true or false. For example, if you select channel 1 to be the trigger, set the setpoint to be 100 and the condition to be greater than (GT), then once the reading is > 100 the trigger is deemed true. This trigger state is then used to start the trending. The check box "Capture only when trigger is true" will only take samples when the trigger is true, starting the first time it becomes true, for the medium and low-speed trending. The pre-trigger and post-trigger options define whether we capture data before or after the trigger becomes true.

No Trigger

Pre-Trigger
starts the capture immediately and stops when the trigger becomes true (in this case "Capture only when trigger is true" does not apply).

Post-Trigger
starts the capture after the trigger becomes true.

Pre- and Post-Trigger
starts capturing data immediately, rolling through the buffer until the trigger condition is true, after which data continues to be captured for half the buffer capacity. This results in a capture with the trigger-point in the middle of the data.

Stopping

Stop at End of Buffer
stops the data capture once the buffer is full, if this is not checked the buffer is used in circular fashion with the oldest data being overwritten. This only applies to the low-speed option.


(See your user notes for this page.)

GenLink-DCP Main Help Page