2020-01-29, 05:53 AM
Any idea why yaw is null?
Am I the only one who thinks the signalk standard would be better:
instead, this:
$source could be left out in subsequent messages if unchanged
The current implementation is difficult to work with, too many rules to interpret so harder to re-implement, confusing to read, and wastes bandwidth because the messages are twice as long as they need to be. This only will increase lag especially on slow links and make data logging larger. Can we re-think this protocol now that use cases are more clear?
Am I the only one who thinks the signalk standard would be better:
Code:
{"updates":[{"$source":"OpenPlotter.I2C.pypilot","values":[{"path": "navigation.attitude","value":{"roll":-0.005427974123,"pitch":-0.0029496065170000006,"yaw":null}}]}]}instead, this:
Code:
{"navigation.attitude":{"roll":-0.005,"pitch":-0.002,"yaw":null,"$source":"OpenPlotter.I2C.pypilot"}}$source could be left out in subsequent messages if unchanged
The current implementation is difficult to work with, too many rules to interpret so harder to re-implement, confusing to read, and wastes bandwidth because the messages are twice as long as they need to be. This only will increase lag especially on slow links and make data logging larger. Can we re-think this protocol now that use cases are more clear?