UAVTalk... at the bottom
Posted: Thu Mar 11, 2010 2:35 pm
Hi All,
After hearing about Tom's work on DIYDrones I have been searching for an area were I could bring something to the Gluonpilot project/community. I guess the Ground Station is the obvious choice for a few reasons, the main reason being the fact that I have knowledge of C# which is common ground with Tom GS I think.
So I decided to kick start this by writing some ideas and doing some research, having Tom's common ground station vision as my primary objective.
It is no easy task, and I am not expecting my work to be adopted by the this project or any other just because I am writing this. I am starting this for myself and if the work has quality to be used/adopted by people then I would be happy with that. But if anyone wants to be part of it I will be very happy to work with you.
I think the best way do achieve this has to be by adopting protocols created by others, that way creating common ground and making it easier for other projects to be brought in as well. Whit that in mind I have been looking around and I think UAVTalk designed by the fine people at OpenPilot.org. I think it is very good and it can easily fit every ones propose. It is, in my opinion, a packaging protocol for UAV. It does only define the way messages are sent and read. The actual messages are not specified which allows us to use and expand this the way we want. I think it will be used by a lot of other projects.
So UAVTalk will be on my communication layer. For the presentation layer I am thinking on using WPF, I am not very familiarized with it but I think this good moment to start learning.
And what about the features... well I am hoping you guys can help me with that. I have published some of my ideas on another post... so here they are again!
Health & Usage Data
Mission
Software Architecture
Any thought on this list, It is a bit short, I know.
Regards,
P.Assuncao
After hearing about Tom's work on DIYDrones I have been searching for an area were I could bring something to the Gluonpilot project/community. I guess the Ground Station is the obvious choice for a few reasons, the main reason being the fact that I have knowledge of C# which is common ground with Tom GS I think.
So I decided to kick start this by writing some ideas and doing some research, having Tom's common ground station vision as my primary objective.
It is no easy task, and I am not expecting my work to be adopted by the this project or any other just because I am writing this. I am starting this for myself and if the work has quality to be used/adopted by people then I would be happy with that. But if anyone wants to be part of it I will be very happy to work with you.
I think the best way do achieve this has to be by adopting protocols created by others, that way creating common ground and making it easier for other projects to be brought in as well. Whit that in mind I have been looking around and I think UAVTalk designed by the fine people at OpenPilot.org. I think it is very good and it can easily fit every ones propose. It is, in my opinion, a packaging protocol for UAV. It does only define the way messages are sent and read. The actual messages are not specified which allows us to use and expand this the way we want. I think it will be used by a lot of other projects.
So UAVTalk will be on my communication layer. For the presentation layer I am thinking on using WPF, I am not very familiarized with it but I think this good moment to start learning.
And what about the features... well I am hoping you guys can help me with that. I have published some of my ideas on another post... so here they are again!
Health & Usage Data
- AHRS Sensor Raw & Filtered Data
- Battery Voltage readings
- Temperature Sensors readings
- Servos positions
Mission
- Total Flight Time
- List Waypoints
- Next waypoint and previous waypoint
- Current position
- Add new WayPoint
- Set next waypoint
- Delete waypoint
- Abort mission/Return Home
Software Architecture
- Modular Design, including the UI
- UAVTalk
Any thought on this list, It is a bit short, I know.
Regards,
P.Assuncao