Visa open problem

Hi
I'm using labview2009. I've connected 8593E spectrum analyzer using GPIB interface to my PC.The problem is the instrument address is not coming automatically in the VISA open function input when I connect the instrument to my PC. can anyone sort it out. I've installed Agilent IO libraries suit15.0 and NI device drivers.
Regards
RobinHood

Hi,
If you are using Agilent GPIB then i guess u need passport tulip. Steps to do it i will attached here the manual.I guess it should work.
Attachments:
Steps_for _Installation_of Intru_Labview.pdf ‏712 KB

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!

When trying to work with Agilent 34401A multimeter (serial RS-232 connection), HP34401A Getting Started.vi gives always the message: "Error 1073807369 occurred at Old VISA Open ".

Baud rate and parity are set correctly, RS-232 cable is also connected correctly. My QuickBasic program has no problems to read and write to the Multimeter. It is obviously a software problem: the same error is persistent if I disconnect RS-232 cable.
I downloaded NI-VISA 2.6 for Windows 95/98/NT/ME/2000/XP frorm digital.ni.com and installed it. But it did not help.
Thank you in advance
Best regards
Alexei Soloviev

Hi Steve
I have problems with the 34401A and serial communication. Do you remember
where the error was in the code ?
Thanks
Klaus
wrote in message
news:[email protected]..
> Alexei,
> This may or may not help, I was tasked to do something similar
> recently and found an error in their driver. The GPIB VISA worked
> fine, but when I tried it on serial it played up. There was an errant
> carriage return (or CR/LF I can't remember). GPIB liked one and Serial
> liked the other. It always amuses me that we never have problems with
> Quickbasic!.
> If you want me to dig deeper give me a shout.
>
> Steve Watts
>
> On Thu, 24 Jan 2002 06:16:55 -0800 (PST), "Alexei V. Soloviev"
> wrote:
>
> >When trying
to work with Agilent 34401A multimeter (serial RS-232
> >connection), HP34401A Getting Started.vi gives always the message:
> >"Error 1073807369 occurred at Old VISA Open ".
> >
> >Baud rate and parity are set correctly, RS-232 cable is also connected
> >correctly. My QuickBasic program has no problems to read and write to
> >the Multimeter. It is obviously a software problem: the same error is
> >persistent if I disconnect RS-232 cable.
> > I downloaded NI-VISA 2.6 for Windows 95/98/NT/ME/2000/XP frorm
> > digital.ni.com and installed it. But it did not help.
> >Thank you in advance
> >Best regards
> >Alexei Soloviev
>

Simple VISA Setup Problem

Hi all,
I'm having issues working with VISA in LabVIEW. Previously, I've used Peek/Poke VIs (before they were VISA VIs) that allowed me to read and write directly to registers at a given Windows address. I have a new, custom PCI Express board that uses the same architecture that I've worked with previously only this time I'm trying to access the registers using VISA.
As this is my first time using VISA, I'm having some setup problems. Yesterday I got to a state where logically things should work but I still end up getting an error when I try to run a simple VISA Open command (see attached screenshot).
The initial problem I had was I was not able to acquire a VISA resource that opens a session to my PCIe board...it would simply not show up on the resource list. After reading around I discovered I needed to create a custom VISA driver for my board. Once I did that using the VISA Driver Wizard, the device showed up in my list (as seen in the screenshot). I wrote the simplest of all VIs where I simply open that VISA resource, however, the error seen in the screenshot is produced.
I'm pretty sure this is a simple setup issue, but does anyone know what I'm doing wrong?
Attachments:
Screenshot1.JPG ‏145 KB

Hi bonhomme,
I see you're having some issues using VISA. It sounds like you're new to VISA, so I wanted to pass along some information that we have availble on this software. This link gives good general information about VISA, and the related links are extremely helpful in finding specific issues.
Thank you for attaching your error. This is extremely helpful in debugging since we can actually see the numbers. There is another forumn that talks about these at this link and at this link.
Hope this helps you out!!
Lea D.
Applications Engineering
National Instruments

NI-VISA 5.1.2 exits/closes right after launching it on a Linux CentOS 6.2 PC, also crashes LabVIEW when trying to create VISA ref constant for VISA Open.

After installing LaBVIEW 2011 and NI-VISA 5.1.2 on a CentOS 6.2 PC, I had noticed a problem with trying to use the VISA vi's in LabVIEW, basically it's not working for me, LabVIEW crashed when trying to create a control or constant for the VISA Open vi. Tried to launch the VISA tools, they all start and then close abruptly. NI I/O Trace only shows one line.
I did read though many threads and decided to collect the NI system.log, which is attached. (system.log.gz). I did notice a strange message in here about nivisaserver:
/usr/bin/tail --lines=25 /var/log/messages:
May 22 11:18:48 localhost abrtd: Package 'nivisaserver' isn't signed with proper key
May 22 11:18:48 localhost abrtd: Corrupted or bad dump /var/spool/abrt/ccpp-2012-05-22-11:18:48-3258 (res:2), deleting
Thanks!
Solved!
Go to Solution.
Attachments:
system.log.gz ‏621 KB

MountainMan12 wrote:
After installing LaBVIEW 2011 and NI-VISA 5.1.2 on a CentOS 6.2 PC, I had noticed a problem with trying to use the VISA vi's in LabVIEW, basically it's not working for me, LabVIEW crashed when trying to create a control or constant for the VISA Open vi. Tried to launch the VISA tools, they all start and then close abruptly. NI I/O Trace only shows one line.
I did read though many threads and decided to collect the NI system.log, which is attached. (system.log.gz). I did notice a strange message in here about nivisaserver:
/usr/bin/tail --lines=25 /var/log/messages:
May 22 11:18:48 localhost abrtd: Package 'nivisaserver' isn't signed with proper key
May 22 11:18:48 localhost abrtd: Corrupted or bad dump /var/spool/abrt/ccpp-2012-05-22-11:18:48-3258 (res:2), deleting
Hi MountainMan,
Thanks for attaching the system report log -- I believe I have a solution for you :-) Let's look at a few of the lines:
890: /proc/meminfo:
891: MemTotal: 3894712 kB
1726: /proc/iomem:
1784: 100000000-12dffffff : System RAM
1807: /bin/dmesg:
1820: BIOS-provided physical RAM map: 2576: [nipal] More than 4GB of addressable memory detected.
1838: BIOS-e820: 0000000100000000 - 000000012e000000 (usable)
2576: [nipal] More than 4GB of addressable memory detected.
2577: [nipal] This configuration is not supported. Check the release notes for more information.
Starting at the bottom at lines 2576..2577, dmesg had more than just the NI-VISA server signing notification. At system boot, the NI kernel modules refused to load because they detected more than 4 GB of addressable memory. But, if you look towards the top at lines 890..891, meminfo says you have less than 4 GB of system memory, which makes it seem like the NI modules don't know what they're talking about. However, if you look at the report from iomem a little further down on lines 1726..1784, system RAM has been re-mapped above the 4 GB boundary. While your system doesn't have more than 4 GB of RAM, some of its memory has addresses above 4 GB, which the NI modules cannot use and so they refuse to load. How did that happen? Your system BIOS provided a physical RAM map with usable addresses above the threshold (line 1838).
The fix here is simple -- you need to tell the kernel to reserve addresses above 4 GB [1] so that it won't remap the RAM to higher memory. Once all of the RAM has addresses below the 4 GB threshold, the modules should load and VISA/LabVIEW/et al should stop misbehaving.
It seems to me that LabVIEW is not handling this situation very gracefully, and maybe you can work with Kira to file a bug report.
[1] Re: Successful SUSE linux and DAQmx install; nilsdev and other utilities missing.
http://forums.ni.com/t5/Multifunction-DAQ/Successful-SUSE-linux-and-DAQmx-install-nilsdev-and-other/...
Joe Friedchicken
NI VirtualBench Application Software
Get with your fellow hardware users :: [ NI's VirtualBench User Group ]
Get with your fellow OS users :: [ NI's Linux User Group ] [ NI's OS X User Group ]
Get with your fellow developers :: [ NI's DAQmx Base User Group ] [ NI's DDK User Group ]
Senior Software Engineer :: Multifunction Instruments Applications Group
Software Engineer :: Measurements RLP Group (until Mar 2014)
Applications Engineer :: High Speed Product Group (until Sep 2008)

Visa Open and Close on every iteration of loop

I have noticed that when you open the front panel of the Instrument I/O Assistant, the diagram starts with a visa session open, sets timeout property, writes, reads, parses data and ends with a visa session closed. If I were to place this into a while loop the visa session would open and close on each iteration of the loop.
Is it common practice to open and close the visa session on each iteration?

No you would not want to open and close that often. If you want to use the Instrument I/O assistant what I would do is configure it the way you want and then save it under another name so you can open the block diagram. Pull the VISA open and close outside of your loop.
Using LabVIEW 2010SP1 and TestStand 4.5

Image open problem in nokia 5230

Dear All,
I have nokia 5230 mobile & i am using from last 10 months but from past few days i am facing problem regarding image/songs open problem. whenever i trying to open image my phone gets hang & it shows nothing in it but i have 100 pics in memory card, same problem is with songs whenever i put some songs in memry card but songs gallery after refreshing shows nothing.
Please help me to resolve this issue.
Vipul

im not sure what to do about the images but the same happened with the songs. here is waht i did:
1. make sure you have the latest firmware installed (fw. 50).
2. when it is installed copy all tracks to pc and install nokia ovi music.
3. delete the folder called 'music' on your memory card.
4. open ovi music and add songs to playlists and copy to device. this will create a new folfre called 'music' and the error should be fixed
if that fails you should try a program called lcg jukebox as this is a much better music player

Desktop.open() Problem

I recently put together an application that relied heavily on the Desktop.open( ) method and several other methods from the Desktop class. However, all of a sudden the Desktop.open() does not work. I believe I read some where that this was due to the ShellExecute function or dll or something like that.
However, since my app is targetted at the Windows platform I resorted to using windows Explorer to launch the system default applications for files using a the code below
public static void openFile(File file) {
try {
    Runtime runtime = Runtime.getRuntime();
    runtime.exec( "explorer.exe \"" + file.getAbsolutePath() + "\"" );
} catch(IOException) {
    ioe.printStackTrace();
    JOptionPane.showMessageDialog(null, "Could Not Open File Location: " + file.getAbsolutePath());
}The code works as expected, but my problem is that I am loosing cross-platform functionality.
Can any point my to solution to this Desktop.open( ) problem, or probably add the my list platform dependent launch procedures so at least the code works on Windows,Linux and Mac.
ICE

Thanks Andrew,
I've do a more simple example of the problem. I create two files on "\\fiuu\proyectosShared", one called "test.txt" and the other one called "te st.txt". I execute your exact source for the who paths whith these results:
File f = new File("//fiuu/proyectosShared/test.txt");
System.out.println(f + " exists: " + f.exists());
dt.open(f);
RESULT:
\\fiuu\proyectosShared\test.txt exists: true
(notepads opens the file)The second test does'nt work:
File f = new File("//fiuu/proyectosShared/te st.txt");
System.out.println(f + " exists: " + f.exists());
dt.open(f);
RESULT:
\\fiuu\proyectosShared\te st.txt exists: true
Exception in thread "main" java.io.IOException: Failed to open file:////fiuu/proyectosShared/te%20st.txt. Error message: El sistema no puede hallar la ruta especificada.
     at sun.awt.windows.WDesktopPeer.ShellExecute(WDesktopPeer.java:59)
     at sun.awt.windows.WDesktopPeer.open(WDesktopPeer.java:36)
     at java.awt.Desktop.open(Desktop.java:254)
     at DesktopTest.main(DesktopTest.java:14)
(translation of error message: System can't find specified path)I've also done some tests with Desktop.browse(file.toURI), and some others with no success.
Something curious: try to execute Runtime.getRuntime().exec("explorer " + f.getAbsolutePath) for a file that has thow white spaces on his name....
File f = new File("//fiuu/proyectosShared/te st.txt");//with two white spaces
System.out.println(f + " exists: " + f.exists());
Runtime.getRuntime().exec("explorer " + f.getAbsolutePath());
\\fiuu\proyectosShared\te st.txt exists: trueSystem says:
Explorador de Windows
La ruta '\\fiuu\proyectosShared\te st.txt' no existe o no es un directorio.
Aceptar
(spanish version of File not found alert message)Note that in alert message one white space of filename is lost!
Thanks again
Edited by: pakomail on Nov 24, 2008 6:12 AM

Oracle error - Open problem

hi friends,
on accessing the database i get this following error:
Open Problem - ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Execution Problemnull
How can i resove it...

Here's a wild idea.... check the Oracle site/documentation for suggestions ?

Erreur -1073807343 dans visa open

pour ouvrir une application (sur un systeme branche en serie) j ai regulierement l erreur -1073807343 dans visa open==> les informations concernant la position sont insuffisante
ou peripherique absent....alors que celui ci est present
merci

Hi Akim_10,
This part of the Forum is in English; please refer to this part of the Forum
to write in French.
Concerning your question:
When entering
the VISA resource name input for the VISA Open function or the VISA Serial
Config function, do not use the standard port names (COM1, COM2, LPT1, etc.).
Instead use the VISA resource name for these ports: COM1 is ASRL1::INSTR, etc.
For example:
Place a VISA Open
function on your block diagram and use the wiring tool to right-click on
the VISA resource name input.
Select Create » Control
from the right-click menu.
Go to the front panel
and right-click on the newly created control.
Select Allow Undefined
Names from the right-click menu (if it isn't already selected).
Enter the VISA Resource
Name for your port. The name should look something like
"ASRL1::INSTR". Note: This name can be found in the Measurement
& Automation Explorer (MAX) under Devices and Interfaces » Ports
(Serial & Parallel). For example, click on COM1 and you will see its
VISA Resource Name in the right-hand portion of the MAX window.
Benjamin R.
R&D Software Development Manager
http://www.fluigent.com/

LV5 VISA Open vs LV6 VISA Open

Currently have TestStand feeding the VISA Resource Name (string) into a LV5 VISA IO Open. We have upgraded to 6i and would like to re-use our current VI's. How do I mimic this same interface using the LV6i VISA IO Open. Specifically, how do I convert the TestStand string into the VISA Resource Name, such that it is controlled thru TestStand.

In my LV5 VIs I wrote for TestStand, I had string constants wired to the VISA Open and when I converted to LV6, it used a new function called Old VISA Open. However, I have no idea where to find this function on any of the pallettes. I've had to do a copy and paste for new VIs when I've wanted the same functionality.

NI I/O Trace VISA Open question

Hello,
I have a big application which has quite a few threads (timed while loops). One of the while loops is communicating on a specific COM port with a timed wait of 100 ms. This is the only loop which uses this specific COM port. When I look at NI I/O Trace, I see VISA Opens to this COM port every 2 ms. I have NI MAX closed. I tried changing my timed wait to 5000 ms but it had no effect. I am trying to see if something is slowing down my application and would like to reduce these number of calls. Is NI MAX or something else trying to communicate via this COM port?
Thanks

In IO Trace, if you navigate Tools >> Options >> View Selection, you can select the ProcessID and ThreadID Column headers to see which process and thread the calls are being made from.
Also, to verify the results of IO Trace, you could run a Portmon scan while the application is running.
'Portmon for Windows v3.03'
https://technet.microsoft.com/en-us/library/bb896644.aspx

CS4 extended file open problem in Windows 7

I am having a little spot of trouble. I switched from Windows to Mac recently and got myselfa copy of Photoshop CS5. I used to run Photoshop CS4 on a 32bit Windows 7 build and it works swell. Not a hitch. I've since moved CS4 onto a 64bit Windows 7 build and... it crashes when I open an image. Any image I've tried opening causes CS4 to crash.
I wonder if any of you would have a solution. I guess the only other piece of information I can talk about is that there's a version of Photoshop Elements 8 already installed on the system but I don't know if that would conflict or not.

Since you're probably still familiar enough with Windows to do maintenance, it sounds like what you're running into may be a display driver problem with OpenGL on your system...
Try this as a workaround: Go into Photoshop, choose Edit - Preferences - Performance, and uncheck [ ] Enable OpenGL Drawing, then restart Photoshop.
If this works around the problem, visit the web site of the maker of your video card and locate the display driver that matches your hardware and Windows 7 x64 OS. Download and install, then go back into Photoshop and reverse the above change (remembering to restart Photoshop after).
Good luck.
-Noel

VISA communication problem

Hello,
In my application i have communicated controller with the labview via serial communication with USB Serial cable (using VISA tool). My application works perfectly fine in development mode and in.exe(without installer)
Problem starts when I create the installer the communication starts malfunctioning. The communication behaviour is unpredictable. I have included different additional installer associated with VISA while creating my installer, the attached image shows it. Tell me if I am missing any additional installer. Some of the thread says that I should be having NI-Serial which is actually not listed in my case in the additional installer list.
The problem is that my application on target device (which is not having labview) is not taking certain commands. Guide me with this please. Thank you
Attachments:
installer.JPG ‏101 KB

Saumil wrote:
Well....a littel doubt in my mind. I developed all the VIs on labview 2011, but by mistake I opened it in labview 2012 and made installer and everything on labview 2012 only. Does it have to do anything with this?
In my experience, there is little risk in updating your VIs to a newer version; it's when you go backwards that you begin to have issues. That being said, maybe There are some options that are different between the two LabVIEW versions?
I know it's too late for this project, but have several versions of LabVIEW on the same (Windows 7) PC, and I've opened up projects in the wrong version even though I selected the project from the --> menu from the correct LabVIEW version on the Start Menu. It seems that the shortcut will open in the last version of LabVIEW that you had open, even if you did what I did above. Now I explicitly open the correct LabVIEW version and select the project from inside LabVIEW instead.
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

How can a I solve and GPIB/VISA compatibility problem?

My Labview (version 5.1 on a Macintosh) application talks to a variety of instruments over GPIB. In one mode it communicates with both 1) a LakeShore 340 temperature controler (LS340) using VISA-based drivers and 2) a Linear Research LR-700 AC resistance bridge using low-level GPIB functions. My application can query these instruments a couple of times per second, usually without trouble. However, periodically (about once an hour) the GPIB Read will cease to work with the LR700 or any of the other instruments on the same bus, returning error 6 (I/O operation aborted). GPIB Write still works fine. Querying the LS340 when the system is in this state produces the VISA error Hex 0xBFFF003C (Insufficient system reso
urces to perform necssary memory allocation). Querying the LS340 a second time is successful, and thereafter GPIB Reads are also successful.
I think somehow the GPIB and VISA protocols are interfering with each other. (Although the data dependency requires that the VISA Write/Read be complete before the GPIB Write/Read begins, I am not opening/closing the VISA session with every iteration. The VISA session is opened on the first iteration and stored in a shift register.) However, the maddening infrequency of this problem makes it very difficult to troubleshoot. Any suggestions?

Hi Chris,
One suggestion;
Write two seperate test routines that each use only one method or the other.
Test the H*&#$ out of each to attempt to determine if the issue is associated with the high level or the the low.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Visa open problem

Similar Messages

Maybe you are looking for