OpenMarine

Full Version: no seconds/msec in navigation.datetime
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I try to use in SK : navigation.datetime.

I think the information is obtained from GPS/NMEA.

I have only in SK hours and minutes, not seconds !

Thanks
Sorry !! 
Compairing NMEA Diags ans SK diags, I just understood.
The NMEA/RMC datetime is good and in real time.
The equivalent SK navigation.datetime is refresh every 1 minute and when I red it the initial seconds was 0 and always after...

What is the meaning of the INTERVAL column ?
(2018-04-05, 05:42 PM)ygageot Wrote: [ -> ]Sorry !! 
Compairing NMEA Diags ans SK diags, I just understood.
The NMEA/RMC datetime is good and in real time.
The equivalent SK navigation.datetime is refresh every 1 minute and when I red it the initial seconds was 0 and always after...

What is the meaning of the INTERVAL column ?
This bug has nothing to do with CAN-USB. NMEA/RMC is NMEA0183.
msec instead of s
It was a known bug of signalk and it is fixed (you should use SignalK/nmea0183-utilities in version 0.6.0).
The Interval column should show the average time diff to the next sentence in seconds.