Show block diagram programmatically?

I'm almost sure that I did this once and then took it back out.  (the "show block daigram" case in the Menu Selection choice of an event structure is still in my code).
Anyway, I often start a program that runs for hours and then realize that I need to open subVIs or probe some wires.  Since these programs have run-time menus I don't have the option to open the diagram once the VI is running.  Is there a way to programmatically open the block diagrams window when a VI is running? 
Thanks,
K
Message Edited by NIquist on 09-20-2007 03:39 PM
Using LabVIEW: 7.1.1, 8.5.1 & 2013

Shhhh......
Its a secret.
But now that you know then you can appreciate the beauty of these items.
The ini used is one of the few time that LabVIEW programmer cares about proper syntax.
OR (to take this analogy way to far)
It is THE "G-String"
Ben
Discalimer: I am a Premium LAVA Member
Message Edited by Ben on 09-21-2007 07:26 AM
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction
Attachments:
G-String.jpg ‏40 KB

Similar Messages

  • Measurement & automation 4.7 / show block diagram?

    Bonjour,
    J'ai utilisé l open VISA test Panel pour le test d'une liste de commande de pilotage d'un instrument via le port rs 232, et maintenant j'aimerais affiché le block diagram de mon test (i.e le .vi du test).
    Meme avec le NI-Visa, je tombe sur  la meme fenetre. je n'y arrive pa avec cette version de MAX (4.7.7.f0).
    D'avance merci.
    Résolu !
    Accéder à la solution.

    Bonsoir,
    Je ne suis pas sûr d'avoir bien tout compris. Vous vouez réaliser la fonction sous Labview qui permet d'envoyer les commandes via le port RS232, des fonctions que vous avez testez via NI VISA?
    Le code ne va pas se faire automatiquement. NI VISA vous permet de vérifier que vous communiquer bien avec l'appareil, et de récupérer la réponse a une commande spécifique. Une fois que cela est assuré, vous pouvez coder lesdites commandes. Je n'ai pas Labview d'ouvert actuellement, mais de mémoire ca doit être dans la même palette que pour les commande GPIB,...

  • Turn off showing block diagram on pause

    Hello,
    Is there a way to disable the block diagram popping up when I pause a running VI?

    No, there is no possibillity.  But why do you want to pause it?
    There are many ways to let your program go into idle if you want to without pushing the pause button.
    Pause, highlight execution, stepping are debugging tools of labVIEW and most of the time in debugging you want to see the blockdiagram to see what is going on.
    Kind regards,
    - Bjorn -
    Have fun using LabVIEW... and if you like my answer, please pay me back in Kudo's
    LabVIEW 5.1 - LabVIEW 2012

  • How can I open a vi and show the block diagram?

    Hi,
    I am opening an vi using "Open VI Reference" and "Invoke Methodpen FP", but I want to open the vi and show the block diagram, but I haven´t found any method (Invoke Method) to do that and any property.
    Any idea?
    Thanks!
    Gracinda

    OK, I can come up with a reason.  I have written a program that will search the entire VI Hierarchy of a program and update all of the descriptions for all VIs with the top level program part #, the name of the top level program that the VI is used in, the company copyright info, the ITAR notice, company address, the name of the engineer performing the update, along with the date and time.  This will also place as a background image on all the VIs, a watermark of the company name, legality stuff and the copyright. It works very slick in that if there are thousands of sub-vis, such as what I'm working on now, it goes through all of them, makes sure the data is there as per company policy without having to open every one of them look at them and update or not whichever the case may be. The one portion that is tough is that the program will detect if there is a description written about what funtion the VI performs and if there is not a description, then it pops up a dialog requesting the user to write a description. The problem is that without looking at the block diagram for the VI, it can be nearly impossible to write a description for the functionality of the VI. So is there a way to programmatically open a VI, show its block diagram (this would only be in the case of a missing description) and then upon completion of the updates, close the block diagram? (I already open and close the VI programmatically in order to read the VI DESC and update as needed, but that is in the background and of course you can't see the block diagram).
    Thanks,
    Dan

  • How do I programmat​ically open block diagram?

    Hi, All
    How do I programmatically open block diagram of subVI and add frame to event structure
    Thanks,

    Could you be a bit more specific on what you are trying to do?
    Do you want to programmatically edit an existing VI that is currently not running? As mike said, scripting could work but it is unsupported (see the Lava scripting forum for details: http://forums.lavag.org/LabVIEW-VI-Scripting-f29.h​tml). Somehow, adding an event case does not give you much, you would also need to add the code contents and hook everything up to the existing controls, indicators, and other nodes.
    If you just need an event that is not always active during run, maybe you can use user events. Check the online help. (Also have a look at e.g. section 4 in the following application note:
    http://zone.ni.com/devzone/cda/tut/p/id/2994.
    LabVIEW Champion . Do more with less code and in less time .

  • I am trying to create an executable vi that will call out another vi and show its front panel in the executable​. When I try this I recieve this error message "top level vi (my main vi) was stopped at unknown on the block diagram of (my sub vi)

    I am trying to create an executable vi that will call out another vi and show its front panel in the executable.  When I try this I recieve this error message "top level vi (my main vi) was stopped at unknown on the block diagram of (my sub vi)

    Well the most common way is to enclude the vi's in the build spec either directly in the dependancies that the App builder automatically generates OR by declaring them in the build spec as "additional enclusions" (like you must do for dynamic vi calls in your app.
    I have heard rummors about My.app Stuff.vi in a nugget Intaris posted- and I've wanted to dig deaper into Intaris' claims- but have not tried it myself.
    If you go down the stuff.vi route Keep us curious guys posted
    Jeff

  • Hot to disabled the "Block Diagram to show" for other users?

    Hi,
    I am doing a LabVIEW program that other persons may use.
    I need them NOT to be able to access the "LabVIEW Block Diagram" (by doing e.g: Ctrl + E).
    How can I do this?
    Kind regards,
    Amaloa S.

    Hi Amaloa,
    You could achieve this by:
    - Click File (on your front panel) > VI Properties
    - On the Category drop down list, click Protection
    - Select Password-Protected
    - Enter New Password and varify it again
    Regards,
    CLA | LabVIEW 7.1... 2013
    www.renishaw.com

  • Why cannot the block diagram view of a VI show the "connector pane" view in the UR corner, like the front panel view does?

    Perhaps there is a good reason for this that I just haven't figured out. I haven't seen any questions about it searching the NI site, however.
    But it just seems totally inconvenient to always have to go to the front panel to get to the connector pane view, especially if some of those connectors are hidden. Then I have to go to the block diagram, guess which control/indicator I want to unhide, go back to the FP to check it on the connector pane, then go back and hide it again, and repeat if necessary. Even if the C/I is visible on the FP, it's still an extra step or two.
    When I'm building connections using the block diagrams and planning where to put connectors in subVIs so they would be easier to wire up (line up inputs/outputs on sides, not have to go top-to-bottom, etc.), it sure would be nice to be able to work totally in the block diagram realm.
    Cameron
    To err is human, but to really foul it up requires a computer.
    The optimist believes we are in the best of all possible worlds - the pessimist fears this is true.
    Profanity is the one language all programmers know best.
    An expert is someone who has made all the possible mistakes.
    To learn something about LabVIEW at no extra cost, work the online LabVIEW tutorial(s):
    LabVIEW Unit 1 - Getting Started
    Learn to Use LabVIEW with MyDAQ
    Solved!
    Go to Solution.

    Yamaeda wrote:
    Good idea, put it in Idea Exchange!
    It has been there for a while already. No need to duplicate....
    LabVIEW Champion . Do more with less code and in less time .

  • How can I display Execution Highlighting if it does not show up on my block diagram?

    I am using a baseline program provided with my zaber translational stage to write a more sophisticated program for the stage.  I have noticed that the execution highlighting icon is not in the block diagram.  I have been able to turn on the stop button which originally wasn't there during running, but I cannot find the option to turn on and off the execution highlighting icon.  Thanks for the help.
     Bigga

    Most likely debugging is disabled in the VI execution properties.
    Why do you need the stop button?
    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!

  • How do I get the Label for a Front Panel Control to appear in the Block Diagram but not on the Front Panel?

    How do I get the Label for a Front Panel Control to appear in the Block Diagram but not on the Front Panel? On the Front Panel I am making a complex control that consists of a Slider and a Numerical Input box. Both Controls display the same information and either can be used for Input. When one changs, the other is made to display the same value.
     But I only want the Slider to display the Label on the Front Panel, to avoid confusion. On the Block Diagram however, I want both controls to display their Labels so that I know what they are. How do I display the Label for a Control on the Block diagram, but not display its Label on the Front Panel?

    No.  The Label Visible property is separate for the front panel control label and the block diagram terminal label.
    How did you start out with the block diagram's label not being visible?  Whenever I drop a control or indicator, the label is always visible on both the FP and BD by default.  Maybe there is a LabVIEW option that causes new controls/indicators not to have their labels visible by default, but I have yet to find it.  I don't think an item should ever be dropped without the label visible, good LabVIEW coding practice demands that the labels for control terminals on the block diagram be visible so that you know what control or indicator a wire is going to.
    That being said, I have seen a lot of VI's posted where the label for the terminal on the BD is not shown (against good programming practice.)  I've gone to the BD and right clicked to show the label.  Sometimes, the people have an empty label (which will turn off the visibility for both the FP and BD) and I'm forced to add some text of my own into the label so I can figure out what their code is doing.  When I add some text to the label, at that time, I find both the BD and FP labels become visible.
    Are you dealing with controls that have empty labels to start?
    Good programming practices:
    1.  Always have a name for all of your controls, never use and empty label by deleting the text in the label.
    2.  Make the labels unique.  For example, don't have two controls both called Stop.  How do you know quickly know which terminal relates to which control?
    3.  Always show the labels on the block diagram, so you know the function of a control's terminal.  If you want to hide the label on the FP, that's okay.
    4.  If you want a different label to appear on the FP than whatever you actually called the control, then use the caption.  You can hide the label and show the caption.  This is useful if you need to programmatically change what the "label" is on the front panel such if you are making an application that needs to change its user interface such as for a foreign language.

  • DISPLAY NAME, BLOCK DIAGRAM

    I am new to LabView and our teacher has given us a very small assignment in which we have to create a program that displays a name that I have input.  I am also required to show him the block diagram. 
    Any help plz?

    Given that this is essentially the "Hello World" program written in LabVIEW I suggest you try a few things on your own first. I doubt anyone here will post the code since it is a homework assignment and it is a very easy one at that. Take a look at the examples that ship with LabVIEW.
    Mark Yedinak
    "Does anyone know where the love of God goes when the waves turn the minutes to hours?"
    Wreck of the Edmund Fitzgerald - Gordon Lightfoot

  • Can I just open block diagram only

    Like I can have only front panel opened. Reason is when I have bunch of VIs
    open, I get too many windows to manage even while using 2 monitors. It will
    be nice if I can just have the window for block diagram open, if I need the
    front panel while editing, I can use Ctrl+E to open it. I know I can
    minimize but then all LV windows look same on task bar. Would be nice if
    icon of the VI showed up on taskbar buttons of each VI.
    vishi

    You can use lvwutil/Hide window.vi to hide the front panel.
    This method has been around for years.
    vishi anand wrote:
    > Like I can have only front panel opened. Reason is when I have bunch of VIs
    > open, I get too many windows to manage even while using 2 monitors. It will
    > be nice if I can just have the window for block diagram open, if I need the
    > front panel while editing, I can use Ctrl+E to open it. I know I can
    > minimize but then all LV windows look same on task bar. Would be nice if
    > icon of the VI showed up on taskbar buttons of each VI.
    >
    > vishi

  • Cannot open block diagram

    I opened a VI I recently created and when I try to open the block diagram its greyed out. doing Ctrl I and selecting Protection shows file as Locked(no password) and all options to unlock are greyed out. Any ideas how I can sort this out?

    You appear to have done everything right.  I doubt that being on the network would be a culprit. 
    You've probably mapped the drive, right?
    Did you even save it with the Locked property?  
    I am wondering if someone else had access to one of your PC's and played a trick on you.
    I tried a test VI and I can open the block diagram.  See image below (composite of 2 images)
    Message Edited by Ray.R on 11-20-2009 10:31 AM
    Attachments:
    locked.PNG ‏37 KB

  • Is Block Diagram Open

    Is there a way to tell if the Block Diagram is open when a VI is started?  I have a subVI that is set to modal when open.  When trouble-shooting, if I run my application, but forget to disable modal for the subVI it causes the system to lock up.
    It would be nice if I could set the property of the VI to not be modal if the block diagram was open.  
    Any suggestions?
    Solved!
    Go to Solution.

    I would attempt this by doing several things:
    1) Go to the VI Properties>Window Appearance and click on the Customize button. From there uncheck the "show front panel when called" box.
    2) When the VI starts, read the VI Property "Front Panel Window.State" - this will tell you if the window is already openned (ie if the window is openned the window state will be "standard", "Maximized" or "Minimized"). Note: this is the visibility of the front panel, not the block diagram 
    3a) If the VI is not already opened, set the "Front Panel Window.Behaviour" property to modal and then open the front panel using the VI Invoke Node of "Front Panel.Open". This is basically mimicking the behaviour you describe right now.
    3b) If the VI is already opened, set the behaviour property to default or Floating to allow you to click other windows.
    4) When finished, if the VI was not already openned, manually close it using the Front Panel.Close invoke node (if it was already openned, leave it openned) 
    I've attached a screen shot of this kind of thing. I hope this helps,
    Shaun 
    Attachments:
    Reading and Changing Front Panel Behaviour.png ‏39 KB

  • Charts and graph shown as --array and cluster datatype in block diagram

    Hi friends,
    I new user...
    I have a basic doubt...
    In many examples the graph and charts are shown as "array data type and cluster data type "------in the block diagram panel...
    Please tell me, how these data types are shown as graph and charts in the front panel window.....
    regards
    raja

    These are very basic issues and it should be clear once you study the online help and examples for a while.
    Waveform Graphs
    Plain waveform graphs assume equally spaced data. The x-values are implicit from x0 and dx of the x-axis. By default x0=0 and dx=1, meaning the x-values are the array indices. You can change the offset and multiplier from the properties dialog or programmatically via property nodes.
    If you give a 2D array, there will be multiple graphs. Transpose if needed.
    Alternatively, you can give a cluster of [x0, dx, y-array] and the x-axis will adjust accordingly.
    As another alternative, you can built a waveform datatype and feed it to the graph.
    You can also graph dynamic data.
    XY graphs
    xy graphs are needed if the x-vlaues are not regularly spaced.They take a variety of data formats, so pick what is most approriate for the data
    A cluster of an x-array and a y-array
    An array of clusters, each containing an xy pair
    A complex datatype (it will graph imaginary vs. real or similar).
    Charts
    Charts are different, because they maintain a data history buffer an retain a certain amount of data. Some examples of data inputs:
    A single scalar: it wil be appended to the existing chart data, possibly throwing out the oldest existing point.
    An array: The array data will be appended to the existing chart data.
    A cluster of e.g. 5 points: The chart will have 5 dividual plots, one point gets appended to each plot.
    etc.
    The express xy-graph can be configured as xy chart, etc.
    Sure, it is a bit complicated at the beginning, but the complexity also gives you flexibility to do exactly what you want. Just play around with various scenarios and look at the outcome. The best way to learn!
    LabVIEW Champion . Do more with less code and in less time .

Maybe you are looking for