Additionally I’m wondering about the OSD element OSDn_RNGF (also showing nothing for me): Is it supposed to show the same rangefinder reading that should show up as sonarrange, or the reading for rangefinder1? And are rangefinders1-4 actually proximity sensors?
Ok thanks, so then I should set prx_type to zero I guess? Will I still get simple object avoidance in that case? (Because that’s what I want to test, like in the demo video with the umbrella a while ago.)
To be honest, I think I still don’t fully get the difference between rangefinder and proximity. From what I understand from the wiki, proximity is 360° and provided either by a real 360° sensor or a combination of up to 10 rangefinders - yet there are only 4 listed in MP Status, presumably meant for front/back/left/right? Rangefinder on the other hand is described as a narrow beam. Can 4 narrow beams really replace a full 360° scan?
Thanks again, last question: There is an RC_OPTION named Rangefinder. On the copter I’m trying this out I used to get (probably before misconfiguring the rangefinder as proximity at some point) a message “Rangefinder low/middle/high”. What does it actually do? The range is fixed as far as I know (30cm to 5m in my case).
As for how to set it up, I’d especially like to see the rangefinder OSD value, so I always know it’s working. As it looks now, this will only be possible by setting it as rangefinder. So best for me would be object avoidance + OSD value, but I’ll test that later today.