I2C "Airspeed invalid" since last PX4-1.13.0

Hello everyone, and thanks for the great work
it’s my first entry on this board so I am not sure where to place it…

Few days ago my daily(22-05-10) build QGC (v4.2.3) upgrade the firmware of my PixHawk4 fmuv5 to the 1.13.0 a “airspeed invalid” stop arm procédure…

nsh> ver all
HW arch: PX4_FMU_V5
HW type: V500
HW version: 0x00000000
HW revision: 0x00000000
FW git-hash: 6823cbc4140e29568f00e1211ae60e057adb1a1f
FW version: Release 1.13.0 (17629439)
OS: NuttX
OS version: Release 10.2.0 (167903487)
OS git-hash: 91bece51afbe7da9db12e3695cdbb4f4bba4bc83
Build datetime: Jun 7 2022 21:31:32
Build uri: localhost
Build variant: default
Toolchain: GNU GCC, 9.3.1 20200408 (release)
PX4GUID: 000200000000353338373138511500370029
MCU: STM32F76xxx, rev. Z

This occur with two different I2C Drotek sensors (SDP33 & 0793B04)

I2C seams to work:
(NSH) NuttX-10.2.0
nsh> i2cdetect -b 1
Scanning I2C bus: 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – – – – – – – – – – – – – – 0e –
10: – – – – – – – – – – – – – – – –
20: – – – – – – – – – – – – – – – –
30: – – – – – – – – – – – – – – – –
40: – – – – – – – – – – – – – – – –
50: – – – – – – – – – – – – – – – –
60: – – – – – – – – – – – – – – – –
70: – – – – – – – – – – – – – – – –
nsh>
and disappear after downgrading to 1.12.3

NuttShell (NSH) NuttX-10.1.0
nsh> ver all
HW arch: PX4_FMU_V5
HW type: V500
HW version: 0x00000000
HW revision: 0x00000000
FW git-hash: 2e8918da66af37922ededee1cc2d2efffec4cfb2
FW version: Release 1.12.3 (17564671)
OS: NuttX
OS version: Release 8.2.0 (134349055)
OS git-hash: bf660cba2af81f055002b3817c87b1f63a78fd09
Build datetime: Sep 6 2021 16:39:27
Build uri: localhost
Toolchain: GNU GCC, 9.3.1 20200408 (release)
PX4GUID: 000200000000353338373138511500370029
MCU: STM32F76xxx, rev. Z
nsh>

Any ideas ?
Thanks again

1 Like

I seem to be having airspeed sensor issues as well, using the Drotek Sensirion SDP3x Airspeed Sensor with both an MRO Control Zero H7 and the CUAV V5 nano Autopilot running PX4 1.13.0.

On my end the airspeed sensor shows up on i2c and seems to be producing correct airspeed values when tested, but fails the calibration step on QGC (Can’t detect over 1 Pa), which then requires workarounds to be able to arm and add flight modes.

1 Like

You don’t calibrate sensirion sensors (the ones in the drotek units). They never need calibration. Just enter the tubing length correctly.

As for why it isn’t working. Starting with 1.13 you need to subscribe to the specific sensor data explicitly. Checks the params. There is one for the sdp33 which is what you’re looking for.

:+1:

1 Like

For SDP3X I had to set SENS_EN_SDP3X enable

Thanks RyanjAA it’s work well with SDP33
The command: SENS_EN_MS4525DO does the same for the drotek0793B04 aka 4525DO sensor…
Curiously i2cdetect -b 1 don’t detect the disconnecting of sensors. it keeps track of the last assigned i2C address.