AnsweredAssumed Answered

vrf Instruments in callable Vee

Question asked by VRFuser on May 13, 2008
Callable Vee has a program named veesm that acts as a sort of surrogate server that dispatches the rpc calls to Vee handler processes.  If you start veesm using the –veeio option, you can select whatever vee.io file you have access to. 

 

From: David Watling [mailto:watling@IceraSemi.com]
Sent: Tuesday, May 13, 2008 8:20 AM
To: PDL-LISTS,VRF (A-Lists,unix1)
Subject: FW: [vrf] Instruments in callable Vee

 

Interesting – your thinking matches my own.  So I created a vee.io file, and put it in:

C:Documents and SettingswatlingLocal SettingsApplication DataAgilentAgilent VEE Provee.io

And

C:Documents and SettingswatlingLocal SettingsApplication DataAgilentAgilent VEE RunTimevee.io

(just to be sure)

 

Got the same error message!

I wonder if there is a third location for …callableVeevee.io ?

 

Dave

 

  _____  

From: Street, Andy M [mailto:andy.street@tycoelectronics.com]
Sent: 13 May 2008 15:05
To: David Watling
Subject: RE: [vrf] Instruments in callable Vee

 

Hi Dave,

 

I am pretty sure that the information about the instrument is going to be in the external vee.io file that is associated with your logon.  Normally when a UF is imported into another VEE program, the IO calls inherit the IO config in the main program, but in the case of Callable VEE, the IO information is going to reside in the vee.io file.  There should be something about this in the Callable VEE Help File.  At least this is how life was in VEE 7.5 days - I have never checked it out in VEE 8+

 

Try tweaking on your vee.io file and see what happens...

 

Hope this helps

 

Andy

 

  _____  

From: David Watling [mailto:watling@IceraSemi.com]
Sent: Tuesday, May 13, 2008 9:56 AM
To: VRF
Subject: [vrf] Instruments in callable Vee

Hi,

I am trying to use callable Vee for the first time.

I have tried importing userfunctions into callable vee (from Excel VBA), and all is fine unless a userfunction contains an instrument call.  I just had one ‘Direct IO’ instrument call in my library, but this caused the import to fail with the message ‘Invalid device encountered, Prerun failed on User Function, etc…’.

 

Is this because the vee.io needs to be in a certain place?  Is there something I need to know about instruments within callable Vee?

 

Regards

 

David Watling

 

--

  _____  

This e-mail (including any attachments) is intended only for the recipient(s) named above. It may contain confidential or privileged information and should not be read, copied or otherwise used by any other person. If you are not a named recipient, please contact the sender by telephone (+44-1454-284800) and destroy the original message. Any statement and/or opinion not related to this company's business and expressed in this message is that of the author and does not necessarily reflect those of Icera. This company does not take any responsibility for the views of the author in any matter not related to the company's objective.

  _____  


---
You are currently subscribed to vrf as: andy.street@tycoelectronics.com
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
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".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".

--

  _____  

This e-mail (including any attachments) is intended only for the recipient(s) named above. It may contain confidential or privileged information and should not be read, copied or otherwise used by any other person. If you are not a named recipient, please contact the sender by telephone (+44-1454-284800) and destroy the original message. Any statement and/or opinion not related to this company's business and expressed in this message is that of the author and does not necessarily reflect those of Icera. This company does not take any responsibility for the views of the author in any matter not related to the company's objective.

  _____  


---
You are currently subscribed to vrf as: john_dumais2@agilent.com
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
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".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".


---
You are currently subscribed to vrf as: ming_meng@agilent.com
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
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".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".  

Outcomes