Table of Contents
Advertisement
ETAS
9.1.4
Operations of type "Bitmask"
What
Bitmask double((long(rint(sig-
9.1.5
Operations of type "Limit Monitoring"
MDA V7 allows to define calculated signals which monitor if one or more sig-
nals exceed a predefined value. For each limit to monitor, a condition is
defined, together with a message to be shown if the limit is not met.
For MDA V8 such an operation is migrated into a calculated signal of type
Boolean. The associated message will not be migrated.
Example:
The XDA file for a signal contains three calculation rules:
1
MyLimitMonitor1?1 = ${'C:_Data\INCA-NG_Sample Files\
Coldstart2.dat:DG0:CG0:N10'}>1000
2
MyLimitMonitor1?2 = ${'C:_Data\INCA-NG_Sample Files\Cold-
start2.dat:DG0:CG0:N10'}<100
3
MyLimitMonitor = ${'MyLimitMonitor1?1'} + ${'MyLimitMonitor1?2'}
These formulas are converted into one calculated signal in MDA V8:
Name
Formula (N10 > 1000) || (N10 < 100)
Type
MDA V8.6 – User Guide
MDA V7
nal)) >> shift_value) &
and_value)
MyLimitMonitor
Booelan
Migrated for-
Comment
mula in
MDA V8
If a measure sig-
All measure signal argu-
nal is used:
ments are wrapped by the
Raw function.
Raw(signal) >>
shift_value &
and_value
If a value is
used:
value >> shift_
value & and_
value
9 Appendix
135
Advertisement
Table of Contents
