Keithley 6430

Good Day,
Does anyone know how to use the instrument drivers of the above mentioned instrument?
I am currently trying to replace Keithley 236 Sourcemeter with Keithley 6430 sourcemeter. However,inside the LABview programme that i am using, I am experiencing difficulty in replacing the K 236's VIs with those of K 6430.
Any help would be greatly appreciated.
thanks

Hello,
Generally instrument drivers have the following major categories:
initialize/open, configure operation, perform measurement, utility functions, close
If you don't have a driver, then you'll need to program using an API which will interface your instrument; this requires that you have knowledge of the commands that the instrument understands; the instrument manual and the manufacturer are really the only place to obtain such information.  Many instruments respond to common commands, such as *idn?, *tst?, and *rst, (which perform an instrument query, self test, and reset respectively).  Usually a question mark being sent implies that the instrument will reply, which means you'll want to read after you write the command.
If you are only looking for a subset of the instrument's functionality, you should be able to program using an interface API (such as VISA) fairly easily.  Of course if you have the driver, that will be easier and faster.  Note that the above "major categories" are generally in the order in which they are called in a given program.
Feel free to repost if you have further questions, and we'll try to help you further!
Best Regards,
JLS
Best,
JLS
Sixclear

Similar Messages

  • LabVIEW 2012: keithley 6430 I-V curve

    Forum,
    This VI appears to work using the Keithley drivers in order to generate an I-V curve. However, it's slow, and it has "time out" problems.
    Using a start of -1.0V and stop of -1.0V and step size of 0.005V (401 points) will issue a "time out error". Increasing the "time out" value in the "Sweep Points" sub VI has helped in obtaining the data such that I can use near 201 points at the moment. Speed is still a problem. If anyone has any suggestions I'd love to hear them.
    Thanks!
    Attachments:
    keithley_6430_Rev2.vi ‏71 KB
    keithley_6430_Rev2_BlockDiagram.jpg ‏193 KB

    It might be useful to see which sub VIs are causing the performance issues.  You can always use LabVIEW's Performance and Memory management tool to help you out.  http://www.ni.com/white-paper/3576/en
    Jesse S.
    Applications Engineer
    National Instruments

  • I need GPIB Driver for Keithley 263 Calibrator/Source Meter using Labview. Can anybody help? Thank you.

    I need GPIB Driver for Keithley 263 Calibrator/Source Meter using Labview. Can anybody help?
    Thank you in advance.

    Hi,
    on Keithley's website is explained :
    "The Model 263 offers a more economical, more precise alternative to the Model 6430 or the Model 236 when used as a low-current source. It is used almost exclusively as a current calibrator."
    This leads to Model 236.... A LabVIEW-driver is available @: http://search.ni.com/query.html?lk=1&col=alldocs&nh=500&rf=3&ql=&pw=595&qp=%2BContentType%3AInstrumentDriver+%2BIDNetManufacturer%3A%22Keithley%22&qt=&layout=IDNet
    Maybe you have to "reconstruct" some parts - but it will help.
    regards
    wha

  • In need of a KEITHLEY 2001 single read .vi that is compatible with LabVIEW 7

    I am updating from LabVIEW 5.1.1 to 7. The KEITHLEY 2001 Single Read .vi has coercion errors, and does not function. Where can I get updated KEITHLEY 2001 .vi's that are compatible with LabVIEW 7?

    You can visit http://ni.com/idnet/, click the "Search Drivers" button
    and select "Keithley" as the manufacturer and hit the "Go" button.
    Look down the list, and you'll find the LabVIEW Certified Plug and
    Play driver for this multimeter scanner.
    I hope this helps.
    Brian

  • Errors in Keithley 237 sourcemeter GPIB drivers

    I've just gotten back to working with our KE237 sourcemeter. I just discovered a couple of new bugs in the LV drivers posted here and at Keithley. It's a pretty unique old instrument, and we're lucky that they still make it, but it has some rough edges. The drivers are a free download, so when we find bugs, the best we can do is tell Keithley and share what we know. Caveat emptor. Beats starting from scratch.
    In the Keith 237 Basic Config vi, The enumerated type control for integration time has the text for 60 hz line cycle, and 50 hz backwards. This is hard to spot, since the instrument only displays "LINE CYCLE INTEGRATION" on the front panel once this has been programmed. Happened to look at the actual string going out to the instrument and noticed it.
    Easy to fix, just change the enum text labels for selection #2 to read 60HZ, and #3 to read 50HZ. So, if you've noticed that your instrument seems noisier running under Labview, this might be why. 
    While I'm at it, I also found a non-optimum feature of the SMU Device Errors query vi. It will overwrite any upstream error messages in the LV error cluster. For instance, if you call it twice along the communication chain connected by the error cluster, if it finds an illegal instruction error in the instrument in the first call, since the first call cleared the error condition in the unit, the later call sees nothing wrong and wipes the error cluster clean, even though the unit wasn't successfully configured. i sprinkle these error queries through my apps pretty liberally.
    Easy fix is to add an outer case structure around what's already there to simply pass through upstream errors with no new action taken. 

    Hi Bill,
    Thanks for bringing this to our attention, it's great to have these workarounds online where they can help other users!
    As you suggested, the best way to get these changes implemented is to contact Keithley directly. Because NI doesn't make these drivers, we can't modify them ourselves.
    Thank you,
    Emily C
    Applications Engineer
    National Instruments

  • Why does the integratio​n time setting of Keithley 2000 (number of PLC) changes to medium (1PLC) from fast (10 PLC) and slow (0.1 PLC) settings, when I tried to read from Keithley?

    Dear All,
    I am trying to change the NPLC (the integration time) of Keithley 2000 and take voltage readings. Whenever I change the settings to fast or slow and then run the VI, the NPLC changes to medium. Could you kindly tell me what is causing this? Thank you and I look forward to receiving your replies.
    Regards

    For the NPLC setting, the higher the number, the longer it takes to get a reading.  So 10 PLC is much slower than 0.1 PLC. 
    See if you can set the NPLC setting from the front panel.  Then try changing the vi to set NPLC only, then read it back to see if it matches your setting.  Sometimes changing ranges will automatically set the NPLC depending on the range chosen.  So you have to send the range command before sending the NPLC command.  This may be what is happening.
    - tbob
    Inventor of the WORM Global

  • Keithley 2000 DMM AC Read Overflow

    I’ve been having problems controlling a Keithley 2000 DMM during AC volts measurement using IVI. When reading AC Volts the DMM will intermittently sense an ‘overflow’ and return the value NaN. I’m using IVI and TestStand 3.0 but get the same problem with IVI and LabWindows 7.0.
    The set-up is as follows:
    Device: Keithley 2000 DMM, GPIB device number 6
    Device interface: GPIB, DMM set-up in MAX as GIPB0::6::INSTR
    IVI Driver version: 3.02, downloaded from the NI web site
    IVI Compliance Package version: 2.1
    NI-488.2 version: 1.70
    NI-DAQ version: 7.1.0f1
    MAX version: 3.0.2.3005
    For test purposes I’ve connected the DMM front panel input high and low and set the inputs mode on the Keithley to front, this should mean that I get a very low Voltage reading. I’ve then run the LabWindows/CVI IVI control sample code provided with the IVI driver. At the initialisation panel I’ve entered the logical name. At the configuration panel I’ve selected Volt AC measurement but left everything else as default. The second configuration panel I’ve left as default. At the Read panel I’ve left all setting as default. Pressing the read button up to about 20 times with about a second gap in between each press will eventually lead to an ‘overflow’ reading.
    Any help/explantion will be appreciated
    Steve

    Here are the results of my investigation into this problem, it’s two fold:
    1. Keithley have informed me that their engineers in the US have just seen the problem I’ve been seeing and are working on a firmware update. Currently here is no date for the release of the updated firmware but I’ll be informed when this it’s ready.
    Note: I’ve found that the read AC Volts overflow problem only occurs when the read trigger delay is set to zero seconds.
    2. The TestStand DMM IVI configuration step always sends a trigger delay of zero seconds regardless of the trigger delay set.
    In my TestStand sequence the DMM IVI configuration sets the read trigger delay to 3 seconds but as noted above this is sent a zero seconds thus invoking the Keithley DMM AC Volts read overflow problem.
    See attached VISA call log captured by NI Spy. The first 22 call are made when the DMM IVI configuration step is called form TestStand the next 22 calls are made by the IVI DMM sample code configuration provided by National Instruments when DMM configuration is run thorough LabWindows. Note call 12 (IVI DMM TestStand) has the trigger delay set to zero seconds (should be 3 seconds) and call 34 (IVI DMM LabWindows) has a delay of three seconds.
    I’ve found a workaround as follows:
    After each call to the TestStand DMM IVI configuration step an additional step that calls the TestStand IVI Tools step can be added. The IVI Tools step can be set-up to specifically configure the DMM Trigger Delay to 3 seconds. I’ve proven that this individual call does in fact send the correct trigger delay command to the DMM thus alleviating the AC Volts read overflow problem.
    Can NI confirm that this problem does exist with the DMM IVI step and when they plan to fix it. I’ve attached the TestStand sequence file that I’ve been using to investigate the problem.
    Thanks
    Steve
    Attachments:
    DMM Overflow.zip ‏9 KB

  • How can I use my Keithley 2100 DMM with LabVIEW 7 Express?

    How can I communicate with Keithley 2100 digital multimeter using LabVIEW 7.0?

    Hi,
    There are a number of ways,
    1) Unfortunately the driver on the Keithley site is for labview version 8.0, so you could speak to keithley to see if they can provide a ver7.0 of the instrument driver
    2) You could use the version for the 2000 model from the NI website
    http://sine.ni.com/apps/utf8/niid_web_display.down​load_page?p_id_guid=E3B19B3E90B0659CE034080020E748​...
    There is a version 7.0 which you could modify to suit the 2100
    3) Use the VISA vi's and create your own driver using the user manual for the bus commands to driver the instrument.
    Hope this helps
    Regards
    Ray Farmer
    Regards
    Ray Farmer

  • When I read from a Keithley 2612, I lose 3 numbers of precsion

    Hello,
    When I read from a Keithley 2612, I lose 3 numbers of precsion.  When I connect a probe to the Keithley driver output I can see a current measurement of 0.000005051 uA.  This output is wire to a "Merge Signalsbox" and then to a "Write LabVIEW Measurement File". But when I look in the excel file there is only 0.000005 uA.  Does anyone know how I can get all of the digits into the excel file?  I am using LabVIEW 8.2.1.
    Thanks,
    Gary

    Hi Gary,
    Are you using any other VI's in this application?  Are you using the write to measurement file to write to a TDM file and then passing that to Excel?  If you probe the input to the write to measurement VI is the data truncated?  LabVIEW usually converts to scientific notation.  Do you have your data formatted to not use scientific notation?  Also, you may want to check the significant digits setting in Excel, as it may be cutting off your data.
    Nick Keel
    Product Manager - NI VeriStand and Model Interface Toolkit
    National Instruments

  • Velocidad del amperímetr​o Keithley 6485

    Buenas,
    Por el momento estoy haciendo adquisiciones de un amperímetro Keithley 6485, el problema que he encontrado es la velocidad de adquisición, según el manual, FAST es igual a 0.1 PLC (Power Line Cycles) pero realmente no es nada rápido, he visto los tiempos de adquisición del mismo amperímetro 10 veces mas rápido de lo que se hace mi adquisición. Realmente no comprendo por qué, claramente esta escrito FAST en mi programa, adjunto una imagen.
    Gracias por sus respuestas.
    Adjuntos:
    Acquisition.JPG ‏21 KB

    Buenas tardes Ivan,
    Perdona mi Castillan, no sé porque esta pregunta ha caido en mi mailbox, porqué soy un ingeniero de NI France...
    Me voy a intentar :
    Usted ha descargado esto driver ?
    En el manual, qué significa FAST ? la velocidad maximum ?
    Cuando has visto una granda velocidad ? tanbien con LabVIEW ?
    Puedes usar esta tecnica per saber su velocidad :
    Se puede ablar tanbien inglès o francès se quiere.
    Mathieu_T
    Certified LabVIEW Developer
    Certified TestStand Developer
    National Instruments France
    #adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
    LabVIEW Tour
    Journées Techniques dans 10 villes en France, du 4 au 20 novembre 2014

  • Keithley to excel interfacing problem ..Please help ! !

       I am currently doing project on scanning the resistance from a keithley 2700 DMM for reliability testing of thermistors.
    I got the resistance value using single measurement VI.
    But what i need is everytime i invoke the keithley scan based on a counter signal ,it should give the resistance value.
    And all these values should get saved in an excel file one after the other along with the cycle number.
    The problem i encountered is that ,"after the trigger pulse is given to keithley 2700, it gives the output only after 5 seconds. So i am not able to interface the  keithley with the table and i am not able to get the previous values."
    I am attaching my current VI. Here i got the 2 required outputs, but i could not import them into excel one after the other.
    Please help me.
    NB: here i have considered a latched boolean switch as my counter signal.
    Regards
    Grugh Mike
    Success is Everything !!
    Attachments:
    gurgh.vi ‏170 KB

    No worries. The best way to learn is to just take a look at examples. You might not know exactly why the examples are the way they are, but it will still help a lot. When I look at the ni.com/idnet page for your DMM, I get this driver:
    http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=0470C9F181C02E75E0440003BA7CCD...
    This driver includes an examples folder--take a look through it, and especially look at "Keithley 27XX Continuous Multi Read". I think that may do what you need, or at least a lot of it.
    As to the examples, look at those links in my last post. If they don't do what you want them do, check ni.com/community and see if you can find something similar. It really comes down to how much information you need to store.
    Thanks,
    D Smith

  • Can you control the display on a Keithley 2400?

    I have created a VI to control a Keithley 2400, but the enduser also wants to see results posted on the actual device.  Is this possible?

    Hi dt 1804,
    Thanks for the post and I hope your well today!
    I just had a read through the commands (from keithley website) and I couldnt spot anything that would display results - so I guess not. Unless there is some manual option..but Im afraid I wasnt up for reading the massive manual!
    Surely if your using LabVIEW there isn't much point seeing the data on the device...
    Kind Regards, 
    Kind Regards
    James Hillman
    Applications Engineer 2008 to 2009 National Instruments UK & Ireland
    Loughborough University UK - 2006 to 2011
    Remember Kudos those who help!

  • Expression Error (#:-1074001424) with Keithley 2000 DMM

    I wrote a program to that uses the Keithley DMM to check voltages on multiple channels, wait a period of time, and then check again. This cycle continues for the time specified.  I made this program on one laptop and it worked fine.  When I moved it over to a different laptop and a different Keithley DMM, then I started to see this issue.
    After stepping thru the program, It seems that the error comes from the "Configure Scan.vi".  The exact error message is:
    <ERR> ke2000 Error Query;
    instrument reports:
    -260,"Expression error"
    and the error code is: -1074001424.
    I searched for these myself and couldnt find anything helpful.  i changed a few things around and it seems that the "scan mode" parameter seems to be the problem.  It needs to be set to "internal" to read the channels on the additional scan card, but the program will return an error if it is not set to "none"... and when its set to "none" nothing happens.
    Please help me out! Thanks

    Nvm.... fixed it.  For the Configure Scan.vi, in some cases, one of the parameters, "Stop Channel", would be set to 1, when the starting channel was, by default, set to 1. Apparently this caused a conflict of some kind but I changed my program around so this doesnt happen anymore.

  • Programmed vs measured voltage on Keithley 2400 and other things

    Hello everyone,
    I have two issues with our Keithley 2400, which we control through Labview, and I would be very grateful for some help/advice. The issues are listed below:
    1) We use the 2400 for 4-point probe measurements, so we plot graphs of current vs voltage to get the resistance from the slope of the curve. However, when we look up the data generated during a measurement, the voltage sweep values that we program often, but not always, do not match the measured voltage values. For example, what was meant to be 1 V, might actually end up being 1.2 V or maybe 0.8 V, this can be both positive and negative with respect to the programmed values and is not constant. This also leads to the fact that our curves, although straight (so Ohmic conductor), do not go through the (0, 0) point on the graph.
    2) Second problem is that we would like to determine what is the time between successive measurements in a voltage sweep. We have tried some example vi files that by default come with the Labview, e.g. Keithley 24XX Read Multiple - SW Trigger or Keithley 24XX Read Multiple. If someone knew how to find the time separation, then we would be grateful. We only have control over the number of invididual readings taken and the timeout, which we guess is the maximum time allowed for the measurement.
    Many thanks!

    Good Afternoon PiotrW,
    1. Could you please provide the code you are using to program the voltage sweeps? 
    2. You could use the timestamp output of the Keithley 24XX.lvlib:Read (Multiple Points).vi to allow you to find the time difference between successive samples. It should be a simple case of subtracting succesive measurements from each other to find the time difference between data points.
    Regards,
    Al 
    Regards,
    Al C
    National Instruments,
    Application Engineer

  • Convert Keithley 2400 Driver for Labview 8

    Hello. I need someone to convert the Keithley Driver (labview 5.1) for me to use in labview 8.6. I can only use the earlier version of the driver since my program was written based on this driver.
    Thank you in advance.
    Attachments:
    Ke24xx.LLB ‏3508 KB

    There you are...
    Best regards
    chris
    CL(A)Dly bending G-Force with LabVIEW
    famous last words: "oh my god, it is full of stars!"
    Attachments:
    Ke24xx_8.5.1.zip ‏884 KB

Maybe you are looking for