# Ping 360 and Sonarview connection issue **URL:** \ **Category:** Ping Sonar Devices\ **Created:** [July 14, 2024, 9:00pm UTC](https://discuss.bluerobotics.com/t/ping-360-and-sonarview-connection-issue/17429 "2024-07-14T21:00:10Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![StrikeLines](https://avatars.discourse-cdn.com/v4/letter/s/0ea827/32.png) [@StrikeLines](https://discuss.bluerobotics.com/u/StrikeLines)\ **Post date:** [July 14, 2024, 9:00pm UTC](https://discuss.bluerobotics.com/t/ping-360-and-sonarview-connection-issue/17429/1 "2024-07-14T21:00:10Z")
I’m having some trouble getting our Ping360 to work with the cerulean sonarview extension in BlueOS 1.2.6. My Ping360 is wired in USB configuration. If I connect the usb cable to my desktop PC, I am able to successfully start the Ping360, hear the device operating, and view sonar data with the BlueRobotics Ping Viewer application. When plugged in to the companion computer (raspberry pi 4) the Ping360 is recognized in BlueOS, and detected by the SonarView application. But after I connect and click start, the sonar never actually starts spinning and transmitting. No data ever appears on the SonarView display. If I zoom way in, I can see a weird yellow submarine, but that’s it. I am not using the default companion IP address under 192.168.x.x. But I have been able to get everything else (video, telemetry, controls, etc) communicating correctly on my local network subnet 10.10.10.X. Is there anything I’m missing to get the Ping360 running on BlueOS? ![ping sonar devices expanded](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/f/fbd7e15160fc62ddbe17846b999fe64e4ccc047d.png) ![app settings](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/b/b9c1af29aef399a4e1a04be0c82e6cef7dcceb8e.png) ![sonarview](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/5/5a0270cb845e8407ca3d8de0743ac8b3e1b6d79e.png) ![sonarview 2](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/e/ed6656d5fdcf21ff4439248b6467ffdec10d4e77.png) ![sonarview zoomed in](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/e/ef807bfb922c99b45a26876c1e0e75b7ffc4c024.png) ---
**Author:** ![tony-white](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/tony-white/32/18385_2.png) [@tony-white](https://discuss.bluerobotics.com/u/tony-white)\ **Post date:** [July 15, 2024, 1:35am UTC](https://discuss.bluerobotics.com/t/ping-360-and-sonarview-connection-issue/17429/2 "2024-07-15T01:35:00Z")
Hi @StrikeLines - Does the Ping360 (via USB) work as expected via PingViewer when connected to the BlueOS device via network connection? If so, then the issue may be with Cerulean’s SonarView… ---
**Author:** ![StrikeLines](https://avatars.discourse-cdn.com/v4/letter/s/0ea827/32.png) [@StrikeLines](https://discuss.bluerobotics.com/u/StrikeLines)\ **Post date:** [July 15, 2024, 1:53am UTC](https://discuss.bluerobotics.com/t/ping-360-and-sonarview-connection-issue/17429/3 "2024-07-15T01:53:59Z")
I want to make sure I understand what you are describing… I am using a desktop computer on our WiFi network to connect to the BlueOS companion computer, which is also on the WiFi network. Are you saying that once I am connected to BlueOS, I can open PingViewer on my desktop computer, and it will automatically connect to the Ping360 over the network? Even though the Ping360 is configured as a USB device on the companion computer? ---
**Author:** ![StrikeLines](https://avatars.discourse-cdn.com/v4/letter/s/0ea827/32.png) [@StrikeLines](https://discuss.bluerobotics.com/u/StrikeLines)\ **Post date:** [July 15, 2024, 3:07pm UTC](https://discuss.bluerobotics.com/t/ping-360-and-sonarview-connection-issue/17429/4 "2024-07-15T15:07:00Z")
OK, this morning I tried PingViewer, and I was able to successfully connect to the Ping360 and view sonar data over the local network. ![ping viewer works over network](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/d/d5d9cd9546c95219825420c4966694aba22b476d.png) So I guess I need to reach out to Cerulean with the bug report? For anyone else who may find this, here’s how you can use BlueRobotics Ping Viewer to connect to a Ping sonar over the network. Once you’re connected to BlueOS in a web browser, open up Ping Viewer on your desktop. Change Communication to UDP. For UDP Host/port: put the IP address of your BlueROV on the local network, and put the port displayed on the “Ping Sonar Devices” menu of BlueOS. ![pingviewer network settings](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/4/4b92afd1e56f744fa48ee5e0eb4c0b3d192b90d1.png) ---
**Author:** ![ljlukis](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/ljlukis/32/3983_2.png) [@ljlukis](https://discuss.bluerobotics.com/u/ljlukis)\ **Post date:** [July 15, 2024, 3:21pm UTC](https://discuss.bluerobotics.com/t/ping-360-and-sonarview-connection-issue/17429/5 "2024-07-15T15:21:44Z")
This is a Ping360 f/w version issue. We updated SonarView to use the new auto\_transmit capability published here: [ping360 - Ping Protocol](https://docs.bluerobotics.com/ping-protocol/pingmessage-ping360/) B/R, what do we know about user’s ability to update the P360 f/w? ---
**Author:** ![StrikeLines](https://avatars.discourse-cdn.com/v4/letter/s/0ea827/32.png) [@StrikeLines](https://discuss.bluerobotics.com/u/StrikeLines)\ **Post date:** [July 15, 2024, 3:27pm UTC](https://discuss.bluerobotics.com/t/ping-360-and-sonarview-connection-issue/17429/6 "2024-07-15T15:27:28Z")
Thanks for the reply! I can confirm I’m on firmware 3.1. ---
**Author:** ![ljlukis](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/ljlukis/32/3983_2.png) [@ljlukis](https://discuss.bluerobotics.com/u/ljlukis)\ **Post date:** [July 15, 2024, 3:41pm UTC](https://discuss.bluerobotics.com/t/ping-360-and-sonarview-connection-issue/17429/7 "2024-07-15T15:41:43Z")
We think it’s V3.3.5 that you need. If necessary we will revert the SonarView P360 code to the earlier version. ---
**Author:** ![StrikeLines](https://avatars.discourse-cdn.com/v4/letter/s/0ea827/32.png) [@StrikeLines](https://discuss.bluerobotics.com/u/StrikeLines)\ **Post date:** [July 15, 2024, 8:30pm UTC](https://discuss.bluerobotics.com/t/ping-360-and-sonarview-connection-issue/17429/8 "2024-07-15T20:30:02Z")
Tony, I found this firmware repository: [GitHub - bluerobotics/ping-firmware: Repository for binary files associated with ping devices](https://github.com/bluerobotics/ping-firmware) What is the procedure for flashing a firmware update to the Ping360? ---
**Author:** ![tony-white](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/tony-white/32/18385_2.png) [@tony-white](https://discuss.bluerobotics.com/u/tony-white)\ **Post date:** [July 18, 2024, 7:06pm UTC](https://discuss.bluerobotics.com/t/ping-360-and-sonarview-connection-issue/17429/9 "2024-07-18T19:06:41Z")
Hi @StrikeLines - That process is not yet possible to do - we’ll be sure to have a guide available when it is! This will coincide with the release of the next version of PingViewer, the current version does not support this. Sorry for the news! I think the issues you were initially having were related to your non-standard network subnet, and Cerulean jumped the gun slightly in supporting unreleased functionality - @ljlukis I would think revering SonarView to previous code would be the best bet for a bit longer. Apologies! ---
**Author:** ![ljlukis](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/ljlukis/32/3983_2.png) [@ljlukis](https://discuss.bluerobotics.com/u/ljlukis)\ **Post date:** [July 20, 2024, 9:58pm UTC](https://discuss.bluerobotics.com/t/ping-360-and-sonarview-connection-issue/17429/10 "2024-07-20T21:58:34Z")
We’ll update SonarView to support both versions, but it will be another week before I’m in the same place as a P360, so it’ll be a bit. ---
**Author:** ![ljlukis](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/ljlukis/32/3983_2.png) [@ljlukis](https://discuss.bluerobotics.com/u/ljlukis)\ **Post date:** [August 1, 2024, 3:34pm UTC](https://discuss.bluerobotics.com/t/ping-360-and-sonarview-connection-issue/17429/11 "2024-08-01T15:34:45Z")
Here is a SonarView update which has the Ping 360 f/w version issue resolved. > **[Release 1.10.0-beta.12 · CeruleanSonar/SonarView](https://github.com/CeruleanSonar/SonarView/releases/tag/v1.10.0-beta.12)** > > Contribute to CeruleanSonar/SonarView development by creating an account on GitHub. ---
**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:** [July 22, 2025, 6:16am UTC](https://discuss.bluerobotics.com/t/ping-360-and-sonarview-connection-issue/17429/12 "2025-07-22T06:16:43Z")
> [@ljlukis](#): > > B/R, what do we know about user’s ability to update the P360 f/w? This is possible as of Ping Viewer 2.6.0. We have also now [released the new Ping360 firmware](https://discuss.bluerobotics.com/t/ping360-firmware-update/21023), with support for the `auto_*` messages 🙂