2023-12-09, 11:48 PM
(2023-12-09, 11:30 PM)Techstyle Wrote: I haven't got a testing environment setup right now, and I am not at my boat, but if you want to test this and report how it goes, please see the link below:I probably will not get back to the boat until Monday coming 11th. Dec I'll do as you suggest and let you know how I get on.
eta2.js.txt
Find eta.js in the calcs directory of Derived Data plugin and back it up. then rename the file above to eta2.js and restart Signal K. you should have 'navigation.courseGreatCircle.nextPoint.TimeToArrival' and it should be "HH:MM:SS" or "--"
the route ones are a little trickier, the calcs use Velocity Made good to Course (next point), and VMG to next point is not necessarily VMG to route, we may use this but I am not sure it will be representative. Also, I need to find what we can use for distance - route length (not distance to the end point) - I will work on these but let me know your thoughts?
I can see the difficulties in picking a velocity to use. I would suggest that the route distance remaining be divided by the current speed over ground. Then you would know that if you maintained the same velocity and stayed on the route the ETA and TTG would be reasonably accurate. I realise that if you had a leg where you had to tack or speed over ground was reduced by tide/current that the times estimated would be incorrect. However as these events would be in the future it would be unreasonable to expect an accurate estimate. That is why I think it best to used the current "knowns"