Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AP_Proximity: TeraRanger Tower Evo support #8732

Merged
merged 5 commits into from
Aug 25, 2018

Conversation

msadowski
Copy link
Contributor

This pull request adds support for TeraRanger Tower Evo. There are lots of changes compared to the TeraRanger One driver (e.g. clockwise sensor order, a need to request modes and initialize streaming) hence to keep the backwards compatybility we created a new driver (Proximity Type: 6).

The driver has been tested in an indoor scenario in AltitudeHold mode and it worked beautifully. Please, feel free to let us know if you would like to see anything changed.

@pl-kabaradjian
Copy link
Contributor

Hello @rmackay9, here is a friendly ping for this request as we didn't have any update since its opening.
Also we are about to launch Teraranger Tower Evo and we would like to know how far is the next release to inform our customer that they can use official version for this product (and not manually build our repository)

Cheers and thanks in advance for your time,

@rmackay9 rmackay9 requested a review from OXINARF July 28, 2018 00:00
@rmackay9
Copy link
Contributor

rmackay9 commented Jul 28, 2018

@pl-kabaradjian, @msadowski,

Thanks for this. I've had a quick look but need to do a more complete review. I'm aiming to get this included in Copter-3.6. In the next release candidate if we can get it into master in time, failing that, the release candidate after the next one.

@pl-kabaradjian
Copy link
Contributor

Thanks @OXINARF and @rmackay9!
We greatly appreciate your help on this. By the way, here is a preview video of the collision avoidance in action with our new product TeraRanger Tower Evo if you're interested. It is always nice to see the code in action!

@charleslinquist
Copy link

There are so many object avoidance systems available, all with a different range, FOV, cost, etc. And all with a different interface.
Wouldn't it be easier to define a standard and then use a small uC (Arduino, ARM, PIC) to iniitialize the sensor and convert the output for the FC? The uC could buffer the data and the FC could poll at whatever rate (10Hz?) was convenient. I don't know which hardware interface would be best for the existing code, but I2c would seem like a good option. Some sensor manufacturers might eventually add the new "Environment Condition" protocol as a standard, eliminating additional hardware.

@rmackay9 rmackay9 merged commit bf274cd into ArduPilot:master Aug 25, 2018
@rmackay9
Copy link
Contributor

very nicely written as far as I can tell. Merged, thanks!

@pl-kabaradjian
Copy link
Contributor

Thanks for your time, much appreciated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Copter 3.6 Backports
  
3.6.0-rc8
Development

Successfully merging this pull request may close these issues.

None yet

5 participants