Thanks for the update. Yes, let us know when there is a pre-release.

@Chad-Sweet what is the reason for using Gralloc allocator on apq8096 for buffer allocation instead of ION memory allocator used in the qrb5165 implementation ?

The Pipe API worked great! Thanks. Can the hires camera output RBG instead of NV12 and can voxl-camera-server support that?

Hi @Brandon-Wightman Please review this diagram, and you can see the serial port is not a functional item in "standalone dongle mode", hence why it is DNI'd. https://docs.modalai.com/microhard-usb-carrier/#block-diagram If you are referring to the Microhard's UART port that we label "pDDL UART" here: https://docs.modalai.com/microhard-add-on-datasheet/#bottom-of-board that is present in either standalone or Voxl configs. You are right, we neglected to post that pinout, since you would actually be the first person in almost 4 years since we launched that product to ask for it. Please clarify if that is what you are after, and we can update our tech docs to include that pinout. However, we do not have Software for it, so you would be trail-blazing both HW and SW efforts here if you plan to develop it on your own. Thanks!

We're sorry if that happened. Someone from operations will reach out

Yes, I saw one camera you mentioned on there, but the SKU was wrong, so it is impossible for me to know which camera you are referring to. To quote the documentation: You can find the Arducam Specs and Selection guide by going here. The Arducam B0229 is an excellent choice. The B0229 is not an Arducam camera. It is a camera cable for Raspberry Pi. I would use some webcam listed on your UVC page, but I need a wide viewing angle and preferably IR support. Refresh rates less than 24Hz aren't really acceptable. They just don't really fit the bill. Maybe you know of a camera that would work? I'd prefer to get what I bought working, but I can get something different if necessary.

You are using the same cable that has worked with other android devices correct? I have used a charging cable on accident before

I found out that the WiFi dongles were broken which is what was causing the issue

Okay, thank you. Will follow up if/when I get something working.

@Eng-Abdullah-Ghazi-AlMusalami This is our 1.14 branch: https://github.com/modalai/px4-firmware/tree/voxl-dev. We have been flying with it for quite some time now but it is not complete and ready for general release. Major features still missing are Qualcomm Flight RB5 5G Platform VIO support, collision avoidance, and M0065 support. The documentation is still being prepared. If you are comfortable getting started without those things then feel free to start playing around with it. Otherwise I would recommend waiting for our official release of it. It's about 4 weeks out at this point.

It would likely be difficult, the seeker isn't designed for payload capacity

Couple of questions How are you attempting to connect to the VOXL? Wifi? Radio? etc... Also, what OS are you running (I have heard of firewalls getting in the way of connecting sometimes)? If you are connecting over wifi, what do you see when you enter the address of the VOXL into a web browser? VOXL-portal is enabled, so if you are truly connected you should see a VOXL webpage pop up Can you please put the output of these commands here cat /etc/modalai/voxl-mavlink-server.conf and cat /etc/modalai/voxl-vision-px4.conf

Hi @Darshit-Desai Sorry, no, that original debug board is limited to 500mA USB VBUS, hence why we made the "M0078" board (first link I had above). The cable we used to carry was MCBL-00019 for this Voxl1 USB ADB Port Host-mode use case, but it has been very difficult to source so we had to obsolete it. We've heard of a few folks hack a normal USB3 cable to swap the RX and TX with marginal success. It's not impossible, but not scalable and reliable unless you have a cable vendor make you a custom cable. We made sure on Voxl2-Mini we listened to customers and enabled true USB-C OTG on that port. We are working on a revised Voxl2 soon which will also make that an option. Sadly however, for Voxl1, it is what it is. Our newer Voxl2 plug-in boards all support at least 1A USB VBUS to accommodate the higher-demanding cameras and accessories our customers have been trying to use, so we are trying to adapt to our customer's needs and keep improving design support/features. Hope this helped.

I came across a former-topic discussing a similar issue to mine. BTW, about a month ago, when I tried using voxl-mapper based on your YouTube video (hands-on test without flying), it was able to generate the path successfully. [image: 1683992105522-portal-able.png] During that time, I accidentally turned over the TOF camera, resulting in a reversed image. I'm wondering if that could be the cause of the problem I'm currently facing?

Hi @Subramanian-Ramasamy Our tech docs site has a ton of useful information for hardware and software features. I suggest you look through these pages and I'm sure most of your questions will be answered: https://docs.modalai.com/voxl-sdk/ For more Hardware level features, look into each drone platform's specific pages from this launchpad: https://docs.modalai.com/voxl-dev-drones/