Topics created by Shivam Sehgal

@Shivam-Sehgal , it seems you are using VOXL SDK that is more than one year old, please upgrade to the latest 1.3.5.

If you are not able to upgrade, then please try the following:

reduce the width/ height of hires camera large video stream to 3840x2160, if that does not help, reduce the FPS of hires camera to 25Hz disable snapshot if you are not using that feature try starting voxl-camera-server manually and assign upper cores 2-7 to the process, which helps with stability stop camera server running in the background (if applicable) : systemctl stop voxl-camera-server run camera server and assign cpu affinity using taskset : taskset -c 2-7 /usr/bin/voxl-camera-server

Alex

@Shivam-Sehgal Re-calibrating cameras if the calibration files are lost requires a precise calibration board which many customers don't have, which is why we back them up in our database before shipping the drones. These calibration files (extrinsic and intrinsic) are specific to each drone.

gyro, accel, and other sensors can be easily re-calibrated on the bench by the user without any extra peripherals.

@Shivam-Sehgal No, there is no Starling model in Gazebo.

@Moderator any advice?

@Shivam-Sehgal , I believe the TOF processing settings may have changed between SDK 1.1 and 1.3 (more noise filtering was added).

In both cases, the ground is visible (although hard to see in the black image). In the 1.3.0 case, the other vehicle is not visible in TOF output, but there is less noise.

Are you able to test the two SDK versions with some easy features for TOF sensor to pick up? Some large objects with simple geometry and some small objects.

Alex

@Shivam-Sehgal , does it look like the board is rebooting after 10 seconds of running with cameras enabled? also, what if you ssh into the board, does the SSH connection stay alive when the cameras are connecting?

Also, how are you powering the drone for this test - battery or power supply?

Alex