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.

  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
overcome XDR challenges?
#1
I am aware that the XDR message is not standardised and therefore not supported by Signal k

But I have environment (temp, pressure) and other data (pitch, roll, tank levels etc) available in NMEA 0183 XDR messages which are currently not getting into my system. It is possible to differentiate between the different data using a combination of talker ID and data field description.

What is the best way for me to get this valuable data into Signal k?
  Reply
#2
A generic solution to XDR is hard/complex but a specific one fairly straightforward. Several different solutions possible here:

A) create a custom hook for the nmea0183 parser. See https://github.com/SignalK/signalk-parse.../146/files for an example. You will have to re-add your own hook after updates that overwrite index.js

B) a plugin, published or private. nme0183 input is available in event nmea0183. Code is similar to B, with a bit of plugin scaffolding. Will not get overwritten by updates

C) node-red flow that connects to tcp port 10110 and handles your XDR, producing deltas. Your setup, so will not get overwritten. Somewhat shareable here: export/import as a single JSON file




Sent from my iPhone using Tapatalk
  Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)