MAX and VISA Resources

I have MAX version 4.6.1 installed from NI-VISA 4.6.2. Recently I upgraded from LabView version 8.5 to 8.6 after which I have lost all previously used VISA resources. When I launch MAX it indicates there aren't any VISA resources found. I have tried adding VISA resource and I am able to validate the connection and verify connectivity using the VISA test panel. However, after I refresh VISA resources in MAX it loses the newly added (and saved) VISA resource. MAX returns the following error code:
0xBFFF0011 (VI_ERROR_RSRC_NFOUND)
Additionally, I have tried the following without success:
Removing MAX and reinstalling using NI-VISA without success.
Importing a colleagues configuration data.
Has anyone experienced this issue and know how to fix it?

Hello, did you reinstall drivers after upgrading LabVIEW? You will need to run the VISA installer again. As well as any other drivers you want to use in LabVIEW
National Instruments

Similar Messages

Old visa open, error code 1073807343, using VISA with a GPIB device, and VISA resource names

Hi everyone,
I'm trying to get a SRS model SR720 LCR meter (manual on this page) working with LabView, connecting it to my PC with an Agilent 82357A GPIB/USB interface (manual on this page). I'm running MAX version 14.0, and NI-VISA version 14.0. I'm running LabView version 13.0f2, 32 bit.
I followed the directions on this page, and I'm pretty confident I can communicate with my LCR meter, because I can go to NI MAX->GPIB0::17::INSTR under "devices and interfaces", then go to the VISA test panel, go to the I/O tab, and I can enter a few commands from the SR720 manual, like changing the frequency, and I see the light on the LCR meter change to what I just told it to do. Here is a picture, just to illustrate it:
Also, if I do the *IDN? command, it returns "
9: Write Operation (*IDN?)
Return Count: 5 bytes
10: Read Operation
Return Count: 41 bytes
StanfordResearchSystems,SR720,08087,1.03\n
So, that's good too. I also made the alias of this device "MyLCRmeter", but that shouldn't matter for now.
Now I'm trying to get it to work in a more usable way. The SR7xx drivers that LabView found for me came with a couple sample programs, one called "Getting Started.vi". I tried to just simply see if it worked, changing the "instrument descriptor" field to "GPIB0::17::INSTR", since that's the one that seemed to be the right device in MAX. Here is a picture of the front panel of "Getting Started.vi":
Trying to run it like this gave me this error (code -1073807343):
Old VISA Open in SR715/720 Initialize.vi->SR715/720 Getting Started.vi
Doing a bit of searching on these forums, I found these few threads (1 2 3), which seem to tell me that, since this program was written, the way you open VISA has changed. In the 2nd of those links, one guy said:
You just have to replace the Old VISA Open function with the VISA Open that is on the Instrument I/O>VISA>VISA Advanced palette. When you do that, the wire to the string that was used for the resource name will be broken. Delete the string and make the actual VISA Resource Name visible on the front panel. Wire the VISA Resource Name control to the connector pane where the string control was (upper left connection).
So, I went into the sub-VI Initialize.vi, and did that. Here is a picture of what the front panel and block diagram of the sub-VI Initialize2.vi (I changed the name in case I screwed things up, but I'm pretty sure the new one is the one being called by Getting Started.vi) looked like before I changed anything (you can see the Old VISA Open):
and here it is after replacing that with the regular VISA Open, deleting the instrument descriptor string and replacing it with a VISA resource, and connecting that to the VISA Open:
However, as you can see in the image above, and it seems like someone else had this problem in the 2nd thread linked above, I don't see my device listed in the drop-down menu (even if I refresh), only "LPT1" (I don't even know what that is):
No, I wasnt able to select the visa resource from the pull down menu. somehow it seems disabled or something.
If I just enter the VISA resource name from MAX manually, GPIB0::17::INSTR, and save and try running that, I get the error(code -1073807346):
VISA Open in SR715/720 Initialize2.vi->SR715/720 Getting Started.vi
So I'm not sure where to go from there, or why it's not in the drop down menu to begin with. I'm sorry if I've missed something but I've searched about as far as I can go. If I had to guess, maybe one thing could be that in MAX, under Tools->NI-VISA->VISA Options->My System->Conflict manager, I have both Agilent VISA and NI VISA enabled; I know sometimes problems arise from conflicts between different software fighting over the same hardware. Is this okay, or do I need to change it?
Thank you and please let me know if there is any other code/screenshots I could provide that could help!

Hi, I did indeed enable NiVisaTulip.dll under MAX->Tools->NI-VISA->VISA Options->My system->Passports->List of passports. Sorry, I should have mentioned that explicitly.
By install as primary, do you just mean as it is here, where it is selected as the "Preferred VISA"?
Or somewhere else? I installed NI-VISA first I believe, and then the Agilent one, and during the installation of the Agilent one, I'm pretty sure I made it not the primary. Here's what I have in the Agilent (it's called Keysight now) Connection Expert software:
I also have this under the "Keysight 488 options" tab:
Should that be checked? I don't actually know the role of VISA vs 488 here...
What could I try?
Thank you!

MAX and VISA displays extra COM port

From the Windows 2000 -> Control Panel -> System, it displayed that there are the following ports:
COM1 - Serial port
LPT1 - Parallel port
COM2 - USB-to-serial port
However, when checked with MAX & VISA, it displays an extra port:
ASRL1:INSTR (COM1)
ASRL2:INSTR (COM2)
ASRL3:INSTR (COM3)
ASRL10:INSTR (LPT1)
I don't know where does the COM3 comes from, or how to eliminate it. I have tried to take out the reference to COM3 on the visaconf.ini , but it reappears.
At the same time, I am having Labview crashes problem (access violation) after I communicate with the instrument connected via COM2 (Labview.exe crashes on a 2nd run of the same script, which needs restarting of computer before it will work again, for one r
un and crash again on the 2nd run). Does this problem has anything to do with the appearance of COM3?
Please help!
Thanks
Vanessa

Vanessa:
I believe COM3 is still in your registry under HKLM\HARDWARE\DEVICEMAP\SERIALCOMM. It is possible that it existed at one time previously and the system never deleted it (although this seems odd to me). You should be able to run regedit, find this key, and delete the COM3 string item in the right hand view.
Even though viFindRsrc is returning COM3, I do not believe that viOpen will succeed - it should return an error for that port since you say it does not really exist. In fact, MAX should show some kind of exclamation point or X through the icon. Does it do this?
Regardless of the MAX behavior, this should not affect your LabVIEW program in any way. I have no idea what is causing your crash but it is probably not related to this phanto
m COM3. If you think the crash is in VISA, I suggest you use NI Spy and enable Log to File with Fail Safe Logging selected. Then after the crash you can load the .spy file and see if any VISA call did not return.
Dan Mondrik
Senior Software Engineer, NI-VISA
National Instruments

No VISA Resources in Labview but all present in MAX

Hi,
I am unable to find any VISA resources from LabVIEW, however, all NI hardware is available and working in MAX. I have just installed a PCI-8433/2 as well as a NI PCI-8512 CAN/HS Card. As part of the installation I believe MAX was upgraded to version 4.6.2. I will attach the max configuration report for those who are interested. I am working with LabView 8.2. I also uninstalled an agilent GPIB card and as a result the NI-GPIB card is the sole controller and is GPIB0... instead of the agilent card.
I have had a similar problem before that was a result of a corrupted database, but I was unable to find this problem on the forums this time and I am not getting any errors. Just an empty VISA Resource control.
Any suggestions would be greatly appreciated.
Nate
MAX Configuration Report
12/27/2010 1:35:05 PM
MAX Summary
My System
Data Neighborhood
CAN Channels
NI-DAQmx Tasks
V1P1V2P2
V3P3
Devices and Interfaces
GPIB0 (PCI-GPIB)
Instrument0
Instrument1
Instrument2
Instrument3
Instrument4
Instrument5
Miscellaneous VISA Resources
GPIB0::INTFC
GPIB0::16::INSTR
GPIB0::2::INSTR
GPIB0::22::INSTR
GPIB0::7::INSTR
GPIB0::10::INSTR
GPIB0::27::INSTR
GPIB0::3::INSTR
Network Devices
NI-DAQmx Devices
NI USB-9481: "Dev2"
NI USB-9481: "Dev1"
NI-XNET Devices
NI PCI-8512 CAN/HS
CAN1
CAN2
PCI-8433/2
Port1
Port2
PXI System (Unidentified)
Serial & Parallel
COM1
COM6
COM9
LPT1
Scales
Software
IVI Compliance Package 3.3
LabVIEW 8.2
LabVIEW Run-Time 7.1
LabVIEW Run-Time 8.0.1
LabVIEW Run-Time 8.2.1
LabVIEW Run-Time 8.5.1
LabVIEW Run-Time 8.6.1
LabWindows/CVI Run-Time 9.0
Measurement & Automation Explorer 4.6.2
Measurement Studio for VS2005
DotNET
Common
NI LabVIEW SignalExpress 3.0
NI Spy 2.7.1
NI-488.2 2.46
NI-CAN 2.7
NI-DAQmx 8.7.2
NI-PAL 2.5.3
NI-Serial 3.6
NI-USI 1.0.2
NI-VISA 4.6.2
NiVisaServer.exe
NIvisaic.exe
NI-VISA Runtime 4.6.2
NI-XNET 1.1
IVI Drivers
Advanced
Instrument Driver Software Modules
Simulation Driver Software Modules
Simulation Driver Sessions
Driver Sessions
Logical Names
-Nate
Solved!
Go to Solution.

Now that IS odd.
Can you show a couple screen shots from MAX?
First expand the software tab and post a png of the screenshot (I'm not yet convinced you do not have SOME driver issue)
Next select MAX>TOOLS>NI VISA>VISA Options- Wait for the new screen then expand Mysystem General settings and select Aliases.
You could also try "Clear all aliases" from there and reboot.
Jeff

Functional difference between VISA resource name ASRL1::INSTR and COM1

Config: LabVIEW 6.02, VISA 2.6.0
I have used a text constant for "VISA Configure Serial Port.vi" for years, and just now I have run into problems.
With my application, a text constant of ASRL2::INSTR would properly open the port, but it would not send any data, but using COM2 worked.
What is the difference?

MAX sets up serial port aliases automatically when possible. Let me try to explain.
If the alias "COMx" was not previously configured in NI-VISA, and you have a serial port really named "COMx", and that VISA resource string does not have any other user-configured alias, then MAX will bind that alias to that port, regardless of what the full VISA resource string is. That part actually makes sense and shouldn't confuse anyone. If the alias "COMx" is taken, or the user has manually configured a different alias for the serial port (such as "MyDMM", for example), then MAX does not auto-assign the alias for that port. So far so good.
The confusing part in many cases is how NI-VISA itself assigns the VISA resource string. For COM3, normall
y NI-VISA would assign ASRL3::INSTR, and so on. There is 1 conflict that usually screws everything up. Since NI-VISA on Win32 allows you to open the parallel port by default as ASRL10::INSTR (for extremely historical reasons), the conflict occurs when you really have a COM10. It's not a terrible conflict, but it is confusing. NI-VISA will match every other port that it possibly can, and then just assign a unique resource name (ASRLx::INSTR) for COM10.
I am not sure why in your case NI-VISA didn't match COM3 to ASRL3::INSTR. If you want to do some experimenting, try this. Go into MAX, delete all your VISA aliases, delete LPT1 from the tree, exit MAX, restart MAX, and refresh. See if that cleared it up.
Dan Mondrik
Senior Software Engineer, NI-VISA
National Instruments

How I can saving visa resource name in windows registery and load it again?

I use visa functions in my program for serial communication , I want to save selected resource name in windows registery and next time that i run my program, i want to read it from registery and assign it to my visa resource name control.
example:         My visa resource name control value = COM2
                        I close my program with this value (how i can easily save COM2 to windows registry key ?)
                        I open my program again (how i can load COM2 in my resource name control from registry Key?)
                        How i can access to visa resource name list? example: COM1     COM2      LPT1     COM56    COM255
Thanks.
Solved!
Go to Solution.

I guess I don't understand your problem. All you have to do is ready the key containing the desired resource name and wire the resulting value to the appropriate terminal on the open VI. That's as hard as it gets...
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Visa resource control loses value set during config and saved to step properties in TestStand

I'm using a Visa resource control to set the instrument handle in my VI (edit sub-step) and it gets saved into a step property of a custom step I've built at edit time. At run time the control value is intermittantly changed to "temp 0" value and I don't understand why. I have LabVIEW 7.1, TestStand 3.0

Hi kphite,
Are you using the Refnum to Session.vi and Session to Refnum.vi?
You would use the Refnum to Session.vi to convert your Visa session value to a U32. Then you can pass this back to TestStand.
Going back to LabView you use the Session to Refnum.vi to convert a U32 back to the Visa session.
Regards
Ray Farmer
Regards
Ray Farmer

Using VISA Resource control with Windows 7 64-bit

Hi.
My company recently upgraded our laptops, and I'm now working on Windows 7 64-bit rather than Windows XP 32-bit. I reinstalled LabVIEW 2009 Base Package, trusting that the Windows 7 64-bit OS would be able to handle LabVIEW 2009 32-bit without problems. But when trying to run our test system, the VISA Resource control doesn't work.
We use it to get a list of the available COM (RS232) ports on the computer. But now the list comes up blank. The only option that comes up in the list, is the text "Refresh". But nothing happens when I press it. Is this a bug in LabVIEW? I've installed the latest patch I found, so now I'm running LabVIEW v9.0f3 (32-bit).
Thanks alot for any and all assistance!
Solved!
Go to Solution.

Sorry for not replying to you earlier. I've been busy on other projects.
I'm not sure what you refer to with MAX, but I'm able to access the com ports using other tools/loggers. So it's not an issue with Windows 7 itself. But it seems logical that the problem would have something to do with running 32-bit drivers on a 64-bit OS. Referring to this list from NI (http://digital.ni.com/public.nsf/allkb/71E9408E6DEAD76C8625760B006B6F98), I'm downloading the 64-bit installer now.
But if I understand it correctly, you cannot run applications from a 64-bit Application Builder on a 32-bit OS. So basically you need the Application Builder installed on both a 32-bit and 64-bit OS to have all bases covered. But in the FAQ, it's asked if it's possible to have both 32-bit and 64-bit LabVIEW 2009 installed on the same 64-bit OS. Why would this be wanted? If you cannot use the 32-bit Application Builder, and you cannot trust that the 32-bit LabVIEW runs successfully (i.e. driver issues etc.), why would you want to have a 32-bit installation on a 64-bit OS?

How to get GPIB address from VISA resource

Hi All,
Is there a way (CVI API) to get the GPIB address of a GPIB instrument from an alias or a VISA resource name defined in MAX?
Thanks,
Rick.

Thanks mkossmann, I was actually looking for an api that would get the gpib address from the visa resource name defined in MAX which has already scanned in the gpib instruments.
I guess it may not be good that way even if there's such an api because instrument gpib address might get changed and if MAX has not been asked to rescan then the address will be out of sync.

No visa resource found - cRIO

Hello,
I have a cRIO chassis with 3 NI-9862, 1 NI-9205 and 4 NI-9401. But in MAX, there is a warning saying that 'No VISA resources found'. And the CAN, analog and digitla IO cards are missing.
Does anyone know how to resolve this issue?
Thanks.

Hi nyc,
I did reboot the computer after the installation of 488.2 on the host. And the target booted as well automatically after the installation.
Right now, the good news is that the 3 CAN cards are available. But the analog and digital cards are still missing.
Thanks a lot for your help.
Jian

How is VISA resource name & COMport name mapping done?

I want to give names like COM1 etc. on front panel. On diagram how to convert it to VISA resource name, in order to be able to give it as I/P to open VISA session vi.

You may want to use the friendlier names that NI-VISA can give you. I'm attaching a VI that gets those names for you in both LabVIEW 6i and 6.1, since you don't mention your version.
Starting with NI-VISA 3.0 (coming soon), you'll also be able to use names like "COM1" even if MAX is not on the system. However, that is a feature for only Win32 and LabVIEW RT, since those names do not exist on Unix systems. So a VI making use of that feature will not be completely platform independent.
Dan Mondrik
Senior Software Engineer, NI-VISA
National Instruments
Attachments:
FindSerial60.vi ‏29 KB
FindSerial61.vi ‏29 KB

Working with VISA resources in Labview 6

I am having difficulties programming through VISA in Labview 6.0.2. I have installed MAX 3.2, and have configured my two devices going through USB:
1) an Agilent 82357A USBtoGPIB adapter connected with an Agilent 53131A Universal Counter
2) a USBtoRS422 converter registered as serial COM4 connected with a Rainin Peristaltic pump
I can open communication with both devices from within MAX, and send/receive data with no problem.
When I try to program in Labview 6, I cannot communicate with either VISA device, even though I am using VISA instrument IO vi's with the configured VISA resource name from MAX. I'm not sure what I'm doing wrong.
Is there an incompatability between MAX 3.2 and Labview 6.0.2, or have I configured something wrong?
Thank you for the assistance.

Hello,
I think we can defeat the problem with Device 1 fairly quickly. If you have established that you can communicate with the device in MAX, I think we simply have a small programmatic change to make in LabVIEW. I am interested in having you attempt using the VI I have attached, which allows you to specify the bytes you would like to send in an array, and then simply sends the corresponding the string of ascii characters (the characters corresponding to the values in the array); this way we can be sure to send exactly what we would like. The following link has an ascii table in it, which you can use as a reference when putting the values into the array: (where the first byte specified will be the first character in the string)
http://www.ni.com/pdf/manuals/371253a.pdf
Simply change the VISA resource name to reflect your device and give it a try.
As for Device 2, let's try using the same VI (attached) and write a command which the device is known to understand. A simply query would be approprite, where you can write using the attached VI, and then read using another VI which literally only has a VISA Read function in it (and a resource control or constant connected with your resource specified).
One thing to verify before reposting is whether the devices you have use EOS (end of string) and/or EOI (end or identify) termination of GPIB operations. For EOS, a character is sought by the listener to indicate the end of a transmitted string, such as a linefeed or carriage return (or both). EOI termination is defined by the talker asserting the EOI line when the last byte to be transmitted is sent; the listener knows it has received the last byte of that transmission.
Definitely repost; it is likely that we are only few programmatic changes and perhaps a spec check (for the devices) away from dependable communication
Thank you,
JLS
Best,
JLS
Sixclear
Attachments:
WriteByteArray.vi ‏14 KB

What determines which inputs you can select from when you're creating a VISA Resource Name Constant?

Hey, I'm trying to write a labview driver an instrument. I have another instrument which came with labview drivers, and I had hoped that by looking at how they did it, I could write my own for this piece of equipment.
However, the problem is they use the old visa open method. That is, they input a string, "GPIB::6", and it outputs a visa session.
The new Visa open requires that you have an input resource name, and the constants only let me pick from "COM1" and "LPT1", but the GPIB interface card in this computer is in a PCMCIA slot.
What determines what choices you get when you select the value of the constant?
Thanks,
-Dobbs

If you created a VISA Resource Name control, right click on the control and select "Allow Undefined Names".
I haven't programmed directly using VISA on LabVIEW 6 but it apppears that if you select from the drop-down menu, it shows the devices that is defined in MAX. Thus, you should be able to select your GPIB resource name if it has been properly installed.
Nevertheless, it still allows you to override the control by selecting "Allow Undefined Names".
I hope that helps.
Shan Pin Koh

VISA Find function to VISA Resource Name

Hi,
Can anyone help me with this VISA question. I'm kind of new to
instrument control, but have been using LV for quite a long time. I'm
using version 6.02. I discovered the VISA Find Resource function, and
thought it would be really neat to find the instruments that are sitting
on my GPIB bus, and then make sure they are the ones I need for my
testing. The Find resource works great, and returns an array of strings
that are the resource names of the instruments. i.e. GPIB0::5::INSTR.
However, the VISA Open (and all the other VISA functions) require a VISA
resource name control (One of those pruple doohickies with I/O in it).
I haven't been able to figure out how to get that string from the find
function into the VISA resou
rce name control (It looks like a pulldown
on the front panel) so that I can do a *IDN? query to find out what
instrument is actually at this address. I've tried property nodes, even
looked at the invoke node, but to no avail. By the way, the property
node DID have the VISA resource name, but it was read only.
Thanks in advance for any help you folks might be able to provide.
David Dupont
Airvana Inc. http://www.airvananet.com

Hello, David!
I'll do my best to answer your question.
In LabVIEW 6, you have to assign VISA aliases in Measurement and Automation Explorer. You can assign meaningful VISA Aliases to your instruments that you control using VISA in the Devices and Interfaces section in Measurement & Automation Explorer. The aliases can be used in your LabVIEW application development to refer to your instrument.
Once you have assigned aliases in MAX, you simply place a VISA Resource Name Constant in your block diagram. Type the alias name into the resource name constant and wire the name constant to the VISA Resuorce Name input of the VISA Write and VISA Read functions to control your instrument.
I hope this helps.
Mark Ridgley

USBMTC scope VISA resource

This is my first time using a USBMTC instrument.
We purchased a Tektronix TBS1052B.
NI-MAX detected it, and I am able to do a *IDN? query.
I am concerned that the VISA resource that is used now on my development PC will change when the program is eventually installed on another PC.
What is the best solution to this?
Do I do a scan for all USB resources?

nyc wrote:
The target PC is at a contract manufacturer.
In this case you may need to use the System API to find the USBTMC device (and reaname its Alias) during intitialization of your app.
Those USB scopes are nice but the darn users keep moving them around So, its best to be safe and make sure there is one present befor you go off and try to use it.
Like So:
Jeff

MAX and VISA Resources

Similar Messages

Maybe you are looking for