@david-moro Yes, the VOXL 2 Mini supports OV9782

@MattK In short, no the VOXL 2 VOA is not using the GPU. The qrb5165-dfs-server runs on the CVP, which is a computer vision dsp. The voxl-tflite-server can put different models on CPU, GPU or NPU based on how the model is configured for object recognition.

@david-moro It would be better to start a new thread with that topic.

@Jeff-Delaune-_ This is a little late, but we have 4208x3120 working now. The changes weren't in the camera driver itself but the camera pipeline and camera-server... we have it available in a nightly build if you're up to trying a pre-release out! [image: 1691793013727-182da38b-69b1-45f1-b775-d8f2f0bc2ec5-image.png]

@camharrisvayu At this point it may be worth submitting an RMA for this flight deck and we can take a look: https://www.modalai.com/pages/rma

@Eric-Katzfey I did what you suggested and it works! Thank you again!

@Chad-Sweet Is this issue, reported also here, solved?

@Brendon Does your device show up with sudo fdisk -l? On my setup, I tested with a random SanDisk drive: The last device in the list is Device Boot Start End Sectors Size Id Type /dev/sdg1 2048 60088319 60086272 28.7G 83 Linux I can then create a dir to mount to, i.e.: sudo mkdir /media/USB-Drive and mount the drive: sudo mount /dev/sdg1 /media/USB-Drive/ and then see the file on my drive: voxl2:~$ ls /media/USB-Drive/ hello

@Moderator Can you take a look at my new post. I can see that the mount command in syslog. No errors, but the mounted file system doesn't show up. Thanks, Brendon.

@Alex-Kushleyev Confirmed, changing the MODAL_IO_BAUD to 250000 fixed the problem for me. Thank you so much for the help!

@wilkinsaf , M0027 was never shipped to any customers, as it was a test version of the ESC. So there should only be M0049, M0117, M0134 and M0129 (mini) ESCs out there. Like Vinny said, all of those ESCs have a blue status LED for each MCU. If your ESC has a larger rectangular shape (as opposed to a square), it could be a really old ESC (Atmel-based, not STM32-based), which we do not really support any more. I hope this helps! Alex

@Vinny @Vinny said in GPS Not OK with VOXL2 PX4: Hi @kp-ng Eric has you covered with all SW. A small tip: From what I see in your picture, please understand that if you have WiFi and GPS antennas next to that very large power supply and no space between them, your radio link performance will be terrible. There is a good chance you will not pick up any satellites, and your WiFi link will disconnect often. For optimal performance, try to mimic the spatial separation that you would expect to see on one of our drone platforms. Thanks! ^Can you provide an example what the ideal routing for wifi antennae would be on the sentinel drone platform (specifically with the microhard modem carrier add-on)? I came across this post while trying to troubleshoot my own issues and realized that the way I have the antennae routed coming out the back of the flight deck puts one of them right next to the gps module because of how the modem is oriented.

Hi @wilkinsaf I was just thinking about your issue was going to ping you for an update. Well, yes, good that it is not repeatable, but bummer we do not know why you had it in the first place so we can all learn why. More importantly, I hope that Voxl2 is functioning correct given the error condition from the non-Quectel modem that was introduced. I also hope you verified your PDB board has the correct grounding scheme. Ping on us again if you need any extra help/tips/etc. Best option is always a new thread, or make sure to tag me on on existing threads. Thanks!

@John-Nomikos Can you enable debug output messages on voxl-streamer (Use -v 0) and post the output? Thanks!

At this point there is nothing new to share. New hardware designs and new software is required to achieve that use case which is a significant amount of work. We hope to have more to share within the next 12 months, but we don't have more precise estimates beyond that.