Starling 2: TOF sensor not recognized by VOXL Portal

hgutier

Hello - I'm having an issue in which the TOF sensor in a Starling-2 is not recognized by VOXL Portal, even though the sensor looks perfectly fine and the connections and cable look fine at visual inspection. I've tried connecting and disconnecting the sensor, and enabling/disabling the cameras one by one, but no luck. After some troubleshooting it seems the issue may be with the camera board. Please advise on how to proceed. Starling-2 was purchased on February 2025 and TOF sensor has not been previously used. Thanks, Hector Gutierrez

Alex Kushleyev

Hello @hgutier ,

Can you please provide output of voxl-camera-server -l, which will scan all the connected cameras? You can just list the top part, something like this (just an example). Please note that this command will stop the background camera server service, if it's running, which can be restarted using systemctl start voxl-camera-server or just rebooting voxl2.

 voxl-camera-server -l
DEBUG:   Attempting to open the hal module
DEBUG:   SUCCESS: Camera module opened on attempt 0
DEBUG:   ----------- Number of cameras: 3

DEBUG:   Cam idx: 0, Cam slot: 0, Slave Address: 0x0020, Sensor Id: 0x0214
DEBUG:   Cam idx: 1, Cam slot: 1, Slave Address: 0x0030, Sensor Id: 0x0356
DEBUG:   Cam idx: 2, Cam slot: 2, Slave Address: 0x0034, Sensor Id: 0x0077

Also, please list the following contents:

ls /usr/lib/camera/*sensormodule*

We will just double check that the software is set up correctly to use the TOF module.

Thank you

Alex