I've just uploaded the latest Ardustation 2 release - 2.0.15 which adds Mavlink 1.0 support. This is to support the upcoming releases of ACM and APM with Mavlink 1.0. You can still use this release with Mavlink 0.9 by commenting out the "#define MAVLINK10" statement in the main ardustation2.pde file.
This version will also warn you if it detects the wrong Mavlink heartbeat being transmitted. Ardustation 2.0.15 will display an error message on the LCD when it detects the wrong heartbeat and direct you recompile with the opposite state of the #define MAVLINK10 statement. The start up message displayed on the LCD will indicate if you have compiled for Mavlink 1.0 or Mavlink 0.9.
I've have tested Mavlink 1.0 with ACM 2.6 Gamma, APM 2.4 (with Mavlnk 1.0 enabled) and with the Mavlink 1.0 version of the Mission Planner.
As always, please let me kinow if you have any issues with this release.
email@example.com or comment on this forum post.
and is also available in my git clone here:
and you will need a git client to pull the clone down.
No - you're not the only one :)
There aren't many that I know of, but there is one on the development team actively using the Ardustation that asks for updates and I've corresponded with a few others. The nice thing is that I use the antenna tracker function all the time for a video downlink and I need the software too. Thanks for the kind words.
yes thankyou for your awesome work
I'm also a user of Ardustation 2, mostly for the antenna tracking for FPV, but it is also useful to see at a glance how many satellites I'm tracking, battery voltage etc. I have a laptop running as well to show maps and artificial horizon etc.
I appreciate the time you have put into it.
your 2.0.15 worked well with the ArduCopter 2.55. (with Mavlink 0.9)
After updating to ArduCopter 2.6 and Ardustation Mavlink to 1.0, I have no real function, with the Ardustation ;-(
There appears no heartbeat.
You had tested the 2.6 beta. What has changed?
I tested last with the 2.6 Gamma beta and haven't tested what is pushed out by the planner. I'll be sure to try it tonight and see what may be going on. Did Ardustation 2.0.15 report Mavlink 1.0 on the display at startup? I'll let you know what I find out and thanks!
Ardustation reports Mavlink 1.0 at startup. But no Heartbeat.
Hope you find something in the software and there is no problem of 3DR radio.
Can not imagine it with, because it has indeed worked well with Mavlink 0.9.
Hope it will not be a long night :-)
Just got back inside from testing. I loaded from the mission planner the 2.6 hex release and repeated set up on my quad. I then powered up the Ardustation with 2.0.15 compiled for Mavlink 1.0 and it seems to work ok on my setup. I flew 2.6 and checked antenna pointing and all looked ok. I think the software is working ok with my Xbee - but unfortunately I don't have any 3DR radios to test with.
The fact that the your 3DR radio worked with Mavlink 0.9 makes me wonder what is going on with your setup. The Mavlink 1.0 heartbeat is different and the message traffic is slightly formatted differently, but the fact that you saw no hearbeats, makes be think there is something going on with the serial data stream being received. Do you have access to an oscilloscope or logic analyzer? If not it will be more difficult to debug - but I suspect if you have serial traffic, that the heartbeat packet is being corrupted somehow. The real question is are the baud rates setup correctly (which I assume they are since they worked with 0.9) and are there bits being received at all by the Ardustation?
Did you download 2.6 from the mission planner also? If you compiled 2.6 you need to check the Mavlink 1.0 define in the config file. I suspect this isn't the problem because the Ardustation will warn you if it detects the old formatted (0.9) heartbeat. If you do have access do a logic analyzer, I would love to see what the first 30 or 40 bytes are in each 1 second frame.
If you can check some of these things I might be able to think what may be up or give you some further suggestions.
I think I've found the error. The Atmega 328 in the Station is probably defective. I'll get a new one, then try again and report in a few days.
Thank you for your trouble.
No problem Joachim - I hope that fixes it for you.
Copter-module and PC module work with Mav1.0. The module from the Ardustation also runs on the two sides (Copter + PC)
Ardustation with 2.0.15 and Mav1.0 shows no heartbeat. Even if I connect directly Ardustation and Copter with cable, no heartbeat will be displayed.
I have no measuring equipment to come here to continue.
When testing with 2.0.15 and Mav 0.9 Ardustation immediately shows that wrongful Mavlink is set. So is received but not evaluated properly. Votes not there any times / cycles? What can that be?
Has anyone else with the Ardustation Mavlink 1.0 and 3DR radio in operation?