-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NMEA0183 XDR sentences for temperature and battery level #21
Comments
At OpenCPN Manual » Engine Dashboard and the Engine Dashboard plug-in for OpenCPN README, I found those example sentences for battery-related values. However, those are meant to be "Battery Voltage" and "Battery Current".
|
I suppose these would usually be used to show the house / starter battery values. |
Other referencesNone of them tell us about the concept of a "Battery Level", however XDR sentences look very versatile. Can we just make up a custom XDR sentence for that?
Footnotes |
I see. Thanks. |
So far, within this conversation, we discovered five types of XDR sentence identifiers already. Does each of them serve a specific purpose? As seen, they have been used for:
See also SignalK/nmea0183-signalk#54 (comment). |
The first two letters are the "talker identifier" in our case it can be AN ( for Anemometer ) or CA ( For Calypso ) or ML ( for maritime labs :) ) |
Thanks for sharing this link, and for explaining the talker identifier. Currently, we are using First, I intended to use |
ML FTW! |
On the other hand, would that be any kind of standard? -- Airmar GH2183 GPS/Gyro Compass User Manual » Table 3: NMEA 0183 Transmitted Sentences, p. 72 |
ProposalWould those example sentences be feasible?
Note: As I've not been able to find any example which implements the concept of a "battery level in percent", I've made up the P.S.: As we can see, there is apparently no way to tell XDR sentences apart, other than looking at the name field, here |
GH-25 implements the most recent suggestions. Thank you so much for the support! |
Dear @UserMacUseface, we just released calypso-anemometer 0.6.0, including the corresponding improvements, and will be happy to hear back from you about its outcome on this matter. The program will now also emit temperature and battery level on the NMEA-0183 telemetry variant. With kind regards, |
I'm surprised to see Calypso inventing a completely incorrect and non-standard NMEA sentence. The XDR format is formally documented in the NMEA 0183 specification. Calypso is registered with the NMEA so you should be following the spec. The anemometer is marketed as NMEA certified, will you be removing the certification since it doesn't comply? |
Dear @tvr256, this software is completely community-based, and not affiliated with Calypso at all. We will happily consider your suggestions on this matter if you think something implemented by this library violates any standard, or if you think the NMEA sentences outlined within this discussion will cause any specific problems when receiving or decoding them. With kind regards, |
Apologies @amotl , the main page gave me the impression the software was provided by Calypso. The official NMEA spec can be found fairly easily on Google, I'll post the relevant parts here for your reference. |
Air temperature should be in the format Battery level isn't defined in the spec, so you should use the "generic" type field with null units. So the format should be Also, more than one transducer measurement can be included in a single sentence. So you could send both air temperature and battery level in a single sentence |
Hello, |
Introduction
At #12 (comment), @UserMacUseface shared a pointer to NMEA0183 XDR sentences 1, which can be used to transmit
pitch
androll
values.XDR more
Other than those, XDR sentences can apparently be used to transmit temperature data, and battery level, see both 1 and 2.
mandag 15. februar 2016 15.30.56 UTC+1 skrev Mike følgende:
OpenCPN Manual displays those examples:
Status
Footnotes
NMEA 0183 Sentences » XDR ↩ ↩2
Nmea XDR conventions? ↩
The text was updated successfully, but these errors were encountered: