@Sarika-Sharma Now TOF is detected. I have choosed pmd-tof instead of pmd-tof-liow2.
But please give solution for the following problem.
When I used J7 according to the following configuration
Hardware Setup
M0104 Connector Interposer Sensor HW ID
J7 M0135 JL Tracking (M0014 ) 2
J7 M0135 JU Hires (M0025-2 ) 3
OR
J7 M0135 JL Hires (M0025-2 ) 2
J7 M0135 JU Tracking (M0014 ) 3

ONLY , The camera which is connected to JL is working either tracking or hires.
Cameras connected to JU is not working.
When i run voxl-camera-server it gives this
WARNING: cam tracking (id 1) does not seem to be alive

------ voxl-camera-server: Started 1 of 2 cameras

------ voxl-camera-server: Camera server is now running
OR
When i run voxl-camera-server it gives this
WARNING: cam hires (id 1) does not seem to be alive

------ voxl-camera-server: Started 1 of 2 cameras

------ voxl-camera-server: Camera server is now running/home/idr/Downloads/WhatsApp Image 2025-12-26 at 5.31.01 PM.jpeg

@Alex-Kushleyev @Luca-Zanatta I am also facing the same issue, can you please tell how to solve resolution problem.
I have tried to manually add preview width and preview height in vim /etc/modalai/voxl-camera-server.conf But when i run voxl-camera-server it still gives previous resolution 240*1557 and hence pmd-tof is not detected.

@Sarika-Sharma Kindly resolve this issue also https://forum.modalai.com/topic/4952/pmd-tof-not-detected-on-voxl2?_=1766730439331.

@Eric-Katzfey Thank you.

Hello ModalAI Team,

I am working with VOXL2 / VOXL2 Mini and PMD ToF V2 (M0169), and I am facing an issue where the PMD ToF camera is not detected/started by voxl-camera-server.

System details

Platform: VOXL2

System Image: 1.7.4

PMD Module: M0169 (PMD ToF)

Use case: Tracking + ToF + HiRes

Hardware connection (Option 1)
VOXL2 → M0076 → M0074 extender → M0169 (external regulated 5V supplied) → ToF

External 5V is provided to M0169.

Camera configuration

Cameras enabled: PMD ToF + IMX214 (HiRes) + OV7251 (Tracking)

IMX214 and OV7251 start correctly, but not pmd-tof

kindly look at the screenshots.
/home/idr/Pictures/Screenshots/Screenshot from 2025-12-25 17-40-44.png
/home/idr/Pictures/Screenshots/Screenshot from 2025-12-25 17-40-54.png
/home/idr/Pictures/Screenshots/Screenshot from 2025-12-25 17-41-05.png

/home/idr/Downloads/WhatsApp Image 2025-12-25 at 6.00.04 PM.jpeg

@Eric-Katzfey If you would be so kind as to tell how can i specify a different port to connect to at the GCS for each drone?

@Eric-Katzfey yes, I am using wifi and station mode.And I am able to connect multiple drones having different IP Address on the default 14550 UDP port .But I wanna ask can I specify different ports for each drone having different IP address???
For ex:
Drone 1 : IP->192.168.1.15 On port no 14551
Drone 2: IP-> 192.168.1.16 On port no 14552

I am trying to connect multiple VOXL2 Mini drones to QGroundControl (QGC) by assigning different UDP ports per drone, but I am unable to connect on any port other than the default 14550.

My Setup

Hardware: VOXL2 Mini
GCS: QGroundControl
QGC running on host PC

Goal

Drone 1

IP: 192.168.1.16

UDP Port: 14551

Drone 2

IP: 192.168.1.15

UDP Port: 14552

QGC successfully connects when using UDP port 14550 but not with 14551/14552

kindly look at the attached screenshots:
file:///home/idr/Pictures/Screenshots/Screenshot%20from%202025-12-23%2016-10-25.png

file:///home/idr/Pictures/Screenshots/Screenshot%20from%202025-12-23%2016-26-45.png

@tom I'm using a LiPo 3S battery with a voltage of 12V.

@tom Yes, I’ve already tried using a USB-A to USB-C cable and also I used the same cable to connect VOXL2 previously, and it works perfectly — I'm able to access the ADB shell without any issues, so the cable and USB port are both functional. However, when I try to connect the VOXL2 Mini using the same cable, I’m unable to see any device listed with adb devices on Ubuntu natively(I have a dual-boot setup).I’ve also checked lsusb on Ubuntu in both normal power-on and while attempting EDL mode, but no Qualcomm device shows up.
When I switch to Windows, the VOXL2 Mini appears in Device Manager as "Unknown USB Device (Device Descriptor Request Failed)" with a yellow warning icon (screenshot attached).