Will the blades spinning affect collision prevention?

AP123

Will the blades spinning affect collision prevention? For some reason when i have it enabled the drone will not move while hovering. I open the stereo screen on the VOXL portal and i do see the blades there.If that is the reason it wont move what do you suggest? I have the flight deck mounted on a S500 HolyBro. Should i reposition the stereos within the Voxl 2 or is there a way to shorten the line of sight at all in the code for the stereos?

Moderator

@AP123 what do you see when you open the DFS images in voxl-portal? If there are obstacles appearing, then it will trigger collision prevention

AP123

@Moderator Yes i see them on the Voxl portal under stereo rear and front is there a way i can shrink the stereo image scope? or must i get smaller props?

AP123

@Moderator Please tell me how i can narrow the frame of the stereo in the code.

Alex Kushleyev

@AP123 you can try decreasing the maximum disparity in the DFS server, please see the following:

https://gitlab.com/voxl-public/voxl-sdk/services/qrb5165-dfs-server/-/blob/master/src/config_file.h?ref_type=heads#L67 . The config file for DFS is located here : /etc/modalai/voxl-dfs-server.conf -- you can update the param.

Since the propellers are very close to the cameras, the disparity for those pixels will be very large. Decreasing maximum disparity should help filter out points that are too close.

Alternatively, you can look into the collision prevention code and add logic to ignore points that are too close.

Finally you can modify the DFS code to just blank out the (rectangular) part of image that sees the propellers before processing. I do not know if a mask is supported, but setting a certain area to 0 or 255 should achieve the effect of "ignoring".

I would try decreasing the maximum disparity first, that is the easiest, but not too much since you could be ignoring true obstacles.

@James-Strawson anything else @AP123 can try?

Alex