RTC Component¶
As already explained in the design document, RTC Components are software applications that adhere to specific communication, computation and composition principles defined in the RTC Tk Component Model.
The RTC Tk component infrastructure provides libraries that support the simple creation of such RTC Components.
Supported Functionality¶
Currently the following functionality is supported for each RTC Component out of the box:
Functionality |
Description |
|---|---|
Component Identity |
Component instance name and component version |
Component Life-Cycle |
Runnable State Machine and interface towards business logic |
Command Reception |
SVIF and FCIF commands are received via CII MAL Req/Rep |
State Publication |
State updates are written to OLDB and published via CII MAL Pub/Sub |
Logging |
Logging is initialised, configured and a default logger is created |
Runtime Repository Access |
Service Adapter to access the Runtime Configuration Repository |
OLDB Access |
Service Adapter to access the Online Database |
Service Discovery |
Service Adapter to access the Service Registry |
API Usage¶
Tutorial Creating a Simple RTC Component explains how to make use of the provided libraries in order to create a simple RTC Component application that runs a user-provided business logic.
Limitations and Known Issues¶
More advanced functionality such as alternative component life-cycles (e.g. Loop State Machine), user-specific commands and life-cycles, or event interfaces with subscription functionality are not supported yet. Such features will be added in a subsequent release.
Other functionality such as the support of user-defined command line arguments was omitted on purpose to disencourage its use for now. This will be revisited later when the CII Config Service is available and some experience is gained how it can be best integrated.