@Eric-Katzfey Thanks Eric, that makes sense!

Hey @KMillzOG ,

This doesn't help with your core issue, but I have had success running the ROS2 docker images on RaspiOS on a pi: https://docs.ros.org/en/foxy/How-To-Guides/Installing-on-Raspberry-Pi.html If you're comfortable running your software inside a Docker container, that'll solve your problem. Conveniently, you can also build a docker file for ARM or for X86, so you can run the same software on a more traditional PC or inside a CI pipeline.

I also recently noticed that there is still an officially supported Ubuntu image for the Pi. I haven't tried it, but it might be another option. If you have a spare SD card, you could install ubuntu on the spare card, then see if that works for you. Then if it doesn't work you can just go back to the old SD card.

I'm evaluating adding a VOXL cam to an existing rover setup, for its ability to generate point clouds and compute visual odometry. I want to get point cloud data from the VOXL cam flowing into our ROS environment on our companion computer. I'm trying to avoid writing additional software to run on the VOXL, since we already have our main ROS software stack running on this companion computer. I was hoping to treat the VOXL CAM as a plug-in peripheral, which may or not be possible.

The VOXL cam comes out of the box with at least two wired connections: the USB ADB connection, and a serial link, which the software (the qvio daemon I believe specifically?) uses to send pose solutions to an external device (we're using a Pixhawk right now). Can either of these be configured to send ROS data in any way? As far as I know ROS typically expects a TCP/IP stack, but maybe there's some sort of bridge for ADB?

There's WiFi connectivity available, but we're already using the WiFi on our companion computer for something else. We'd need some design compromises to include the VOXL in that network. Plus, it just feels stunningly ridiculous to need a wireless connection between two parts of the same rover.

Is there any way to establish a wired network connection to the VOXL CAM? Or, to communicate ROS data over the existing wired interfaces (ADB, serial)? Our existing software stack is in ROS2, so that's also a bridge we'll have to cross.