08-17-2007 04:35 PM
08-20-2007 12:05 PM
08-24-2007 01:35 PM
08-27-2007 04:49 PM
08-27-2007 05:08 PM
Chad,
You are totally right. A co-worker and I just found out the same thing. After agreeing that it would be better to have a single initialize and close, we worked pretty much through a trial and error method to find out what would work and what would not. We found out that if the keithley program is aborted in the middle of a program without undergoing the close function, it will pause on the the single data read vi until LabVIEW is closed and reopened. Strangely, the keithley DMM did not need to be power cycled.
We eventually decided that the best way to get around this error was to have the close vi at the beginning of the program prior to the initialize vi. This way, if the program was aborted it could still be run later because the first thing the program will do is close the keithley DMM. Now, while watching this program run with a close vi at the beginning I noticed that if the program runs uninterrupted, the second time through an error will crop up. Nothing fatal, it does not shut down the program or even show up with a simple error handler, but I think it comes from trying to close a device that was closed in the first place. Not really sure though.
Once this program is finished and packaged as an executable, the close vi at the beginning will be removed, but it is pretty necessary presently for debugging and testing purposes.
I think thats it, thanks for the help.
08-28-2007 09:11 AM
09-13-2010 09:58 AM
Good morning everybody
I am new in this forum and in Lab view and my task is to do an interface with this port.
After read lots of messages here, I remember that I installed NI 488,2 driver and It didnt work. So, I uninstall-ed NI488,2 and then Installed keithley driver(It is not possible to have both because they are conflictant) and installed another drive That a I have found in this forum(keithley 2000).
I made the device communicate with the Labview but I dont know what happened that in the next day that anything was working!
I am afraid that some actualization was installed when I restart the computer.
so, I will put in order every thing:
-installed all Lab view and drivers (including ni488,2)
-uninstalled ni driver and installed keithey interface to test the port comunication(that send me an asnwer of the device that can communicate with the port)
-installed labview-keithley driver for keithley 2000 multimeter, found on the forum´s topics.
-opened the single measure Vi example and it worked!
Next day:
-I installed other drivers for the other device I need to comunicate, the keithley 7002,and my programm stopped to comunicate or find gpib 11( the address of gpib)
-so, Unistalled these programs and It Worked again.
-I turned on my computer next day and It wasn't working again! it was unable to find the gpib correct address. I notice that in the max, the gpib changed automatically the address of the device to 10 (but the day earlier, was 11, the correct one and working)
-things tried: reinstall all drivers, delete all new programs I installed, turn firewall off.
I tried to configure another gpib but are so much addresses and I don´t know what to put in the fields.There isn't other way to detect automatically?
(F5 only dosnt work). I didnt need to configure in the first time.
thank you very much
Leandro V. Zaccarias
09-15-2010 11:01 AM
Hi Leandro,
If you are using an NI GPIB card in your computer, you will need the NI-488.2 drivers installed.
In addition, to communicate with the Keithley 2000 multimeter, it is easiest to use the drivers that Dennis linked here. You will install NI-488.2 first, and then the Keithley driver.
After doing so, there should be examples in the Keithley driver folder on your computer, and an additional LabVIEW Pallet for the Keithley 2000.
You should also be able to have drivers for the 7002 installed at the same time without a problem, but know that that driver is not supported or certified by NI.