AnsweredAssumed Answered

vrf Controlling App Window location

Question asked by VRFuser on Oct 26, 2007
We had a similar situation 2 years ago with mixed cards. We actually had an issue with the same code working differently and the only difference was the cards. We replaced all our cards with the same and the problem did not happen again. I did go back and reinstall the old card and the problem came back so I know it was the card.

 

We currently use the NI usb  gpib card.

 

Eddie Rickey

Engineering Technician

HVAL

Storage Products Advanced Characterization Engineering

Texas Instruments, Inc.

  _____  

From: ksalter [mailto:ksalter@kdsengineering.com]
Sent: Sunday, October 21, 2007 2:50 PM
To: VRF
Subject: RE: [vrf] 1 Program, 2 different GPIB cards

 

Bill,

I’m not sure which version of vee or the io libraries you’re using, but since we’ve switched over to io lib 14.2 and vee 8.0 we’ve switched to just using the visa alias in the vee application and handling all the physical layer i/o setup in the io lib manager (connection expert).  Its great.  On one station I have the spectrum analyzer on tcp/ip and the other uses gpib bus 14.  they use the same vee application.  Both call on the same visa alias, sa1.  but they have the alias assigned to different io’s on each machine.  

Kevin

 

 

  _____  

From: William.Drago@L-3com.com [mailto:William.Drago@L-3com.com]
Sent: Thursday, October 18, 2007 7:10 AM
To: VRF
Subject: RE: [vrf] 1 Program, 2 different GPIB cards

 

Hi Michael,

 

Somebody else wrote this program, I'm just trying to help him find a quick fix for getting it to work with both cards.

 

In my own software I wrote drivers for every piece of test equipment we use here, and I pass the address along with any other req'd parameters, so it's not a problem (There's only one instrument in my vee.io info and all my drivers talk to it just using different addresses.)

 

In his case all the instrument I/O is hard coded right in his program, and vee.io info is saved with the program. I showed him how to edit the .VEE file using search and replace to change the addresses. I was hoping there was some other "backdoor" method.

 

I suppose the easiest thing to do is to have two vee.io files, one for each GPIB card.

 

Thanks,

Bill

 

 

 -----Original Message-----
From: Strutt, Michael [mailto:MStrutt@tycoelectronics.com]
Sent: Thursday, October 18, 2007 4:24 AM
To: Drago, William @NARDAEAST; VRF
Subject: RE: [vrf] 1 Program, 2 different GPIB cards

Hi Bill

I guess from your mail that you are not using the VEE.io file to manage your instrument addressing?

This becomes a pain when you have more than 1 instrument of any type fitted in a system.

 

The method we use here is to create a loader file "programme_name".ini which can be different on each system.

This file loads the libraries and bus address used by each test system. That way the .ini file holds the specific system information

the main programme is the same on all test systems. so you can hold an address list in each .ini file e.g.

scope=702 or scope=1402

Or you can hold just a base address variable, e.g. gpib card = 14 or gpib card = 7 then you can set the address pin

of the instrument by gpib+address = local address.

 

Hope this makes sense good luck Mike

 


  _____  


From: William.Drago@L-3com.com [mailto:William.Drago@L-3com.com]
Sent: 17 October 2007 23:37
To: VRF
Subject: [vrf] 1 Program, 2 different GPIB cards

All,

 

When the same software is going run on a number of computers, some with Agilent GPIB cards and some with Nat'l GPIB cards, I create a version for each GPIB card. (I use search and replace to replace 7 with 14 in the appropriate places)

 

Is there a better way? Can VEE auto detect the GPIB card and then act accordingly or am I stuck forever maintaining 2 versions of the same software?

 

Bill

 


---
You are currently subscribed to vrf as: MStrutt@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".


---
You are currently subscribed to vrf as: KSalter@kdsengineering.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: e-rickey@ti.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