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

Similar Messages

  • XYGraph Cursor legend bug instantly crashes LabView 2012

    Hi!
    I am just facing a very annoying bug.
    Please find my example VI attached, I would like to know wheather you can confirm the bug? Run the VI if you wish to see some curve (actually the bug appears even if you do not put any data on the graph, if you do, just the same) and after that try to click on the cursor legend vertical scrollbar to scroll up or down to see the cursor names.
    It instantly crashes my LabView 2012 Full version:  12.0.1f2 (32-bit). This XYGraph always crashes LabView... I cannot go on with my project, now I will just try to bypass the error, I will try to delete the cursors, and add them again...
    Anyhow, very strange and annoying behaviour...
    Anyone could repeat the same bug?
    Thanks for support!
    Solved!
    Go to Solution.
    Attachments:
    XYGraph_bug_test1.vi ‏149 KB

    hello,
    please find attached my example VI, where I would like to programmatically set the label position of a cursor. Why my code does create at every run a new cursor with the same name?
    thanks!
    Attachments:
    cursor_offset_label_via_propertynode.vi ‏12 KB

  • 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

  • Some fonts are not shown correctly in LabVIEW 2012

    I found a bug related with fonts in LabVIEW2012 f3 KR.
    - When I select NI7SEG in font selection dialog, right font is not shown in the example box.
    - Draw text at point.vi shows same problem for some fonts while other fonts are working.
    I reported it to Korean NI. As far as I know, this was not reported in previous versions and I couldn't find any related documents in Google. 
    So, here I would like to know whether it is related with only Korean version. Please let me know if English version is OK. 
    * OS: Windows 7 32bit KR

    Just now, I installed LabVIEW 2012 f3 (32-bit, English) and checked for the issue. But the font(NI7SEG) was not shown properly in VI either.
    - Both of Korea and English version of LabVIEW 2012 on Win 7 Korea OS shows wrong results. It is same on 64-bit OS.
    - LabVIEW 2010 but on same PC shows correct fonts.
    Is there a limit of number of fonts in LabVIEW? There are more than 100 fonts are shown in the "Selection Font" dialog and I can divide them into 3 groups by sequential order. I find that all fonts in the 3rd group are not applied correctly.
    (1st group)
    Arial Unicode MS...
    Bookshelf Symbol 3....
    Windings 3
    (2nd group)
    @Arial Unicode MS...
    @Terminal
    (3rd group)
    Arial...
    Consolas...
    Courier...  
    Licida Console... 
    NI7SEG...
    Verdana

  • Issues with windows 7 after Labview 2012 installation

    Hi
    I am having some issues after installing Labview 2012 on machines running Windows 7. Firstly, after installing a program on a user's machine, the machine sometimes takes 20 minutes to boot up before the user can log on. The 'Please Wait' message appears during this time. This is also the case on the development machine.
    Secondly, on the development machine, I am having an issue when trying to run compiled programs created in Labview. When installing, everything works fine but when I go to open the program, it appears on the task bar for a brief period before closing. It does not appear in the task manager either. I have tried this on 2 other machines with windows 7 and Labview installed and still get the same issue.
    Any help on these matters would be much appreciated. Thank you

    Hi
    Firstly, looking at the issue with the slow Windows 7 boot up time, as Norbert_B suggested the Windows Event Log is a good starting point to find the root of the problem. The following link describes how to launch “Event Viewer” and some common problems:
    http://itexpertvoice.com/home/what%E2%80%99s-taking-so-long-how-to-fight-slow-startup-times-in-windo...
    Aside from that, if your computer is part of a domain, the problem may be connected with certain Windows Services that start automatically on boot up. I recommend trying the following steps:
    Open up “Control Panel” go to “System and Security” then “Administrative Tools” from here launch “Services”.
    Sort the list by name and scroll down to “Network Store Interface Service” right click and select “Properties”. Under the startup type dropdown select “Automatic (Delayed Start)”.
    Next scroll down to the “WebClient” service again under “Properties” this time select “Disabled” under the startup type.
    As for the problem with running LabVIEW executables, I have a few questions:
    Do you get any error codes when it closes automatically?
     Does this occur for multiple executables or just one in particular?
     Does the code run without a problem within LabVIEW?
     Have you tried to update LabVIEW?
    What hardware are you running?
    Without this information I can only think it may be caused by the Windows Data Execution Prevention (DEP) security feature. So you can try the following steps:
    Right click on “Computer” and select “Properties”.
    Click on “Advanced System Settings” and select the “Advanced tab, then under the performance section click “Settings”.
    Click the “Data Execution Prevention” tab.
    Make sure it is activated for essential Windows programs and services only, or you have an exception for your EXE.
    You may also find the following link helpful on debugging applications:
    http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/debug_apps_dlls/
    Let me know if these solve the problems.
    Andrew.N
    Applications Engineer
    National Instruments

  • Spartan 3E with Labview 2012 (32 bit) on WIndows 7 64-bit - Error Code: -310602 NI-COBS: Unable to communicate with device over communication cable.

    Thanks for the info, Kyle.  I will probably try to find an older 32-bit XP machine.  VM is just not an option for me right now.

    Hello everybody,
    I am trying to use the DIgilent Spartan 3E board with Labvew 2012 SP1 32 bit.  I am able to compile the example code for LED shift.  I am however unable to transfer code to the FPGA.  I get the following error message:
    Error Code: -310602 
    NI-COBS:  Unable to communicate with device over communication cable. 
    Please verify that the cable is connected to a supported device and that the appropriate drivers are installed.
    My system configuration is as follows:
    Windows 7 (64 bit) on Dell XPS laptop.
    Labview 2012 SP1 (32 bit)
    Labview FPGA 2012 SP1
    Labview 2012 FPGA support for Spartan3E
    Xilinx 13.4 tools
    DEFB LV FPGA 2012sp1 support installer
    Xilinx USB cable driver v1.3 installed.
    I took all the precautions mentioned by others on this forum and others, mainly that the cable must be disconnected before installing the Xilinx cable driver. All software and drivers were installed correctly.  I even uninstalled and reinstalled the entire Labview software set I had.  I still get the same error.
    A few other questions:
    1.  Is the Xilinx cable different from a regular USB cable of the same configuration ?
    2.  When I program the FPGA I only have the USB cable connected between my computer and the Spartan 3e board.  Should any other cable be connected ?
    3.  What should be the correct jumper settings for J1 - JP30 (especially J30, J11, JP9, JP6, JP7, etc) ?
    I have been at this or over 3 days trying to figure it out.  Any help will be greatly appreciated.
     

  • Can I get MJD (date and time) in LabVIEW 2012 SP1?

    I need to time stamp my data before sending it to the file.  I have been doing this with the standard calendar date and time but MJD is what we prefer to use.  How can I get an MJD timestamp in LabVIEW 2012 SP1?
    Solved!
    Go to Solution.

    Hello Brad_Henry,
    The Format Date/Time String will return the day of the year when the %j argument is used, as per this help document:
    LabVIEW Help: Format Codes for the Time Format String
    http://zone.ni.com/reference/en-XX/help/371361J-01/glang/codes_for_time_format_str/
    If you're looking for the actual MJD, I'm not aware of a built-in function that generates this so you'll probably need to create or find a function to calculate it manually.  This should pretty basic arithmetic, and it looks like people have already made a few public examples, the first two search results here look to be just about what you need:
    ni.com search:
    http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/catnav:ex/q/julian/
    Regards,
    Tom L.

  • Bind FPGA host reference to type definition in labVIEW 2012 crashes labVIEW

    Hi,
    I am using FPGA target device 5641R and labview FPGA 2012 with 5640R ver 1.7.
    On the configure window of open FPGA VI reference function, choosing the dynmaic mode shows broken arrow when wired to the 5640R configuration VIs (i.e. Configure timebase, Configure ADC default, Configure ADC NCO functions). So i tried the other option which is binding the FPGA host reference to type definition and choose the control from path C:\Program Files\National Instruments\LabVIEW 2012\instr.lib\ni5640R\Configuration\NI-5640R VIs\ni5640R FPGA VI Reference.ctl. But after that when i try to save the VI on which open FPGA VI reference function is placed, labVIEW crashes. I am unable to figure out the reason. Earlier I was working with labVIEW 2011 and it was working fine there. Any suggestions would be highly appretiated. 
    Please see the attached images for more details.
    Thanks
    Attachments:
    1.png ‏33 KB
    2.png ‏71 KB
    3.png ‏40 KB

    Check out this thread.  It looks like someone else ran into a similar issue and made changes that fixed their application.
    http://forums.ni.com/t5/IF-RIO/correct-5640r-template-use-recommendation/td-p/1331918
    Jeff B.
    Applications Engineer
    National Instruments

  • Compatibility of LabView 2012 installed on XP with Vision and Trad DAQ

    Is LabView 2012 runnung under Windows XP compatible with
    A: NI Vision 2011 ? 
    B: Traditional DAQ 7.4.4 ?

    This should answer your question:
    Windows Version Compatibility with LabVIEW
    Compatible Versions of Vision Development Module with LabVIEW and LabWindows/CVI
    NI-IMAQ, NI-IMAQdx, NI-IMAQ I/O, and VAS Compatibility with Different LabVIEW Versions
    NI-DAQ and LabVIEW Version Compatibility (for Windows)
    I would still suggest to have a look at the readme files as well.
    Adnan Zafar
    Certified LabVIEW Architect
    Coleman Technologies

  • LabView 2012 Security System Main vi's have error 200559

    The vi's give errors of 200559 in my LabView 2012 and NI application engineer "John Staskal" told me as "Another good step 
    is to recreate the VI in your current version of LabVIEW so that you know the error is not caused by upgrading the VI to a newer version of LabVIEW." I did all that, but not resolved.
    Their application engineer John Staskal also told me as "In addition to working to resolve the error you may want to pursue is posting on our upgrade forum and asking the community to convert the VI to a current 
    version of LabVIEW.  http://forums.ni.com/t5/Version-Conversion/bd-p/VersionConversion".
     I did all trouble shooting steps such as highlight execution, probes, etc as what their application engineer told me and still having error of 200559 in LabView 2012.
    I  appreciate help from any one.
    Ali Tariq Bhatti
    Ali Tariq Bhatti
    Advice: Some people talk on different issues and abusive against your post because they do not want to help and arguing with you on some other topic. You all will observe and I also observed, so also do not want to mention their name and best way is complaint them to the moderator. If anyone still wants to talk on different issues against the post, other way is to do private message.
    ~~~Be nice, have faith in ALLAH(God)~~~
    Attachments:
    NI ELVIS II Security System VIs (2).zip ‏313 KB
    Error 200559.docx ‏500 KB

    RavensFan,
    I) Yes, I open up the front panel of the Express VI's and probe into them.
    2) I use the express vi's, but if you see my attached vi's file. You will see Security System Main vi is the main vi where the program is running and where I am getting the error of 200559.
    3) I also attached the word document file, so I am getting error of 200559 in probes 3, 4, and 5 using Export Key Press and Voltage vi's in this post.
    4)Do you know, how to convert these my attached vi's to 2011, 2010, 2009, or LabVIEW8.5 version. May be, it fix the problem, or if you know some one to get help from or get chance to use ELVIS II board, so let me know .Your help or any one's help is appreciated.
    Advice: Some people talk on different issues and abusive against your post because they do not want to help and arguing with you on some other topic. You all will observe and I also observed, so also do not want to mention their name and best way is complaint them to the moderator. If anyone still wants to talk on different issues against the post, other way is to do private message.
    ~~~Be nice, have faith in ALLAH(God)~~~
    Attachments:
    did probes for Export Press and Key vi's file.docx ‏340 KB

  • When will the Ingenia Motion Control Library be available in LabVIEW 2012?

    http://sine.ni.com/nips/cds/view/p/lang/en/nid/210877
    I get the following error when I try to open an Ingenia example in LabVIEW 2012
    1) Does anybody know when this library will be available in LV2012?
    2) Are there any other motion control librarys available for LabVIEW?
    Patur Sivertsen Vase
    www.hfjensen.dk

    It looks like the block diagrams have been removed so no version of LabVIEW will be able to open it.
    Contact the manufacturer if you need assistance:
    www.ingeniamc.com/En/Soporte/Soporte-Tecnico.aspx
    English home page:
    http://www.ingeniamc.com/En/default.aspx?ChangeLanguage=true
    -AK2DM
    ~~~~~~~~~~~~~~~~~~~~~~~~~~
    "It’s the questions that drive us.”
    ~~~~~~~~~~~~~~~~~~~~~~~~~~

  • Only have LabVIEW 2012. Why am I asked to download LabVIEW 2011 SP1 f2 RTE Patch?

    Hello,
    I recently got a new machine (clean install of Windows 8), and installed LabVIEW 2012, with no other previous versions. However, when I ran the NI Update Service, it listed "LabVIEW 2011 SP1 f2 R(32-bit) Run-Time Engine Patch" as a critical update.
    I'm confused; did I accidentally install LV 2011 too?
    Thanks
    Solved!
    Go to Solution.

    Also, some addons use older RunTime Engines.  It is not suprising that you need the 2011 RTE patch.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • What files do I send to be upgraded from LabVIEW 5.1.1 to LabVIEW 2012?

    OK.  Just to be clear.  I am a complete newb to ANYTHING LabVIEW or LabWindows related.  I am a programmer, but I have never used any version ever.  That said, I am responsible for the upgrade process of getting our old LabVIEW 5.1.1 system up to date.  The old system (still running and doing it's job everyday), is an old Windows NT v4.0 SP6 system running LabVIEW 5.1.1.  You can just imagine how ancient this is by today's standard.
    Have I set the stage properly?  I hope so.  Newb, Ancient LabVIEW version 5.1.1, Windows NT 4.0, upgrading from 5.1.1 to 2012.
    Now here is what I "think" I know about what is required.  Because LabVIEW 2012 will not directly read in, process and /or compile LabVIEW 5.1.1 files, I must first open and save the files using an intermediate version of LabVIEW (specifically 8.2.1) to bring the files up to a version that 2012 can handle.  I have noticed in reading the Version Conversion forum, that I can attach a zip file of my LabVIEW files and one of the resident Gurus will convert it for me and give them back - quite nice I think.
    Now, I have what I think are all of the required LabVIEW vi and llb files that make up this system we have in place, but I want to be sure before I just post a bunch of stuff.  
    What exactly do I need to zip up and what can I leave out? 
    Are there LabVIEW vi and llb files in a "project" that are not needed? 
    Are there any setup/configuration/project specific files I need to include? 
    Are there any limitatations to this conversion process that I need to be concerned with - such as various toolkits/suites/modules that may have been used but are no longer supported?
    Secondly, I am not really comfortable with posting my vi and llb files for the world to see (and possibly use) as I am not the owner of said modules, just the user/future developer who will be responsible for insuring they stay up to date.  Is there any way I can send my files to a specific NI guru via email instead of just posting them?
    Solved!
    Go to Solution.

    So if I understand you correctly,  all I really need to do is to get LabVIEW 8.2.1, and update my .vi, .lib, and any .ctl files to that version.
    Is it a simple matter of just opening the files and hitting something like SAVE AS, or just SAVE and it will do this?  Once done, LabVIEW 2012 will then allow me to open them and do what I need to do?  Do I have to save them into LabVIEW 2012 first, or is that automatic when I try to recompile them?
    When I get a copy of LabVIEW 8.2.1 (eval version), do I have to get all of the pieces (modules, toolkits, etc.) in order to update the 5.1.1 files?  Based on what is installed on that NT v4.0 system, we have the following items installed:
    NI VISA
    NI ComponentWorks 3D Graph
    NI DataSocket
    NI LabVIEW 5.1.1 Advanced Analysis Library
    NI LabVIEW RTE 5.1.1
    NI LabVIEW v5.1.1
    NI Measurement and Auto Explorer 1.1
    NI-488 2.1.60
    NI-DAQ 6.6
    NI-PAL 1.3.110
    NI-Reports
    NI-VXI/VISA
    You mention DAQ.  Our program uses NI DAQ v6.6 now.  I have LabVIEW Developer 2012, so I just download the DAQ files for it and it will replace the NI DAQ v6.6 library files we use now? 
    Thanks for your help so far.  If we had a support contract in place, this wouldn't be an issue.  However, as I stated, I am not the owner of the files, just the currently assigned caretaker, and part of my task is to get from where we are now on this ancient hardware/software platform, to the latest and greatest.  However, I am specifically not allowed to just place the files on a public forum for all to see.  It just isn't done.  We can send them to a known location and a known entity, but not to just anyone/anywhere as a public forum is by its very nature.   
    I know there is nothing you guys can do if I cannot give you the files, but thanks for helping me to do it myself.    Getting an eval copy of 8.2.1, et. al is probably what I have to do here.

  • Vlm 3.0 LabVIEW 2012 SP1 disabled in Installer

    Hello folks,
    i have a Problem with die build Installer with my new updatet vlm 3.0.
    I already get the the new license file for vlm 3.0 and installed it, then i made the installer for
    LabVIEW 2012 SP1 like i have done it with the previous versions of LabVIEW 2009 2010 2011
    In the produkt list of the installer LabVIEW and the DriverDVD is disabled by default (see Screenshot).
    Solved!
    Go to Solution.

    Today i was looking on the server and i have seen that the licenses are LabVIEW 2012 licenses.
    I want to install LabVIEW 2012 SP1.
    So that's normal, i think i have to wait until i get the new license file for the new version.
    Thanks BRennhofer for this idea.
    I will report here.

  • Again mixed signal graph and Labview 2012

    I have just experienced a weird change in labview 2012 on the mixed signal graphs. In a preliminary analysis, it seems that the most critical behavior is related to the silver mixed signal graph, although i didn't have the time to test the standard one.
    Straight to the point... the property "plot area size" not only resizes the plot area, but also the graph; this is in contrast with what happened previously in LV2011. If the graph belongs to a subpane and if the property "fit control to pane" is enabled, the area resize prevents the graph from correctly fitting the pane. 
    Any suggestion?
    cheers
    m.
    Attachments:
    MixedSignalDisaster.vi ‏13 KB

    I think that since this behavior is a regression (working properly until LabVIEW 2011 SP1) this should be fixed as soon as possible through a specific fix, without waiting for the next Service Pack.
    This regression has been blocking the development of our application.
    Could someone from the NI support give an answer, please?
    Vix
    In claris non fit interpretatio
    Using LV 2013 SP1 on Win 7 64bit
    Using LV 8.2.1 on WinXP SP3
    Using CVI 2012 SP1 on Win 7 64bit, WinXP and WinXP Embedded
    Using CVI 6.0 on Win2k, WinXP and WinXP Embedded

Maybe you are looking for