Skip to content
Brand Logo

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

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 757
    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]
  • G

    Hires Camera

    1
    0 Votes
    1 Posts
    467 Views
    No one has replied
  • J

    TOF Sensor Range

    1
    0 Votes
    1 Posts
    509 Views
    No one has replied
  • Shlok AgarwalS

    New image not installing waiting for fastboot

    2
    1
    0 Votes
    2 Posts
    356 Views
    tomT
    @Shlok-Agarwal I assume you've taken a look at this page in our docs: https://docs.modalai.com/unbrick-voxl/ If not, give that a read through and it'll give you a bunch of good info. Were you able to ADB into the VOXL before you started the flashing process?
  • ryan_meagherR

    Setting up network interfaces

    7
    1 Votes
    7 Posts
    2k Views
    Eric KatzfeyE
    @Nirge You should use voxl-wifi for wlan0.
  • D

    Invalid local position

    30
    0 Votes
    30 Posts
    10k Views
    A
    I found the QGC EKF2_AID_MASK parameter settings above (configuring to 280: Vision position fusion, vision yaw fusion, vision velocity fusion) to allow the seeker to enter position and off-board modes. Prior to configuring, QGC was receiving VIO but was still unable to enter position mode as referenced here To make the forum search engine happy: seeker position mode rejected
  • John MccartyJ

    Change Pwm channel

    8
    0 Votes
    8 Posts
    2k Views
    modaltbM
    Alright! Thanks for the update, I'll likely use this post to get some updates to our docs, appreciate it!
  • A

    Voxl-mapper instructions

    2
    0 Votes
    2 Posts
    551 Views
    ?
    Hello @alarm_hq! Please see the updated readme on voxl-mapper's dev branch for an overview guide of this package. As for the timestamp too new error, this error typically arises when there is a VIO blowup, and one way to prevent this is by ensuring that the tracking camera is correctly calibrated pre-flight. Also, please see the overview guide for instructions on viewing, as RVIZ is no longer utilized!
  • modaltbM

    This topic is deleted!

    2
    0 Votes
    2 Posts
    3 Views
  • Michael BarrowM

    Unable to run example TFlite model in emulator docker image

    3
    0 Votes
    3 Posts
    531 Views
    Michael BarrowM
    Thanks, so what is the emulator for exactly? emulating native compilation? I am unclear of the emulator use case if it is not intended to emulate the voxl platform for application testing. Let me know, cheers!
  • A

    Seeker replacement props

    2
    0 Votes
    2 Posts
    582 Views
    ?
    Hey @alarm_hq! The props for the Seeker development drone can be found here.
  • A

    How to: Seeker ESC calibration

    9
    0 Votes
    9 Posts
    2k Views
    James StrawsonJ
    @alarm_hq said in How to: Seeker ESC calibration: And if I've already made the "mistake" of reflashing px4 firmware, is the closed loop RPM control affected? The ModalAI ESCs used on Seeker have their own firmware and settings stored on the ESC itself, independent from PX4 so your ESC is fine after changing PX4 firmware.
  • T

    Unstable Seeker after flashing

    6
    0 Votes
    6 Posts
    1k Views
    T
    Thanks Chad. We did the calibration again with a better calibration target, and this fixed the problem.
  • Prasobh PP

    hires Camera for barcode

    2
    0 Votes
    2 Posts
    471 Views
    Chad SweetC
    Have you looked at voxl-tag-detector?
  • R

    voxl-uart-loopback problems

    2
    1
    0 Votes
    2 Posts
    500 Views
    Alex KushleyevA
    Hello, There were a few issues with the uart loopback example: the test buffer size was not handled properly (if test size is larger than HelloWorld strin the sleep time was not enough to allow the transfer to happen (the write function is non-blocking, it seems) I have made some fixes here: https://gitlab.com/voxl-public/core-libs/libvoxl_io/-/blob/dev/lib/apps/voxl-uart-loopback.c Now the behavior is as shown below.. please try it. ./voxl-uart-loopback -d 7 -b 9600 -s 20 INITIALIZING Sending 20 bytes: 0123456789:;<=>?@ABC Transfer should take ~20833us, sleeping for 25833us (+5000us overhead) Reading back data... Received 20 bytes: 0123456789:;<=>?@ABC closing uart bus PASS ./voxl-uart-loopback -d 7 -b 9600 -s 500 INITIALIZING Sending 500 bytes: 0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789:;<=>?@ABCDEFGHIJ Transfer should take ~520833us, sleeping for 525833us (+5000us overhead) Reading back data... Received 500 bytes: 0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789:;<=>?@ABCDEFGHIJ closing uart bus PASS
  • Prasobh PP

    hires camera issue

    2
    1
    0 Votes
    2 Posts
    465 Views
    ?
    Hi Prasobh, It looks like rosnode got an invalid metadata when reading from the hires camera pipe. This is an uncommon issue and should really only occur if the CPU is overloaded and starts throttling the client reading the camera images, eventually overflowing the camera pipe, thus getting out of sync. Additionally, it says that the data pipe disconnected, possibly indicating a problem with voxl-camera-server. If this occurs again, checking the logs with journalctl -u voxl-camera-server may provide some useful information as to what issue may have occurred on the hardware side.
  • J

    Dual Camera Adapter

    2
    0 Votes
    2 Posts
    622 Views
    Chad SweetC
    That cable was posted as a mistake, it is now deleted. You can stream any sensor connected to QGC. This doc here articulates all of the possible connections
  • J

    USB to Ethernet Adapter

    4
    0 Votes
    4 Posts
    958 Views
    tomT
    Interesting, can you post a picture of the hardware setup you are attempting to use that isn’t working?
  • M

    is it possible to run the VIO processing offboard, rather than on the VOXL Cam?

    2
    0 Votes
    2 Posts
    457 Views
    Chad SweetC
    The VOXL platforms are all open, with the code available at https://code.modalai.com . This enables our customers to modify however they see fit. The qvio server that ships takes ~33% of one CPU core (out of 4 cores). So it might not be a worthwhile exercise to move that to the could. If you were processing a much larger state estimate, like a full keyframe SLAM, then that processing could be done on a server. It might be hard to close the control loops in flight if you are trying to fly with it. As an outer loop though, it should work fine.
  • Sébastien de Pret Roose de CalesbergS

    OpenVpn don't launch on boot

    5
    2
    0 Votes
    5 Posts
    885 Views
    tomT
    Also, ensure you aren't connecting to your VPN with the same key on a different machine.
  • M

    Is it possible to use the VOXL CAM with a second companion computer?

    4
    0 Votes
    4 Posts
    725 Views
    M
    Thanks @modaltb , I appreciate your feedback. I think the usb-to-ethernet can make sense at least for proof-of-concept. @Chad-Sweet Yes, I am aware there is already a companion computer on the VOXL Cam. In my current work, I've already got an autonomy stack implemented on-top of a custom px4 drone platform with the upboard as the companion. My first interest is to add the VOXL Cam purely as a "tracking module" to replace something like the intel t265, and integrate the odometry out of it into my existing software. This would give me a way to evaluate the VOXL Cam in the use-cases I am exploring with a drone/autonomy configuration that is known to work. From there, depending on how well it works, I might consider replacing the upboard with the VOXL Cam, but that would not be the first thing I would do, as I would have quite a bit of software to re-work/port edit: It's good the VOXL can already run ros; I figure I could use voxl_mpa_to_ros to pass the VIO data over ROS from the VOXL to the Upboard in this PoC just to get started easily.