@I_Dwyer @Chad-Sweet Hello all, has this issue been solved in and particular version, we too are facing the same issue, on HS1 the voxl-mavlink server is initiating but we are not able to see any data from this port. We are right now on the 1.5.3 build. Pls provided more info on the same.

@tom Thanks

@Zachary-Lowell-0 @Eric-Katzfey Yup, all's good now after stopping voxl-qvio-server. Thanks for the help!

Hi @Zachary-Lowell-0, sorry for the late reply. I've run the test that you asked with the new code that you wrote (v0.3.7). The results were pretty random, we go from a lower bound of 3 detections sent through voxl-mpa-to-ros over 10 detections present in tflite, to an upper bound of 8 over 11. This happens also for a small number of detections i.e. 2/4 as lower bound to 3/3 as an upper bound. Are your tests aligned with mine? I'm still using a custom yolo v5 for 2 class detections.

@tom I was able to pug the hardware to the expansion board that goes to the j13 port of the voxl flight, lsusb the one im using is the Bus 001 Device 002: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter [image: 1698281173198-screenshot-from-2023-10-25-18-45-49.png] the success connection of the hardware [image: 1698281636465-conection_succes.jpeg] the setup [image: 1698281643642-setup.jpeg]

@Felipe What mavlink message(s) would this sensor be sending over the UART?

@tiralonghipol I have never used that sensor but from the code it looks like adc_report is indeed the data it is publishing.

@Aaron-Porter I am facing the same issue, is it solved?

@JSchinowsky These should help you out: voxl add-on: https://docs.modalai.com/microhard-add-on-datasheet/#board-connections-and-io standalone: https://docs.modalai.com/microhard-usb-carrier/#board-connections-and-io

@Wei-Cui you could write your own hi-res overlay to render whatever information you'd like. You can see the qvio-overlay source code here. You would need to create your own service that received the high-res data, drew the overlay, and then published over MPA as a new pipe. voxl-portal will automatically grab all of the camera pipes and make available as potential streams

@Moderator Oh, thank you so much for sharing it. I'll check it!

@kerct I ended up building the mpa wrapper from source There you can modify the frames id and create your own tf tree took a while but it works now

@Moderator @modaltb

@bcarden unfortunately, we are not aware of those acronyms or technologies. The project to build the kernel for VOXL 1 is here: https://gitlab.com/voxl-public/system-image-build/voxl-build you could try to include those into your build

@jonathankampia Did you solve this issue?