@Eric-Katzfey @Alex-Kushleyev not exactly what I was looking for. I already implemented it using ffmpeg library. Basically I wanted to use voxl-send-command utility to send start/stop recording commands while also have the ability to save snapshots. I didn't like the idea of using gstreamer pipes for implementing this so I chose ffmpeg. I think my solution is good enough for now. I am able to start/stop recordings do snapshots and embed xmp metadata into the snapshots. Although I might come back to using OMX library if I decide I need the hardware encoding.

@Rawdha-R Yeah that SDK is very old and doesn't have the SKU tooling in it yet. I would recommend flashing the latest SDK (1.3.3) from downloads.modalai.com under "VOXL 2 Platform Releases" Just follow the instructions here to do so: https://docs.modalai.com/flash-system-image/#flashing-a-voxl-sdk-release

Thank you @Eric-Katzfey , I'll check it out and will get back to you.

@Denver-Bennett were you able to find a solution to this? same issue on our end

@Denver-Bennett Were you able to find a solution to this? same issue on my end

@Eric-Katzfey I had backed up my ROS workspace using adb pull before flashing the drone and used adb push to reinstate my workspace on the drone. This unfortunately changed up the file permissions for the folders within the workspace. I was able to fix this by deleting (using rm -rf) all folders within my ROS workspace except the src (which contains the packages I was working on) and building the packages again. I was then faced with the other CMake error visible above - @Prabhav-Gupta said in Unable to build ROS python workspace on the RB5 drone: CMake Error at /home/root/python_ws/src/vision_opencv/cv_bridge/CMakeLists.txt:16 (find_package): Could not find a package configuration file provided by "OpenCV" (requested version 3) with any of the following names: OpenCVConfig.cmake opencv-config.cmake I fixed this by building opencv from source on the drone (following this - https://docs.opencv.org/4.x/d7/d9f/tutorial_linux_install.html) After installing opencv, the catrkin build did not return any errors at the time. I do need to check whether my ROS Nodes are working as expected or not. Will update here once I do the same. Thank you for your time!

Hey @dvPr1m3 , How were you able to do it on VOXL 2?

After connecting the VOXL2 Mini to an external flight controller as described here via J10 on VOXL2 Mini, MAVlink data was viewable from a VOXL Flight Core v2. We are still having some troubles with viewing the streams, however now the stream/camera names are appearing in QGC with the video feed selector now that the above MAVlink connection has been established. It seems like in order to route MAVlink data out of J3 on VOXL2 Mini via USB, we will need to look into MAVrouter or a similar solution. For now we will continue integration via J10. Our goal with routing MAVlink data via USB on VOXL2 is to reduce the telem connections required on a flight controller for our product. We would like the ability to run multiple RTSP streams and MAVlink communication via a single USB connection (from J3 on VOXL2 Mini) to an external flight controller. Is UART communication via J10 the preferred or only method of communicating with VOXL2 Mini over MAVlink? Is there a way to do MAVlink routing with the VOXL SDK as I mentioned, or will this need to be custom implementation? If the VOXL2 Mini is receiving MAVlink data via a UART connection from another device, will the VOXL2 Mini forward and receive MAVlink data to/from the MAVlink device through to a Flight Core via the external flight controller connection J10 on VOXL2 Mini? Thank you for very much for your time and feedback on this topic.

@tahawaru Okay, that shows you have 1.14.0-2.0.78. If you want to build 1.14.0-2.0.63 then you need to check that version out instead.

@enrico-bandera-0 It's not easy and, unfortunately, we cannot support that right now.

@Eric-Katzfey I figured out the problem. I changed the mavlink pipe to mavlink_onboard keeping the channel number as 1. Setting the channel number as 2 seems to fix the problem. I haven't looked into the implementation of modal-pipe architecture but I thought that the channel number is just used by the client of the pipe (kind of like an open file descriptor number?). Basically it looks like having the channel number as 1 breaks the mavlink pipe somehow.

@tahawaru It's just a change in the naming. Used to be platform, now is SDK. Go with the most recent SDK.

@Eric-Katzfey Sure. Here is the link of the new post: https://forum.modalai.com/topic/3649/trouble-in-running-the-mavros_test-project-simple-example?_=1721124109041

@jacob-yaacubov , I am not sure why this is happening. However, you maybe able to debug this yourself using gdb and starting the ros node manually: gdb /opt/ros/melodic/lib/voxl_mpa_to_ros/voxl_mpa_to_ros_node r __name:=voxl_mpa_to_ros_node __log:=/opt/ros/foxy/log/my_new_ros_log/voxl_mpa_to_ros_node-1.log (wait for crash) bt (this will print stack backtrace, at least will tell you in which function the crash occurred) Please try..

@Nicholas-Clark you can find the voxl-cross Dockerfile and source here. We're happy to incorporate merge requests if you feel you have a solution that can be generalized across our customers.

@dario-pisanti Hi Dario, Thanks for sharing your issue. I'm also working with the Qualcomm Neural Processing SDK on VOXL2 Mini. The error you mentioned could be due to: Model compatibility issues during conversion. SDK configuration, especially for GPU. Double-check the GPU-specific settings in $SNPE_ROOT/bin/envsetup.sh and try running a simpler model to verify the GPU setup. Have you managed to resolve this, or do you have any additional details? I'm also trying to use the QNN SDK with ONNX runtime on VOXL2 Mini. Best, Manu

@AndriiHlyvko Thanks! We have merged in those changes.