<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[VOXL 2]]></title><description><![CDATA[VOXL 2 Support Forum]]></description><link>https://forum.modalai.com/category/26</link><generator>RSS for Node</generator><lastBuildDate>Mon, 13 Jul 2026 05:47:52 GMT</lastBuildDate><atom:link href="https://forum.modalai.com/category/26.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 29 Jun 2026 16:01:29 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[VOXL2 J19 external I2C not showing clock activity]]></title><description><![CDATA[Hi @Eric-Katzfey
Thank you for your help!
I got it to work on J19 through PX4.
]]></description><link>https://forum.modalai.com/topic/5300/voxl2-j19-external-i2c-not-showing-clock-activity</link><guid isPermaLink="true">https://forum.modalai.com/topic/5300/voxl2-j19-external-i2c-not-showing-clock-activity</guid><dc:creator><![CDATA[saegsali]]></dc:creator><pubDate>Mon, 29 Jun 2026 16:01:29 GMT</pubDate></item><item><title><![CDATA[Is there a way to power this Wi-Fi Adapter + Radio using this specific ModalAI UART adapter board?]]></title><description><![CDATA[@Raiyan-Alam said in Is there a way to power this Wi-Fi Adapter + Radio using this specific ModalAI UART adapter board?:

rfd900x

Hi @Raiyan-Alam,
My suggestion: keep the Wi-Fi adapter on USB and feed the RFD900X separately.
You can pull an extra 5V feed using this power module cable, which splices off a 5V red JST SFHR connector:
https://docs.modalai.com/cable-datasheets/#mcbl-00095
Splice from that into the RFD900X's 5V input. For the M0151, don't power the RFD900X off USB but pull it directly from the power module supplying VOXL 2 instead.
]]></description><link>https://forum.modalai.com/topic/5299/is-there-a-way-to-power-this-wi-fi-adapter-radio-using-this-specific-modalai-uart-adapter-board</link><guid isPermaLink="true">https://forum.modalai.com/topic/5299/is-there-a-way-to-power-this-wi-fi-adapter-radio-using-this-specific-modalai-uart-adapter-board</guid><dc:creator><![CDATA[Vinny]]></dc:creator><pubDate>Mon, 29 Jun 2026 14:03:02 GMT</pubDate></item><item><title><![CDATA[Communication module]]></title><description><![CDATA[@Robbie-McCue
Thank you for your feedback I will look into this.
]]></description><link>https://forum.modalai.com/topic/5282/communication-module</link><guid isPermaLink="true">https://forum.modalai.com/topic/5282/communication-module</guid><dc:creator><![CDATA[Jetson Nano]]></dc:creator><pubDate>Mon, 22 Jun 2026 15:41:52 GMT</pubDate></item><item><title><![CDATA[Donwloads site contains incorrect files]]></title><description><![CDATA[@andrek Thanks for catching it! We just updated flat builds and now it contains m0054-2!
]]></description><link>https://forum.modalai.com/topic/5281/donwloads-site-contains-incorrect-files</link><guid isPermaLink="true">https://forum.modalai.com/topic/5281/donwloads-site-contains-incorrect-files</guid><dc:creator><![CDATA[ZuraNeb]]></dc:creator><pubDate>Mon, 22 Jun 2026 13:26:39 GMT</pubDate></item><item><title><![CDATA[M0054-2 Unbricking Image]]></title><description><![CDATA[@WesleyHavocAI Thanks for catching it! We just updated flat builds and now it contains m0054-2!
]]></description><link>https://forum.modalai.com/topic/5270/m0054-2-unbricking-image</link><guid isPermaLink="true">https://forum.modalai.com/topic/5270/m0054-2-unbricking-image</guid><dc:creator><![CDATA[ZuraNeb]]></dc:creator><pubDate>Tue, 16 Jun 2026 16:12:02 GMT</pubDate></item><item><title><![CDATA[Broken off Capacitor???]]></title><description><![CDATA[Hi @isagmz
That is indeed a cap. It is a 4.7uF 25V 0603 in support of the 5V input rail when sourced by J5.
[image: 1782190949170-0a20b27c-498c-4971-be16-f9c02719c08f-image.png]
We have so much margin on the 5V power rail, I would not worry about one cap missing. My best advice is to clean up that area to make sure there is no FOD or ripped up pads that can cause a short on that 5V rail from the broken cap, and just keep developing.
Let us know if you have any other issues.
Thanks!
]]></description><link>https://forum.modalai.com/topic/5268/broken-off-capacitor</link><guid isPermaLink="true">https://forum.modalai.com/topic/5268/broken-off-capacitor</guid><dc:creator><![CDATA[Vinny]]></dc:creator><pubDate>Tue, 16 Jun 2026 00:18:17 GMT</pubDate></item><item><title><![CDATA[Connecting to QGC Via Transmitter]]></title><description><![CDATA[@PatkirkMartin No, as I said a UART mapped to the applications processor would also work. PX4 has a split architecture on VOXL2 with all flight critical operations happening on the DSP and support functions such as Mavlink, logging, and data manager are on the applications processor. But there is flexibility to move functions between them as needed. So, to match the ELRS receiver with the Mavlink module you could run it on the applications processor instead of the DSP. However, you would need an expansion board that exposes such a connector.
]]></description><link>https://forum.modalai.com/topic/5255/connecting-to-qgc-via-transmitter</link><guid isPermaLink="true">https://forum.modalai.com/topic/5255/connecting-to-qgc-via-transmitter</guid><dc:creator><![CDATA[Eric Katzfey]]></dc:creator><pubDate>Wed, 10 Jun 2026 14:15:14 GMT</pubDate></item><item><title><![CDATA[Unbrick VOXL2 instruction help]]></title><description><![CDATA[@Engineer123
You can download all the necessary flat build files from our page: [modalai.filecloudonline.com](link url). Go into flat builds folder and download the m0054(154-1) flat build file
With regards to actually flashing the flat build, and using modal-qdl repo:

Make sure to put the flat build file properly in a correct folder as mentioned by the doc (./qdl/qfil_app/modalai). Make sure the file is unzipped  (it should be m0054(154-1)/ all the files, NOT m0054(154-1)/m0054(154-1)/....)
Some users have seen a higher qdl success rate when they ran install_dependencies.sh and run.sh with sudo commands. So sudo might work better
Confirm that the voxl is in edl mode

]]></description><link>https://forum.modalai.com/topic/5251/unbrick-voxl2-instruction-help</link><guid isPermaLink="true">https://forum.modalai.com/topic/5251/unbrick-voxl2-instruction-help</guid><dc:creator><![CDATA[ZuraNeb]]></dc:creator><pubDate>Fri, 05 Jun 2026 22:47:07 GMT</pubDate></item><item><title><![CDATA[Using Here 4 Blue GPS into J19 on VOXL2 with Ardupilot]]></title><description><![CDATA[Thanks @Eric-Katzfey ! Here is the pinout for the dev board "UART" port that includes i2C_SCL and I2C_SDA.
[image: 1778773646212-0cda71eb-2c0f-4b1b-ba91-8b3862fc9763-image.png]
The dev board pins 1-6 matching to J19 pins 1-6
We will give the COMPASS_DISBLMSK parameter a shot and see if that works.
]]></description><link>https://forum.modalai.com/topic/5207/using-here-4-blue-gps-into-j19-on-voxl2-with-ardupilot</link><guid isPermaLink="true">https://forum.modalai.com/topic/5207/using-here-4-blue-gps-into-j19-on-voxl2-with-ardupilot</guid><dc:creator><![CDATA[restore]]></dc:creator><pubDate>Wed, 13 May 2026 14:56:14 GMT</pubDate></item><item><title><![CDATA[AprilTag Localization not affecting static coordinate system]]></title><link>https://forum.modalai.com/topic/5197/apriltag-localization-not-affecting-static-coordinate-system</link><guid isPermaLink="true">https://forum.modalai.com/topic/5197/apriltag-localization-not-affecting-static-coordinate-system</guid><pubDate>Wed, 06 May 2026 15:09:15 GMT</pubDate></item><item><title><![CDATA[Mavlink &#x2F; TFLite &#x2F; Camera server timestamps]]></title><description><![CDATA[@Plingaas02 Regarding odometry in voxl-mavlink-server, it will not modify timestamps on this message. There will be, potentially, VIO odometry messages going to the flight controller from voxl-vision-hub via voxl-mavlink-server and flight controller odometry messages being routed out to the GCS and to the onboard stream. The odometry messages coming from PX4 will have the DSP monotonic timestamp which is different than the Linux monotonic clock and these will drift with respect to each other over time. PX4 runs the timesync service so it can correct the incoming messages from VIO.
]]></description><link>https://forum.modalai.com/topic/5191/mavlink-tflite-camera-server-timestamps</link><guid isPermaLink="true">https://forum.modalai.com/topic/5191/mavlink-tflite-camera-server-timestamps</guid><dc:creator><![CDATA[Eric Katzfey]]></dc:creator><pubDate>Fri, 01 May 2026 10:24:47 GMT</pubDate></item><item><title><![CDATA[Question about sonar sensor(distance sensor) in voxl2]]></title><description><![CDATA[What commands did you use to start each one? I would try qshell mb12xx start -X -b 4 -a 0x66 and qshell mb12xx start -X -b 4 -a 0x70
]]></description><link>https://forum.modalai.com/topic/5137/question-about-sonar-sensor-distance-sensor-in-voxl2</link><guid isPermaLink="true">https://forum.modalai.com/topic/5137/question-about-sonar-sensor-distance-sensor-in-voxl2</guid><dc:creator><![CDATA[Eric Katzfey]]></dc:creator><pubDate>Fri, 27 Mar 2026 10:04:24 GMT</pubDate></item><item><title><![CDATA[Modal AI Schematic Review]]></title><description><![CDATA[Hi @austin-c
Sorry I missed this message somehow.
I will email you to kick this off with your team.
]]></description><link>https://forum.modalai.com/topic/5122/modal-ai-schematic-review</link><guid isPermaLink="true">https://forum.modalai.com/topic/5122/modal-ai-schematic-review</guid><dc:creator><![CDATA[Vinny]]></dc:creator><pubDate>Sun, 22 Mar 2026 13:44:40 GMT</pubDate></item><item><title><![CDATA[Moving functions from J19 legacy or high speed B2B]]></title><description><![CDATA[@austin-c , The GPS driver is built for SLPI as well as APPS PROC, so you could connect it to a apps-proc UART and start the driver on the apps proc side of PX4.
This was done on RB5 : https://docs.modalai.com/Qualcomm-Flight-RB5-linux-user-guide/
https://docs.modalai.com/voxl2-linux-user-guide/
Regarding magnetometer, just like with the GPS driver, you should be able to enable the mag driver to build for apps proc. Since the apps proc i2c uses standard posix interface, it should just work. However, i don't think we have ever tried it.
Alex
]]></description><link>https://forum.modalai.com/topic/5121/moving-functions-from-j19-legacy-or-high-speed-b2b</link><guid isPermaLink="true">https://forum.modalai.com/topic/5121/moving-functions-from-j19-legacy-or-high-speed-b2b</guid><dc:creator><![CDATA[Alex Kushleyev]]></dc:creator><pubDate>Sat, 21 Mar 2026 18:49:03 GMT</pubDate></item><item><title><![CDATA[Trigger Hadron camera with DO_SET_CAM_TRIGG_DIST]]></title><description><![CDATA[@restore There are a few examples of code that listens for Mavlink messages in our SDK. For example, in voxl-mpa-tools, take a look at the source code for voxl-inspect-mavlink.c. https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-tools/-/blob/master/tools/voxl-inspect-mavlink.c?ref_type=heads
Probably would be a good idea to run voxl-inspect-mavlink on the mavlink_onboard and mavlink_to_gcs pipes to see which one has the desired Mavlink message in it. Then create your own application that listens for the Mavlink message on that pipe.
]]></description><link>https://forum.modalai.com/topic/5108/trigger-hadron-camera-with-do_set_cam_trigg_dist</link><guid isPermaLink="true">https://forum.modalai.com/topic/5108/trigger-hadron-camera-with-do_set_cam_trigg_dist</guid><dc:creator><![CDATA[Eric Katzfey]]></dc:creator><pubDate>Mon, 16 Mar 2026 21:39:28 GMT</pubDate></item><item><title><![CDATA[Wifi Card - Intermittent Connection]]></title><description><![CDATA[@Alex-Kushleyev Thanks.  On the both drones, we used them exactly out of the box, no modifications.  The issues we experienced before installing the ALFA adapter on the first drone.
For example for the 5/8 message, the model MRB-D0012-4-V4-C28-M36-T8-K2 is using the daughter board with the BOTS chip (I think it's board MDK-M0213-1-00).
]]></description><link>https://forum.modalai.com/topic/5106/wifi-card-intermittent-connection</link><guid isPermaLink="true">https://forum.modalai.com/topic/5106/wifi-card-intermittent-connection</guid><dc:creator><![CDATA[Jon Brookshire]]></dc:creator><pubDate>Mon, 16 Mar 2026 18:59:50 GMT</pubDate></item><item><title><![CDATA[Recommendations on Custom Build]]></title><link>https://forum.modalai.com/topic/5083/recommendations-on-custom-build</link><guid isPermaLink="true">https://forum.modalai.com/topic/5083/recommendations-on-custom-build</guid><pubDate>Wed, 04 Mar 2026 16:57:16 GMT</pubDate></item><item><title><![CDATA[Doodle Labs + Low Latency on VTX]]></title><description><![CDATA[@Moderator
Thanks for the clarification on the ~50 ms glass-to-glass number.
Trying to get a better understanding  the performance envelope:
1.	Does the 50 ms include RF transport over Doodle, decode, and HDMI output latency, or is that measured only within the VOXL + VRX software stack?
2.	Was this measured in point-to-point mode or mesh routing mode?
3.	Can you expand on  bitrate, resolution, and encoder settings were used (GOP structure, B-frames disabled, UDP vs RTSP)?
4.	Is MAVLink or other traffic running on the same link during that measurement?
5.	Do you have a latency breakdown per stage (encode / RF / decode / display)?
Appreciate any information you can provide. I just want to make sure I can test and validate this effectively.
]]></description><link>https://forum.modalai.com/topic/5067/doodle-labs-low-latency-on-vtx</link><guid isPermaLink="true">https://forum.modalai.com/topic/5067/doodle-labs-low-latency-on-vtx</guid><dc:creator><![CDATA[Demarconius]]></dc:creator><pubDate>Thu, 19 Feb 2026 18:05:44 GMT</pubDate></item><item><title><![CDATA[Using J18 for expander I&#x2F;O Board]]></title><description><![CDATA[@magnetocircuit Yes, this is supported. In the config file for px4 /etc/modalai/voxl-px4.conf set ESC=VOXL2_IO_PWM_ESC.
]]></description><link>https://forum.modalai.com/topic/5022/using-j18-for-expander-i-o-board</link><guid isPermaLink="true">https://forum.modalai.com/topic/5022/using-j18-for-expander-i-o-board</guid><dc:creator><![CDATA[Eric Katzfey]]></dc:creator><pubDate>Thu, 29 Jan 2026 22:46:52 GMT</pubDate></item><item><title><![CDATA[Understanding voxl-evaluate-vins]]></title><description><![CDATA[@Aaron-Porter Hello there,
voxl-evaluate-vins is currently not used by the Autonomy team @ ModalAI, we opted for our new benchmark solution, a bit more consistent in terms of statistical rigor and better integration with voxl-portal. Still, when replaying logs for VINS, it is imperative that one replays them using the ION pipes, as our VINS solution is optimized for cl_mem ptrs. Note that when replaying ION pipes, it is recommend to stop camera-server before replaying -- as clean killing ION pipes via the voxl-replay args is currently being optimized. This should resolve the common segfaults experienced during the replay/benchmark operation itself.
https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-benchmark-vio
Finally, I would recommend updating your VINS to the latest available tag on Gitlab
]]></description><link>https://forum.modalai.com/topic/5021/understanding-voxl-evaluate-vins</link><guid isPermaLink="true">https://forum.modalai.com/topic/5021/understanding-voxl-evaluate-vins</guid><dc:creator><![CDATA[zauberflote1]]></dc:creator><pubDate>Thu, 29 Jan 2026 20:05:12 GMT</pubDate></item><item><title><![CDATA[Boot System Image from SD Card Possible?]]></title><description><![CDATA[@sja123 No, unfortunately, we do not currently support boot from SD card.
]]></description><link>https://forum.modalai.com/topic/5019/boot-system-image-from-sd-card-possible</link><guid isPermaLink="true">https://forum.modalai.com/topic/5019/boot-system-image-from-sd-card-possible</guid><dc:creator><![CDATA[Eric Katzfey]]></dc:creator><pubDate>Thu, 29 Jan 2026 19:37:34 GMT</pubDate></item><item><title><![CDATA[ROS_DOMAIN_ID Change]]></title><description><![CDATA[Hey @yunwool
Just to be clear, consider only your first drone, if you run export ROS_DOMAIN_ID=1, then run ros2 topic list, you aren't seeing any topics right?
After you set the ROS_DOMAIN_ID of a drone to 1, to get the PX4 topics to show up, on QGC &gt; Analyze Tools &gt; MAVLink Console, run the following commands:
param set XRCE_DDS_DOM_ID 1
param save

Then power cycle the drone, give it like 15s after boot up, then the topics should come up directly when running ros2 topic list on that drone.
]]></description><link>https://forum.modalai.com/topic/5000/ros_domain_id-change</link><guid isPermaLink="true">https://forum.modalai.com/topic/5000/ros_domain_id-change</guid><dc:creator><![CDATA[ApoorvThapliyal]]></dc:creator><pubDate>Wed, 21 Jan 2026 01:17:19 GMT</pubDate></item><item><title><![CDATA[VOXL2 WiFi SoftAP issues (M0141 + AWUS036EACS)]]></title><description><![CDATA[Update:
I bought an Alfa Networks AWUS036ACS and it worked out of the box with the M0151 board
]]></description><link>https://forum.modalai.com/topic/4971/voxl2-wifi-softap-issues-m0141-awus036eacs</link><guid isPermaLink="true">https://forum.modalai.com/topic/4971/voxl2-wifi-softap-issues-m0141-awus036eacs</guid><dc:creator><![CDATA[Dronodev]]></dc:creator><pubDate>Wed, 07 Jan 2026 19:14:28 GMT</pubDate></item><item><title><![CDATA[Voxl 2 USB-C And Unity]]></title><description><![CDATA[@JoonaR Hi Joona, the DP should work to drive an HDMI projector with the appropriate adapter. This adapter has been tested to work: https://www.amazon.com/Cable-Matters-48Gbps-Adapter-Supporting/dp/B08MSWMXT4?th=1
]]></description><link>https://forum.modalai.com/topic/4947/voxl-2-usb-c-and-unity</link><guid isPermaLink="true">https://forum.modalai.com/topic/4947/voxl-2-usb-c-and-unity</guid><dc:creator><![CDATA[Moderator]]></dc:creator><pubDate>Tue, 23 Dec 2025 15:09:39 GMT</pubDate></item></channel></rss>