Trigger
Use the trigger module to add diverse trigger functions to a scope configuration.
As to provide a simple way to configure multiple sets of single trigger conditions and and actions, these are combined to trigger groups. The upper toolbar in the trigger module can be used to add or remove trigger groups.
Trigger Groups
The trigger module holds different trigger groups in an own tab page. Each tab is separated in a condition area (on top) and an action area (bottom).
The condition area contains a toolbar to add or remove, and a table to configure single trigger sets.
Trigger-Set
Each row in the table contains a trigger set to define a single trigger condition. By selecting a combine option from the associated colum the sets are linked to a group relation. Please note that AND-relations are operated before OR-relations.
A name for the set can be selected as well as a channel to which the release condition should be connected. The celease condition contains the operation (in the Release column) and the assigned threshod. The release operation can be a rising or falling edge through the threshold (edit a number). If the condition happens the hit flag is marked in red color. All trigger sets will hold the released state until the whole group is raised.
Trigger-Action:
The action area in the trigger group defines what happens if a trigger group is raised:
- StartRecord: To use this option the scope settings should be configured to trigger start. Otherwise the record will be started as usual. When this action is selected a question box appears to set the option for you. Once the record button is hit, the scope will be connected to the involved servers and starts checking the trigger conditions without starting the record. The start time will be the release time of the last raised trigger set.
- StopRecord: To use this option the scope settings should be configured to ringbuffer mode. When this action is selected, a question box appears to set the option for you. Use the Pre- and/or Post-Trigger to define a timerange before and after the triggerevent.
- StopDisplay: This action stops all connected charts in case they're in live mode. Use the trigger position to change the position of the trigger event in the chart as a percentage of the display width (example below: raising-edge through zero of the green graph at 10% of 2.5s = 0.25s). If the trigger condition is hit again the display will jump to this new event. To avoid the retrigger use the break button in the charts toolbar.
- RestartDisplay: This trigger action restarts all charts paused by a "Stop-Display"-Trigger.
- StartSubsave: Once this trigger event is raised a background record is started, using the active configuration. This subsave allways run in Ringbuffer-Mode (even if not set in the baseconfigruation). Up to five parallel subsaves may run at the same time (triggered by one or more trigger-events). The recordlength of the subsave can be edited in the 'Record-Time'-box. It is possible to choose a larger time than using in the baseconfiguration (in this case the baseconfiguration should use the 'Ringbuffer-Mode' too).
- StopSubsave: This event stops the oldest subsave. The containing data will be send to the view and stored in a .svd-file. The storage path can be changed to each accessible location. The savefile-name is build from the name of the scope in the baseconfiguration and a date-time string in alphanumerical alignment.
