Recently, I've noticed that MavLink Protocol v1.0 has been implemented in ArduPilot Mega. I gave it a try and it worked fine with QGroundControl 1.0. However, with Mission Planner it doesn't work at all, so I presume that Mav1 is not implemented yet. Are there any plans to implement Mav1 in Mission Planner, in the near future? Thank you in advance.
Yes, it will be implemented in the next week or so.
Thank you for the really fast answer! I will be waiting!
Any news on MavLink 1.0 implementation? Thank you.
Pedro, the planner is mavlink 1.0 is ready, just needs to be built for mavlink 1.0. but wont be released mainstream untill all the AP and AC code is ready for it.
It's implemented in ArduPlane but not ArduCopter yet. Probable a few more weeks before we push it out to everyone.
Any news on MavLink 1.0 support? Thank you!
I've made a "git clone" of ardupilot-mega repository and I tried compiling Mission Planner with the "conditional compilation symbol" MAVLINK10 and it all worked like a charm! I can now use Mission Planner with my APM1 using MavLink 1.0. Thank you very much for your efforts!
1. Where in ArduPlane V 2.33 source can you force MAVLINK V1.0 or MAVLINK V0.9?
2. I am using APM Planner 1.1.83 (the latest I think) and in the top of the window title bar it displays "APM Planner 1.1.83 mav 0.9 By Michael Osborne" does this mean the the APM Planner only supports MAVLINK 0.9?
3. I can successfully connect APM Planner to the APM 2 (V 2.4.1) flashed with ArduPlane V 2.33 using the USB cable/port at 115200 baud. However I cannot connect directly to the APM2 telemetry port (Getting not Mavlink heartbeat packets received) set up as follows:
#define GCS_PROTOCOL GCS_PROTOCOL_MAVLINK
#define GCS_PORT 3// Serial port speeds.
#define SERIAL3_BAUD 57600
I have tried with and without the USB connected to the APM2 board. Is it because the ArduPlane V2.33 firmware uses Mavlink V 1.0 and is not compatible with APM planner (see 2) above)?
By default the APM will use Mavlink 0.9. If you want to use Mav1.0 you will need to add #define MAVLINK10 in ArduPlane.pde and in GCS_MAVLink.h (located in \libraries\GCS_MAVLink) and upload using Arduino1.0.
Regarding the Mission Planner, the built available for download only supports MAV0.9 (hence the 0.9 in the program top). I build myself the Mission Planner using VisualStudio 2010. The only thing you need to change is the preprocessor definition MavLink1.0cra to MavLink1.0 (in ardupilotmega>properties>build>conditional compilation symbols), inside Visual Studio IDE.
Despite this, I don't think your problem is related with MAVlink, since you can connect via USB. If your APM and Mission Planner were using different versions it will not connect at all.
Any news on when Mavlink 1.0 will be implemented in the Mission Planner? I upgraded to v2.6 but now I cant connect to the MP. Tried all the update links but it still stays on 0.9...
It is already implemented. Look for the file ArdupilotMegaPlanner10.exe in the same directory as your current ArdupilotMegaPlanner.exe. You need to run the "10" version for Mavlink 1.0.