[time-nuts] Timelab, two SR620s and losing samples

Poul-Henning Kamp phk at phk.freebsd.dk
Mon Jan 18 03:05:20 EST 2016


--------
In message <00d801d15170$f91c6630$eb553290$@miles.io>, "John Miles" writes:

>By timing issues,
>I wasn't referring to layer-1 handshaking, but rather the interplay
>between the GPIB software application, the network or bus connectivity
>between the app and GPIB controller, the controller itself and its
>firmware, and an addressable counter that returns each measurement
>only in response to a command from the app.

If your measurements are timing sensitive at or below milliseconds,
you should *always* pace them with an external trigger.  They didn't
add that input just to take up space.

If you insist on pacing via the GPIB, the protocol has a primitive
for that, TRG, which is usually hardwired to the external trigger
circuitry in quality instruments.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.



More information about the time-nuts mailing list