LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

visa timeout error keithley 2000


@RTSLVU wrote:

 

Maybe the driver package for the Keithley 2000 should be fixed at the NI website? I mean, when I use an "official" llb from NI, I would expect that it works without such hidden traps...?

 


Well... Yes and no. 

 

I believe that "NI Certified" only means the driver package conforms to NI standards for creating an instrument driver. It does not mean the driver works in every possible instance or configuration.

 

You have to remember that most of the drivers available on the Instrument Driver Network were written by users or the instrument manufacturer.

 

I have seen some of the absolute worst examples of LV programming in instrument drivers supplied by the manufacturer of the instrument. Obviously some manufacturers either higher a contractor  who does not fully understand the instrument or task one of their C programmers who does not understand proper  LV programing techniques to just throw together an LV driver just so they can say they have LV support.


AMEN brother! Preach on! Preach on!

 

Mike....

 

PS: Sorry, I just got carried away...


Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 11 of 14
(649 Views)

@mikeporter wrote:

@RTSLVU wrote:

 

Maybe the driver package for the Keithley 2000 should be fixed at the NI website? I mean, when I use an "official" llb from NI, I would expect that it works without such hidden traps...?

 


Well... Yes and no. 

 

I believe that "NI Certified" only means the driver package conforms to NI standards for creating an instrument driver. It does not mean the driver works in every possible instance or configuration.

 

You have to remember that most of the drivers available on the Instrument Driver Network were written by users or the instrument manufacturer.

 

I have seen some of the absolute worst examples of LV programming in instrument drivers supplied by the manufacturer of the instrument. Obviously some manufacturers either higher a contractor  who does not fully understand the instrument or task one of their C programmers who does not understand proper  LV programing techniques to just throw together an LV driver just so they can say they have LV support.


AMEN brother! Preach on! Preach on!

 

Mike....

 

PS: Sorry, I just got carried away...


Which is why I almost always write my own driver for an instrument I must use.  Not to mention the fact that there is way more happening in that VI than I would have bothered with.  Just need a read command and be done with it.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Message 12 of 14
(648 Views)

yep, lazy people (like me) work twice: if i made my own subVIs, it would be ready and running by now 🙂

But to stay lazy, I think I will try to capture and handle the error, and in this case just to reinitialize the Keithleys...I guess it should work, dirty but quick as it was suggested above...

Thanks, and regards,

0 Kudos
Message 13 of 14
(639 Views)

hello,

 

FYI, I have swapped the mentioned two VISA VIs in the subVI, but I got error over the weekend again. So it did not help.

I just wrote an error handling subVI, which captures this error code, and re-initialize the Keithleys, also indicating on the display when and how many such error happened.

 

I also reported this bug toward NI, linking this post, they answered replying that they will look into this issue at the next planned update of the driver.

 

Regards!

0 Kudos
Message 14 of 14
(605 Views)