We are trying to integrate a Garmin Lidar Lite v3 distance sensor over i2c on our Sentinel. It appears to be available via i2c-detect on /dev/i2c-1, however px4 is not sending mavlink distance_sensor messages. It's unclear if the ll40ls driver from px4 is running.

Currently the sensor i2c is plugged into a 5G modem via the I2C port on J9, although power is coming from the VOXL2 J19 port as it requires 5V. Previous documentation references voxl-i2c, however it doesn't appear to exist on the VOXL2 so I assume this is a VOXL only tool (?). i2c-detect finds a slave on /dev/i2c-1 with address 62, which is correct for the sensor.

The SENS_EN_LL40LS param is set to 2. I'm unsure if the driver is installed, however there is an executable called px4-ll40ls. px4-ll40ls does not seem to ever print, however I can see from echo $? that any command (start, status, start -I, start -X) terminates with value 255 so presumably it always fails.

Via manually writing and reading to the slave, the sensor is confirmed to work.

In this configuration, is there another command or parameter that needs to be set to activate the distance sensor in PX4?

Other details:
We initially tried using the i2c port on J19 on the VOXL2, however the sensor never showed up in i2cdetect. The pins are listed "for future use", and as QUP3. In the documentation for the QUPs, QUP3 is listed as an SPI port for the IMU.

We currently have a Sentinel with voxl-remote-id running. However, when I try to enter the remote-id serial number on the FAA website (to register the drone for Part 107 flights), its rejected as an invalid serial number.

Is there some configuration that needs to change to get a valid remote-id serial number? Or is there a different serial number I need to access?

We are trying to integrate a Garmin Lidar Lite v3 distance sensor over i2c on our Sentinel. It appears to be available via i2c-detect on /dev/i2c-1, however px4 is not sending mavlink distance_sensor messages. It's unclear if the ll40ls driver from px4 is running.

Currently the sensor i2c is plugged into a 5G modem via the I2C port on J9, although power is coming from the VOXL2 J19 port as it requires 5V. Previous documentation references voxl-i2c, however it doesn't appear to exist on the VOXL2 so I assume this is a VOXL only tool (?). i2c-detect finds a slave on /dev/i2c-1 with address 62, which is correct for the sensor.

The SENS_EN_LL40LS param is set to 2. I'm unsure if the driver is installed, however there is an executable called px4-ll40ls. px4-ll40ls does not seem to ever print, however I can see from echo $? that any command (start, status, start -I, start -X) terminates with value 255 so presumably it always fails.

Via manually writing and reading to the slave, the sensor is confirmed to work.

In this configuration, is there another command or parameter that needs to be set to activate the distance sensor in PX4?

Other details:
We initially tried using the i2c port on J19 on the VOXL2, however the sensor never showed up in i2cdetect. The pins are listed "for future use", and as QUP3. In the documentation for the QUPs, QUP3 is listed as an SPI port for the IMU.