Obsolete GPIB-USB-A problem again

Hi , all, sorry to bother you but I really do not know how to deal with this,
I have a obsolete GPIB-USB-A cable to connect with an instrument,
this morning I installed NI488.2 V2.2 on WinXP, it works, the instrument responds to my commands.
This afternoon I installed labview 2012, then the GPIB explorer is reporting error,
I can no more communicate with the instrument!
I think there might be some newer versions automatically included in LV2012, which might not be suitable for the obsolete GPIB-USB-A,
so I re install NI488.2 V2.2, it is still reporting error.
I checked the VISA version is 3.0.1,
What is the problem? Is that VISA version not compatible with LV2012?

Hi Julia2013,
Based on this chart: http://www.ni.com/white-paper/5326/en/, GPIB_USB_A is compatible with NI 488.2 Ver 2.2. However, based on this link: http://digital.ni.com/public.nsf/allkb/2BFCEE471BECB95F862574020059117E, NI 488.2 Ver 2.2 is compatible with LabVIEW 6.1, 7.0 and 7.1. Therefore, to begin with, I believe that the NI 488.2 Ver 2.2 is not compatible with LabVIEW 2012
Based on this link: http://digital.ni.com/public.nsf/allkb/CF4279A34F855AB186257B1F00003B82, you'll notice that NI VISA 5.2, 5.3 and 5.4 are the only VISA versions that are compatible with LabVIEW 2012.
Therefore in summary, GPIB-USB-A is not compatible with LabVIEW 2012. Based on the first link I have mentioned, GPIB-USB-B and GPIB-USB-HS
uses NI 488.2 Ver. 3.1.1 which is compatible with the LabVIEW 2012 and thus is compatible with the VISA ver 5.2, 5.3 and 5.4.
Hope it answers your enquiry.
Warmest regards,
Lennard.C
Learning new things everyday...

Similar Messages

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

Itunes 7 and USB port problems

I recently upgraded to Itunes 7.0.2, and have been trying to get it to work with my 60GB Ipod Photo. With Itunes 6, I could connect my Ipod via USB with no problems. With Itunes 7, my Ipod will connect perfectly fine. When I attempt to update my Ipod, though, it will sync a couple songs and then say that my Ipod is corrupted. I forget the exact error message, but the gist of it is that Itunes won't write to the Ipod because it thinks it is corrupted. Syncing through Firewire works perfectly fine, though. Firewire is a pain for me, so I would like to get my USB connection working again.
I am running WindowsXP with Itunes 7.0.2 and using USB 2.0. Any help you can give me on this would be greatly appreciated.

I'll post my solution in the hope that this helps others. Tech support for Ipod is apparently non-existent.
1. Uninstall iTunes. Completely. This means deleting temporary files and any windows installation files. Also, ensure that there is no iTunes related registry values.
2. Connect your Ipod, go to the disk drive icon corresponding to your Ipod, and right click. Select Properties.
3. On the hardware tab, select the Apple Ipod option and press the Properties button.
4. Select the "Optimize for Performance." option. Hit the Apply and OK buttons until you've gotten out of the dialogues.
5. Restart the computer! This means turn it off! Do not just hit the restart button! Then re-install iTunes.
Although I doubt Apple reads this stuff, this will be my last Apple product that I buy. I find their lack of software support appalling. On top of that, they seem to only produce buggy software and unstable hardware. For $300 I expected something a little better.

GPIB-USB-HS//how to use in VC++?

I have a GPIB-USB-HS,and want to use in VC++ with windows xp.
question: I do not fine that are .h /.dll/.lib file.and who can give me??
email;[email protected]
thanks

Hi again,
As you can see in the image included, I think I´m doing something wrong in the simulation.
First of all I have included the NI USB-6001 device, but an exclamation icon apeared --> ¿Is this correct?
Then I simulate with the "Test panel" an analog signal in the first channel "Dev1/ai0".
At least, I extract "DAQmx Global Channel" from this first signal (Dev1/ai0), and taken to a string visualizator.
I think It should be very simple to manage this variables... Would you mind to help me again?
Thank you.
Attachments:
Chanel1.PNG ‏43 KB

[N85] USB charging problem

Hello all,
I tried to charge my N85 with an [non-Nokia] USB battery charger (Lenovo 90W Slim AC/DC Combo Adapter) via the Nokia Connectivity Cable (CA-101) to keep down the amount of chargers I have to carry.
But except of asking, which data connection profile I want to use, there is no charging at all.
Am I doing something wrong or is the N85 only chargeable by the original Nokia wall charger?
Thank you
sicut

30-Nov-2008 09:35 PM
rbreton74 wrote:
@sapporaby: Are you sure you have read my post completely? "Apple" is a brand o usb charger that does not work with my Nokia N85. It's a brand like "Kensington", with a usb charger that do work. Both usb charger worked with my old Nokia N95. I just want to know whether someone else has this problem usb charging problems too or if only my problem, and to make know @sicut that he is not the only one with usb charging problems with his Nokia N85 and his Lenovo charger.
@sapporaby, is it "apple" a word taboo for you? Why "kensington" is not taboo? Why "lenovo" is not taboo either?
1. I have had every Mac made since 2003.
2. I am typing this on a Mac now.
3. I have had and still have every iPhone made.
4. Same with every brand iPod.
5. I am running Apple software right now and the Nokia for Mac software.
Is that taboo enough for you? DON'T ASSUME because now your taboo question is moot.
As for your the Apple charger does not work issue, my question still stands. While your Apple charger may have worked with your N95 there is no reason why it should work with your N85. Are they the same phone?. Is the N85 made by Apple? No again. Does the Apple charger supply the same charging voltage as the Nokia charger that came with the phone? These are issues that come into play. What is so hard to use the cable that came with the phone. It seems, and maybe I am wrong but you and the OP are making a mountain out of a moe-hill.
Just use the cable that came with the phone, in the USB port of your computer and be done with it. I am having a very hard time trying to understand what the problem is with using the cable.
Message Edited by sapporobaby on 30-Nov-2008 10:07 PM
Show the KUDOS button some love.... Hit that bad boy.... It don't hurt....
Apple iPhone 5,
Retina MacBook Pro, iPad Mini, Nikon D4

Can't see boards in a VXI chassis connected via VXI-MXI-2 cards using a GPIB-USB adapter

I'm working on a system that has two VXI enclosures, and the two are bridged via VXI-MXI-2 boards in each of them. The first one has a GPIB-VXI board in slot 0, and I have a Winodows XP computer connected to that with a GPIB-USB-HS adapter. The problem is that I cannot see any of the boards in the second chassis over GPIB in the Measurement & Automation Explorer. As far as I can tell, everything is configured correctly; the VXI-MXI-2 board in the first chassis is in the last slot and has a logical address of 126, and the VXI-MXI-2 board in the second chassis is in slot 0 and has a logical address of 127. To make things even more confusing, if I put a VXI PC in slot 0 of the first chassis, it seems to see everything without any problems. Do you have any idea why this might be happening? I'm pretty new to working with these systems, so I might be missing something obvious. Thanks in advance.

Nevermind that -- I just discovered that you can't bridge two VXI chassis with VXI-MXI-2 boards if you're using a GPIB-VXI board as the controller. So, I'll just have to find another way to accomplish what I need to do.

MAX does not see PCMCIA-GPIB or GPIB-USB-B

I am using a legacy Windows XP SP3 system with MAX 3.1 and NI-488.2 V2.1. I use either a PCMCIA-GPIB card or a GPIB-USB-B.
When logged into an administrator account there are no problems; both devices appear in MAX and in the WIndows device manager.
When logged into a user account with limited privileges, the devices appear in the WIndows device manager, but not in MAX, but the VIs and compiled EXEs I user still operate correctly. However, if I convert the user account to an admin account the devices are visible, but this is not a solution because 'Security'.
The problem lies within the compiled EXEs as their respective VIs have been lost over time and the address of the PCMCIA or USB interface are hardcoded, and are not the same in all EXEs. I would appreciate any insight you may have.
Solved!
Go to Solution.

Hi Maelmorde,
If some features aren't working for users with reduced privileges you may need to grant them privileges to the National Instruments installation directory, the method is detailed in the KB article here.
I'd recommend trying this to see if it helps.
Regards,
Adam Brown
Applications Engineer
National Instruments UK

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)

GPIB-USB-A-- NI488.2 2.0

Installing a GPIB-USB-A, installs okay and the NI 488.2 2.0 software
installs
okay. The NI488.2
"Add GPIB Hardware" and
"Getting Started Wizard" both find and detect the GPIB-USB-A hardware and
it
passes the tests.
But MAX does not find it or recognize it in the "Devices and Interfaces:
Section of MAX.
Refresh does not find it either.
OS: Windows XP Professinal
This is on a new DELL 8250 computer with 2 USB ports on back and two on
front.
I have it plugged into one of the front USB ports. Could that be a problem?
NI Software : LabVIEW version 6.1
NI Hardware : GPIB/IEEE 488 device GPIB-USB-A
Driver Version : NI 488.2 2.0
OS :Windows XP
CPU :2.4 GHz
RAM :512 MB
Vendor : DELL

Hi,
Try this: go to Tools >> Install Legacy Driver Support. This seems strange but it should update the installed drivers. If this fails, there are some good suggestins at this thread:
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=506500000008000000D8520000&ECategory=LabVIEW.LabVIEW+General
Hope this helps out! Let me know if this works for you.
Best Regards,
Aaron K.
Application Engineer
National Instruments

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

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.

Does GPIB-USB-B controller not recognize device Aliases in Instrument I/O Asst express VI ?

Hi everyone,
I'm currently having problems with my device. I'm trying to communicate with the instrument simulator through the Instrument I/O express VI but the device alias I designated wasn't being recognized. After selecting the Alias from the pulldown menu and tried the "query and parse" command, there was no response. The "write" and the "read" commands also did not work. I'm suspecting that the problem is from my GPIB-USB controller card. I have the GPIB-USB-B controller. It recognizes only the instrument descriptor but not the alias. My NI 488.2 is of the 2.46 version and NI VISA is v4.2. I think everthing was configured correctly but the card might be the problem. Does anyone know how to fix this problem?. Is there some kind of driver upgrade that could help rectify it.
Thanks

Aliases have nothing to do with GPIB controllers and their software though if you cannot communicate to the instrument in MAX, then there might be problem with either one. Aliases are part of VISA. You can try upgrading to 4.5. Also search your entire pc for a file called visaconf.ini. Post back with the location and whether you found more than one instance. You can also try deleting the file and then go into MAX and do a refresh. You will have to recreate all aliases.
I am confused about something. Are you saying that if you use something like GPIB0::address::INSTR, communication works just fine but the exact same command with an alias does not work? If that's the case, there is nothing wrong with the GPIB controller. If that is not what you mean, then what does it mean when you say 'it only the instrument descriptor'? Another test of the gPIB controller is to use MAX to communicate with the instrument. Do not select VISA for communication. Just right click on it in MAX. This does not use VISA at all and if it works, then the controller and software are just fine.

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.

Booting os from External usb hd problem

First i tried firewire, i found the partitions and could make new ones, but when i started to copy windows files the instalation refused to go on. Ok so i tried the usb port, i could now copy all the windows files, the pc rebooted and the xp logo was turning up as it supose to but right when the main instalation was supose to start i get a nice bluescreen instead, telling me my hard disk is corrupt, that is not true, checked it sevral times, tried to reinstall only to have the same problem again (also went into bios and tried diff settings with the usb hardisk boot etc)
Im positiv that this should work, im so close but what im i missing to get to install my xp on external usb hardisk controller?
i use kn8 platinium with all the newest drivers and bios flash.
Thankful for any sugestion or reply!!
Edit: i want i dual boot as i run xp on my internal hardisk.

But i should work, heard many that pulled this off.Ii think that if you could have a portable bootable external hardisk, it would be perfect for bringing home the exact system from work (when you have similar or exact same specs on your pc). Well no matter what my reasons should be i want to pull this off
And i dont think Xp is the problem, the last thing i tried was setting the usb disk active from managment, but that didnt work either. If anyone have any info at all i would gladly take it.

Can I use a USB hub to connect to multiple USB ports from one GPIB-USB-HS?

I have one instrument which has a GPIB-USB-HS connected and the USB cable is connected to a USB hub. Can I have multiple PCs to connect using USB hub at their respective USB ports? If so, how many PCs can I connect using the USB cable?
I have downloaded the latest NI-VISA from the website.
Solved!
Go to Solution.

You would first need a hub that allows you to switch between multiple pc's and then only one pc at a time would be connected and in control.
When you buy this special type of hub, one of the specs is how many pc connections it has.

Obsolete GPIB-USB-A problem again

Similar Messages

Maybe you are looking for