Hi Tony
Installed PingViewer Next (PVN) although havent had a chance for an in water test but have some preliminary feedback to share below.
Although it worked well (see below) Sonarview (in a Cockpit iframe) can no longer detect the Ping1D after I installed and ran PVN. Omniscan 450FS still detects OK in Sonarview and Ping1d is still detected in Pingviewer though. I uninstalled PVN, Sonarview and Cockpit to see if I could recover the ability to detect Ping1D in Sonarview but no luck.
It may be that I dont have the correct port set in the vehicle settings in the SonarView Session Configurations menu so really appreciate any advice about what this setting should be as disappeared with the reinstall?
Otherwise be good to know if PVN can run in a Cockpit iframe? Reason I like this functionality is because it allows rapid switching between the sonar (Ping1D, Omniscan 450FS) and video during underwater surveys which require all this info to detect underwater targets and minimise collisions etc.
Not sure its relevant to the possibility that installing PVN was incompatible with the Sonarview Ping1D settings but do see under PVN Device Managment menu that PVN uses the address (lp: 127.0.0.1 port:9090) which is diffferent than used in SonarView and PingViewer?
The PVN display is large which is a definite advantage over SonarView as this is smaller and so detail not as visible - particulary if used in the field where visibility of Cockpit displays are dimished (eg sunlight, small displays, AR glasses etc.)
Output seems a lower resolution display than in the original PingViewer standalone though and not entirely clear how to turn Ping1D off which is a little disturbing particularly when testing in air! The bar/depth graphic you get when clicking in the PVN display is great as shows the estimated depth point against the scrolling display which is really useful.
When first opening PVN it says “connection successful” yet in the menu icons on the left no device is connected - which is a little confusing. Advises to use ‘Auto Create’ which is an option under another icon and sub menu (Advanced Settings). Connecting seems to require going to Auto Create and then Open Device under a seperate menu (three dots) although this didnt always work without closing and reopening Cockpit first- so a little unstable.
Under menus - Settings > Server I dont seem to be able to connect to MAVlink at all. At least nothing seems to happen when I try this? Have this enabled under the Ping Sonar Devices menu in BlueOS though (Mavlink Distances).
Only relevant miniwidgit I could find was an option you discussed on a seperate post that uses the Mavlink variable with the generic indicator miniwidgit giving the ‘altitude’. Which is awesome as also discovered in the same post a much awaited ArduPilot terrain following like function (SurfTrak) has now been incorportated in BlueOS - very nice work blue robotics!!