Search results for all lists

10000 messages found
Sort by
List: time-nuts@lists.febo.com
From: Perry Sandeen
 
Am I missing something?
Mon, May 23, 2011 3:11 AM
Wrote: May this thread die now please. Perhaps. But those that don’t learn and remember history are doomed to repeat it. There are long, long, discourses posted on stuff that I will never understand, use, or even care about. Then there is the PITA of top posting. For some reason this list is the absolute worst in this respect of any I’ve ever seen.
List: time-nuts@lists.febo.com
From: George Allen
 
Re: [time-nuts] The link to the "introduction"
Wed, Mar 14, 2012 3:10 PM
Who will throw it in the dumpster > when > you die? > > If you are completely new to this, where would you like to start? Something > cheap > from an "auction" site or a new hydrogen maser?
List: time-nuts@lists.febo.com
From: Clint Turner
 
WWVB clocks no longer lock (Was: Used Spectracom)
Thu, Jan 17, 2013 8:35 PM
For one of these, I popped the cover and found the trace with the WWVB time code from the die-mounted receiver chip and it looks pretty clean: No "stuttering" is apparent, but I didn't make any attempt to time every type of mark or space to verify its timing.
List: time-nuts@lists.febo.com
From: Bob Camp
 
Re: [time-nuts] Low noise power supplies?
Fri, Feb 1, 2013 2:18 PM
It does *eventually* die down some, but you may have to wait for days... Bob -----Original Message----- From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On Behalf Of M. Simon Sent: Friday, February 01, 2013 9:11 AM To: time-nuts@febo.com; jleikhim@leikhim.com Subject: [time-nuts] Low noise power supplies?
List: time-nuts@lists.febo.com
From: lists@lazygranch.com
 
Re: [time-nuts] Can I get 1 millisecond accuracy with a USB GPS-18
Tue, May 14, 2013 4:13 AM
You have to stop looking for a transition at some point and reject the chip or die. Test engineering needs a limit, even if the spec is internal. And if you set a limit, it has to be justified. Dry labbing is frowned upon. ;-) So the parts would be bench tested over temp to brick wall this limit. A storage scope is set up to get the envelope.
List: time-nuts@lists.febo.com
From: Chris Albertson
 
Re: [time-nuts] Lady Heather W/O a PC: Alternative
Tue, Aug 20, 2013 3:55 AM
They > would provide a cheap LH monitor and when they die, just buy another. > > If you wanted to go upscale there were loads of > 14.1 inch IBM Thinkpads running various flavors of XP for $225.
List: time-nuts@lists.febo.com
From: Bob Camp
 
Re: [time-nuts] fast edge, rise time.
Fri, Dec 27, 2013 2:26 AM
Pulse length about 100ns so only some 0.5mJ energy that would die inside the pulse source( this would be the worst case). > The 100us repetition rate make a a very small duty cycle of 1/1000 so average power > maximum 5W. > > Since the amplitude and timing parameters are to be controlled (pulse timing come from an FPGA) I really need a solution using that trivial
List: time-nuts@lists.febo.com
From: Bob Camp
 
Re: [time-nuts] New NIST Time Code to Boost Reception for Radio-Controlled Clocks
Sun, Jun 1, 2014 12:48 AM
The next issue might be that they only have them in die form. The issue after that probably is that you really want the version 3 (or 9) chips that actually work with all the modulation schemes. I’ve been down the road with a number of similar chips that took *many* rev’s before they really did what they were intended to do.
List: time-nuts@lists.febo.com
From: Azelio Boriani
 
Re: [time-nuts] STEL-1173/CM Source
Fri, Nov 14, 2014 3:56 PM
The die is labelled 'ORBIT B-100'. When I chopped out > the dead chip from my FTS-4065A, the bottom was stamped with the word ORBIT. > ORBIT Semiconductor works on FPGA to ASIC conversions. It looks like > Stanford used Orbit as a fab house. > > I'm currently measuring my 4065A against my Tbolt.
List: time-nuts@lists.febo.com
From: Bob Camp
 
Re: [time-nuts] Lucent / Z3810A log time offset.
Sun, Dec 7, 2014 3:26 PM
If you do, things die fairly quickly. I have empirical data (and a pile of 53131’s) to prove this. You write your magic bytes much less often. What likely happened is you are inside the granularity of that write process.