On Tue, Aug 14, 2018 at 10:34 PM Tom Van Baak wrote:
> One version of this would be to make the pulse width 100 ns * (1+STOD), where
> STOD (Seconds-Time-Of-Day) varies from 0 to 86399. So your pulse width
> would vary from 100 ns to 864 ns = 8.64 ms. If 100 ns is too short use a
>
> Arecibo did a kind of cute trick with their distributed 1PPS. The one
> second pulses were of one length
> (100 ns as I recall), but the 10 sec boundaries had the pulses be about
> twice that length. One could carry
> this scheme to considerable lengths as desired.
Dana,
One version of this
Arecibo did a kind of cute trick with their distributed 1PPS. The one
second pulses were of one length
(100 ns as I recall), but the 10 sec boundaries had the pulses be about
twice that length. One could carry
this scheme to considerable lengths as desired.
Dana
On Tue, Aug 14, 2018 at 4:00
On Tue, 14 Aug 2018 20:52:50 +0200
"Bernd Neubig" wrote:
> Is there any common practice for the duty cycle of the 1 PPS pulse?
As short as the consumer can take. Because a long pulse means that
you are wasting energy and heating up both the pulse generator
and the consumer. As TvB wrote, it
