Removing block diagram

Is there any way to remove the block diagram on a single file basis (just like in the old good LV 7) without creating a source code distribution project?
I'm trying to create hook scripts for SVN and I'd like to remove the Block Diagram before publishing my code..., I'm using LV8.2.1 and will be moving to 8.5 soon
Please help!!!!
<<N>>
Message Edited by << - N - >> on 04-08-2008 11:09 AM

Hi Mike,
I think they work the same way in both 7.0 and 7.1 but in 8.2 and 8.5 there is no "Save with options" and the only way to do this seems to be creating a project...
Hopefully this functionality is 'hidden' somewhere otherwise I won't be able to create my script =S...
Does anyone know if this is possible for LV8.2/8.5???
Thanks for your help !!!
<<N>>
Message Edited by << - N - >> on 04-08-2008 01:53 PM

Similar Messages

  • Remove block diagram support for multiple targets

    Hi all, 
    Have you ever wanted the security of "remove VI block diagram" but not wanted to deal with the "now I need n+1 copies of all my VI's" where n is the number of supported targets you need and the "1" is for your development source?
    It isn't possible today, but take a moment and read/comment and maybe even up-vote this idea on the exchange: http://forums.ni.com/t5/LabVIEW-Idea-Exchange/quot-Remove-block-diagram-ed-quot-VI-s-contain-compile...
    then maybe one day... 
    QFang
    CLD LabVIEW 7.1 to 2013

    On a counter-note I'm working on a VI to actually automatically revert such trivial "dirt" VIs when using svn.
    I tested it yesterday and the basic functionality seems to work.  I need to test a bit and polish it up and maybe I can release it.  This would be a huge time saver for me when committing, not to mention doing away with a source of human error when cleaning up my local files before a commit.
    Shane.
    Say hello to my little friend.
    RFC 2323 FHE-Compliant

  • How to delet block diagram

    Dear Sir,
    Please help , how to permanentaly delet block diagram of the programme, so it will protected and show only front panel and no one can see the code of the programme.
    please tell me steps or any example of deleting it.
    Solved!
    Go to Solution.

    If you have difficulties in following the link then here it is.
    Make sure of these and remember
    1. You can no longer make any editing changes or view the block diagram. 
    2. You cannot open or run the VI on any other version of LabVIEW, older or newer.  
    3.You cannot open or run the VI on any other OS.
    One more thing, once it deleted then you will never able to recover it back so I sugges you to take a backup.
    Thanks
    Kudos are always welcome if you got solution to some extent.
    I need my difficulties because they are necessary to enjoy my success.
    --Ranjeet
    Attachments:
    remove block diagram.png ‏65 KB

  • Property Node activated even though it's been removed from Block Diagram

    Hi,
    I messed around with the property node of one of my controls and when I was finished and removed the property node from the block diagram it still makes my control blink.
    How do I make it stop??
    Is the option of Enable state not possible to set in property node mode. I'd like to go from disabled and grayed to enabled.
    Thanks.
    Solved!
    Go to Solution.

    Hi
    Your blinking property might still be set. Add the property again to set it to False.
    To set the enabled/disabled/grayed state use the "Disabled" property.
    Hope this helps.

  • How to remove the simulation loop from the block diagram

    hi,
    i have used lap view version 8.6 to design pid system. i have the pid block diagram with daq  on simulation loop. now my supervisor want me to remove the simulation loop. anyone know how to remove the simulation loop without deleting the pid block diagram. i have attached my pid program.
    Attachments:
    Copy of LAP VIEW FINAL for engine dyno.vi ‏221 KB

    logaraj wrote:
    hi,
    i have used lap view (  ) version 8.6 to design pid system. i have the pid block diagram with daq  on simulation loop. now my supervisor want me to remove the simulation loop. anyone know how to remove the simulation loop without deleting the pid block diagram. i have attached my pid program.
    You cannot remove the simulation loop alone because all the functions kept inside that loop will work inside that loop only. If you have to remove means then you have to find another way to inplement the PID control.
    The best solution is the one you find it by yourself

  • After I remove the Block Diagram, The VI under RT target is always broken.

    Why the VI is always broken under RT target if I remove their BD?
    My LabVIEW Version is 2012 f1. I remerber that I have done a lot of remove in the last year and works well on RT. Really don't know why it's not work this time. Even for a very simple diagram...

    I removed it's BD and put it under a PXI Real-time target. It says:
    "This VI has a bad connection to or cannot find a subVI or external routine but it has no block diagram to show or fix the error. You must find or correct the subVI or external routine. Check for more information in the Explain dialog box in Get Info."

  • Why Is the Block Diagram Disabled?

    What did I do now?  Please look at the attached image.  A VI that I am using as a subVI in various different programs suddenly started looking like I had used application builder to create an exe file out of it (But I didn't!!).  The only options are Start and Run Continuously, and the block diagram is disabled.  What did I do to get myself in this mess?  How do I undo whatever I did, so I can edit the block diagram again?  Any help or suggestions would be greatly appreciated.
    Thanks!
    Solved!
    Go to Solution.
    Attachments:
    Disabled Block Diagram.png ‏259 KB

    Did you ever built a source distribution with the option set to remove the diagrams? In this case, the original must still be around somewhere.
    Since LabVIEW 8 you can no longer simply save without block diagram and you would not be able to upgrade such a VI to LabVIEW 2011, which it is now. (details)
    Of course it is possible that there is some corruption, but looking at the memory usage, the block diagram is blanked out.
    LabVIEW Champion . Do more with less code and in less time .
    Attachments:
    NoBlockDiagram.png ‏38 KB

  • Probe windows disappear on Block Diagram

    Hi all,
    I came across an odd issue yesterday using the probes in Labview 2011. When I attach a probe to a wire and leave the probes inside the probe window they seem to work fine, however as soon as I launch the probes as separate windows, then click the title bar to move it to a convinient place they seem to disapear from the block diagram. Once this happens the probes no longer function and simply retain the values they had before they removed themselves.
    I have attached a couple of images to show what I mean:
    probe-window.jpg shows everything working as normal with the values in each probe acquired correctly.
    separate-window.jpg shows what happens when I launch the probe windows and try and move them. They disappear from the BD and no longer function as probes.
    Not a major issue I know but one I find very annoying as I like to move the windows to meaningful positions to clearly tell me which wire the values are coming from on the BD. I couldn't find anything similar on the forum so I don't know if I'm the only one with this problem, but it definitely did used to work!
    Any ideas?
    Attachments:
    probe-window.jpg ‏81 KB
    separate-window.jpg ‏98 KB

    I can't replicate the condition. Have you tried to run a repair on your LabVIEW installation?
    By the way, there is a much simpler way (and more scalable) approach to accomplishing what you are trying to do:
    Attachments:
    string to array.png ‏18 KB

  • Terminal images for arrays on block diagram

    I had always know that the thickness of the wire is representative of the size of the array on the block diagram (Thin wire, scalar, thicker wires, larger dimension arrays)
    I never noticed before that the terminal on the block diagram contained the [ ] symbols to indicate it is an array.  But also, the larger the dimension of the array, the thicker the brackets are, up to about 5-D.  (Probably because I rarely need a 3-D array, and large than isn't any practical, logical reason for a 4-D or larger array.)
    However, looking at the image of the terminal, the shaded area containing the outgoing or incoming triangle actually obscures one bracket or the other.
    While I wouldn't want the terminal to get any larger (which is why I don't like the icon view, it is way too large), it seems like the terminal should show both the opening and closing brackets to indicate an array rather than obscuring one.
    Any comments?
    Message Edited by Ravens Fan on 08-22-2009 12:59 AM
    Attachments:
    Example_VI_BD.png ‏3 KB

    Definitely keep the arrows. They are what tell me the direction of the terminals.
    As I was saying in another post, there is nothing intuitive about the thick border/thin border differences to tell whether the terminal is a source or sink. I like that they are a bit different, but if you put them side by side with no wires and no arrows, I couldn't tell you which was which.
    As for array size, as Christian says, if I want to know the type/dimensions of the array, I'll use context help. I just thought it was interesting (and I had never noticed it before) that the array size was encoded in the image as well.
    I myself wouldn't mind if the terminal grew 2 or 4 pixels wider, but I can completely understand how it would bother a lot of people.
    I think in the current image, too much is obscured by the arrow and its background, even for the scalar type. Actually, why is there a light background behind the arrow at all. That is the real source of the problem. Eliminate the background, and move the arrow over to the edge, and you can see everything without extra shading and without causing the terminal to grow.
    See below:
    1. Terminal size maintained.
    2. Direction arrow maintained, just slightly moved.
    3. Goofy shaded background removed.
    Message Edited by Ravens Fan on 08-22-2009 09:48 PM
    Attachments:
    terminals3.png ‏5 KB

  • Why do I get an Error Code 70229 when running Block Diagram ?

    Hi everyone,
    This error is very weird because at one time I got the block diagram to run and it worked well then when I tried it again after reopening the block diagram I got this error . 
    Can someone help me please ?
    I am using SolidWorks Premium 2014 x64 Edition.
    The attached files show the version I got for SoftMotion and for Labview 2013 32 bit installed . 
    PS. I had Labview 2013 64 bit installed but I removed it. not sure if any files remained that may cause this...
    Thank you,
    Isaiah 
    Attachments:
    Softmotion.JPG ‏54 KB
    Labview2013.JPG ‏55 KB

    Read related topic
    Thank you & Best regards
    syrpimp
    =======================================================
    “You must continue to gain expertise, but avoid thinking like an expert." -Denis Waitley

  • Is it possible to build exe with vis that have striped block diagrams?

    We can tell that an entity has stolen our code and are using them in their .exe file.  
    We used to distribute our program as a light exe layer that dynamically loads some source code distribution vis (block diagram striped) off disk and runs them.
    What we don't know is whether they actually got our in house source code, or if they are somehow taking the distributed vi's and compiling them into their exe.  
    So the question is: Is it possible to take vis compiled for a 'source distribution' with the block diagrams removed (but front panels not removed) and compile them into an executable?

    It's actually quite possible to use a source distribution VI for a new app. You need to select the "Do not disconnect type definitions or remove unreferenced
    members" option in the "Additional Exclusions" page.
    I've attached an example on how this can be done. Untitled Project 1 would be your project, which has a build target of your app, along with the source distribution for a VI with the block diagram stripped. Untitled Project 2 would be your competitor's project, which is a VI that uses your subVI directly and builds a separate application. As you can see, I can successfully build an application using your code.
    Attachments:
    source dist ex.zip ‏76 KB

  • Cut and paste from one block diagram to another?

    Is it possible to cut objects from the block diagram of one vi and paste them into the block diagram of another vi?
    Also, is it possible to "comment out" parts of a block diagram like you can in a text based program? That is, can you disable "code" on a block diagram without removing it from the diagram entirely?

    querty999 wrote: 
    As for training, I've got diploma's in Core 1 and Core 2 LabVIEW. I've worked numerous examples independently and read large part of several books. I'm living proof that LabVIEW ain't for dummies."Pictures and wires" programming doesn't click for me. Too many details to memorize.
    CVI is much easier to me than LabVIEW, maybe since I've been programming extensively in C for 20 years. But boss says we gotta use LabVIEW. It's the politically correct thing to do.
    Lots of LabVIEW advocates in management here. Few have done anything of significance with it. Some use Signal Express and call it LabVIEW. I guess they're technically correct. SE says LabVIEW on the splash page.
    You may be interested in this discussion: http://forums.ni.com/t5/BreakPoint/LabView-vs-LabWindows-CVI/td-p/400121

  • Block diagram for yahoo webcam viewer by activex

    sir 
    i wants to know how to make block diagram for yahoo webcam viewer in actvex controls. or are we able to see live video or face to face communication by it by using a normal usb webcam. or there is any other method so that we can live or face to face interaction. 
    mpsingh

    sir , i wants to download ni imaq usb driver from ni website i tried it many times in these 5 days but it is telling me that webpage is temperorly down or removed from this space if there is any other link then please provide me as soon as possible. i have labview 8.6 full version there was mostly all the drivers present except ni imaq usb driver.
    mpsingh

  • LabVIEW 2011 Block Diagram/Fr​ont Panel reacts slowly

    Since today the block diagram as well as the Front Panel of my application (using LabVIEW 11.0) became very slow. Any modification (add item, move item, scroll etc.) takes more than a second. Restarting LabVIEW helps for some time and then it becomes slow again. Restarting the PC did not help either.
    So, I tried to remove all items added today but the effect remains the same. When I try to close the Project Explorer LabVIEW does not react anymore (not responding). Very annoying.
    I tried also modifying the settings of the graphics card: nope.
    What do I do? Start the project again?
    Any suggestions except not using LabVIEW for further projects?
    Would be appreciated.
    Ben
    Solved!
    Go to Solution.

    BMajor7 wrote:
    Any suggestions except not using LabVIEW for further projects?
    seems to be funny
    Thanks as kudos only

  • Labview: Null Window ... stopped at unknown on the block diagram

    Hi,
    I have a fairly large program that was written in Labview 6.0. Recently we upgraded to Labview 9.0 and this program was exported to an executable with the new version.
    When running the executable I sometimes get the following error as seemingly random places. I have not been able to make it crash when not using the executable. Labview: Null Window. The top-level VI ".vi" stopped at unknown on the block diagram of ".vi"
    I apologise for having to blank out the vi names but i cannot give vi names, say what the software is used for or give over code. I can say that it uses NI USB 6212 IO cards, interfaces with Rhode and Swartz instruments and uses alot of file IO.
    I was hoping that someone could give me a hint on how to debug such an error. I have noticed that When this error occurs, the memory use almost doubles.
    Thankyou
    James 
    Solved!
    Go to Solution.

    I think you open the front panel of a VI that has it's front panel removed during the build. Try to adjust the built settings of that specific VI to include the front panel.
    Ton
    Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
    Nederlandse LabVIEW user groep www.lvug.nl
    My LabVIEW Ideas
    LabVIEW, programming like it should be!

Maybe you are looking for

  • Changing the size of a single field in runtime in table view

    Is it possible to change the row height to fit the entire text into the field for the column Exception text ? Is it possible to change the row height of the field exception text in run time, based on the amount of text it carries ?? Please suggest.

  • Not authorized when suspensing, but not when logged in from terminal

    Hi All, I have the following line in my inittab, to start an X server for the user "cedric" x:5:once:/bin/su cedric -l -c "/bin/bash --login -c /usr/bin/startx >/dev/null 2>&1" This works great, my X server is started during the startup of the rest o

  • Ever since upgrading to Lion I keep getting the error message "disk was not ejected properly."

    Ever since upgrading to Lion on my iMac G5 Intel Core 2 Duo, I keep getting the error message "disk was not ejected properly."  I have repaired permissions and reformatted my external LaCie 2TB USB hard disk, but the error continues.  I use this disk

  • Mac mini no longer connects to external monitor

    I had my mac mini connected to a LG HDTV and it worked great up until recently. When I know go to the external connection it says "signal not found". I then tried to connect it to the monitor on my desktop and that doesn't work either. I'm guessing t

  • Problem with iWorks attachments

    I recently purchased the latest version of iWorks so that I can send attachments to my iPhone 3G, but I have not been able to open any attachments saved in any of the iWorks formats (.numbers, .pages or .key). The files have the proper extensions and