A Custom Implementation of the ByteStream Driver Model to support a Network of Deployments #1469
Replies: 2 comments 9 replies
-
I haven't run it yet but it looks amazing! As far as managing the configuration of your project, you could use fprime as a sub-module as shown in separated-project-example. This would make it easier to see which components you had to create specifically for your mission. And you could more easily manage your dependency on fprime by simply updating the hash of the submodule. |
Beta Was this translation helpful? Give feedback.
-
Update! New Repository: https://github.com/Emil808/fprime-Mesh_Network I separated the deployment and new driver files, with fprime as a sub-module. Should work with ver. 3.0.0 |
Beta Was this translation helpful? Give feedback.
-
I have been working on an implementation for the ByteStream Driver Model to support a Network of Deployments. I built some classes inheriting the TCP Server and TCP Client classes that were present, and based heavily on the operations of the Drv/Ip files.
https://github.com/Emil808/fprime/blob/multi_tcp/DepA/MultiNode.md
The goal was to allow communication between identical Deployments/Space Vehicles, working together as a swarm. For the example I present here, each Deployment has their own GPS position (in ECEF), and is sending it out to the other nodes. When receiving another Node's GPS position, the receiving Node will calculate the distance between itself and the other Node.
Suggestions, and criticism would be appreciated to help me get better at this. Thank you!
Beta Was this translation helpful? Give feedback.
All reactions