interface
is TTL and all commands are single byte commands...
btw: the reason for the limit on number of devices powered down is
that NMOS/TTL based interface chips tend to clamp the bus to ground.
This is less of a problem with modern CMOS based interface chips.
--
Poul-Henning Kamp | UNIX since
different.
This doesn't happen in any of the designs I've seen. They basically have
a FET in series with the line and when the instrument is OFF, it is really
OFF.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer
In message [EMAIL PROTECTED], David Forbes writes:
Has anyone on this list ever heard of EECL logic used anywhere
besides HP test equipment? I hadn't heard of it *at all* before
today, and I've been designing high speed digital stuff for over 25
years.
Cray computers.
--
Poul-Henning Kamp
In message [EMAIL PROTECTED], David Kirkby writes:
Poul-Henning Kamp wrote:
http://www.icst.com/datasheets/ics2305.pdf
Be aware they don't mean the same with jitter as you do: they
include production tolerances, so the 200ps is the worst case jitter
measured between two output pins
-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
time-nuts mailing list
time
can recommend this site for data-sheets:
http://www.alldatasheet.co.kr/
They almost have too many...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can
list to give a history for the board.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
such that the
3rd, 5th and 7th overtones were intact.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
http://www.nasawatch.com/archives/2005/10/nasa_space_stat_2.html#more
Halfway down the second table it looks like the clock-in-space project
for ISS is getting killed...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer
just have
to be able to receive three chains, and you know what time it is.
I'm probably the only person to ever having used this feature :-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
5000M was multi-chain (and took a PDP/11 ?)
Megapulse have some multi-chain receivers as well.
I don't think I've seen any other.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never
? Is it any good ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
time
, especially in an arbitrary way, can be frustrating to code up.
Other than that, the packets seem to be 'about the same' as Motorola
packets and the bundles you need may indeed be separated out
differently than the M12+.
But Trimble still don't have a checksum, do they ?
--
Poul-Henning Kamp | UNIX
. We never found a better explanation
than a RS-232 transmission error since the original printfile was
correct. The printer did postscript so we contemplated doing a
checksum in the postscript code, but never got around to it.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL
-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
time-nuts mailing list
time-nuts
In message [EMAIL PROTECTED], John Ackermann N8UR writes:
Happy holidays to all. I'll be raising a toast* at 31/12/2005 23:59:60.
How about you?
You bet, at 1AM new-years night a fair number of toasts gets hoisted
here in .dk :-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
in advance,
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
In message [EMAIL PROTECTED], Scott Newell writes:
At 12:35 PM 12/21/2005 , Poul-Henning Kamp wrote:
I have asked the GNUradio crew to help out with off-the-air samples,
and I hope people in this forum can help me out with captured data
streams from all sorts of radio receivers (WWV/DCF/GPS etc
it.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
time-nuts mailing
engineering resistant.
There is practically nothing to learn today by taking things apart:
you can't see how they work.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what
to teach them disassembly before you can satisfy their curiosity,
the technological world is in deep trouble indeed.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice
loop antenna.
It should contain not only HBC and TDF, but also DCF77, Rugby, LORAN-C
but also anything else up to around 300 kHz (low-pass filter in my antenna)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD
that
there will be enough engineers 10-20 years from now ? Doesn't look
like it over here in Denmark.
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can
.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
time-nuts mailing
or not, doesn't do it.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
into the capture data and you
can also see the extra second going from 28430.638 to 28491.639
Rugby and HBG and France Inter will follow in the coming days if I can
get my software to decode them.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since
Looks like the inserted the leapsecond after the minutemarker:
http://phk.freebsd.dk/Leap/20051231_HBG/
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can
).
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
time-nuts mailing list
:
http://www.metas.ch/en/labors/official-time/pdf/hgb_info_e.pdf
The description given there of how the leap-second is handled, clearly
disagrees with our observations.
Thanks! I've updated my page.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since
I just received email from Gregor Dudle at Metas and he confirmed
that HBG did bungle the leap second.
He says the bug is found and fixed for the case there should ever
again be a leap second
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC
698207
NTPns
We're certainly far from no one, in the above about 60% (698 of
1144) of the machines syncing to my server is in the millisecond
range and about 20% (207 of 856) for machines synching from other
servers. For the entire population it is about 45% (905 of 2000)
--
Poul-Henning
don't even know what is ?.
I guess we think we know what they are now, but the argument is
still pretty powerful as we don't know how stable we can expect
pulsar rates to be in the long term.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
and that they use UTC in
various forms for that, but not phase is not linked to UTC in
the sense that a synchronous clock would loose the leapsecond
at some point in the future.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer
In message [EMAIL PROTECTED], Magnus Danielson writes:
However, it may be stable enought for tau in the range of 1 Ms to 1Gs or so,
and that is still usefull.
Ohh, absolutely.
But how would we know ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP
allowed that
in more recent firmware.
Poul-Henning
PS: If you read the PRS10 docs, it's pretty simple to replicate
their PLL parameters. Just remember that they had to do it
on a small microcontroller and you'll see how simple it is.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
to record these every hour and after a day or so make a
tweak to the PRS10 frequency. This way the only additional equipment
would the the uC connecting to the PRS10 serial port.
That's more or less what I did, except I used a box from www.soekris.com
instead of a uC to do the job.
--
Poul-Henning
In message [EMAIL PROTECTED], Chuck Harris writes:
Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Chuck Harris writes:
It would be interesting to see how such an oven performs compared
to the traditional double oven.
According to a guy at the danish metrology lab, the optimal
absorption.
All of the kilogram artifacts are slowly changing weight (Can't
remember which direction though) and that's why there is so much
focus on a different definition of the kilogram.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
receivers can take an external clock signal from your
10MHz house standard.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained
a board with it...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
can be configured
for all sorts of experiments.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
is constant and known, so
it can be handled in software).
Consider adding a D/A converter for tweaking OCXO. Using the two-tier
trick which SRS uses in the PRS10 may be a good and cheap way.
So does the basic idea make sense?
Worked fine for me :-)
--
Poul-Henning Kamp | UNIX since Zilog
are summed through a 1:1000 network
to give around 20 bits of effective resolution at the cost of some
discontinuities.
Because the ratio is only a quarter of the full ratio of the individual
D/A's, they can always center the interresting range in the lower D/A's
range.
--
Poul-Henning Kamp | UNIX
it in hardware would be more expensive than in software, hardware
access is much slower than memory access.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately
glitches). How bad are these discontinuities/glitches?
I can't see them in my log.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained
.
I have not writte any snazzy tool that does it all, but I have some
hacked together programs that will read my 5370B and a program which
will do allan and modified allan on a dataset.
C-programming skills required.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED
.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
time-nuts mailing
the opposite way this time, and precompute that for the desired
DDS frequency.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained
).
The reason you can precompute it is that the DDS produces a cyclic
and predictable signal.
Over and out.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can
in a +/-
1/2 DDS clock cycle time error, this phase-quantization error becomes an
additional signal to that of the carrier frequency...
I'm not sure it's easier to do the math under that interpretation, but
it is certainly valid.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED
message?
That's the negative sawtooth correction.
For me, It looks like a message telling the actual
error of one particular 1PPs pulse. Does it sound
right?
Exactly.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer
can capture and store the almanac on your
computer/microcontroller/whatever and initialize the receiver with
it when you cold start.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never
their
polarisation and work fine.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
and framelengths
being quite long, a receiver will not necessarily notice loss of
signal instantly, and similarly, it may not be able to reaquire
locking instantly because even very small drifts will push the
correlator out of the center in a few seconds.
--
Poul-Henning Kamp | UNIX since Zilog
I'm sure some of you thought time-signals were an risk-free hobby:
http://people.freebsd.org/~phk/dlink/
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice
$company.vendor.pool.ntp.org or something like that so it can be
turned off or pointed to their own servers or some variation of that
if/when their software turns out to be broken[1].
D-Link would be an eminent posterboy for the need for that concept.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
.
The FreeBSD server in question has more bandwidth than that, last
I heard it was pretty much on a GigE that had several Gig's of
bandwidth backing it. We've taken several slash-dottings in
the past with no trouble.
(Yes, FreeBSD _is_ a good server OS :-)
--
Poul-Henning Kamp | UNIX since
.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
time-nuts mailing list
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
time-nuts mailing list
of a content-managlement-system
which must lookup everything in a database.
For a plain HTML in a single file page like this one, the slash-dot
effect is non-existent.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD
38mm fan these days.
There are many 92x92x25 mm fans available, you may be able to
substitute one of these if 92x92x38 is impossible to find.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
. The absorption
also makes the glas darker and darker, being a major wear-out
mechanism for Rb units.
As far as I know, this is why Rb is never classified as a primary
standard: A drift-free unit has yet to be constructed.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED
than Cs standards?
They last longer.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
models for the drift and they give very good
match to reality.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
In message [EMAIL PROTECTED], John Day write
s:
So Loran isn't really dead yet!
Not quite.
The draft European Radio Navigation plan shows that Loran-C gives
22% of the benefit for 7% of the money.
But who knows if that translates to political decisions in its favour.
--
Poul-Henning Kamp
of a nearby LORAN-C
chain. Connect it to the external sync trigger of your spectrum analysator
Then set it for start=100khz, stop=100khz, bandwidth=10khz and video
averaging (or whatever it's called)
You should be able to see the loran-C pulses quite clearly.
Poul-Henning
--
Poul-Henning Kamp
are at?
This is called Time Of Coincidence and it works generally OK.
In Europe where the chains have 4 digit GRIs it works much better
because most of the chains were chosen as prime numbers so they
only coincide very seldomly.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED
In message [EMAIL PROTECTED], Poul-Henning Kamp writes:
In message [EMAIL PROTECTED], M. Warner Losh writes:
Can't you recover the time by tracking multiple chains and using the
relationship between them to come up with at least small number of
possible seconds? Hasn't the US started
time :-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
time
In message [EMAIL PROTECTED], [EMAIL PROTECTED] writes:
Hello Poul,
I have seen these jumps on my M12+ as well. Would increasing the mask angle
to say 20 degrees help mitigate this?
Depends what your antennas view of the horizon looks like :-)
--
Poul-Henning Kamp | UNIX since Zilog
this problem.
Aha! A cure. Would you post a URL? Pretty please?
http://phk.freebsd.dk/rrdd
It's not very slick, but it works :-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute
.
No mounting holes in the PCB ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
In message [EMAIL PROTECTED], John Ackermann N8UR writes:
If you think we should include holes, I'll see if I can stick one or two
on the board.
I would prefer at least one. Double-stick tape is all nice and good,
but nothing beats a M3 bolt.
--
Poul-Henning Kamp | UNIX since Zilog
In message [EMAIL PROTECTED], Jim King writes:
I've found that when Windows is behaving its SNTP client does a pretty
good job of keeping the system time within 100ms of an NTP server.
I've heard from a M$ insider that they aim for no better than
plus or minus a few seconds.
--
Poul-Henning
In message [EMAIL PROTECTED], Rex writes:
Just curious... 19.6608 MHz seems like an unusual frequency. Is there
some logical reason why that frequency was chosen for this application?
It is the heartbeat of CDMA celluar networks as far as I know.
--
Poul-Henning Kamp | UNIX since Zilog
times indeed...
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
a dislocation in the
crystal lattice.
For new crystals pollution left over from manufacturing will also
be a cause.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can
In message [EMAIL PROTECTED], Brooke Clarke writes:
Hi Poul:
Thanks for that insight on Loran-C in Europe.
Have you done any work on the new digital data format for Loran-C?
I've played a bit with EuroFix, but not the new rubber pulse format
since I can't receive it here.
--
Poul-Henning
) which would
imply a clock frequency of approximately 40 MHz.
The M12 does some kind of temperature compensation, so if you feed
in an external frequency, you need to find a way to turn that off.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC
on the
low (or if you prefer: high) side of the ideal.
Given that the spikes in the (corrected) PPS on the Oncore UT were
related to just such a sign bug, I'm not surprised Motorola did
this for the M12 family.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP
In message [EMAIL PROTECTED], Richard \(Ric
k\) Karlquist writes:
Wasn't humidity also the main source of trouble with the cesiums ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never
didn't, but I bought another PRS10 which had it.
I belive only upgrade option is mail in to SRS.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately
In message [EMAIL PROTECTED], Fred King
writes:
Hmmm.. How fast could one update the internal cable delay value?
It doesn't help you, because the PPS pulse can only be generated
at the same discreete places relative to the Oncore clock.
--
Poul-Henning Kamp | UNIX since Zilog
changes
in threshold voltage would come out as large jitters in time.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
codes, Ie: readings that just didn't
happen in practice.
Testing any other such design is similarly trivial.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what
of the C-field,
but if you disable that, you ruin the long term numbers.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
In message [EMAIL PROTECTED], Tom Van Baak writes:
If nothing else everyone should view this one plot
where 4 rubidiums are compared:
http://www.leapsecond.com/images/4rb.gif
Tom, can you try to measure the PRS10 with the magnetic switching
turned off ?
--
Poul-Henning Kamp | UNIX since
In message [EMAIL PROTECTED], Magnus Danielson writ
es:
Eh... well, not the antenna. :O) That you stick onto a temperature-stabilzed
concrete piller built onto the stable rock.
At this point Magnus forgot to say: You stop continental drift and ...
:-)
--
Poul-Henning Kamp | UNIX since
better with Vivaldi string quartets than they do with Metallica.
But if you can make your master-tape sound good on BW, it will sound
good on a wet cardboard box.
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer
In message [EMAIL PROTECTED], Joseph Gray writes:
Can anyone recommend a low cost GP-IB PCI card (and cable) that works
with FreeBSD and/or linux?
The only two that work with FreeBSD are the PC2A (or PCIIA) and PCI-GPIB
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED
away with trace amounts
of heavy metals on the banned list, under a theory of environmental
contamination, but if you include them deliberately, you're in
violation.
Fortunately metrological equipment is easy to get an excemption for :-)
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
In message [EMAIL PROTECTED], Chuck Harris writes:
Actually, as I understand it, all test equipment is exempt from RoHS. As are
all batteries, oddly enough.
RoHS is mostly aimed that the high-volume markets.
Batteries are not excempt, they get their own special rules.
--
Poul-Henning Kamp
In message [EMAIL PROTECTED], [EMAIL PROTECTED] writes:
How much test equipment ends in a land fill?
RoHS also addresses this, the manufacturers have to take back
old equipment and dispose of it properly.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP
one of them.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
time
://phk.freebsd.dk/20040101svn23/
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
on the receiver's primary purpose is not
that wrong!
The motorola timing receivers can also run in navigation mode
and I belive they do so by default.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
can't
help wondering how much relativity data the USN might have in their
classified files.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately
...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
time-nuts mailing list
, it all depends how precise you want it.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
time-nuts mailing list
801 - 900 of 1767 matches
Mail list logo