Subcategories

• VOXL SDK

  General questions regarding the VOXL SDK that do not fit into other categories

  104
  Topics
  479
  Posts

  S

  I’m having trouble recovering a couple voxl2 minis (M0104). Here’s what I observed and tried so far:

  The minis were working normally on a reliable power supply. Minor issues occurred (in one case voxl-camera-server segfaulted, in another I tried a custom binary). This may not be relevant. Units continued to boot normally for 3–4 power cycles. On the 4th or 5th restart, they stopped booting: LEDs show D1 + DS2 solid immediately. Sometimes they briefly show D1 + D2 solid before going back to D1 + DS2. Tried adb in those rare instances where D1 + D2 were on, didn't work Tried powering with nothing connected, same result. Tried unbricking procedure: Board recognized as a QDL device (web UI and lsusb both show the QDL device). Attempting “Flash Flat Build” with VOXL2 QDL Image 14.1a_1.7.8 always times out. I couldn’t find a voxl2 mini specific flat build, and in the latest voxl2 mini SDK there's no ufs directory as described here

  My questions:

  Is there a separate QDL flat build for the voxl2 mini (M0104), or should the standard voxl 2 flat builds work? Since I’d prefer to recover data if possible, is there any way to get the board into fastboot or ADB without reflashing? Does the LED pattern (D1+DS2 solid, sometimes briefly D1+D2) indicate anything specific about the boot state?

  Any help would be greatly appreciated, thank you!

• Video and Image Sensors

  General questions regarding the VOXL SDK that do not fit into other categories

  24
  Topics
  150
  Posts

  M

  @Alex-Kushleyev I only need the RAW output I plan to do all the post processing myself so this is exactly what I need, Thanks!

• GPS-denied Navigation (VIO)

  Questions about developing software on the products

  61
  Topics
  287
  Posts

  P

  I am trying to set up VIO for a custom frame which has two ar0144 (down and front) cameras.
  I have followed this sequence so far:
  1- voxl-camera-serveris up and running and I can see both camera feed in portal and using voxl-inspect-cam
  2- saved Extrinsics to /etc/modal/extrinsics.conf
  3- made sure vio_cams.conf exists and information makes sense
  4- following instructions as outlined here: https://docs.modalai.com/open-vins/ (with the exception of my SDK version which in my case is 1.5.0)

  here is the default content of voxl-open-vins-server.conf:

  /** * This file contains configuration that's specific to voxl-open-vins-server. * * *NOTE*: all time variables are measured in seconds */ { "en_auto_reset": true, "auto_reset_max_velocity": 20, "auto_reset_max_v_cov_instant": 0.20000000298023224, "auto_reset_max_v_cov": 0.20000000298023224, "auto_reset_max_v_cov_timeout_s": 0.5, "auto_reset_min_features": 1, "auto_reset_min_feature_timeout_s": 3, "auto_fallback_timeout_s": 3, "auto_fallback_min_v": 0.600000023841858, "en_cont_yaw_checks": false, "fast_yaw_thresh": 5, "fast_yaw_timeout_s": 1.75, "yaml_folder": "/usr/share/modalai/voxl-open-vins/VoxlConfig/starling2", "using_stereo": 0, "takeoff_alt_threshold": 0.5, "takeoff_occlude_stereo_left": false, "takeoff_occlude_stereo_right": false, "sync_config": true }

  5- I see voxl-open-vins-server process is not running and when I try to run it manually I get the following warning/error:

  WARNING: cal file opencv_tracking_front_intrinsics.yml is missing or invalid run voxl-check-calibration to see what calibration files are missing WARNING: cal file opencv_tracking_down_intrinsics.yml is missing or invalid run voxl-check-calibration to see what calibration files are missing failed to find cam cal for vio cam tracking_front ERROR cam_config_file_read QUIT REQUESTED Shutting down cameras... Camera shutdown complete error code: -1

  I am currently in the process of calibrating the camera but I am unable to complete it. I can see the overlay in the portal and all corners being detected but calibration is not progressing beyond %0

• Modal Pipe Architecture (MPA)

  Questions about developing software on the products

  42
  Topics
  235
  Posts

  M

  Thank you @Alex-Kushleyev for the clarification. Currently I just redefined the magic numbers on my own and voxl-inspect-pose works as usual. I am hoping that this breaking change only affects a small number of use cases. If anyone else faces the same issue with magic numbers theres at least the discussion that might help them as well 🙂

• AprilTag Relocalization

  Questions about developing software on the products

  11
  Topics
  55
  Posts

  Z

  @tomverstappen I am unable to recreate the issue with a starling running 1.5.0 - the output from voxl-vision-hub shows the relative coordinate frame from the tag relative to the camera and was able to get the drone to offset correctly.

  Are there any logs you can paste in here or video?

• ROS
  65
  Topics
  317
  Posts

  K

  @Eric-Katzfey got it, thank you for the info.

• Mapping and Planning
  19
  Topics
  59
  Posts

  M

  @tom can anyone help me with this

• Remote ID

  Questions about developing software on the products

  1
  Topics
  2
  Posts

  M

  @Mastermind That sounds like it would be possible, but obviously depends on the driver of the wlan adapter you choose. You would need to implement the bluetooth broadcast portion of Remote ID. The source code for voxl-remote-id is here and only currently supports the Wifi portion of Remote ID