[time-nuts] Local System Time Sync

On macOS and Linux, a program that messes with the time needs root privileges. Try running Heather via the sudo command. Then issue the TS keyboard command. If you hear a beep after a few seconds, that verifies that Heather can set the system time. Automatic time sets don't beep... Note

Re: [time-nuts] 5065A - Looking for AC XFMR PAECO 9100-2742 specification

Ulf Perhaps you are reading peak VAC that is 1.414 X the RMS voltage typically called out in manuals. I would email you directly but don't seem to have your email. Everything points back to time-nuts. Regards Paul WB8TSL On Thu, Jul 27, 2017 at 1:24 PM, Ulf Kylenfall via time-nuts <

[time-nuts] 5065A - Looking for AC XFMR PAECO 9100-2742 specification

 Trying to repair an old 5065A. After a lot of problems with the Rubidium cavity restoration, it was time to startthe unit. Lucklily, I did not have the Rubidium temperature controller PCB mounted,but the Power supply regulator malfunctioned and blew the AC mains fuse (0.5A). Removing that board

Re: [time-nuts] A look inside the DS3231

Pete: If you are concerned about someone copying a chip, you can not rely on the original manufacturers' markings on the die. I have experience where the counterfeiter just photocopied the chip layout, including the original manufacturers marks, and copyright symbol and notice from the original

Re: [time-nuts] Trimble Thunderbolt no longer determines the correct date

Well quite an unpleasant surprise. So after the 30th do the TBolts stop working or is it a case of just the wrong date? I know my Hp3801s been working just fine and its old. Is the TBolt the same issue. Wrong date but still locks thats all I care about actually. With to respect of some sort of a

Re: [time-nuts] Trimble Thunderbolt no longer determines the correct date

I seem to recall several people (tvb?) doing tests and determining that the 10 MHz and PPS outputs will continue to function as normal, since the Thunderbolt will continue to track and lock onto the satellites. The only difference is it'd think the date and time were N weeks in the past, where N

Re: [time-nuts] A look inside the DS3231

Graham, That's very true! Still, my past experience with copied chips typically involves a particular type of RS-232-to-TTL serial converter, the MAX3232. I've found that nearly all of the ones from unauthorized distributors (e.g. auction site vendors) are fake, even though the package is marked

Re: [time-nuts] A look inside the DS3231

On Thu, Jul 27, 2017, at 09:31 PM, Pete Stephenson wrote: [...] > Based on a sample size of one and the markings on the die itself, it > appears the chip is authentic. The markings on the outside of the epoxy > package look a bit dubious and not like typical Maxim laser-markings, so > it's

[time-nuts] A look inside the DS3231

Hi all, A few days ago I reported the results from letting a DS3231 RTC run for a year, and how the chip kept time well within the published specs. Since I had acquired several DS3231s from dubious sources (Asian vendors on a major auction site) as part of an RTC module that fits on the

Re: [time-nuts] 5065A - Looking for AC XFMR PAECO 9100-2742 specification

In message <675538475.428966.1501176257...@mail.yahoo.com>, Ulf Kylenfall via t ime-nuts writes: >Removing that board I discovered that the "24-32V" raw DC was some >40 Volts. That's a bit on the high side, but not excessively so. HP tended to let the linear regulators shave a big

Re: [time-nuts] Trimble Thunderbolt no longer determines the correct date

On Thu, 27 Jul 2017 17:49:14 -0500 Didier Juges wrote: > I cannot imagine a work around since the problem stems from the GPS service > only identifying the current date within a particular 1024 weeks epoch > unless the government changes the amount of data that is sent over

Re: [time-nuts] Trimble Thunderbolt no longer determines the correct date

Since the Thunderbolt is hard coded to detect a particular week to determine if it should add 1024 to the week number, I would guess that each product has a magic date based on the anticipated release date of the product (week 936 for the Thunderbolt), and it will work for 1024 weeks from that

Re: [time-nuts] Trimble Thunderbolt no longer determines the correct date

> There is: There is a 13bit week number in message type 10. Attila, Well, yes and no. Yes -- paragraph 30.3.3.1.1.1 in www.gps.gov/technical/icwg/IS-GPS-200D.pdf describes a 13-bit extended week number. No -- because this is part of the new CNAV format and existing GPS SV do not transmit

Re: [time-nuts] Trimble Thunderbolt no longer determines the correct date

Thanks I thought it would still work as the 3801 does. On Thu, Jul 27, 2017 at 10:03 PM, Tom Van Baak wrote: > > There is: There is a 13bit week number in message type 10. > > Attila, > > Well, yes and no. > > Yes -- paragraph 30.3.3.1.1.1 in www.gps.gov/technical/icwg/IS-

Re: [time-nuts] A look inside the DS3231

Yes, I doubt that the volume on a specialty chip like the DS3231 is high enough to attract the counterfeiters. RS-232 chips and the FTDI USB to serial chips, and consumer FM tuner and audio amplifier chips, is another story. My experience was with a proprietary full custom IC that totally

Re: [time-nuts] Trimble Thunderbolt no longer determines the correct date

Hi > On Jul 27, 2017, at 8:01 PM, Attila Kinali wrote: > > On Thu, 27 Jul 2017 17:49:14 -0500 > Didier Juges wrote: > >> I cannot imagine a work around since the problem stems from the GPS service >> only identifying the current date within a particular