Event job – settings

General settings

Note
	"Starting" does not mean that the tasks configured in the job are executed immediately, but that the job waits for the trigger to start the execution.

Retry failed operations every ... minutes

Set the time after which tasks marked as failed will be retried.

Retry failed operations maximum ... times

Here you can define how many times the attempt will be made to reprocess time periods.

If you disable this option and the Retry failed operations every ... minutes option is enabled, ibaDatCoordinator will not stop trying to process the data marked as failed.

Trigger selection

ibaHD-Server

To open the server selection dialog, click the <Select server...> button. Select the desired ibaHD-Server from the table and close the dialog by clicking <OK>.

If user management is enabled for the selected ibaHD-Server, you must then enter a user name and the correct password.

For more information on the ibaHD-Server connection and user management, see Establishing ibaHD-Server connection.

Once the connection to the ibaHD-Server has been established, you will see the event-based HD stores and the available events under Event selection. Select at least one event for the configuration to be valid. The job is executed each time a selected event occurs.

Process historical unprocessed events

When enabled, all unprocessed events that occur after the defined start time (From) or within the defined time range From/To.

To reset the saved time range, click the button . Processing begins at the configured start time when the job is restarted.

Processed data settings

Here you specify the source for data processing, i.e., the HD store with the desired data, response behavior, and time range.

Time range

Here, you can specify exactly when the job should be executed for an event. Choose from the following options:

Option	Description
Relative to incoming event	The job is executed at the "start" of a selected event (e.g., rising edge).
Relative to outgoing event	The job is executed at the "end" of a selected event (e.g., falling edge).
Range between incoming and outgoing event	This option only makes sense if the job is to generate HDQ files. In this case, the HDQ files also contain the time range between incoming and outgoing events.
Range between successive incoming events	The job runs from the “start” of one event until the “start” of the next event.

Similar to conditional HD queries in ibaAnalyzer, you can also set pre-trigger times and post-trigger times here. The times are relative to the monitored event moments.

Enable pre-trigger range

Select this option if you want to query a period of time before an event. You can set the length of the period directly below. When the job is executed, the data from the period up to the specified event (incoming or outgoing) is then queried.

Enable post-trigger range

Select this option if you want to query a period of time after an event. You can set the length of the period directly below. When the job is executed, the data from the period starting from the specified event (incoming or outgoing) is queried.

Maximum time range

The setting for this time range is only available if you have selected the trigger option Range between incoming and outgoing events or Range between successive incoming events.

The maximum time range serves as a limit in the event that an incoming event has occurred but the outgoing or subsequent incoming event has not occurred before the maximum duration has expired. Note that the maximum time range includes the pre-trigger time and post-trigger time.

Preferred time base

Similar to HD queries with ibaAnalyzer, you can select a preferred time base. Depending on the setting of the time ranges and the number of samples contained therein for the HD query, the range of time bases changes.

If you do not need a specific time base for the query results, use the default setting "auto". This ensures that the query delivers the highest possible resolution, which can be particularly important for subsequent calculations.

HD store selection

Select the HD stores from which data is to be retrieved. If available, you can select multiple stores.

For testing purposes, you can generate an HDQ file by clicking on the <Generate test file> button. In order for such a file to be created, any occurrence of one of the specified events is taken, or, if no event occurrence is found, the current time.

Once you have completed these settings, you can add the desired tasks to the job. The tasks then process the measurement data contained in the HDQ file.