1e17a86a39
collisionprevention: fix typo in param description & minor code style
2018-11-20 14:14:13 +01:00
053494c535
use only one parameter and enable parameter change in flight. clean up code
2018-11-20 14:11:33 +01:00
efa7e0ba77
clean up
2018-11-20 14:11:33 +01:00
f5369db245
Put parameters inside library. Get rid of unnecessary activation logic
2018-11-20 14:11:33 +01:00
dd45fa6541
change feature name from CollisionAvoidance to CollisionPrevention
2018-11-20 14:11:33 +01:00
f611eddadd
unadvertise publishers in the destructor
2018-11-20 14:11:33 +01:00
81ec6c5b1e
ColisionAvoidance: move instantiation to FlightTask
2018-11-20 14:11:33 +01:00
7e276bc163
CollisionAvoidance: move activation logic to library
2018-11-20 14:11:33 +01:00
27dc60a419
Improve comments
2018-11-20 14:11:33 +01:00
ce7dc85450
Change wrong comment
2018-11-20 14:11:33 +01:00
db514fe441
Add a collision avoidance library which uses range data
2018-11-20 14:11:33 +01:00
1d12827408
Commander:Replace color based LED manipulators with logical ones.
2018-11-19 14:32:47 -05:00
fbc143dc55
sitl:Added Logical BOARD specific LED mapping
...
Define the logical LED that are uses on sitl
2018-11-19 14:32:47 -05:00
05ea187b1d
px4nucleoF767ZI-v1:Added Logical BOARD specific LED mapping
...
Define the logical LED that are uses on px4nucleoF767ZI-v1
2018-11-19 14:32:47 -05:00
b37675fa76
px4fmu-v5:Added Logical BOARD specific LED mapping
...
Define the logical LED that are uses on px4fmu-v5
2018-11-19 14:32:47 -05:00
26026b5d39
px4fmu-v4pro:Added Logical BOARD specific LED mapping
...
Define the logical LED that are uses on px4fmu-v4pro
2018-11-19 14:32:47 -05:00
735830a483
px4fmu-v4:Added Logical BOARD specific LED mapping
...
Define the logical LED that are uses on px4fmu-v4
2018-11-19 14:32:47 -05:00
90106c1fd2
px4fmu-v2:Added Logical BOARD specific LED mapping
...
Define the logical LED that are uses on px4fmu-v2
2018-11-19 14:32:47 -05:00
e40a0839e9
px4-stm32f4discovery:Added Logical BOARD specific LED mapping
...
Define the logical LED that are uses on px4-stm32f4discovery
2018-11-19 14:32:47 -05:00
03aae61395
px4-same70xplained-v1:Added Logical BOARD specific LED mapping
...
Define the logical LED that are uses on px4-same70xplained-v1
2018-11-19 14:32:47 -05:00
42a8a6ffac
omnibus-f4sd:Added Logical BOARD specific LED mapping
...
Define the logical LED that are uses on omnibus-f4sd
2018-11-19 14:32:47 -05:00
1da0021be9
nxphlite-v3:Added Logical BOARD specific LED mapping
...
Define the logical LED that are uses on nxphlite-v3
2018-11-19 14:32:47 -05:00
a12f26aee0
mindpx-v2:Added Logical BOARD specific LED mapping
...
Define the logical LED that are uses on mindpx-v2
2018-11-19 14:32:47 -05:00
3c6539257f
crazyflie:Added Logical BOARD specific LED mapping
...
Define the logical LED that are uses on crazyflie
2018-11-19 14:32:47 -05:00
e960978296
auav-x21:Added Logical BOARD specific LED mapping
...
Define the logical LED that are uses on auav-x21
2018-11-19 14:32:47 -05:00
aa30560d68
aerofc-v1:Added Logical BOARD specific LED mapping
...
Define the logical LED that are uses on aerofc-v1
2018-11-19 14:32:47 -05:00
96ba6c1174
sitl led:Support logical LED operations in commander
...
add support for all the LEDS to support
BOARD_HAS_CONTROL_STATUS_LEDS
2018-11-19 14:32:47 -05:00
0a1dd24af6
omnibus-f4sd:led clean up code and prevent out of bounds indexing
2018-11-19 14:32:47 -05:00
dc29820bd9
Document the LED colors used
2018-11-19 14:32:47 -05:00
98394afcc7
board common:Define default CONTROL_STATUS LED mapping
...
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.
2018-11-19 14:32:47 -05:00
bba475aca1
logger limit trajectory_setpoint rate
2018-11-19 09:59:22 -05:00
26bac9594f
add simple SITL shutdown test
2018-11-16 16:43:19 -05:00
48ba88eaf0
pwm_out_sim add mixer saturation status publication ( #10866 )
2018-11-16 16:42:20 -05:00
3ee596284d
ecl: Magnetic declination use improvements
...
Fixes bugs causing learned or GEO lookup declination to not be used in some circumstances.
https://github.com/PX4/ecl/pull/518
https://github.com/PX4/ecl/pull/520
2018-11-16 10:25:59 -05:00
8090734fe1
appveyor: switch cache to the entire PX4 folder
...
to save the time running the installer for every build
which was necessary before because the folder exceedes
the maximum of 1GB cache of the appveyor free plan
2018-11-16 10:19:58 -05:00
30fe079844
qurt px4_layer fix style
2018-11-16 09:53:28 -05:00
4278dd8fb4
posix px4_layer fix style
2018-11-16 09:53:28 -05:00
05d9932f6c
logger: limit vehicle_*_odometry topics to 30hz on default logging
2018-11-16 09:44:32 +01:00
2c111222cf
logger: fix vision topics naming
2018-11-16 09:44:32 +01:00
4901f8a1dc
add execption check after malloc
2018-11-16 08:15:26 +01:00
7779c0bd69
MPC - Update velocity integrator definition
2018-11-15 22:08:00 +01:00
d852ce20e6
MPC - Increase max velocity integral gain to 3.0
2018-11-15 22:08:00 +01:00
0863e95a2c
Add "Tracking Anti-Reset Windup" in velocity PID controller
2018-11-15 22:08:00 +01:00
88f6271061
Jenkins add tests on MacOS
2018-11-15 20:52:48 +01:00
c2e0368370
Update submodule Mavlink v2.0 to latest Thu Nov 15 00:37:24 UTC 2018
...
- mavlink v2.0 in PX4/Firmware (0b3f4014bf751cde2a08abb578c10ae5606404b1): https://github.com/mavlink/c_library_v2/commit/32dcf73bb24516dc0d52119e624fda8987a03f62
- mavlink v2.0 current upstream: https://github.com/mavlink/c_library_v2/commit/408a7bedf3074bcae265ea0ce8ec5bb3519ed272
- Changes: https://github.com/mavlink/c_library_v2/compare/32dcf73bb24516dc0d52119e624fda8987a03f62...408a7bedf3074bcae265ea0ce8ec5bb3519ed272
408a7be 2018-11-13 PX4BuildBot - autogenerated headers for rev https://github.com/mavlink/mavlink/tree/f3e60ba1ca9c458364cc9538499a1335aa2feb5e
c18232f 2018-11-12 PX4BuildBot - autogenerated headers for rev https://github.com/mavlink/mavlink/tree/2c52b06e125f88f6b674db112f127dc35d7a9c71
49a94c7 2018-11-09 PX4BuildBot - autogenerated headers for rev https://github.com/mavlink/mavlink/tree/c788ca3e143fbb0fd1f90a14fd2a473673b50973
0c4b296 2018-10-29 PX4BuildBot - autogenerated headers for rev https://github.com/mavlink/mavlink/tree/387c0fd71547d71f1e89578c8ef78c6bac8d6094
40bfa6c 2018-10-29 PX4BuildBot - autogenerated headers for rev https://github.com/mavlink/mavlink/tree/4590822ebde2a5737504c832669d74310afa4b8e
ad2c30b 2018-10-26 PX4BuildBot - autogenerated headers for rev https://github.com/mavlink/mavlink/tree/38ecb35a3e3e6702b5522ac33188a53cc1fe698e
9fbf059 2018-10-24 PX4BuildBot - autogenerated headers for rev https://github.com/mavlink/mavlink/tree/30b63eb0c20160ddeeca3eef4238f370d3f3d43f
7915ad4 2018-10-23 PX4BuildBot - autogenerated headers for rev https://github.com/mavlink/mavlink/tree/2c6a8807b85317275c9d027afba7f646eb7db961
4371e84 2018-10-23 PX4BuildBot - autogenerated headers for rev https://github.com/mavlink/mavlink/tree/573e35231804ad775796472bcdcd331b4479cf4d
d67e172 2018-10-22 PX4BuildBot - autogenerated headers for rev https://github.com/mavlink/mavlink/tree/40f83b2d4ff43fa65d08bb5ebeb9186dc2e8c2a6
852935c 2018-10-16 PX4BuildBot - autogenerated headers for rev https://github.com/mavlink/mavlink/tree/d683ddc28b1254ea8645dd2a18e5765b6bab0eba
2018-11-14 20:43:53 -05:00
c882ca9389
On Posix: Don't shutdown (half) the connection from the client.
...
This triggered POLLHUP too early on Mac.
2018-11-14 17:36:29 +01:00
d7c34ddee4
mavlink: fix yawing to North for LOITER_TIME ( #10828 )
...
* mavlink: yaw should wrap at 2 pi, not pi
* mavlink: use newer rad/deg conversion
2018-11-13 14:32:40 -05:00
9594ebf72e
Use unix sockets instead of pipes for posix daemon. ( #10766 )
...
Unlike pipes, unix sockets provide bi-directional
communication with each connected client.
- No need to generate a unique uuid per client anymore.
- The client doesn't have to create its own pipe anymore.
- Since there is no risk of multiple client's writes getting mixed up,
messages don't need to fit in a single write anymore, removing the
limit on command length.
- Since the server can detect a connection closing, the client no longer
needs to handle signals. When the client is killed, the connection is
automatically closed, which will cause the server to kill the related
px4 thread.
Since this does not rely on handling signals and the client sending an
additional message, this is much more reliable.
- Client is no longer a singleton.
- The protocol is simplified. Standard output is directly written to the
socket back to the client, without wrapping it in any protocol
message.
- Because of the simple protocol, one could now even use netcat to run a
px4 command:
$ echo hello | netcat -UN /tmp/px4-sock-0
Also removes a few race conditions.
2018-11-13 14:31:22 -05:00
9379c010f1
TRAJECTORY message renamed
2018-11-13 12:13:01 -05:00
9a9c17b979
vehicle_attitude_setpoint: add comment that attitude sp angles can be NaN for FW
2018-11-13 09:30:18 +01:00
Beat Küng