Disable conditional symbols & base development system

I use LabVIEW 8.0.1 Basic with Application Builder development system.

I want to apply disable conditional for a code when running in the development environment.

That one (TARGET_TYPE) symbol appears in the drop-down menu symbol selection.

Symbols to disable conditional does not appear in the "category" in the Project Explorer.

This feature is not available in the basic package? Am I missing something?

I would like to have available optionally DEPLOY...

Thank you

Hi clark.leach,

An excerpt from LV 8.0 help :

'TARGET_TYPE is the only symbol that is available by default. If you use the conditional structure disable in a LabVIEW project, use the page conditional symbols turn off to set the additional symbols. »

Did you go to project > properties before searching for conditional symbols turn off in the category list?  This is where you're looking?

Tags: NI Software

Similar Questions

  • Disable conditional symbol search

    Is it possible to find all uses of the conditional symbols to disable in a large project?

    Joel

    CTRL + f

  • Filter database development system

    Hi all

    I recently discovered that in LabView base development system does not cover the filter VI, but I don't know that there is a way around it. I know it is possible to create my own VI of low-pass filter, but I'm curious to know if this is the only way? I am acquiring my signals using several index berries, then by applying a formula to the signal to convert the voltage entering a flow or temperature. I know that you can apply filters using DAQmx, but I need to convert all my code far Assistant DAQ to incorporate that. Thanks for all the help possible.

    The DAQ Assistant use DAQmx so convert these functions is not win you something. There are simply not filtering functions in the basic version of LabVIEW. Write your own, upgrade, or use an external hardware filter.

  • LabVIEW TEN compared to the speed of development system

    Hi all

    I worked on some software labview, which is called by Teststand. The target system has a labview license so I was not initially concerned by the RTE, but then after working with another company, I discovered that they were creating their VI then in turning them into .NET Interop assemblies and calling those rather than directly to the VI. When I asked them about this, they said they did it because he had run more quickly using the RTE rather than the full development system.

    My question is has anyone know if through the VI RTE is actually faster? If so can I just change the setting to use the RTE and reach the extra speed of the Teststand adapter or changing to an Interop Assembly .NET would be necessary?

    WARNING: I am a material engineer who hated the programming, but try to learn it as fast as I can now that I don't have a software engineer. While I'm not familiar with some concepts/terminology/best practices so patience is appreciated

    All things being equal, an executable will go faster because debugging (default) stops on the code. This will make faster, more when debugging is disabled, there is more the optimizer can do during compilation. Or that's the theory. Personally, I never noticed the difference.

    Mike...

  • Fingerprint memory for the LabVIEW 7.1 development system

    Hello

    I would like to know the size memory for LabVIEW 7.1 full development System.Both during the installtion and to develop applications later.

    If anyone can help. Thank you.

    There is no one answer for this, as this varies considerably.

    For what is on the disk, if my memory serves, the 7.x base takes a few hundred MB, but which could greatly inflate according to the modules and drivers you add.

    For the RAM, I believe than 7.0 used to identify approximately 20-50 MB immediately after loading, but this number then would also change a lot over time depending on what you are doing. Loading, editing and execution of code just regularly change the amount of RAM used.

    Why do you ask? Also, are you aware that 7.1 is relatively old now (came out 7 years ago)?

  • selection of development system

    I'll build a test bench and you want to use LabVIEW as a control and a monitoring system. I have planned for the full development system, but after reading the specifications for the basic system, according to me, that I'm able to use it instead. I hope that someone with more knowledge of LabVIEW will be able to give me some advice on this subject.

    The LabVIEW requirements are:

    Log data of about 10 sensors (thermocouples, load, pressure, speed) for several hours (about 30).

    The sampling rate when a certain temperature is reached.

    Order two servos.

    Control a motor inverter.

    For display purposes, perform data manipulation using basic mathematics.

    If anyone can advise me on my choice, I would be very grateful.

    Kind regards

    Steve

    Steve,

    Choose the right package for you depends not only on the requirements of your current project. This is what you will use in the future and what tools need you to do.

    As example, let's take the LV Application Builder. It is part of the professional package, but not of database development. When picking the one-based, so you'll need this toolkit as addon separate if you want to create an EXE file on your request later. Or you upgrade your Base of professional who will create additional costs.

    According to the engine, you might be interested in NI Motion or NI Soft Motion. You can learn more about this here. If the engine (or external motor controller) does not require you to work/use defined control circuits (for example, the PID), it is possible you don't need those.

    As a recommendation: download an evaluation version (evaluation) and looking for the functions that you will use (coming soon). Using of each function, it is listed package that you need in order to access this feature. If all are "Core development", this is the perfect package for you (except maybe above mentioned Application Builder)!

    Norbert

  • Missing link in the file write Key.vi LabView after switching LV development system server to RTE

    Hello

    TS4.2 LV8.6.1

    I have a strange behavior of TS. All of the code works well under the development system. But when I pass the server of LabView runtime LabVIEW development system then, during the call one of my screws (action step calling the LV adapter), I have the window 'vi search' open looking for the Key.vi to write (one of the interns LV VI). Finally, is the write file Key.vi and TS is happy, however, I don't want it to happen on the production floor.

    Is this a bug or I have some sort of option or something?

    Why this does not happen under the development environment? What is the mechanism?

    K.

    (1) more complex nodes in LabVIEW are stored in vi.lib.  This is not uncommon.  Are not only very basic items (add, subtract, table functions, etc...).  They are usually yellow and you can not open them.

    (2) they need to go somewhere, and vi.lib is the standard location for all built-in screws

    (3) instr.lib is very similar to vi.lib, just a different location.  LabVIEW stores a relative path for the screws here called in.  This path does not exist with the runtime, although TestStand will add it in the search directories if you installed LabVIEW Development.

    (4) if it is possible to use LabVIEW to do this, there are more ways to get into trouble, because doing it this way would never update your sequence or find problems that would be specific to TestStand.  Is there a reason why you don't want to use the TestStand deployment utility?  Behind the scenes, TestStand calls in the same frame as LabVIEW for the deployment, but do it with more knowledge that LabVIEW alone would have.  This can be done, but there are more considerations, and you can meet potential problems.  Unless you have a good reason for this, it is generally not advisable.

    I recommend reading the chapter on deployment in the handbook here (Chapter 14):

    http://www.NI.com/PDF/manuals/373435d.PDF

  • LabVIEW Professional 2012 development system

    Please provide us the link to download 2012 LabVIEW Professional Development System.

    Look here:

    http://download.NI.com/evaluation/LabVIEW/ekit/other/Downloader/

    Search for files beginning with "2012sp1LV" and pick your flavor.

  • Professional Development System: Can not build the Application

    Hello

    I have the LabVIEW Professional Development System 2015 on my computer.   According to National Instruments, this version of LabVIEW has already provided with the Application Builder.  However, when I try to compile a standalone application, I don't have access to the application of the manufacturer. I've referenced the tutorial here and think that I do everything correctly: http://www.ni.com/tutorial/3303/en/#toc1

    If please see the attached screen shot and notice how I do not have the option ' new > application ", as claimed by the my system of professional development tutorial * must * have. How can I access the Application Builder with my professional development system?  Should I enable it?  If so, how should I do this?

    Thank you

    Jason

    Go to OR under the National Instruments License Manager in the Start Menu.

    Make sure it is turned on it.  It should have happened automatically.  But if you had some odd order of installation, or maybe don't have access to the internet when it installed first, that she might leave the hanging of activation.

  • Development system LabVIEW 2011 fails to install

    I just tried several times to install my new copy of LabVIEW 2011 Suite of Dev, but get an unknown exception (with no details - see photo) from the beginning of the installation of the development system (32-bit English).  I restarted and closed all applications, including the virus scan, but still the same.  I use Windows XP Pro SP3 and have LV 8.6, 2009 and 2010 is installed.  I'm completely baffled as this type of problem has never happened before, and there is no information on the cause of the exception.

    Mike


  • Download LabVIEW Development System 2010 SP1 64 bit

    Hello

    I am looking to download the development system LabVIEW 2010 for 64 bit on windows Server 2008, but I can't find link: the only one I found is a 2011, and I don't want to upgrade the project for 2011.
    Best regards

    HI V. f.,.

    Simply call your local representative of NEITHER, they will help these issues...

  • How to create a stand-alone executable in LabVIEW 2009 Professional Development System?

    How to create a stand-alone executable in LabVIEW 2009 Professional Development System?

    This should help you http://zone.ni.com/devzone/cda/tut/p/id/3303

    Remember that the quick search with Google in many cases will be quicker to ask in this forum. I always use Google before asking for help in any forum. It is much faster

  • in the output log file bit 00's are added, why? (Do not run the attached vi. It disables all devices in your system)

    Hi all

    I've attached a zip file when co-existence.vi is the main file of vi that communicates with a USB device and returns some responses of ATR.

    The answers are stored in a log file. I have attached the log file. In the log file in three places while displaying ATR, get added some unwanted 00's. Please help me how it is and how to remove it?

    Thank you

    Mathan

    [Note: (not to run the attached vi.] It disables all devices in your system)].

    It seems that the duration depends on the value you get out of the dll (dwARTLen). You have wired it as 100, so it seems that the dll simply returns the entry. Maybe you want to check the documentation for the dll on the way to get the actual length.

    A large part of your code is very confusing...

    • You have several subVIs that are essentially the same, but with different names. Not one of these not enough?
    • What is the purpose of the loop IN the adhc.vi? Since you autoindex in a table of a line, it will be executed only once, and the result is the same as if you would remove the loop FOR.
    • Your main VI is extremely repetitive with lots of duplicate code. You have 12 instances of the file name constant, would be enough! Enable.VI is identical to disable.vi, except for a constant of diagram. Much the same constant string ("ATR: ', ' peripheral access card:", etc. "), once again, everyone is enough.

    Here a nice state machine would make all the difference.  You need only about 10% of the current code, eliminating all the rehearsals.

  • Empty text box value when reading about the LV2012 development system but no Production

    Development platform: 32-bit Windows 7, LV2012 Professional Development System.

    Production of platforms: Windows XP.

    We have a test application, we have developed (in haste, I might add) who has a curious problem.  As part of the installation for each test, read us a text box with a serial number entry and record them in the log files.  Series enough.

    This works very well on production machines - no apparent problem.

    However, on the development computer, when I try to read the text box, all I get is an empty string.  I tried to read directly from the Terminal, as well as using a property value box.  Each time, there is nothing in the string.  This is even though I'm looking at the text box and there are visible data in it.

    Clear the text box repeatedly, I'm looking to see if any of those that occur at the wrong time.  And, indeed, I am looking a probe value of ' ' from the property node Value with the string "1234" visible in the text box while NONE of the compensation functions have been affected.

    The test application uses a pretty standard user interface event loop model, with an event loop manages the user input and the other event loop manages the business logic.

    Anyone have any idea what can cause this, or a better search string to find clues?

    Thank you

    Geoff

    As promised, I did go to the bottom of it.

    Simply enable "update of value while typing" gave me the result I expected.

    To explain: I had a key event down to the first text box that has been copied to this text box.  Whenever a key was hit in this text box, the value would be read and updated.  I did not have all the events for the new text box.  It has not been updated to what some other events.  At that time, it was apparently too late (most of the time on the development computer) and occasionally on the Production machine.

    Activation of the "Update value while typing" indicator means that the value field would properly up-to-date each time he has been seen/accessible.

    Life is a learning experience...

  • References: Different Aspect in the development system and Run Time System

    I noticed a difference the appearance of references in system development and run time system.  He seems to have no effect in the executable version, but, out of curiosity, anyone has an explanation?

    Development system

    Run time system

    Jean-Marc

    TST wrote:

    When LabVIEW generates an executable file, it deletes the parts which are not necessary the screw (like the comics, or FPs of screws that will not open). I guess that's an extension of the one where the icon is not copied on. Another option is that RTE simply lack the code necessary to display this specific to this.

    In any case, I would say that this is a bug, even if it is minor.

    I don't think it's a bug, the summary of references to a CTL file, which is not present in the RTE, I think that LabVIEW disconnected from the reference shape the typedef and saves only the required properties.

    Tone

Maybe you are looking for