Skip to content

Support Request Format for Best Results

164 Topics 751 Posts
  • Barometer was not working perfectly (Temperature raises)

    5
    3
    0 Votes
    5 Posts
    2k Views
    Alex KushleyevA
    regarding external baro, please see response here : https://forum.modalai.com/topic/3996/unstablr-baro-in-voxl-2-mini
  • Drone not flying manually with ORQA FPV.Ctrl controller

    9
    0 Votes
    9 Posts
    2k Views
    Jainik MehtaJ
    @tom Thank you! This solution worked. I changed this value and reboot the drone and it now connects and fly well with the RC controller.
  • 0 Votes
    7 Posts
    757 Views
    tomT
    @aryan-yadav If you had purchased a drone with the M0173 it would've already had the correct kernel flashed but we ship bare boards with the default kernel
  • Issue with takeoff in Starling 2 Max in Manual flight mode

    2
    8
    0 Votes
    2 Posts
    347 Views
    No one has replied
  • Battery Charger for Starling 2 Max

    5
    3
    0 Votes
    5 Posts
    1k Views
    V
    @Zachary-Lowell-0 Thank you for letting me know. this is my first time working with a multi-cell battery and a smart charger. I will be careful not to connect multiple batteries at the same time.
  • ROS Melodic on VOXL-Flight

    8
    0 Votes
    8 Posts
    1k Views
    Kiazoa JoaoK
    @jonathankampia got it. Thank you so much.
  • VOXL 2 Camera Connected but Not Feed

    18
    3
    0 Votes
    18 Posts
    2k Views
    Wesley GunawanW
    @Moderator [image: 1730146896479-bf357fde-1761-4850-8a9a-4b9ba6c37115-image-resized.png] This is after power cycle (poweroff -f, power source off, turn on again)
  • GPS-denied offboard mode and MAVROS configuration on VOXL

    3
    0 Votes
    3 Posts
    690 Views
    C
    @LR Are you able to fly seeker indoor (for which no GPS available) with Position mode? If not, for seeker to use VIO as position estimate you need to use this set of parameter for px4.
  • Left Stick Not Self-Centering Issue

    2
    0 Votes
    2 Posts
    550 Views
    tomT
    @deeplearning361 That is normal, that is how the majority of drone controllers work. You can read through the commando 8 user guide to figure out how to make it self-centering if that is preferred: https://manuals.plus/iflight/commando-8-radio-transmitter-elrs-manual
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    2 Views
    No one has replied
  • Unable to Generate the Mavsdk Docker on a M500

    5
    0 Votes
    5 Posts
    909 Views
    Zachary Lowell 0Z
    @Sarah-McMahon said in Unable to Generate the Mavsdk Docker on a M500: @Zachary-Lowell-0 I encountered an issue with the threading during the download process, which caused it to take about 9 hours. The main problem arose when running deploy-to-voxl.sh—the drone ran out of storage after pushing the tar file, preventing the image from being loaded into Docker. While attempting to free up space, I mistakenly ran the wrong opkg command and deleted all opkg packages, making it impossible to SSH or ADB into the drone. Do you have any suggestions for a potential fix? I noticed the USB Expander and Debug Add-On Board might be helpful, but I couldn't find it available for purchase on the website. Reply Hi Sarah - I am unsure if I am following - the docker tarball is only a few gig's so I am unsure how you ran out of space. For now I would just reflash your voxl from the downloads page here https://developer.modalai.com/categories (download the most recent voxl1 sdk unzip it and run the install script from the parent computer) - this will reinstall the entire sys image and newest SDK onto the voxl and allow you to adb shell and ssh in again. From there you will need to configure the SKU and mpa and then you can try the docker installation again from the parent computer. Can you let me know how big your image is for the mavsdk docker tarball? And if you run df -h on your voxl can you paste the output I want to see where all your disk space is being utilized. Zach
  • VOLX MSU-M0107

    1
    1
    0 Votes
    1 Posts
    338 Views
    No one has replied
  • TOF sensor quailty down after upgrading to VOXL 1.3

    2
    2
    1 Votes
    2 Posts
    497 Views
    Alex KushleyevA
    @Shivam-Sehgal , I believe the TOF processing settings may have changed between SDK 1.1 and 1.3 (more noise filtering was added). In both cases, the ground is visible (although hard to see in the black image). In the 1.3.0 case, the other vehicle is not visible in TOF output, but there is less noise. Are you able to test the two SDK versions with some easy features for TOF sensor to pick up? Some large objects with simple geometry and some small objects. Alex
  • Sales Contact

    1
    0 Votes
    1 Posts
    265 Views
    No one has replied
  • Qualcomm Flight RB5 stuck in fastboot

    10
    0 Votes
    10 Posts
    2k Views
    tomT
    @royb If you have another SOM sitting around it wouldn't hurt to try
  • Missing install_build_deps.sh in voxl-opencv

    5
    0 Votes
    5 Posts
    827 Views
    N
    Excellent. Thank you!
  • Specification of Starling2 Sensors

    1
    0 Votes
    1 Posts
    284 Views
    No one has replied
  • IMX214 min exposure time

    5
    0 Votes
    5 Posts
    887 Views
    Alex KushleyevA
    @stephengerdts , in majority of cameras, the exposure time of the whole frame is set as a multiple of a specific number, let's call it T0. T0 is the minimum exposure of the whole frame and you can set any other exposure values, which will get rounded to a multiple of T0 ( K*T0 ). This T0 number is actually exactly equal to something called the Line Readout Time, which is the time it takes for the camera hardware to sample, process and send out a single line of pixels. This may be a little confusing, but if you think about how rolling shutter camera works, it "reads out" one line at a time (it cannot store the whole image in memory, so exposure and read out of each line are staggered). Please take a look at this link that shows how exposure time relates to readout time : https://www.researchgate.net/figure/Timing-diagram-of-the-CMOS-sensor-array-shown-in-Fig-2-The-readout-times-of-the_fig2_3328923 I believe that in order to simplify the exposure timing logic, the cameras then use the readout time as a unit of increment for the exposure time. So, the minimum exposure time reported by the voxl-camera-server is the minimum exposure time for the whole frame, which is also equal to the readout time of a single line In case of IMX214, the line readout time is 10.449us which is also the increment for adjusting exposure. The logic inside the camera framework will take the desired exposure time from the user / voxl-camera-server and then set the correct integer number of exposure in terms of "lines" (not microseconds) in order to achieve the correct exposure duration in units of time. Alex
  • Accedently replaced ./bash with adb push command

    2
    0 Votes
    2 Posts
    325 Views
    tomT
    @QuiroJ6427 I'd recommend just downloading the latest SDK from downloads.modalai.com and installing it. The latest for M500 should be SDK 1.2.0. 0.9 is quite old at this point so this will be a nice upgrade regardless
  • VOXL2 takeoff and land script

    2
    0 Votes
    2 Posts
    529 Views
    ModeratorM
    @Gary-Holmgren Check out the AprilTag Relocalization page Basically, every time an AprilTag is viewed, the position is updated to reflect that tag as an anchor. So, it's not precision landing as much as position refinement. You then land at the desired position which should be more accurate due to the position refinement with the fiducial marker We haven't looked at the MAVSDK in a while, is there a specific error you're running into?