@Jskim Can you please open these new questions as new topics? That way the appropriate staff member can address them. Thanks!

@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

@James-Strawson Thanks for your reply! It made me realise what the error must be. We use a locally cloned repository for libmodalpipe because we want to build our software directly on the drone. This is then used in the build and link process of our software. This happened to be on the 'master' branch and not the 'SDK-1.0.0' branch. So the pipe clients use a different version than the pipe servers which is likely the cause of our errors.

Please refer to the mavlink routing documentation here: https://docs.modalai.com/mavlink/#mavlink-routing-on-voxl

@Matt-Holmes You have to be on the voxl-dev branch

@Filip-Slezak-0 The standard way to install px4 is via a Debian package. You can look at our px4 "wrapper" project to see how we create the package here: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-px4/-/blob/master/make_package.sh

@ModalAI could you answer this question?

@James-Strawson ERROR fetching tf from tf ringbuffer - published constantly. [image: 1689581930287-image1.png]

@Tjark Thanks for pointing this out! I applied your fix in voxl-vision-hub v1.6.7 which is now up on the staging repository and will be included in SDK 1.0.1 Best Regards, James

@Philemon-Benner Seems like some else had the same issue but there was no further investigation on the problem. https://forum.modalai.com/topic/2125/voxl-mavlink-server-external-fc-bus-error?_=1688565579723

@relevinsky For now your best bet will be to get an add on card that has a UART available for the applications processor. Future software releases will provide access to a UART on the DSP (As long as the flight controller isn't running) but that is not available today.

@Alex-Pabouctsidis Nice! That whole process and API will be cleaned up in the future but looks like you were able to figure it out. All of the actual I/O driver code is baked into the sensors DSP image. As Qualcomm licensees we have access to it (and build that image) but we cannot share it.

@relevinsky reposting my answer from another thread: The VOXL SDK projects aren't meant to be built on VOXL2 itself. We offer a few different docker images to build on a PC, voxl-qvio-server on VOXL2 is built using qrb5165 emulator: https://docs.modalai.com/voxl-emulator/#install-the-voxl-emulator-docker-image while some other projects are built using voxl-cross: https://docs.modalai.com/voxl-cross/#install-pre-built-voxl-cross

@hedd apologies as I was OOO for a few days. Feel free to send me an email at andrew.wilkins@ascendengineer.com I would like to better understand what you are attempting to accomplish. It should not matter what VOXL version you are on.