I would like to add an additional sensor (that doesn’t suppose to be used by autopilot) to my Pixhawk and add it to MAVLink protocol, so I need to study out the code and principles first.
So my question regarding [color=#0000BF]THIS[/color] instruction Step #3. Do I have to change ardupilotmega.xml or pixhawk.xml in case I have last-mentioned board? And what is actually the difference between changing common.xml “[color=#008080]If this command will hopefully be added to the MAVLink protocol…[/color]” or “[color=#008080]…only for your personal use or only for use with Ardupilot…[/color]” ardupilotmega.xml ? Doesn’t changing of ardupilotmega.xml already imply adding to the MAVLink protocol?
And the second question is about using Linux, as I understood we need it only for utilizing Step #5 - “[color=#008080]run this command:./libraries/GCS_MAVLink/generate.sh[/color]”. So maybe there is a way to avoid using Linux, 'cause for a person who never worked with it wastes a lot of time, likewise switching all the time between OSes?
Thank you in advance!
So I found out the answers by myself and I will write them in case somebody have the same questions.
In Step #4 it is said, that [quote]first cd to the ardupilot directory and then run this command: ./libraries/GCS_MAVLink/generate.sh[/quote] by that you create from *.XML file a MAVLink lib that maintain data flow between UAV-GCS. For instance in …GitHub\ardupilot\libraries\GCS_MAVLink\include\mavlink\v1.0 there are 2 folders Ardupilotmega and Common that are made from ardupilotmega.xml and common.xml. There are six others header files (checksum.h,protocol.h etc) as well in v1.0 folder, but they don’t change.
So the answer is - Ilia, you should use ardupilotmega.xml if you have arduplane firmware, and pixhawk.xml if you have an original pixhawk one.
Unfortunately all my attempts using Cmaker didn’t work, so I just ran Linux, generated that files and returned back to my precious windows with required folder=)