[time-nuts] z3801a, z3805a, z3815a, z3816a, thunderbolt and thunderbolt
justin at fuzzythinking.com
Wed Nov 30 17:11:02 EST 2011
I've done it before with the Palisade driver in non-polling mode. It
works, but you have to rely on the timing of a serial port and apply your
best guess for a delay. If he's trying to detect phase differences between
multiple thunderbolts, the serial port + OS combination might be too
jittery to measure that difference.
On the other hand, I suspect using a FatPPS and the ATOM driver would be
even less jittery than polling (if it worked), so maybe it's a moot point.
On Wed, Nov 30, 2011 at 4:56 PM, <bg at lysator.liu.se> wrote:
> Hi Justin,
> > There are some issues using a Thunderbolt with NTP. See
> > http://www.eecis.udel.edu/~mills/ntp/html/drivers/driver29.html (the
> > about event polling).
> The Trimble Palisade (aka Acutime, Acutime 2000, Acutime Gold) has a nice
> feature called Event input.
> "Event input
> The Acutime Gold accepts an external event input in the shape of an RS-422
> pulse. The external event pulse input is supported on Port A (pins 6 and
> 7). The Acutime Gold transmits a TSIP time packet (0x8F-0B or 0x8F-AD) in
> response to the event input. The TSIP packet increments the event count
> field for each event received. The event time stamp is generated within
> 488 nanoseconds of its arrival at the Acutime Gold interface connector."
> The prefered mode for the palisade driver is to use this feature. When the
> driver was adapted for Thunderbolt is was seen as a problem that the Tbolt
> receiver lacked the "Event input".
> I have not runt a Tbolt with NTP, but it should be very doable with the
> Palisade driver in the "Thunderbolt"-mode. Another option could be the
> running in the Trimble TSIP mode. (mode 10)
> time-nuts mailing list -- time-nuts at febo.com
> To unsubscribe, go to
> and follow the instructions there.
More information about the time-nuts