AnsweredAssumed Answered

vrf Modulated waveform and VEE eye pattern display

Question asked by VRFuser on Nov 11, 2003
>       I'm not quite sure how to do it in VEE, but in general, you'll
open
> a
> reference to the driver object.  IVI-COM drivers typically have two
> interfaces--a class-compliant interface (that's the same for all
Scopes,
> for

If you download one of the Agilent IVI drivers, say the 34401 and look
in the helpfile under getting started, there are step by step breakdowns
on how to bind an IVI-COM driver to all common languages including VEE
and LabVIEW.  I have found this to be the most concise reference
available.

Jay Nemeth-Johannes
Complete Test
720 SW 14th Street
Loveland, Colorado 80537

www.completetest.com

> -----Original Message-----
> From: Brian Powell [mailto:hpvee-list@natinst.com]
> Sent: Wednesday, November 12, 2003 1:17 PM
> To: VRF
> Subject: [vrf] Re: IVI-COM and VEE
>
> "Hal Cornelius" <halc@quixnet.net> wrote...
> >I am starting to check out IVI-COM.  I see that Tek has IVI-COM
software
> and
> >Agilent also has IVI-COM software.  My gut reaction is that I only
need
> to
> >install the IVI-COM (and associated shared components) from Agilent
to
> use
> >it in VEE.  Will this allow me to use my Tektronix test equipment?
Or do
> I
> >need to install the Tek IVI-COM software?
> -----
>       The "shared components" are supposed to be identical, so you
should
> only need to install them once.  However, each device you want to talk
to
> has its own IVI-COM components, so you still need to install the Tek
IVI-
> COM
> driver for your particular device(s).
>       I'm not quite sure how to do it in VEE, but in general, you'll
open
> a
> reference to the driver object.  IVI-COM drivers typically have two
> interfaces--a class-compliant interface (that's the same for all
Scopes,
> for
> example), and an instrument-specific interface (which might be
completely
> different from scope driver to scope driver).  You'll access your
driver
> object through one of those interfaces and find all the low-level
> properties
> and methods that way.  For the most part, you'll find a one-to-one
> correspondence between these properties and methods and the SCPI
commands
> that your instrument understands.  (At least, that's the way it looks
in
> the
> Tek IVI-COM drivers I've seen.)
>       I hope this helps.
>
> Brian Powell
> LabVIEW R&D
> National Instruments Corp.
>
>
> ---
> You are currently subscribed to vrf as: jay.johannes@completetest.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".




---
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".

Outcomes