I'm following https://gobot.io/documentation/platforms/chip/ on macOS and seeing a compilation error in the sample program:

undefined: gobot.On

Repro steps

I ran go get -d -u gobot.io/x/gobot/... (worked)

Pasted the sample listed to main.go:

package main

import (
    "fmt"

    "gobot.io/x/gobot"
    "gobot.io/x/gobot/drivers/gpio"
    "gobot.io/x/gobot/platfor

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

Problem:
If you try to save a preset with a dis-allowed character (e.g. "map 25/25") the preset fails to save and there is no feedback to the user.
We've heard about this causing confusion with a bunch of users already (seems everyone wants to use a special character, probably a "/" in many cases).

Request:
Warn the user when saving Preset names with special characters is not allowed

There seems to be some issues with the landing function in ./software/px4_mavros_scripts/1_px4_mavros_offboard_controller/commander.py.

To do:

1. Test the land function and report if it works well.
2. Fix if there is an issue.

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

fix: remove the api about avoid obstacle//commit 5e38044cf41583acf451da909d9829b86d0988b2

in api document describe use collision avoidance,
but in code why remove that api?

I wanted to know more information regarding the roll ,pitch,yaw rate and thrust controller i was trying to develop a position controller with it but its not working

http://wiki.ros.org/mavros/Plugins

I fixed up some of the issues with setpoint and waypoint. Much more needs updated still.

The documentation for the velocity command is very wrong. After working with the drones for the past week and going through Parrot's ardronelib, here's what I have found about cmd_vel:

linear.x - percentage of maximum tilt angle forward to backward (1 to -1)
linear.y - percentage of maximum tilt angle left to right (1 to -1) 
linear.z - velocity of altitude in meters / second (parrot's docs 

Can we set up a wiki so we can start to add LibrePilot content.

Initial content suggestion:

• How to contribute to the code using the GitHub development cycle (as opposed to Antlassian)
• Key points for building on each platform

There is also a link to the wiki in the makefile which needs updating.

• 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

We should not try to reconnect to the FC when msc or dfu commands are given since the FC will not respond for sure

Here, the Transfer ID timeout is set to be 1 second:

https://github.com/UAVCAN/libuavcan/blob/f99907251859d7e8dee54f71a19bd80c9b0c64c9/libuavcan/include/uavcan/transport/transfer_receiver.hpp#L24

The spec (both v0 and v1) says it should be 2 seconds by default, although it also could be changed by the application if necessary. We should change it to 2 seconds and possibly add a method to mak

At the moment if the digital twin model does not have the plugins built, we can not communicate them them thus we get the following error,
Timeout communicating with flight control plugin.
It would be helpful if the error message included a message reminding the user to check to make sure the plugin is built, or better yet do the check automatically.

Hi,

In the data processing section of Zac's instructions on controller tuning the example output shows some parameters like "drag coefficients" and "yaw_gain" which don't show up when I run the mav_sysid.m script. Do you have any reco