Gregw - My [signalk-racing](https://github.com...
My signalk-racing plugin is progressing and I'd appreciate if anybody would like to test it. It current calculates: start line end points from named waypoints; start line length; start line bias; distance to start line; true heading for the next leg of a course; TWA for the next leg of the course.
8 Replies
This is really cool!
Thanks - now published on npm: https://www.npmjs.com/package/signalk-racer
Next step is integration with the kip start timer
This plugin is perfecto for me! I'm going to try it.
I've just added an API and a simple webapp to set the port/stb ends of the line from the boats bow
Now I'm working on a KIP UI for it. The idea being that from the timer you can set the port/starboard ends of the line. It will always indicate if you are OCS or not. When the count reaches 0, if you are not OCS, the dashboard will change to a configured preferred dashboard. If you are OCS then it will stay on the timer and the OCS will be very RED and visible.
I raced with my plugin for the first time today. The line calculations worked great. However, the timer needs a rethink. The problem is that the timer is entirely local in the browser. For whatever reason, the browser lost contact with the server for a moment, so it lost state and the counter reset. I think it needs to store the absolute time of 0:00 on the server, so that if it does restart (or if there are multiple displays) then they all share the same info. So I'm thinking that timer becomes a server side thing and the widget is just a display of it.
I've now got this webapp working for line adjustments using websockets to the v2 API of the plugin. I'll work on the timer part of that over the next few days and once I'm happy with it I'll replicate in a KIP widget.
This is a demo of the current state of the plugin. I'll do a more concise version when I do a release in the next few days: https://youtu.be/7GwjwE9X9WQ?si=n064ivF4lgbaSEcW