2019-10-10, 03:38 PM
..trying to emulate wind mode:
Did same on my equipment. Got basicly the same result.
Executed script on OPlotter which is paired to the Tpilot AP; over a usb wifi dongle.
Reason being, i try to maintain all default configuration in case of any single failure point.
Ill use tinypilot wifi client only for updates!
Then in Oplotter, pypilot is connected to <tinypilot>. Wind mode appears in dropdown list; i select it; AP turns BLUE;
and heading cursors (red and green) swing to wind direction momentarily; then pypilot revers back to compass mode.
Looks like pypilot makes decisions off of signalK states, and that data is never establishing residence in the signalK node.
Did same on my equipment. Got basicly the same result.
Executed script on OPlotter which is paired to the Tpilot AP; over a usb wifi dongle.
Reason being, i try to maintain all default configuration in case of any single failure point.
Ill use tinypilot wifi client only for updates!
Then in Oplotter, pypilot is connected to <tinypilot>. Wind mode appears in dropdown list; i select it; AP turns BLUE;
and heading cursors (red and green) swing to wind direction momentarily; then pypilot revers back to compass mode.
Looks like pypilot makes decisions off of signalK states, and that data is never establishing residence in the signalK node.