Added MAVProxy in testing of a custom MAVLink message

[wasaybaig]

I had a discussion with @hamishwillee that there is another easier way of testing your custom mavlink message. We can use MAVProxy which automatically uses messages in Pymavlink. However, if we clone the mavlink github repo, define our custom message, then generate the headers and then install pymavlink using setup.py in the mavlink repo, we can easily view our custom message on the MAVProxy console.

I find this method was easier and you could test it with MAVProxy without the need of building QGroundControl. Once this is tested on MAVProxy, you import the same headers in QGroundControl and build if required.

[github-actions[bot]]

No flaws found

[hamishwillee]

Thank you very much. I have restructured to put the update part in a separate section, and linking from where you had it. This makes the testing section a little more digestible. FWIW I prefer wireshark to this because it gives you traffic in both directions, but if you just want to test that the message is being sent, this is certainly pretty quick.

I think some of the instructions may not be quite right, but I'll add a separate comment.

[peterbarker]

Just thought I'd mention my workflow for using modified message definitions.

pbarker@fx:~/rc/pymavlink(master)$ MDEF=~/rc/ardupilot/modules/mavlink/message_definitions pip install .

Running setup.py is deprecated and is likely to break in the next few years - I'm retraining my brain, I suggest other people start to do likewise :-)

[hamishwillee]

Thanks @peterbarker ! I'll add that to the docs.

[hamishwillee]

We're closing this - docs have moved into the PX4-Autopilot repo under /docs. We effectively decided this was more complicated than it looked

[peterbarker]

@wasaybaig feel free to raise a PR against the MAVProxy wiki directly!