Tony Wall

Code **must** always format and layout the same way for all developers, hence no user settings are required for code style and formatting options. Perhaps start by shifting such settings...

The start of the Teensy code (any any other MAVLink code such as MinimOSD) sends subscription messages and following-on only receives those messages. I don't know if Pixhawk is hard-coded...

Delayed due to issues with tools (see RC Input #2).

This particular module is not a good choice. First the proof of concept I am working on for driver development must be done to the point we have no more...

You should go and read the history in #12 and the others (there are not many). All of this stuff has already been investigated in depth by me and discussed...

Brought forward and now top priority because access to the RCIO chip (a proxy to most the useful functionality of the Navio 2 board) is blocked by limitations again programming...

Indeed successful in C++, the code is now migrating to the "HardwarePlus" project. On the C++ landscape there are also major changes occurring. Basically it seems Microsoft realized the effort...

https://github.com/Microsoft/cppwinrt/issues/93#issuecomment-277464513

Depending on GPS support in the IoT preview it might even be possible to make an ACPI table so the BIOS hooks-up the Navio uBlox GPS to the built-in driver...

Tests prove access to the second SPI bus is indeed possible but strangely enough not in C# XAML applications compared to C# background applications (or broken by the Visual Studio...