# Ping1D not always detected in Pingviewer

**URL:** <https://discuss.bluerobotics.com/t/ping1d-not-always-detected-in-pingviewer/19833>\
**Category:** Blue Robotics Products\
**Tags:** ping\
**Created:** [March 20, 2025, 2:46pm UTC](https://discuss.bluerobotics.com/t/ping1d-not-always-detected-in-pingviewer/19833 "2025-03-20T14:46:44Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![eri3t](https://avatars.discourse-cdn.com/v4/letter/e/dfb087/32.png) [@eri3t](https://discuss.bluerobotics.com/u/eri3t)\
**Post date:** [April 30, 2025, 9:43am UTC](https://discuss.bluerobotics.com/t/ping1d-not-always-detected-in-pingviewer/19833/4 "2025-04-30T09:43:16Z")

</div>

Hi, I’d like to follow up on this issue, as no significant improvements have been made. As I said earlier, we have a BlueROV2 R3, we’re connecting to ping1d through USB to serial adapter, we’re using BlueOS 1.3.1 and we recently upgraded Ardusub to v4.5.3.

Yesterday I couldn’t connect to the echosounder using either PingViewer or BlueOS (through “ping sonar devices”). I’ve tried to connect it manually following [this video](https://www.youtube.com/watch?v=nJz9Ex-yCYQ) from [this post](https://discuss.bluerobotics.com/t/connection-problems/8274) with the following configuration:  
 → Device: Ping1D  
 → Communication: UDP  
 → UDP Host/Port: 192.168.2.2:9090

After trying the ROV in a pool (ping1D not detected), I connected the ROV again in my house, and ping1D was working/detected! What is happening?? I haven’t changed anything, and suddently it works?? Probably it has nothing to do with this, but upgrading Ardusub has caused some misconfiguration in the autopilot output channel configuration, maybe it afects other things?

The truth is that I have a number of issues in BlueOS: sometimes cockpit doesn’t appear in the menu (it looks like if it wasn’t able to charge, and I have to refresh the BlueOS page), or cockpit stops working while piloting the ROV (a “page not found” message appears). Imagine this happening during a open water mission! For the moment, QGC seems more reliable in this sense. Could all these issues be related?

Following the indications of @tony-white in [this post](https://discuss.bluerobotics.com/t/failed-to-fetch-available-firmware-error-in-blueos/19892) (see below), I attach a screenshot of the surftrak fixit page:

> [@"Failed to fetch available firmware" error in BlueOS](https://discuss.bluerobotics.com/t/failed-to-fetch-available-firmware-error-in-blueos/19892/2):
>
> Once you have the ROV working as expected, we can dig into what might be the issue for your UGPS and Ping. The latter can be configured with assistance from the “surftrack fixit” extension, which validates parameters necessary for the ping sonar to send distances to the autopilot necessary for the (new) SurfTrack flight mode.

 ![WhatsApp Image 2025-04-30 at 09.49.59](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/7/737c2f8fa7eba0b074cf688f1b1e4cc24b426ef1.jpeg)  
Could someone help me understand what these messages mean?  
Thanks in advance.

---

_[View the full topic](https://discuss.bluerobotics.com/t/ping1d-not-always-detected-in-pingviewer/19833)._