Tree: eb88e6a37c

c415-sdk

celiu-4.0

celiu-4.0.17-rc8

master

mission-4.1.18

zr-sdk-4.1.16

zr-sdk-4.3.1

zr-v4.1.17

zr-v5.0

zr-v5.1

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'eb88e6a37c'

${ noResults }

Commit Graph

44993 Commits (eb88e6a37c6dc2e8df8d1238e882c31fbb68ceef)

 

All Branches   

Search

Author	SHA1	Message	Date
Michel Pastor	eb88e6a37c	AP_OSD: Fix vertical speed varying length	4 years ago
Andrew Tridgell	88b5523d47	AP_UAVCAN: added logging of UAVCAN LogMessage messages ... this allows us to log internal errors from nodes into main flight controller log	4 years ago
Andrew Tridgell	b2885e3e32	AP_CANManager: exposed can log level	4 years ago
Andrew Tridgell	cf22caa7ef	HAL_ChibiOS: raise stack limits in f303 peripherals	4 years ago
Andrew Tridgell	3ba46d5bd9	HAL_ChibiOS: enable reporting of watchdog reset on AP_Periph	4 years ago
Andrew Tridgell	0c2770a8d4	AP_Periph: added DEBUG parameter for displaying stack usage	4 years ago
Andrew Tridgell	ba69cd72c9	HAL_ChibiOS: improved stack checking and stack display ... display both ISR stack and thread stacks. Show total stack sizes as well as amount of stack remaining	4 years ago
Andrew Tridgell	84eac7642b	HAL_ChibiOS: improved stack checking	4 years ago
Andrew Tridgell	2d459dccc3	HAL_ChibiOS: reduced stack usage in CAN RX handler	4 years ago
Andrew Tridgell	c778d14fd3	HAL_ChibiOS: enable stack checking on f303 boards	4 years ago
Andrew Tridgell	573cd6db6d	HAL_ChibiOS: adjust MAIN_STACK for more ISR stack ... we need more stack to deal with interrupt nesting between CAN, system timer and serial interrupts	4 years ago
Andrew Tridgell	52a90e7a33	HAL_ChibiOS: fixed monitor thread with no logging	4 years ago
Andrew Tridgell	2a29b0fcf5	HAL_ChibiOS: fixed AP_Periph build with --enable-asserts	4 years ago
Andrew Tridgell	d586a2d853	AP_Periph: added magic FLASH_BOOTLOADER=42/43 values ... when FLASH_BOOTLOADER=42 we will enter into a lockup loop, which will trigger a watchdog. This is useful for testing watchdog support	4 years ago
Andrew Tridgell	5e81fadf13	AP_DAL: ensure RRNH is written before RRNI ... this is required now we are dynamically allocating the backends in replay	4 years ago
Andrew Tridgell	172854c894	AP_DAL: fixed build on navio ... avoid shadowed variables	4 years ago
Andrew Tridgell	bdba430e55	AP_NavEKF3: save memory on beacon debug structure ... only allocate when beacons are enabled. This relies on a guarantee in the DAL that the beacon count cannot change	4 years ago
Andrew Tridgell	7b08053ef2	AP_DAL: guarantee that the beacon count cannot change after startup	4 years ago
Andrew Tridgell	bb32f1a397	AP_NavEKF3: avoid initialising unused ring buffers ... this assumes the nav sources are treated as reboot required	4 years ago
Andrew Tridgell	4fdbbd8984	AP_NavEKF: added functions to see if a nav source is enabled ... this allows us to avoid initialising ring buffers when not needed	4 years ago
Andrew Tridgell	ab917ed92e	AP_NavEKF: add more protections on ring buffer code ... declare an internal error if we try to access an element when not initialised	4 years ago
Andrew Tridgell	0c05e9a2e7	AP_RangeFinder: fixed handling of instance numbers ... if a backend allocation failed then we could end up with the backend being assigned to the wrong instance number. Switch to using _add_backend() everywhere, and pass the instance number to _add_backend() to ensure that it always uses the correct slot. Also added comment explaining how num_sensors() works when we have a sparse set of rangefinders configured	4 years ago
Andrew Tridgell	73755e2d1f	AP_DAL: only allocate rangefinder backends that we need	4 years ago
Andrew Tridgell	893e9ea7fd	AP_DAL: don't allocate sensor backends unless needed ... this saves memory on boards without those sensors	4 years ago
Peter Barker	ba0367fa9f	Replay: add check_replay_branch.py to check for EKF output changes ... Create a replay log using master branch. Check out a specified branch, compile and run Replay against replay log Run check_replay.py over the produced log	4 years ago
Peter Barker	8d756d8758	Replay: check_replay.py: default to print for progress function	4 years ago
Peter Barker	e972fb31b1	AP_NavEKF3: remove unused variables	4 years ago
Peter Barker	fc7e7dcee4	AP_NavEKF2: remove unused variables	4 years ago
Peter Barker	0529ddcd67	AP_NavEKF3: move badMagYaw onto stack	4 years ago
Peter Barker	addd57dcab	AP_NavEKF2: move badMagYaw onto stack	4 years ago
Peter Barker	2885026bba	AP_NavEKF3: move tasHealth to be a stack variable	4 years ago
Peter Barker	0aa10d8281	AP_NavEKF2: move tasHealth to be a stack variable	4 years ago
Peter Barker	b79a26135c	AP_NavEKF3: move posvel fusion health booleans to be on the stack	4 years ago
Peter Barker	3a98d51427	AP_NavEKF2: move posvel fusion health booleans to be on the stack	4 years ago
Peter Barker	2d25149e2e	AP_NavEKF3: move global state to be on the stack	4 years ago
Peter Barker	400ba7a9df	AP_NavEKF2: move global state to be on the stack	4 years ago
Brent McLaughlin	e241433c89	AP_Rangefinder: change lightware lost signal timer to 20 ... The LightWare lost signal timer is set to 20 by the manufacturer.	4 years ago
Andrew Tridgell	d242339f2e	AP_NavEKF3: added have_vz flag to GPS buffer data ... this ensures that we record GPS vertical velocity status for every sample correctly	4 years ago
Andrew Tridgell	4e4a044d5d	Tools: removed inhibitGps and inhibitGpsVertVel options ... these were unused	4 years ago
Andrew Tridgell	80f7906744	AP_NavEKF3: removed inhibitGps and inhibitGpsVertVel options ... these were unused	4 years ago
Andrew Tridgell	7313e9eb0f	AP_NavEKF2: removed inhibitGps and inhibitGpsVertVel options ... these were unused	4 years ago
Andrew Tridgell	281e2cb693	AP_DAL: removed inhibitGps and inhibitGpsVertVel options ... these were unused	4 years ago
Andrew Tridgell	0a80fce8b8	AP_AHRS: removed inhibitGps and inhibitGpsVertVel options ... these were unused	4 years ago
Andrew Tridgell	603e0c090d	AP_NavEKF3: don't reset EKx_GPS_TYPE when GPS has no vertical velocity ... setting the parameter to 1 causes the following issues: - the GPS may not have vertical velocity at the time the parameter set happens, but may get it later when the GPS is fully configured - we may switch between GPS modules which do/don't have vertical velocity - the user may download parameters after the set(1), and end up with incorrect parameters they may later load onto the vehicle, permanently disabling use of vertical velocity	4 years ago
Andrew Tridgell	79148498d3	AP_NavEKF2: don't reset EKx_GPS_TYPE when GPS has no vertical velocity ... setting the parameter to 1 causes the following issues: - the GPS may not have vertical velocity at the time the parameter set happens, but may get it later when the GPS is fully configured - we may switch between GPS modules which do/don't have vertical velocity - the user may download parameters after the set(1), and end up with incorrect parameters they may later load onto the vehicle, permanently disabling use of vertical velocity	4 years ago
Peter Barker	4d30b52744	RC_Channel: add string for motor eSTOP	4 years ago
Peter Barker	4b6e4e10ed	AP_Button: allow RC Channel function to be specified for a button ... Function will be executed on transition	4 years ago
Peter Barker	164bd95538	AP_Button: allow PWM to be used for button input	4 years ago
Peter Barker	7ea78791c2	RC_Channel: make string_for_aux public	4 years ago
Peter Barker	0f597e0919	RC_Channel: expose do_aux_function for button to call	4 years ago