ETAS MDA V8 - Appendix; Import Calculated Signals from XDA Files: Differences between MDA V7 and MDA V8

10 Appendix | 131
10 Appendix
10.1 Import Calculated Signals from XDA Files:Differences
between MDA V7 and MDA V8
Since MDA V8.3.3 it is possible to import calculated signals from XDA files.
Because of several reasons, the results of the calculated signals in MDA V8 may
be different to the ones in MDA V7. This document lists the differences in detail.
MDA V7 and MDA V8 use different calculation engines for evaluating for-
mulas: MDA V7 uses a Perl interpreter, while MDA V8 uses a C-like cal-
culation engine. This may lead to different results (e.g. due to resolution).
Internally MDA V8 uses different data types (e.g. int8, uint8, int16, boolean,
double…) automatically, based on the calculation result (type deduction).
For calculated signals, MDA V8 supports the types Boolean, Double and
Automatic. MDA V7 in addition supports different integer types (uint16,
sint32 …). During the import, the mode Automatic is applied for all Integer
types. If you have selected an integer type in MDA V7 to ensure an integer
result, MDA 8 may deliver float values.
MDA V7 uses the decimal() function automatically for binary operations
(e.g. in the function Binary_AND). MDA V8 will emulate this behavior by call-
ing the Raw() function. If you use a calculated signal, MDA V8 does not do
this and will use the physical value instead.
When using the modulo (%) operator, MDA V7 uses the decimal value. MDA
V8 uses the physical value.
User-defined Perl scripts, which define new functions for calculated sig-
nals, are not supported. Calculated signals, which use such functions, are
imported, but their formula shows an error.
If you reference a signal in the raster settings, which is not part of the cur-
rent formula, MDA V8 uses “Combined Rasters (Merge Rasters)”.
Verbal conversion settings are not supported by MDA V8 and are ignored.
Signals of type "Limit monitoring" are imported. However, the verbal con-
version settings (and the associated messages) are ignored. The resulting
signal type is set to Boolean (not string) in MDA V8. The signals are deleted
from the oscilloscopes during the import. Please assign the calculated sig-
nal manually to a Boolean strip in an oscilloscope. You can also assign it to
an Event List instrument. This will give a similar view than the event strip in
MDA V7.
The functions TableMap1 and TableMap2 are not supported and show
errors in MDA V8.
MDA V8 | User Guide