Unable to connect with Ping360 via ethernet

Rickj8rick62

1

4h

I have not been able to connect to my ping360 via the ethernet switch on my BR2.

When I have changed my network adapter settings to use 192.168.2.1. I connect to the Rov just fine. I start ping viewer, and the ping360 pops up quickly. But it shows (I think) a self provided ip 169.254.241.14., has the gear symbol, and a green dot. However I have not been able to get it to take the static ip 192.168.2.4:12345. Neither can I connect to it.

I have for an experiment, changed the adapter settings to automatically create an ip. I then can connect thru the tether/communication board/ethernet switch/ ping360 with no problem, with ping viewer. I think I had the rspi disconnected from the ethernet switch during that test.
Of course I can’t connect to the rov with that setup.
Blueos can see the Ping360 when all is connected, I can’t get to it from ping viewer with the ip address that it has.

For now, I have reverted to usb operation.

If you search “Ping360” you will find lots of threads of folks having connection issues.
For me, BR replaced my Ping360 board, Ping360 cable and Ethernet switch for ones that they knew worked together.
I am not saying that you are encountering exactly the same issues, however this is the thread referring to my issues Ping360 not working through Ethernet and Low Bandwidth on brand new build

1 Like

Thank you, I have read and considered that thread.
I have received a replacement processor board for the ping360. I have also built a new cable for it.
Except for not being able to connect to it because of the ip address issue, the Ping360 seems to work fine. In ethernet or usb, and seems to pass through the ethernet switch and the tether.