hello,
Do you find the solution for ping 360 by the ethernet switch from blue robotics?
@Ibrahim @Jnyberg did you ever get to the bottom of this issue? We have exactly the same issue and can replicate all that you found.
Cheers
Matt
Not sure how this got dropped off, but it sounds to me like a faulty ethernet switch (using any of the interfaces to any of the ports should be equivalent, as long as you’re not making multiple connections to the same port), in which case it’s likely best handled via our Product Problems form.
In case it’s relevant, my ethernet switch has
| Port | Type | Connection |
|---|---|---|
| 1 | RJ-45 | Raspberry Pi |
| 4 | JST-GH | Ping360 |
| 5 | RJ-45 | Fathom-X |
and works consistently, with detection both in BlueOS and Ping Viewer 
Hi Eliot,
We’re in discussion with tech support. We’ve tried 2 different ping360s and switchs with multiple port configurations all seem to result in lots of dropped packets from the ping360 when it is passing through the switch and very poor rates ~4000 bps in pingviewer instead of 60k+ bps when connected without the switch.
Cheers
Matt
1 Like
Hi- I am also having the same problem. Here is where I currently stand- ping360 works direct connect from sensor via usb to topside computer. However, intermittently it shows up via Ethernet to topside computer when I manual search. It seems it only responds when I ping it- I get a reply of 192.168.2.4 but there is no transmit from the sensor. When it does occasionally pop up as available it never populates data or sensor info.
While connected via usb, the sensor automatically transmits.
I’ve removed the ROV/tether from the scenario except for direct power to the sensor from the ROV.
Any help is most appreciated!
Hi @sciboticsamy, welcome to the forum
My main recommendations are to
- make sure the onboard computer IP is on the same subnet as the Ping360 (e.g.
192.168.2.xif the Ping360 is assigned to192.168.2.4) - make sure nothing else on the network is assigned to the exact same IP address or port as the sensor (to avoid address conflicts)
As above, if that doesn’t help I’d recommend you submit a support request via our product problem form.
Hi Eliot, Thanks!
I’m all set now. I had exhausted all the potential issues for UDP sensor integration issues already. I was told there is a known hardware issue and was sent a tested kit two weeks ago. I switched out the board on the sonar first and all is working now.
2 Likes