Feature request

Customer request to add support for the Celsius Fast-Response, ±0.1°C Temperature Sensor (I2C) for ArduRover.

Support for the Library and Driver were added in 2017, but only for ArduSub, no other firmware type. [AP_TemperatureSensor: Add AP_TemperatureSensor library and TSYS01 driver](https

Hello,

I'm currently working on safety of PX4. And there are some gaps between documentation and PX4 stack. Especially there is only one mention about what is the scenario when 2 failsafe actions come up.

**If a failsafe occurs while the vehicle is responding to another failsafe (e.g. Low battery while in Return mode due to RC Loss), the specified failsafe action for the second trigger is

INAV 2.4, configurator 2.4.1

While trying to issue command:

aux 20 ....
CLI says only slots 0-19 are allowed. Documentation at https://github.com/iNavFlight/inav/wiki/Modes says 0-39 are allowed.

Inav configurator allows to configure 21st slot in modes tab, but nothing gets programmed to FC. This is somehow understandable as CLI takes only 20 slots.
Is it a bug or a feature?
Personally

The airframes in the TUDelft folder are a bit difficult to navigate, some have quite redundant info with little documentation. We need to update this.

Issue details

Mission Planner documentation page describes that HDOP values can be changed from 100 to 900, but the GPS_HDOP_GOOD parameter is not listed in the config> full or advance parameter.
Did this parameter got replaced with something else, and documentation is lagging behind?

Version

1.3.7

Platform

[ ] All
[ ] AntennaTracker
[ ] Copter
[X ] Plane
[ ] Rove

please see http://diydrones.com/forum/topics/wpnav-parameters-changed-to-0-after-autotune
maybe there should be some logic that prevented parameters from being written unless all are populated/read before ?

• Seen in version (release version or githash): ALL
• On flight controller (if applicable): ALL

Issue details:
When using the latest Ubuntu 18.04 LTR release, no data is displaying in the Welcome Tab "GitHub Ativity" area. The Map tiles on the Flight Data tab are also not displaying when using the standard Google Sat maps. They display fine when switching to "default"
![MissingGitStuff](h

• F4 Wiring diagram
• Note on powering external sensors
• low-latency USB timer (see rosflight/rosflight#98)
• updated VSCode debugging instructions.
• Using the secondary serial device (which leads to 3DR Radio Instructions) (see #350)
• Post-Processing Bag files

As a user, I would like to be able to clearly understand what a specific property mean and how does it affect the output.