- Mar 13, 2018
-
-
Beat Küng authored
-
Amir Melzer authored
-
Philipp Oettershagen authored
Fix: Increase pwmsim module stack by 100 bytes again because load_mon was giving warning about low stack
-
- Mar 12, 2018
-
-
David Sidrane authored
The mode change was not necessary and in fact caused the chip to not update the registerfile resulting in MAG timeouts
-
Beat Küng authored
On kinetis, the TPM_STATUS_TOF was used to detect missed interrupts for PPM decoding. However this was not correct, because the TOF bit was set on each timer overflow. This happened regularly after every 64ms interval, which meant that most PPM frames were just discarded. I have not found any equivalent register/solution that is used on STMF4, so this just removes the TOF handling. However there is now no way to detect missed edges/interrupts!
-
Beat Küng authored
Before, the RC channel was published as fast as the fmu was running (around 200Hz in unarmed state). And fix code style.
-
Beat Küng authored
-
Beat Küng authored
-
David Sidrane authored
Allow whoami of fxos8701cq and fxos8700cq
-
Daniel Agar authored
- Mar 11, 2018
-
-
Mohammed Kabir authored
-
- Mar 10, 2018
-
-
Vasily Evseenko authored
-
- Mar 09, 2018
-
-
acfloria authored
-
Simone Guscetti authored
In the stm32f7 the configuration variable for SD card with DMA changed from CONFIG_STM32_SDIO_DMA to CONFIG_STM32F7_SDMMC_DMA the maximum clock speed of 16MHz can now be achieved.
-
Roman authored
Signed-off-by:
Roman <bapstroman@gmail.com>
-
Thomas Stastny authored
* ecl: attitude_fw update - move angular rate limits to body angular rates - handle rattitude/acro vs attitude mode rate limits
-
- Mar 07, 2018
-
-
Daniel Agar authored
-
Roman authored
- the main idea is to prevent airspeed less systems to stall after a transition Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
calculation Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
- more intuitive - avoids tons of divisions Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
- more intuitive - avoids tons of divisions Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
- do not call hrt_elapsed_time since it's expensive - remove P2 front transition phase (was not even used) Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
microseconds - seconds is more intuitive - avoids tons of divisions by 1e6f Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
Signed-off-by:
Roman <bapstroman@gmail.com>
-
Roman authored
- standard vtol was implementing many custom parameters although they are generic and should be shared between the vtol types - removed heavy usage of hrt_elapsed_time() which is a system call and could be computationally expensive
-
Julian Oes authored
This fixes a problem where we do not properly go to the set takeoff altitude but end up lower. The problem was that the setpoint triplet is reset when the navigation mode changes. So in this case, the triplet is reset when we switch from takeoff to loiter which can happen before reaching the actual takeoff altitude. The fix is an ugly hack to prevent the reset in the case of takeoff to loiter. A better solution would be to remove the general reset and have all navigation modes do the proper resets themselves. This hotfix should however be lower risk.
-
- Mar 06, 2018
-
-
Daniel Agar authored
-
Daniel Agar authored
-
Daniel Agar authored
-