Subcategories

• VOXL SDK

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

  98
  Topics
  451
  Posts

  E

  @Ege-Yüceel Wow, this is a very ambitious plan! Keep in mind that VIO needs not only camera images but also IMU input. Camera images are normally supplied by the voxl-camera-server on MPA pipes. So, you would need to stop voxl-camera-server and start your own application that takes the images from Gazebo and places them into correctly named MPA pipes. The images would have to be formatted properly, etc. Likewise for IMU samples that normally come from voxl-imu-server. I think this will be quite difficult to get working properly but theoretically possible.

• Video and Image Sensors

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

  17
  Topics
  108
  Posts

  Q

  @Riley-Dove would you have any insight on this? Thanks!

• GPS-denied Navigation (VIO)

  Questions about developing software on the products

  59
  Topics
  280
  Posts

  M

  @Idan-Fiksel Is the calibration card mounted to a hard backing piece so there are no warps or wrinkles in the checkerboard?

  Did you print with a PDF so that the checkerboard measurements are accurate?

• Modal Pipe Architecture (MPA)

  Questions about developing software on the products

  41
  Topics
  232
  Posts

  R

  @Jeffrey-Mao Hello Jeffery, We are currently working on implementing SLAM for the Starling 2 platform. Our initial approach involved using the available ROS 2 topics provided by voxl_mpa_to_ros2, installing standard SLAM packages, and using RViz for visualization. However, we've encountered a major issue: most of the topics do not have a frame_id defined, and there is no existing transform (TF) tree that can be used with RViz.

  So far, we've only been able to visualize the tof_pc (Time-of-Flight point cloud) data. To do this, we had to manually publish a static transform between the TOF frame (which is named world) and map. However, in this setup, the drone's location does not update dynamically. To address this, we're considering writing a transformation node to define the relationships between coordinate frames (e.g., map, odom, base_link, tof, etc.). However, developing this from scratch is proving to be time-consuming and error-prone.

  I also noticed that you were able to generate a map using voxl-mapper and et the map in ROS2 with the mpa_ros2 interface. This could be a much more efficient path for us to pursue. Could you please explain in detail:

  What exact steps you followed to export the map using voxl-mapper?

  Is it possible to regenerate or update the map in real-time in RViz, or export it to another visualization tool?

  Thanks

• AprilTag Relocalization

  Questions about developing software on the products

  10
  Topics
  44
  Posts

  J

  @Alex-Kushleyev Is there some news about this issue ?

• ROS
  65
  Topics
  310
  Posts

  T

  Hi @taiwohazeez,

  The " /fmu/in" prefix is used for sending data to the autopilot - you're never going to receive data from the autopilot listening to that topic.

  Look at the "/fmu/out" topics to see messages coming from the autopilot.

  Best,
  Ted

• 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