Simon Hancock

Following merging of #894, this now proposes to add a multiplier value of 360/255 to be used by satellite_azimuth, rather than create a new not-a-real-unit. I specified this literally as...

> 360/256 seams more logical > 0° == 360° > 8 LSBs of 0 bin == 8 LSBs of 256 bin yes I made the same suggestion when raising the...

It looks like if you specify `--wire-protocol 1.0` on the command line, it will generate only messages which have ids up to 255 - which makes sense as id field...

I had a super-quick look. I think the answer is to change line 306 of mavgen_cpp11.py (in function enum_remove_prefix) from: ```python if pl[i] == sl[0]: ``` to: ```python if len(sl)...

The test I did before and after the change was to edit my local xml and temporarily change 'FIRMWARE_VERSION_TYPE_OFFICIAL' to 'FIRMWARE_VERSION', and then run the generator command. I am not...

Thinking about it, I think this will still not cover the case where the enum name has a trailing "_".

From your path it looks like you are using python2.7 - the website suggests that pymavlink is only supported from Python 3.5 onwards, so maybe this is the reason. (to...

I think the import can be fixed by changing `from . import mavparse` to `from .generator import mavparse`. But then it shows up another error... ``` $ python -m pymavlink.mavtestgen...

Ah yes, I recall noticing that I must use a full sized array when building a PLAY_TUNE message, but did not dig as you have. I would vote for using...

I've had a crack at this in the following branch, if you want to try it out: https://github.com/shancock884/pymavlink/tree/iss725-string-serializarion