This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
no seconds/msec in navigation.datetime
#1
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
Reply
#2
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 ?
Reply
#3
(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.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)