I've release a new version with an additional 5 parameters for Arducopter:
Added missing Arducopter parameters stab_d, stab_d_s, acro_p, axis_p, axis_enable for a total of 47 parameters. Compatibility with ACM 2.5.3 and APM 2.3.0
The new release is available here:
Thanks for the update!
Hey Jack that is a cool station, could you list some of the items you used to build it?
I used the Ardustation with Heino awsum firmware, The Ready Made RC pan tilt for the antena, its a wood unit thats very well done comes with survos and gears, just made some mods to mount the Ardustation and then painted it, On the side I mounted a small DVR so I can record the downlink video. The video RX is 1.3gz with a patch antena. All runs on a 3 cell 2200 lipo. I have a stepdown reg. for the DVR but the rest of the system runs on 12V.
Do you have a filter on the receiver?
Yes I have a low bypass filter there because my radio is 433hz my XBee,s are 900hz and video is 1.3ghz. I seem to take some noise out of the video.
Great, thanks for the update. Do you think it would anyhow be possible to use one of the source code repositories? This would make integrating changes much easier. The easiest way of course would be to put it into the APM git repo but that's already quite full with all the ArduX projects. Then there already seems to exist a Ardustation2 svn repo but svn is so last-year :-) git actually makes life a lot easier.
I'm asking because I'm integrating the code to my own arduino mega based GCS. I have a different LCD, different button layout, etc, but the functionality is otherwise pretty much the same and so is the code. So it would simplify things a lot to have some kind of code repository, as also with the other ArduX projects.
Please let me know what you thing. Cheers and Thanks,
We had SVN set up on the Google code repository and used it for a while when there where multiple developers. For the last 6 months or so I've been the only one working on it and I really thought interest was waning - except for a few who do use it. I'm on the Arducopter and Arduplane development lists and I've been updating to try to match changes to APM and ACM and I actually use git here to track my own changes - but again didn't think there were other developers interested. However given you're interest I'd be glad to push my git repository somewhere.
My git repository is set up using pulled git from the development site so I have to figure out where to push and I'll look over the weekend for a home. I've used SVN for years and git for only 6 months so I'll bone up this weekend. I guess I could also create a clone git as described on the Arduplanes repository.
I've also broken the parameter update code working on a new version (2.0.14) with D terms added so I'm going to release that hopefully this weekend.
I'll let you know when I figure this out.
Perfect :) Yes, I'm definitely interested also to contribute. So please let me know when you picked a location.
I think the Ardustation has a lot of potential. Initially I also thought I cannot live with google maps display but actually most often I need the GCS to check for GPS lock, verify the correct parameters are loaded, etc. Laptop/smartphone based GCS's are more complex, more difficult to setup and in the case of a laptop also to carry around.
I'm also more familiar with SVN (and before, CVS) but have recently started to enjoy the benefits of git although I still don't know how to use it properly.. hehe.
I've created a clone repository here with the latest code in it:
This version has parameter update problems which I'll be working on tomorrow.
I found the problem with parameter updates failing from the Ardustation. It turns out that the Ardustation requested Mavlink messages that are transmitted at 1 Hz cause an overflow of the Xbee buffer dropping some of the bytes for the last messages transmitted. The last message was received missing the data payload which caused the Mavlink received message state machine to get stuck with an error and ignore the Mavlink parameter value message which is sent confirming the parameter change.
I disabled some of the Mavlink requested messages (which are not needed) and the parameter mechanism is now very reliable. I will release 2.0.14 tomorrow with these changes and the other missing D terms.
Thanks, I just cloned it. How do you actually set git up so that it always pulls the other directories from the APM git repo?
About the parameter sync: would it make sense to set the flow rates to 0 prior to requesting the parameters and then set them to whatever they were after parameters are received correctly? Since I was bench testing with no xbees but jumper cables this whole issue didn't occur to me.
BTW: after getting the code changes synchronized my plan was to add the following main menu items: "SET_HOME" which (re)sets the GCS home location, "ADD_WP_HERE" which would append the current location to the mission on APM. Also in flight data I already have the current waypoint index shown. Once I have everything (meaning my LCD functions, the different buttons, etc.) isolated via ifdefs I could also upload this somewhere. This will take me a few days though I guess.