PX4 Sync / Q&A: Dec 4, 2024Dronecode Calendar
Announcements
Release Discussion
Q&A
There will be no calls on Dec 25th 2024 and Jan 1st 2025
1- New release tag v1.15.3 is cut
2- @hamishwillee Params since v1.15 - 20241204
1- @AustinMeyer How to use all AUX/MAIN outputs on Pixhawk 6X board for servo control? uorb topic only has 8 placement for servos.
2- @AustinMeyer Implementing X-Plane as SITL or HITL discussion: The process is that all sensor data are collected at the end of each video frame which could be a fluctuating number since the average needs to be kept constant.
3- @ra1nyu : Why does acceleration control in offboard mode need velocity estimate?
PX4:main ← slgrobotics:bmi088
opened 01:37AM - 16 May 24 UTC
### Solved Problem
In my testing of Bosch Sensortec BMI088 IMU data logged to a… n ulg file had strange spikes and was not good for EKF either.
Fixes [#23111](https://github.com/PX4/PX4-Autopilot/issues/23111)
### Solution
It looks like there's a problem reading FIFO - at least for I2C connected devices.
Reading data directly from device registers (for both accelerometer and gyroscope) - using NormalRead() functions seem to solve this issue.
### Test coverage
I use a Raspberry Pi 4 and SeeedStudio BMI088 breakboard to test this code, as this is what I have on my two rovers.
More testing on Bitcraze CrazyFlie 2.1 hardware should be done, as this is the only PX4-supported platform that uses I2C for this IMU. All others connect BMI088 via SPI and therefore use different driver.
```
make bitcraze_crazyflie21
```
### Notes:
1. I believe that the code for SPI-connected devices has an error when incoming values are compared with INT16_MIN. If any of X, Y or Z values are equal to INT16_MIN - whole sample must be discarded.
This is described in https://github.com/PX4/PX4-Autopilot/issues/23111
2. There's a lot of unused FIFO-related code in _bmi088_i2c_ driver. It can be removed as we progress with this PR.
Related issue:
opened 03:47PM - 08 May 24 UTC
stale
bug-report
### Describe the bug
I am having hard time making _bmi088_i2c_ driver to work… .
It is used **only** in CrazyFlie, **other platforms use SPI version** (which I don't have).
I use _SeedStudio BMI088_ breakboard, very basic, with Raspberry Pi 4 and modified _emlid_ build.
Gyro sensor data comes with significant jitter (looks like spikes). Accel data looks normal.
The EKF orientation output, as seen in QGC, is slow to react and goes wild when sensor is moved even slightly.
The question is - is bmi088_i2c driver still supported/tested by the team? Would it be possible to verify that it works on CrazyFlie 2.1 hardware?
<img width="1406" alt="bmi088" src="https://github.com/PX4/PX4-Autopilot/assets/16037285/90ea3312-6521-48f6-b064-ae2f4aca0158">
### To Reproduce
Follow CrazyFlie build/flash procedure and see if copter orientation shows properly in QGroundControl. If it does - it is my problem, otherwise something is in the bmi088_i2c code.
### Expected behavior
CrazyFlie copter orientation shows properly in QGroundControl
### Screenshot / Media
_No response_
### Flight Log
https://review.px4.io/plot_app?log=39964b55-f407-47e5-b828-56f814986e1c
### Software Version
Current Main as of May 8, 2024
### Flight controller
Raspberry Pi + SeedStudio BMI088 over I2C
### Vehicle type
Rover
### How are the different components wired up (including port information)
_No response_
### Additional context
@mrpollo - related to Community call today
PX4:main ← PX4:mrpollo/fix_gha_deps
opened 06:24PM - 25 Nov 24 UTC
Problem
GitHub deprecated older versions of the cache, and checkout actions whi… ch are now using an updated version of node which isnt' available on the older PX4 container images
Solution
Updated cache, and checkout deps to latest where possible, and switched to the newer [px4-dev](https://github.com/PX4/PX4-Autopilot/pkgs/container/px4-dev/310191526?tag=1.16.0-alpha2) container image with the updated base operating system environment
