From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

problems with LabView drivers for Keithley 236

Hello, I have illegal device dependent command option (iddco error) for all examples from ke236.lib I use Labview 5.11(GPIB interface). What is strange that after modification(just added unbundle by name for output parameters), two examples for dc-mode started to work, without error. Now situation is that if I start my modified example first, another official examples also work, if I start first official example, keithley 236 returns error and my modified example does not work too. In sweep mode I have always IDDCO error.
Can anyone help me, please?
0 Kudos
Message 1 of 4
(2,807 Views)
Malchik,

Probably what is happening is that the instrument driver was built with a different version of the GPIB driver than what you are using. When you add something to the driver, it causes it to recompile and relink to the newer functions for GPIB. Here is what I suggest: Open up the examples and press ++LabVIEW Run Arrow. This will force a recompile and link of all VIs in that VIs hierarchy. Then choose to Save All from the File menu. Now run the examples and check if they work. If they do not, can you open the lower level VIs to see whcih function is giving you the error and where? That is the next step.

Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask
0 Kudos
Message 2 of 4
(2,807 Views)
Ok, thank you. I tried ++LabVIEW Run Arrow and Save all, but it does not help, I still have the mistake. The mistake occurs when the subVI "Send Message" runs the command "GPIB write" with parameter: "F0,000P0Z0S1W1B2,000000E+0,0,0L1,000000E-1,0XM),XM8,X"
Please advise me,
Malchik
0 Kudos
Message 3 of 4
(2,807 Views)
Malchik,

Since this is turning into much more of a GPIB programming issue, I would suggest reposting this question (with what you have learned) in the GPIB forum instead of the LabVIEW forum. Not all of the GPIB specialists monitor the LabVIEW forum here and they would be much better at handling this programming issue.

Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask
0 Kudos
Message 4 of 4
(2,807 Views)