Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] FMUv6X with MS5525DSO Airspeed Sensor Not Working Correctly #23434

Open
vincentpoont2 opened this issue Jul 22, 2024 · 1 comment · May be fixed by #23650
Open

[Bug] FMUv6X with MS5525DSO Airspeed Sensor Not Working Correctly #23434

vincentpoont2 opened this issue Jul 22, 2024 · 1 comment · May be fixed by #23650
Assignees

Comments

@vincentpoont2
Copy link
Member

Describe the bug

With the Pixhawk 6x + MS5525DSO Airspeed sensor, Master PX4 FW, the air speed went through calibration, but it did not require blowing into the tube. After going through calibration, the airspeed reading is incorrect & fluctuating.

No issue with Pixhawk 6C & Pixhawk 4

image

To Reproduce

Select VTOL airframe, enable SENS_EN_MS5525DS parameter, calibration airspeed sensor, look at airspeed value.

Expected behavior

The calibration should require blowing into tube, and sensor reading should be correct after calibration.

Screenshot / Media

6x_master.px4.mp4

Flight Log

N/A

Software Version

1.14.3 & Master

Flight controller

Pixhawk 6X

Vehicle type

Hybrid VTOL

How are the different components wired up (including port information)

No response

Additional context

No response

@julianoes julianoes assigned julianoes and unassigned julianoes Jul 28, 2024
@julianoes julianoes self-assigned this Aug 25, 2024
@julianoes
Copy link
Contributor

Ok, I can reproduce the problem. It turns out the issue is that the 6X has a MS5611 baro on the "external" I2C 3 which uses the same I2C address, unfortunately.

ms5611 #0 on I2C bus 3 (external) address 0x76
ms5525dso #0 on I2C bus 3 (external) address 0x76

Need to think whether there is any way around this...

@julianoes julianoes linked a pull request Sep 6, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants