Now we have described how to control ADTF, but our main concern is to transfer data, synchronize time and work deterministically across computer boundaries.
For this purpose we developed ADTF components to embed the
FEP functionality in the ADTF Filter Graph. So that we can describe the boundaries of our ADTF Session and what signals and clocks can be used from outside.
FEP Sink and
FEP Source give access to the topics/signals from the simulation bus.
The smallest execution unit in
FEP is a
fep3::arya::IJobRegistry::IJob. A Job will be registered at the active scheduler and executed according to its scheduling mechanism.
If you want ADTF to behave as a deterministic component in the distributed system you need to replace your usually used ADTF Timer Runner with a
FEP Job Runner.
This guarantees that all ADTF Filters and other ADTF Components are executed in a synchronized way related to the other
FEP Participants of the
FEP System and therefore behave deterministically.
ADTF as a Framework provides several options and is extenable. The architecture is very common and provides a lot of possibilities but also seperations to fulfill these requirements.
The job of our toolset is to provide the user convenience and automization for that - of course also for using
FEP within ADTF.
You can use the context menu to launch an ADTF Session as
FEP Participant directly from the ADTF Configuration Editor in the two ways we described in the last guide:
We plan to expand the ADTF Configuration Editor so that it not only supports the creation of signals, but should also be able to display, configure and manage a entire
So stay tuned for a lot more improvements the upcoming ADTF releases!
FEP is integrated in the
All components based on the
adtf::remotesdk can now be addressed via
FEP System. For example you can use the ADTF Status Monitor with the url
Another tool could be the ADTF Logview.
Require more details ? The next will show you how deep the rabbit hole goes.