px4_autopilot

Commit Graph

Author	SHA1	Message	Date
Beat Küng	e999075ac7	lockstep_scheduler: fix system_sleep -> system_usleep The effect was that threads that tried to exit were unnecessarily kept running. This did not cause problems except for increased resource usage.	6 years ago
Beat Küng	08298ab3d0	drv_hrt: make lockstep_scheduler a pointer This solves a potential dead-lock when trying to shutdown: a call to exit() stops all threads and calls all destructors for static objects. The destructor of LockstepScheduler takes a lock. However this is not safe, as the lock could already be taken (by any thread).	6 years ago
Daniel Agar	27ad3178f8	Jenkins add SITL tests AddressSanitizer	6 years ago
mcsauder	d12cec81ba	Add const specifier to remaining methods utilizing mavlink_message_t and similar message pointer types.	6 years ago
mcsauder	278fddb585	Cut case MAVLINK_MSG_ID_ODOMETRY content and paste into handle_message_odometry() method.	6 years ago
mcsauder	3918d0ce0a	Cut case MAVLINK_MSG_ID_VISION_POSITION_ESTIMATE content and paste into handle_message_vision_position_estimate() method. Add const specifier to publish_odometry_topic() method.	6 years ago
mcsauder	c3acd3bad3	Delete unnecessary curly braces in simulator_mavlink.cpp	6 years ago
mcsauder	e43a0bbf1d	Cut case MAVLINK_MSG_ID_RC_CHANNELS content and paste into handle_message_rc_channels() method.	6 years ago
mcsauder	801cbc856e	Cut case MAVLINK_MSG_ID_HIL_GPS content and paste into handle_message_hil_gps() method.	6 years ago
mcsauder	b705bf6b1c	Cut case MAVLINK_MSG_ID_HIL_SENSOR content and paste into handle_message_hil_sensor() method.	6 years ago
Daniel Agar	37cda4e264	Update submodule jMAVSim to latest Wed Mar 6 00:38:35 UTC 2019 (#11597 ) - jMAVSim in PX4/Firmware (`a97151feed`): `0c25b7c189` - jMAVSim current upstream: `8b2f4568e0` - Changes: `0c25b7c189...8b2f4568e0` 8b2f456 2019-02-28 Julian Oes - Merge pull request #95 from PX4/shell-style 3d0174a 2019-02-27 Matthias Grob - Fix shell script style	6 years ago
Daniel Agar	a01b598694	Update submodule mavlink v2.0 to latest Wed Mar 6 00:38:42 UTC 2019 (#11596 ) - mavlink v2.0 in PX4/Firmware (1a2b88ea30ae3bec38d2e9f11793042d7582506a): `f073569b74` - mavlink v2.0 current upstream: `2a47f11e73` - Changes: `f073569b74...2a47f11e73` 2a47f11 2019-03-01 PX4BuildBot - autogenerated headers for rev `747c3e73e9`	6 years ago
Daniel Agar	beca16fa37	ekf2 update setGpsData usage	6 years ago
mcsauder	a97151feed	Set default set_publlish() argument to true.	6 years ago
mcsauder	0bd5d6caff	Refactor set_publish() logic so that a default false value is not (re)set each loop in simulator_mapvlink.cpp and provide a default argument to set_publish() in simulator.h.	6 years ago
mcsauder	6e0fc150c0	Create Simulator::set_publish() method and Simulator::_publish member variable to allow redefinition of the Simulator::handle_message() prototype to match MavlinkReceiver::handle_message().	6 years ago
Daniel Agar	1221556515	RTL fix RTL_TYPE param metadata group	6 years ago
Paul Riseborough	6e0ca90852	ekf2: Minor parameter description edits	6 years ago
Paul Riseborough	643d8e968b	ekf2: style fixes	6 years ago
Paul Riseborough	09da8e7dfc	ekf2: Split static pressure correction into separate RH ad LH ellipsoids	6 years ago
Hamish Willee	1079ae3402	CONTRIBUTING:Fix up code.html link to goto master	6 years ago
Daniel Agar	468fb53459	navigator fix FW loiter to alt tangent exit (#11576 ) - fixes #11317	6 years ago
Gabriel Moreno	fc7c7ac206	simulator: fix to set system and component IDs as defined in params The simulator had hardcoded component ID and system ID (sysID was 0), ignoring what was set up in the params MAV_SYS_ID and MAV_COMP_ID. This caused an issue with multi-vehicle simulations that that rely on sysID to identify the vehicles. Signed-off-by: Gabriel Moreno <gabrielm@cs.cmu.edu>	6 years ago
Morten Fyhn Amundsen	951f33145f	Fix link to code style guide In CONTRIBUTING.md, the current link to the coding style leads to a 404 error. I've replaced it with a link to the Source Code Management part of the developer documentation, which is where the style guide seems to be now.	6 years ago
mcsauder	9f3937e2d2	Formatted and edited a few comments in mavlink_receiver.h.	6 years ago
mcsauder	d60d802194	Correct board-config PIN1/PIN0 typo in fmu-v5/src/board_config.h.	6 years ago
mcsauder	d42bb01e0c	Standardize method definition newlines in mavlink_receiver.cpp.	6 years ago
David Sidrane	dc50a564dd	Revert "Jenkins hardware test temporarily disable px4_fmu-v5_stachcheck tests" This reverts commit `0df34af181`.	6 years ago
David Sidrane	edd9f91a19	board:Set larger stack margin	6 years ago
David Sidrane	12d442e8dd	px4_fmuv5:Stack Check build Increase to 2624 The cause of the stack detection fault is because of the level of nesting in the start up script. We need to determine the worst case configuration and set the bar there. This fault occurred some 42 calls deep due to script calling script (repeat). The HW stack check requires as a margin of 204 bytes. That is ISR HW stacking of CPU(8) FPU(18) registers and SW stacking of CPU(11) and FPU(16) registers. Total CPU(19) registers is 68 bytes and the total FPU(34) registers is 136 bytes. On a system with a separate ISR stack This only needs to be 104 so there is 100 bytes of headroom. But as coded the detection will give a false positive detection and fault. This does not mean that the stack will be corrupted. Adjustments to that stack can have no effect due to rounding. A stack size of 2608 and 2616 can yield the exact same size stack. So even when the failure is due to a 4 byte overflow, it can take greater than a 16 bytes increase to fix it. Because the final stack size is calculated with an 8 byte alignment after a 4 byte decrease. So 2624 becomes 2620 at runtime and will boot with SYS_AUTOSTART=4001.	6 years ago
Daniel Agar	e2bf4b1894	List container improvements and testing - support range based for loops - add remove() method to remove a node - add clear() to empty entire list and delete nodes - add empty() helper	6 years ago
Beat Küng	6c3e79f361	mc airframes: reduce I gains a bit A side-effect of the previous commit is that the integral is loaded up during a flip, which leads to visible bounce-backs after a flip. Reducing the I helps, but there's a trade-off and we'll need a better solution.	6 years ago
Beat Küng	2f72e93d6f	fix mixer multicopter: do not clip for max/min throttle Except for the lower end with disabled airmode. Otherwise the rate controller would disable the integrals, which can lead to severe tracking loss in acro. It is noticeable when flying in FPV, e.g. simply when throttling straight up. Relevant part in the rate controller: https://github.com/PX4/Firmware/blob/master/src/modules/mc_att_control/mc_att_control_main.cpp#L702	6 years ago
bresch	684e2974ac	mc_pos_control_main - Re-add updateVelocityControllerIO for glitch-free position unlock	6 years ago
mcsauder	1eced05359	Rename Simulator class private methods names to match snake case of other private class methods.	6 years ago
mcsauder	b0a79996ae	Cut case MAVLINK_MSG_ID_HIL_STATE_QUATERNION content and paste into handle_message_hil_state_quaternion() method.	6 years ago
mcsauder	8b42045546	Cut case MAVLINK_MSG_ID_HIL_OPTICAL_FLOW content and paste into handle_message_hil_optical_flow() method.	6 years ago
mcsauder	24e55e4d4d	Cut case MAVLINK_MSG_ID_DISTANCE_SENSOR content and paste into handle_message_distance_sensor() method.	6 years ago
mcsauder	411db781eb	Cut case MAVLINK_MSG_ID_LANDING_TARGET content and paste into handle_message_landing_target() method.	6 years ago
Daniel Agar	0df34af181	Jenkins hardware test temporarily disable px4_fmu-v5_stachcheck tests	6 years ago
Daniel Agar	e7dfb375be	create jlink gdb upload script and use in Jenkins Hardware pipeline	6 years ago
TSC21	12d29fd093	navigator: mission_feasibility_checker: remove lazy comparison	6 years ago
TSC21	c9c86ae2ff	navigator: mission feasibility checker: minor cleanup	6 years ago
TSC21	9fa7f341e4	mission_feasibility_checker: takeoff: fix init of mission item	6 years ago
TSC21	8bf9ec32dc	mission_feasibility_checker: takeoff: add a different log message when there's a takeoff item but it's not the first waypoint	6 years ago
TSC21	468a002355	mission_feasibility_checker: takeoff: minor spelling mistakes fixing	6 years ago
TSC21	f6ab40d2dd	mission_feasibility_checker: takeoff: fix logic to return as valid	6 years ago
TSC21	676e1eb224	mission_feasibility_checker: takeoff: accept mission when takeoff is not the first item but the previous items are not waypoints	6 years ago
TSC21	6bb84af1db	mission_feasibility_checker: takeoff: change warning message	6 years ago
TSC21	5b151a5df7	navigator: mission feasibility checker: check for a takeoff waypoint on mission on specific conditions	6 years ago

1 2 3 4 5 ...

29009 Commits (3a4066c19f95e9b000218f36c3b3109c24ae2ee6) All Branches Search

29009 Commits (3a4066c19f95e9b000218f36c3b3109c24ae2ee6)

All Branches