Re: [time-nuts] HP 58540A GPSDO date

jg...@zianet.com said: > All this talk of GPS week rollover reminds me of a problem that I am having > with my HP 58540A since I moved. I can't seem to set the correct date. > Perhaps someone here knows the magic formula. For the Z3801A: power off unplug antenna power on set data

Re: [time-nuts] WWVB Disciplined Oscillator

Hi Wayne, Great to see you found my presentation! The paper is available here: https://www.kevincroissant.com/WWVB/WWVB_PTTI_2018_paper.pdf I traveled to CO and met with NIST people there and gathered more data then. We're planning to put out another paper soon (I'm finishing up my bachelor's

[time-nuts] Rollover: Trimble Resolution T

Some older ResTs with v1.2 firmware stopped tracking 15 minutes after the rollover but recovered trackingafter a hard reset. UTC time of day in the 8FAB message has stepped back 20 years, unsurprisingly. Cheers Michael ___ time-nuts mailing list --

[time-nuts] HP 58540A GPSDO date

All this talk of GPS week rollover reminds me of a problem that I am having with my HP 58540A since I moved. I can't seem to set the correct date. Perhaps someone here knows the magic formula. I am positive that when I had the 58540A running in my previous location (NM), that I had managed to set

Re: [time-nuts] Rollover : Thunderbolt

My ancient T'bolt (purchased well-used several months ago) also went from 1023 to 1024. A quick look at IQ phase data I was recording (referred to a free-running PRS-10) shows no discernible glitch at the moment of rollover. This old T'bolt has been living in 1999 for as long as I've had it. So

Re: [time-nuts] WWVB Disciplined Oscillator

Wayne good read on the paper. All of the spectracoms and such were rendered useless by the new BPSK modulation. Though now that 5 years or so have passed not so new. Unless the modulation is accounted for they can't track the carrier. There are external modifications and other approaches that have

[time-nuts] GPS week rollover

I thought for sure my Motorola Oncore receiver in my older Tom Clark's Tac2 would rollover today at 23:59:42 UTC. Using CNS's tac32 software it took me in to gps week 2048 without a hitch. >From the log: -> @@Bo - UTC offset = 18 seconds -> @@Ea,04/07/2019, 00:00:21.000117714, 1.71986531e+008,

[time-nuts] Rollover : Thunderbolt

Thunderbolts have a rollover date based upon the firmware build date. That delays the week rollover. They went into rollover mode around May-June of 2017. ___ time-nuts mailing list -- time-nuts@lists.febo.com To unsubscribe, go to

Re: [time-nuts] Rollover : Thunderbolt

HP 3801 locked after the rollover. Thats all I have checked so far. Regards Paul On Sat, Apr 6, 2019 at 9:01 PM Martin VE3OAT wrote: > Well! I must have misunderstood something. At 23:59:42 on 06 April, > LadyHeather informed me that my Thunderbolt changed from week number > 1023 to 1024. > >

Re: [time-nuts] WWVB Disciplined Oscillator

Not personally, but in the UK a company called Quarztlock made both MSF (similar to WWVB) and 198kHz (a frequency-standard broadcast station) that were popular frequency standards in labs. They still exist but have replaced those products with Rubidium and GPS based standards.

Re: [time-nuts] WWVB Disciplined Oscillator

Hi The gotcha with WWVB is correcting for the day / night ionosphere issues. Since they are not 100% predictable, it’s not a real easy problem to solve. Toss on top of the the ambiguous status of WWV or WWVB ( = will it be there next year …. if so in what format ….) there layers and

Re: [time-nuts] Rollover : Thunderbolt

Well!  I must have misunderstood something.  At 23:59:42 on 06 April, LadyHeather informed me that my Thunderbolt changed from week number 1023 to 1024. Drama!  Suspense!  Excitement!  I had expected a reset from 1023 to 0.  But that isn't what happened.  Maybe in another 20 years ... 73,

[time-nuts] WWVB Disciplined Oscillator

Perhaps this has been mention before, but I found the following document while researching some details on WWVB and thought it might interest the group: https://www.kevincroissant.com/WWVB/WWVB_PTTI_2018.pdf I know that Spectracom once made a WWVB Disciplined Oscillator in the form of the

[time-nuts] EFRATOM MFST rollover way before 6/4 23:59:59

Gents, i realized that my EFRATOM MFST mainframe Rb + OXCO with GPS has rolled over many months before expeted. This summer, in August 21, the display has rolled over to 21/08/1999, and stayed locked then. I wasn't aware, since the unit is located in a rack away from my working desk, but

Re: [time-nuts] GPS 50 bps recording today

Ok. I have a bin file recording going via winoncore12 of the Raw data from an M12 . I hope that it is OK. Mike > Le 6 avr. 2019 à 21:14, Tom Van Baak a écrit : > > Would someone be a hero and record the raw subframe data from GPS today? It's > only 50 bits per second (that's about 8

Re: [time-nuts] GPS 50 bps recording today

At 02:14 PM 4/6/2019, Tom Van Baak wrote: Would someone be a hero and record the raw subframe data from GPS today? It's only 50 bits per second (that's about 8 bytes/second) per SV. I've two uBlox LEA-6Ts recording RXM-SFRB (0x02 0x11) subframe data with crummy indoor antenna positions (rain

Re: [time-nuts] GPS week rollover

Hi Jeff, On 6/04/2019 3:30 pm, Jeff Zambory wrote: Yes Steve, you are correct. https://www.gps.gov/ Scroll down a bit and you can find a count down to the roll over. And it states the time when it will roll over. Just what you have said. Thanks !!! I'll watch that and watch my receivers.

[time-nuts] GPS 50 bps recording today

Would someone be a hero and record the raw subframe data from GPS today? It's only 50 bits per second (that's about 8 bytes/second) per SV. A select few GPS receivers have binary commands that return this low level of detail: M12 (@@Tr), SiRF (8), uBlox (RXM-SFRB). My attempts to pull this off

Re: [time-nuts] Garmin GPS12XL V3.51

I just checked the Garmin site and indeed there are upgrades to versions 4.60 and 3.53. It seems that since I have V3.51 I can jump to 3.53 but not 4.60. I assume my hardware precedes yours. "Mine had the batteries out for about a year.? Put some fresh ones in, turned it on and set it outside

Re: [time-nuts] GPS week rollover

> Le 6 avr. 2019 à 17:53, jimlux a écrit : > > On 4/6/19 12:53 AM, Mike Cook wrote: >> The OP doesn’t state where he got the « quote » from, but IMHO it is wrong. >> As I understand it. >> The GPS epoch started at 0h 1st June 1980 > > 6 Jan 1980 00:00:00 UTC Just so… 01/06 tripped me > >

[time-nuts] Navsync CW25 rollover

I recently got in a Navsync CW25 based receiver and added support for it to Lady Heather. I found some info that says current firmware will be affected by the rollover... in a major way! When the week reaches 0, it stops tracking sats for the whole week. Conner-Winfield has updated

Re: [time-nuts] GPS week rollover

On 4/6/19 12:53 AM, Mike Cook wrote: The OP doesn’t state where he got the « quote » from, but IMHO it is wrong. As I understand it. The GPS epoch started at 0h 1st June 1980 6 Jan 1980 00:00:00 UTC ___ time-nuts mailing list --

Re: [time-nuts] Garmin GPS12XL V3.51

Mine had the batteries out for about a year.  Put some fresh ones in, turned it on and set it outside for several minutes. It located position and is showing today's date and time just fine.  Software version on mine is 4.58. Wes   It had to On 4/6/2019 12:10 AM, David J Taylor via time-nuts

Re: [time-nuts] GPS week rollover

Steve Olney wrote: > Just curious - WNRO is not an issue for me even if my GPS receivers are > affected - but I note that the time of rollover is being quoted as > 23:59:59 UTC 6th April. > > Wouldn't the time actually be 18 seconds earlier ? - i.e., 23:59:42 - > due to leap seconds ? > > BTW -

Re: [time-nuts] GPS week rollover

Hi Martin, On 6/04/2019 6:44 pm, Martin Burnicki wrote: Steve Olney wrote: Wouldn't the time actually be 18 seconds earlier ? - i.e., 23:59:42 - due to leap seconds ? Martin Burnicki wrote: so the WNRO occurs 18 s before UTC midnight. So - yes. Thanks for the clarification. Cheers

Re: [time-nuts] GPS week rollover

The OP doesn’t state where he got the « quote » from, but IMHO it is wrong. As I understand it. The GPS epoch started at 0h 1st June 1980 and the week number roles at 1024 week intervals at 0h GPS time. When a leap second is added its as if the clock stops for a second so GPS time will be in

Re: [time-nuts] GPS week rollover

I checked my Garmin Emap, 1999 vintage IIRC. That is telling me that it is 20/05/2014. I found this for Trimble which shows a number of devices affected by this which are commonly used bt timenuts. Have a nice day

Re: [time-nuts] GPS week rollover

Yes Steve, you are correct. https://www.gps.gov/ Scroll down a bit and you can find a count down to the roll over. And it states the time when it will roll over. Just what you have said. Jeff Z. Sent from my iPhone > On Apr 5, 2019, at 4:40 PM, Steve Olney wrote: > > Just curious - WNRO

Re: [time-nuts] Lars GPSDO

Hi One thing to watch out for on any OCXO, but more on ones with crazy large tuning ranges: As the OCXO changes temperature, it’s current draw changes. It’s amazing just how much voltage drop you get in some seemingly well laid out boards when this occurs. The gotcha is that a “bias it up” with

Re: [time-nuts] Garmin GPS12XL V3.51

Thanks! I don't ever think I relied on the date in the unit.  It is going to get some use soon. I would have no idea what to replace it with. Next I need to check out my Symmetricom / /Datum 9390/-/6000/ EXACTIME next. The antenna has been off \for a while. It was updated some years back to

Re: [time-nuts] Garmin GPS12XL V3.51

If you ignore date/year, everything else should be just as before. — Björn Sent from my iPhone > On 6 Apr 2019, at 05:40, Joe Leikhim wrote: > > Just checked my wonderful Garmin GPS12XL tonight. before midnight UTC I > checked navigation and UTC time and all was well. I did not bother

Re: [time-nuts] Garmin GPS12XL V3.51

Just checked my wonderful Garmin GPS12XL tonight. before midnight UTC I checked navigation and UTC time and all was well. I did not bother to check date for some reason. Well now April 6 2019 at 03:39:19 UTC I see the time is 21 August 99 and no apparent way to change. The navigation and time