@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 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.

Hello community,
I am being using VOXL2 with system image 1.2.0 since long time now. Since yesterday I am facing booting problem with my VOXL2. VOXL2 isnt booting properly and initially it was going into boot loop. I took following steps to recover VOXL2 and failed.

1. I am aware of ESD problem and so have ESD matt and ground cable always connected to my hand so ESD shouldn't have been problem. I tried to put VOXL2 in fastboot mode and yes its going successfully into fastboot mode and also shows as fastboot device with command "fastboot devices" but never comes out of it. Even "lsusb" dosent show any Qualcomm device and only fastboot mode is detected correctly.

2. I tried to recover VOXL2 with QDL process as mentioned in document where QDL device and process successfully completes on VOXL2 but still it dosent boot up and adb shell never comes up for this VOXL. If I do "lsusb" while in QDL recovery then Qualcomm QDL device is been shown in the list and as a proof the process also completes successfully.

3. After QDL process, I tried to install new SDK 1.3.3 with manual fastboot mode entry by pressing fastboot switch on voxl2. Few components loads up successfully but then voxl fails to reboot and proceed with installation. Then over here I tried manual reboot by switching power off-on but still VOXL2 continues to stay disconnected.
   

Please help @Alex-Kushleyev @Eric-Katzfey

@modaltb I also want to check the stock availability of new TOF sensor over here. Is this TOF camera available for shipping currently? I cant see that on website so wanted to check with you.

@Alex-Kushleyev Sorry to bug you again. Actually I have urgent customer requirements which could be fulfilled with robust VIO which I feel is going to be with dual cam open vins approach.

1. So I wanted to check with you if there is any update over dual cam open vins release?
2. Also I have started my study over open source open vins algorithm and also would like to know some insights if there would be any modifications in open source open vins codebase or general camera and IMU driver integration?
3. Dual camera part would need frame synchronisation if I am not wrong so is that part also handled in current open vins work?

It would really give me some pathway for further work if you can shade some light over here. Thank you!

@Alex-Kushleyev Thanks Alex. I will test this out. Also I will wait for your update on PX4 related integration of this ESC AUX OUT configuration. Also PWM only outputs in voxl_esc driver extension should suffice the need.

@Alex-Kushleyev Thanks for the update.

PX4 integration is ongoing.. You could test the functionality using the python scripts for now. How would you normally expect to use the additional pwm outputs? just have voxl-esc driver provide more than 4 actuators (4 for motor rpm output and additional actuators just regular pwm?)

On this one, I would like to have AUX configurable as we do for VOXL2 IO, for example I was previously using VOXL2 IO for controlling gripper so I just configured particular Channel to Gripper functionality and then I was able to use all gripper related options in Manual and Autonomous modes in PX4. So making PWM AUX OUT available as configurable channel on QGC Actuator Tab and assigning particular functionality over there can be beneficial similar to VOXL2 IO.