eive/fsfw
eive/fsfw
15
1
Fork 0
forked from fsfw/fsfw
Code Issues Pull Requests Releases 1 Wiki Activity

doc improved

Browse Source
This commit is contained in:
Robin Müller 2020-09-02 23:45:14 +02:00
parent 6069c64048
commit e8fa9816ce
1 changed files with 4 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
devicehandlers/DeviceHandlerBase.h
View File

@ -44,12 +44,10 @@ class StorageManagerIF;
* objects. It inherits SystemObject and thus can be created by the * objects. It inherits SystemObject and thus can be created by the
* ObjectManagerIF. * ObjectManagerIF.
* *
* This class uses the opcode of ExecutableObjectIF to perform a step-wise execution. * This class uses the opcode of ExecutableObjectIF to perform a
* For each step an RMAP action is selected and executed. * step-wise execution. For each step a different action is selected and
* If data has been received (GET_READ), the data will be interpreted. * executed. Currently, the device handler base performs a 4-step
* The action for each step can be defined by the child class but as most * execution related to 4 communication steps (based on RMAP).
* device handlers share a 4-call (sendRead-getRead-sendWrite-getWrite) structure,
* a default implementation is provided.
* NOTE: RMAP is a standard which is used for Flying Laptop. * NOTE: RMAP is a standard which is used for Flying Laptop.
* RMAP communication is not mandatory for projects implementing the FSFW. * RMAP communication is not mandatory for projects implementing the FSFW.
* However, the communication principles are similar to RMAP as there are * However, the communication principles are similar to RMAP as there are