@Alex-Kushleyev , I think that is plenty for now. We will order a couple and test them. Thanks a lot!
Latest posts made by david.moro
-
RE: Next-gen TOF sensor specs
-
RE: Next-gen TOF sensor specs
@Moderator , @Alex-Kushleyev , thanks a lot! Please keep us posted!
-
RE: Next-gen TOF sensor specs
@Moderator, do we have any more specs of this module? Weight, power? Also, is there an ETA for it to be in production?
Regards,
-
Next-gen TOF sensor specs
Hi @Moderator, we are looking to integrate the ToF sensor in one of our drones and we just found out it is EOL. According to the product page, you are working on a replacement. Would you be able to share any details on it? Is it larger/smaller? heavier/lighter? Does it have similar range? Thanks!
-
RE: OV9782 VIO parameters
@SMRazaRizvi We did not. But the more I look at the qualcomm API for mvVISLAM the more I think there is aren't very many knobs to turn.
-
M0113 Image fipped
We successfully installed a VOXL2 and OV9782 for tracking on a vehicle. When trying to replicate the setup on a second vehicle we found out that the image is upside down. The mechanical design does not have room to rotate the sensor. Can this be done in software?
Thanks
-
RE: OV9782 VIO parameters
@Moderator. en_auto_reset is true for these flights. What we see is that once a reset kicks in, it has a hard time staying stable. My question above is more along the lines of how to make the vio algorithm not drop points so aggressively. That is what the images above show.
Cheers!
-
RE: OV9782 VIO parameters
@david-moro . Quick follow-up.
We are doing testing up to 400ft with moderate success. One thing we notice is that the qvio algorithm can struggle to converge after a reset. I attach two picture. On the first one, right after the reset, there are 25 points being tracked.
A few seconds later, this drops to 3 points. The vehicle barely moved between frames.
A few seconds after this the qvio reset again. This behavior is very common once the first reset happens. Up until that point, if we take it easy, we can fly at 400ft without any issues. Could this be related to mistuned parameters? In particular, what is the effect of cam_noise_std_dev, min_std_pixel_noise and fail_high_pixel_noise_points? Can those be used to trade robustness for accuracy?
Thanks!
-
RE: Add mask file to QVIO algorithm
@Alex-Kushleyev . Just went through the process of compiling the code and pushing it to the VOXL2. I can confirm the mask works (i.e. no new points in the masked region, however, points can move into it if captured before). One thing to note is that the qvio server did not complain when the file was missing. Maybe I am not looking at the right output though.
Thanks a lot for the help!
-
Voxl2 mini support for OV9782 tracking sensor
Hi ModalAI!
I wanted to ask about the OV9782 sensor (MSU-M0113) on the VOXL2 mini. It is not explicitly supported in the documentation. Thanks!