LabView Instrument Profiles

Cameron:
I'm working on a similar type of application that uses various user
inputs to control my instrumentation. I also used an array of clusters
that I can flatten and unflatten for file storage. The way I handled
the problem you describe is to create a local variable and pass user
inputs into the cluster. One thing you might want to do that I found
useful was to validate all my user inputs prior to passing them to the
local variable. This way your instrumentation doesn't receive invalid
set-up commands. Although this may not be to critical for your
application without verifying my input I could potentially damage the
device under test by acidentaly adding a zero to a voltage or
temperature profile.
I hope this is helpf
ul.
Another hint I recently found out about something called a state machine
for building user interfaces. My interface sort of looks like astate
machine but I wish I would have learn about them before I started.
Take care,
Brian Wells
Space Power Institute
PS: I thinking about looking into organizing a little bit tighter
network of people starting to use LabView. I recently started writting
Labveiw code several months ago and have thought that I would learn more
if there were more individuals to bounce my ideas off of. I am
currently developing software to control an instrument of my design to
test the effiency of solar cells at various temperatures. In the near
future I will probally be writting some software for cycling and
analyzing super capacitors and in the fall I'll be working with fuel
cell characterization. If your work leads you into test bed design and
you might be interested in a internet learning group drop me a line.
I'm still not sure how it would work but I expl
oring possibilities
currently.

I was hoping that someone doing similar work would give some help. I've seen several post about solar cells, but looked about specifically one problem, that I still haven't faced.
This is really a thread digging. My bad.
Cheers!

Similar Messages

  • Labview Instrument driver development-career path

    Hi,
     How is the career path for a labview Instrument Driver Developer ( Third party instruments like Scope,DMM).

    First off LINK, just click on your name the link is duplicated in your recient posts on your profile page.  (Lots of interesting features in the forums)
    As far as career potential for a LabVIEW developer:
     All the skill in the world with LabVIEW won't do much unless you can apply it effectively.  It is a good skill set to have but, LabVIEW itself is a means to accomplish something else.  In my case it facillitates developing automated tests. From your post it would facillitate development of instrument drivers likely, secondary to the goal of facillitating the sales of those instruments.  So, you need more than LabVIEW, you should develop skill and knowledge about Instrument driver standards, instumentation, and communications protocols. While you are doing that you also need to be able to demonstrate your LabVIEW proficeincy.  Certification can help with that.
    Couple some serious understanding of test and measurement techniques with NI Certification and.... well lets just say you can pay the bills with it.  I Know. 
    Jeff

  • Best way to distribute LabVIEW Instruments Drivers.

    Hello,
    I'm trying to stick to the standards described just there:
    Developing LabVIEW Plug and Play Instrument Drivers
    Instrument Driver Development Tools and Resources
    Instrument Driver Guidelines
    However, I cannot see clearly what is the best way to distribute the LabVIEW Instruments Drivers, except that I need to be compliant with those standards to be on the IDNET (Instrument Drivers Network).
    Here is a couple of questions I'm not really sure about their answers:
    Is it okay to use a .NET dll and to make some calls?
    Is it fine to hide the Block Diagram? With passwords in the Drivers
    Can we put prevent the modification
    In my situation several devices (or let's say modules can controlled through one communication medium), so basically I might have one instrument drivers for several things.,,
    May I use some OOD? In order to control the equipment with methods and set some properties and encapsulate the communication stuff in classes, some equipments could be consider are inherited from others (more recent for instance), or this is totally prohibited by the guidelines above?
    What is the most suitable Specification Build type: Packet Library or other? If packed library, how to handle the early version created issue when opening the lib with newer version of LabVIEW then?
    How to deal with the copyright thing, do I need to copy and paste the copyright on both the Front Panel and on the Block Diagram?
    Is this copyright enough: "Copyright (c) <Company Name>. All rights reserved"?
    Solved!
    Go to Solution.

    Ehouarn wrote:
    Hello,
    I'm trying to stick to the standards described just there:
    Developing LabVIEW Plug and Play Instrument Drivers
    Instrument Driver Development Tools and Resources
    Instrument Driver Guidelines
    However, I cannot see clearly what is the best way to distribute the LabVIEW Instruments Drivers, except that I need to be compliant with those standards to be on the IDNET (Instrument Drivers Network).
    Here is a couple of questions I'm not really sure about their answers:
    Is it okay to use a .NET dll and to make some calls?
    Is it fine to hide the Block Diagram? With passwords in the Drivers
    Can we put prevent the modification
    In my situation several devices (or let's say modules can controlled through one communication medium), so basically I might have one instrument drivers for several things.,,
    May I use some OOD? In order to control the equipment with methods and set some properties and encapsulate the communication stuff in classes, some equipments could be consider are inherited from others (more recent for instance), or this is totally prohibited by the guidelines above?
    What is the most suitable Specification Build type: Packet Library or other? If packed library, how to handle the early version created issue when opening the lib with newer version of LabVIEW then?
    How to deal with the copyright thing, do I need to copy and paste the copyright on both the Front Panel and on the Block Diagram?
    Is this copyright enough: "Copyright (c) <Company Name>. All rights reserved"?
    Not sure about 1) but 2) and 3) are definitely a no go if you want your library to be distributable through the ID network. The standard only allows for DLLs in that  are really developed in C but would require you to also distribute the C code as far as I understand.
    OOP may not be a problem.
    Packed Library is definitely not something you want to do. They only work in the LabVIEW version in which they were created. You will hate the moment you decided to go with packed libraries as requests come in for other LabVIEW versions and your drivers are bashed on all discussion forums as being a pain in the ass to use.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Labview Instrument​: how to set some parameters back to default after restarting the simulation (in Multisim)?

    Hi everyone,
    I wrote a Labview Instrument VI that I use later in my simulation in Multisim. The problem is, after stopping the simulation and restarting it again, some important parameters of the VI are not initialized again and therefore all my calculations in the Labview Instrument file are messed up.
    Is there any option to set the params back to their default values after the simulation has been restarted?
    Has that something to do with Serialize/Deserialize Data in the VI?
    Thanks in advance!
    Ussr123

    ussr123 wrote:
    The problem is, after stopping the simulation and restarting it again, some important parameters of the VI are not initialized again and therefore all my calculations in the Labview Instrument file are messed up.
    Is there any option to set the params back to their default values after the simulation has been restarted?
    Where is the data held inside the LabVIEW code (local variables, uninitialized shift registers, etc.)?
    LabVIEW Champion . Do more with less code and in less time .

  • Advanced LabVIEW Instrument Driver Development Techniques

    Hi, reading AN006-Developing a LabVIEW™
    Instrument Driver and in page 2 I find:
    "refer to the Advanced LabVIEW Instrument Driver Development Techniques application note."
    I can not find this AN. Is the name correct ?
    Bye
    Luca

    Hi Luca,
    the link you're looking for should be this:
    http://zone.ni.com/devzone/conceptd.nsf/2d17d611efb58b22862567a9006ffe76/e7a1635c2166e0728625680a005b0b9a?OpenDocument
    Happy new year,
    Alberto

  • Deploy teststand system Labview instrument drivers

    I'm trying to deploy a teststand application but I have an error with some Labview VI's.
    I'm using some VI's to control an Agilent 34401A, so Labview instruments library that
    is in the default package was used. The error says that Labiew Could no open the following VIs...
    I don't want to install the Labview development system on the target machine, so I don't know
    how to fix this problem.
    I tried to copy the library to a different location an removing the VIs that are not wired (VI Tree.vi),
    but I have the same error. (On the sequence was changed the path to the new VI location).
    Thanks
    Marcos

    Marcos,
     You can execute VIs using the LabVIEW Runtime Engine, but all of the source VIs must be processed to collect their required dependencies and insure they are compiled in the current version of LabVIEW.  The Deployment Utility process VIs from your sequences automatically.  The TestStand Reference Manual has a chapter on deploying TestStand systems that should help you get started.
    -Rick Francis

  • New LabVIEW Instrument -Nugget

    How to add "New LabVIEW Instrument" to the windows "New" context menu.  This is something I have meaning to try for a while, and I am sure I will find useful where very long paths are involved.  I thought I would share the process with you, even though its not really a LabVIEW thing.
    Here is what I want to see in the NEW menu when i right click in a folder::
    And here's how to do it.  First, be careful in the registry!
    Use the registry editor and browse to HKEY_CLASSES_ROOT\.VI
    Add a new key called ShellNew
    Create a string value "FileName" in this new key.  Give in a value of LabVIEWInst.vi.  This VI is the template that windows will use to create the new vi.
    Close the registry editor when it looks like this:
    Now create a new, blank VI and call it LabVIEWInst.vi
    Save it in the folder Windows\ShellNew.  (I had to save it to the desktop first, then move it to the ShellNew folder as Win7 had issues saving to the Windows folder.)
    All Done!
    Now log off and back on to refresh the ShellNew list.
    I Hope this is of use to somebody.
    Michael.

    ussr123 wrote:
    The problem is, after stopping the simulation and restarting it again, some important parameters of the VI are not initialized again and therefore all my calculations in the Labview Instrument file are messed up.
    Is there any option to set the params back to their default values after the simulation has been restarted?
    Where is the data held inside the LabVIEW code (local variables, uninitialized shift registers, etc.)?
    LabVIEW Champion . Do more with less code and in less time .

  • LabVIEW instruments in transient simulation

    Hi,
    I'm performing some tests with an InputOutput LabVIEW Instrument that I made myself (2 in/4 out) that basically implements a simple lookup table (on the basis of two DC voltage levels it perform a 2D interpolation and then sets the 4 voltage outputs accordingly).
    In the interactive simulation mode everything works great.
    However, if I try to run a transient simulation, the LabVIEW instrument does not respond, it seems to ignore the two inputs so it gives zero for all the 4 parameters. 
    This suggests me that LabVIEW instruments are interactive-simulation objects only. Is it correct?
    This would limit the benefits of this great tool! 
    Can anyone suggest me a way to overcome this? 
    I work with Multisim 11 and LabVIEW 2009.
    Thanks.

    Everasia,
    Yes the custom LabVIEW instruments are used in interactive mode only.  What other things are you looking to do in Analysis -> Transient mode?  Expresssions, Post Processor data, etc?
    Are you are trying to use LabVIEW as a type of I/O behavioral component?
    Also, another possibility is using the Multisim API with LabVIEW (www.ni.com/labs) -
    LabVIEW Multisim Connectivity Toolkit (Beta), this will allow you to create interactivity between LabVIEW controls and the Multisim simulation - you can adjust source inputs and measure probes and pause the simulation between steps.
    If you would like to discuss the use case in more detail, please email me directly. 
    Regards,
    Pat Noonan
    [email protected]

  • Custom Labview Instrument with Multisim

    Hi,
    I want to use a custom Labview Instrument (Phasor_Diagram) with Multisim 13.0:
    http://www.ni.com/example/30200/en/
    I copied Phasor_Diagram.llb and the folder Phasor to C:\Program Files\National Instruments\Circuit Design Suite 13.0\lvinstruments but
    I can't find the Phasor Labview Instrument in my Multisim.
    What is going wrong? How to get this work?
    Regards Peter Stolz
    Solved!
    Go to Solution.

    Hi Peter,
    It looks that phasor instrument was built using an old LabVIEW version, I rebuit it in LabVIEW 2013.
    Tien P.
    National Instruments
    Attachments:
    Untitled Project 2.zip ‏1634 KB

  • NI MAX works but LabVIEW Instrument I/O VISA does not

    Hello,
    I am trying to communicate with SIM900 mainframe using RS232 connection in a VI but it is not working.
    It is strange because the communication works when I use NI MAX or MATLAB Instrument Control Toolbox but it doesn't when using LabVIEW VISA functions such as VISA Open, VISA Write, or VISA Read, etc.
    I confirmed that I use the correct serial settings (baud rage, data its, parity...), so it is hard to find out what might be the reason of this issue.
    Could anyone help me resolve this?
    Thank you,
    Jeong

    What are you using for a termination character? Are you using one of the example VIs where the string control is set for '\' Codes Display?

  • Looking for Labview instrument programmers in/near Michigan

    We are looking to hire a programmer familiar with Labview for high speed instrument control and data analysis applications

    pico wrote in message news:<[email protected]>...
    > We are looking to hire a programmer familiar with Labview for high
    > speed instrument control and data analysis applications
    Hi, I am exactly what you want! Here is (part of) my cover letter.
    Please email me where I can send the resume.
    In addition to my broad educational background including two Masters
    Degrees in Electrical Engineering and Physics, numerous Computer
    Science courses taken, and twelve years of diverse experience in
    programming, system administration, and support, I am a National
    Instruments Certified LabVIEW Developer. As you can see on the
    National Instruments website, there are only 167 people worldwide and
    4 including me in the State of Illinois who were granted this title. I
    have a history of numerous successful projects in the areas of
    industrial automation, control and data acquisition. In particular, I
    have implemented several LabVIEW test systems projects including the
    following:
    - Real-Time Electron Beam Doses Monitoring, Beam Parameters
    Measurement, and Ion Charge Measurement Systems for Steris
    Corporation;
    - Control and Data Acquisition Program for an Electron Spectrometer
    System in the Western Michigan University Accelerator Laboratory;
    - LIMS II (Temperature Test),Surge Test Automation, Locked Rotor Test,
    Variable Ambient Chamber Control and Data Acquisition for Underwriters
    Laboratories (UL);
    - Abrasion Wear Test for Caterpillar;
    - Distributed Data Acquisition and Reporting System for Hydraulic
    Spray Nozzles Testing for Spraying Systems Co.
    Descriptions and code examples of projects I have done are available
    upon request.
    The latest projects utilize my own architecture which allows creating
    complex applications as a collection of components that have uniform
    structure, but different purposes. Each component runs independently
    providing services to other components and exchanging data via
    standardized queued messages. The resulting code looks similar
    regardless of specific functionality. It is easily readable and
    modifiable by developers other than the author.
    I also have done several projects involving HMI, digital I/O, motion
    control, communication between a PC and PLC's, using Visual Basic,
    Think & Do, Steeplechase and other software tools.
    My experience and background enable me to master any software
    development tool quickly, making me a perfect candidate who can always
    keep up with the ever-changing world of computer technologies.
    I am looking forward to discussing this opportunity with you.
    Sincerely,
    Stanislav Rumega
    (847) 437-0794(home)
    (312) 255-8757(office), (312) 925-0780(cell)
    [email protected]

  • Need help in converting old LabVIEW instrument drivers to new version.

    Hello,
    I just rented a Tektronix DG2020A data generator. I did not find any instrument drivers for the DG2020A on the Instrument Driver Network, although there are drivers for DG2040 that could be used to some extent. With the instrument, I also received a floppy with example programs. This does include LabVIEW drivers for the DG2020A. However, when I tried to load the VIs, I received an error message that the VI version 3.1 is too old to be converted to 7.1. Can someone at NI help with the conversion? It would be very useful.
    Thanks.

    There is a driver available for the DG2020 on NI's site. Models supported are the DG2020, DG2030, and DG2040. Available in both 7.x and 8.x.

  • LabView Instrument​ation Experiment​s without any Physical Interface

    Hi friends I need some kind of experiments that can be made using LabView without any external Interface especially in Instrumentation (VCO,PLL,Opamp like) so please tell is it possible or I will need the Interface or can I do something in Instrumentation without Interface in LabView

    LabVIEW can be used as a pure programming language (I do it all the time!). Data acquisittion or instrument control hardware is completely optional.
    You can even simulate a real instrument by using simulated devices. For more complex functionality, you can simulate any other behavior yourself in software.
    Of course you still have the "user interface", i.e. the LabVIEW front panel.
    Can  you explain in a few more sentences what you have in mind?
    LabVIEW Champion . Do more with less code and in less time .

  • How can I increment channels on 34970A DAQ with the 34908A 40 channel mux using the LabVIEW instrument library.

    I have my external multimeter reading a voltage on a channel but with my LabVIEW program, I am trying to increment the channels so I can see the voltage on each of the 40 channels. Some help would be greatly appreciated.
    Thanks in advance,
    Jason

    Dennis,
    The channels vi that you attached to your response worked perfectly. Thank-you very much for your help. I am completing this LabVIEW vi as a workterm project as I am an electronics student at a local college in Newfoundland. I will be sure to add your name to the list of acknowledgements in the report.
    Thanks again,
    Baird

  • Creating Labview instruments

    Hi.
    I want to create the sine generator. I read the manual in Multisim 10.0 about creating instruments. I opened the output VI template.
    I can't understand, how can I set the frequancy in the VI?
    Thank You.

    Hello Dimon87,
    Instead of the 'generate Simulated Data' subVI try using the 'Sine Waveform' VI from the Waveform Generation palette.
    Follow the next steps:
    In the Template delete the 'generate Simulated Data.vi'
    Place the 'Sine Waveform' VI from Functions>>Signal Processing>>Waveform Generation.
    Configure this function.
    I hope this helps,
    Fernando D.
    National Instruments

Maybe you are looking for