Instrument Control (GPIB, Serial, VISA, IVI)

Showing results for 
Search instead for 
Did you mean: 

communication test labview with Keithley2612 (GPIB)



I try to drive a 2612 Keithley SMU by Labview (2018, 32 bits). I have Windows 7, and the GPIB interface is KUSB-488B (driver installed).

I passed all the communications tests with Keithley Diagnistics Tools, NI MAX... (see pictures below).

But I failed to drive a query with using Labview.


May someone help me please to solve such an issue? I do not know what is wrong? Where is the issue?


Thank you. Kind Regards,



comm Keithley.jpg

comm NI Max.jpg

query comm labview.jpg


0 Kudos
Message 1 of 4

Make sure NI-MAX and KI-488 test panels are closed when you try to connect via LabVIEW?


What version of the K26xx driver are you using?  Where did you download it from?

Most recent is -


Try RESET, without ID QUERY, then repeat with ID QUERY.  Does that work? 



0 Kudos
Message 2 of 4

I found a functional path if I put "False" the ID Query and Reset in the Initialize VI.

Does it seem correct to you?

Thank you for you help.

Kind regards.

0 Kudos
Message 3 of 4

The ID Query is not necessary, but can be useful if you have 30 instruments and need to very the 2612 is at the expected address. 


Is this a new or an old Keithley 2612?  The ID query just reads a string from the instrument in response to the *IDN? command and compares it to a list of expected strings.  If the response is in the list then it must be the right instrument.  See image below.





For some reason your SMU isn't returning a string the recognizes as belonging to a K2612.  Perhaps its because its a really new instrument and the K2612A should be a K2612B or K2612C??  Or its a really old instrument and they firmware omitted the "A".  You could easily debug the ID Query by watching the returned string with Execution debugging on and then making your own to accomodate the string your instrument is returning. 


Another option might be to update your firmware.  Perhaps you have a very old instrument and all the more recent LabVIEW code was written for more recent firmware versions and the response string to the *IDN? command has been updated.


If you solve the issue post it here and you could report the bug to Keithley to fix too!


0 Kudos
Message 4 of 4