Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Collapse
Brand Logo

ModalAI Forum

  1. ModalAI Support Forum
  2. General Questions
  3. voxl-open-vins-server???

voxl-open-vins-server???

Scheduled Pinned Locked Moved Unsolved General Questions
3 Posts 2 Posters 879 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • tkddnjs825T Offline
    tkddnjs825T Offline
    tkddnjs825
    Contributor
    wrote on last edited by
    #1

    I have a question.
    I am currently using VOXL2 with SDK 1.4.1 and utilizing dual tracking with the M0173 module. Since I am only flying indoors, I have not attached a GPS module.

    I am using voxl-open-vins-server, but I noticed that the documentation and the configuration file contents for voxl-open-vins-server are different.

    Could you provide a summary of the correct voxl-open-vins-server setup for SDK 1.4.1?

    1 Reply Last reply
    0
    • James StrawsonJ Offline
      James StrawsonJ Offline
      James Strawson
      ModalAI Team
      wrote on last edited by
      #2

      voxl-openvins-server is under rapid development at the moment and I expect the entire configuration file to be cleaned up dramatically quite soon. After that point the configuration file contents will stabilize and we will update the documentation to match. Fully documenting the current state would be a wasted effort.

      It should not be necessary to modify the configuration file. When flashing the 1.4.1 SDK a new default config file will have been made. What differs from drone-to-drone is the physical layout of the cameras and IMU which is defined by /etc/modalai/extrinsics.conf as well as the cameras that should be used for vio which is set up in /etc/modalai/vio_cams.conf

      tkddnjs825T 1 Reply Last reply
      0
      • James StrawsonJ James Strawson

        voxl-openvins-server is under rapid development at the moment and I expect the entire configuration file to be cleaned up dramatically quite soon. After that point the configuration file contents will stabilize and we will update the documentation to match. Fully documenting the current state would be a wasted effort.

        It should not be necessary to modify the configuration file. When flashing the 1.4.1 SDK a new default config file will have been made. What differs from drone-to-drone is the physical layout of the cameras and IMU which is defined by /etc/modalai/extrinsics.conf as well as the cameras that should be used for vio which is set up in /etc/modalai/vio_cams.conf

        tkddnjs825T Offline
        tkddnjs825T Offline
        tkddnjs825
        Contributor
        wrote on last edited by
        #3

        @James-Strawson
        "takeoff_cam": Tells OpenVINS which camera to use for takeoff. This should be a camera where "is_occluded_on_ground" is set to false in vio_cams.conf. Besides this setting, what else needs to be configured?

        1 Reply Last reply
        0

        Reading along? Create a free ModalAI Forum account to join in.

        With an account you can reply, ask your own question, get an email when a ModalAI engineer answers, and mark the reply that solved it. Your place in each thread is saved between visits.

        Questions about VOXL, Flight Core, ESCs and ModalAI drones are answered here by the engineers who build them.

        Register Login
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        ModalAI
        Categories Recent Tags ModalAI.com Docs
        © 2026 ModalAI® · Accelerating autonomy for smaller, smarter, safer drones · Powered by NodeBB
        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups