Change to c_library_v2 (v2.0) submodule version of Mavlink?

[samacumen]

Currently, the mavesp8266 library takes support of older version of Mavlink. The problem is that if a custom ground control software uses Mavlink v2.0, it needs to detect the older version and change its own mavlink version in real-time.

Most of today's custom software uses Mavlink v2.0. Could you please look into switching to the later version for ease of use?

PS: The only way to currently downgrade to version v1.0 of mavlink (to avoid checksum error when sending/receiving) is by toggling the mavlink status flag, which might confuse other users.

mavlink_status_t* mavlinkStatus = mavlink_get_channel_status(mavlink_channel);
mavlinkStatus->flags |= MAVLINK_STATUS_FLAG_OUT_MAVLINK1;

As we know, Pixhawk and QGC both use v2.0, so why would we need v1.0 for ESP module?

Thanks! Shyam

[tve]

Anyone in the know care to reply? I'm also confused about this...

[LorenzMeier]

The MAVLink version detection docs are here: https://mavlink.io/en/mavlink-version.html

I don't think the ESP Firmware implements this yet. I'm sure @dogmaphobic would appreciate a pull request.