Campbell Scientific LoggerNet Datalogger Support Software - Manual (Page 394)

Section 9. Automating Tasks with Task Master
• After Any Scheduled Call – After a scheduled data collection attempt,
regardless of whether or not the call is successful. The task is triggered
only by a scheduled collection.
• After Successful Call – After a successful scheduled data collection, after
using a Collect Now button successfully, after a call-back, or after another
task that calls the associated station successfully.
• After Failed Scheduled Call – After a scheduled data collection fails,
after using a Collect Now button unsuccessfully, or by another task that
calls the associated station unsuccessfully.
• After Any Call – After a scheduled collection, after using a Collect Now
button, after a call-back, or after another task that calls the associated
station. The task is triggered regardless of whether or not the data
collection was successful
• After Some, Not All, Data – After some, but not all data is collected
during a scheduled collection, when using a Collect Now button, or when
another task calls the associated station.
• On Call-Back – When a call-back attempt is detected. This option does
not wait for data collection to finish. The task is triggered by a call-back
from a datalogger executing a P97 instruction or a SendVariable
instruction.
• After Call-Back – When a call-back attempt is completed and data is
collected. Even if data collection fails part way through the call, the task
will be run. The task is triggered by a call-back from a datalogger
executing a P97 instruction or a SendVariable instruction.
• After Failed Retry – Whenever a retry fails. This can be the failure of a
primary retry, a secondary retry, or a retry using a Collect Now button.
(Scheduled collection failures and “Collect Now” failures both increment
the same retry counter.)
• After Primary Retries Failed – After the specified number of primary
retries has been exhausted. The task is triggered by a failure of primary
retries from scheduled collection or from using a Collect Now button.
(Scheduled collection failures and “Collect Now” failures both increment
the same retry counter.)
• After One Way Data – After data is received from a datalogger executing
a SendData instruction or when data is collected via Data Advise.
• After File Closed – After any data file being written to is closed. The task
is triggered by a scheduled collection or by using a Collect Now button. A
datalogger call-back, One Way Data, Data Advise, or another task that
calls the associated station, which causes a file to be written to and closed,
will also trigger the task.
The option %F can be used in the command line options to represent the
just closed data file. This condition is especially useful when performing
post-processing on a data file that has been created using Create Unique
File Name as the File Output Option. In this case the user does not know
9-4