|
From: | Andy Brown |
Subject: | Re: [Paparazzi-devel] paparazzi user edition? |
Date: | Wed, 23 May 2012 07:32:56 -0700 |
As someone still getting their head around the entire system and tool chain (for the last several months actually) my observations are as follows: - it's quite hard to get things going on non-Linux systems and once you do it's difficult to get Linux and Mac based systems to talk (hard coded subnet issue)
- I don't care for ivy bus very much at all. It's quite brittle and only works on a single subnet. - storing all the config files within the main repository makes keeping things updated pretty difficult - id love to see most of the XML get its own repo and the reference with a git submodule.
- The config files are quite opaque and there is not much documentation that is useful for someone not familiar with flying or telemetry or gps - (I'm just a lowly iOS programmer and network engineer type :)
- fixed number of waypoints are a bummer and it's all pretty brittle. So what are you gunna do about it random guy from the internet you ask? Here is what I'm working on. Feedback welcome:
- tool chain is hard: I'm working on prebuilt amazon machine images running paparazzi and some better automated scripts to keep them up to date. I'll let the list know when I get the first version done so the list can try it out. My ultimate goal is to be able to configure and build from the remote system and just download the compiled result to be transferred to the micro controller.
- ground station difficult to manage: Continue work iPad ground station based on the iGCS project from github. I have made progress and can dynamically bind to ivy bus telemetry from a ground station based as long as I have a copy of the xml config files on the iPad (writing my own parser for these was as fun as it sounds). I'm going to publish my work on Github as soon as I can get my fork out it's svn repo and up. It's by no means complete but I'm happy with the start. Eventually I want this on android tablets as well.
- brittle system: Finally I just want to try and understand the guts of the system better so I can start to help make it a bit more user friendly, less brittle and more robust. (I'm also going to need to learn Ocaml)
I hope I can help and would be interested in collaborating on making the entire system easier to use - we should not have to fight our tools and I would love to help build on the awesome work everyone has done!
- Andy Brown IRC/twitter: magicbeef Team evaForge San Francisco, California Future work will be posted to github.com/evaforge
Feel free to contact me off list as well.
|
[Prev in Thread] | Current Thread | [Next in Thread] |