Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

IDDCO Error on Kethley 237 with LabView

Hello everybody!

I have a problem ith the manipulation through LabView of my Keithley 237. I made a LabView program on the computer in which I have LabView installed (LabvView 8). I tested the program while developing it on my Keithley 237. It communicated with the PC  through a National Instruments GPIB-PCI Card. Everything worked erfect and fine. Then I created an installable file so that I could run this program on another computer without LabView. I then connected my Keithley 237 with a LPCI-3488A Card from ADLINK Technology.

Now, though I'm able to run the program succesfully (there is indeed a connection between the computer and the Keithley 237), but however I keep getting the error IDDCO on my device. That means that I'm sending wrong commands to the Keithley, but they are the same commands that I used on the other computer! (It is important to say that I did not write any of this commands by myself, as I used the SubVI that are on the Keithley website.).

What can I do? I think this has to do with the change of the card but I do not really have an answer 😞

I saw in another thread that maybe the version of the ADLINK Card was to new, so I downgraded the driver version but had no effect whatsoever.

I would frankly appreciate your help.

Greetings,

Luis.

0 Kudos
Message 1 of 6
(4,265 Views)

Seems like this is more a question you should be asking Adlink. Since you did not include the code, impossible to say if what you are sending is correct or not.

 

Obviously, the only way communication can work with LabVIEW is if you are using VISA so you must have the Adlink VISA driver installed as well as NI-VISA and have tulip support enabled.

0 Kudos
Message 2 of 6
(4,262 Views)

Now, though I'm able to run the program succesfully (there is indeed a connection between the computer and the Keithley 237), but however I keep getting the error IDDCO on my device. That means that I'm sending wrong commands to the Keithley, but they are the same commands that I used on the other computer! (It is important to say that I did not write any of this commands by myself, as I used the SubVI that are on the Keithley website.)

 


 

Its important to note that the IDDCO indicates that the instrument recognized the command but the numeric parameter is invalid.  (Illegal Device Dependant Command Option).  One easy way to get this is to happen is to have a inconsistancy in the term char sent and the term char that the instrument is progremmed to expect- (since the command isnt terminated the parameter cannot be evaluated)

 

Check your GPIB settings!

 

 


"Should be" isn't "Is" -Jay
0 Kudos
Message 3 of 6
(4,257 Views)

Thank you both for your help. I solved the problem, but not in the way that you mention. The only issue was that I made the LabvView program in a computer where the regional configuration was in English, and then installed the card in a computer with a German configuration. I guess that when the differente voltages and currents were sent the program expected a decimal point where a decimal comma was sent.

Thanks!

0 Kudos
Message 4 of 6
(4,231 Views)

Thanks for the update! 

<that's another one for the localization guys at Keithley>


"Should be" isn't "Is" -Jay
0 Kudos
Message 5 of 6
(4,224 Views)

In fact for the idiot default for a language meant for instruments.

I never found an instrument with a localised decimal point in the Netherlands but already found at least 20 programmers with this bug.

And we are only changing that default when installing LabVIEW for our customers.

 

So please America, leave the localised decimal point by default disabled......

greetings from the Netherlands
0 Kudos
Message 6 of 6
(4,214 Views)