@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.
@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.
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.
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.
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.
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.
@Alex-Kushleyev Perfect. Thanks for detailed explanation Alex. Regarding the beta firmware for PWM over AUX OUT, I will look forward to your firmware release later this week. Also how can we configuonfigure PWM output of these AUX OUT's? Via QGC Actuator tab? Or this would be inside firmware?
@modaltb Thanks for your inputs. So 1280x800 pixels streaming of two cameras (AR0144) over J6/J7 seems to be workable.
@Vinny Thanks Vinny for your inputs.
@Alex-Kushleyev Looking forward to your response over AUX control capabilities of this ESC along with battery/voltage monitoring integration for PX4. Thanks.
Hello community,
I have been using VOXL2 with latest SDK. I want to use M0138 FPV ESC for closed loop control over my custom drone and here are my queries.
The M0138 link say's it can power VOXL2 directly and also has battery voltage and current sensing capability. We would be using this ESC with VOXL2 Mini and want to eliminate need of using VOXL Power module. There is mention but I wanted to know if there is direct 4 pin JST similar to VOXL Power module to connect to VOXL2 Mini or we have to customize any cable? Also is the power monitoring packet delivery to PX4 on DSP happening on same UART as that used for motor control or seperate I2C channel (Similar to VOXL Power module) with M0138 ESC?
I also have requirement to control one PWM payload (Mostly trigger) with 3.3V signal voltage. I can see mention of AUX out from M0138 and toggle capability. Can someone please ellaborate on this feature weather this toggle capability is with PWM or just normal GPIO signals?
Thank you!
@Vinny Thanks Vinny. This answers my query well.
@Eric-Katzfey Please tag someone to answer camera query.
@Vinny Thanks Vinny for prompt response. I also read somewhere regarding external CAP's to be used for high speed USB3.0 datarate. Do I need to do that for doodle labs modem? My doodle would be powered externally and not from VOXL2 Mini board for sure. I just need D+ and D- connections. Also suggest connection pinout since USB on VOXL2 Mini seems to be USB3.0 and Doodle labs USB is 2.0
@Eric-Katzfey Thanks Eric for clarification. Can you please tag someone who can answer my query on camera configuration part? Also does this board have no B2B ports for expansion? I can see it has USB3.0 JST connector on board. So I guess my doodle labs connection can go directly over that USB JST?
Hello community,
I am been using VOXL2 over my custom drones since long and now I would like to get my hands onto VOXL2 Mini. My system needs two M0149 tracking camera (AR0144) and one TOF sensor. So three concurrent streams are essential. Apart from that I guess J19 is same as VOXL2 so my GPS and VOXL2 IO would work out of the box over here. But please validate and confirm. Also on USB I need to connect my doodle labs modem. Does this architecture looks viable, especially the camera requirement before I go for purchase?
Also the new TOF sensor is in stock now for sale since I can see old TOF is sold out from long time?
@Alex-Kushleyev On a seperate note, Wanted to discuss one more point on dual cam QVIO pipeline itself.
Is there a real need to actually fuse the dual qvio instances odometry into PX4 together? Can they be mutually exclusive? Something like say if one qvio instance is failing, only then fuse second qvio's odometry? Since EKF in PX4 operates in global coordinate system and it shouldn't matter to EKF from which source the fusion is actually happening. Say this backup fusion source is present as a switch in voxl-vision-hub package which only sends the fusion source whenever needed to PX4 but only one at a time. Also while changing the source, we can set reset_counter flag which has good handling now in PX4 1.14 firmware. Any thoughts on this quick approach? (I aspire to get myself onto openvins anyways for dual cam due to more control over software pipeline but I am anticipating some delay in release so asking for this alternative)