@@ -130,15 +130,15 @@ The roadmap can be the following one:
...
@@ -130,15 +130,15 @@ The roadmap can be the following one:
## IPC/RT
## IPC/RT
### Introduce ZeroMQ support
### Introduce MavLink support
MBDyn offers several possibilities to communicate with external processes: UNIX sockets, RTAI mailboxes or standard TCP/UDP sockets can be used to exchange data.
MBDyn offers several possibilities to communicate with external processes: UNIX sockets, RTAI mailboxes or standard TCP/UDP sockets can be used to exchange data.
The purpose of this project is to add the support to [ZeroMQ](https://zeromq.org), an universal messaging library supporting the creation of high-level network structures and patterns.
The purpose of this project is to add the support to the [MAVLink](https://https://mavlink.io/en/), a lightweight messaging protocol born for communicating with drones.
The desired output is the implementation of a new `zeromq``socket type` for the `Stream``File Driver` and the `Stream Output`, which can allow to set up the desired pattern for the inboard or outboard data flow (Request/Reply, Pub/Sub, Pipeline, etc...)
The desired output is a module similar to [module-flightgear](https://public.gitlab.polimi.it/DAER/mbdyn/-/tree/develop/modules/module-flightgear?ref_type=heads), in which a new mode of operation of the file drivers of type `stream` and of the output elements of type `stream` is defined, allowing the user to select which MBDyn signal put into which MAVLink fields.
Depending on the amount of flexibility/implemented features, this project can be scoped at **175 hours** or **350 hours**.
Depending on the amount of flexibility/implemented features, this project can be scoped at **90 hours** or **175 hours**.