-
Notifications
You must be signed in to change notification settings - Fork 48
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
ROT: navigation/rateOfTurn seems not to be parsed from NMEA AIVDM #178
Comments
The GeoGate encoder contains samples with ROT |
Very good! |
This is good. It would be much less devious if ggencoder output would be null or undefined for ’no data’, but I guess we need to work with this for now. |
You get out what comes in. The definition is The input is b10000000 (x80) and the rule of the GetInteger routine says for signed integer this is a negative value. from this page |
Hi,
For signal-K the value could be the real RoT I guess. |
In the above |
So we should convert -128 to |
Background for this issue to be found here:
SignalK/signalk-server#1116
Since the rateOfTurn path is mentioned in SK specifications I assumed it was covered also by nmea0183 parser but I may be mistaken.
Anyhow.
The "rate of turn" info from a AIVDM message is parsed by OCPN in this way:
https://github.com/OpenCPN/OpenCPN/blob/69c30afcf7be8398e092ddaff6e434707fcd2e18/src/AIS_Decoder.cpp#L1699
I'll be back when here I've cached some AIVDM messages where the ROT info is present.
Thanks
Håkan
The text was updated successfully, but these errors were encountered: