AnsweredAssumed Answered

vrf Instrument Panel driver development ???

Question asked by pavel.korensky on Sep 16, 2002

Like • Show 0 Likes0
Comment • 4

Hello,

anyone knows where it is possible to find some documentation about
instrument panel driver development ?

I have the BK Precision 4070A waveform generator with serial port and I
would like to write the driver for it.

Best regards

PavelK

---
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@it.lists.it.agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".

No one else has this question

Outcomes

4 Replies

reiner.schlieker Sep 16, 2002 5:54 PM
Mark Correct
Correct Answer
When I first started using VEE, I wanted to do the same thing, but HP
strongly discouraged me from doing this, as it is quite tricky, apparently.
Therefore, finding any resources to do this might prove difficult. The
easiest way to create a driver for an instrument is to create functions for
each instrument operation that you require, and use Direct I/O inside the
functions to get the instrument to do what you want. You can then keep each
set of functions as a separate library, and load each library into your main
program as required.

Reiner

-----Original Message-----
From: Pavel Korensky [mailto:pavel.korensky@dator3.cz]
Sent: Tuesday, September 17, 2002 7:18 AM
To: VEE vrf
Subject: [vrf] Instrument Panel driver development ???

Hello,

anyone knows where it is possible to find some documentation about
instrument panel driver development ?

I have the BK Precision 4070A waveform generator with serial port and I
would like to write the driver for it.

Best regards

PavelK

---
You are currently subscribed to vrf as: reiner.schlieker@siemens.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@it.lists.it.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@it.lists.it.agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Like • Show 0 Likes0
Actions
ramarquardt Sep 16, 2002 6:21 PM
Mark Correct
Correct Answer
> anyone knows where it is possible to find some documentation about
> instrument panel driver development ?

I'll see if I can dig up some documentation. I might have some buried in a
box some where.
Jay and I use to write these drivers and oversee their development, although
that was a long time ago. If you have specific questions, feel free to ask
them here. At least one of us has touched each of the supported Classic
drivers in Agilent's list. We are listening and I'm sure the questions
will jog our memories.

To start with, find an instrument in the "Classic" list that is close to the
instrument that you want to develop a driver for. This will give you the
basic driver structure. There are two parts to the driver - the component
section and the panel section. The component section defines all the
components (or variables) and the actions associated with them when they are
"set" (changed by the user) or when doing a "get" (receiving from the
instrument). The panel section defines the display look and feel. If you
have components that are linked together or commands that are chained
together in one big command, there are "tricks" that can be used to get them
working the way you like.

As far as building a Classic driver versus just doing Direct I/O ... If
there are only a few things that you wish to do, doing direct I/O is a lot
faster - you can write many Direct I/O boxes in a day. A big command or
SCPI subsection may take a day to write in a Classic driver by the time you
do the component section and panel section and sort out all the
interactions. On the other hand, the Classic driver will give you
flexibility, especially if the end user may not fully understand the part in
the manual that says "you must send the commands in this order." That is,
the Classic driver can have all the details of the manual built into it.

If you have any further questions, just ask - either on the reflector, or to
me individually.

Les Hammer
Complete Test
PO Box 6
Loveland, CO 80539
970-663-0006
Les.Hammer@CompleteTest.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@it.lists.it.agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Like • Show 0 Likes0
Actions
les_hammer Sep 16, 2002 9:07 PM
Mark Correct
Correct Answer
> anyone knows where it is possible to find some documentation about
> instrument panel driver development ?

I'll see if I can dig up some documentation. I might have some buried in a
box some where.
Jay and I use to write these drivers and oversee their development, although
that was a long time ago. If you have specific questions, feel free to ask
them here. At least one of us has touched each of the supported Classic
drivers in Agilent's list. We are listening and I'm sure the questions
will jog our memories.

To start with, find an instrument in the "Classic" list that is close to the
instrument that you want to develop a driver for. This will give you the
basic driver structure. There are two parts to the driver - the component
section and the panel section. The component section defines all the
components (or variables) and the actions associated with them when they are
"set" (changed by the user) or when doing a "get" (receiving from the
instrument). The panel section defines the display look and feel. If you
have components that are linked together or commands that are chained
together in one big command, there are "tricks" that can be used to get them
working the way you like.

As far as building a Classic driver versus just doing Direct I/O ... If
there are only a few things that you wish to do, doing direct I/O is a lot
faster - you can write many Direct I/O boxes in a day. A big command or
SCPI subsection may take a day to write in a Classic driver by the time you
do the component section and panel section and sort out all the
interactions. On the other hand, the Classic driver will give you
flexibility, especially if the end user may not fully understand the part in
the manual that says "you must send the commands in this order." That is,
the Classic driver can have all the details of the manual built into it.

If you have any further questions, just ask - either on the reflector, or to
me individually.

Les Hammer
Complete Test
PO Box 6
Loveland, CO 80539
970-663-0006
Les.Hammer@CompleteTest.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@it.lists.it.agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Like • Show 0 Likes0
Actions
VRFuser Sep 16, 2002 9:11 PM
Mark Correct
Correct Answer
Refer to the bottom of the following url fo rthe driver writing archive:
http://ftp.agilent.com/pub/mpusup/pc/binfiles/vee/index.html

-----Original Message-----
From: Les Hammer [mailto:les_hammer@att.net]
Sent: Tuesday, September 17, 2002 12:07 PM
To: VEE vrf
Subject: [vrf] Re: Instrument Panel driver development ???

> anyone knows where it is possible to find some documentation about
> instrument panel driver development ?

I'll see if I can dig up some documentation. I might have some buried in a
box some where.
Jay and I use to write these drivers and oversee their development, although
that was a long time ago. If you have specific questions, feel free to ask
them here. At least one of us has touched each of the supported Classic
drivers in Agilent's list. We are listening and I'm sure the questions
will jog our memories.

To start with, find an instrument in the "Classic" list that is close to the
instrument that you want to develop a driver for. This will give you the
basic driver structure. There are two parts to the driver - the component
section and the panel section. The component section defines all the
components (or variables) and the actions associated with them when they are
"set" (changed by the user) or when doing a "get" (receiving from the
instrument). The panel section defines the display look and feel. If you
have components that are linked together or commands that are chained
together in one big command, there are "tricks" that can be used to get them
working the way you like.

As far as building a Classic driver versus just doing Direct I/O ... If
there are only a few things that you wish to do, doing direct I/O is a lot
faster - you can write many Direct I/O boxes in a day. A big command or
SCPI subsection may take a day to write in a Classic driver by the time you
do the component section and panel section and sort out all the
interactions. On the other hand, the Classic driver will give you
flexibility, especially if the end user may not fully understand the part in
the manual that says "you must send the commands in this order." That is,
the Classic driver can have all the details of the manual built into it.

If you have any further questions, just ask - either on the reflector, or to
me individually.

Les Hammer
Complete Test
PO Box 6
Loveland, CO 80539
970-663-0006
Les.Hammer@CompleteTest.com

---
You are currently subscribed to vrf as: dave_finniff@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@it.lists.it.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@it.lists.it.agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Like • Show 0 Likes0
Actions

vrf Instrument Panel driver development ???

Outcomes

Related Content

Recommended Content