TOF sensor quailty down after upgrading to VOXL 1.3
-
I have two Starling drones, one running VOXL-SDK 1.1.2 and the other running VOXL-SDK 1.3. I've noticed a significant difference in the depth output from the TOF sensor between the two drones. The drone with the newer VOXL version is producing poorer depth data, even though both drones are running at the same 15 FPS and have identical quality settings. I'm trying to understand the cause of this issue and explore ways to improve the depth output on the drone with the newer VOXL version.
Below are the images attached.
-
I have two Starling drones, one running VOXL-SDK 1.1.2 and the other running VOXL-SDK 1.3. I've noticed a significant difference in the depth output from the TOF sensor between the two drones. The drone with the newer VOXL version is producing poorer depth data, even though both drones are running at the same 15 FPS and have identical quality settings. I'm trying to understand the cause of this issue and explore ways to improve the depth output on the drone with the newer VOXL version.
Below are the images attached.
@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
-
S Shivam Sehgal referenced this topic on
Reading along? Create a free ModalAI Forum account to join in.
With an account you can reply, ask your own question, get an email when a ModalAI engineer answers, and mark the reply that solved it. Your place in each thread is saved between visits.
Questions about VOXL, Flight Core, ESCs and ModalAI drones are answered here by the engineers who build them.
Register Login