2017-09-18, 02:03 PM (This post was last modified: 2017-09-18, 02:14 PM by Luckbert.)
sailoog Wrote:2. heel key does not exist in signal k definition, only roll: http://signalk.org/specification/master/...ranch.html
The heel value you see in compass tab is navigation.attitude.roll in signal k. Yes a little bit confusing.
Hello @sailoog,
I think in the current OP in the signalk key: "navigation.attitude.roll" the value roll is used.
But the value heel would have to be used, right?
The value "roll" is displayed in OP and in opencpn. Better would be the value heel.
Greetings Jürgen
Entschuldigung für mein Englisch. Es ist "deepl.com english"
PN bitte auf german.
We use the value heel from compass to send data to the signal k key "navigation.attitude.roll" because key "navigation.attitude.heel" does not exist in signal k specification.
2017-09-19, 11:32 PM (This post was last modified: 2017-09-19, 11:43 PM by seandepagnier.)
Sorry for the confusion. The value you may be looking for is "roll + heel"
I had been experimenting with using the roll and roll rate values to influence the autopilot. The autopilot needs to differentiate between the static heeling and the roll position (as well as roll rate)
The heel value is subtracted from the raw roll value. Maybe this is confusing??
I tried to have some input in the signalk specification, but gave up when I realized that the implementors were not interested in efficiency. I have my own standard which is nearly the same, and hopefully will be compatible soon. Currently there is a simple translation written by sailoog between the two signalk standards which translates I think only, heading, pitch and heel.
As you can see from the scope (and autopilot if you run it) I have _many_ more values than what is in the official standard, not only "heel"
What do you need this value for exactly? How are you using it?