@Kris I found and fixed a bug in voxl-camera-server that seems to be the culprit. I flashed my seeker with SDK1.2.0 and sideloaded the following voxl-camera-server with the bugfix to re-enable ingestion of TOF data into voxl-vision-hub http://voxl-packages.modalai.com/dists/apq8096/dev/binary-arm64/voxl-camera-server_1.9.7_202407111658.ipk Note VOA simply does not work in the default PX4 acceleration-based position mode so MPC_POS_MODE needs to be set to 0 (velocity control) as done by the voa_enable px4 param helper file here: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-px4-params/-/blob/dev/params/v1.14/voa_helpers/voa_enable_indoor.params?ref_type=heads

@Memmed-Shamurov we have draw.io based drawings here if you want to try to mock something up for review, we can take a look: https://gitlab.com/voxl-public/support/drawings VOXL2 Mini based drawings here: https://gitlab.com/voxl-public/support/drawings/-/tree/master/M0104

@Memmed-Shamurov it claims USB Video Support so it 'should' work although we've not tried this exact one.

@Gary-Holmgren Check out the AprilTag Relocalization page Basically, every time an AprilTag is viewed, the position is updated to reflect that tag as an anchor. So, it's not precision landing as much as position refinement. You then land at the desired position which should be more accurate due to the position refinement with the fiducial marker We haven't looked at the MAVSDK in a while, is there a specific error you're running into?

Great @jacob-yaacubov. Sorry for the issue overall, but glad we made it right.

@Gary-Holmgren Hi Gary, we have not thought to try that setup as HITL is typically used to develop the lower level flight controller. What are you trying to achieve?

@Eric-Katzfey I try, and show me this error: [image: 1720207747511-captura-de-pantalla-de-2024-07-05-15-27-53.png]

@Eric-Katzfey all the messages I got in QgroundControl are these: [image: 1720205542772-captura-de-pantalla-de-2024-07-05-13-40-36.png] [image: 1720205542796-captura-de-pantalla-de-2024-07-05-13-48-28.png] [image: 1720205542810-captura-de-pantalla-de-2024-07-05-13-47-26-1.png] [image: 1720205542825-captura-de-pantalla-de-2024-07-05-13-47-26.png] [image: 1720205542841-captura-de-pantalla-de-2024-07-05-13-41-01.png] [image: 1720205542862-captura-de-pantalla-de-2024-07-05-13-40-49.png] [image: 1720205542879-captura-de-pantalla-de-2024-07-05-13-40-41.png] [image: 1720205542904-captura-de-pantalla-de-2024-07-05-13-40-24.png] In the other side, the configuration and, services in the voxl are these: [image: 1720206486347-captura-de-pantalla-de-2024-07-05-13-52-40.png] [image: 1720206486374-captura-de-pantalla-de-2024-07-05-13-52-23.png] [image: 1720206486393-captura-de-pantalla-de-2024-07-05-13-50-47-1.png] [image: 1720206486416-captura-de-pantalla-de-2024-07-05-13-50-47.png] [image: 1720206486466-captura-de-pantalla-de-2024-07-05-13-50-31.png] Is posible, that the flight core 2 has been damage? or someting, or it's a configuration problem? because it's am worried when I try the usb connection with the same problem.

@Jeffrey-Mao Thank you for providing the update and the instructions!

@Alex-Kushleyev I have checked inference_helper and modify to handle RGB format successfully. [image: 1719806154374-screenshot-2024-07-01-113145.png]

@Alex-Kushleyev Good to know, Thankyou for clarifying Alex!

@Suvasis-Mukherjee We have succesfully integrated the D435i to stream video recently with the Voxl2 through ROS2. however this process is a bit involved with a few twists and turns, so it is possible

@hmlow we're still working through the product details of what should be included in the kit. We will try to get something into beta this week

@Alex-Kushleyev yes you can reference the log

@Denver-Bennett , sorry for the delay. Have you followed our documentation on this topic? https://docs.modalai.com/voxl2-io-user-guide/ The firmware needs to be updated, if it has not been done when you installed SDK 1.3.0. The following docs page tells you how to check and install the firmware : https://docs.modalai.com/voxl2-io-firmware/. The voxl2-io package should already be installed on voxl2 with SDK 1.3.0, so you should be able to use commands like: voxl-2-io scan voxl-2-io upgrade_firmware (here is the actual script : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl2-io/-/blob/master/scripts/voxl-2-io?ref_type=heads)

@blossomrd , this issue is most likely due to incorrect YUV line stride or plane stride for a specific resolution. That is to say, the ISP outputs a YUV image with certain line stride and plane stride (there may be some space between the Y and UV planes in order to align the image data for fast processing in hardware) and voxl-camera-server incorrectly interprets that information about the image layout. For anyone who is experiencing this issue, please post the exact conditions to reproduce: version of voxl-camera-server camera type used entire voxl-camera-server.conf config file explain how exactly you are getting the image (what MPA pipe) or viewing via voxl-portal and what resolution Thanks! Alex

@Samuel-Bryan Have you tried building the image on VOXL following these steps: https://gitlab.com/voxl-public/voxl-docker-images/voxl-docker-mavsdk-python#optional-building-the-image

@WineVirus @Moderator What part do I need to modify to automatically save it to the QGC area?