Ping360 not connecting

Blue Robotics Products Ping Sonar Devices
1

Hi,

I have been having issues trying to connect to the ping 360 both ways directly via usb or through the ROV. Manual connection doesn’t work either. Using the most recent version of ping viewer. Any help would be appreciated.

connection
connection1920×1080 91.4 KB

Thanks

2

Hi @keshavr, welcome to the forum! :slight_smile:

Sorry to hear you’ve been having connection issues. To get some context:

  1. Is this the first time you’ve tried to use the Ping360, or was it working previously and has now stopped working?
  2. Are you using this with a BlueROV2, or some other setup?
  3. Are you using the default (USB) communication setup, or one of the alternatives (ethernet/RS485)?

To start with, I’d recommend you go through our PingViewer troubleshooting docs. If you’re using an ROV with our companion computer, when you’re trying to connect the Ping360 via the companion you can check the companion web interface System page (on your surface computer) - there should be an ‘Active Service’ called Ping360-id-1 or similar, and a ‘Detected Device’ called FT.... If you start the companion before the Ping360 has power then the detected device might show up (and will disappear if you unplug it) but the active service likely won’t show up at all (it only tries to detect on companion startup).

3

Thanks for the help. Starting the companion after the Ping360 solved the issues.

1 Like
4

Hi,

I have the same problem as described in the original question. PingViewer cannot find the sonar. I have the default configuration.
How do you start the companion computer after the ping360? I am just connecting the battery to the ROV. Should I do something different?

Ping360-id-1 service doesn’t show up.

By the way, I am using companion version 0.31

I get this output from Ping viewer:

[16:56:02.077] ping.protocol.protocoldetector[Debug]: UDP socket disconnected.
[16:56:02.077] ping.protocol.protocoldetector[Debug]: Probing UDP: "LinkConfiguration{Name: BlueRov2 Ping360 Port, Sensor: UNKNOWN, LinkType: UDP, Arguments: (192.168.2.2:9092)}"
[16:56:02.082] ping.protocol.protocoldetector[Debug]: ""
[16:56:02.082] ping.protocol.protocoldetector[Debug]: Socket is not in connected state.
[16:56:02.082] ping.protocol.protocoldetector[Debug]: "Error (0): Connection refused."
[16:56:02.082] ping.protocol.protocoldetector[Debug]: UDP socket disconnected.
[16:56:02.082] ping.protocol.protocoldetector[Debug]: Probing UDP: "LinkConfiguration{Name: Development port, Sensor: UNKNOWN, LinkType: UDP, Arguments: (127.0.0.1:1234)}"
[16:56:02.083] ping.protocol.protocoldetector[Debug]: ""
[16:56:02.083] ping.protocol.protocoldetector[Debug]: Socket is not in connected state.
[16:56:02.083] ping.protocol.protocoldetector[Debug]: "Error (0): Connection refused."
[16:56:02.083] ping.protocol.protocoldetector[Debug]: UDP socket disconnected.
[16:56:02.083] ping.protocol.protocoldetector[Debug]: Probing UDP: "LinkConfiguration{Name: , Sensor: Ping1D, LinkType: UDP, Arguments: (192.168.2.2:1234)}"
5

Hi @rezenders,

That should generally work ok, although if it doesn’t then you can try rebooting Companion via the web interface (top right corner), since that only restarts the Raspberry Pi, and not the Ping360.

If the service doesn’t show up in Companion then that means it’s not forwarding the signal to the topside, so Ping Viewer won’t be able to find it.

Good to know :slight_smile:

If you’re not already you should also make sure you’re using the latest version of Ping Viewer, but that’s only relevant once Companion is actually recognising and forwarding the device connection :slight_smile: