Unable to use any disance sensor on Holybro Durandal

Hello, I am trying to use a distance sensor as altimeter.
I am running 1.13.2 firmware version, and I have followed the instruction reported on lidar_lite page for I2C connection without any results.

EKF2_AID_MASK: 133 (GPS + IMU bias + GPS yaw)
EKF2_RNG_AID: 1 (enabled)
EKF2_TERR_MASK: 1 (range finder)
EKF2_MIN_RNG: 0.30
EKF2_HGT_MODE: 2 (range sensor)

The strange thing is that even with SYS_HAS_NUM_DIST setted, I do not have any error or warning in QGC regarding the missing sensor(is connected).

As you can see from the image, the distance sensor page does not show up in QGroundControl (v4.2.4).

I have alredy try to use different QGC and PX4 versions, but nothing changes.
I have already check multiple times cables position and the voltage, I have 5V on power (external BEC) and 3.3V on the signals.

After the boot if I run dmesg on MAVLink Consolle I get the following output:

NuttShell (NSH) NuttX-11.0.0
nsh> dmesg
HW type: VD00
HW version: 0x00000000
HW revision: 0x00000000
FW git-hash: 46a12a09bf11c8cbafc5ad905996645b4fe1a9df
FW version: Release 1.13.2 (17629951)
OS: NuttX
OS version: Release 11.0.0 (184549631)
OS git-hash: 91bece51afbe7da9db12e3695cdbb4f4bba4bc83
Build datetime: Nov 22 2022 09:02:55
Build uri: localhost
Build variant: default
Toolchain: GNU GCC, 9.3.1 20200408 (release)
PX4GUID: 000600000000343434363038510b0042002b
MCU: STM32H7[4|5]xxx, rev. Y
INFO  [param] selected parameter default file /fs/mtd_params
INFO  [param] importing from '/fs/mtd_params'
INFO  [parameters] BSON document size 2386 bytes, decoded 2386 bytes (INT32:43, FLOAT:78)
INFO  [param] selected parameter backup file /fs/microsd/parameters_backup.bson
Board architecture defaults: /etc/init.d/rc.board_arch_defaults
Board defaults: /etc/init.d/rc.board_defaults
INFO  [dataman] data manager file '/fs/microsd/dataman' size is 62560 bytes
rgbled_ncp5623c #0 on I2C bus 1 (external) address 0x39
Loading airframe: /etc/init.d/airframes/6001_hexa_x
INFO  [uavcan] Node ID 1, bitrate 1000000
INFO  [px4io] IO FW CRC match
Board sensors: /etc/init.d/rc.board_sensors
icm20689 #0 on SPI bus 1 rotation 2
bmi088_accel #0 on SPI bus 1 rotation 2
bmi088_gyro #0 on SPI bus 1 rotation 2
WARN  [SPI_I2C] Already running on bus 1
ERROR [SPI_I2C] bmi088: no instance started (no device on bus?)
WARN  [SPI_I2C] Already running on bus 1
ERROR [SPI_I2C] bmi088: no instance started (no device on bus?)
ist8310 #0 on I2C bus 3 (external) address 0xE rotation 10
ms5611 #0 on SPI bus 4
ist8310 #1 on I2C bus 1 (external) address 0xE rotation 10
WARN  [SPI_I2C] ll40ls: no instance started (no device on bus?)
ERROR [heater] Valid SENS_TEMP_ID required
WARN  [SPI_I2C] Already running on bus 1
INFO  [pwm_out] instance: 0, max rate: 100, default: 50, alt: 50
INFO  [init] Mixer: /etc/mixers/hexa_x.main.mix on /dev/pwm_output0
INFO  [init] Mixer: /etc/mixers/pass.aux.mix on /dev/pwm_output1
INFO  [pwm_out] instance: 0, max rate: 100, default: 50, alt: 50
ekf2 [843:237]
Starting Main GPS on /dev/ttyS0
Starting MAVLink on /dev/ttyS1
WARN  [mavlink] offboard mission init failed (-1)
INFO  [mavlink] mode: Normal, data rate: 1200 B/s on /dev/ttyS1 @ 57600B
INFO  [logger] logger started (mode=all)
INFO  [logger] Start file log (type: full)

NuttShell (NSH) NuttX-11.0.0
nsh> WARN  [commander] Switching to Altitude is currently not available    
INFO  [logger] [logger] /fs/microsd/log/sess137/log100.ulg    
INFO  [logger] Opened full log file: /fs/microsd/log/sess137/log100.ulg
ERROR [uavcan] couldn't start parameter count: -2
INFO  [gps] u-blox firmware version: SPG 3.01
INFO  [gps] u-blox protocol version: 18.00
INFO  [gps] u-blox module: NEO-M8N-0
WARN  [commander] Switching to Position is currently not available    
INFO  [mavlink] Starting mavlink shell

If I check the I2C connection with i2cdetect and the sensor does not show up on the second bus as expected.

If I try to manualy start the sensor with ll40ls start -X -b 2 command, I get this message from MAVLink console:

Screenshot from 2023-02-08 10-23-27

The strange thing is that If I change Durandal, lidar lite, and type of sensor (I had try with a I2C teraranger) is the same extact thing. I can not get any sensor work.

Can you please help me?

try to use the -a “I2C adress of the sensor” argument. Maybe the default one in the driver is different than yours.

try to edit the file name is px4_pluginlists.yaml in the mavros/mavros/launch
comment the distance sensor and rangefinder
ref: How to Read Distance Sensor Data from MAVROS Topic - #2 by mfurkannargul