LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

VISA resource name constant

Hello all,
I'm working with LabVIEW 6.0.2 on Windows 2000 service patch 2. I have
two machines - one a development workstation, the other a portable.
They are not the same machine, but both are fast pentiums running the
same OS and LabVIEW version as mentioned above.
When I insert a "VISA resource name constant" into the wiring diagram
on my development workstation, I can use the manipulation cursor (the
hand) to select COM1, COM2, or LPT1. If I do the same thing on the
portable computer, I get different choices - the visa resource names
ASRL1::INSTR, ASRL2::INSTR, and ASRL10::INSTR. Such constants created
on one machine and then exported to the other create errors, although
they work on the machine in which they were created.
Why is
this happening? Right-clicking on the constants, they have the
same properties; under "Select VISA Class" and then "I/O Session",
"Instr" is checked. Nothing else is checked except "Size to Text".
These properties are the same on each computer.

---------------------------
Dan Greenspan
Mail Stop 14-707M
Johns Hopkins University
Applied Physics Laboratory
11100 Johns Hopkins Road
Laurel, MD 20723-6099

240-228-7490
daniel.greenspan@jhuapl.edu
---------------------------
0 Kudos
Message 1 of 3
(2,782 Views)
Hello,

"ASRL1::INSTR" is the resource name and "COM1" is the alias of one and the same resource.

Probably no aliases are defined on your portable computer. Launch the Measurement & Automation Explorer and choose menu Tools->NI VISA->Alias Editor (I hope thats the right translation, because I use the german version). Here you can define an alias for every VISA-resource. These alias-names will then shown on your "VISA resource name constant".
Christian

Test Engineering
digades GmbH
www.digades.com
0 Kudos
Message 2 of 3
(2,782 Views)
Hi,

My guess is, on the development workstation, some aliases have been setup for those Visa Resources, eg COM1 is an alias for ASRL1::INSTR.
If you look in Measurement and Automation Explorer under Devices, you can tell if this is the cases.

Regards
Ray Farmer
Regards
Ray Farmer
0 Kudos
Message 3 of 3
(2,782 Views)