Were you able to find a resolution to this? We are also experiencing the exact same issue has you. IMU is coming in around 220 Hz and there is alot of dropped data and timestamp jumping. Check out this sample graph below.
imu-timestamp.png
@Ariel-Young Thanks the new camera server works. The only thing is we still see the wierd repeating part in the image when using the snapshot function (top image), is this something you also see?
If it is a carbon fiber frame, you are better off mounting directly. Carbon fiber has great vibration characteristics, likely better than anything a dampener could do
@Amisha-Bhaskar However, it won't revert to 0 if you change it. The parameters that you update are saved in the file /data/px4/param/parameters. Do you have that file in your filesystem?
@elfowl currently, we have to use a proprietary Qualcomm toolchain to generate camera binaries... we would need to add this setting. Our goal is to open up this area such that we can all customize as needed but we don't have this functionality yet. The framework we are using is in general setup for phone manufactures to add a sensor or two to a phone to known locations, so we are kind of hacking it to allow folks to add numerous types to up to 6 locations, which involves removing some onion layers 😉
Here are the instructions for how to use voxl-uvc-server. Make sure you are correctly specifying the resolution and frame rate. The Stereolabs ZED doesn't output 640x480 30fps. https://docs.modalai.com/voxl-uvc-server/