Subcategories

• VOXL SDK

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

  89
  Topics
  419
  Posts

  J

  @James-Strawson

  hmmm, by any chance are you failing to link against symbols from libgmb.so? That is a new library dependency of libmodal_pipe. Most of our packages use the following linker flags to avoid recursive linking, I think this would be a better solution than specifying the libmodal_pipe version in install_build_deps.sh

  set(CMAKE_C_FLAGS "-Wl,--unresolved-symbols=ignore-in-shared-libs ${CMAKE_C_FLAGS}")
  set(CMAKE_CXX_FLAGS "-Wl,--unresolved-symbols=ignore-in-shared-libs ${CMAKE_CXX_FLAGS}")

• Video and Image Sensors

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

  13
  Topics
  82
  Posts

  A

  Hello @Kerry-Snyder,

  This has been on our todo list for a while, but the Boson units we had at the time of integration did not support switching to 16-bit MIPI stream due to an issue in the Boson firmware (well, it is really a 14 bit packed into 16 bit data). While MIPI 16 bit stream did not work, it was working via USB (linux uvc)

  Some of the newer versions of the Boson firmware have fixed the issue, but we have not tested it. Can you check which version of Boson firmware you have?

  If the Boson firmware supports the 16 bit output, in order to test this with VOXL2, a new sensormodule bin file would be required as well as an update to voxl-camera-server, which is pretty easy to do, but we cannot test it at the moment.

  If your firmware does support the 16 bit mipi output and you are willing to help with beta testing, I could update the camera server and provide the sensormodule driver for testing.

  Alex

• GPS-denied Navigation (VIO)

  Questions about developing software on the products

  55
  Topics
  266
  Posts

  J

  @Alex-Kushleyev Thank you for reverting, I will check this out and get back to you

• Modal Pipe Architecture (MPA)

  Questions about developing software on the products

  40
  Topics
  226
  Posts

  G

  @tom @Zachary-Lowell-0 Looks like I got it to work, I was just running the wrong command. Is there an existing topic called "tag_detections" that should be appearing or is there another repository I need to download in order to obtain that? Thank you.
  ca188661-3943-4bac-beb5-16765bb7f96b-image.png
  05a2c723-dd2b-4f8d-a243-3f6e61a9c56d-image.png

• AprilTag Relocalization

  Questions about developing software on the products

  10
  Topics
  43
  Posts

  Q

  @Eric-Katzfey Thank you for the reply,
  If I understand correctly, the example you provided shows MAVSDK running directly on the VOXL — so on the drone itself. However, we want to run our script on a separate PC to be able to control all drones at once. We're not sure which port to use to communicate with PX4 while also taking advantage of the relocalization handled by VOXL.

  Thank you again for your help!

• ROS
  59
  Topics
  279
  Posts

  V

  I am following this tutorial (https://docs.px4.io/main/en/ros2/offboard_control.html#humble) which uses ROS 2 and uXRCE-DDS. My Starling drone is running on PX4 v1.14 which is compatible with uXRCE-DDS and the offboard code works in the PX4-Autopilot simulation using the command "make px4_sitl gz_x500".

  I would like to run this offboard code in my physical drone but I couldn't find a step by step guide on how to do so. I'm totally new to drone development overall and am quite lost to how to upload or run my offboard cpp code on the drone. Any guidance is appreciated, thank you.

• Mapping and Planning
  19
  Topics
  58
  Posts

  M

  @Alex-Kushleyev @Moderator

• 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