[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[paparazzi-commits] [paparazzi/paparazzi] df8555: possible fix for adxl3
From: |
GitHub |
Subject: |
[paparazzi-commits] [paparazzi/paparazzi] df8555: possible fix for adxl345 issue in aspirin driver r... |
Date: |
Thu, 02 Feb 2012 11:09:37 -0800 |
Branch: refs/heads/aspirin_adxl345_fix
Home: https://github.com/paparazzi/paparazzi
Commit: df85559cb44aadc5d6ac8c87d376f5121cb6111e
https://github.com/paparazzi/paparazzi/commit/df85559cb44aadc5d6ac8c87d376f5121cb6111e
Author: Felix Ruess <address@hidden>
Date: 2012-02-02 (Thu, 02 Feb 2012)
Changed paths:
M sw/airborne/arch/stm32/subsystems/imu/imu_aspirin_arch.c
Log Message:
-----------
possible fix for adxl345 issue in aspirin driver reported by Luke Barnett:
It would seem that periodically the data in the rx buffer gets offset by one,
i.e. it starts at accel_rx_buf[2] instead of accel_rx_buf[1].
The strange thing is that this does not occur if I disable the magnetometers
and read gyros and accels only.
What I did to fix the issue is to call adxl345_clear_rx_buf() at the beginning
of adxl_start_reading_data().
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [paparazzi-commits] [paparazzi/paparazzi] df8555: possible fix for adxl345 issue in aspirin driver r...,
GitHub <=