MARTe2 » MARTe2-core

Comments for commit 82271f198093d5ef5fc3bbe6a7e5d91784a03e99:

In the tutorial/environment/building.rst page, please:

• Remove the reference to the SDN (as it is only meaningful for environments with CCS)
  • By the way - SDN - is the ITER Synchronous Databus (real-time) Network - https://www.iter.org/doc/www/content/com/Lists/ITER%20Technical%20Reports/Attachments/15/ITR_20_009_Plant_Control_Design_Handbook_v1.pdf
  • Instead, for the demos, we can now use the portable UDPDataSource implementation (https://vcis-gitlab.f4e.europa.eu/aneto/MARTe2-components/-/tree/master/Source/Components/DataSources/UDP)
    • (The SDN is also based on UDP)
• Add a small description and a reference to the MDSplus page https://www.mdsplus.org/index.php/Introduction

Before the EPICS example, let's add and explain some (easier) examples:

• A MARTe application that reads from a LinuxTimer and prints the Counter and the Time to a LoggerDataSource at a fixed frequency of 2 Hz;
• A MARTe application that reads from a LinuxTimer, executes a WaveformSin and prints the value of the sine to a LoggerDataSource at a fixed frequency of 10 Hz;
• A MARTe application that reads from a LinuxTimer, executes a WaveformSin and stores the value of the sine to a FileDataSource;
• A MARTe application that reads from a LinuxTimer, reads the values from a file (using the FileDataSource), use the MathExpressionGAM to modify these values (e.g. by multiplying them by 2) and then stores the values to a FileDataSource;
• A MARTe application with two threads communicating between them using the RealTimeThreadSynchronisation DataSource.
  • The first RealTimeThread is driven by a LinuxTimer running at a frequency of 100 Hz;
  • The second RealTimeThread prints the value of the counter at a sub-frequency of 1 Hz (Samples = 100).
• A MARTe application - driven by a LinuxTimer at 10 Hz - that uses the HistogramGAM to compute statistics about the thread cycle time and outputs to the LoggerDataSource.
• A MARTe application with the same structure of the EPICS application (example 1), but without the EPICS::EPICSCAClient.