Plugin: DashBoard

[Hakan]

Originally Posted by Rasbats

Think it should be up to the user to decide which frequency to use. No need for priority.

Where to decide. On the sensors display I suppose not in OCPN?


If so either of LO and HI can occur in the XDR received by O? If both we may have to prioritize?

[Hakan]

To exemplify:
$SDXDR,D,2.3,M,XDHI,D,2.92,M,XDLO*63
That sentence will make the depth graph ragged.

[Hakan]

For info.
Dave has kindly accepted a PR changing the XDR behavior a little.
What's new in O master v5.9 alpha:
- The air temp conditions are more general. So every message type "C" with a name containing "Air", case independent, will be accepted. So e.g. Corsair's message mentioned above will now work.
- Any type "P" containing "BARO" (upper/lower) is accepted for air pressure.
- A new message for type "D" Hi/Low sounding frequencies like "$SDXDR,D,2.3,M,XDHI,D,2.92,M,XDLO*63" is now accepted. If both HI and LO are present HI is favored. (The Hi is normally used for short distances and LO for long. (very deep)

[Schnapsy]

In this case, is it possible to also make the following change "{Contains("PITCH")} " and "{Contains("ROLL")} ", as already indicated in this thread?

https://www.cruisersforum.com/forums...ml#post3793846
One obvious patch for OCPN Dashboard would be to look for a XDR that {Contains("PITCH")} and {Contains("ROLL")} instead of specifically "PITCH" and "ROLL" ?
I'll se if that change may be accepted for next OCPN release.

[Hakan]

Schnapsy
I'd say it's like that in the present Git master code:

----
if (m_NMEA0183.Xdr.TransducerInfo[i].TransducerName.Contains(
        _T("PTCH")) ||
    m_NMEA0183.Xdr.TransducerInfo[i].TransducerName.Contains(
         _T("PITCH"))) {
-----
else if (m_NMEA0183.Xdr.TransducerInfo[i].TransducerName.
            Contains("ROLL")) {

[Hakan]

About humidity discussion above:
A PR is accepted to Github master (5.9 alpha) introducing a single instrument for Humidity.
It takes data from N2k PGN130313, Signal K, XDR (type: H unit: P) and MDA. In that order of priority.

Please if anyone have the opportunity to test N2k PGN 130313. It's not tested since I'd no source for that PGN.
Thanks

[rgleason]

Hakan, I'm not using 5.9 right now, maybe later I can test. Sorry, and thankyou.

[rgleason]

David Burch advises

We have a new high-accuracy, low-cost barometer that works great in OpenCPN. This video shows how to set it up: https://youtu.be/ZqQN4uWb9hI

Hakan advises Dashboard has been updated for barometer XDR sentences.

We just found that Plots_pi also supports a Barometer with MDR sentences, we should update this for XDR, but nmeaconverter should work to convert the sentences.

Also I think this Barometer Cheat Sheet Information should be a part of the plugin somehow.

https://sailingeurybia.com/reading-b...m-cheat-sheet/

https://www.sailingeurybia.com/wp-co...r-WBF-2016.pdf

Veering vs Backing
Veering is the same as “clocking around” in a clockwise direction. So a north wind veers to the northeast but backs to the northwest. Common usage says this is the same in the southern hemisphere.
Where is the Low Pressure Storm Center?

Buys-Ballots Law: With the wind at your back, low pressure will be to your left and forward ~ 20° (open water). “Wind Back, Low Left”. For the southern hemisphere it is reversed – with the wind to your back the low will be to your right.



Hurricane and Typhoons Rules
Northern Hemisphere, winds move counter-clockwise. Right upper quadrant is the windiest.

Southern Hemisphere, winds move clockwise. Left upper quadrant is the windiest.

[rgleason]

Hakan requested:

About humidity discussion above:
A PR is accepted to Github master (5.9 alpha) introducing a single instrument for Humidity.
It takes data from N2k PGN130313, Signal K, XDR (type: H unit: P) and MDA.

Please if anyone have the opportunity to test N2k PGN 130313. It's not tested since I'd no source for that PGN.
Thanks

[GordotheGrey]

Hi, hoping that I'm in the right place to report a bug

I am running the latest stable version of OCPN (5.8.4-0), and have made sure that I have updated the plugin catalog and plugins.

I'm on a PC running Win10 with all latest updates

The Wind History widget in the Dashboard does not update TWS. It shows a fixed line at the speed when the Dashboard is first initialised I think. Stopping and restarting the Dashboard doesn't change the TWS displayed.

TWD works as expected in the history widget

The standalone TWS widget works as expected in a separate dashboard window.

I have validated the problem on 2 separate Win10 PCs and also on my android phone

NMEA 0186 feed via WiFi from B&G Vulcan plotter.

Any suggestions on whether this is just me? Further info required?

regards Gordon

[rgleason]

GordotheGrey

Can you please use the VDR_pi Voyage Data Recorder to record a nmea 0183 data file of the output from your Vulcan, that is being picked up by your OpenCPN software over the wifi connection.

Another way to look at this information data stream is to use Toolbar Options Connections and check the Nmea Data Window to see the data stream by. That is what we want in a file format.

Then upload the file to this thread. To help with that effort under FAQ in the wiki Manual there is a section for Support. Please read it. Thank you.

[Hakan]

GordotheGrey..
rgleason's comment about more data is relevant!
The wind history graph as such is working for others:

[GordotheGrey]

Hi,

hopefully I have every thing needed this time

Device Info
Device Alienware 15 R3
Processor Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz 2.80 GHz
Installed RAM 16.0 GB (15.9 GB usable)

System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display
Edition Windows 10 Home
Version 22H2
Installed on ‎25/‎07/‎2022
OS build 19045.4239
Experience Windows Feature Experience Pack 1000.19055.1000.0

ini file, log file, vdr and screen shot attached. remove the PDF ext when downloaded

regards Gordon

[Hakan]

GordotheGrey..
Let's see if I can explain what's happening.
Using you VDR file I see the xxMWD sentences as of below.
The wind history instrument uses in first hand MWD if present. As you can see all MWD in you VDR file does have the wind speed 6.3 Knots or 3.2 m/s. Obviously is the MWD used since it's present and then other wind data sentences are not used for this graphical instrument.

If MWD is not present in the data stream the wind history tries to use other data to read or create wind direction and true wind speed. (wind direction is the wind angle related to north.)

Now since you have a heading and other wind data you could try to filter out the MWD sentences since you seemingly don't trust these values?
The heading you receive is magnetic only so be sure to have plugin WMM enabled.

Note:
To filter out a sentence: (If you not already know)
For the connection where you receive WIMWD scroll down and select "Ignore sentence". Click the three dot icon and select MWD-> OK (see Pict)

19:59:58 (virtual) $WIMWD,83.0,T,69.8,M,6.3,N,3.2,M*52<0x0D><0x0A>
20:00:41 (virtual) $WIMWD,83.0,T,69.8,M,6.3,N,3.2,M*52<0x0D><0x0A>
20:01:24 (virtual) $WIMWD,83.0,T,69.8,M,6.3,N,3.2,M*52<0x0D><0x0A>
20:02:07 (virtual) $WIMWD,83.0,T,69.8,M,6.3,N,3.2,M*52<0x0D><0x0A>
20:02:50 (virtual) $WIMWD,83.0,T,69.8,M,6.3,N,3.2,M*52<0x0D><0x0A>

[GordotheGrey]

Hi Hakan

thank you for the suggestion. It was successful ....

I am confused why it does though.

Before dropping MWV, the standalone TWS widget worked perfectly, but the TWS element of the Wind history widget did not ...after the change both work perfectly.

Something that I forgot to mention was that the TWS element of the Wind history widget did not respect the preference for wind speed units but the standalone widget did. After the change the wind history units worked as expected ...

Anyway, it's fixed and that's the important thing.

Thanks and regards
Gordon