Temperature through NMEA XDR, Dashboard PI

[omnia]

Hi.

I have a NASA marine wind instrument with wind and temperature sensor.

Wind information sent through MWV NMEA sentence. Displays fine in dashboard pi opencpn.

Air temperature information through XDR NMEA sentence. No display.

Im using Dashboard plugin version 1.2 to display the data.

I cant find dashboard_pi on opencpn site.

what is the latest version and where can I get it? (Windows installer)

thanks

[bcn]

Dashboard - and WMM, GRIB, ChartDownloader - are "inline" plug-ins.
They belong to core OpenCPN and are installed together with the main software.

[omnia]

OK - I see.

What is the version number of the Dashboard PI in OCPN v.4.6? and does it interpret XDR NMEA sentences?

I have major issues with 4.6 (does not even want to start) I have 4.4 stable as f.

I see a plugin: NMEA Converter that can help me but no windows installer and the git source is not updated in years. Anyone know the status of this or want to build a windows installer/release? :P
https://opencpn.org/wiki/dokuwiki/do...nmea_converter

[omnia]

Found this thread:
http://www.cruisersforum.com/forums/...ml#post2128329

Someone tell me to use the f*ing search function.

The NMEA Converter plugin is very powerfull and should there be a candidate for another "inline"-plugin, i nominate this one.

[bcn]

You are on what platform?

XDR is a NMEA0183 "bastard" - open for vendors.
You can't expect that OCPN just understands that vendor specific sentence.

There are quite a lot of recent posts about XDR here in this subform.
You might search for "hakan and XDR"

[omnia]

Thank you bcn.

I was cursing myself.

Also was not aware of the XDR non-standard nature. Explains alot.

Im on windows. I found an installer for the plugin NMEA Converter in the thread i linked above. It does the trick but seems a little unstable. some bugs with the logbook plugin among other things. I understand the converter pi is beta and the development seem to be on hold or abandoned.

What happened to the development of the pi and why is its function not implemented as an integrated feature of opencpn?

[bcn]

Originally Posted by omnia

Thank you bcn.
What happened to the development of the pi and why is its function not implemented as an integrated feature of opencpn?

Why do you think this should be a core function of OCPN?

For Chart Plotting and Navigation?

In an external plug-in, why not? And up to develop the functions in the PI, if somebody is interested to go for it.

OpenPlotter with its SignalK stuff is handling sensor integration - and visualization. Recommend to study..
A layer on top of OpenCPN if you want to see it like this. In a specific HW/SW environment.

Hubert

[Hakan]

omnia...
To be understood by OCPN the air temp message should look like this:
$IIXDR,C,20.5,C,AIRT,*75
The Name of transducer "AIRT" in my example is not read by Dashboard so the text there can for Type "C" be whatsoever.

** $--XDR,a,x.x,a,c--c, ..... *hh<CR><LF>
   **
   ** Field Number: 
   **  1) Transducer Type
   **  2) Measurement Data 
   **  3) Unit of Measurement, Celcius
   **  4) Name of transducer
   **  ...
   **  n) Checksum
   ** There may be any number of quadruplets like this, each describing a sensor. The last field will be a checksum as usual.

Håkan