# Recovering research equipment after 6months with BlueROV2 **URL:** \ **Category:** General Discussion\ **Tags:** positioning\ **Created:** [June 10, 2022, 12:51am UTC](https://discuss.bluerobotics.com/t/recovering-research-equipment-after-6months-with-bluerov2/12299 "2022-06-10T00:51:59Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![EliotBR](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/eliotbr/32/6937_2.png) [@EliotBR](https://discuss.bluerobotics.com/u/EliotBR)\ **Post date:** [June 10, 2022, 8:04am UTC](https://discuss.bluerobotics.com/t/recovering-research-equipment-after-6months-with-bluerov2/12299/2 "2022-06-10T08:04:00Z")
Hi @Salome, welcome to the forum! 🙂 Sounds like an interesting (and hopefully fun) project! > [@Salome](#): > > A) how likely/challenging will it be to find these loggers again using a BR2 (considering I have no USBL or Sonar)? I’d say that depends on how accurate the initial position record is, and the visibility and current strength at the time of recovery combined with the skilfulness of the operator(s). > [@Salome](#): > > B) Do any of you have done anything like this at these depths? It’s not something I’ve personally done at those depths. [This retrieval example](https://discuss.bluerobotics.com/t/action-packed-weekend-at-lake-coeur-d-alene/10236) from @btrue may be worth a look, although your use-case is quite a bit deeper so will need lighting from the ROV to see what you’re looking for. > [@Salome](#): > > C) Is Anyone doing anything like this but with help of better tech: e.g. some kind of acoustic pinger that can be attached to the mooring with loggers and the ROV has some kind of receptor or sonar that can detect it? That may be possible, although depending on the constraints of the use-case it could be quite challenging to achieve. Hardware wise it would require at minimum a transmitter at the bottom (with the loggers) and a receiver on the ROV or the boat, but the most efficient and practical retrieval approaches would likely make use of both transmitting and receiving on each end. Behaviour wise the main approaches I can think of are: 1. bottom transmitter transmits at regular intervals, and is searched for and detected by the moving receiver - too frequently could be wasteful of power, and may cause confusion for other vessels that come by if they have a sonar sensor with a similar frequency, and could potentially be [disruptive to nearby marine life](https://discuss.bluerobotics.com/t/is-the-ping360-sonar-signal-harmful-to-humans/10285/2#hearing-2) - too infrequently could make searching and finding slow and challenging 2. bottom receiver waits for a transmission, and when it detects one it transmits back so it can be detected (resulting in faster ping-ponging as the sensors get closer) Beyond that, if you know you’ll only be searching after a set amount of time, or within a particular time period during each day, then that could be used to help save power by turning off the bottom sonar while it’s not needed (albeit potentially with some extra risk, because if your control computer somehow loses track of time it may change to a range that’s misaligned with the search time). Technologically speaking that kind of use-case could be achieved with a couple of [Ping Sonars](https://bluerobotics.com/store/sensors-sonars-cameras/sonar/ping-sonar-r2-rp/) being controlled by some Arduinos or Raspberry Pi boards or similar, although it would require custom firmware on the sonars to support the non-standard usage. At the moment we don’t provide firmware source code (i.e. that would allow adding custom messages and/or logic), so unless that changes custom firmware would need to come from us. The ~30 degree beamwidth on the Ping Sonar means detection would be possible within a radius of about 10m for an ROV 35-40m above the bottom transmitter 🙂 --- _[View the full topic](https://discuss.bluerobotics.com/t/recovering-research-equipment-after-6months-with-bluerov2/12299)._