@taiwohazeez Could you post the error and we can take a look? Also here's an easier way of installing it if you just want to run this script on the voxl. wget http://voxl-packages.modalai.com/dists/qrb5165/sdk-1.5/binary-arm64/voxl-ros2-foxy_0.0.1_arm64.deb wget http://voxl-packages.modalai.com/dists/qrb5165/sdk-1.5/binary-arm64/voxl-mpa-to-ros2_0.0.7_arm64.deb sudo dpkg -i voxl-ros2-foxy sudo dpkg -i voxl-mpa-to-ros2 voxl-configure-mpa-to-ros2

@taiwohazeez The build flow should be like this: cd voxl-mpa-to-ros2 git checkout dev git submodule update --init --recursive voxl-docker -i qrb5165-emulator ./install_build_deps.sh qrb5165 dev ./build.sh qrb5165 dev ./make_package.sh deb

Hi again, From investigating the voxl-vision-hub code with added prints for debug, I see that the setpoint SETPOINT_POSITION_MAGIC_NUMBER is sent to mavlink-server from two functions - (1) _send_current_position() sending the current position, and type-mask ignoring vx,vy,vz,ax,ay,az,yaw_rate // fetch latest position and attitude from px4 itself so the setpoint // we are about to send is a close as possible to where we currently are (2) execute_setpoint_position_command() sending the setpoint as recieved from voxl-planner The implemented behaviour of (1) suits the situation of position+yaw command. However for vx+vy+z+yaw_rate command I think something is missing. Any help will be appreciated. Thank you, Meytal

@Idan-Fiksel , it looks like it worked since your machine variant is now 1.0.0 . I assume it was 1.0.1. Sorry the numbering in the name of the kernel is 00.0 vs 00.1…

@dvz https://gitlab.com/WondesenB/voxl-tag-detector

@Alex-Kushleyev Thank you! For the moment we have decided to stick with USB since we can fit that into the current electrical architecture, but I appreciate the offer and may take you up on it at some point in the future if our design changes. Thanks, Kerry

@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}")

@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. [image: 1747414782060-ca188661-3943-4bac-beb5-16765bb7f96b-image.png] [image: 1747414856393-05a2c723-dd2b-4f8d-a243-3f6e61a9c56d-image.png]

@Alex-Kushleyev Gotcha, thanks for the info Alex and your help resolving this issue!

@Moderator That's exciting, I'll be on the lookout. Thanks!

@KnightHawk06 That is the source, yes.

Hi @SKA Alex's instincts are correct, we do not have a smaller plug in board for just tracking in a synce'd config. We only had an M0155 for one image sensor for a while, so your best bet is what Alex said and get the new M0188 for VOXL 2 Mini (VOXL 2 uses M0173, whereas VOXL 2 Mini uses M0188) It's quite cost competitive for what it does!! https://www.modalai.com/collections/all/products/m0188

You need to push the install folder as thats where the executables live in ros2 once you run colcon build. src folder is just the code you wrote with zero executables after colcon build is run.

@Matthew-Wellner , I am glad you got it working! When you used M0076 single camera interposer connected to VOXL2 J7, actually you were connecting to the "lower" camera slot, so that would be J7L, meaning slot ID 2, not 3. That is why your camera was not detected in that case. Regarding your M0084 not working, it could be a hardware issue in the flex cable or it's connectors. In order to figure this out, some more testing would be needed. Also, typically we suggest avoiding daisy chaining flex cables, so M0076 / M0135 allows you to do just that. It is possible that a combination of M0084 and another extension cable create sufficient signal distortion of the MIPI lines to cause CRC errors. Alex

@Alex-Kushleyev Yeah it was the cable. Getting hires feed now.