r quality than any of
> the local board houses I used in the past.
>
> Having said that, I did hand
> manufacture fifty single sided boards from
> photo laminate to completed product in one
> weekend using a Dremel drill
> press for
> somewhere around four thousand
> On Jun 22, 2016, at 1:33 PM, Mark Sims wrote:
>
> The value, quality, and turn-around from all these places is amazing. In
> the olden days, one was paying $50 a square inch for a single prototype board
> with 4 week turn-around.
>
Not to turn this into the “Four
This may be too far off-topic, but I’ve used both Dirty and OSHPark. For U.S.
based folks, Dirty sounds like a better value proposition than OSH, but for
most of us, it doesn’t really work that way:
1. If you are building one thing, getting 10 vs 3 boards doesn’t add value.
2. To actually get
> On Jun 20, 2016, at 12:52 PM, Bob Camp wrote:
>
> Hi
>
> The cheaters way is to simply use a fully synthesized radio tied to a known
> reference frequency.
Yeah, that’s what I’ve got in mind. Both the synthesized tuning LO and the
second LO would be derived from an external
I'm considering taking a shot at the next ARRL frequency measurement contest.
The assumption going in is that the signal is CW, with at least a half minute
or so of just solid "on" at one point or another and that reception is
reasonably good.
I've got a good TIA and excellent references, but
This looks a lot like my initial GPSDO try. I didn’t create an account on that
site, so I couldn’t look at the full schematics, but from the text description,
it looks like they’re using 100 second sampling of whole cycle counts. This
worked ok, but the addition of the phase discriminator
That’s not a USB chip, it’s an RS-232 level converter.
I am not aware of any USB 2 UART devices (that doesn’t necessarily mean much).
They just don’t need to be that fast.
> On Jun 13, 2016, at 11:53 PM, Gary E. Miller wrote:
>
> Yo Mark!
>
> On Tue, 14 Jun 2016 00:53:10
> On Jun 9, 2016, at 10:11 AM, Bob Camp wrote:
>
>
> One very real possibility is: The reason we *have* all these parts is that
> they
> have a bug in them, and were scrapped out because of it.
>
>From what I’ve read elsewhere (and I can’t find a citation right now), they
> On Jun 8, 2016, at 9:59 AM, Charles Steinmetz wrote:
>
> You can achieve substantially lower jitter (phase noise) with a regenerative
> divider, which also allows you to divide by 3/2 for a 10MHz output. I've
> built several like that, and they work extremely well.
>
For what it’s worth, the GPS boards I’ve designed for the FEI devices use the
TPS54[23]31 for the primary 15v supply (which also powers the 5v supply), and
it has been configured with a hysteretic UVLO with a start threshold above 16
volts. Additionally, the slow-start is configured for
requency
> dividers in your system, unless you do something to
> synchronize the various dividers.
>
> This is probably old hat to most readers of time-nuts, but
> I just wanted to mention it in case some were unaware
> of it.
>
> Rick
>
> On 6/8/2016 6:55 AM,
of 3 phases with respect to any other frequency
>> dividers in your system, unless you do something to
>> synchronize the various dividers.
>>
>> This is probably old hat to most readers of time-nuts, but
>> I just wanted to mention it in case some were unaware
>
I’m contemplating trying my GPS board with an FE-405B. That’s a different
kettle of fish, but at the end of that, if I’m successful, one of the goals
would be to be able to use it for the external reference of my 53220A.
Unfortunately, 15 MHz isn’t one of the options - only 1, 5 and 10.
So I
:
>
> Hi
>
> If the counter is the limiting factor, it should scale by 10 as the timebase
> scales by 10. Your data goes from
> 90 ppt at 1 second to 9 ppt at 10 seconds. That is the expected outcome.
>
> Bob
>
>
>> On Jun 2, 2016, at 8:57 PM, Nick Sayer via time-n
Oh, the limitation is on the TimeLab side? I was blaming the TIA. :)
Since then, I have found an advanced gate setting that appears to add 500 ms
after start. The time intervals seem to be without that delay, so it works. The
resulting ADEV is unchanged (other than obviously truncated at low
out a bit, which probably indicates the noise
floor of the 53220A near 1E-12), but the FEI datashe
et shows a spec with points more like tau 1s = 1.5E-11, 10s = 4.5E-12 and 100s
= 1.5E-12.
> On May 30, 2016, at 2:25 PM, Nick Sayer via time-nuts <time-nuts@febo.com>
> wrote:
&g
floor-test/
>
> Anders
>
>
> On Sat, May 28, 2016 at 7:11 PM, Nick Sayer via time-nuts
> <time-nuts@febo.com> wrote:
> So far, I’ve been configuring my 53220A for frequency measurements with a 500
> msec gate time, and using the external reference and one input.
>
So far, I’ve been configuring my 53220A for frequency measurements with a 500
msec gate time, and using the external reference and one input.
If instead I send the two devices into inputs A and B, and ask for the time
interval between the two and give that to Timelab, my results look quite a
> On May 23, 2016, at 11:34 AM, Skip Withrow wrote:
>
> Hello Time-Nuts,
>
> Nick Sayer's GPSDO controller will also work with the FEI FE-5650A rubidium
> oscillators as well. A small modification is needed to the board, but is
> rather trivial.
>
> First, the 5680
>
>> If that sounds too weird, I am open to receive advises for a microcontroller
>> based solution.
>
> If you want to go that way, probably the simplest solution would be to
> take one of Nick Sayers boards, pull out the GPS receiver and feed the
> PPS input from your GPS receiver.
It’d be
Absolutely. There’s a standard AVR ISP header on the board and the firmware is
open source - on github - so even if I didn’t do it, anyone else could.
> On May 22, 2016, at 9:04 AM, GandalfG8--- via time-nuts
> wrote:
>
> Nick,
>
> This looks very interesting but just
at was sent to the 5680.
>
>> On Sat, May 21, 2016 at 8:37 AM, Nick Sayer via time-nuts
>> <time-nuts@febo.com> wrote:
>> You're right. The EEPROM of concern is the one in the 5680. Since they're
>> used, you have no idea how many writes they've already endured
You're right. The EEPROM of concern is the one in the 5680. Since they're used,
you have no idea how many writes they've already endured (likely a low number),
and they're quite old.
Sent from my iPhone
> On May 20, 2016, at 3:20 PM, paul swed wrote:
>
> Mark
> By
> On May 20, 2016, at 2:29 AM, Attila Kinali <att...@kinali.ch> wrote:
>
> Hoi Nick!
>
> On Thu, 19 May 2016 10:08:10 -0700
> Nick Sayer via time-nuts <time-nuts@febo.com> wrote:
>
>
>> This is a mash-up of my breakout board and GPSDO. You give
This is a mash-up of my breakout board and GPSDO. You give it 30+W 18-24 VDC in
(hack up a surplus laptop power supply) and it supplies up to 2A @ 15 VDC and
500 mA @ 5 VDC. In my testing I see around 25 mV p-p of ripple on the 15V rail.
The 5V rail is a bit noisier at around 35 mV.
.
> On May 16, 2016, at 7:25 AM, Nick Sayer via time-nuts <time-nuts@febo.com>
> wrote:
>
> Anybody done business with a reseller of uBlox GPS timing receivers (in the
> US) that they like a lot? Looking to do Qty:10 or so on an irregular basis. I
> haven’t actually picked
Anybody done business with a reseller of uBlox GPS timing receivers (in the US)
that they like a lot? Looking to do Qty:10 or so on an irregular basis. I
haven’t actually picked *which* one I want just yet, as I want to design around
availability and price.
Seems like it’d be easy to use either a small microcontroller or 3 discrete
decade counters to perform a divide-by-1000 from a 10 MHz standard to achieve
this. Am I missing something?
> On May 15, 2016, at 11:17 PM, Ilia Platone wrote:
>
> Can anybody here advice me a
f the 5680A?
>
> On Sat, May 7, 2016 at 6:51 AM, Nick Sayer via time-nuts
> <time-nuts@febo.com> wrote:
>> I got a second 5680 in the mail the other day and so far my firmware isn’t
>> bricking it, so.. yay.
>>
>> A couple of odd things have turned up, though.
I got a second 5680 in the mail the other day and so far my firmware isn’t
bricking it, so.. yay.
A couple of odd things have turned up, though.
1. So far as I can experimentally tell, the tuning step on this unit is 50
times larger than the 17E-15 quoted by FEI. Either the tuning curve is not
I sort of learned a bit about this the hard way not too long ago with my Crazy
Clock. I bought crystals with a tolerance of 10 ppm, but what I learned was
that what that actually meant was that if you buy 1000 of them and give them
all the same load capacitance, they’ll all be within 10 ppm of
I haven’t tried, but if you take two GPS receivers of different manufacturers
and feed them the same antenna feed… to what sort of tolerance can you expect
their solutions to coincide?
I mean, obviously they’re *supposed* to show the same location, but I can
imagine that the math can come up
> On May 2, 2016, at 9:51 AM, jimlux wrote:
>
>
> The real question is whether "cron" is timely enough. No matter, just write
> a script (or python) that reads time in a loop (and you can put a sleep in
> there) and pulses the GPIO when needed.
>
A Raspberry Pi with
To flesh this out a bit more, on a Raspberry Pi, it would be easy to make a
cron job that would pulse a GPIO pin high. They really *want* you to use Python
(thus the name), but this is easy to do in just a shell script. First, do this
to set things up:
#! /bin/sh
GPIO_PIN=9 # pick whatever
> On Apr 29, 2016, at 12:07 PM, Chuck Harris wrote:
>
> We have to sort of conclude that the failure is either
> caused by bad data getting stored, or some sort of overflow
> error.
>
> It really is pretty unlikely that the firmware has been
> changed, unless you happened
I'm sending at most a single 9 byte command per second. I currently wait for
the TX reg empty flag, which means I'm sending them all back-to-back. I'd have
to instead wait for the TX complete flag and then add a delay after that. It's
doable, but it would astonish me if 9 bytes in a row were
In principle, nothing I was ostensibly sending should have written to EEPROM. I
*did* catch and fix a bug that was sending one too few bytes in the 0x2E
command, but if they had their shit together they should have had checksum
mismatches and ignored them.
Sent from my iPhone
> On Apr 29,
fix being required, or is Bert right and the
unit is hosed?
> On 29 Apr 2016 02:02, "Nick Sayer via time-nuts" <time-nuts@febo.com
> <mailto:time-nuts@febo.com>> wrote:
> Just as I started testing the GPS discipline board prototype, my FE-5680A
> seems to have d
> On Apr 29, 2016, at 5:44 AM, Tom Van Baak wrote:
>
> Hi Bert,
>
> I wish you the best solving the FEI bug. Not likely the factory will find and
> fix the bug and issue a service bulletin or offer f/w upgrades to us all.
I’d be happy if there was a way to get the thing
Just as I started testing the GPS discipline board prototype, my FE-5680A seems
to have developed a very odd problem.
If I give it power, it outputs a “kinda” 10 MHz sine wave while it sweeps
around looking for a physics lock. This is as expected.
About the time that I would expect the lock
In my own experience, using the PA6H (AdaFruit) with GPSD as an NTP source
doesn’t work. By contrast, the PPS using the kernel module PPS timestamp driver
works exceptionally well.
The issue with gpsd with this module is that the time reported in the NMEA
sentences always has 0s for the
Rather than use the Hat, you might consider just using the breakout board and
just using hookup wires to connect it up. Connect up the Vin pin to +5, ground
to ground, TX and RX to the serial port pins and the PPS pin to GPIO 18.
That’ll save you $5, if nothing else.
Add
Lady Heather does say what the S/N for each satellite is. I use a lot of PA6H
modules (the AdaFruit ones) and GPSMon also conveniently gives the S/N too.
It’s in the GPGSV sentences.
I’m kinda blessed in that my antenna location is just outside the wall from my
workbench, and that position
> On Apr 22, 2016, at 1:58 AM, GandalfG8--- via time-nuts
> wrote:
>
> Thanks. I’ve taken your suggestion for the sine-to-square converter.
> I believe there are two separate commands for tuning the 5680 - one is “
> temporary” and one writes through to the EEPROM. I’ll
I would think the major difficulty of the scenario you outline would be the
periodicity of the measurements coinciding with whatever environmental
differences impact the device under test during the measurement window. If you
get to see the oscillator the *same* 8 hours every day, are those
select() is the best way to keep from blocking, at least if you’re not going to
use threads or sub-processes.
Unless you’re going to support one or more of the intermediate sound libraries
(ALSA comes to mind), then playing a sound involves opening a device, using
ioctl()s to set the format
short term
stability (OCXO) or medium term (Rubidium) for my reference.
> On Apr 20, 2016, at 1:57 PM, Attila Kinali <att...@kinali.ch> wrote:
>
> On Wed, 20 Apr 2016 07:17:58 -0700
> Nick Sayer via time-nuts <time-nuts@febo.com> wrote:
>
>> I spent some time yeste
I spent some time yesterday mashing together my FE-5680A "breakout" board with
my GPSDO to make a GPS discipline board for it. Before I send the board off to
OSHPark, I'd like to open the design to criticism (and I mean that in its
neutral sense) here first.
At one point, I did try an LM393 instead of a 358. The result was that noise
caused excessive false triggering. The 358, so far as I can tell, when acting
as a comparator lacked sufficient bandwidth and/or speed to keep up with the
noise. The result was that the per-second cycle offsets
> On Apr 11, 2016, at 2:31 PM, Tom Van Baak wrote:
>
>
> 6) picPET output is directly readable by TimeLab via serial/USB.
This one line item twigged my interest.
Dedicating my 53220A to certain long running tasks that don’t require its full
capabilities irks me a
> On Apr 9, 2016, at 10:20 PM, Bill Hawkins wrote:
>
> The schematic is too simple. There is noise on the power line from
> switching things on and off, leakage from dimmers and switching power
> supplies, and the occasional animal that gets across the HV distribution
>
11:34 PM, Nick Sayer via time-nuts wrote:
>> fed into a Raspberry Pi serial port that was running a simple daemon
>> that logged every line it got to syslog. Syslog is handy because it
>> timestamps everything for you and keeps rotating log files and the
>> like.
>
> W
I did this not too long ago.
I used GPS PPS as the reference.
I took a 9v wall wart, pinned one side to ground, ran the other through a
rectifier diode and into one input of an LM358 wired as a comparator, comparing
to 2.5 volts (Vcc/2). The 358 was slow enough that hysteresis wasn’t required.
I’m coming at this thread a bit late, but I’m part-way down the DIY GPSDO
design path and I’d like to share my looking-back perspective, for what it’s
worth.
I think it’s good to start with some sort of goal in mind. The problem with
that statement is that as a beginner, I didn’t fully
I just went through the exercise of adding a phase comparator to my GPSDO. Jim
Harmon from the list gave me the concept for it. It’s quite simple and elegant
and so far it seems to be doing its job. I’m still in the throes of tuning the
firmware to use it. Where I initially went wrong was
Well, they flip the “warning” bit at 0h UTC (4PM PST the afternoon before), so
I think the explanation is that my clock was able to sync up at that time, and
it reacted to the warning bit rather than using that as a cue to make the
change at 0200J like it should have. Either that, or the
Well, then my clock (and perhaps others) is being lazy about interpreting the
bits. If it looks at the left bit only, then that would explain early
transitions. The other possibility is misreading the right hand bit as being a
1 during one reading and deciding that it had “missed” the change
Our WWVB clock switched way, way early last night - like 20:00 or so (PST).
It’s conceivable that it’s a coincidence and it switched because of a parity
error or something like that, but that clock hasn’t exhibited any whacky
behavior as long as I can remember.
> On Mar 13, 2016, at 7:48 AM,
I would second that, FWIW.
> On Mar 4, 2016, at 6:41 AM, Pete Lancashire wrote:
>
> my vote Thunderbolt
>
> known entity, well studied
>
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
performance. Have you taken Phase
> Noise measurement of the output?
I have not. My TIA (53220A) lacks the ability to do so (unless there’s a
capability in there I haven’t found yet - which wouldn’t surprise me in the
least).
> With a good PN system it should be
> possible to fix these
> On Feb 25, 2016, at 12:41 PM, Keith Loiselle wrote:
>
> Below is a message Said asked me to forward to the group:
>
>
> Gents,
>
>
>
> While I haven’t posted here for a while, I have been following Time Nuts.
> One recent post caught my attention, and here are
> On Feb 24, 2016, at 8:30 AM, Chris Albertson
> wrote:
>
> On Wed, Feb 24, 2016 at 6:22 AM, Neil Green wrote:
>
>>
>> What would be my next step up be, hardware-wise, in terms of improving
>> precision, stability, etc? A GPSDO? Budget is
I watched the video. It’s a spectacular discovery, no doubt. But the next day,
the headlines in the non-technical press were all about how we can now “hear”
the universe. The parlor trick the scientists did for the press conference was
what lead the news. I don’t know which side the face-palm
> On Jan 14, 2016, at 3:44 PM, Morris Odell wrote:
>
> Am I missing something here?
>
> I understand the ease and fun of programming up an AVR as much as anyone but
> surely this task could be accomplished easily with a chain of fast
> synchronous TTL or CMOS
:12 PM, Nick Sayer <nsa...@kfu.com> wrote:
>
> Just shy of a half dozen folks have asked, so I'll post here as soon as I
> finish cleaning it up. I'll put it on Github when it's ready. I just need a
> day or two.
>
> Sent from my iPhone
>
>> On Jan 13, 2016,
any interrupts, it’s all good. And by using the timer prescaler,
you have pretty good assurance that that’s the case.
>
> Dan
>
>> On Jan 13, 2016, at 9:35 PM, Nick Sayer via time-nuts <time-nuts@febo.com>
>> wrote:
>>
>> The code is at
>>
>> http
Just shy of a half dozen folks have asked, so I'll post here as soon as I
finish cleaning it up. I'll put it on Github when it's ready. I just need a day
or two.
Sent from my iPhone
> On Jan 13, 2016, at 6:43 AM, Nick Sayer via time-nuts <time-nuts@febo.com>
> wrote:
&g
me Thunderbolt over ser2net? That seems like the best
>
> On Tue, January 12, 2016 4:01 pm, Nick Sayer via time-nuts wrote:
>> I'm going to guess no, because only one thing can connect to the
>> ser2net socket at a time.
>
> No, ntpd would be getting time from the seri
If anyone is interested in the equivalent functionality using an ATTiny25 (for
instance, if you’re already heavily invested in AVR instead of PIC, like I am),
ping me. I’ve privately written code to solve almost the same problem and it
could easily be adapted into doing the same job.
> On Jan
the serial interface all to itself.
I’ve done this with a far more ordinary GPS module to make a public stratum 1
server out of a Pi Zero for the NTP pool (ntp.kfu.com).
> On Jan 12, 2016, at 7:17 AM, Chris Caudle <ch...@chriscaudle.org> wrote:
>
> On Mon, January 11, 2016 7:00 pm,
but can't make it work. My USB/serial
> cable is /dev/ttyUSB0 just like yours. I used your .conf file. But lady
> heather says connection rejected.
>
>
> Ed
>
> On 1/11/2016 8:00 PM, Nick Sayer via time-nuts wrote:
>> I answered my own question. :)
>>
>> s
I answered my own question. :)
ser2net works perfectly as a “server” for LH. I’m using a USB to serial adapter
and the ser2net.conf line for it is
3200:raw:0:/dev/ttyUSB0:9600 8DATABITS NONE 1STOPBIT LOCAL
And for LH, /ip=n.n.n.n:3200 works.
> On Jan 11, 2016, at 9:30 AM, Nick Sayer via t
How about a simpler question. I see in the documentation that LH can use a
network connection to remotely read. Can a server for that protocol be made for
the RPi? That would be super awesome deluxe for me, and assuming it's just a
serial-to-TCP protocol should be nearly trivial to write (heck,
> On Nov 22, 2015, at 7:47 AM, paul swed wrote:
>
> As mentioned a nice answer to the wwvb modulation change.
> I looked up the parts and it seems that they have gone into the NOS state.
> Though you can get some from digikey and such especially in the SOIC
> package. Also
> On Nov 21, 2015, at 2:43 AM, Attila Kinali wrote:
>
>
> MFi means here "Made for iPhone" which is Apples way of extorting money
> from device manufacturers. You have to buy an Apple crypto chip for that
> and put it in each device. And they wont talk to you unless you buy a
I briefly considered designing a board that would GPS discipline the FE-5680A.
It’d simply substitute an RS-232 level shifter for the DAC and would speak the
protocol to trim the frequency. I haven’t done it, though, because the OH300’s
performance specification at low tau is not that far
> On Oct 31, 2015, at 3:29 PM, Magnus Danielson
> wrote:
>
> Some people is very fond of using the frequency measure of counters, I've
> grown more and more sceptic to it for a number of reasons when doing ADEV and
> friends, then I use TI that avoids a number of
> On Oct 24, 2015, at 2:43 PM, Gregory Maxwell <gmaxw...@gmail.com> wrote:
>
> On Fri, Oct 23, 2015 at 11:08 PM, Nick Sayer via time-nuts
> <time-nuts@febo.com> wrote:
>>
>>> On Oct 23, 2015, at 2:09 PM, Gregory Maxwell <gmaxw...@gmail.com> wrote:
&g
> On Oct 23, 2015, at 9:10 AM, Attila Kinali <att...@kinali.ch> wrote:
>
> On Fri, 23 Oct 2015 07:30:10 -0700
> Nick Sayer via time-nuts <time-nuts@febo.com> wrote:
>
>
>>> BTW: Tom van Baak mentioned in a private mail, that the DOC supply current
>&
> On Oct 23, 2015, at 10:18 AM, Nick Sayer <nsa...@kfu.com> wrote:
>
>
>> On Oct 23, 2015, at 9:10 AM, Attila Kinali <att...@kinali.ch> wrote:
>>
>> On Fri, 23 Oct 2015 07:30:10 -0700
>> Nick Sayer via time-nuts <time-nuts@febo.com> wrote:
&g
> On Oct 23, 2015, at 2:09 PM, Gregory Maxwell wrote:
>
> On Tue, Oct 20, 2015 at 8:53 PM, Bryan _ wrote:
>> Saw this on the Hackaday site if anyone is interested.
>> https://hackaday.io/project/6872-gps-disciplined-tcxo
>
> Will this design that uses
> On Oct 23, 2015, at 2:25 AM, Attila Kinali <att...@kinali.ch> wrote:
>
> On Thu, 22 Oct 2015 21:07:38 -0700
> Nick Sayer via time-nuts <time-nuts@febo.com> wrote:
>
>
>>> I like the choice of the TXCO. Which allows you to replace it
>>> by the
> On Oct 22, 2015, at 1:17 AM, Attila Kinali wrote:
>
> On Tue, 20 Oct 2015 13:53:54 -0700
> Bryan _ wrote:
>
>> Saw this on the Hackaday site if anyone is interested.
>> https://hackaday.io/project/6872-gps-disciplined-tcxo
>
> Oh.. that one looks nice.
21, 2015, at 11:33 PM, Bob Albert <bob91...@yahoo.com> wrote:
>
> How much for the kit?
>
> Bob
>
>
>
> On Wednesday, October 21, 2015 9:03 PM, Nick Sayer via time-nuts
> <time-nuts@febo.com> wrote:
>
>
> Thanks. That’s me.
>
> I posted
Thanks. That’s me.
I posted a while ago here, but I’ve made a great deal of progress since then.
I’ve logged most of what I’ve discovered and learned on the project itself. I
believe I now have reasonable confidence in the performance of the two models.
I’d be happy to share my methodology so
> On Oct 14, 2015, at 4:42 AM, billriches wrote:
>
> Not milisecond time distribution but time related!
>
> In the early half of the 1900s Western Union was in the time business. They
> would rent businesses such as banks, office buildings, etc clocks for a few
>
I’d like to quickly mention that I’ve now got an FE-5680A “breakout board” for
sale on Tindie.
It has a 2.1mm barrel connector for 16-24 VDC @ 30W - easily obtainable from a
surplus laptop power supply. It has a buck converter to make 15V and an LDO
(from that) to make 5V. It has a two pin SIP
I just went through this exercise. You can use DC blocking on all ports and an
injector, but they also have splitters where one port is a DC-pass and the rest
are DC block. You use the pass port for a device you’re just always going to
have hooked up. In my case, it’s the GPS module on a
I’m running the latest beta, and I’ve found the spot in Edit > Trace details
where you tell it the two sources that contribute to a particular dataset. I’d
expect that having done that and loaded two traces A-B and B-C that I’d be able
to elect to show the N cornered hat and see something
> On Sep 27, 2015, at 5:06 PM, John Miles wrote:
>
> If you're only loading two files, that's definitely not going to work since a
> 3-cornered hat requires 3 plots. In your example, there must be a third plot
> representing A-C, so that each of the three sources will
> On Sep 19, 2015, at 4:20 PM, Nick Sayer via time-nuts <time-nuts@febo.com>
> wrote:
> […]
> I’ve tested it against GPS and as it came, it had about a 0.5 ppm error.
Oops. That was supposed to be 0.5 ppb - 500 ppt.
___
time
uming it shows locked, that would suggest that (for what ever reason)
> it’s been re-tuned at some point after it left the factory.
>
> Bob
>
>> On Sep 20, 2015, at 9:06 PM, Nick Sayer via time-nuts <time-nuts@febo.com>
>> wrote:
>>
>>
>>> O
I’ve designed and built a small power/interface board for my FE-5680A. It takes
DC power from a surplus laptop power supply (16-24 VDC) and uses a buck
converter to drop that down to 15v and a 5v LDO to supply the 5v pin. It brings
the serial and PPS out to a 4 pin SIP header and the 10 MHz to
n.
>
> Normal drill is to go back to the seller and see what they do or don’t know
> about it.
>
> Bob
>
>
>> On Sep 10, 2015, at 9:06 PM, Nick Sayer via time-nuts <time-nuts@febo.com>
>> wrote:
>>
>> I’ve acquired an eBay 5680. I’ve hooked it
are getting -5V, my guess is that you have an RS-232
>> output on that pin.
>>
>> Normal drill is to go back to the seller and see what they do or don’t know
>> about it.
>>
>> Bob
>>
>>
>>> On Sep 10, 2015, at 9:06 PM, Nick Sayer via time-n
I’ve acquired an eBay 5680. I’ve hooked it up to +15 and +5 and am getting 10
MHz out and the test pin is low. The unit is warm and within any reasonable
expectations, it appears to be working properly.
What I wonder about is pin 6 on the connector. Google results seem to indicate
that that’s
Sent from my iPhone
On Aug 18, 2015, at 4:42 PM, Charles Steinmetz csteinm...@yandex.com wrote:
Nick wrote:
I believe I'm at or better than the stability I originally sought. Part 1 of
my question is whether that's actually true or whether my naivety is
presenting me with a delusion.
On Aug 17, 2015, at 12:49 PM, Nick Sayer via time-nuts time-nuts@febo.com
wrote:
On Aug 17, 2015, at 12:07 PM, Attila Kinali att...@kinali.ch wrote:
You really should read the wikipedia article on the PID loop and implement
a simple PI loop (no need for the D part). That's not more
On Aug 17, 2015, at 1:16 AM, Attila Kinali att...@kinali.ch wrote:
On Sun, 16 Aug 2015 16:54:08 -0700
Nick Sayer via time-nuts time-nuts@febo.com wrote:
If I counted correctly, you have a maximum offset of 350ns. For GPSDOs
that are close to each other, that's a quite considerable
, but perhaps
it wasn’t the correct one.
There is only so much you can pack in a single message …
Bob
Bob
On Aug 16, 2015, at 3:39 PM, Nick Sayer via time-nuts time-nuts@febo.com
wrote:
On Aug 16, 2015, at 12:31 PM, Tom Van Baak t...@leapsecond.com wrote:
Anyway
101 - 200 of 207 matches
Mail list logo