Re: [time-nuts] GPS seconds conversion on an Arduino

Are you still going for Sidereal time? If so that is floating point The ARM processor unlike the Arduino does not have fixed pin assignment. Typically there are many UARTS, I2C interfaces, ADC units and so on more than there are physical pins. Within some limits you assign functions to pins in

Re: [time-nuts] GPS seconds conversion on an Arduino

Also consider the $16 Chip Pro (https://getchip.com/pages/chippro), which runs linux and thus lets you write normal code for the normal things. They also have a $9 more arduino-like version (still runs linux) -j On Sun, May 14, 2017 at 11:22:57PM -0700, Chris Albertson wrote: > Are you still

Re: [time-nuts] GPS seconds conversion on an Arduino

Tom Van Baak wrote: > > 32-bit integers is sufficient. Use days instead of seconds. Use MJD > instead of JD. Here's an example: > > Step 1, convert calendar date to MJD, and then to GPS day: Mark was asking for the reverse calculation, which is a bit trickier :-) My version

[time-nuts] Need information - CTS Knights JKTO-66 oscillator

Hello Time-Nuts, Anyone out there have ANY information on the CTS Knights JKTO-66 Frequency Standard? Seems that even Google has never heard of it. The particular one that I have is three boxes (battery, power supply, and oscillator in very large dewar) mounted on a 4U rack panel. BTW, the one

Re: [time-nuts] Need information - CTS Knights JKTO-66 oscillator

Never heard of this one but having lived in Sandwich all my life, would love to see some pictures if you have any.  I casually collect Faberadio/James Knights/CTS Knights crystals and related.  I'm not aware of any catalog archives available through the local historical society but will cleck

Re: [time-nuts] GPS seconds conversion on an Arduino

Hi Chris and list, On 5/15/2017 1:22 AM, Chris Albertson wrote: Are you still going for Sidereal time? If so that is floating point I'm not sure how Sidereal time came up...it wasn't one of my goals and after reading the discussion, it's going to be way past what I think I can understand,

Re: [time-nuts] HP 55300A

> This appears to be pre Y2K. Is it Y2K, or the 1024 week GPS rollover? At least with the Z3801A, you can get around the 1024 week problem by telling it a date before it gets it from the GPS. -- These are my opinions. I hate spam. ___ time-nuts

[time-nuts] HP 55300A

I have a HP 55300A GPSDO that works well except for having the wrong date. It does not decode the date from the GPS correctly. It has firmware 3704-D. This appears to be pre Y2K. Does anybody have newer firmware for one of these. ? Gary ___

Re: [time-nuts] GPS seconds conversion on an Arduino

On Mon, May 15, 2017 at 1:49 PM, Ben Hall wrote: > Hi Chris and list, > > On 5/15/2017 1:22 AM, Chris Albertson wrote: > >> Are you still going for Sidereal time? If so that is floating point >> > > I'm not sure how Sidereal time came up...it wasn't one of my goals and > after

Re: [time-nuts] GPS seconds conversion on an Arduino

Sorry for the email with zero new content. It was a "mis-click". Don't bother with a stand-along logic analyzer. They were designed for the old days with people built stuff using about a hundred or so 74xxx TTL chips.No one does that any more.Today we use micro controller and FPGA and

Re: [time-nuts] GPS seconds conversion on an Arduino

That Chinese guy selling boards shipped for $1.67 is buying the boards, paying for postage and 10% commission to eBay and STILL earning some income.It's an insane price and the unit is dramatically more powerful than Arduino and $1.67 is so close to "free" that I don't care about the

Re: [time-nuts] GPS seconds conversion on an Arduino

t...@leapsecond.com said: > 32-bit integers is sufficient. Use days instead of seconds. Use MJD instead > of JD. Here's an example: I think it depends on how far forward or back in time you want to go. POSIX keeps track of time using seconds since 1970. 31 bits works until 2038. POSIX also