rust-mavlink
rust-mavlink copied to clipboard
mavlink
MAVLink library for Rust.
Right now it's necessary to know if the connection is done with mavlink1 or mavlink2
It would be nice to have a way of non-blocking `recv()`. I think there is many applications for it, just like in [`std::sync::mpsc::Receiver`](https://doc.rust-lang.org/std/sync/mpsc/struct.Receiver.html).
@laptou can you take a look ?
Right now we have a feature called **emit-extensions** that generate it it compile time. But we have mavlink V1 or mavlink V2 as a runtime option and that should the...
With `0.8` I get the following warning: ``` $ cargo build ... warning: unused import: `crate :: { }` --> /tmp/rust-mavlink/target/package/mavlink-0.8.0/target/debug/build/mavlink-2d6a5ed84e19de61/out/common.rs:2:174 | ... It is not critical, but it would...
This fixes #245 as outlines there.
The feature `emit-extensions` that is supposed to enable mavlink v2 extension does not currently work for versions 0.13.x. This can be seen when comaparing the documentation (which enables all features)...
On the latest 0.13.1 version a dialect containing an enum definition without explicit entry value assignments such as ```xml This is just for testing the bindgen ``` will generate the...
(depends on #284) So, my goal is to have some sort of way to fetch raw messages from the connection wrappers ([`AsyncMavConnection`](https://github.com/mavlink/rust-mavlink/blob/master/mavlink-core/src/async_connection/mod.rs), [`MavConnection`](https://github.com/mavlink/rust-mavlink/blob/master/mavlink-core/src/connection/mod.rs#L20)) directly, without having to do the extra-step...
Currently using `mavlink` against [mavlink](https://github.com/mavlink/mavlink/) master's message definitions does not compile. There are 2 issues, both related to bitmasks: - The enum `GIMBAL_MANAGER_FLAGS` that is `bitmask="true"` is used in messages...