through consolidate() TDI call
on MDS+ server side

SCD DMmag control and tests

See merge request spc/tcv/scd/rtccode!13

Cristian Galperti authored 5 years ago and Federico Felici committed 5 years ago

digdens not yet ready

Tcv02standard mar te crosschecks

See merge request spc/tcv/scd/rtccode!10

now a single actualize call loads params, wavegens and ADCs
for expcode 1005, everything to simulate

F4e example

See merge request spc/tcv/scd/rtccode!9

At this stage we begun running tcv02standard in MARTe
in i9 (tcvrt02b) machine and to compare results
with the simulation

tcv02standard loads all the cfg of hybrid + IOH
+ stddiag from MDS+ in MARTe2.
IOH control setup time works and configured itself
correctly according to G2(17,1) matrices content.
This is a strong clue that the 3D G matrices
are loaded with the correct alignement.
All spurious tunable parameters are removed now,
so we can have a strict loading.
Tasks and wavegens still pending.

Corrected + improved MARTe2 config writer

See merge request spc/tcv/scd/rtccode!8

+ some cosmetics

Feature/server tree order

See merge request spc/tcv/scd/rtccode!7

Feature/server tree order

See merge request spc/tcv/scd/rtccode!6

With reusable function ERT target,
found the right code to expose the CAPI mmi data\
structure on the .so interface.
Number of parameters, root inputs and outputs
correctly read in MARTe2 from the generated .so
via CAPI

Standard Java based MDS+/Matlab interface tested
with the F4E example. Previously SPC mdsipmex based
interfaced was used, not suitable for a public
accessible example. NB: we do not know if
the Java interface is as optimized as the mdsipmex
one (i.e. if it uses a connection stack for example),
for for SPC usage we have to revert back to the
mdsipmex version or implement a connection
stack/ corrnection order in the SCDclass* objects.