@Alex-Kushleyev By any chance is the camera focus application ready for testing? I am actually struggling to get proper focus on AR0144. Initially I was able to get very good focus but now image just looks very much blurry. Have a look at below images. These images are captured by voxl-logger.

First time focus :

Current focus :

Current image appears to be blurry and also I am having hard time to get camera calibration right (reprojection error below 0.5). Previously it was good and my camera calibration worked well very fast. Let me knoiw.

Hello community,
I am regular user of VOXL2 with latest stable SDK 1.6.0. I have situation wherein I need to connect an IP camera to my microhard add-on board with mirohard OEM modem installed over the same. Now my modem is well configured and I am able to ping VOXL2 from my host machine connected to standalone microhard board but I am unable to ping my camera. This camera is connected via Ethernet to USB convertor over microhard add-on board 4 pin JST USB connector. I can ping camera from VOXL2 but for that I had to set my camera IP to 169.254.4.2 whereas eth0 interface's default IP address is coming up as 169.254.4.1. If I go to ping this camera IP of 169.254.4.2 from my host machine it isnt able to ping. Please help me solve this problem.

@John-Nomikos Hi, Can you please explain how you solved this? I am facing same problem where my camera is connected via USB to ethenret convertor with Microhard add-on board and my host machine is unable to ping my camera but can ping voxl2.

Hello community,
We are working on VOXL2 and we have Mini 4 in 1 ESC with us with in-built power module. On its datasheet page there is no mention of its continous and peak current support per channel. My UAV needs hover time 5 Amp of current per channel and in worst case scenerio at full throttle/max thrust it might shoot to maximum of 12 Amp. Will this requirement be catered by this ESC?

Hello community,
I am been using VOXL 2 with latest SDK. Recently I have purchased this ESC link text with 5V variant for VOXL2 connectivity for quadcopter configuration UAV. I have Emax 1106 motor with 6000 KV rating and Gemfan 4024 Propeller( dia of 4.0" and pitch of 2.4" with twin blade). Also I am using 2S Lipo battery. Can I get any readymade tuning parameters for this propulsion combination? If yes please do share the same.
Thank you!

@Alex-Kushleyev Hi Alex, I have one quick query on Open-vins. As mentioned on this forum link, people are able to run open-vins on nightly builds successfully. Can you please guide me to link of nightly build of openvins? Is it included in latest SDK already or needs to be downloaded and installed?

Also seperately what are the timelines for Open-vins documentation and code to be released?

Hello community,
I am working on VOXL2 with latest SDK 1.3.3 since long time now. For one of my projects I need to run single object tracker (SOT) ML model on GPU of VOXL2. I am fully aware of voxl-tflite-server and its supporting models. Now for example I am having one target tracker (Link) which works over mobile phone based on NCNN.

1. I need some guidelines on how I can approach on porting such kind of ML models to VOXL2 via voxl-tflite-server inference engine?
2. Do we have any known ML based target tracking model already ported on VOXL2? I have not seen anything as of now but still wanted to check.

@tom I fixed this problem. This was power supply cable problem. Now voxl is booting normally.

@tom No this is not on virtual machine. I am on ubuntu 22.04 LTS OS. I am powering up board with this power supply from modalai itself.

@tom Below is the output of "sudo dmesg -wH" when voxl2 is detected.

[Sep13 05:33] usb 1-4: new high-speed USB device number 7 using xhci_hcd
[  +0.128244] usb 1-4: New USB device found, idVendor=18d1, idProduct=d00d, bcdDevice= 1.00
[  +0.000017] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  +0.000005] usb 1-4: Product: Android
[  +0.000004] usb 1-4: Manufacturer: Google
[  +0.000003] usb 1-4: SerialNumber: 480f9a4a

I am seeing my voxl is going by default into fastboot mode always after bootup.

ASUS-TUF-Gaming-F15-FX507ZE-FX577ZE:~$ fastboot devices 
480f9a4a	 fastboot

What we can look at next to recover this voxl2?

@tom Yes. I did flash the correct QDL image for M0054-1 and verified that process. It completed successfully as well.