My hope was to bring the C# implementation in pymavlink up to v2 with as little API breakage as possible. Spending some time in the history, it looks like the code in pymavlink was originally the same as that in Mission Planner, but some years back the relevant code from pymavlink was copied to Mission Planner and has continued development there. It seems like a pragmatic choice for Mission Planner not to have a submodule dependency on pymavlink. However, for our needs would it be reasonable for us to lift the code from Mission Planner back to pymavlink? Since this appears to be mostly @Michael_Oborne 's work, I was curious about “the rest of the story” and wanted to get his input.