# Ping Sonar Python code

**URL:** <https://discuss.bluerobotics.com/t/ping-sonar-python-code/5280>\
**Category:** General Discussion\
**Created:** [June 12, 2019, 2:30pm UTC](https://discuss.bluerobotics.com/t/ping-sonar-python-code/5280 "2019-06-12T14:30:29Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![randylewis7](https://avatars.discourse-cdn.com/v4/letter/r/90db22/32.png) [@randylewis7](https://discuss.bluerobotics.com/u/randylewis7)\
**Post date:** [August 20, 2019, 7:18pm UTC](https://discuss.bluerobotics.com/t/ping-sonar-python-code/5280/11 "2019-08-20T19:18:08Z")

</div>

Hello, I also emailed support about this issue, and they pointed me to the forums. It occurs to me that this may be a different issue than the original one above, so I made a separate forum post here to continue the discussion:

> [@Ping Sonar Measurement Latency](https://discuss.bluerobotics.com/t/ping-sonar-measurement-latency/5810):
>
> Hello, I am attempting to integrate the ping sonar onto the blue ROV 2. However, I have noticed that the sensor’s readings lag significantly. I emailed support about this, and they said that this is not expected. They suggested that I go back to the basic ping-python exampe, and the ping-viewer application. So I did that. In ping viewer, the measurement lags by about a second behind reality. I measured this by moving the ping quickly between two positions in water, and having a colleague start …

I collated everything we have tried there.

---

_[View the full topic](https://discuss.bluerobotics.com/t/ping-sonar-python-code/5280)._
