thanks Tony, I managed to calibrate and save all.
I got the ping viewer widget onto cockpit , but it does not seem to be regestering
should the ping viewer also be open in desktop ?
can you turn the ping viewer off and on in Cockpit?
please advise correct procedure
thanks
No, Ping Viewer Next is intended as a replacement for the original Ping Viewer, not a complement to it. That said, I just tried it and it at least doesn’t seem to overtly complain about the multiple connections 
Also no, as far as I’m aware - although you can start and stop data recording if that’s s relevant.
Per your second screenshot, your current “connection” to the device is experiencing an error. Is there an explanation if you click on it?
I have just tried the interface in Cockpit, and it seems to only work consistently for me at specific sizes, so it’s possible there’s a problem with Cockpit, and/or with PVN’s port access collision handling logic.
Hello Eliot,
I understood the first two explinations, but I am lost with the last explination :
could you explain in simple terms , and how can I resolve the issue ?
If I click on it it just shown me what network it is cionnected to
thanks
I did some more testing, and it seems like the widget in Cockpit stops rendering the waterfall plot if it is too tall. I’ve reported that to Raul (the main PVN developer) and it’s hopefully something he can get working more consistently. If the distance and confidence values are updating in your widget, but not the scrolling plot, then you’re likely facing the same issue, which you can work around by resizing the widget to be shorter.
That said, from your screenshots and description I believe your Ping Viewer Next is not successfully connecting to the Ping Sonar device in the first place, in which case the Cockpit side of things is irrelevant. The waterfall should first be showing up in the Ping Viewer Next Extension interface before it’s worth attempting to get things working in Cockpit.
The “error” indicator at least tells you that something is going wrong, but not having any more information is quite unhelpful for determining what’s actually happening. Could you try downloading the logs from Extensions / Installed → Ping Viewer Next → View Logs → top right button:
@RaulTrombin is there a nice way to get an error message for a failed device connection? Not sure if that’s expected to appear on hover, or click, or clicking the 3 dots, or in the browser console, or just in the Extension logs, or not at all at the moment.
Hello Eliot,
Thanks for the replies. I am running Cockpit V1.16 at the moment, as I am awaiting a new computer with a higher CPU for operating the V 1.17 program ( see previous posts with Rafael), Before I look into possible issues with the ping viewer would running V1.16 affect the issues I am having ?
thanks
Not from what you’ve described so far - connecting to and communicating with the Ping Sonar device has to happen successfully before its data can be displayed or sent anywhere (including to Cockpit).
When you open Ping Viewer Next the expected functionality is that it detects the sonar device, which you can then click on the listing of to see a waterfall plot of the sonar readings, along with distance measurements and confidence estimates. From there, Cockpit should then allow importing a Ping1D widget which should show the same plot.
Hello Eliot,
ok I will look into it and let you know how I get on
thanks
