Drivers: Add TeraRanger Evo 600Hz support #9169
Conversation
|
Nice! The new Evo has the same I2C address as the existing one, correct? This breaks the auto-detection of which TeraRanger is connected. We should either remove the auto-detection or document that it will always assume the 60m Evo. |
|
@ndepal that's correct, the addresses and whoami's will be the same for all sensors in Evo family. How important are the minimum and maximum ranges from the flight control perspective? We were hoping that for users that are likely to test multiple sensors we could leave autodetection that provides minimum and maximum distances across the whole Evo family of sensors (e.g. 0.1-60m). I'm more than happy to document this functionality if that's something we want. |
|
It would be great if we could update the docs: https://docs.px4.io/en/sensor/rangefinders.html#teraranger-one Also excellent if the driver could get some in-source docs that can are generated here - you can see how this is done in the Module Template and in the GPS driver here: |
|
@msadowski auto-detection sounds interesting. Were you thinking an additional parameter to enable it? |
|
Base driver changes look good. We can do another PR to if for module documentation. |
|
@dagar Thanks for the merge! I don't know if understood your comment on auto-detection. What kind of parameter do you have in mind? There is already an Autodetect parameter in SENS_EN_TRANGER. |
|
Ah, I didn't see the existing autodetection option. |
Hi!
We are soon launching a new TeraRanger Evo sensor (Evo 600Hz) and we thought it is a good idea to create a new option for SENS_EN_TRANGER that will correctly represent the minimum and maximum distance of this new sensor.
We also renamed the previous option to TREvo60m (previously just Evo).
If there is anything else you wold like us to update please don't hesitate to ask and someone from our team will work on it.