Creating exe with GPIB-USB

When I create an application that uses my GPIB-USB-A interface it is not included as one of the VISA selections when the application is installed. Which files do I have to add to application installation to have my application work with GPIB-USB?

You would need to install the GPIB and VISA driver,
For GPIB, follow the steps from www.ni.com/support/install. You can download the latest visa driver from, ftp://ftp.ni.com/support/visa/drivers/

Similar Messages

LabVIEW exe. with 2 USB Daq devices

Hello All,
I am trying to build a LabVIEW exe. with two USB 6210 data aquistion modules plugged into a USB hub installed inside a 19" rack. I used the DAQ Assistant to generate the LabVIEW code for the aquisition and it works fine. However, when I disconnect the USB cable from the development machine and reconnect later, my I/O are mapped to the wrong modules. Is there a way to map my channel names to the actual module, maybe in MAX, and just include the Max configuration file in my exe? Can I use the DAQ assistant, or do I configure the physical channel names and create my own tasks in MAX and not use the DAQ Assistant?
Any help would be appreciated.
Thanks

Hi Botman,
Unfortunately you are in a unique situation in that you have 2 of the same type device that are removed from the system and reconnected to the system at the same time. However, it is probably not guaranteed that one device will be detected before another consistently. Given your situation I would recommend that you set up your application to programmatically discover the devices in your system. There is an example program here that demonstrates how to do this. In your case I think detecting by serial number would be ideal. All you would need to do is include the LLB file in your project to ensure that all of the necessary VIs are included.
Keep in mind that this will require some modification of your code. You will need to use the lower-level DAQmx functions rather than the DAQ Assistant (which basically serves as a wrapper around the lower-level functions). In the end, adding the VI from the example program above and using lower-level DAQmx functions will make your code more robust because distributing the executable to another system (or even using it on the development system) will not require the user to interface with MAX at all. Let me know if you have any other questions.
Regards,
Andrew W
National Instruments

Setting up a DS345 with GPIB-USB-HS

Quick guide to how to set up a Stanford Research Systems (SRS) DS345 synthesized function generator.
1) Ensure you're not going to shock anything (i.e. having the computer and device on two different grounds), then plug in the GPIB-USB-HS cable to device.
2) On the front panel of the DS345 set gpib to on (address default should be 19).
3) Open NI's Measurement and Automation Explorer, and ensure the device shows up.
4) Open NIvisaic.exe and send a query "*IDN?\n". You should get the device info back.
5) Using NIvisaic, write "FUNC\s1\n" this should change the function type generated to Square Wave type.
6) Use Labviews VISA library. For still unknown reasons, I could not get the normal GPIB library to control the DS345 over GPIB-USB-HS. This means the entire driver library for the DS345 didn't work for me. This means you'll have to do some more work learning the DS345's communication protocol (see http://www.thinksrs.com/downloads/PDFs/Manuals/DS345m.pdf). But I only needed to change 2 things on the DS345 so that fit my needs.

Quick guide to how to set up a Stanford Research Systems (SRS) DS345 synthesized function generator.
1) Ensure you're not going to shock anything (i.e. having the computer and device on two different grounds), then plug in the GPIB-USB-HS cable to device.
2) On the front panel of the DS345 set gpib to on (address default should be 19).
3) Open NI's Measurement and Automation Explorer, and ensure the device shows up.
4) Open NIvisaic.exe and send a query "*IDN?\n". You should get the device info back.
5) Using NIvisaic, write "FUNC\s1\n" this should change the function type generated to Square Wave type.
6) Use Labviews VISA library. For still unknown reasons, I could not get the normal GPIB library to control the DS345 over GPIB-USB-HS. This means the entire driver library for the DS345 didn't work for me. This means you'll have to do some more work learning the DS345's communication protocol (see http://www.thinksrs.com/downloads/PDFs/Manuals/DS345m.pdf). But I only needed to change 2 things on the DS345 so that fit my needs.

Create exe with some vi files

Hello,
I am using LabVIEW 2010
I am trying to build a "Main.vi" into an exe, in which this Main.vi needs to dynamically call two vi "1.vi" and "2.vi". I have put into "always included" before building the exe. But after creating exe "1.vi" and "2.vi" don't run.
Solved!
Go to Solution.
Attachments:
рисунок1.jpg ‏81 KB
рисунок2.jpg ‏247 KB

Just to show what Norbert is saying. You should get in the habit of using relative paths. They will save you a lot of headaches down the road, especially if you are dynamically calling VIs inside of EXEs.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
Relative Path.png ‏11 KB

Combine 2 computers ea with GPIB-USB-HS connected to different calibrators into one system

I’ve got 2 separate systems: Computer A fitted with a GPIB-USB_HS+ controller and connected to a calibrator A and bench multimeter A, and Computer B fitted with a GPIB-USB_HS+ controller and connected to calibrator B and bench multimeter B. To enable computer A to gain access to calibrator B and bench multimeter B (and visa versa) I want to interconnect the 2 systems with a GPIB cable. Will it work?

Since there can only be one CIC, you just can't connect the cables. Your software on both pc's will have to detect if the other program is running and make the controller on the non-running pc not to be CIC.
Your other option is to remotely control the other pc's instruments with VISA Server if there is a network connection. You would still need some means of checking if a program is running on the other pc.

GPIB-USB-A malfunction after connection to old instrument

I connected a Solartron 1286 potentiostat (made in mid-80's) to my GPIB-USB-A interface, and it seems to have damaged my interface. I can install the GPIB-USB-A just fine, but when I try to search for instruments, the search time seems infinite. Are there warnings issued about the USB-A model regarding connecting to older instruments? Has anybody encountered this behavior before?

There is no known issues with GPIB-USB-A with your particular instrument and I know people have uses this USB-GPIB interface with older instruments without a problem.
It does not seem like there is a problem with interface if you could install the driver fine. You can use NI-SPY to take a SPY capture when "Scanning for instrument", this should give you more info on what was wrong. Also make sure your instrument is still functioning correctly; install the latest NI4882 driver (ver 2.3); and try to connect the instrument with a different cable, etc.

Troubles with Agilent gpib/usb interface

I have a problem to use Agilent 82357A gpib/usb interface with NI VISA (os Win98). I have Visa3.0.1. I did all what is written in file niinfo.htm, which containes some advices for running the agilent gpib/usb card with NI software(it is in directory prog. files\agilent\IO Libraries\readme\trouble\) and I also tried most of advices written on the web pages of ni.com. In MAX3 I can only see "miscellaous VISA resources". When I run NIVISAAIC, I can communicate with interface as well as with instrument attached to it. When I close nivisaaic, it returns arror message, that program performed unauthorised operation in module agvisa32.dll. It indicate that trouble is between libraries of NI and Agilent. I tried to install agilent gpib/u
sb driver in many ways, only SICL, or SICL + agilent visa (secondary, side by side), but nothing works. When I run Getting started wizard in run-programs-national instruments-Ni.488.2, it detects no gpib hardware, even MAX indicates some "miscellaous VISA resources". Is there somebody with experiences how to solve this problem.? Thanks

1. I have tried method 1 in that KB you have adviced me. I uninstalled Ni-Visa and instaled HP-Visa (is not clear from the KB description, if HP should be primary or secondary, side-by side. I tried both configurations). Of course MAX does not find gpib board in any case. To solve this problem in the KB is written "you must right-click on the control or constant and select "Allow Undefined Names." In this step I stopped, because in the MAX I did not find where this "constant or control" is. I tried to do right-click on "devices and interfaces", but only "Create new..." menu appears. The right-click on anything in the MAX does not open the menu which contains "Allow undefined names". Can you please, specify where this right-click should be done to allow undefined names and to continue with method1 to reach the goal of using LV for data aquisition.
2. Then I tried method 2 from the KB. I have uninstalled HP-visa; HP-SICL and Ni-Visa3.0 is installed, NiVisaTulip.dll passport is allowed and F5 refresh made. In MAX in the section Devices and Interfaces I can see "? Miscellaneous VISA resources" with "GPIB1::22::Instr" (it is for one device with address 22). Instead of "? Miscellaneous VISA resources" I expected, there will be written something like GPIB1(USB-GPIB). In this point I have few questions.
a) Is it correct if there is only "? Miscellaneous visa resources"?
b) If I configure usb/gpib card with Agilent config. utility to SICL name gpibn and visa name gpibn, where n is some integer, MAX shows everytime gpib1. There is only one gpib card installed in the PC, so I expect there will be gpib0 in the MAX.
Now, when I run nivisaic, I can see gpib interface named gpibn with gpibn::22::instr. I can communicate through this interface to the instrument in the session opened by double-click on the resource. In the Nivisaic there is also another interface marked as unknown-gpibn::intfc and gpibn::servant. I cannot communicate with this interface. When I install HP SICL with HP visa as secondary, side-by-side, this "unknown gpib" disappears. Then nivisaic seems to be OK(but MAX still shows "? miscellaneous visa resources"),the status of each operation in NI Spy is succesfull. I think I did everything required in method 2 of KB but, I cannot perform any data aquisition by LabView. Are there further thinks to do for starting data aquisiton? Thanks for any advices.

GPIB-USB libraries that need to be included with Installer

Hi,
I need to make a small application executable, and the application needs to communicate with a power supply over a GPIB-USB-B connection. MAX can communicate with the power supply on this PC, and the second PC that I have my Base LabVIEW 7.1 installed on runs the executable application successfully. When I try to run the executable on the first PC, however, the process hangs. I included an Installer in the original executable build for the first PC, and in this build all the options under LavVIEW Run-Time Engine were checked (although LabVIEW RT Support wasn't available for checking.) However, none of the other options (Remote Panel License Support, Serial Port Support, Port I/O Support, and Hardware Configuration) are checked because I didn't think that I needed any of these for the basic GPIB communication I'm performing (just VISA Open, Read, and Write). Do you have any idea which of these libraries I need to include in the Installer to make this work? Or is there some other problem I'm not thinking of?
Thanks,
Mark

What makes the situation odd is that MAX was capable of communicating with the device, but my application was not. In the interest of making it work, I stuck a spare license of Base LabVIEW onto the PC, and then the application (even the compiled, executable one) worked fine. So clearly something wasn't loaded along with the GPIB-USB-B drivers (or my application installer) that WAS loaded by the full installation of LabVIEW. But, again, the oddness of the situation stems from the fact that before loading the full LabVIEW, MAX (loaded by the GPIB-USB drivers) could communicate fine with the device. This set of circumstances doesn't make any sense to me, but maybe someone else can come up with something.
The PC is a W2K box, and I assume whatever driver information that came in the installer and the GPIB-USB drivers has been overwritten by the full LabVIEW that's since been installed on the machine. I didn't actually oversee the installation of the GPIB-USB drivers, so it's possible the engineer who did that put the card into some odd state--it's also possible he didn't reboot after the driver installation. If the resources come free I'd like to clear out the machine and start fresh and recreate the sequence of events to see if I get the same result. I wouldn't be surprised if the problem stemmed from issues in the driver installation. But I want to hear if anyone's been in a situation like this before I go and do everything over again.
Thanks for your help, and for the additional installer information,
Mark

Creating a desktop PC utility with an USB boot utility

Creating a desktop PC utility with an USB boot utility
Hi everybody
when I looked for how create an Real-Time Desktop ETS I found two ways to do it:
1. With USB create, here is the program: http://joule.ni.com/nidu/cds/view/p/lang/en/id/1369
2. With Measurement & Automation Explorer (MAX)
With both, I been having trouble, but I could find an explanation of the error that comes up. This is the warning message that comes up: "Unable to find a USB drive. Make sure that it is connected to your computer." So I thought that the USB drive wasn't good, I changed the USB and the same message keeps coming up. I looked for all the necesary requirements, and I have everything in order, the real time module, the CVI, and LabVIEW SP1, but I only have the evaluation version, I would like to check it first and look if it works OK.
Here are the instructions:
http://digital.ni.com/public.nsf/allkb/9209361E17708D548625744A007FF353?OpenDocument
I hope that someone can help me. thanks.
"Everything that has a beginning has an end"

Hey anfedres,
I went ahead and deactivated by labview and labview rt installs, and I was still able to format a USB drive just fine with both the utility and MAX. My suggestion would be to try switching out the USB drives again, the smaller the better. The utility is very small, so if you have any of those small flash drives that people give out at conferences/expos/etc, you may be better served by using that rather than a 16 GB drive. Some flash drives come with built in utilities that can cause problems, so the simpler the better. You might also completely format the usb drive using windows before using our utility. The flash drive I used was completely empty.
I also wanted to make sure that you were aware of the deployment license associated with the process you are attempting:
http://sine.ni.com/nips/cds/view/p/lang/en/nid/13753
Let me know how a different drive works out, and we can move forward from there.
Thanks,

Compatibility of Agilent GPIB/USB adapter with NI

Hi,
I have an Agilent GPIB / USB adapter 82357B, and I'm experiencing some problems for detecting my instruments in the laboratory when I try to use the labview software for capturing the data from the measurement instruments.
I installed the CD with the libraries the adapter has and through this software I can detect the instruments, however once that I open the Labview software from National instruments(NI) for capturing my data, I miss comunication with the devices in both programs, the Agilent one and in the MAX of NI.
I run across a document regarding tip on using Agilent GPIB solutions in National instruments's Labview environment. I have done all the document indicates, but It is not workingt, I experience the problem I outlined above for detecting the instruments.
I hope someone can help me with that.
Regards

DCU STUDENT wrote:
Yes I am. According to documents it is possible. But I don't know want else to do, since I have done what document indicated. I as mentioned in previous message, now I can see the measurement instrument with Labview and using the Agilent cable adapter, and I can stablish communication with device since that when I select the device in the labview program, a led in the instrument is ON, indicating communication. However when I try to capture the data on screen, there is not data at all.
Hello DCU STUDENT,
It sounds like there may be some conflict between the NI VISA and Agilent drivers, which can occur between certain models; considering when you use the NI cable data can be collected when when you're using the Agilent you cannot. Please tell me what versions of both drivers you are using so I can determine whether or not there are any known incompatibilities between the two if you're still receiving the same error after following these instructions.
Can you also please go through this instrument troubleshooting guide to see if your installation matches the expected configuration of a functional device so we can confirm that your driver has been installed correctly from the previous guides.
For a IEEE488 Agilent Device Card, as you mentioned that you have the NIVISATulip.dll enabled, for this GPIB configuration to work you must ensure that the 488 Programs must be activated with NI 488.2 (At the Enable Agilent GPIB cards option) through the Agilent Connection Expert.
You've mentioned that you've been able to establish a connection with the device and see communication transfer, yet you are getting no returned communication. Do you see a similar response when you view the device through the Measurement and Automation Explorer?
If it is possible, could you test your configuration with any other Agilent devices with your current configuration and see if the error persists?
Alex Thomas, University of Manchester School of EEE LabVIEW Ambassador (CLAD)

Create uninstaller exe with application builder

Hi!
Im using LabVIEW 8.5. I have created an application with the app. builder, it works fine, also an installer.
But I need an UNINSTALLER, like Uninstall.exe to be created also.
I have found a NI doc, which says:
"The Create Uninstaller option was removed from the
Advanced Installer Settings dialog box because the Application
Builder always creates an uninstaller"
But where can I find it?
im able to uninstall my app, using the Windows add/remove softwares option, but i need an exe.
Can you help me?
Thanks:
Waszil

Since the installer is based on Microsoft technology and the Microsoft standard is to only have the Add/Remove option, you cannot create an uninstall.exe with LabVIEW. I'm not even sure why would would need to if everything works with Add/Remove Programs and that is what everyone is used to now. In any case, there are probably some commercial installer packages available that still support the old technology.

When ever I use Adobe reader 11 with a USB device, I cannot safe remove the USB device and get the following message (or similar one) in system log: The application \Device\HarddiskVolume1\Program Files (x86)\Adobe\Reader 11.0\Reader\AcroRd32.exe with pr

When ever I use Adobe reader 11 with a USB device, I cannot safe remove the USB device and get the following message (or similar one) in system log: The application \Device\HarddiskVolume1\Program Files (x86)\Adobe\Reader 11.0\Reader\AcroRd32.exe with process id 6620 stopped the removal or ejection for the device USB\VID_05DC&PID_C75C\20131215015821328FC8.
I am running on Windows Server 2012 R2 in Desktop Experience mode.
Any ideas?
Roger

In addition to that symptom, I discovered that even though I had closed all Adobe Reader sessions, the processes kept running and used up 90%+ of my CPU.

External GPIB-USB Controller with Windows2000

Is there a Chance to use the external GPIB controller GPIB-USB (NOT the
newer USB-A version) with Windows 2000 ?? The special GPIB driver for the
"A" revision is not working.
Ciao
Matthias

I am not sure if this will fix your problem, but I was able to get a USB GPIB controller to work in Win2K by replacing the file "NiVi488.dll" as described in the following NI support page:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/862567530005f09f862569dd007da5f0?OpenDocument
Best of Luck,
-Jim

I would like to know a question regarding interfacing with a Yokogowa WT130 utilizing a NI GPIB-USB-HS is possible in Dasy Lab

I have a Yokogowa WT130 power analyzer and I would like to use this to communicate to DASY Lab. The Yokogowa utilizes IEEE 488 communication and I was thinking of using the NI GPIB-USB-HS to connect the Yokogowa to the computer. I do know that DASY Lab is capable of utilizing IEEE 488 but I am confused on if I would neede a seperate driver for the Yokogowa or if the driver for the NI GPIB-USB-HS would allow communication. Any feedback would be greatly appreciated.

backhausr1,
I would recommend asking this in the DASYLab forum, which can be found here: http://forums.ni.com/t5/DASYLab/bd-p/50
You will likely get better and more prompt assistance.
Christopher S. | Applications Engineer
Certified LabVIEW Developer
"If in doubt... flat out." - Colin McRae

Is GPIB-USB-B compatible GPIB card? if yes, which card and driver?

I have my codes written while I was using GPIB-USB-B to communicate with HP-4145 from my PC win-XP.
Now I want to use a GPIB card rather than the USB version.
1- Can I use a GPIB card without changing my codes?
2- if yes, then which GPIB card( and which driver) should I use?
Thanks
Solved!
Go to Solution.

does any one know the proper location to use firmware upgrade for GPIB-USB-B
$ rpm -q kernel
kernel-2.6.18-274.7.1.el5
------ result from exe command line ---
[root@gb095 ni_gpib_usb_b]# fxload -D /proc/bus/usb/003/001 -I niusbb_firmware.hex -s niusbb_loader.hex
can't modify CPUCS: Broken pipe
README FILE CONTENTS
The firmware files can be uploaded to your NI GPIB-USB-B adapter
using fxload. Example:
fxload -D /proc/bus/usb/001/002 -I niusbb_firmware.hex -s niusbb_loader.hex
If you wish for the firmware to be automatically loaded through hotplug,
copy the firmware files to the /usr/share/usb/ni_usb_gpib/ directory
(or wherever the /etc/hotplug/usb/ni_usb_gpib script expects to find them).
Thanks go to Michael Ritzert for figuring out how to extract the firmware
from a usb sniff log. The log that was used is included
(file name is "ni-usb-b-initialization-log.txt"), as well as the perl
script for creating the hex file ("firmware_extract.pl").
what i have to do is upgrade these cards to latest firmware to see if the work with this level kernel
$ rpm -q kernel
kernel-2.6.32-358.el6.x86_64

Creating exe with GPIB-USB

Similar Messages

Maybe you are looking for