ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics
    • All categories
    • M

      IMX664 MISP decoding issue

      Video and Image Sensors
      • • • mark
      4
      0
      Votes
      4
      Posts
      32
      Views

      Alex KushleyevA

      @mark , it looks like your version of voxl sdk has an early version of the imx664 driver (not supporting 2704x1540 resolution.

      Are you able to upgrade sdk to 1.5.x or 1.6.x?

      Alternatively, i could share the latest camera drivers to use with 1.4.5.

      I would also recommend updating voxl-camera-server to the latest, but that would also require updating other packages.. would you consider upgrading the sdk or are you locked to 1.4.5?

      Alex

    • C

      TOF Sensor Stock (Order #7777)

      Ask your questions right here!
      • • • Catalystmachine
      2
      0
      Votes
      2
      Posts
      22
      Views

      Alex KushleyevA

      @Catalystmachine , for questions regarding orders, please reach out here : https://www.modalai.com/pages/contact-us

    • J

      I am considering purchasing this product and would like to inquire about its VIO performance

      Ask your questions right here!
      • • • jh81306
      2
      0
      Votes
      2
      Posts
      32
      Views

      zauberflote1Z

      @jh81306
      Hello there,
      Yes, real time performance is achievable with 3 cameras at 30fps, evidencing the benefits of our hardware accelerated GPU feature tracker. From this perspective, if you plan on using GPU-heavy applications, QVIO may be the second best option, as it uses remote procedure calls between the linux processor and the DSP, freeing GPU usage. However, due to the inherent nature of the DSP (L2 Cache, etc) and timing considerations, running QVIO on 3 Cameras may not guarantee a consistent update rate depending on the processor load/scheduler priorities. In essence, choosing one or the other is a trade-off that should be based on user use-case.

      In terms of estimator robustness, our branch of OpenVINS has been considerably modified to support accurate estimates under degraded conditions, and all ModalAI UAV platforms have gone through extensive calibration in order to obtain the optimal parameter set. Hence, in terms of estimator quality, OVINS outperforms QVIO, but requires carefully calibration of your visual-inertial sensors. Finally, If you opt to acquire a ModalAI Vision drone, OpenVINS should be fully functional out-of-the-box, facilitating a potential pipeline transition.

    • A

      MDK-M0048-2-01 change to MDK-M0048-2-01

      Microhard Modems
      • • • austin.c
      2
      0
      Votes
      2
      Posts
      21
      Views

      VinnyV

      Hi @austin-c
      yeah, and it will not.
      There are dozens of changes between the two boards.
      It's just easier and cheaper to order the correct version. We have no documents showing how to convert it is simply not doable for the cost and risk and time.

      Not the news you wanted, but please trust me on that one. 🙂

    • S

      voxl-cross error when building voxl-open-vins-server

      VOXL SDK
      • • • SKA
      1
      0
      Votes
      1
      Posts
      13
      Views

      No one has replied

    • C

      Letter of Volatility

      Ask your questions right here!
      • • • cannedspam
      1
      0
      Votes
      1
      Posts
      14
      Views

      No one has replied

    • Jetson NanoJ

      Feasibility & Integration Inquiry – FLIR Lepton XDS with VOXL2

      Ask your questions right here!
      • • • Jetson Nano
      1
      0
      Votes
      1
      Posts
      12
      Views

      No one has replied