Re: [time-nuts] TU30 jump second

Hi OK I will try out to see what Lady Heather can do for me. However, I use a MCU for reading the GPS and not all the time so perhaps I have to change this. Björn can you remember something about the reason for the behavior? Thanks Bo ___ time-nuts

[time-nuts] TU30 jump second

Lady Heather can work with the Jupiter receivers in either NMEA or Zodiac (binary) mode. Heather checks time stamps for consistency and flags any that are out of sequence. I usually run it in binary mode. It's been a while since I ran mine, but I don't remember ever seeing any skips. The

Re: [time-nuts] TU30 jump second

Hi, On 04/04/2017 05:47 PM, Bob kb8tq wrote: Hi On Apr 4, 2017, at 10:01 AM, Bo Hansen wrote: Hi all The data can be a bit hard to read in an email. So I will give it another try. PC-time | Diff. | GPS-time | Diff. ... 011606.005 | 0.992 | 011604 |1 011607.013 |

Re: [time-nuts] TU30 jump second

bject: Re: [time-nuts] TU30 jump second Hi > On Apr 4, 2017, at 10:01 AM, Bo Hansen <timen...@rudius.net> wrote: > > Hi all > > The data can be a bit hard to read in an email. So I will give it another try. > > PC-time | Diff. | GPS-time | Diff. > ... > 01

Re: [time-nuts] TU30 jump second

Hi > On Apr 4, 2017, at 10:01 AM, Bo Hansen wrote: > > Hi all > > The data can be a bit hard to read in an email. So I will give it another try. > > PC-time | Diff. | GPS-time | Diff. > ... > 011606.005 | 0.992 | 011604 |1 > 011607.013 | 1.008 | 011605 |1 > 011608.005 |

Re: [time-nuts] TU30 jump second

Hi all The data can be a bit hard to read in an email. So I will give it another try. PC-time | Diff. | GPS-time | Diff. ... 011606.005 | 0.992 | 011604 |1 011607.013 | 1.008 | 011605 |1 011608.005 | 0.992 | 011607 |2 <--- The issue 011609.013 | 1.008 | 011608 |1 011610.004 | 0.991 | 011609 |1

Re: [time-nuts] TU30 jump second

Hi Bo, Are you getting data in binary format [1] or NMEA? The NMEA mode for some Jupiter receivers are known to behave badly in NMEA-mode. The delay would go from 1:ish to 2:ish seconds depending on signal processing load. -- Björn [1] Navman/Jupiter/Conexant/Zodiac/Rockwell binary...

Re: [time-nuts] TU30 jump second

Hi Welcome to the ever growing list of people with buggy GPS modules. One thing that makes this stuff tough to track down is the firmware. A lot of these parts went out with various revs of the standard firmware. Some of them went out with specific customized versions of the firmware. Since

Re: [time-nuts] TU30 jump second

Hi The odd behavior is seen in NMEA mode. I have not tried in binary mode. Bo ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.

[time-nuts] TU30 jump second

Hi List Like many of you I also use a Navman Jupiter TU30 in a GPSDO. Besides the 10 kHz used for the PLL I also have a display showing time. But since a couple of years, Jan 15?, the time sometimes jumps -1 s and and then later returns by jumping +1 s Please see an example of the latter