A SysML model can describe a DDS interface. This plugin for CATIA Magic lets it take part in one: a simulation can publish and subscribe to real RTI Connext DDS traffic, so a service that exists only as a model can exchange data with services that already exist as code.
The video (linked below) shows the setup and a live demo.
What it's for
- Checking interfaces before implementation. A supplier's code runs against the model's live behavior instead of a document describing it.
- Mixed systems. Modeled and implemented services share one bus while the rest of the system is still being built.
- One source for the interface. The DDS XML is generated from the model, so the model and the wire configuration can't drift apart.
Design choices
- A signal in the model is a DDS topic, marked with a stereotype. Its payload block defines the data type.
- Ports with flow direction declare who publishes and who subscribes, so the configuration comes from the model's structure.
- The plugin uses supported extension points where they exist. Where they don't, the dependency on an internal API is isolated in one class, so a CATIA Magic update only has to touch that.
Limits today
- Incoming data is injected into the simulation in arrival order. It isn't re-paced by the timestamps inside the data.
- This is a first iteration, proven on one example system.
Video: https://www.youtube.com/watch?v=deBfPiIk2tU&t=215s
Source and README: https://gitlab.com/notesandnotches-group/rticonnextdds-cameo-integration
Any sort of feedback will help me improve this further.
0
