Steven,
there seems to be some mismatch in your process understanding. Let me explain some technical background.
1. You write some commands to the Xantrex. This means finally sending a
data packet via USB to the GPIB controller. This data packet contains
the instruction to send the command to the Xantrex. As USB is a
packet based protocol, there is often a delay between receiving some
data to be sent and the actual sending of the packet. USB data packet
have a somehow fixed size. 'Incomplete' (e.g. not filled) packets are
usually delayed to save bandwith by accumulating complete packets.
There is, however, a timeout, when even those packets are sent, but
this timeout is an effective delay. We have seen delays of up to nearly
a second.
2. After all, the GPIB part of transmission is quite quick and may reach the throughput you mentioned.
3. When the Xantrex has received the command, ist must execute some
code and send a respond back. This takes some time, which depends on
the firmware and probably the command you requested to be executed.
Even a simple voltage increase may take some 10 to 100 ms or more until
the response is send.
4. The response goes first through GPIB transmission - see 2.
5.The GPIB controller translates the response into a USB data pvcket - see 1.
You may gain some speed when using a different GPIB controller -
especially one that directly sits in the controlling PC (usually a PCI-
or PXI-based one). But I am not sure if this will solve your problem.
A much better way is to check if your Xantrex device supports such
sweepings by itself. If so, you instruct it to perform the required
action and trigger it to start. After that, there is no more
communication needed in order to fullfill the sweeping task. And such
those delays are no longer affecting the process.
Greetings from Germany!<br>-- <br>Uwe