
7
Areas for defined cut-off behavior
8
Remove field set from a monitoring case
In the monitoring case editor, you can also define the monitoring cases with input
conditions and assign the field sets.
Further topics
•
7.10.1
Settings for monitoring case tables
Name
In the
Name
field, enter a name for the monitoring case table that is as descriptive as
possible.
Inputs used
If you want to use static control inputs for monitoring case switching, then select the
inputs here.
In antivalent evaluation, the 2 channels of each static control input must always be
inverted, even if the status of a control input in a monitoring case is random. If it is not
inverted, all safety outputs switch to the OFF state and the device displays a fault.
Input delay
If you use static control inputs for monitoring case switching, you can select a delay for
the inputs.
If your control device, which you use to switch the static control inputs, cannot switch
to the appropriate input condition within 12 ms (for example because of the switch’s
bounce times), you must configure an input delay. For the input delay, select a time
in which your control device can switch in a defined way to a corresponding input
condition. You can increase the delay time incrementally.
The following empirical values exist for the switching time using various methods:
Table 14: Empirical values for the required input delay
Switching method
Required input delay
Electronic switching via control, complementary electronic outputs
with 0 ms to 12 ms bounce time
12 ms
Tactile controls (relays)
30 ms to 150 ms
Control via independent sensors
130 ms to 480 ms
Also, take account of the notes relating to when to switch between monitoring cases
(
see "Monitoring case switching time", page 34
).
Further topics
•
"Static control inputs", page 52
7.10.2
Settings for monitoring cases
Name
Enter a name which is as descriptive as possible for the monitoring case in the
Name
field. If you create a lot of monitoring cases, you should consider a naming concept that
makes it possible to identify the monitoring cases easily (for example right cornering,
left cornering).
CONFIGURATION
7
8023152/1G5N/2022-06-28 | SICK
O P E R A T I N G I N S T R U C T I O N S | outdoorScan3 Core I/O
99
Subject to change without notice