Innovate Motorsports LogWorks 3 - Manual (Page 52)

LogWorks3_Manual_1.01.doc - 52 -
Trigger Start Condition Setup
In the Log Trigger Start field you enter the session start condition. In the above example the
session starts when the Throttle channel indicates more than 50% and RPMs are greater than
3000. Use parenthesis () liberally to indicate conditions.
DO NOT ENTER THE UNITS in the condition equations.
For example DO NOT enter: Throttle > 50%. LogWorks knows the units already from the channel
name (Throttle in this case) and does not need to be told.
The persist field allows you to specify a length of time for the condition to persist before the
recording is started. This allows eliminating false starts due to for example spikes or glitches.
The Pre-Record field allows you to set a time that LogWorks records before the start condition
happened. If set to 60 seconds for example, LogWorks will include in the session the last 60
seconds before the start condition happened. Pre-Record times of up to 300 seconds can be
programmed. If a persist time is used, the persist time is included in the pre-record time.
Trigger Stop Condition Setup
Once a recording session has started, it will only stop if the following things happen:
a. The user stops recording with the stop button in the Log Window
b. A stop recording condition has been specified and the condition happened.
In the Log Trigger Stop field you can specify a stop condition. This is done exactly the same way
as for a start condition, including the capability to program a persistence time to avoid stopping a
log on short glitches and spikes.