Seatalk Time Date issue - Other SeaTalk users?

[Boatingbaileys]

Hi all,

We are having an issue with the date/time that's coming from the SeaTalk network. I'm using the SeaTalk-1 input, it's inverted and running via a cheap optocoupler. All other date seems stable and consistent, however, the month changes every second or two, I see that in KIP. In the SK data browser I see it change less often, but it still happens.

I don't see this on the C80 Raymarine plotter or my VHF.

Any other SeaTalk users seeing this?

Thanks all.
Mat

[holgerw]

Hi all,

We are having an issue with the date/time that's coming from the SeaTalk network. I'm using the SeaTalk-1 input, it's inverted and running via a cheap optocoupler. All other date seems stable and consistent, however, the month changes every second or two, I see that in KIP. In the SK data browser I see it change less often, but it still happens.

I don't see this on the C80 Raymarine plotter or my VHF.

Any other SeaTalk users seeing this?

Thanks all.
Mat

try if the led is bright enough in the coupler, minimise its resistor.

[Boatingbaileys]

Hi all,

We are having an issue with the date/time that's coming from the SeaTalk network. I'm using the SeaTalk-1 input, it's inverted and running via a cheap optocoupler. All other date seems stable and consistent, however, the month changes every second or two, I see that in KIP. In the SK data browser I see it change less often, but it still happens.

I don't see this on the C80 Raymarine plotter or my VHF.

Any other SeaTalk users seeing this?

Thanks all.
Mat

try if the led is bright enough in the coupler, minimise its resistor.

I have tried changing the resistors (both ways) and it doesn't seem to make a difference. I have had to up the resistor as its stopped my VHF receiving GPS but that's not made any difference. Is there a way to debug the Seatalk side so I can actually see the sentences coming out?

[Sailoog]

could it be that more than one source was struggling to set the time?

try disabling the "set system time" plugin: http://localhost:3000/admin/#/serverConf...ystem-time

[Boatingbaileys]

could it be that more than one source was struggling to set the time?

try disabling the "set system time" plugin: http://localhost:3000/admin/#/serverConf...ystem-time

Disabling the plug-in  stops the date changing  if I can get it to set correctly at boot but it’s still jumping in the data browser. Is there a way to troubleshoot seatalk data? A debug option ?

Is SignalK expecting mm/dd/yy or is this dependent on location settings?

Thanks,

[tkurki]

You can activate data logging for that connection and check the data.

Seatalk to sk code https://github.com/SignalK/nmea0183-sign...ks/seatalk

[Boatingbaileys]

You can activate data logging for that connection and check the data.

Seatalk to sk code https://github.com/SignalK/nmea0183-sign...ks/seatalk

Thanks for this - I've run the debug and the Seatalk data does look correct, and consistent. If I've got this right, sentence 56 is the data and its in HEX so 2nd June 22 - 6/02/22

Jun 02 20:03:16 2022-06-02T19:03:16.472Z signalktreams:pigpio-seatalk $STALK,54,01,0e,13
Jun 02 20:03:16 2022-06-02T19:03:16.493Z signalktreams:pigpio-seatalk $STALK,56,61,02,16

Jun 02 20:03:17 2022-06-02T19:03:17.485Z signalktreams:pigpio-seatalk $STALK,54,11,0e,13
Jun 02 20:03:17 2022-06-02T19:03:17.705Z signalktreams:pigpio-seatalk $STALK,56,61,02,16

Jun 02 20:03:18 2022-06-02T19:03:18.509Z signalktreams:pigpio-seatalk $STALK,54,21,0e,13
Jun 02 20:03:18 2022-06-02T19:03:18.667Z signalktreams:pigpio-seatalk $STALK,56,61,02,16


Jun 02 20:03:19 2022-06-02T19:03:19.344Z signalktreams:pigpio-seatalk $STALK,56,61,02,16

Jun 02 20:03:19 2022-06-02T19:03:19.628Z signalktreams:pigpio-seatalk $STALK,54,31,0e,13
Jun 02 20:03:20 2022-06-02T19:03:20.333Z signalktreams:pigpio-seatalk $STALK,54,41,0e,13
Jun 02 20:03:20 2022-06-02T19:03:20.364Z signalktreams:pigpio-seatalk $STALK,56,61,02,16

When I debug the set data time or turn that it instantly jumps a month and then occasionally sticks on the correct date. I have no other source for time. I've just got Seatalk data, a USB Victron SDR (makes no difference it did this before) and some temp sensors really..... very odd!

[TVR]

I had a very similar problem with an NMEA 0183 source, so I don't think it's specific to SeaTalk.

With a Garmin chartplotter sending RMB, RMC, APB and BWC messages, all the messages had the correct timestamp except BWC which was consistently 4 weeks and 1 hour earlier :
   

[Boatingbaileys]

I had a very similar problem with an NMEA 0183 source, so I don't think it's specific to SeaTalk.

With a Garmin chartplotter sending RMB, RMC, APB and BWC messages, all the messages had the correct timestamp except BWC which was consistently 4 weeks and 1 hour earlier :

Interesting - Did you manage to solve it? Have you tried changing any date/time formats?

[TVR]

I had a very similar problem with an NMEA 0183 source, so I don't think it's specific to SeaTalk.

With a Garmin chartplotter sending RMB, RMC, APB and BWC messages, all the messages had the correct timestamp except BWC which was consistently 4 weeks and 1 hour earlier :

Interesting - Did you manage to solve it? Have you tried changing any date/time formats?

No, I ended up using OpenCPN instead of the Garmin. I assumed at the time it was a problem with the Garmin, but it sounds like it could be a SignalK issue instead?