Hi @Tejas-Shah . Yes you can. We are using AT10 right now for ouru work.

@scottesicdrone
The problem is because fastboot command needs root to run properly or else it wont detect device in bootloader.

refer this for more info about running it without root.
https://docs.modalai.com/setup-adb/

or simply run install.sh script as root.

Thank you so much for this. This was of great help @Chad-Sweet

@Prasad-Antervedi as far as I rember we calibrated the stereo cameras and then pushed the resulting files into voxl.

@Chad-Sweet Thanks for the reply. I actually wanted to test landing feature. If we could get the instruction for landing on the apriltag, that'd be great.

Hi, we are trying to implement obstacle avoidance feature on our VOXL flight deck. The documentation provided is for collision prevention where we set 4 parameters in PX4 and enable the VOA flag in the configuration file. However, as per PX4 documentation, collision prevention works in position flight mode. However, we are trying to run our code in offboard flight mode, and while testing, we confirmed that it doesn't work with the offboard flight mode.

Is there any separate documentation that we can see what changes can we do on the VOXL side to enable obstacle avoidance in Offboard flight mode?

@Alex-Gardner the issue is solve. The imu0 was not working, so by switching to imu1, it worked. Thanks for the help.
But we don't know why imu0 is giving very off values compared to imu1 , its a new voxl board that we have.

@Alex-Gardner this is the orientation of the boards which look fine to us. I'm attaching the picture. For the image that attached , the imus value are 0,0,-9.8. We checked this on QGC on highres_imu

HI. I'm working on just the VOXL board and I've integrated my own Pixhawk 4 flight controller. When I'm trying to print the odometry on the terminal by doing the command "voxl-vision-px4 -o" I'm getting this ```
WARNING initializing VIO gravity correction, system not level enough

What could be the possible reasons for this? I've done caliberation numerous times now making sure everything is correct and the overall system does look level. I have placed the Pixhawk on top of the VOXL board. I also tried disconnecting the pixhawk 4 connections (Power and communication port) with the VOXL, to check if this changes anything on VOXL, but the result is still the same.
Is there anything else that I should be looking at?

@Alex-Gardner I want to check the stereo disparity. However, when I do the voxl streamer -c dfs-server, the stream is getting stuck on the the VLC media player. How do I see the disparity output?

@Alex-Gardner its now perfectly running on boot up. Thanks for the help.

Update - we are able to get the obstacle data printed on the terminal. But this only comes when we run the voxl-dfs-server in one terminal and then run voxl-vision-px4 -s in other terminal.
Do we have to always run voxl-dfs-server in one window for this?

Update - we were able to push the opencv_intrinsics.yml. But when I do voxl-inspect-services, it still shows dfs server enabled, but not running.