Selecting "Setting" enters the sub-environment in
which it is possible to specify various critical configurations for the
activities in "Run".
In this image you can see the
area in which you decide how to open the various windows at the entrance to
In this image we can see the area in which you can decide the possible automatisms to trigger at the entrance in "Run":
In this image we can see the area
where to set the channels necessary for the integrated management of a brake
("B") and of an actuator/accelerator ("A") typically into
an engine test bench.
In this image we see the area
where to combine Actions ("GEN") to "DI" ("Digital
Input") input channels, typically to trigger Actions when a hardware
button is pressed in a completely analogous way to what has already been said
for the software buttons available in Native Desktop (and therefore with the
same absolute priority).
In this image we can see the area where to define the configuration of Alarms to be automatically activated at the entry in "Run", having a possible delay (to manage "settlements" of the channels being acquired).
In "Run" it’s also
possible to load other configurations of Alarms that will always be added to
the one defined here, meaning that they will eventually update the thresholds,
possibly increasing but never decreasing the list of logical channels to be