[time-nuts] time-nuts Digest, Vol 147, Issue 13

[Jim Stone]

Re: TNS-BUF Amplifier

--Jim Robbins wrote:

 Many thanks for your helpful TN work to John A. , Dr. Bruce and John M.
Ordered 3 pieces.

----------------------------------------------------------------------------------------------
I second the thanks and ordered 2 pieces

--Jim Stone

On Wed, Oct 5, 2016 at 9:00 AM, <time-nuts-request at febo.com> wrote:

> Send time-nuts mailing list submissions to
>         time-nuts at febo.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> or, via email, send a message with subject or body 'help' to
>         time-nuts-request at febo.com
>
> You can reach the person managing the list at
>         time-nuts-owner at febo.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of time-nuts digest..."
>
>
> Today's Topics:
>
>    1. Re: Need Time Help (Mark Spencer)
>    2. TNS-BUF Amplifier (James Robbins)
>    3. Re: Need Time Help (Chris Caudle)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 5 Oct 2016 07:35:21 -0700
> From: Mark Spencer <mark at alignedsolutions.com>
> To: Peter Torry <peter.torry at talktalk.net>, Discussion of precise time
>         and frequency measurement <time-nuts at febo.com>
> Subject: Re: [time-nuts] Need Time Help
> Message-ID:
>         <DBFC5AA1-67C3-4DDD-BB8F-EE398A7E022D at alignedsolutions.com>
> Content-Type: text/plain;       charset=us-ascii
>
> Yes I'd be curious in knowing more about this as well.  I've often
> observed time differences from other stations of several tenths of a second
> when running the JT modes on HF.  Although I am beginner at EME I have made
> a couple of EME (earth moon earth) JT65 contacts on VHF without taking any
> special measures to sync the time on a Windows XP machine beyond using the
> built in features of the operating system to sync to my own local time
> server which was in turned synced to the 1 pps output of a GPS timing
> receiver.
>
> I've also made FSK441 contacts (another related form of amateur radio
> digital communications) in the field without any time reference besides the
> free running clock in my Windows xp laptop.  If there is a significant
> performance improvement to be had with these modes by having time nuts
> levels of timing precision on my computers I'd be very interested to know
> more.
>
> All the best
> Mark S
>
> Sent from my iPhone
>
> > On Oct 5, 2016, at 6:18 AM, Peter Torry via time-nuts <
> time-nuts at febo.com> wrote:
> >
> > I must admit to being rather puzzled at the sub microsecond timing
> requirement as I use ntp to set the W7 clock in my computer and have not
> had any issues. In fact less than one second is OK for the usual two minute
> periods that are required to allow for the Faraday rotation. Although I use
> a GPSDO for a frequency reference I find JT software reasonably tolerant of
> frequency.  As I may be missing something I would welcome observations on
> how important the period timing requirement is, you never know I might get
> more contacts.
> >
> > Regards
> >
> > Peter
> >
> >
> >> On 05/10/2016 12:50, Graham / KE9H wrote:
> >> For the group. This ham is trying to work EME. Earth-Moon-Earth
> propagation
> >> path. Aka, "moonbounce."
> >>
> >> He is trying to time synchronize a system, where the other station he is
> >> communicating
> >> with can be any other place on the Earth that can also see the Moon.
> >>
> >> So the system time sync is for a little bit tougher case than a local
> area
> >> network.
> >>
> >> --- Graham
> >
> > _______________________________________________
> > time-nuts mailing list -- time-nuts at febo.com
> > To unsubscribe, go to https://www.febo.com/cgi-bin/
> mailman/listinfo/time-nuts
> > and follow the instructions there.
> >
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 5 Oct 2016 10:56:05 -0400
> From: "James Robbins" <jsrobbins at earthlink.net>
> To: <time-nuts at febo.com>
> Subject: [time-nuts] TNS-BUF Amplifier
> Message-ID: <01c301d21f18$9994aee0$ccbe0ca0$@earthlink.net>
> Content-Type: text/plain;       charset="us-ascii"
>
> Many thanks for your helpful TN work to John A. , Dr. Bruce and John M.
> Ordered 3 pieces.
>
>
>
> 73,
>
> Jim Robbins
>
> N1JR
>
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 5 Oct 2016 10:19:10 -0500
> From: "Chris Caudle" <chris at chriscaudle.org>
> To: time-nuts at febo.com
> Subject: Re: [time-nuts] Need Time Help
> Message-ID:
>         <c250d2aeb72af61ded8aafda4b9f27b1.squirrel at email.powweb.com>
> Content-Type: text/plain;charset=iso-8859-1
>
> On Wed, October 5, 2016 6:14 am, Bob Camp wrote:
> > If you buy a GPS receiver and get it set up for timing, just use it.
> > Then there is no need for NTP at all.
>
> Is there another way to get computer system time set from a GPS receiver
> other than NTP?
> In the case that the system clock is controlled by GPSDO and the seconds
> delineated by PPS, there should be no need for the NTP clock discipline
> code, but I am not aware of any way to inform the NTP daemon that no
> disciplining is needed.  Presumably the code should determine that
> eventually.
>
> In the case that the system clock is free running, the clock discipline is
> still needed, but I found a note in one of the NTP documents (that I can
> no longer locate at the moment) that stated something to the effect that
> NTP did not run well as it could with a single reference, which would seem
> to directly affect the case where a GPS receiver is the only reference.
> That document had only that short note, no details on why or specifics of
> behavior.
>
> --
> Chris Caudle
>
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> time-nuts mailing list
> time-nuts at febo.com
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>
> ------------------------------
>
> End of time-nuts Digest, Vol 147, Issue 13
> ******************************************
>