LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Question on creating a driver


@JohnCS wrote:

You can download a LabVIEW Instrument Driver for Keithley model 192 from the NI Instrument Driver Network.  It may not suit all your needs but combined with the 181 manual that Jeff Bohrer found for you, it can be a jumping off point in your development. At the least it will show you how Keithley does their messaging. There are many other drivers there that you can look at for inspiration.

 

There's a model 181driver in the collection as well but it is a LabWindowsCVI and can be converted to LabVIEW. You can try the LabVIEW Instrument Driver Import Wizard. Or, if you have a copy of LabWindows/CVI you can follow the procedure in the tutorial: "Conversion of an Instrument Driver from LabWindows/CVI to LabVIEW." 

 

JohnCS


John, the 181 CVI driver hasn't been updated since 1994- Its not up to standards for import and the OP does not have CVI.  

 

Tell you what- I'm baching it this weekend with Mrs Bohrer out of town  I'll whip up a PnP Project for the 181 on spec and backsave to 8.5 if the OP will test and submit to the IDN.  the command set is pretty basic.  But the GPIB options (Unaddressing etc) will need to be set and tested since the device is so uhmmmm.. dated, ancient, is there a PC way to say it?

 

Lars- are you game?

 

 


"Should be" isn't "Is" -Jay
Message 11 of 19
(1,047 Views)

Ive seen the labwindows driver for the keithley 181 and tried to convert it to labview, but it does not work.  There is a problem with the .fp file.

0 Kudos
Message 12 of 19
(1,043 Views)

And Jeff, that sounds good to me

0 Kudos
Message 13 of 19
(1,042 Views)

Though I won't be able to test it until Monday

Message 14 of 19
(1,032 Views)

 


@LarsUlrich wrote:

Though I won't be able to test it until Monday


No problem!  But well have to teach you how to kudoSmiley Very Happy


"Should be" isn't "Is" -Jay
Message 15 of 19
(1,026 Views)

I suspected that the 181 driver may have some issues due to its age.  I have all the tools so I converted it anyway. It only has a few of the functions implemented as DLL calls.  Set zero, filter, resolution and damping are missing from the configuration VI.. They are included in the C code and may be accessible from the DLL. Definitely not up to today's standards!  I don't think it will be much use in developing an up to date PnP driver but here it is anyway.

 

JohnCS

 

 

 

Message 16 of 19
(1,020 Views)
Sorry the Internet went down at the office and I couldn't respond.
That is fine about the missing functions, as long as it has the high res function it will work for me.
I'll check those out when I get the chance, thanks for all your help
0 Kudos
Message 17 of 19
(1,011 Views)

Status update:

 

I wound up busier than I expected this weekend.  I should have the project to you Tuesday


"Should be" isn't "Is" -Jay
0 Kudos
Message 18 of 19
(975 Views)

I didn't clean up the .mnu files but this should get you started down the right path

 


"Should be" isn't "Is" -Jay
Message 19 of 19
(962 Views)