Download Software User Manual

SUM
iss: 6 rev: 3
NLR-EFO-SUM-2
entry point will be generated. Scheduling the parameter exchanges is described in Section 18.3.4. Use
the Parameter Exchange Editor to create or modify a Parameter Exchange file. There is no need to re-run
the build process in the Model Editor after creating or modifying a Parameter Exchange file, as the entry
points are generated “on the fly” when the simulator is started.
For our use case example a screen shot of the Parameter Exchange Editor looks like Figure 18.3. Each
time the parameter exchange entry point is scheduled, the value of output variable counter of ModelB
is copied to input variable x of ModelA and to the input variable counter of ModelB. The parameter
exchange entry point receives the same name as name the exchange group node. Thus, in our example
the entry point will be available as “Model B to model A”.
Figure 18.3: Parameter Exchange Editor
18.3.3.1
Why are Parameter Exchange files not part of the model?
This is done for flexibility. It allows the model developer to put together several sub-models into one
simulator executable and describe the model variables by means of one or more Model Description files.
The simulator developer could then create two Parameter Exchange files and reference these from two
Schedule files. The first variant of the Parameter Exchange may for example update the input variables
of one of the models with variables in the datapool that are updated by an external simulator (see Chapter 30). The second variant may update the input variables of one of the models with variables in the
datapool that are updated by an internal model. In that way the test controller can easily switch between
the two configurations, simply by selecting the appropriate Schedule file. The reason for having the
Parameter Exchange file(s) referenced by the Schedule file is that the entry points are generated “on the
fly” and you need the entry points when you edit the Schedule.
18.3.4
Specifying the schedule
As the last step when using Simulator Integration Support the schedule has to be specified. At this point
we should have:
• A successfully built simulator executable,
238
c Airbus Defence and Space