Skip to content

Ask your questions right here!

2.4k Topics 11.7k Posts

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

Subcategories


  • 167 Topics
    757 Posts
    Colby HowellC
    Hello. I purchased a Starling 2 Max development drone and when attempting a first flight test I discovered that one of the batteries arrived entirely dead. I was curious if there was a way to receive replacements, and if this falls within replacement territory. I contacted the support email and was directed here. I can provide more information if needed.
  • 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]
  • voxl-dfs-server running but no disparity shows in voxl-portal

    1
    4
    0 Votes
    1 Posts
    358 Views
    No one has replied
  • VOXL2 Compute schematics

    1
    0 Votes
    1 Posts
    291 Views
    No one has replied
  • This topic is deleted!

    3
    0 Votes
    3 Posts
    32 Views
  • Incoherence in the vi extrinsics.conf for my m500

    1
    3
    0 Votes
    1 Posts
    434 Views
    No one has replied
  • VOXL2 px4 ESC config with QGroundControl

    11
    0 Votes
    11 Posts
    2k Views
    Eric KatzfeyE
    @Benjamin-Ruks This shows that GPS has been selected as NONE so it won't try to set up the LED, magnetometer, or GPS. That will have to be changed to HOLYBRO. You can directly modify the file /etc/modalai/voxl-px4.conf to change that value.
  • launching scripts from profile.d

    1
    0 Votes
    1 Posts
    270 Views
    No one has replied
  • m500 vio

    3
    0 Votes
    3 Posts
    512 Views
    José QuintanillaJ
    @Chad-Sweet Hi Chad, I think I am into a trouble similar to Wenxi LiU. It appears to me that qvio server is enable and running but, when trying to check odometry in QGC or even with voxl-inspect-qvio, all the T_imu_wrt_vio(m) data is in 0 even when moving the drone. In QGC it appears the XY coordinates are in absolute 0 and Z with an offset os 10 meter, it appears to be a -10.9 coordinate while it hasn't moved at all. I tried to open the link you attached to the answer but the page is down. Is it another page or someone that could help me to troubleshoot this problem? Regards,
  • qvio server says low features

    2
    2
    0 Votes
    2 Posts
    585 Views
    Chad SweetC
    Please refer to the troubleshooting documentation https://docs.modalai.com/flying-with-vio/#troubleshooting-vio
  • OV7251 vs. OV9782 sensor

    3
    0 Votes
    3 Posts
    623 Views
    E
    @Chad-Sweet thanks. Is there also a datasheet doc for M0113?
  • Information on creating a custom expansion PCB

    2
    0 Votes
    2 Posts
    1k Views
    Chad SweetC
    You can find the document here https://docs.modalai.com/expansion-design-guide/
  • VOXL2 GPIO Pin Layout

    1
    0 Votes
    1 Posts
    327 Views
    No one has replied
  • VOXL2 ESC calibration using VOXL2 IO board and m500 frame

    3
    0 Votes
    3 Posts
    688 Views
    J
    @Chad-Sweet Hey Chad! Yes 100% I'm open to the PC tools to get it done as well. I suppose I'm a bit uncertain about the hardware pipeline in this case. I'll want to have the traditional m500 ESC and motor, so I'll need to generate the PWM calibration curve somehow and generate the correct parameters. Should I use a surrogate m500 VOXL1 board to just get the values and run with those? -Joe
  • April Tag Relocalization with External Fight Controller

    3
    0 Votes
    3 Posts
    746 Views
    A
    To conclude this post in the hope to help someone else who's having the same problem, I found this reply on another question in this forum which dates back to 2021. I guess the Relocalization still works only in Offboard and NOT in Mission. The same applies for an external flight controller e.g. in Ardupilot it works in Guided Mode and NOT in Auto.
  • voxl-camera-server sudendly crash m500

    1
    3
    1 Votes
    1 Posts
    421 Views
    No one has replied
  • Starling 2 Inverted Yaw and Pitch

    2
    -1 Votes
    2 Posts
    803 Views
    James StrawsonJ
    @Kashish-Garg-0 Yes, everything in the aerospace industry including PX4 and ardupilot use the standard NED coordinate frame with Z pointing down. A significant portion of the code in MAVROS seems to be flipping the direction of the Y and Z axis back and forth when converting from mavlink to ros topics. I suggest using the vvhub_body_wrt_local pipe instead of the qvio pipe as the qvio data is centered around the imu whereas voxl-vision-hub transforms this to be centered around the body (COG) and corrects for gravity alignment. You can inspect the local pose on VOXL natively with voxl-inspect-pose vvhub_body_wrt_local OR voxl-inspect-pose --local Note this pipe was called vvpx4_body_wrt_local in SDK0.9 and older. I don't think ROS libraries like TF2 care which way gravity points. A transform is a transform, you can have it oriented however you prefer when you do your math. You should only need to change coordinate frames for the sake of visualization if RVIS doesn't let you define a default orientation or rotate the ground plane around in the UI.
  • RB5 Flight Replacement ESC version?

    2
    0 Votes
    2 Posts
    541 Views
    tomT
    @Sam-Kiley You'll want the standard M0117
  • This topic is deleted!

    2
    0 Votes
    2 Posts
    9 Views
  • My m500 doesn't connect to qground control

    9
    3
    0 Votes
    9 Posts
    1k Views
    José QuintanillaJ
    @tom Thanks, I will try it
  • VIO "Q" (quality) metric and distant features

    2
    0 Votes
    2 Posts
    515 Views
    Chad SweetC
    The code where quality is computed can be found here: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-qvio-server/-/blob/master/server/quality.h
  • VOXL Calibrate Stereo Camera

    2
    1
    0 Votes
    2 Posts
    613 Views
    Chad SweetC
    Your sensors need to be mounted co-planar and rigidly like you see in our drone and flight deck products