Skip to content
Brand Logo

ModalAI Forum
  1. ModalAI Support Forum
  2. Ask your questions right here!

Ask your questions right here!

2.3k Topics 11.7k Posts

Note sure where to post? Ask questions here for direct access to the ModalAI engineering team

Subcategories

  • 164 751
    164 Topics
    751 Posts
    Ben LinneB
    @heiko.lizan Any elrs radio that's 900mhz or dual band compatible should work when in low band mode. If the transmitter is running v4+ you should be able to downgrade it to v3 following the elrs update guide It's normal that some services aren't running. You may need to re-enable px4 with systemctl enable voxl-px4

  • Do you have a great idea for our products you would like to see implemented?

    27 90
    27 Topics
    90 Posts
    Serhii RovnyiS
    Hello everyone, I am looking for some expert advice on a VOXL 2 companion computer setup for a long-range platform. I have two main integration challenges: Challenge A: VIO at Higher Altitudes To solve the motion blur and pixel density issues at higher altitudes, I am planning a 6-camera configuration. I want to use 4 downward-facing sensors (2 daylight + 2 IR) equipped with narrow-angle lenses, alongside 2 standard wide-angle sensors (front and rear). Could you advise on the best supported sensors (e.g., IMX series) for this? Has anyone successfully tuned the voxl-qvio-server for narrow-angle lenses, and what were the altitude limits you achieved? Challenge B: LAN Integration & WireGuard The payload data flow will be: External RTSP Camera -> Ethernet -> VOXL 2 (WireGuard encryption) -> Ethernet -> Digital RX. Because VOXL 2 lacks multiple LAN ports, I will need a miniature industrial Ethernet switch. Does ModalAI have any tested hardware recommendations for this? Furthermore, what is the best practice for routing this VPN traffic through the VOXL 2 Ubuntu environment without bottlenecking the CPU? We are currently evaluating the VOXL 2 for a broader fleet deployment and want to ensure the ecosystem can support this custom optics requirement. Any feedback on off-the-shelf solutions or standard configurations for this use case would be greatly appreciated. Thank you!

  • Are you looking for a 3D model of one of our products?

    33 86
    33 Topics
    86 Posts
    Alex KushleyevA
    @nl_vdi , if you log into developer.modalai.com, you will see the CAD models. the latest model we have is: D0012-4-V3-C28-M36-T7-K0-Starling2-Max-V3-20260317.step [image: 1781036132877-376bf0dd-494a-4bf1-8d92-1b2d91afb83d-image.png]
  • KnightHawk06K

    Processing point cloud data

    1
    1
    0 Votes
    1 Posts
    327 Views
    No one has replied
  • S

    Immediate crashes in HITL

    12
    0 Votes
    12 Posts
    2k Views
    S
    @Eric-Katzfey Okay, I'll keep this in mind as I develop toward offboard control. If I find any more information, I'll follow up here. Just a side note: I don't see this behavior in real-world flight during manual or position, seems to be isolated to HITL at this point in time. Thanks!
  • S

    Doodle Labs mini-OEM Helix Mesh Rider Radio M1-M6 Hex Band not configuring

    doodlelabs
    8
    0 Votes
    8 Posts
    3k Views
    S
    @Vinny Really appreciate the in-depth response and thoughtfulness, your intuition was correct I tried to reproduce the setup from the windows PC Wall power supply to Starling 2 (Same mains outlet) 12VAC to 5VDC to doodle labs radio Twisted D-/+ cables Upon USB connection, I'm able to see the following on dmesg -w: [ 1156.696173] usb 1-1: new high-speed USB device number 6 using xhci-hcd [ 1156.832876] usb 1-1: New USB device found, idVendor=0424, idProduct=9e00, bcdDevice= 3.00 [ 1156.832886] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 1156.848011] smsc95xx v1.0.6 [ 1156.912009] smsc95xx 1-1:1.0 eth0: register 'smsc95xx' at usb-xhci-hcd.0.auto-1, smsc95xx USB 2.0 Ethernet, 00:30:1a:3a:eb:c8 [ 1156.981572] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 1156.989474] QTI:Netlink Query to Kernel Success [ 1158.456775] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 1158.464411] QTI:LINK_UP message posted [ 1158.465167] QTI:Processing LINK_UP [ 1158.465606] smsc95xx 1-1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1 [ 1158.472660] QTI:Enable mobileap [ 1158.479629] QCMAP:Enable mobileap [ 1158.598399] QCMAP:Enable mobileap done [ 1158.602320] QTI:Setup TETHERED link [ 1158.676632] QTI:LINK_UP Processed and am able to stream data via voxl portal for a few seconds. Afterwards, the USB connection goes into a repeated disconnect/reconnect cycle. Moving forward for next testing (and obviously final configuration), I'll power both from the same source (w/ a BEC), shorten the cables, and be sure to twist the data lines (similar to mcbl-0085)
  • h3roboticsH

    mavlink peripherals

    5
    0 Votes
    5 Posts
    816 Views
    Eric KatzfeyE
    @h3robotics I've been using v2.5 on my development machine and it works fine so v2.7 should also be fine. (Dang, I need to update )
  • G

    VOXL Flight Deck Bricked - Unable to Connect via ADB or WiFi

    voxl-flight wifi bricked
    1
    0 Votes
    1 Posts
    809 Views
    No one has replied
  • V

    m0076 / VOXL 2

    4
    3
    0 Votes
    4 Posts
    462 Views
    No one has replied
  • S

    VOXL 2 Mini not booting...LEDs on and whirring noise

    3
    0 Votes
    3 Posts
    483 Views
    VinnyV
    Hi @serviceberry I happened to stumble on your post here, sorry it looks like no one ever responded to you. Is your HW still in error? Can you confirm how you are powering the VOXL 2 mini, and if anything changed before this issue? The two ICs you show that are smoking hot are interesting. The one at 156C is the level translator for our I2C bus on the power connector. Are you sure you have pins 1 and 2 as power, and not pins 3 & 4? If pins 3 & 4 were accidentally used to power the VOXL 2 Mini, this chip would indeed see the brunt of that issue. The other chip heating up may just be secondary due to the other failure since that chip is downstream of this one for powering the board from the voltage impacted. Looking forward to your response and sorry again no one responded (or did you submit a second case??) Thanks!
  • M

    Starling 2 Max Dead Reckoning

    1
    0 Votes
    1 Posts
    333 Views
    No one has replied
  • N

    Heavy drift on VOXL 2

    6
    0 Votes
    6 Posts
    1k Views
    astro_philA
    @astro_phil with some further investigation over the weekend, i found a small fix in the px4 codebase that seems to reduce the velocity estimation error. I low pass filtered the delta time (dt) value that is used to integrate the linear acceleration to obtain the velocity estimate. [image: 1746443064707-vibration_fix-resized.png] Left is without the "fix" and right is with the "fix". Flying in position hold. [image: 1746443272985-whatsapp-image-2025-05-03-at-15.50.57.jpeg] I tried to induce more vibration on purpose to test the impact on position tracking. Both flights shown in the plot where done with the system shown in the picture.
  • T

    Starling 2 Max endurance & Propulsion system

    1
    0 Votes
    1 Posts
    336 Views
    No one has replied
  • W

    SYS_AUTOSTART param missing, shown in QGC, after flashing the flight deck with voxl2_SDK_1.4.1

    11
    1
    0 Votes
    11 Posts
    1k Views
    W
    @Eric-Katzfey From other discussion, I add qshell gps start -d 7 -b 115200 and get the GPS now. Here is my setting and please let me know if any questions. Thank you for your precious time on this matter. AIRFRAME=MULTICOPTER GPS=AUTODETECT RC=CRSF_RAW ESC=VOXL_ESC POWER_MANAGER=VOXLPM AIRSPEED_SENSOR=NONE DISTANCE_SENSOR=NONE OSD=DISABLE DAEMON_MODE=ENABLE SENSOR_CAL=ACTUAL ARTIFACT_MODE=DISABLE EXTRA_STEPS=( qshell gps start -d 7 -b 115200 )
  • S

    no data being piped thru /run/mpa/tflite_data

    2
    0 Votes
    2 Posts
    404 Views
    Alex KushleyevA
    @ssansoy , you cannot access the data from these pipes directly, you have to use the MPA mechanisms to do that. There is an example of doing that for tflite detections right here : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-tools/-/blob/master/tools/voxl-inspect-detections.c and the compiled app should also be present in the SDK, so you can run it on your VOXL2 (voxl-inspect-detections). Alex
  • Yoshimaru TanakaY

    [Starling2] The devices are recognized as /dev/video* but no assigned as the device available in the voxl system

    9
    2
    0 Votes
    9 Posts
    1k Views
    Alex KushleyevA
    @Yoshimaru-Tanaka , you are right, the information in the documentation is not sufficient to diagnose this issue. There is a page already for camera debugging information, but it is very brief. We will add more details (from this thread and more) to this page. https://docs.modalai.com/debugging-camera-issues/ Thank you Alex
  • Jetson NanoJ

    microhard integration with voxl2, not able to get the data.

    10
    3
    0 Votes
    10 Posts
    1k Views
    tomT
    @Jetson-Nano We have never used Microhard on windows but it's possible your firewall is blocking UDP data on that port
  • KnightHawk06K

    Country of origin for stereo camera

    1
    0 Votes
    1 Posts
    310 Views
    No one has replied
  • Simen HusøyS

    SPIR-V on Voxl 2 Mini

    1
    0 Votes
    1 Posts
    215 Views
    No one has replied
  • N

    VOXL 1 - Seeker Drone Setup with QGC

    voxl seeker qgc
    2
    1
    0 Votes
    2 Posts
    1k Views
    N
    Also this is what I was getting when inspecting the mavlink server. 00:19:39.969721 IP 192.168.1.1. domain > 192.168.1.134. 40850: 5282 Refused 0/0/0 (42) 00:19:39.970315 IP 192.168.1.134.48451 > 192.168.1.1. domain: 5282+ PTR? 1.1.168.192. in-addr • arpa. (42) 00: 19:39.973637 IP 192.168.1.1. domain > 192.168.1.134.48451: 5282 Refused 0/0/0 (42) 00:19:40. 106351 IP 192.168.1.138.14550 > 192.168.1.134.14550: UDP, length 21 00:19:41. 068099 IP 192.168.1.138.14550 > 192.168.1.134.14550: UDP, length 21 00:19:41.553204 ARP, Request who-has 192.168.1.1 tell 192.168.1.134, length 28 00:19:41.553488 ARP, Request who-has 192.168.1.138 tell 192.168.1.134, length 28 00:19:41.558414 ARP, Reply 192.168.1.1 is-at 80:69:1a:06:84:4e (oui Unknown), length 28 00:19:41.561634 ARP, Reply 192.168.1.138 is-at 34:c9:3d:07:16:8d (oui Unknown), length 28 00:19:42. 065376 IP 192.168.1.138.14550 > 192.168.1.134.14550: UDP, length 21 00:19:43.070712 IP 192.168.1.138.14550 > 192.168.1.134.14550: UDP, Length 21 00:19:44.075718 IP 192.168.1.138.14550 > 192.168.1.134.14550: UDP, length 21 00:19:45. 064630 IP 192.168.1.138.14550 > 192.168.1.134.14550: UDP, length 21 00:19:46.062935 IP 192.168.1.138.14550 > 192.168.1.134.14550: UDP, Length 21 00: 19:47. 107960 IP 192.168.1.138.14550 > 192.168.1.134.14550: UDP, length 21
  • Jetson NanoJ

    M0173 dual tracking camera error

    12
    0 Votes
    12 Posts
    1k Views
    Jetson NanoJ
    @Alex-Kushleyev, I using voxl2 with M0173 board with camera config 29. The errors are now solved, I made the necessary changes and reconfigured every server and pipeline and calibrated the cameras.
  • KnightHawk06K

    algorithm for voxl-dfs-server depth estimation

    2
    0 Votes
    2 Posts
    434 Views
    Alex KushleyevA
    @KnightHawk06 , DFS on VOXL2 uses the Qualcomm's proprietary implementation of the DFS algorithm, which runs on the specialized DSP (CVP - Computer Vision Processor). Unfortunately we do not have any details about the actual algorithm. Alex
  • G

    (VOXL2 PX4 ROS2) px4_msgs Unrecognized In Program

    5
    1
    0 Votes
    5 Posts
    768 Views
    G
    @Zachary-Lowell-0 Yes I installed voxl-ros2-foxy. This time I just tried "source /opt/ros/foxy/mpa_to_ros2/install/setup.bash" and that was accepted. However, looking now px4_msgs is still not recognized within my program. [image: 1745358768903-73d768a7-bab0-42d9-b73e-b4e84749294a-image.png]