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 .

Similar Messages

  • 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

  • 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

  • Creating a new software instrument track in Logic Pro 9

    When I create a new software instrument track in Logic 9, the newly-created track always defaults to "EVP 88 Electric Piano" instead of "Inst 1" like it's supposed to. Why does Logic do this and how can I restore the settings so that it opens the new track as "Inst 1."
    Thanks much!!
    Alex

    That was added around 9.1.1 - presumably so people wouldn't create an instrument and then ask "I created an instrument, but it don't make no sound." 
    You can uncheck the open library box or go to HD>Library>App support>Logic>channel strip settings>Instrument>01 Logic instruments and change the one called something like "EVP88 Electric Piano" to just "Electric Piano."

  • Can't install new loops/instruments in GB '08

    I went to install iLife 08 on my iBook yesterday. I did a custom install because I didn't want to install all the apps right away. For Garage Band, I noticed that the option for installing additional loops and instruments was grayed out. It would not allow me to even check it.
    What's going on? Why can't I install the new loops/instruments that are part of GB '08?

    So, I installed GB 08
    Then, I went back to the installer. I can now check the garage band add ons option. Except that I can't check just that. It forces me to check the main garage band install box as well. I assume that means it would re-install GB, just to get those extras??
    Also, sounds and jingles still can't be checked. It says there is stuff for GB and iMovie. I can't install iMovie since my G4 ibook won't run it, but I would think I would still be able to get the sounds and jingles to use in GB.

  • Bug in SURROUND when instnciating new SOFTWARE INSTRUMENT?

    Hi all
    Is this a bug?
    This only seems to appear after mix is up to say a dozen tracks.
    Whilst working in SURROUND ... I have some audio and some software instrument tracks running ... instanciate a new EX24 or KONTAKT 3 by choosing NEW TRACK with a key command ...... choose NEW SOFTWARE INSTRUMENT .... when you've opened the new instrument, everything in the mix is shunted over toward the left hand side of the room.
    There's no apparent way to get the mix back to where it was so you have REVERT TO SAVED?
    Best
    Dick

    If so, don't.....   Use the New Project command instead
    at the startup of the song it creates 5 busses......
    using Empty project....... Every new SI.... same issue
    It may be you have created a template, or are using one.. that includes those busses....
    I do use a template song with some busses, but it creates 2 new if I create a new Software Instrument.
    I don't understand this behavior.......
    This issue occurs using the command New Software  Instrument tracks, and not creating New Audio Tracks
    The unique way to avoid this for me is to copy a SI in the Environment and then change its Inst channel....

  • 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 .

  • 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

  • Making new EXS instruments show up in the library

    Is it possible to make new EXS instruments (such as third-party EXS instruments) show up in the new Library column, and not just the EXS24's own instruments list?
    It would be great do access them directly from the main library column.

    Haakon,
    If you look at the channelstrip, you'll see a white halo around one of the buttons. It defaults to Settings but if you select the Instrument button with EXS instanciated, then the first library column becomes EXS presets.

  • Newbie:  How do I create a new Audio Instrument?

    Hi there,
    Sorry to be asking such a stupid basic question, but I've searched high and low and it is not obvious.
    I want to start a new Audio Instrument track.
    On the Track menu, I select "Create", and a new track will appear. However, it is always either an Audio track or a MIDI track. Never an Audio Instrument track.
    Can I change the other track types into Audio Instrument tracks?
    If I click-and-hold on the track name in the Arrange window, a pop-up menu appears, but there's no obvious way to change the track type.
    Thanks

    That menu that you clicked should hold 5 options. The middle one (since I'm not looking at the software right now I can't be 100% sure) should be the "Audio Instrument" track you are looking for. Your five options should be along the lines of MIDI track, Bus, audio instrument, Master Fader, and Audio Track. The middle one is what you are looking for. After that, in the arrange channel strip window to the left of the arrange window, go to the selectable I/O menu at the bottom and select any of logic's many softsynths or the excellent sampler. I hope that helped. I'm on another computer and couldn't pop open my software to confirm all this. The MIDI tracks that it opens up to are next to useless, as they are meant as General MIDI tracks for some purpose that I have not yet found a use for. Hope that helped!

  • Using New LabVIEW Merge Tool LVMerge With Tortoise SVN

    Hi,
    I've just posted a new blog article Using New LabVIEW Merge Tool LVMerge With Tortoise SVN to my blog at ExpressionFlow. Check it out!
    Tomi
    Tomi Maila

    The LV merge tool really does become far more powerful when integrated into SVN than when used manually.  Here's an article on Using LVmerge LabVIEW Merge Tool with TortoiseSVN with all the necessary setup instructions for LabView 8.5 and 8.6.
    Jesse

  • 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]

  • Installing old VIs in newer LabVIEW folder: how to avoid conversion warnings?

    We are offering a set of VIs to our users. We build our own installer which installs them into the LabVIEW program folder under vi.lib. A menu file is installed in the menus tor which collects the VIs in a palette.
    For providing compatibility with LV 8.2 and up the VIs are in v8.2 format. When they are installed in a higher LV version and a LV program that contains some of the VIs is closed, LV issues the warning that the VIs have been recompiled and converted from an older format. How can we install the VIs so that LV ignores the format version?

    smercurio_fc wrote:
    I did not mean to imply that setting the read-only flag would fix your problem. Only that it would prevent the file from being saved, if that's what you were intending to be done. You cannot change the behavior, as it is by design. You can deal with it by compiling the VIs when you install the software, as has been mentioned. Or, you can distribute pre-compiled versions in the LabVIEW versions of your choice.
    You mean it is definitely not possible to have VIs in one, relatively old LabVIEW format and install them for newer LabVIEW versions without getting this (completely useless) warning? This is hard to believe. How do other companies distribute their LabVIEW programming interfaces? Do they really maintain a VI versions for every LV version (and possible sub-version) just to guarantee a good user experience?
    Since the recompiled changes are dumped anyway, I would expect a VI or library flag I could set or a special way of installing the VIs that tells LabVIEW: ignore the changes when the VI is closed.
    Recompiling everything during installation is not what we want since it would make the installation process too complicated, in which our LabVIEW API is just a small part. If nothing else works I would rather install the VIs writable so the user could just hit "save all" when he closes his program and get rid of the warnings, but this is not optimal.
    Olf

  • 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

Maybe you are looking for