AnsweredAssumed Answered

vrf developing with libraries

Question asked by paul.fowler on May 22, 2003

Like • Show 0 Likes0
Comment • 3

Try using the Import Library object in the MAIN of LIB1.vee to load
LIB1.vee as a library named INST1. You will then have copies of all the UFs
available correctly named. When you make a change hit "save" followed by
"start" in MAIN to re-load the altered version.

Have briefly tested this and it seems to work OK.

Paul F

                    Richard Kleinhenz       To: "VEE vrf" <vrf@it.lists.it.agilent.com>
                    <scubaman@us.ibm.com>   cc:
                              21/05/03      Subject: [vrf] developing with libraries
          13:19

          Please respond to Richard
          Kleinhenz

          Stationery name:-Untitled-

I need some advice on working with libraries. I would like to have
instrument dependent subroutines in separate libraries, to be loaded during
runtime. If a specific instrument subroutine SUB1 needs to call another
instrument subroutine SUB2 in the same library INST1, I am running into
some gotchas during development. For the call to work in the main program,
the call needs to be to INST1.SUB2. But now, I can't play around in LIB1
directly, debugging, because if I call SUB1 in a test MAIN mdule, it calls
INST1.SUB2 which does not work. It needs to call SUB2 directly. So I
started making a SUB1local version also, for debugging. But this quickly
gets out of hand, having each routine twice.

Maybe I am missing some basic feature. How do others develop instrument
driver libraries?
--
Regards,
Rich
===================
Richard Kleinhenz
Wafer Engineering
845-892-2617
scubaman@us.ibm.com
===================

---
You are currently subscribed to vrf as: Paul.Fowler@raytheon.co.uk
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".

No one else has this question

Outcomes

scubaman May 20, 2003 5:19 PM

I need some advice on working with libraries. I would like to have
instrument dependent subroutines in separate libraries, to be loaded during
runtime. If a specific instrument subroutine SUB1 needs to call another
instrument subroutine SUB2 in the same library INST1, I am running into
some gotchas during development. For the call to work in the main program,
the call needs to be to INST1.SUB2. But now, I can't play around in LIB1
directly, debugging, because if I call SUB1 in a test MAIN mdule, it calls
INST1.SUB2 which does not work. It needs to call SUB2 directly. So I
started making a SUB1local version also, for debugging. But this quickly
gets out of hand, having each routine twice.

Maybe I am missing some basic feature. How do others develop instrument
driver libraries?
--
Regards,
Rich
===================
Richard Kleinhenz
Wafer Engineering
845-892-2617
scubaman@us.ibm.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".

Actions

reiner.schlieker May 20, 2003 6:49 PM

Rich,

This can be frustrating at times. What I do most often is make sure each
function has a unique name, not just in the local library, but across all
libraries. I do this by prefixing the name of the function in every library
with a common descriptor, eg DMM_Initialize, DMM_Set_Volts, etc. Now,
whenever I CALL a function, I strip of the dot notation (eg
"import_name.DMM_Initialize" is CALLed as "DMM_Initialize") As long as your
functions have unique names, then there is no problem. However, you must
always remember to strip off the imported library name in every CALL that
you make.

You can also load all of the libraries into a common test program and test
them. Have the individual libraries open at the same time, and make changes
(and save them) in the libraries, re-load them into the test program, and
try the changes.

Hope it helps (and that I've understood your problem),

Reiner

I need some advice on working with libraries. I would like to have
instrument dependent subroutines in separate libraries, to be loaded during
runtime. If a specific instrument subroutine SUB1 needs to call another
instrument subroutine SUB2 in the same library INST1, I am running into
some gotchas during development. For the call to work in the main program,
the call needs to be to INST1.SUB2. But now, I can't play around in LIB1
directly, debugging, because if I call SUB1 in a test MAIN mdule, it calls
INST1.SUB2 which does not work. It needs to call SUB2 directly. So I
started making a SUB1local version also, for debugging. But this quickly
gets out of hand, having each routine twice.

Maybe I am missing some basic feature. How do others develop instrument
driver libraries?
--
Regards,
Rich
===================
Richard Kleinhenz
Wafer Engineering
845-892-2617
scubaman@us.ibm.com
===================

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

Actions

VRFuser May 20, 2003 7:43 PM

Rich,
     If you have a look on my website under VEE Object Libraries you'll see
I have tried to address this by viewing the libraries as classes and then
making instances e.g. DMM22, DMM23 etc. where you may use the suffix to
denote the hardware address.

There are some notes when using these e.g. you cannot have a library and an
instrument name the same ( shame ) and so I prefix an 'i' e.g. a device
called GPIB_Dev would be set up in the instrument manager as iGPIB_Dev. In
the calling program you still need to have iGPIB_Dev set up ( which will
cover all GPIB instruments ) and also ones for iDMM22, iDMM23 etc. - this
allows VEE to import the 'class' without getting a warning that the device
is not configured.

It may sound a bit of an overhead but I ( along with some others on this
forum ) have used this very successfully for some time.

Let me know if you want to look at this - the examples there do not have
all of my latest thoughts on the subject.

Regards,

Mike Watts

Message text written by Richard Kleinhenz
>
I need some advice on working with libraries. I would like to have
instrument dependent subroutines in separate libraries, to be loaded during
runtime. If a specific instrument subroutine SUB1 needs to call another
instrument subroutine SUB2 in the same library INST1, I am running into
some gotchas during development. For the call to work in the main program,
the call needs to be to INST1.SUB2. But now, I can't play around in LIB1
directly, debugging, because if I call SUB1 in a test MAIN mdule, it calls
INST1.SUB2 which does not work. It needs to call SUB2 directly. So I
started making a SUB1local version also, for debugging. But this quickly
gets out of hand, having each routine twice.

Maybe I am missing some basic feature. How do others develop instrument
driver libraries?
--
Regards,
Rich
===================
Richard Kleinhenz
Wafer Engineering
845-892-2617
scubaman@us.ibm.com
===================<

_______________________________________________________________________

Michael Watts, Consultant                                 PO Box 92
on the web: www.PreciselySo.Co.UK                      Exeter,Devon
e-mail: MJWC@PreciselySo.Co.UK                              England
tel: +44 7714 339 729                                       EX4 2YY
_______________________________________________________________________

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

Actions

3 Replies

scubaman May 20, 2003 5:19 PM
Mark Correct
Correct Answer

I need some advice on working with libraries. I would like to have
instrument dependent subroutines in separate libraries, to be loaded during
runtime. If a specific instrument subroutine SUB1 needs to call another
instrument subroutine SUB2 in the same library INST1, I am running into
some gotchas during development. For the call to work in the main program,
the call needs to be to INST1.SUB2. But now, I can't play around in LIB1
directly, debugging, because if I call SUB1 in a test MAIN mdule, it calls
INST1.SUB2 which does not work. It needs to call SUB2 directly. So I
started making a SUB1local version also, for debugging. But this quickly
gets out of hand, having each routine twice.

Maybe I am missing some basic feature. How do others develop instrument
driver libraries?
--
Regards,
Rich
===================
Richard Kleinhenz
Wafer Engineering
845-892-2617
scubaman@us.ibm.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
reiner.schlieker May 20, 2003 6:49 PM
Mark Correct
Correct Answer
Rich,

This can be frustrating at times. What I do most often is make sure each
function has a unique name, not just in the local library, but across all
libraries. I do this by prefixing the name of the function in every library
with a common descriptor, eg DMM_Initialize, DMM_Set_Volts, etc. Now,
whenever I CALL a function, I strip of the dot notation (eg
"import_name.DMM_Initialize" is CALLed as "DMM_Initialize") As long as your
functions have unique names, then there is no problem. However, you must
always remember to strip off the imported library name in every CALL that
you make.

You can also load all of the libraries into a common test program and test
them. Have the individual libraries open at the same time, and make changes
(and save them) in the libraries, re-load them into the test program, and
try the changes.

Hope it helps (and that I've understood your problem),

Reiner

I need some advice on working with libraries. I would like to have
instrument dependent subroutines in separate libraries, to be loaded during
runtime. If a specific instrument subroutine SUB1 needs to call another
instrument subroutine SUB2 in the same library INST1, I am running into
some gotchas during development. For the call to work in the main program,
the call needs to be to INST1.SUB2. But now, I can't play around in LIB1
directly, debugging, because if I call SUB1 in a test MAIN mdule, it calls
INST1.SUB2 which does not work. It needs to call SUB2 directly. So I
started making a SUB1local version also, for debugging. But this quickly
gets out of hand, having each routine twice.

Maybe I am missing some basic feature. How do others develop instrument
driver libraries?
--
Regards,
Rich
===================
Richard Kleinhenz
Wafer Engineering
845-892-2617
scubaman@us.ibm.com
===================

---
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
VRFuser May 20, 2003 7:43 PM
Mark Correct
Correct Answer
Rich,
     If you have a look on my website under VEE Object Libraries you'll see
I have tried to address this by viewing the libraries as classes and then
making instances e.g. DMM22, DMM23 etc. where you may use the suffix to
denote the hardware address.

There are some notes when using these e.g. you cannot have a library and an
instrument name the same ( shame ) and so I prefix an 'i' e.g. a device
called GPIB_Dev would be set up in the instrument manager as iGPIB_Dev. In
the calling program you still need to have iGPIB_Dev set up ( which will
cover all GPIB instruments ) and also ones for iDMM22, iDMM23 etc. - this
allows VEE to import the 'class' without getting a warning that the device
is not configured.

It may sound a bit of an overhead but I ( along with some others on this
forum ) have used this very successfully for some time.

Let me know if you want to look at this - the examples there do not have
all of my latest thoughts on the subject.

Regards,

Mike Watts

Message text written by Richard Kleinhenz
>
I need some advice on working with libraries. I would like to have
instrument dependent subroutines in separate libraries, to be loaded during
runtime. If a specific instrument subroutine SUB1 needs to call another
instrument subroutine SUB2 in the same library INST1, I am running into
some gotchas during development. For the call to work in the main program,
the call needs to be to INST1.SUB2. But now, I can't play around in LIB1
directly, debugging, because if I call SUB1 in a test MAIN mdule, it calls
INST1.SUB2 which does not work. It needs to call SUB2 directly. So I
started making a SUB1local version also, for debugging. But this quickly
gets out of hand, having each routine twice.

Maybe I am missing some basic feature. How do others develop instrument
driver libraries?
--
Regards,
Rich
===================
Richard Kleinhenz
Wafer Engineering
845-892-2617
scubaman@us.ibm.com
===================<

_______________________________________________________________________

Michael Watts, Consultant                                 PO Box 92
on the web: www.PreciselySo.Co.UK                      Exeter,Devon
e-mail: MJWC@PreciselySo.Co.UK                              England
tel: +44 7714 339 729                                       EX4 2YY
_______________________________________________________________________

---
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 developing with libraries

Outcomes

Related Content

Recommended Content