Speeding the Keithley 6485 readings with LabView

Hi All,
I'm new with LabView and with current measurements. I'm using a Keithley 6485 Pico-Amp to recored the current changes in microchannels. I downloaded the instrument drivers from the NI website and I tried to control the Pico-Amp current readings with LabView 7.1 but the rate of readings from the Pico Amp was slow ( a reading every 0.5 s). I tried to change a lot of parameters and I found the main problem causing such slow measurements is the read VI for the Pico-Amp was very slow in the while loop.
is there any way to recored fast continuous measurements from the Pico-Amp using the read VI in a while loop with LabView 7.1?.  or if there is another to do fast recordings form the Pico-Amp with LabView? 
I appreciate your help and suggestions.
thanks

thanks a lot guys for your suggestions and comments.
at the present time I'm using the analog output of the Pico -Amp to recored the readings via a Daq since I couldn't control it form the drivers. So,  I only control the Pico Amp from the front panel.
Dennis, thanks for your suggestions and it is true that fetch multi-point is faster but it is still not fast enough since I want reading at a rate of 40-50 Hz. if you know of a way to increase the readings rate to the frequency I need it will be helpful.
F. Schubert, thanks for comments. I don't know how to change the NPLC since when I change the value in the VI an error message appears and Labview terminates. the NPLC setting is 1 and PLC 60 Hz.
I attached a sample of VI I'm using to find the readings from the Pico-Amp and I would appreciate any suggestions to improve the readings rate. also how can I change the NPLC value of the device?
Thanks
Message Edited by Zeyad on 09-13-2007 11:51 AM
Attachments:
Pico_AMP_tests_2.vi ‏125 KB

Similar Messages

  • Is the Keithley 2612A compatible with Labview 7.1?

    Hi,
    I've got a shiny new Keithley 2612A dual channel sourcemeter and would like to start using it our lab's system.  We are currently using LabView 7.1.
    I found a driver for the 2612A, but it says it's only compatible with LabView 8 or higher:
    http://www.keithley.com/base_download?dassetid=51950
    Does anyone know of another driver, or other method that I might get this thing working in LabView 7.1?
    Many thanks,
    John
    Solved!
    Go to Solution.

    Download it and post it to the Downconvert thread.
    edit - It's a project style driver which was introduced with LabVIEW 8. It might take a little longer.

  • 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

  • Keithley 2750 interfacing with LabVIEW 8.5?

    This is my first time trying to set up the two software and hardware.  The Keithley 2750 was originally installed and taking data using ExceLink.  Now, I want to use LabVIEW instead for data acqusition.  I have already installed the LabVIEW cds.
    Where do I start to set up the interface between the Keithley 2750 multimeter and LabVIEW 8.5?

    If the title says Agilent, then you have opened the wrong example. Exactly which driver did you download? Project style plug and play or just the plain plug and play? Where did you install it? With either, you should have a folder under your instr.lib called ke27xx. What is in that folder will depend on the type of driver you downloaded. The project style (recomended), will have a .lvlib and .lvproj files and folders called Examples, Private, and Public. If you don't have these, what do you have? Post an image of the directory structure.
    Message Edited by Dennis Knutson on 06-23-2008 10:08 AM

  • What is the difference in execution time between a program written in C language and the same program made with LabView?

    what is the difference in execution time between a program written in C language and the same program made with LabView?

    Hi Pepe
    You cannot say which is faster, the LV or the C programm. The only way to be sure is to program in both environments and to check than. Check this for some benchmark examples:
    http://zone.ni.com/devzone/conceptd.nsf/webmain/DC9B6DD177D91D6286256C9400733D7F?OpenDocument&node=200059
    Luca
    Regards,
    Luca

  • Reading DC volts from Keithley 2000 Multimeter with LabView

    Hello, 
    I am new to LabView. I am trying to read and write DC Volts data from a KE2000 Multimeter using KUSB-488A interface. I need guidance on how to proceed. I need to simply read the voltage drop across a 1 megaohm resistor and write them in a file to plot later. Please help me with sequential steps since I do not know LabView much. I am using Labview 9.0
    Thanks a lot for your help.

    There are LabVIEW drivers for the Keithley meters available on the NI Instrument Driver Network.  They include examples that should do what you need with very little effort.
    Using LabVIEW: 7.1.1, 8.5.1 & 2013

  • Trouble getting consistent voltage readings with LabVIEW using a 1102/B

    Here's the situation:
    I have an optical sensor with reflector that I'm using these to determine the velocity of a rotating wheel. (actually it's a spool of cable)
    no beam reflection = 0 Vdc (actually it's floating from 0 - 2 volts)
    beam reflection = 10Vdc
    This is hooked up to an 1102/B channel configured for reading voltage in MAX
    Now, everything is fine at slower speeds.  The trouble is when the velocity increases...
    I'm using a DAQmx read VI in LV 7.1 to read the virtual channel I set.  It's in a while loop, outputting to a chart.
    The reads are missing reflections at higher speeds, but only seems to happen in LabVIEW.  The cable needs to be letting out at 2 ft/sec.
    Now, the sensor has an indicator light that says when it's seeing the reflected beam.  When I spin the wheel by hand (faster than the necessary speed) the sensor says it's picking up the reflectors (2 at 180 deg apart).  When I open MAX, and the test panel for that channel, I see that I have to increase the "sampes to read" to about 5k and the "rate" to 5kHz.   At that point, MAX  sees every beam reflection as well.
    Within LV, it still misses...  even with the loop delay set to 5ms.   I'm hesitant to go much lower with the delay... 
    The final destination for this reading function will be in a fairly large VI with a lot of serial communication to external instruments.
    Anyone have any advice?
    Thanks!
    Chuck

    Hi Chuck,
    Looks like you are configuring a DAQmx task/global channel
    My suggestion would be why not use any continous voltage read examples you will find in the examples shipped with LabVIEW?
    Go to examples>>Hardware input output>>DAQmx>>Analog measurements>>Voltage in this folder find and use the example VI cont-acq-volt-int-clk.VI ( named something like that ) read its documentation to know how to use it
    Or find the VI here
    any doubts, do get back

  • Is the cRIO 9067 compatible with LabVIEW 2013?

    I just purchased 2 cRIO 9067s and I'm trying to configure one of them to use.  I got the IP address set and booted it into safe mode.  The status light blinks twice, then pauses.  The documention says this means I need to download software.  NI MAX only suggests using versions 14.?, which I'm assuming is LabVIEW 2014, but that option is grayed out.  And if I  try to do a custom install, everything in the list produces a concfict and wont download.  Is the 9067 only compatible with LV 2014?  Or am I missing a step?  the version of LV that I am using is 2013.  I'm installing 2014 to test this theory, but I'm no thopeful.  Thanks for the help people.  
    Solved!
    Go to Solution.

    The cRIO-9067 does require LabVIEW and NI-RIO 2014. You can use http://download.ni.com/pub/gdc/tut/crio_software_versions.htm to look up the minimum software support for cRIO products.
    I don't see how I can link directly to the result, but if you select "CompactRIO Chassis and Controllers" from the drop down and then "cRIO-9067" you should see this table.
    NI cRIO-9067
    Minimum Software Support
    Software
    CompactRIO (FPGA Interface)
    CompactRIO (Scan Interface)
    ✔ Supported
    ✔ Supported
    LabVIEW
    2014
    2014
    LabVIEW FPGA Module
    2014
    LabVIEW Real-Time Module
    2014
    2014
    Device Driver Software
    NI-RIO Device Drivers August 2014
    NI-RIO Device Drivers August 2014
    NI-DAQmx
    Other Minimum Software

  • Need urgent help with communicating with the HP 4155B analyser with Labview

    i folks,
    I'm currently trying to communicate with our HP 4155B semiconductor pamaremter analyser.  I do not have experience with GPIB yet. I have installed the NI VISA.
    I was wondering if anyone could help with getting me started on how to start communicating with the device using Labview.
    I'm not certain where to start.
    Kind regards
    Rob

    Hi,
    Thanks for the help. I now have communication with the instrument.
    I was wondering if it's possible to to setup a data measurement (I-V Sweep) and be able to read the measurement data in realtime as it is being measured. So I basically see the graph updating itself on the PC during the measurement.
    Is this possible? Could anyone give advice on how I can go about this or are there any examples that can help me understand how to do this?
    I'm not completely sure how to initialise the instruemnt for communication and handle VISA WRITEs and READs. within LabView
    Best regards
    Rob

  • Help with Controlling the HP E1411B multimeter with LabView

    Hi -
    I'm using LabView 7.1, and trying to control the HP E1411B multimeter in a Textronix VX1410 frame, using a VXI-MXI-2 interface.  I've read that this is a register based device, which means what?  I can't control it using the VISA method in LabView?  I've been successful in this with other devices, so I'm guessing it can't be done because it doesn't work.  I also downloaded both the drivers for this device from the driver database, and neither work.  I can't seem to figure out to nake them work either.  Can anyone help?  I just want to use the MM to make simple measurements and display them in LabView.  If I wanted to create my own driver, what would be the best way to communicate with it?  Thanks.
    Charlie

     Sir,
       I want to make automatic test setup for testing accelerometer. My resources are Test station PC with windows 2000, Agilent E1401B High power mainframe with slot 0 controller, Slot 0 controller is NI VXI-MXI-2 controller, shaker etc. MXI-2 bus begins at PCI at the PC and goes to VXI backplane. Agilent E1401B cage have Agilent E1411B 51/2 Multimeter (in slot 3), Etec Test Head Support Module (slot 2), Etec Digital stimulus response module, ETEC test head I/O panel etc. we have old version labview-2009. using labview i want to control my test whole setup.
         Procedure for test setup is that i need to give power supply to shaker. Also i have to give input signal of 1kHz to shaker for vibration. Accelerometer will be mounted on shaker. Accelerometer output voltage has to be measured with agilent DMM E1411B in VXI cage.
    I have installed NI-VISA n NI-VXI driver and i was trying to program it using visa VIs in LABVIEW, but couldn't succeed.
    First, i am trying to make a simple program which can read resistance and voltage from HP E1411B DMM. There is difficulties in using VISA Out and VISA In VI. to measure DC voltage value from DMM, how should i give command to DMM using VISA out, because input to VISA out is numerial value so how can i give command to DMM. VISA In has only input offset and address space, so how will i know that which offset setting will show voltage value.

  • Can I target the STM32 Primer2 hardware with LabVIEW for ARM

    The STM32 Primer2 hardware looks very cool.  Can LabVIEW for Arm target this hardware?  From looking at the list of ARM devices supported by LabVIEW, this would appears to be a Tier 2 device (ARM Cortex-M3) with no support for TCP/IP or IO.
    Can anyone tell me the feasibility or effort required to get TCP/IP, IO, and maybe even display support for this device? 
    Message Edited by Jim Kring on 09-11-2009 10:46 AM

    Have you ever said something you wish you could take back after having time to reflect upon it?  Another forum I like, http://newsbusters.org lets the author edit his posts for a short time.  Maybe NI could to that and I would not be pulling out my foot so often.
    Well, perhaps I was a bit more "colorful" than I meant to be.  Frustration does that to me sometimes.  Still the idea of a strong rope covered with disgusting risks does get the point across magnificently.  I just wish I had saved it for something more suitable.
    Let me think back to some of the problems I've had in which I've lost hours trying to figure out...
    1.  Can't use the Wait ms function.  It halts the program.  Express wait works fine.  It was sprinkled throughout which made it hard to isolate.
    2.  Some sub VIs don't run unless they are checked as inline code.  I don't yet understand why.
    3.  At the beginning of my main vi there was a small cluster in which I filled the data from an SD card file.  I used a constant of the cluster on the input of the Bundle function, but because my program and variable sizes were near the max I changed a number of variable representations to save memory.  ...But I didn't replace the constant.  The program started exhibiting really strange behaviors.  I couldn't even get a simple state machine to run.  I was reduced to commenting out (disable structure) sections to find the problem before noticing the coercion dot on the input to the bundle (The dot against the red string color doesn't stand out very strongly which is why I missed it).  Apparently it overwrote memory since the older cluster was significantly larger than the new.
    4.  Spent a lot of time trying to get the SD card to work with SPI functions.  Even though I read that 2009 supported SD card file services I didn't intuitively understand how to wire up since the Open/Create/Replace function has a ref num output which actually connects to the file(use dialog) input of the read and write functions.
    5.  Had a problem with breakpoints and probes not working.  That apparently was caused by item #3.
    6.  Typo bug in the Arm_irq.c file  LM3Sxxxx_GPIOCAHandlerP to LM3Sxxxx_GPIOCHandlerP
    Some of these are of the rope variety. A few are actual bugs.  All probably could have been solved in moments had I a local guru.  Anyway, I've spent hours and my hands hurt.  I hope to have this little project working on the LM3s8962 today and after some hardware changes will port it over to the Primer2... Hopefully...
    This forum has been a real help... especially your quick responses.
    regards to all,
    David 

  • Sensirion EKP-3 Code to read the raw ticks from the SDP6xx Pressure Transducer with LabVIEW

    Guys:
    I have seen the post here about the Temp Humidity sensor: Ref: http://forums.ni.com/t5/forums/replypage/board-id/170/message-id/749141
    Pardon the post under a new topic but I was advised to post it in a "new thread"... With the Device name in the title..  If this is a no-no let me know...
    Here is a question for the EKP-3 using the USB for the SDP6xx Here is an overview of what I am looking for... 
    http://www.screencast.com/t/RUDOisSvqC
    I have the Sensirion EK-P3 Stick to talk to the pressure transducer..
    This stick is made by these guys: http://www.codemercs.com/349/
    My question is how did you figure out the binary code to read the T and RH from the  iowkit.dll
    I want to read the RAW TICKS from the device that represent pressure. They go from 0 - 65535 and I have spied on it with WireShark and can not wrangle the binary code to read the raw ticks I am after.
    I made a video you can look at to see what I want from my learnings from this post: 
    http://www.screencast.com/t/UnCTJtvWLe
    I attached the DLL as well (Just rename it to iowkit.dll because LabVIEW does nol like dll's in attachments... so you do not have to mess with the msi.
    You may contact me directly at [email protected]
    Thanks!
    Dave Korpi
    Ref: http://forums.ni.com/t5/forums/replypage/board-id/170/message-id/749141
    Attachments:
    SHT75_IOWarrior.llb ‏139 KB
    iowkitdll.txt ‏71 KB

    Cameron... Wondering if you knnow how to get a 2's compliment for a 12 bit value in LabVIEW?
    I am looking to get the code to communicate to this top secret Sensirion product.
    Anyone know if I am properly sending the commands at 1, 2 and 3 of the image below?
    At issue, I think, is getting the two's compliment of the two 8 bit registers at Data LSB and Data MSB using LabVIEW...
    I have been working with the wizards at http://www.codemercs.com/258/?L=1 who have been EXTREMELY helpful.
    They have an AWESOME I2C to USB converter that you can get OEM devices to work for your I2C project. It is a single channel version of the NI-8451
    Anyone out there can figure this out so I can read the RAW TICKS from the Sensirion SDP6xx product line?
    Thanks a million! 
    Feel free to contact me at 831-455-0418 (pacific time) or [email protected]
    Attachments:
    SensirionCalls.png ‏121 KB
    Sensirion_Differential_Pressure_SDP6x0_Sample_Code_V1.pdf ‏97 KB
    LabVIEW_IOWarrior_V150Second.zip ‏1403 KB

  • Will the ELVIS board work with LabVIEW 2010 Student Edition?

    I recently acquired a traditional ELVIS board (with the PCI DAQ board). So far I've only installed the evaluation for LabVIEW 2010 (x64), and when I attempt to install the ELVIS Traditional 3.0.5 software I get the following message: "This installer requires LabVIEW 8.5 Full Development system or later to be present on this computer. LabVIEW Base Development System in any version of LabVIEW is not supported. Please install LabVIEW and then run the NI ELVIS installer again."
    I am eligible to purchase a student license for LabVIEW 2010 and would like to know if the ELVIS Traditional 3.0.5 software will install after I've acquired a student license.
    I am running windows 7 (x64) with an evaluation version of LabVIEW 2010 (x64). 
    Solved!
    Go to Solution.

    Perhaps I spoke too soon. I purchased a student license for LabVIEW 2010 and am still receiving the same error. I've provided screenshots of my license and the message from the ELVIS Traditional 3.0.5 installer.

  • How to Control the Valves and Pump with Labview?

    I have started a new project where I have to control the valves operation through Labview 2009,using PXI 1031, NI 5105(Digitizer) and NI 6251(M-series DAQ).
    The valves I need to control using the labview are:
    a) Pressure Reducing Valve (open & close)
    b) Remote control Valve(On & Off) with in-built actuator
    c) Flow control valve(open, semi open, partially open, semi close, partially close, fully close), 1%, 2%, 3%..etc
    d)saftey valve (opening closing depending on increase in pressure from certian limit)
    I hav eto control
    a) Hydraulic pump operation with in built gear-box
    Please let me know, how should l develop the VI for all? How to get started?, any helpful links? If there is any example code?
    Its little urgent !

    If you are not familiar with LV, I would suggest you go through the tutorials. Then take the leap and figure out how to use Action Engines and State Machines (search any of the terms I used that don't understand, there are a zillion threads on them).
    Then...
    Sit down and write stand-alone testers for each of the widgets you are going to control monitor etc.
      These testers will give you an idea if they really work the way you think, their character, and will serve as a "Sanity Check" when you think you are going crazy  durring development.
    THen integrate the tester so they can all work at the same time. This will become a utility screen that will serve you well when maintaining the critter latter in its life.
    Only then...
    write out a complete set of state diagrams that describe what you plan to do (don't cheat! ) and walk through them in your head until you are cetain it will all work blah blah blah.
    This step is optional but highly recomened...
    Compose a detailed set of documemtns describing what you have in mind and post them here (include the images, they will get many mor readers) and let people  pick aprat your design.
    When you have a final design, use everything you learned along the way to be a kick-ass developer.
    Along the way post distinct well defined question on this site and as long as it looks like you are trying someone will probably reply and get you going again.
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • Is the Intel I340-T4 Ethernet card compatible with LabView 8.6?

    We are currently looking in to having our LabView program process the output of two Allied Vision cameras, run through a PCI GigE card.
    On our old machine (32-bit Vista), we have a PRO/1000 PT Quad working just fine with the LabView interface - and we want to upgrade to a better PC with 64-bit Win 7.
    We are under the impression that PRO/1000 PT is not compatible with Win 7, and were looking into either I340 quad-port adapters:
    http://ark.intel.com/products/49186/Intel-Ethernet-Server-Adapter-I340-T4
    Does anyone have any insight as to the compatibilities of the Intel 82580 controllers with LabView 8.6? 

    Hi Civa,
    Scott here from AVT technical support.   You are correct re. that PT card not being Win7 compatible.  Here's a link to our current recommendations for NICs and switches.
    http://www.alliedvisiontec.com/fileadmin/content/PDF/Support/Application_Notes/Hardware_Selection_fo...
    If it's NOT in that list, it doesn't mean it won't work, merely that we haven't tested it and do not know.  We do not attempt to test every 3rd party product on the market.
    And our testing is typical with AVT SDKs not with Labview, though there are thousands of joint AVT / NI customers, and we'd have heard by now if there were any conflicts, I am confident.
    Regards,
    Scott

Maybe you are looking for