# I would like to inquire about the Ping2 product **URL:** \ **Category:** Ping Sonar Devices\ **Tags:** ping\ **Created:** [April 1, 2025, 6:35am UTC](https://discuss.bluerobotics.com/t/i-would-like-to-inquire-about-the-ping2-product/19945 "2025-04-01T06:35:08Z")\ **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:** [April 1, 2025, 7:55am UTC](https://discuss.bluerobotics.com/t/i-would-like-to-inquire-about-the-ping2-product/19945/2 "2025-04-01T07:55:57Z")
Hi @mrpk, welcome to the forum 🙂 There’s a 0.3 minimum range the device is capable of detecting (due to ringing vibrations from the pulse transmissions), but you’re past that, and it shouldn’t cause a distance estimate offset. As I understand it the distance estimates are from the transducer location, which is roughly at the face of the sonar. The main ideas I can think of around measurement error here are - there are objects within the sonar beam that are closer than the point you were measuring to visually - the surface you are measuring has a gradual density change, or the sonar return signal is saturated, so the visual edge of the surface does not align with the results from the sonar’s density estimation algorithm - this may be visible in the profile data - there is some potentially relevant discussion in [this thread](https://discuss.bluerobotics.com/t/interpretation-of-sonar-raw-data/11722/4) - the [speed of sound of the water](https://bluerobotics.com/learn/speed-of-sound-in-water-calculator/) is substantially different from what you have configured - this would cause a scaling error for all your measurements in that location --- _[View the full topic](https://discuss.bluerobotics.com/t/i-would-like-to-inquire-about-the-ping2-product/19945)._