Ping360 widget setup in Cockpit

Blue Robotics Software BlueOS
, ,
1

Hello all,

I am having trouble setting up the Ping360 widget in the cockpit app.

I have a Ping360 with the latest firmware connected to a Raspberry PI via the USB interface. Using Pingviewer app on Windows topside computer, I am able to detect the ping360 and display data on my topside computer. Pingviewer shows the 192.168.2.2:9092 as the connection address.

In BlueOS via the web interface blueos.local, I can open “Ping Sonar Devices” and the Ping360 is shown at Bridge UDP 9092 with FW 3.3.0.

If I open the Pingviewer extension in BlueOS, I am able to view the sonar data stream. The Device Management menu of this app shows the Ping360 connection at 127.0.0.1 Port 9092.

Now if I open up Cockpit and go to “Edit Interface” i can see the Ping360 widget at the bottom of the screen. Notably, the widget-icon is a broken link, which may be a possible clue. I can drag the Ping360 widget onto the display, and it just shows up as a transparent box.

If I then click the settings button for Pint360, I get a screen that says “Iframe Source” http://blueos.local:6060undefined.

If i change this value to http://blueos.local:9092, then the widget window turns into a grey frowny file face. I have also tried these iframe source addresses, but never successfully connect to the sonar:
http://192.168.2.2:6060 – Tranparent background

http://192.168.2.2:9092 – frowny file

http://127.0.0.1:9092 – frowny file

http://127.0.0.1:6060 – frowny file

http://blueos.local:6060 ----> WORKS.

Ok, I answered my own question. Could someone explain what port 6060 is, and how it is different from 9092? Also, why does the 192.168.2.2:6060 (the vehicle’s ip address) not work, but blueos.local does? **

**

2

Hi @StrikeLines,

It’s the port the Extension exposes and binds to (as opposed to the port the sonar itself is communicating over with serial data).

Are you able to connect to your vehicle using http://192.168.2.2? If that works then I would expect Ping Viewer to work that way as well, but otherwise you may have some network configuration issue, or you may have run into an issue where the vehicle loses its static IP (which is a bug that has been fixed in the 1.4.4 beta releases).

That said, @tony-white did recently mention an issue with loading the widget in Cockpit, so it’s possible there’s just a bug in the Extension - we’ll investigate and see if we can find a cause.