Skip to content

General Questions

2.2k Topics 11.3k Posts

Not sure where your question goes? Ask here. ModalAI engineers and the community answer questions about any VOXL product.

  • Looking for deatiled flight logs

    Unsolved
    1
    0 Votes
    1 Posts
    131 Views
    No one has replied
  • Configuration for VOXL 4in1 mini 6S ESC and Newbee Drone Flow 2808 1300KV motors

    Unsolved
    3
    0 Votes
    3 Posts
    375 Views
    A
    @Alex-Kushleyev said in Configuration for VOXL 4in1 mini 6S ESC and Newbee Drone Flow 2808 1300KV motors: ESC M0138 FPV ESC : Thank you very much for your reply Alex. I appreciate the references and support documentation you provided as well.
  • M0149 IR Filter with 36 Pin Connector

    Unsolved
    3
    0 Votes
    3 Posts
    241 Views
    Kashish Garg 1K
    @Alex-Kushleyev Thanks Alex, very helpful!
  • 1 Votes
    1 Posts
    195 Views
    No one has replied
  • How much can cameras be obscured?

    Unsolved
    11
    0 Votes
    11 Posts
    1k Views
    Alex KushleyevA
    @Myles-Levine , if you are masking out 90% of down-facing camera, then it is probably useless any movement of the features will get it out of the unmasked region very easily and feature will be dropped.. It may hurt VIO as there may be features going in and out, only trackable for a few frames (just adds to the complexity). You should try to move the down-facing camera to free up it's FOV or even have it facing slightly angled to the back of the drone.. Alex
  • Confusion about the VOXL 2 MIPI Boson+ website page

    Unsolved
    2
    1
    0 Votes
    2 Posts
    219 Views
    Alex KushleyevA
    Hello @Catalystmachine , Sorry for the confusion. We have updated the page to be more clear that Boson is not included, see below: "(No Boson)" was added to the kit description. The title of the product already states "VOXL 2 MIPI Boson+ Adapters for Thermal IR FPV" as well as the Kit description used to say (Before we added (No Boson)) : "PCB Adapters Only..." The price of the Boson cameras varies significantly, depending on the specifications. You can contact a distributor to get more details. For example : https://www.oemcameras.com/product-category/thermal-imaging-cameras/thermal-imaging-cores/flir-boson-series-htm/boson-plus/ (you can find more at https://oem.flir.com/contact/find-a-dealer/) Please note that Boson+ series of the Boson sensor is required for compatibility with VOXL2. Regarding the pricing of the adapter kit, we do offer discounts in higher volumes, if you are interested, please send us a request: https://www.modalai.com/pages/contact-us [image: 1773106957515-ebff1907-0495-4a65-8f27-2138562022d3-image.png]
  • Microdds not working with Microhard modem

    Unsolved
    10
    0 Votes
    10 Posts
    1k Views
    A
    Hey @voxltester It seems there is an issue with how MicroXRCE and the microhard modem interfaces are starting up, I had to edit the service files to get the topics on the VOXL2. Edit /etc/systemd/system/voxl-microdds-agent.service: [Unit] Description=voxl-microdds-agent SourcePath=/usr/bin/MicroXRCEAgent After=network.target After=multi-user.target [Service] User=root Type=simple ExecStart=/usr/bin/MicroXRCEAgent udp4 -p 8888 [Install] WantedBy=multi-user.target Edit /etc/systemd/system/voxl-modem.service: [Unit] Description=Modem Initialization After=sdsprpcd.service [Service] User=root Type=oneshot ExecStartPre=/bin/sleep 2 ExecStart=/usr/bin/voxl-modem-start RemainAfterExit=yes [Install] WantedBy=multi-user.target Add export ROS_DOMAIN_ID=0 to your .bashrc Reboot the VOXL2, and the topics should come up Thanks
  • Feasibility & Integration Inquiry – FLIR Lepton XDS with VOXL2

    Unsolved
    4
    0 Votes
    4 Posts
    407 Views
    Alex KushleyevA
    @Jetson-Nano , since we currently have no plans to do the MIPI integration of this sensor, you always have the option to use USB connection and voxl-uvc-server to publish images via MPA. You would need to check if the sensor supports the standard UVC interface and try it out... Alex
  • Starling 2 not following navigation path

    Unsolved
    21
    1
    0 Votes
    21 Posts
    3k Views
    Cliff WongC
    @greg_s That would explain a lot what's happening. If you start fresh and connect to the drone with voxl-portal and goto the VIO tab/menu option, you should be able to pick up the drone and perform a bench test. Considering Figure 8 is not working, you will need to inspect the front and downward camera, tighten/remount any loose parts and possibly check camera focus & calibration. Worse case if the forward camera is good and not changed from factory, you can edit /etc/modalai/vio_cam.conf on the drone and disabled the faulty camera (disabled the down camera). You'll have degraded precision (mainly bad vio in fast yaw motions), but should be able to perform a figure 8 and should get you running until you repair that bottom sensor.
  • Where to find the ToF and Hires sensors calibration?

    Unsolved
    8
    1 Votes
    8 Posts
    1k Views
    J
    @Alex-Kushleyev Thank you so much! I'm a bit preoccupied with a few other projects but hopefully I can take a look by the end of next week and get back to you.
  • Starling 2 Indoor SLAM Development Drone

    Unsolved
    1
    0 Votes
    1 Posts
    288 Views
    No one has replied
  • 0 Votes
    2 Posts
    293 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.
  • This topic is deleted!

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

    1
    0 Votes
    1 Posts
    2 Views
    No one has replied
  • TOF Sensor Stock (Order #7777)

    Unsolved
    2
    0 Votes
    2 Posts
    208 Views
    Alex KushleyevA
    @Catalystmachine , for questions regarding orders, please reach out here : https://www.modalai.com/pages/contact-us
  • How do I find the camera sensor adapters on the website?!

    Unsolved
    2
    1
    0 Votes
    2 Posts
    220 Views
    Alex KushleyevA
    @Catalystmachine https://www.modalai.com/products/m0155 https://www.modalai.com/products/m0188 (fixed link) https://www.modalai.com/products/m0194 If you need M0195, you can contact us directly for a custom order (it's not in the shop yet). https://modalai.com/contact Alex
  • M0181 Pin Out and Electrical Diagram

    Unsolved flir
    23
    0 Votes
    23 Posts
    5k Views
    Alex KushleyevA
    @Dan-Jennings , M0181 can be used to enable a Boson and another hires or tracking camera (or Hadron combo), see diagram below. You would need to use the kernal variant 1.0.1 (same one used for M0173, which I am assuming you are already using). So basically, you can use any standard config C26-C29 + two more cameras connected to VOXL2 J8. Please note that VOXL2 J8 shares CCI (i2c) buses with J6 and J7, so you have to be a little careful about what cameras you connect to J8 to avoid i2c address conflicts. I am going to put together some more information on that soon. But if you are adding a Hadron or Boson + IMX412 to J8, there will be no conflict. Please let us know if you have any other questions. Alex [image: 1771605639258-voxl2_m0181_boson_hires.png]
  • 0 Votes
    3 Posts
    411 Views
    P
    Hi @DavidTorres, Thanks a lot for the detailed explanation — this is very helpful. Your comments about VIO drift, autonomy limitations, and the development effort required give us a much clearer picture. We’ll review the documentation and PX4 resources as suggested. Thanks again for taking the time to share your experience. Best regards
  • Product Lifecycle

    Unsolved
    1
    0 Votes
    1 Posts
    194 Views
    No one has replied
  • 0 Votes
    5 Posts
    1k Views
    H
    @Alex-Kushleyev I made the following changes. Modified the DTS files as stated prior. Flashed the devcfg.mbn file from SDK 1.0.0 I did not need to configure the level shifter actually. The port worked in SPI mode even without running voxl-gpio -w 67 1. Running the command doesn't seem to change anything. I used Channel 1 on /dev/i2c-0 for the second lepton. I simply wrote TCA9543A_CHANNEL_1_ENABLE to TCA9543A_CONTROL_REGISTER in voxl-lepton-server. I pretty much followed what was described here.