This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
plots plugin - barometer error: nan
#1
Hello,

I would like to track baro changes using the 'Plots' plugin but got 'nan' and no baro data when plotting.

   

My setup: the baro data comes from enviro pHAT attached to the 40 pins of raspberry pi 4. The baro data detected on the i2c app and the signalk connection was established. I can see the pressure and temp data on signalk without problems. The pressure is also correctly displayed on opencpn's dashboard.

     

Since 'Plots' plugin for barometer expects NMEA/ MDA, the baro data on signalk is then converted to NMEA0138. 

Here is the problem:
The 'Plots' plugin shows only nan and no data goes into it. From the NMEA debug window, I got the following (red indicates error):

Code:
<GREEN>18:50:52 (TCP:localhost:10110) $IIXDR,P,1.0155,B,Barometer*17<0x0D><0x0A>
<RED>--> 18:50:52 (TCP:192.168.14.1:20220) $IIXDR,P,1.0155,B,Barometer*17<0x0D><0x0A>
<GREEN>18:50:53 (TCP:localhost:10110) $IIMMB,29.9900,I,1.0156,B*71<0x0D><0x0A>
<RED>--> 18:50:53 (TCP:192.168.14.1:20220) $IIMMB,29.9900,I,1.0156,B*71<0x0D><0x0A>
<GREEN>18:50:53 (TCP:localhost:10110) $IIXDR,P,1.0156,B,Barometer*14<0x0D><0x0A>
<RED>--> 18:50:53 (TCP:192.168.14.1:20220) $IIXDR,P,1.0156,B,Barometer*14<0x0D><0x0A>

Is it because a comma is missing in the NMEA sentence. For example, in
Quote:Barometer*17<0x0D><0x0A>
between 'Barometer' and the checksum '17<0x0D><0x0A>'? Therefore, the format is not valid? 

Any ideas how to debug this? Many thanks!
Reply
#2
(2024-03-27, 03:15 AM)volksbar Wrote: Is it because a comma is missing in the NMEA sentence. For example, in
Quote:Barometer*17<0x0D><0x0A>
between 'Barometer' and the checksum '17<0x0D><0x0A>'? Therefore, the format is not valid? 

Any ideas how to debug this? Many thanks!

Sentence looks OK in nmea checksum calculator
https://nmeachecksum.eqth.net/
Command:$*
With checksum:$IIXDR,P,1.0155,B,Barometer*17

Mine is the same, assumming it's because signalk creates a XDR nmea0183 sentence, not a MDA sentence, which is obsolete apparently >>
https://opencpn.org/wiki/dokuwiki/doku.p..._sentences
"MDA
Meteorological Composite (obsolete) This message is obsolete and NMEA recommends to use XDR transducer messages instead. However, old instruments might still sending this message."


Maybe more of an Opencpn question than openplotter.
https://www.cruisersforum.com/forums/f134/

Or probably possible to do a hack in node-red. 
Reply
#3
(2024-03-27, 08:44 AM)PaddyB Wrote:
(2024-03-27, 03:15 AM)volksbar Wrote: Is it because a comma is missing in the NMEA sentence. For example, in
Quote:Barometer*17<0x0D><0x0A>
between 'Barometer' and the checksum '17<0x0D><0x0A>'? Therefore, the format is not valid? 

Any ideas how to debug this? Many thanks!

Sentence looks OK in nmea checksum calculator
https://nmeachecksum.eqth.net/
Command:$*
With checksum:$IIXDR,P,1.0155,B,Barometer*17

Mine is the same, assumming it's because signalk creates a XDR nmea0183 sentence, not a MDA sentence, which is obsolete apparently >>
https://opencpn.org/wiki/dokuwiki/doku.p..._sentences
"MDA
Meteorological Composite (obsolete) This message is obsolete and NMEA recommends to use XDR transducer messages instead. However, old instruments might still sending this message."


Maybe more of an Opencpn question than openplotter.
https://www.cruisersforum.com/forums/f134/

Or probably possible to do a hack in node-red. 

Thanks for the confirmation. I re-posted in opencpn forum in case anyone knows a quick fix. (I don't know at this stage how to hack the node-red...)
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)