NI-488: Nonexistent GPIB interface.

Error 7 occurred at Open File+.vipen File
LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS X, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
=========================
NI-488: Nonexistent GPIB interface.

the messege againe and againe show on .
Attachments:
New Microsoft Excel Worksheet.xlsx ‏105 KB

Similar Messages

Error 7 occurred at Open File+.vi:Open File,NI-488: Nonexistent GPIB interface

I did some clean-up of my computer and have been having issues ever since.
I'm not the one that did the programming; the person who did is long gone.
The VI loads fine but when I hit run I get:
Error 7 occurred at Open File+.vipen File
LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
=========================
NI-488: Nonexistent GPIB interface.
All the necessary VIs are available and I've tried changing all the file calls in the VIs to the new locations but the error is the same.
Any suggestions?
Thanks.

Error 7 is a generic file not found. If it is happening after cleaning up files, more than likely you moved some subVIs called in a main VI to a new location on your computer. If all the VIs are in a project, a possible solution would be to remove the vis in the project directory and add them back to the project as they may be pointing to a previous location where the files were once stored. Perhaps this is what Anon123123123 meant by "linking". Hope this helps.
Regards,
Isaac S.
Regards,
Isaac S.
Applications Engineer
National Instruments

Error 7 file not found NI-488 nonexistent GPIB interface

I'm trying to use an accelerometers with cRIO through NI 9234. I'm using an Fpga example which I modified according to my characteristics. Till here, everything is OK, nevertheless when I open the Fpga vi file and I run it compilation is not finished and it si returned the next message:
Error 7 occurred at NI_LVConfig.lvlib:Load.vi
Possible reason(s):
LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS X, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
=========================
NI-488: Nonexistent GPIB interface.
I have attempted several possible solutions paste in the forums but I have not solved the problem
Attachments:
error 7.docx ‏13 KB

Are you using any filepaths in your application? Does the VI have any subVI's? The error you are getting is triggered by a reference to a filepath. Does your application call a file at any point? You need to make sure that all of the filepaths your application is referencing are in fact the correct location for these files.
Also, you may need to check your Open FPGA Reference VI, which loads a bitfile. Usually, this bitfile relies in the same directory as your LabVIEW Project.
Hope this helps!!
Anuar Rojas
Anuar R.
National Instruments México y Latinoamérica
Ingeniería de Aplicaciones
www.ni.com/soporte

EMtest GPIB interface error after updating NI-488.2 driver

I am using GPIB interface and Vendor Software to control EMtest devices (Autowave & VDS). After updating the NI-488.2 from version 2.2.7 (ni488227.exe) to 3.1.2 (ni488_312) the EMTest software is no longer recognizing the NI PCIe-GPIB interface (?).
After re-installing back the old NI-488.2.2.7 everything is returned to normal. Is there any known solution to this type of errors?
Thank you!
Attachments:
GPIB.png ‏70 KB
GPIB-ok.png ‏68 KB

There are no HW changes on my system (the only variable is the NI-488 driver version) and my software has no options to add or change the settings of an GPIB interface (except the GPIB addresses of my devices).
In NI-MAX I found no diferences, my PCI card is always defined as GPIB0. The problem is that somehow my software is set on GPIB1 after updating the NI-488 driver ... therefore is not able to find any GPIB card.
I was just wondering if anyone had similar problems while I am not able to find any satisfying configuration to my software (except using the old version of NI-488). And maybe there is a solution/configuration of the NI-driver.
Thank you!

NI -488.2 GPIB

I am Sze Yuen Cheng from Osram Sylvania Inc. I have a few questions about your NI-488.2 GPIB. I need to use the GPIB to interface a few Xitron power analyzer instruments with the computer by using Visual Basic 6, and this is the first time that I am using both Visual Basic and GPIB. I found 2 files from the NI-488.2 software CD: one is called Vbibi-32.bas and the other is Niglobal.bas. What are these files? Are they just the initialization and variable definitions for the GPIB hardware? Do I have to include these files with the Visual Basic program in order to communicate between the computer and the instruments through the GPIB? How can I include these files in the Visual Basic program? What are the most important things that I have to know
or acquire from the Vbibi-32.bas and the Niglobal.bas files in order to finish my task? I am going to attach these 2 files for your references.
If you need more information, please contact me at [email protected] or 847-726-6258.
Thank you,
Sincerely,
Sze Yuen Cheng
Attachments:
Vbib-32.bas.txt ‏52 KB
Niglobal.bas.txt ‏13 KB

Hi,
You have found the right two files! These two files make up what we call the "language interface files" for VB. You can find out more here: http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B45EACE3D90756A4E034080020E74861&p_node=DZ52353&p_source=external
In summary:
NIGLOBAL.BAS: global module containing predefined constant declarations
VBIB-32.BAS: source file containing NI-488.2 routine and NI-488 function prototypes
I always find that the best way to learn is by example. There should be some basic examples that installed with your NI-488.2 driver. If you installed it to the default path, it will be located in C:\Program Files\National Instruments\NI-488.2\Languages\Visual Basic
Take a look at those examples. They should hel
p you get on your way.
Best Regards,
Aaron K.
Application Engineer
National Instruments

What exactly is happening/failing when "GPIB Interfaces sequentially verified" FAILS?

I have an AT-GPIB/TNT+ card installed in my computer. It fails the "GPIB Interfaces sequentially verified" portion of the Wizard program. I am able to communicate (IBIC) with my instruments, so it appears that all is working well. I do have older non-compliant GPIB interfaces so the "Scan for Instruments" does not work. What exactly is failing in the Wizard and what can I do? I have windows 95.0.

Janet,
Typically when the installations fails the sequential verification, it is due to either a resource conflict or a device being connected to the board during the test. You can click on the failed interface to get a brief explination of what may have caused the error.
There are instances reported using the AT-GPIB/TNT+ board and Win 98 inwhich this error was reported even though there were no problems with the board's setup. Since you are communicating properly with the board through IBIC your board is functioning properly, and I would not be concerned with the error message.
As for your instrument, this is likely due to your instruments non-compliance to 488.2 standards. Whenever the Measurement & Automation Explorer does a "Scan for Instruments", it sends out the stri
ng "*idn?" (which is an IEEE 488.2 identification query string) to all of the devices on the bus. If you have older, non-IEEE 488.2 compliant instruments on your GPIB, then they will not recognize this string as a valid command. This will cause "Scan for Instruments" to fail.
Best Regards,
Chris D

HP3885A with GPIB interface

I'm trying to develope a program under Labview 7.1 to acquire the spectrum from the HP3885A with GPIB interface. Does anyone have the driver or example vi for HP3885A?
Thanks,
Waymon

Is the HP3885A an IVI compliant instrument? Can you use an IVI driver with it? Even if there isn't one available, or if no users respond with a driver, you could use the IVI Class drivers, if it is classified as an IVI device. Also, have you submitted a request a driver?
Logan S.

Problem retriving data from OSA MS9710 with GPIB interface

Hi all,
I'm trying to read data from Anritsu OSA MS9710 using a GPIB interface and a terminal software in computer. However, I am not having sucess with it. Anyone know how can I do this? or another way to read this data without needing a floopy disk?
Thank a lot!

Anritsu has a LabVIEW driver. I don't know what kind of terminal software you are talking about. Most terminal emulators are only useful for RS-232. You can use MAX (Measurement & Automation Explorer) to communicate. Nor do I understand how a floppy disk could help.

Populating list with connected GPIB interfaces

I'm working on the setup section of an APP in Delphi5.0 using the GPIB-32.DLL and am a little baffled. Ni supplied this little gizmo that searches for GPIB interfaces (not devices). I would like to emulate this functionality for my application in a setup wizard sort of way so the end user can simply select from a list of 'detected' interfaces. In looking at the DLL calls they all seem to require previous knowledge of the device location. So I'm wondering if there is a set range of possible Primary and Secondary addresses I can use to just loop through searching for an interface. I'm assuming here that anything that wouldn't toss a failure when sent a Pri/Sec Address would be a set of valid device ports. On that note...
are there some specific commands to issue that will return a string telling me exactly what it found on that Pri/Sec address?
Thanks!
CT

Ok.. I made some progress. Using SendIFC and ibfind, etc, watching NiSpy I have determined this is coming back as an Integer and other Ni applications use the Init_DA_Brds to obtain a translation of the integer to descriptive title. However I don't have access to that and the only reference I found of the device list codes is from 1999 which does not include some of the newest hardware including the USB based devices.
Is there a newer list of product codes available?

Will data transfer in parallel in GPIB interface?

Hi all,
I have two devices (supporting GPIB) connected in serial and connect to the GPIB interface card. Those two devices have two different addresses and I use VISA module to send data in parallel. But the GPIB cables are connected in serial, so does it mean it will be locked when transferring data to one device? I think GPIB transfer rate is not that low (about 1Mbyte/sec) but it takes so long to transfer 500kB to the device (about 45sec).
Solved!
Go to Solution.

Dennis_Knutson wrote:
The GPIB bus does not support parallel data transfers so you are certainly sending it that way.
You have not provided the instrument or your code so it.is impossible to say anything about your transfer rate but the 1MB is a theoretical maximum that you seldom achieve in the real world.
Here is the link for the device I have
http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=E3B19B3E9294659CE034080020E748...
The code is not written by me, but I extract the core part and show as below
You will see that there is only one GPIB interface (0), both device 1 and device 2 are connecting to the same card. The data sending to device 1 and device 2 is about 400kB (shown as xxxx.xxxxx. and yyyy.yyyyy).

PC-Card GPIB Interface for a Desktop PC using USB card reader?

I have a IOTech's PCMCIA GPIB interface card. It works well on the notebook with LabVIEW. I want to use it on the Desktop PC using USB card reader or other connectors with LabVIEW.

Somebody wrote in about this issue. From his comments, it sounds like it may work.
See:
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=506500000008000000E6100000&ECategory=Measurement+Studio.LabWindows-CVI
Randy Solomonson
Applications Engineer
National Instruments

GPIB instruments connected through Agilent USB/GPIB Interface can bee seen in MAX but can't communicate in labview

I have an Agilent 82357B USB/GPIB Interface connected to my computer.
Attached to that, I have two lock-in amplifiers (an SR830, and an SR
850). I would like to be able to communicate with them through GPIB.
I have downloaded and installed the software for the Agilent device
(Agilent IO Control), and I can see the interface and the two devices
in that software. Here's what is configured in this software, that I
can see:
The VISA interface ID is GPIB0, and its address is 0
The VISA addresses of the devices are GPIB0::4::INSTR and GPIB::12::INSTR, and the GPIB addresses are 4 and 12
In Measerment and Automation Explorer (MAX), I made sure that the
Passport for Tulip box was checked. Once it was, I could see the
devices in the Configuration window under Devices and Interfaces ->
Miscellaneous VISA Resources. There, I see GPIB0::INTFC, GPIB0::4::INSTR and GPIB::12::INSTR.
I can right click on either of the instruments, and "Open VISA Test
Panel" where I am successfully able to send commands and read from both
devices.
HOWEVER, when I am running an actual LabView program, I am unable to communicate with the devices.
For example, when I try to communicate to the devices through VISA,
using the 'Basic Serial Write and Read.vi' (while VISA Resource Name is
GPIB0::12::INSTR), I get an error:
Error -1073807331 occurred at Property Node (arg 2) in VISA Configure Serial Port (Instr).vi->Basic Serial Write and Read.vi
Possible reason(s):
VISA: (Hex 0xBFFF001D) The specified attribute is not defined or supported by the referenced resource.
When trying to communicate with them through GPIB (which is what I want
to do in the end), using 'GPIB.vi' I also get an error. Here, GPIB
address is 12, and I am just trying to give it the command *IDN?
GPIB Write returned error code:
EDVR: Error connecting to driver or device
What's going on?

You can use VISA Write and VISA Read. You just can't use the example called Basic Serial Write and Read because that is specifically for the RS-232 port. The GPIB-VISA is one of the shipping examples. Start the example finder and go to the search tab. Search for VISA.
Again, no you cannot use the GPIB functions with a non-NI controller. The low level functions for an NI board and an Agilent one are completely different. You can rewrite the driver to use VISA or you can rewrite it to use the low level functions that Agilent provides. You use the Call Library Function Node, I believe to access their GPIB driver.
I hate to say it but the $20 difference between the Agilent and the NI controller does not seem like much of a saving.

Can't find GPIB interface

I have a HP82350A GPIB card installed in my computer with Win2000 OS. The old IO library provided by HP doesn't work under Win2000, so I went to agilent's site and got a new IO library which is for their GBIP card also named 82350A. (I guess these two products are the same) And it works, the io config shows the GBIP card, and my program written with SICL in C++ can also control a power supply. But what I want, is to use Labview to control a hp oscilloscope(now it also belongs to agilent), so I installed NI488.2 from NI's site. And, it said that I have no GPIB interface!! I've reinstalled the software and hardware for many times, no use. Anyone knows what's wrong with this card? or, did I miss something? Thanks a lot!
Dan

I have gone through this a number of times on our WIN NT platforms. The instructions that I got from NI was to load the HP VISA drivers and do NOT load NI VISA. NI488.2 is for NI cards. If the HP IO library sees the cards, then you're set. Also, MAX will not work with the HP card.
Use the VISA calls in LabVIEW and use the "standard" VISA names for instruments on the GPIB bus (eg. GPIB0::9::INSTR). Since MAX does not work, you will not be able to setup an alias that LabVIEW will work with.
I use this method and my LabVIEW programs work with our NI cards, HP cards and Computer Boards cards without having to change the program.
Rob

Problem with Get the current and voltage from HP Power Supply (HP E3631A), using the GPIB interface.

my USB device's power support is from the DC Power Supply ( HP E3631A)
I need to read using current from a DC Power Supply ( HP E3631A),via GPIB interface.
When I use the follow command.Why can't read the current value.My environment is in vc++ 6.0.
"APPL P6V,5.0,1.0"
"OUTP ON"
"MEAS:CURR? P6V"
attached the NI SPY File.Please check it.
Can you tell me what the problem is ??
Thanks in Advance !
Hope you can solve my problem !!!"
Attachments:
E3631AERR.spy ‏7 KB

Hi neilchuang,
A read timeout error is usually caused by an error on the command string sent.
The first thing I would check is if the instrument requires a termination character at the end of each message (such as linefeed). I noticed in the Spy capture that the commands do not have a termination character attached. This means that the instruments never recognized that you completed the query command, it doesn't execute the requested action and as a consequence of that it doesn't have any data to return.
One question: Is the instrument detected by MAX when you scan for instruments?. If yes then you can assume that the GPIB software and hardware are properly installed. The scan for instruments sends the *IDN? (terminated by a linefeed). You can right-cli
ck on the instrument entry in MAX and select "Communicate with instrument". Notice that at the end of the command the linefeed is included (\n).
Double check with the instrument manual if the commands sent are the right ones.
Finally, there is an instrument driver available in the idnet library: www.ni.com/idnet. Search for 3631. Since you are working in C you can use the LabWindows/CVI Plug and Play driver. Even if you decide not to use the instrument driver, you can still use it as an excellent reference on how to program with the instrument.
Hope this helps!.
DiegoF
National InstrumentsMessage Edited by Molly K on 02-18-2005 11:05 PM

488.2 GPIB versus VISA

Hi,
I have an issue regarding GPIB. I want to do the following:
1. Initialising a Tektronix scope TDS7154 using the provided VISA driver VIs.
2. Sending a couple of pulses with a waveform generator using the 488.2 GPIB functions
3. Reading data from the scope with the VISA drivers.
What I see now is that the scope initialization works fine, also the communication with the waveform generator. But the following VISA communication is very slow. Reading data from the scope takes minutes. Has anybody suggestions what's the problem and how it can be solved? This task is a subroutine in a much bigger program using only the 488.2 GPIB functions. So it would be nice if I don't have to change the way of GPIB communication for one of the two devices.
Tanks,
Steve

I doubt that there is any issue with VISA. There is very, very, little extra overhead in using VISA functions. Under the hood, the VISA functions call the low level GPIB functions after all.
The time it takes to read the scope will depend on how many points you are requesting, the sample rate, how long it takes for the scope to be triggered. You have not provided this basic sort of information or attached your code.
p.s. It would probably be advantageous to switch to VISA at some point. It helps prevent obsolence in your code. If you ever switch to Ethernet or USB connections, you would not have to do any rewrites at all or just a minor one.

NI-488: Nonexistent GPIB interface.

Similar Messages

Maybe you are looking for