Hi Graeme,
I would like to know if there are Agilent I/O Libs installed on the scopes WinXP and if you
have the possibility to install VEE. If so, you could use VEE's profiler for a direct compare
of the execution times.
I you say TCP/IP is implemented as SICL Lan or VXI-11 protocol, the Instrument string
should look like
TCPIP0::<scope_ip>::gpib0,8::INSTR which means the GPIB interface will be used
anyway.
Am I wrong ?
Best regards
Christian
Betreff: Re: I/O bottlenecks (Was: We want to entertain you for
Thanksgiving.)
Von: Graeme Hilton <GHilton@slb.com>
Datum: Wed, 13 Oct 2004 11:34:59 +0100
Antwort an: Graeme Hilton <GHilton@slb.com>
> Shawn Fessenden wrote the following:
> > Well that's twice now it's been echoed back to the whole **** list. Anybody
> > wanna go for three?
>
> I'll leave that for someone else. I'm sure Scott and Nicole will be jumping
> down the throat of Mr Mike Kugler, or his ISP, very shortly.
>
> You never know, we might all get a free Thanksgiving dinner
>
> Onto my problem of the day. I'm running a data capture program on an Agilent
> scope (8353A for those that are interested). The program runs in two modes.
> One mode captures 32.8 million data points off one trigger and then does some
> number crunching. The other mode captures between 100 and 500 data points on
> every trigger. I would like this second mode to run as fast as possible (within
> the limitations of Windows XP).
> The limitation at the moment seems to be getting the data off the scope memory
> and into the program. The runtime program runs on the scope (it's a scope with
> WinXP as the operating system. The program uses the TCP/IP address to talk to
> Agilent's Scope program. I also have the option of using GPIB, but I reckon
> that TCP/IP is faster (100Mbps on TCP/IP vs 750kbps on GPIB).
>
> Ideally I suppose it would be fastest to talk directly to the Scope program
> through some API, but I doubt Agilent are going to let that one out of the bag.
>
> If anyone has any ideas on how to acheive maximum data transfer rate, feel free
> to tell me!
>
> --
> Graeme Hilton
> Product Engineer
>
> Schlumberger Sensa
BIOTRONIK GmbH & Co.
EIT-1/CW
D 12359 Berlin - Neukoelln
Tel.: +49 30 689 05 - 4819
--------------------------------------
christian.wienhold@biotronik.de
--------------------------------------
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
I would like to know if there are Agilent I/O Libs installed on the scopes WinXP and if you
have the possibility to install VEE. If so, you could use VEE's profiler for a direct compare
of the execution times.
I you say TCP/IP is implemented as SICL Lan or VXI-11 protocol, the Instrument string
should look like
TCPIP0::<scope_ip>::gpib0,8::INSTR which means the GPIB interface will be used
anyway.
Am I wrong ?
Best regards
Christian
Betreff: Re: I/O bottlenecks (Was: We want to entertain you for
Thanksgiving.)
Von: Graeme Hilton <GHilton@slb.com>
Datum: Wed, 13 Oct 2004 11:34:59 +0100
Antwort an: Graeme Hilton <GHilton@slb.com>
> Shawn Fessenden wrote the following:
> > Well that's twice now it's been echoed back to the whole **** list. Anybody
> > wanna go for three?
>
> I'll leave that for someone else. I'm sure Scott and Nicole will be jumping
> down the throat of Mr Mike Kugler, or his ISP, very shortly.
>
> You never know, we might all get a free Thanksgiving dinner
>
> Onto my problem of the day. I'm running a data capture program on an Agilent
> scope (8353A for those that are interested). The program runs in two modes.
> One mode captures 32.8 million data points off one trigger and then does some
> number crunching. The other mode captures between 100 and 500 data points on
> every trigger. I would like this second mode to run as fast as possible (within
> the limitations of Windows XP).
> The limitation at the moment seems to be getting the data off the scope memory
> and into the program. The runtime program runs on the scope (it's a scope with
> WinXP as the operating system. The program uses the TCP/IP address to talk to
> Agilent's Scope program. I also have the option of using GPIB, but I reckon
> that TCP/IP is faster (100Mbps on TCP/IP vs 750kbps on GPIB).
>
> Ideally I suppose it would be fastest to talk directly to the Scope program
> through some API, but I doubt Agilent are going to let that one out of the bag.
>
> If anyone has any ideas on how to acheive maximum data transfer rate, feel free
> to tell me!
>
> --
> Graeme Hilton
> Product Engineer
>
> Schlumberger Sensa
BIOTRONIK GmbH & Co.
EIT-1/CW
D 12359 Berlin - Neukoelln
Tel.: +49 30 689 05 - 4819
--------------------------------------
christian.wienhold@biotronik.de
--------------------------------------
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Hey, even for $5 I'm in. I can drink an awful lot of booze
> but I reckon that TCP/IP is faster
> (100Mbps on TCP/IP vs 750kbps on GPIB).
One would think so, but then again what protocol is the scope using. If it's
standard TCP (proto 6), there's still overhead. Figure in all the control
bytes & ACKs & NAKs & retries... 100M can start to look like not quite 100M!
In fact any proto will have overhead. I don't think there's all that much,
and there's going to be some overhead on the GPIB too, but at least that's a
parallel bus.
Maybe put a sniffer on it and see what all is going on. Ethereal is
awesomely helpful, but anything that can break out packets would be cool.
> I would like this second mode to run as fast as
> possible (within the limitations of Windows XP).
Well, between 100 & 500 per trig doesn't sound so terrible. How fast is the
trigger? (Oh, yeah! As fast as possible.) And yes - it is going to be an IO
bottleneck. XP can go really fast if it has to. FWIW I'm also seeing more
TCP/IP delay than I'd like to, though it has nothing to do with
instrumentation.
Can the scope be switched to a datagram mode? I'm sure an entire capture
would be too large to packetize, but if it could send out individual points
over UDP that would help.
Or if it could just be set to send after capture. So you don't have to
actually tell the thing to send data, just have it do so. You could start up
a server thread whose whole purpose in life is to just sit there and wait
for the scope to send data, then grab it and queue it up in memory for VEE
to chunk when it has time. As soon as it's done storing data have it send
another trigger. That would keep things rolling pretty darn quick.
-SHAWN-
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".