- Nov 21, 2018
-
-
TSC21 authored
-
TSC21 authored
-
Daniel Agar authored
-
PX4 Build Bot authored
- matrix in PX4/Firmware (4005de7b9600db8a310d52f9bf7a47a0019868d8): https://github.com/PX4/Matrix/commit/0d3bff5e006cfaa358b51e3a6d11984e3782a90e - matrix current upstream: https://github.com/PX4/Matrix/commit/9c0acfba36a928b7b002eea3a9dca54a5a0c1250 - Changes: https://github.com/PX4/Matrix/compare/0d3bff5e006cfaa358b51e3a6d11984e3782a90e...9c0acfba36a928b7b002eea3a9dca54a5a0c1250 9c0acfb 2018-11-20 Matthias Grob - Matrix: remove unsafe copyToRaw method
-
Daniel Agar authored
- mavlink v2.0 in PX4/Firmware (14b8108caabb99d1bad2daef31ac51fc061b3691): https://github.com/mavlink/c_library_v2/commit/408a7bedf3074bcae265ea0ce8ec5bb3519ed272 - mavlink v2.0 current upstream: https://github.com/mavlink/c_library_v2/commit/6203e2b64395cfa416b9321f633bc3256a79f722 - Changes: https://github.com/mavlink/c_library_v2/compare/408a7bedf3074bcae265ea0ce8ec5bb3519ed272...6203e2b64395cfa416b9321f633bc3256a79f722
-
PX4 Build Bot authored
- sitl_gazebo in PX4/Firmware (560a9b45): https://github.com/PX4/sitl_gazebo/commit/3d80f63562c24c1537e1f8423ce649c99ebc15ea - sitl_gazebo current upstream: https://github.com/PX4/sitl_gazebo/commit/2adc86b5bf84543091470966caf33c3b4f3ee666 - Changes: https://github.com/PX4/sitl_gazebo/compare/3d80f63562c24c1537e1f8423ce649c99ebc15ea...2adc86b5bf84543091470966caf33c3b4f3ee666 2adc86b 2018-11-14 Elia Tarasov - add max value for wind and wind gust means fb20a36 2018-11-14 Elia Tarasov - add normal gaussian distribution to wind gust force and direction bd5ce12 2018-11-14 Elia Tarasov - add normal gaussian distribution to wind force and direction 913c094 2018-11-07 Jacob Schloss - reverse order of test 7d08ef5 2018-11-07 Jacob Schloss - fall back to only enabling up to c++14 on old cmake 0fd93b0 2018-11-07 Jacob Schloss - set CMAKE_CXX_STANDARD so cmake does not append a defualt language standard
-
- Nov 20, 2018
-
-
Eric Babyak authored
-
Julian Oes authored
-
Julian Oes authored
The open flag `U` causes a deprecation warning starting with Python 3.4. The option to open all kinds of newlines as `\n` has been replaced with the argument `newline=None`. However, this argument is not available for Python 2 unless we use `io.open` instead of `open`.
-
Beat Küng authored
-
baumanta authored
-
baumanta authored
-
baumanta authored
-
baumanta authored
-
baumanta authored
-
Matthias Grob authored
-
Matthias Grob authored
-
baumanta authored
-
baumanta authored
-
baumanta authored
-
- Nov 19, 2018
-
-
David Sidrane authored
-
David Sidrane authored
Define the logical LED that are uses on sitl
-
David Sidrane authored
Define the logical LED that are uses on px4nucleoF767ZI-v1
-
David Sidrane authored
Define the logical LED that are uses on px4fmu-v5
-
David Sidrane authored
Define the logical LED that are uses on px4fmu-v4pro
-
David Sidrane authored
Define the logical LED that are uses on px4fmu-v4
-
David Sidrane authored
Define the logical LED that are uses on px4fmu-v2
-
David Sidrane authored
Define the logical LED that are uses on px4-stm32f4discovery
-
David Sidrane authored
Define the logical LED that are uses on px4-same70xplained-v1
-
David Sidrane authored
Define the logical LED that are uses on omnibus-f4sd
-
David Sidrane authored
Define the logical LED that are uses on nxphlite-v3
-
David Sidrane authored
Define the logical LED that are uses on mindpx-v2
-
David Sidrane authored
Define the logical LED that are uses on crazyflie
-
David Sidrane authored
Define the logical LED that are uses on auav-x21
-
David Sidrane authored
Define the logical LED that are uses on aerofc-v1
-
David Sidrane authored
add support for all the LEDS to support BOARD_HAS_CONTROL_STATUS_LEDS
-
David Sidrane authored
-
David Sidrane authored
-
David Sidrane authored
This commit is the groundwork to fix the power LED blinking on V5 Background: ---------- Early boards only had an AMBER LED that was used to indicate a High Load condition. This change defines the new logical inteface the LED_<color> should not be used in application code moving forward, only the minipulator macros should be used. Logical usage Legacy default ------------------------+------------- BOARD_OVERLOAD_LED | LED_RED Later boards defined BOARD_HAS_CONTROL_STATUS_LEDS and added the use of a BLUE and GREEN LED that were used as follows: Logical usage Legacy default ------------------------+------------- BOARD_ARMED_LED | LED_BLUE BOARD_ARMED_STATE_LED | LED_GREEN With this PR a board may now define _only_ a subset the leds and map them at the board level to the color LED it wants to use. Logical usage Legacy default ------------------------+------------- BOARD_OVERLOAD_LED | LED_RED when BOARD_HAS_CONTROL_STATUS_LEDS is defined BOARD_ARMED_LED | LED_BLUE BOARD_ARMED_STATE_LED | LED_GREEN If any of the BOARD_{OVERLOAD|ARMED|ARMED_STATE}_LED are not defined. The code output generates a null action for that LED.
-
Daniel Agar authored
-