ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Software Development
    3. GPS-denied Navigation (VIO)
    Log in to post
    • Newest to Oldest
    • Oldest to Newest
    • Most Posts
    • Most Votes
    • Most Views
    • T

      How to Enable OpenVINS to Start Feature Tracking on Boot for Full Autonomous Use-Case

      • • tejasram
      2
      0
      Votes
      2
      Posts
      348
      Views

      Michael BaldwinM

      @wilkinsaf Do you happen to have any experience with this?

    • S

      Missing ov_overlay

      • • saegsali
      3
      3
      Votes
      3
      Posts
      306
      Views

      S

      @tom Thank you for your answer!

      Unfortunately the overlay does not appear, even when the drone is armed. We are using Starling 2 drones with SDK 1.6.2.
      Also in the voxl-open-vins-server.conf we can't find a setting for something related to the overlay.

      Do you have any ideas what we can try to see the ov_overlay again?

      Thank you in advance!

    • Rowan DempsterR

      Migrating from QVIO to OpenVINS (SDK1.6)

      • • Rowan Dempster
      5
      0
      Votes
      5
      Posts
      426
      Views

      zauberflote1Z

      To clarify, our current platforms are shipped with voxl-open-vins-server as the default VINS solution; however, QVIO is still available (SDK 1.6.2).

    • JP DroneJ

      Request: Add Flight Deck 2 YAML Configurations for OpenVINS Testing

      • • JP Drone
      1
      0
      Votes
      1
      Posts
      140
      Views

      No one has replied

    • J

      Open-VINS Mask File Location

      • • jakkkkobo
      3
      1
      Votes
      3
      Posts
      279
      Views

      J

      @zauberflote1 ok, thank you!

      I will try to implement the mask as in VoxlCam.

      Regards,
      Jacob

    • Nitin Varma VegesnaN

      This topic is deleted!

      • • Nitin Varma Vegesna
      1
      0
      Votes
      1
      Posts
      11
      Views

      No one has replied

    • D

      No ov_overlay in portal

      • • Dronodev
      7
      0
      Votes
      7
      Posts
      263
      Views

      D

      @zauberflote1

      alright, thanks for your help!

    • Nitin Varma VegesnaN

      OpenVINS issue

      • • Nitin Varma Vegesna
      8
      0
      Votes
      8
      Posts
      333
      Views

      Nitin Varma VegesnaN

      @zauberflote1 I am no longer having this issue. I have been flying with OpenVins for some time, and I was sometimes seeing drift in the vio estimate, and I was wondering what are the best configs to use. for vio_cams.conf and voxl-open-vins-server.conf?

    • N

      This topic is deleted!

      • • newdroneflyer
      2
      0
      Votes
      2
      Posts
      27
      Views
    • Rowan DempsterR

      Running QVIO on a hires camera

      • • Rowan Dempster
      14
      1
      Votes
      14
      Posts
      538
      Views

      Alex KushleyevA

      Hi @Rowan-Dempster , you are right, actually, there is no option right now to log from an ion buffer using voxl-logger. However, voxl-replay has an option to send camera frames as ion buffers. I have not tested it recently, but you could give it a try : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-logger/-/blob/extend-cam-logging/tools/voxl-replay.cpp

      For offline processing, it should not matter much whether you are using ion buffers or not. There would be a bit more cpu usage, but hopefully not too much. Having voxl-replay support cam playback as ion buffers is probably more important than using ion buffers for logging, since then your offline processing pipeline uses the same flow (ion buffers) as the live vio pipeline.

      We may add logging from ion buffer, but it's probably not a high priority.

      By the way, i wanted to mention one detail. I recently made a change in camera server dev branch to allocate the ion buffers that are used for incoming raw images as uncached buffers. This actually happens to reduce the cpu usage (so that cpu does not have to check / flush cache before sending the buffer to the GPU). The cpu reduction was something like 5% of one core per camera (for a large 4K image). For majority of hires camera use cases, this is beneficial, because usually the cpu never touches the raw10 image before sending to GPU.

      However, when you are logging the raw10 image to disk using voxl-logger, the cpu will have to read the contents of the whole image and send it via the pipe - uncached reads are more expensive. There will be increased cpu usage (i dont remember how much), but it should still be fine unless you are trying to log very large images at high rate. If you wanted to profile the cpu usage while logging, you can just disable making the raw buffers uncached and see if that helps. I have not yet figured out a clean way to handle this, maybe i will add a param for type of caching to use for the raw camera buffer.

      look for the following comment in https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/blob/dev/src/hal3_camera_mgr.cpp :

      //make raw preview stream uncached for Bayer cameras to avoid cpu overhead mapping mipi data to cpu, since it will go to gpu directly

      Alex

    • Rowan DempsterR

      Switching between Mag+GPS and VIO indoors

      • • Rowan Dempster
      8
      0
      Votes
      8
      Posts
      956
      Views

      Eric KatzfeyE

      @Sarika-Sharma You can get v1.0.10 here: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/libfc-sensor_1.0.10-202602041609_arm64.deb

    Powered by NodeBB | Contributors