I am in the process of converting from MAVLink 0.9 to MAVLink 1.0.  I use a bit stream processing method for decomming  (parsing) the MAVLink frames.  I define each message that I am interested in as a spread sheet (see attached).  I derived the spread sheet by processing the common.xml that is contained in the APM flight code delivery.  I ran into a problem with packet ID 24 (GPS_RAW_INT).  The XML definition does not match the header file definition.  The attached file 24.lis is an excerpt from the header files, and id_24_xml.lis is an excerpt from the common.xml file.  Using the header file to define the decom table works, but using the XML does not. 

Is there a central place where the MAVLink messages are defined?

Thanks in advance for your help,

Warren

mavdecom_saved_070712.txt

24.LIS

id_24_xml.lis

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • https://pixhawk.ethz.ch/mavlink/

    scroll down to MAVLink Messages ...

  • Warren, I'm guessing that the discrepancy you're talking about is the order of fields, is that correct?

    That is, in the header excerpt, the fields are in this order:

      time_usec,fix_type,lat,lon,alt,eph,epv,vel,cog,satellites_visible

    while in the XML excerpt, the fields are in this order:

      time_usec,lat,lon,alt,eph,epv,vel,cog,fix_type,satellites_visible

    The XML is the definition of the MAVLink messages, it is not generated from anything else.  The code to parse MAVLink in various languages is generated from the XML.  In this case it seems that there is a bug in the header.

  • 3D Robotics

    Start here, which is automatically generated by comments in the code:

    http://code.google.com/p/ardupilot-mega/wiki/TestParamPage

This reply was deleted.

Activity

Chris Anderson liked Zara Mae Pickering's profile
May 21
Azjeg liked Azjeg's profile
Apr 27
DIY Robocars via Twitter
RT @chr1sa: Donkeycar 4.4 released with tons of new features, including path learning (useful with GPS outdoors), better Web and Lidar supp…
Nov 27, 2022
DIY Robocars via Twitter
RT @NXP: We are already biting our nails in anticipation of the #NXPCupEMEA challenge! 😉 Did you know there are great cash prizes to be won…
Nov 24, 2022
DIY Robocars via Twitter
RT @gclue_akira: レースまであと3日。今回のコースは激ムズかも。あと一歩 #jetracer https://t.co/GKcEjImQ3t
Nov 24, 2022
DIY Robocars via Twitter
UC Berkeley's DIY robocar program https://roar.berkeley.edu/
Nov 24, 2022
DIY Robocars via Twitter
RT @chr1sa: The next @DIYRobocars autonomous car race at @circuitlaunch will be on Sat, Dec 10. Thrills, spills and a Brazilian BBQ. Fun…
Nov 24, 2022
DIY Robocars via Twitter
RT @arthiak_tc: Donkey car platform ... Still training uses behavioral cloning #TCXpo #diyrobocar @OttawaAVGroup https://t.co/PHBYwlFlnE
Nov 20, 2022
DIY Robocars via Twitter
RT @emurmur77: Points for style. @donkeycar racing in @diyrobocars at @UCSDJacobs thanks @chr1sa for taking the video. https://t.co/Y2hMyj1…
Nov 20, 2022
DIY Robocars via Twitter
RT @SmallpixelCar: Going to @diyrobocars race at @UCSDJacobs https://t.co/Rrf9vDJ8TJ
Nov 8, 2022
DIY Robocars via Twitter
RT @SmallpixelCar: Race @diyrobocars at @UCSDJacobs thanks @chr1sa for taking the video. https://t.co/kK686Hb9Ej
Nov 8, 2022
DIY Robocars via Twitter
RT @PiWarsRobotics: Presenting: the Hacky Racers Robotic Racing Series in collaboration with #PiWars. Find out more and register your inter…
Oct 23, 2022
DIY Robocars via Twitter
RT @Hacky_Racers: There will be three classes at this event: A4, A2, and Hacky Racer! A4 and A2 are based around UK paper sizing and existi…
Oct 23, 2022
DIY Robocars via Twitter
Oct 23, 2022
DIY Robocars via Twitter
Oct 19, 2022
DIY Robocars via Twitter
Oct 18, 2022
More…