You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1This is what I use for the OpenCPN Engine Dashboard, and it is important to note that it interprets the "Generic" transducer Type "G" as Engine Hours. The actual NMEA 183 standard does not define any particular measurement for transducer type "G".
These are some sample NMEA 183 XDR sentences.
$ERXDR,P,300000,P,ENGINEOIL#0,C,89.5,C,ENGINE#0,U,13.4,V,ALTERNATOR#0,G,250,,Engine#047
$ERXDR,T,920,R,ENGINE#079
$ERXDR,E,15,P,Fuel#0,E,80,P,FRESHWATER#0#0,E,50,P,FRESHWATER#1,E,75,P,FRESHWATER#2*67
I guess it is just a mapping of the SignalK data model to the appropriate NMEA 183 sentence elements.
Eg. vessel/propulsion/port/coolantTemperature generating something like C,89.5,C,ENGINE#2 and performing the appropriate conversion from SI units.
Important to note also the NMEA 183 engine numbering, Eg. For the RPM sentence, 0 refers to single or mid engine, odd numbers refer to starboard and even refers to port whereas I don't believe any engine numbering standards are defined. for XRR sentences. Might be best to follow the same numbering as defined by the RPM sentence.
Just to confuse things, I don't believe any similar standard exists for NMEA 2000 engine instance numbering,. The SignalK specification, for NMEA 2000, the namespace is something like vessel/propulsion/engine_1/coolantTemperature but nothing really implies that engine_1 is a mid, port or starboard engine.
No description provided.
The text was updated successfully, but these errors were encountered: