Display TTG in KIP

[Jodel]

Hi,  Am I correct in assuming that Time to Go has to be calculated and is not included in any NMEA sentence coming from Opencpn to SgnalK?  Can KIP calculate TTG and display it?  
Jodel

[SCarns]

If OpenCPN calculates it, it should be able to send it back out to signalk through NMEA over TCP/IP. There's also a bunch of other ways to calculate it, like in some sort of SK plug-in. I thought the derived-data plugin calculated it, but it doesn't at this time. You could always use Node-Red to calculate it inside of SignalK using ETA and current time to calculate TTG.

As far as I know, KIP only displays data, you'll need to come up with TTG some other way. Derive-data does calculate ETA.

[Jodel]

If OpenCPN calculates it, it should be able to send it back out to signalk through NMEA over TCP/IP. There's also a bunch of other ways to calculate it, like in some sort of SK plug-in. I thought the derived-data plugin calculated it, but it doesn't at this time. You could always use Node-Red to calculate it inside of SignalK using ETA and current time to calculate TTG.

As far as I know, KIP only displays data, you'll need to come up with TTG some other way. Derive-data does calculate ETA.

Hi,
Thanks for the help.  I am not sure if there is a NMEA sentence for Time to Go or for ETA.  I'll check out the derived data plugin.   That seems useful. 
I suppose for manipulating data there is no escaping Node Red  
I'll have to give it some time and learn how to use it properly.
Thanks again, Jodel

[Techstyle]

If OpenCPN calculates it, it should be able to send it back out to signalk through NMEA over TCP/IP. There's also a bunch of other ways to calculate it, like in some sort of SK plug-in. I thought the derived-data plugin calculated it, but it doesn't at this time. You could always use Node-Red to calculate it inside of SignalK using ETA and current time to calculate TTG.

As far as I know, KIP only displays data, you'll need to come up with TTG some other way. Derive-data does calculate ETA.

Hi,
Thanks for the help.  I am not sure if there is a NMEA sentence for Time to Go or for ETA.  I'll check out the derived data plugin.   That seems useful. 
I suppose for manipulating data there is no escaping Node Red  
I'll have to give it some time and learn how to use it properly.
Thanks again, Jodel

Derived Data does calculate it and sends out a SignalK value for navigation.courseGreatCircle.nextPoint.estimatedTimeOfArrival

[Jodel]

If OpenCPN calculates it, it should be able to send it back out to signalk through NMEA over TCP/IP. There's also a bunch of other ways to calculate it, like in some sort of SK plug-in. I thought the derived-data plugin calculated it, but it doesn't at this time. You could always use Node-Red to calculate it inside of SignalK using ETA and current time to calculate TTG.

As far as I know, KIP only displays data, you'll need to come up with TTG some other way. Derive-data does calculate ETA.

Hi,
Thanks for the help.  I am not sure if there is a NMEA sentence for Time to Go or for ETA.  I'll check out the derived data plugin.   That seems useful. 
I suppose for manipulating data there is no escaping Node Red  
I'll have to give it some time and learn how to use it properly.
Thanks again, Jodel

Derived Data does calculate it and sends out a SignalK value for navigation.courseGreatCircle.nextPoint.estimatedTimeOfArrival

Brilliant.  When I get back to the boat again I will install the derived data plug-in and experiment.  Thanks

[SCarns]

Derived Data does calculate it and sends out a SignalK value for navigation.courseGreatCircle.nextPoint.estimatedTimeOfArrival

ETA, yes, but TTG, I don't see it. I hope I'm wrong. Unless it's part of "Course DTG, XTE, BRG, etc (based on courseGreatCircle.nextPoint / previousPoint)". Perhaps I'll dig into Scott's code on GitHub and see if TTG is in there.

[Techstyle]

Derived Data does calculate it and sends out a SignalK value for navigation.courseGreatCircle.nextPoint.estimatedTimeOfArrival

ETA, yes, but TTG, I don't see it. I hope I'm wrong. Unless it's part of "Course DTG, XTE, BRG, etc (based on courseGreatCircle.nextPoint / previousPoint)". Perhaps I'll dig into Scott's code on GitHub and see if TTG is in there.

I wrote the ETA calc code, if you define what you want I can add it?

it is just text so KIP doesn't handle it well, but it works.

[Jodel]

Derived Data does calculate it and sends out a SignalK value for navigation.courseGreatCircle.nextPoint.estimatedTimeOfArrival

ETA, yes, but TTG, I don't see it. I hope I'm wrong. Unless it's part of "Course DTG, XTE, BRG, etc (based on courseGreatCircle.nextPoint / previousPoint)". Perhaps I'll dig into Scott's code on GitHub and see if TTG is in there.

I wrote the ETA calc code, if you define what you want I can add it?
it is just text so KIP doesn't handle it well, but it works.

I have the plug-in installed and selected navigation.courseGreatCircle.nextPoint.estimatedTimeOfArrival

The SignalK data browser is showing the data but as the boat is on the marina, there is no SOG,  so data is just --
In Kip it does not appear in the drop down for the path but I typed it in manually.  However I did not realise that it was only txt and chose time.

It would be nice if Kip could display in addition to ETA at next waypoint also Time to go.  Similar for time to go to end of route and ETA there.
Thanks Jodel

[Techstyle]

Derived Data does calculate it and sends out a SignalK value for navigation.courseGreatCircle.nextPoint.estimatedTimeOfArrival

ETA, yes, but TTG, I don't see it. I hope I'm wrong. Unless it's part of "Course DTG, XTE, BRG, etc (based on courseGreatCircle.nextPoint / previousPoint)". Perhaps I'll dig into Scott's code on GitHub and see if TTG is in there.

I wrote the ETA calc code, if you define what you want I can add it?
it is just text so KIP doesn't handle it well, but it works.

I have the plug-in installed and selected navigation.courseGreatCircle.nextPoint.estimatedTimeOfArrival

The SignalK data browser is showing the data but as the boat is on the marina, there is no SOG,  so data is just --
In Kip it does not appear in the drop down for the path but I typed it in manually.  However I did not realise that it was only txt and chose time.

It would be nice if Kip could display in addition to ETA at next waypoint also Time to go.  Similar for time to go to end of route and ETA there.
Thanks Jodel

So:
Next Point
Time of Arrival at next Point (an actual time of arrival eg. 19:37)
Time to the next point (Hours remaning, eg. 8:52 - 8hrs and 52mins)

Route
Time of Arrival
Time to Arrival

is that what you were thinking?

[Jodel]

Derived Data does calculate it and sends out a SignalK value for navigation.courseGreatCircle.nextPoint.estimatedTimeOfArrival

ETA, yes, but TTG, I don't see it. I hope I'm wrong. Unless it's part of "Course DTG, XTE, BRG, etc (based on courseGreatCircle.nextPoint / previousPoint)". Perhaps I'll dig into Scott's code on GitHub and see if TTG is in there.

I wrote the ETA calc code, if you define what you want I can add it?
it is just text so KIP doesn't handle it well, but it works.

I have the plug-in installed and selected navigation.courseGreatCircle.nextPoint.estimatedTimeOfArrival

The SignalK data browser is showing the data but as the boat is on the marina, there is no SOG,  so data is just --
In Kip it does not appear in the drop down for the path but I typed it in manually.  However I did not realise that it was only txt and chose time.

It would be nice if Kip could display in addition to ETA at next waypoint also Time to go.  Similar for time to go to end of route and ETA there.
Thanks Jodel

So:
Next Point
Time of Arrival at next Point (an actual time of arrival eg. 19:37)
Time to the next point (Hours remaning, eg. 8:52 - 8hrs and 52mins)

Route
Time of Arrival
Time to Arrival

is that what you were thinking?

Exactly.  It is the kind of information, particularly in coastal cruising that is very nice to know.

Also I think that KIP does not display the Path of derived data in the drop downs when configuring the data to display.