Hi,
Looking online, I've heard of GPIB latency being on the order of 30us, but I assume this is from a PC to an oscilloscope. If I were to run a series of SCPI commands locally on the oscilloscope, through a C program, does anyone know what the latency might be around? I am using a 54855a scope.
Thanks,
lcalderin
Looking online, I've heard of GPIB latency being on the order of 30us, but I assume this is from a PC to an oscilloscope. If I were to run a series of SCPI commands locally on the oscilloscope, through a C program, does anyone know what the latency might be around? I am using a 54855a scope.
Thanks,
lcalderin
The short answer is, "This is not specifiied, and will be highly variable".
Where did you get the 30 usec number? Are you talking about GPIB, or SCPI? What do you mean by latency? Does it include transmission time, decode time, turnaround time, etc.?
In the scopes, all commands go through the same internal pipeline. This includes USB, LAN (local or remote), and GPIB. This means that commands from all sources take about the same amount of time to be decoded and recognized by the scope. Actually getting data from the scope will take differing amounts of time, just due to the differing maximum speed of the various transport mechanisms.
The only way you'll be able to figure this out will be by writing some code. If you use a socket connection between your program and the scope, you should be able to run it from anywhere (local or remote), using any transport (USB, LAN, GPIB), and compare the results.
Al