CPC 100 V1.41
3 - 12
Note:
Trigger conditions with "<" are meaningful in combination with
external signals only, that is, with signals that are not coming from
CPC 100
.
Reason: if the trigger signal comes from
CPC 100
,
the trigger
condition will always be "true" at the moment the I/O (test start/
stop) push-button is pressed.
After having pressed K
E E P
R
E S U L T S
, the trigger event is locked and
cannot be changed.
Data entry field for the threshold value.
Setting a threshold value is not possible ("n/a", as shown above), if
either
– a binary trigger condition
– no trigger
– overload
was selected.
After having pressed K
E E P
R
E S U L T S
, data entry for the threshold
value is disabled, that is, the value cannot be changed.
Bin.In:
Indicates the signal condition at the binary input
Bin In
. 4 different
characteristics are possible:
Closed
: potential-free contact between BinIn+ and BinIn–
closed.
Open
: potential-free contact between BinIn+ and BinIn–
open.
Come:
trigger signal with rising edge
occurred at BinIn.
Go:
trigger signal with falling edge
occurred at BinIn
Delay time display
The delay time is the time between the last change of the
CPC 100
output value and the occurrence of the trigger event.
2
3
4
Summary of Contents for CPC 100
Page 12: ...CPC 100 V1 41 x...
Page 28: ...CPC 100 V1 41 1 16...
Page 90: ...CPC 100 V1 41 3 14...
Page 194: ...CPC 100 V1 41 6 30...
Page 250: ...CPC 100 V1 41 8 32 Figure 24 Settings of Amplifier test card for this example use case...
Page 258: ...CPC 100 V1 41 9 4...
Page 264: ...CPC 100 V1 41 10 6...
Page 282: ...CPC 100 V1 41 12 10 Figure 9 Saving tests with the CPC Editor...
Page 284: ...CPC 100 V1 41 12 12...
Page 312: ...CPC 100 V1 41 14 12...
Page 316: ...CPC 100 V1 41 15 4...
Page 350: ...CPC 100 V1 41 16 34...
Page 372: ...OMICRON Contact Addresses 22...