Hey Alex. Thanks for this input. I will incorporate your feedback as we continue initial motor testing and let you know if we need further guidance.
Much appreciated!
Hey Alex. Thanks for this input. I will incorporate your feedback as we continue initial motor testing and let you know if we need further guidance.
Much appreciated!
I really appreciate you taking the time to answer this question! Thank you so much. Very helpful.
My team and I are definitely interested in making this work, so if you are willing to release the source to us that would be great. I will most likely need to continue reaching out for technical guidance as we work to get this implemented. What might be the best way to continue technical discourse on this subject? A new thread? Direct message?
Hardware
Software Version (voxl-version)
voxl2-test-fixture (TF-M0054):/$ voxl-version
────────────────────────────────────────────────────────────────────────────────
system-image: 1.8.06-M0054-14.1a-perf
kernel: #1 SMP PREEMPT Wed Oct 22 04:13:18 UTC 2025 4.19.125
────────────────────────────────────────────────────────────────────────────────
hw platform: M0054
mach.var: 1.0.1
SKU: TF-M0054-4-V1-C11
────────────────────────────────────────────────────────────────────────────────
voxl-suite: 1.6.3
────────────────────────────────────────────────────────────────────────────────
Packages:
Repo: http://voxl-packages.modalai.com/ ./dists/qrb5165/sdk-1.6/binary-arm64/
Last Updated: 2023-03-02 12:58:39
List:
libfc-sensor 1.0.9
libmodal-cv 0.6.0
libmodal-exposure 0.1.4
libmodal-flow 1.0.3
libmodal-journal 0.2.7
libmodal-json 0.4.8
libmodal-pipe 2.14.11
libqrb5165-io 0.6.3
libvoxl-cci-direct 0.3.3
libvoxl-codec 0.0.2
libvoxl-cutils 0.1.6
modalai-slpi 1.2.2
mv-voxl 0.1-r0
qrb5165-bind 0.1-r0
qrb5165-dfs-server 0.2.0
qrb5165-mini-tof-server 0.2.2
qrb5165-rangefinder-server 0.1.6
qrb5165-slpi-test-sig 01-r0
qrb5165-tflite 2.17.2
voxl-bind-spektrum 0.1.1
voxl-camera-calibration 0.6.1
voxl-camera-server 2.2.19
voxl-ceres-solver 2:2.0.0-2
voxl-configurator 1.1.5
voxl-cpu-monitor 0.7.7
voxl-docker-support 1.3.1
voxl-elrs 1.1.0
voxl-esc 1.5.7
voxl-esptool 0.2.0
voxl-feature-tracker 0.5.2
voxl-flow-server 0.3.6
voxl-gphoto2-server 0.0.10
voxl-imu-server 2.0.1
voxl-io-server 0.0.8
voxl-jpeg-turbo 2.1.3-7
voxl-lepton-server 1.3.3
voxl-lepton-tracker 0.0.4
voxl-libgeographic 1.0.0
voxl-libgphoto2 0.0.4
voxl-libuvc 1.0.7
voxl-logger 0.6.1
voxl-mavcam-manager 0.6.0
voxl-mavlink 0.1.6
voxl-mavlink-server 1.4.14
voxl-modem 1.2.3
voxl-mongoose 7.19.0
voxl-mpa-to-ros 0.3.9
voxl-mpa-tools 1.5.6
voxl-nano-tracker 0.1.7
voxl-open-vins-server 0.6.0
voxl-opencv 4.5.5-3
voxl-osd 0.3.8
voxl-portal 0.8.7
voxl-px4 1.14.0-2.0.133
voxl-px4-params 0.9.0
voxl-qvio-server 1.2.3
voxl-remote-id 0.0.9
voxl-reset-slpi 0.0.1
voxl-state-estimator 0.0.6
voxl-streamer 0.8.0
voxl-suite 1.6.3
voxl-tag-detector 0.1.0
voxl-tflite-server 0.5.1
voxl-utils 2.0.2
voxl-uvc-server 0.1.7
voxl-vision-hub 1.9.21
voxl-vtx 2.0.2
voxl-wavemux 0.0.3
voxl2-io 0.0.3
voxl2-security-hardening-utls 1.0-r0
voxl2-system-image 1.8.06-r0
voxl2-wlan 1.0-r0
────────────────────────────────────────────────────────────────────────────────
Services/Config (voxl-inspect-services)
voxl2-test-fixture (TF-M0054):/$ voxl-inspect-services
Scanning services...
Service Name | Enabled | Running | CPU Usage
───────────────────────────────────────────────────────────────────
docker-autorun | Disabled | Not Running |
modallink-relink | Disabled | Not Running |
voxl-camera-server | Enabled | Not Running |
voxl-cpu-monitor | Enabled | Running | 0.0%
voxl-dfs-server | Disabled | Not Running |
voxl-dma-latency | Enabled | Running |
voxl-feature-tracker | Disabled | Not Running |
voxl-flow-server | Disabled | Not Running |
voxl-imu-server | Enabled | Running | 3.8%
voxl-io-server | Disabled | Not Running |
voxl-lepton-server | Disabled | Not Running |
voxl-lepton-tracker | Disabled | Not Running |
voxl-logger | Disabled | Not Running |
voxl-mavcam-manager | Disabled | Not Running |
voxl-mavlink-server | Enabled | Running | 0.0%
voxl-mini-tof-server | Disabled | Not Running |
voxl-modem-doodle | Disabled | Not Running |
voxl-modem | Disabled | Not Running |
voxl-nano-tracker | Disabled | Not Running |
voxl-open-vins-server | Disabled | Not Running |
voxl-osd | Disabled | Not Running |
voxl-portal | Enabled | Running | 0.0%
voxl-px4 | Disabled | Not Running |
voxl-qvio-server | Disabled | Not Running |
voxl-rangefinder-server | Disabled | Not Running |
voxl-remote-id | Disabled | Not Running |
voxl-softap | Disabled | Not Running |
voxl-state-estimator | Disabled | Not Running |
voxl-static-ip-watcher | Disabled | Not Running |
voxl-static-ip | Disabled | Not Running |
voxl-streamer | Disabled | Not Running |
voxl-tag-detector | Disabled | Not Running |
voxl-tflite-server | Disabled | Not Running |
voxl-time-sync | Disabled | Not Running |
voxl-uvc-server | Disabled | Not Running |
voxl-vision-hub | Enabled | Running | 1.9%
voxl-vrx | Disabled | Not Running |
voxl-vtx | Disabled | Not Running |
voxl-wait-for-fs | Enabled | Completed |
I am doing some bench testing with my VOXL ESC FPV 4-in-1 and noticing significant motor desync. There is an audible 0.25 second delay between spinup of motor 1, then 2, etc. I have loaded the sentinel param XML file (I am using a custom aircraft, not the sentinel) to my ESC as a template and have only made one change; I set the motor KV to the value spec'd for my motors but I was getting this behavior prior to that change.
Any input would be greatly appreciated.
DSHOT Telemetry seems like the only option for the MadMotor ESC linked in the original post so that would be our requirement.
Hardware
Software Version (voxl-version)
voxl2-test-fixture (TF-M0054):/$ voxl-version
────────────────────────────────────────────────────────────────────────────────
system-image: 1.8.06-M0054-14.1a-perf
kernel: #1 SMP PREEMPT Wed Oct 22 04:13:18 UTC 2025 4.19.125
────────────────────────────────────────────────────────────────────────────────
hw platform: M0054
mach.var: 1.0.1
SKU: TF-M0054-4-V1-C11
────────────────────────────────────────────────────────────────────────────────
voxl-suite: 1.6.3
────────────────────────────────────────────────────────────────────────────────
Packages:
Repo: http://voxl-packages.modalai.com/ ./dists/qrb5165/sdk-1.6/binary-arm64/
Last Updated: 2023-03-02 12:58:39
List:
libfc-sensor 1.0.9
libmodal-cv 0.6.0
libmodal-exposure 0.1.4
libmodal-flow 1.0.3
libmodal-journal 0.2.7
libmodal-json 0.4.8
libmodal-pipe 2.14.11
libqrb5165-io 0.6.3
libvoxl-cci-direct 0.3.3
libvoxl-codec 0.0.2
libvoxl-cutils 0.1.6
modalai-slpi 1.2.2
mv-voxl 0.1-r0
qrb5165-bind 0.1-r0
qrb5165-dfs-server 0.2.0
qrb5165-mini-tof-server 0.2.2
qrb5165-rangefinder-server 0.1.6
qrb5165-slpi-test-sig 01-r0
qrb5165-tflite 2.17.2
voxl-bind-spektrum 0.1.1
voxl-camera-calibration 0.6.1
voxl-camera-server 2.2.19
voxl-ceres-solver 2:2.0.0-2
voxl-configurator 1.1.5
voxl-cpu-monitor 0.7.7
voxl-docker-support 1.3.1
voxl-elrs 1.1.0
voxl-esc 1.5.7
voxl-esptool 0.2.0
voxl-feature-tracker 0.5.2
voxl-flow-server 0.3.6
voxl-gphoto2-server 0.0.10
voxl-imu-server 2.0.1
voxl-io-server 0.0.8
voxl-jpeg-turbo 2.1.3-7
voxl-lepton-server 1.3.3
voxl-lepton-tracker 0.0.4
voxl-libgeographic 1.0.0
voxl-libgphoto2 0.0.4
voxl-libuvc 1.0.7
voxl-logger 0.6.1
voxl-mavcam-manager 0.6.0
voxl-mavlink 0.1.6
voxl-mavlink-server 1.4.14
voxl-modem 1.2.3
voxl-mongoose 7.19.0
voxl-mpa-to-ros 0.3.9
voxl-mpa-tools 1.5.6
voxl-nano-tracker 0.1.7
voxl-open-vins-server 0.6.0
voxl-opencv 4.5.5-3
voxl-osd 0.3.8
voxl-portal 0.8.7
voxl-px4 1.14.0-2.0.133
voxl-px4-params 0.9.0
voxl-qvio-server 1.2.3
voxl-remote-id 0.0.9
voxl-reset-slpi 0.0.1
voxl-state-estimator 0.0.6
voxl-streamer 0.8.0
voxl-suite 1.6.3
voxl-tag-detector 0.1.0
voxl-tflite-server 0.5.1
voxl-utils 2.0.2
voxl-uvc-server 0.1.7
voxl-vision-hub 1.9.21
voxl-vtx 2.0.2
voxl-wavemux 0.0.3
voxl2-io 0.0.3
voxl2-security-hardening-utls 1.0-r0
voxl2-system-image 1.8.06-r0
voxl2-wlan 1.0-r0
────────────────────────────────────────────────────────────────────────────────
Services/Config (voxl-inspect-services)
voxl2-test-fixture (TF-M0054):/$ voxl-inspect-services
Scanning services...
Service Name | Enabled | Running | CPU Usage
───────────────────────────────────────────────────────────────────
docker-autorun | Disabled | Not Running |
modallink-relink | Disabled | Not Running |
voxl-camera-server | Enabled | Not Running |
voxl-cpu-monitor | Enabled | Running | 0.0%
voxl-dfs-server | Disabled | Not Running |
voxl-dma-latency | Enabled | Running |
voxl-feature-tracker | Disabled | Not Running |
voxl-flow-server | Disabled | Not Running |
voxl-imu-server | Enabled | Running | 3.8%
voxl-io-server | Disabled | Not Running |
voxl-lepton-server | Disabled | Not Running |
voxl-lepton-tracker | Disabled | Not Running |
voxl-logger | Disabled | Not Running |
voxl-mavcam-manager | Disabled | Not Running |
voxl-mavlink-server | Enabled | Running | 0.0%
voxl-mini-tof-server | Disabled | Not Running |
voxl-modem-doodle | Disabled | Not Running |
voxl-modem | Disabled | Not Running |
voxl-nano-tracker | Disabled | Not Running |
voxl-open-vins-server | Disabled | Not Running |
voxl-osd | Disabled | Not Running |
voxl-portal | Enabled | Running | 0.0%
voxl-px4 | Disabled | Not Running |
voxl-qvio-server | Disabled | Not Running |
voxl-rangefinder-server | Disabled | Not Running |
voxl-remote-id | Disabled | Not Running |
voxl-softap | Disabled | Not Running |
voxl-state-estimator | Disabled | Not Running |
voxl-static-ip-watcher | Disabled | Not Running |
voxl-static-ip | Disabled | Not Running |
voxl-streamer | Disabled | Not Running |
voxl-tag-detector | Disabled | Not Running |
voxl-tflite-server | Disabled | Not Running |
voxl-time-sync | Disabled | Not Running |
voxl-uvc-server | Disabled | Not Running |
voxl-vision-hub | Enabled | Running | 1.9%
voxl-vrx | Disabled | Not Running |
voxl-vtx | Disabled | Not Running |
voxl-wait-for-fs | Enabled | Completed |
I am interested in integrating an FPV camera setup on my VOXL2-based aircraft. I am planning on using the USB3.0 / UART Expansion Adapter (link) to connect to an FRSKY OSD module via UART (link). I am in the process of executing this integration, but was looking for some technical guidance on how to get this working within the VOXL2 environment. Open to feedback on this approach if there is a more optimal way to go about doing this.
I am aware of this documentation (link) regarding integration of third party VTX, but I am just wanting to get input on any implementation details regarding OSD integration in the mix of this. I am using the FATSHARK aura VTX (link) and FPV camera (link)
Few caveats:
Thanks for passing my note along. Greatly appreciated.
The biggest thing we need out of DSHOT is the telemetry. At this point, or for a first pass, any way we can get telemetry from a third party ESC if fine. Even if we are still using PWM or OneShot.
A large part of my team's selection of your hardware was the small footprint we get by combining flight controller + companion computer on the same piece of silicon. If we move to a third party flight controller, we honestly may as well just move away from this ecosystem.
I am not afraid of getting into some more technical details with your development team on what it might look like for us to work on a DSHOT integration.
PS: As an aside, my team has a large order put in with your sales team that we have not heard back about in some time. Would you please pass along that we need a response on that? I have sent a follow up via your sales inquiry forum on the website with more information
Hi all, some questions about the VOXL ESC
Hardware
Software Version (voxl-version)
voxl2-test-fixture (TF-M0054):/$ voxl-version
────────────────────────────────────────────────────────────────────────────────
system-image: 1.8.06-M0054-14.1a-perf
kernel: #1 SMP PREEMPT Wed Oct 22 04:13:18 UTC 2025 4.19.125
────────────────────────────────────────────────────────────────────────────────
hw platform: M0054
mach.var: 1.0.1
SKU: TF-M0054-4-V1-C11
────────────────────────────────────────────────────────────────────────────────
voxl-suite: 1.6.3
────────────────────────────────────────────────────────────────────────────────
Packages:
Repo: http://voxl-packages.modalai.com/ ./dists/qrb5165/sdk-1.6/binary-arm64/
Last Updated: 2023-03-02 12:58:39
List:
libfc-sensor 1.0.9
libmodal-cv 0.6.0
libmodal-exposure 0.1.4
libmodal-flow 1.0.3
libmodal-journal 0.2.7
libmodal-json 0.4.8
libmodal-pipe 2.14.11
libqrb5165-io 0.6.3
libvoxl-cci-direct 0.3.3
libvoxl-codec 0.0.2
libvoxl-cutils 0.1.6
modalai-slpi 1.2.2
mv-voxl 0.1-r0
qrb5165-bind 0.1-r0
qrb5165-dfs-server 0.2.0
qrb5165-mini-tof-server 0.2.2
qrb5165-rangefinder-server 0.1.6
qrb5165-slpi-test-sig 01-r0
qrb5165-tflite 2.17.2
voxl-bind-spektrum 0.1.1
voxl-camera-calibration 0.6.1
voxl-camera-server 2.2.19
voxl-ceres-solver 2:2.0.0-2
voxl-configurator 1.1.5
voxl-cpu-monitor 0.7.7
voxl-docker-support 1.3.1
voxl-elrs 1.1.0
voxl-esc 1.5.7
voxl-esptool 0.2.0
voxl-feature-tracker 0.5.2
voxl-flow-server 0.3.6
voxl-gphoto2-server 0.0.10
voxl-imu-server 2.0.1
voxl-io-server 0.0.8
voxl-jpeg-turbo 2.1.3-7
voxl-lepton-server 1.3.3
voxl-lepton-tracker 0.0.4
voxl-libgeographic 1.0.0
voxl-libgphoto2 0.0.4
voxl-libuvc 1.0.7
voxl-logger 0.6.1
voxl-mavcam-manager 0.6.0
voxl-mavlink 0.1.6
voxl-mavlink-server 1.4.14
voxl-modem 1.2.3
voxl-mongoose 7.19.0
voxl-mpa-to-ros 0.3.9
voxl-mpa-tools 1.5.6
voxl-nano-tracker 0.1.7
voxl-open-vins-server 0.6.0
voxl-opencv 4.5.5-3
voxl-osd 0.3.8
voxl-portal 0.8.7
voxl-px4 1.14.0-2.0.133
voxl-px4-params 0.9.0
voxl-qvio-server 1.2.3
voxl-remote-id 0.0.9
voxl-reset-slpi 0.0.1
voxl-state-estimator 0.0.6
voxl-streamer 0.8.0
voxl-suite 1.6.3
voxl-tag-detector 0.1.0
voxl-tflite-server 0.5.1
voxl-utils 2.0.2
voxl-uvc-server 0.1.7
voxl-vision-hub 1.9.21
voxl-vtx 2.0.2
voxl-wavemux 0.0.3
voxl2-io 0.0.3
voxl2-security-hardening-utls 1.0-r0
voxl2-system-image 1.8.06-r0
voxl2-wlan 1.0-r0
────────────────────────────────────────────────────────────────────────────────
Services/Config (voxl-inspect-services)
voxl2-test-fixture (TF-M0054):/$ voxl-inspect-services
Scanning services...
Service Name | Enabled | Running | CPU Usage
───────────────────────────────────────────────────────────────────
docker-autorun | Disabled | Not Running |
modallink-relink | Disabled | Not Running |
voxl-camera-server | Enabled | Not Running |
voxl-cpu-monitor | Enabled | Running | 0.0%
voxl-dfs-server | Disabled | Not Running |
voxl-dma-latency | Enabled | Running |
voxl-feature-tracker | Disabled | Not Running |
voxl-flow-server | Disabled | Not Running |
voxl-imu-server | Enabled | Running | 3.8%
voxl-io-server | Disabled | Not Running |
voxl-lepton-server | Disabled | Not Running |
voxl-lepton-tracker | Disabled | Not Running |
voxl-logger | Disabled | Not Running |
voxl-mavcam-manager | Disabled | Not Running |
voxl-mavlink-server | Enabled | Running | 0.0%
voxl-mini-tof-server | Disabled | Not Running |
voxl-modem-doodle | Disabled | Not Running |
voxl-modem | Disabled | Not Running |
voxl-nano-tracker | Disabled | Not Running |
voxl-open-vins-server | Disabled | Not Running |
voxl-osd | Disabled | Not Running |
voxl-portal | Enabled | Running | 0.0%
voxl-px4 | Disabled | Not Running |
voxl-qvio-server | Disabled | Not Running |
voxl-rangefinder-server | Disabled | Not Running |
voxl-remote-id | Disabled | Not Running |
voxl-softap | Disabled | Not Running |
voxl-state-estimator | Disabled | Not Running |
voxl-static-ip-watcher | Disabled | Not Running |
voxl-static-ip | Disabled | Not Running |
voxl-streamer | Disabled | Not Running |
voxl-tag-detector | Disabled | Not Running |
voxl-tflite-server | Disabled | Not Running |
voxl-time-sync | Disabled | Not Running |
voxl-uvc-server | Disabled | Not Running |
voxl-vision-hub | Enabled | Running | 1.9%
voxl-vrx | Disabled | Not Running |
voxl-vtx | Disabled | Not Running |
voxl-wait-for-fs | Enabled | Completed |
Integration with Third Party ESC
This is a follow up to a previous post (link) regarding supported ESC hardware with the VOXL2. As directed by @vinny in that previous post, I am breaking out this follow up as its own topic.
I am looking to integrate this 12S ESC from Mad Motor (link) for my project. For now, I am open to using the VOXL IO expander (link) to do this integration via PWM/ONESHOT with BLHELI32 firmware but I am finding the lack of DSHOT support in the VOXL ecosystem a real road block for future project development with this product.
What I am particularly interested in is guidance on what it would take to get a DSHOT implementation working in the VOXL ecosystem. Is there a technical reason why this has not yet been implemented? If there are no plans for the Modal team to implement this, is this something I could attempt via the VOXL2 SDK?
Any guidance is much appreciated.
Thanks!
@vinny
Awesome! Thanks. I will follow your guidance and make a new post with the ESC I'd like to use (once I make that selection).
Helpful, as always. Much appreciated!
Hi all, some questions about the VOXL ESC
Hardware
Software Version (voxl-version)
voxl2-test-fixture (TF-M0054):/$ voxl-version
────────────────────────────────────────────────────────────────────────────────
system-image: 1.8.06-M0054-14.1a-perf
kernel: #1 SMP PREEMPT Wed Oct 22 04:13:18 UTC 2025 4.19.125
────────────────────────────────────────────────────────────────────────────────
hw platform: M0054
mach.var: 1.0.1
SKU: TF-M0054-4-V1-C11
────────────────────────────────────────────────────────────────────────────────
voxl-suite: 1.6.3
────────────────────────────────────────────────────────────────────────────────
Packages:
Repo: http://voxl-packages.modalai.com/ ./dists/qrb5165/sdk-1.6/binary-arm64/
Last Updated: 2023-03-02 12:58:39
List:
libfc-sensor 1.0.9
libmodal-cv 0.6.0
libmodal-exposure 0.1.4
libmodal-flow 1.0.3
libmodal-journal 0.2.7
libmodal-json 0.4.8
libmodal-pipe 2.14.11
libqrb5165-io 0.6.3
libvoxl-cci-direct 0.3.3
libvoxl-codec 0.0.2
libvoxl-cutils 0.1.6
modalai-slpi 1.2.2
mv-voxl 0.1-r0
qrb5165-bind 0.1-r0
qrb5165-dfs-server 0.2.0
qrb5165-mini-tof-server 0.2.2
qrb5165-rangefinder-server 0.1.6
qrb5165-slpi-test-sig 01-r0
qrb5165-tflite 2.17.2
voxl-bind-spektrum 0.1.1
voxl-camera-calibration 0.6.1
voxl-camera-server 2.2.19
voxl-ceres-solver 2:2.0.0-2
voxl-configurator 1.1.5
voxl-cpu-monitor 0.7.7
voxl-docker-support 1.3.1
voxl-elrs 1.1.0
voxl-esc 1.5.7
voxl-esptool 0.2.0
voxl-feature-tracker 0.5.2
voxl-flow-server 0.3.6
voxl-gphoto2-server 0.0.10
voxl-imu-server 2.0.1
voxl-io-server 0.0.8
voxl-jpeg-turbo 2.1.3-7
voxl-lepton-server 1.3.3
voxl-lepton-tracker 0.0.4
voxl-libgeographic 1.0.0
voxl-libgphoto2 0.0.4
voxl-libuvc 1.0.7
voxl-logger 0.6.1
voxl-mavcam-manager 0.6.0
voxl-mavlink 0.1.6
voxl-mavlink-server 1.4.14
voxl-modem 1.2.3
voxl-mongoose 7.19.0
voxl-mpa-to-ros 0.3.9
voxl-mpa-tools 1.5.6
voxl-nano-tracker 0.1.7
voxl-open-vins-server 0.6.0
voxl-opencv 4.5.5-3
voxl-osd 0.3.8
voxl-portal 0.8.7
voxl-px4 1.14.0-2.0.133
voxl-px4-params 0.9.0
voxl-qvio-server 1.2.3
voxl-remote-id 0.0.9
voxl-reset-slpi 0.0.1
voxl-state-estimator 0.0.6
voxl-streamer 0.8.0
voxl-suite 1.6.3
voxl-tag-detector 0.1.0
voxl-tflite-server 0.5.1
voxl-utils 2.0.2
voxl-uvc-server 0.1.7
voxl-vision-hub 1.9.21
voxl-vtx 2.0.2
voxl-wavemux 0.0.3
voxl2-io 0.0.3
voxl2-security-hardening-utls 1.0-r0
voxl2-system-image 1.8.06-r0
voxl2-wlan 1.0-r0
────────────────────────────────────────────────────────────────────────────────
Services/Config (voxl-inspect-services)
voxl2-test-fixture (TF-M0054):/$ voxl-inspect-services
Scanning services...
Service Name | Enabled | Running | CPU Usage
───────────────────────────────────────────────────────────────────
docker-autorun | Disabled | Not Running |
modallink-relink | Disabled | Not Running |
voxl-camera-server | Enabled | Not Running |
voxl-cpu-monitor | Enabled | Running | 0.0%
voxl-dfs-server | Disabled | Not Running |
voxl-dma-latency | Enabled | Running |
voxl-feature-tracker | Disabled | Not Running |
voxl-flow-server | Disabled | Not Running |
voxl-imu-server | Enabled | Running | 3.8%
voxl-io-server | Disabled | Not Running |
voxl-lepton-server | Disabled | Not Running |
voxl-lepton-tracker | Disabled | Not Running |
voxl-logger | Disabled | Not Running |
voxl-mavcam-manager | Disabled | Not Running |
voxl-mavlink-server | Enabled | Running | 0.0%
voxl-mini-tof-server | Disabled | Not Running |
voxl-modem-doodle | Disabled | Not Running |
voxl-modem | Disabled | Not Running |
voxl-nano-tracker | Disabled | Not Running |
voxl-open-vins-server | Disabled | Not Running |
voxl-osd | Disabled | Not Running |
voxl-portal | Enabled | Running | 0.0%
voxl-px4 | Disabled | Not Running |
voxl-qvio-server | Disabled | Not Running |
voxl-rangefinder-server | Disabled | Not Running |
voxl-remote-id | Disabled | Not Running |
voxl-softap | Disabled | Not Running |
voxl-state-estimator | Disabled | Not Running |
voxl-static-ip-watcher | Disabled | Not Running |
voxl-static-ip | Disabled | Not Running |
voxl-streamer | Disabled | Not Running |
voxl-tag-detector | Disabled | Not Running |
voxl-tflite-server | Disabled | Not Running |
voxl-time-sync | Disabled | Not Running |
voxl-uvc-server | Disabled | Not Running |
voxl-vision-hub | Enabled | Running | 1.9%
voxl-vrx | Disabled | Not Running |
voxl-vtx | Disabled | Not Running |
voxl-wait-for-fs | Enabled | Completed |
Questions
@vinny @alex-kushleyev @tom
Thanks for the input guys! Happy to report it is all working as intended. Much appreciated.
Okay, so after tinkering a bit yesterday, I've been unable to figure out the aux button mapping process. Could you kind of walk through a step by step on what exactly I need to configure? I think what I am most confused on is what on my RadioMaster GX12 transmitter counts as an "AUX button". I initially though the 1-6 buttons, but those all seem bound to flight modes so I am not really sure.
Appreciative of your help!
Thanks for your reply. I ended up just writing a small bash script to toggle the pad. I then probed all the exposed pads on the ESC in order to find which one was toggling battery voltage, so I did discover the correct pads as you have circled above. If you're open to the suggestion, I might make this more explicit in the documentation is it is not very obvious at first read. Maybe including the above picture would suffice since there's no labeling in the docs or on the silkscreen that makes this explicit.
My battery voltage is 6S. I do have concerns about the total current draw being capped at 500mA. My VTX module pulls 500mA at baseline, and I've observed in the field it pulling up to 600mA when transmitting at full power. I will have to rethink my harness design if I am truly limited to only 500mA.
I am going to attempt the PX4 integration using my hand controller and will report back if I have troubles. If you do have any notes on how to set that all up please do let me know.
Again, very appreciative of your reply. Thanks!
Update:
I did find this (link) old post on the forums from 2024. From what I can gather, the voxl-esc-gpio.py command is supposed to be configured to toggle the AUX power pad on the ESC. However, even though I am running the script with the --val flag alternating between 0 and 1, I see 3.3V on that pad at all times. Maybe I have something incorrectly configured here? The 3.3V reading is confusing because per the previous forum discussion this script is supposed to be for VTX power, but I would expect a VTX power source to be battery voltage per the documentation
Currently, I'm just trying to test this in the CLI right now. I am eventually wanting this to work concurrently with PX4.
Hi all,
Looking for guidance on wiring my FatShark Aura Analog VTX module to my FPV 4in1 ESC. I would like to take advantage of the software defined power switching mentioned in the datasheet, however, it is unclear to me where exactly on the ESC I need to solder my leads to in order to use this feature.
Please advise. Thanks!
For reference (link to datasheet) :

@Eric-Katzfey
Yes sir. I think I see now what you are suggesting. Is it fair to say that any application trying to do anything with Mavlink on this system must do so over UDP connection to the voxl-mavlink-server? I think I was operating on some incorrect base assumptions. My apologies! Greatly appreciative of your help.
@Eric-Katzfey
Thanks for your reply! I am not attempting to establish communication via UART. I have already successfully been communicating the the FC/PX4 via WiFi, ethernet, and USB-C through the ADB shell (link). What I am talking about doing in my post is fundamentally different. I have an ELRS receiver plugged into J19 on the VOXL2. As mentioned in the above post, I have verified that the ELRS receiver/transmitter works for RC inputs over CRSF.
What I am trying to get working now is using the transmitter for QGC connection. This is possible on other flight controllers by connecting to the transmitter's local WiFi or via USB, but this does not seem to be working in the same way for the VOXL2. I imagine I am missing a specific configuration option or setting somewhere, or maybe this just isn't possible since Mavlink seems to be only communicated via UDP on this device. That is what I am looking for clarity on.
Hi all,
Here is my setup:
What I would like to do is connect to QGC via the transmitter. However, I am unsure how to go about doing this or if it is even possible on the VOXL2. I've successfully established RC with the FC in CRSF link mode; I can see the stick inputs updating when connected to QGC via USB-C.
On other flight controllers, I have been able to establish transmitter/QGC connection by putting the transmitter in "Mavlink" mode and connecting to the transmitter WiFi. This does not seem to be working with my VOXL2. I've tried changing the /etc/modalai/voxl-px4.conf "RC" setting to "external" and "crsf_mav" and neither seems to work (maybe I'm missing something).
Any help would be greatly appreciated. Happy to provide more information as needed.