Open Block Diagram in Subpanel

In LV 8.6, when a VI is embedded into a subpanel on another VI, when you right-click on the panel of the embedded VI and select "Open Block Diagram", nothing happens. In LV 8.51 and LV 8.21, using the same code, the procedure opens the block diagram of the embedded VI, as it should. I think it's a bug, but I don't know where else I can report it.
Sergey Liberman

Andrew, Attached are two LLB's - same code, one in v.8.5, the other in v.8.6. Run mainVI.vi (in matching version of LV), right-click in the subpanel and select "Open Block Diagram". In LV85, the diagram opens, in LV86 it does not.
Regards,
Sergey
Attachments:
SubpanelBugV85.llb ‏37 KB
SubpanelBugV86.llb ‏27 KB

Similar Messages

  • How can i avoid to see the source code when any user open block diagram third time without password

    i have a probelem regarding source code control. my problem is that  when user open block diagram of any sub vi in vi. i would like to make a such a vi which source code can not open after seeing the block diagram thrice time and i dont want to make password to see the block diagram so what can i do ?
    give me the perfect solution for this type of problem.

    First protect you diagram
    create a tap on your FP and create a picture of your diagram and put it on the second tap
    DON'T expect answers if you only want perfect one's
    Greetings from Germany
    Henrik
    LV since v3.1
    “ground” is a convenient fantasy
    '˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'

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

  • Opening block diagrams directly

    The default behaviour for LabVIEW when one double clicks on a subVI in a block diagram is to open its front panel. For a variety of reasons, this is undesirable. Is it possible to open the block diagram directly without having to look at the front panel ?
    When you are debugging code, the default LabVIEW behaviour is, how do I put it, extremely irritating ?

    Plus, these ideas exist:
    http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Directly-open-VI-s-block-diagram-from-project-window/i...
    http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Block-Diagram-default-window/idi-p/972620
    http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Be-always-able-to-open-block-diagram/idi-p/917601
    http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Allow-ONLY-the-Block-Diagram-to-be-opened-Without-Fron...

  • Close front panel but leave open block diagram

    Is there a way to do this? I would like to have my block diagrams of a few subvi's open but front panels closed so my task bar isn't so cluttered. It's not a big deal, I was just curious
    CLA, LabVIEW Versions 2010-2013

    Chris_VH wrote:
    No current way unfortunately.
    A colleague and I actually just put in a product suggestion for this yesterday.
    So if they fix this do I give you or them credit for the solution?
    CLA, LabVIEW Versions 2010-2013

  • 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

  • How to open block diagram of daq's example of NIDAQ6.9.3 in labview7.1

    i use Daqcard-1200, which only supported by 6.9.3 version. so I only can use 6.9.3's daq function, I can open front pannel, and dont know how to open therelated block diagram.
    Thank you

    I completely agree, gosh!
    Napoleon
    "Too bad, she said she doesn't want you here when she gets back because you've been ruining everybody's lives and eating all our steak!"

  • Automatically open block diagram on extended monitor?

    Hello,
    I was wondering if anybody know how to pop-up the block diagram on an extended monitor automatically so that ctrl+E need not be pressed to shift between FP and BD. It would be nice to see FP on monitor 1 and BD on monitor 2(ext). applicable to opening any number of VI/subVIs. (not needing to drag window to ext monitor either)
    Thanks in advance,

    See page 2 of this thread: http://forums.ni.com/ni/board/message?board.id=170&thread.id=102680&view=by_date_ascending&page=2

  • 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

  • Nugget: Open block diagram programati​cally

    There are a way to open a block diagram programatically. Exists a undocumented function located in
    "%Program Files%\National Instruments\LabVIEW 8.6\vi.lib\Utility\sysinfo.llb\Set Block Diagram Open.vi"

    My good old 7.1. (ok, I run that in hyper-boost mode ) has a property node 'VI.Block Diagram Window.Open'. Should be available for anyone and documented in 2010.
    Felix
    www.aescusoft.de
    My latest community nugget on producer/consumer design
    My current blog: A journey through uml

  • Open Block Diagram After Deployment on a Non-LabVIEW PC

    Hello all,
    I have a application created in LabVIEW which will be deployed on a PC which does not have LabVIEW Development System installed in it, but only the RTE. With this application, I am also deploying the dependent VIs in a separate folder.
    My question is, is there any way we can open the BD of these dependent VIs in Highlight Execution mode on such PC with no LabVIEW Development System installed? I just want to view the BD of the VI in highlight execution mode, I don't want to edit/make any changes to the VI. Then obviously, we would be needing the LV development system.
    Since I've left block diagram (allow debugging) option enabled before deployment, I hope there must be some way we can acess the BD in highlight execution mode. I know that BD get image property works in PC with no LabVIEW Development system installed, so there must be some way or other to access the block diagram in highlight mode.
    Can anyone try to help in this?
    Thanks in advacne!
    -FraggerFox!
    -FraggerFox!
    Certified LabVIEW Architect, Certified TestStand Developer
    "What you think today is what you live tomorrow"

    You can't do it on a PC without the development environment.  If you have debugging enable in the .exe, you can connect to it remotely over the network from a PC with the development environment to watch the execution.  Look for "remote panel connection" under the tools menu.

  • Crash when opening Block Diagram

    I am converting a Windows .dll based program to an event driven state machine using my Mac (LV2010) as a development computer.  The final program will run in the development environment on a Windows computer.  When I reach a certain point in the conversion process, the VI will crash LV while trying to open the block diagram.  The VI is broken and always has been because of the .dll and possibly because of some bad wires.  I tried rebuilding the VI from scratch and the same thing happened again.  I can open the diagrams of the subVIs with the CLFN calls.  The .dll file is present on the same directory as the VIs.
    Clues: 1. I have had this happen when first opening the BD after restarting LV.  Maybe this means I need to work all night and finish everything before shutting down LV??
    2. I started with an example VI and was modifying it to include the state machine.  Maybe I should build a state machine VI and then add in the camera-specific parts later.
    I am attaching a zip file with the VI "testNewCamera.3.vi" and various subVIs, typedefed controls and the .dll.  I am also attaching the crash log file.
    This has now cost me too many man-hours so I am looking for suggestions.
    I am going to save several interim versions the next time I restart this process.
    Thanks,
    Lynn
    Attachments:
    OpenBDcrash.zip ‏384 KB
    lvmaccrashlog2010-11-10-10-44-33.txt ‏34 KB

    Hi,
    The first thing I try to do when I get a VI (FP or BD) corruption/ issue when opening / crash / whatever...is to mass compile all the VIs I have. Sometimes it works, sometimes not.
    I was able to open the BD of TestNewCamera3.vi but I am missing a lot of IMAQ VIs and LabVIEW is telling me that a DLL is missing (maybe it is what is causing the crash in your case).
    I join the files saved on my computer, maybe you could use it.
    Regards,
    Da Helmut
    Attachments:
    Dossier testNewCamera.3.zip ‏48 KB

  • How to lock block diagram alone from editing leaving front panel for editing?

    i want to lock block diagram from editing but front panel can be edited for creating controls, moving controls editing properties...

    executables will be delivered to customer and they can create new vi and edit frontpanel and link tag through databinding. but i dont want them to open block diagram...
    Natasftw is right - you seem confused about the difference.
    If the customer can "create a new VI and edit frontpanel" then they have to have LabVIEW Development System.
    If you give them an EXE, and they don't have the DevSys, then they can use your VIs, but not edit them or look at the code.
    If they have the DevSys, then they can edit your VI and look at the code, UNLESS you protect it.
    If you save a VI with protection (VI PROPERTIES - PROTECTION ) then you can LOCK it (user has to explicitly unlock it with an extra step), or you can PASSWORD PROTECT it (user has to explicitly unlock it by giving a password).  Either way requires the DevSys.
    There is no situtation where one can edit the front panel without being able to edit the block diagram.
    Steve Bird
    Culverson Software - Elegant software that is a pleasure to use.
    Culverson.com
    Blog for (mostly LabVIEW) programmers: Tips And Tricks

  • Block diagram wont open properly

    I have written a big labview program for my application. I have been workig on it for 6 months. I keep adding the peice of code every day and save it with a new name every week.
    At one point when I added some code into my program, the block diagram started acting weird and wont let me work on the program easily. For If I add an add function, it would take time and insert this function a couple of inches away where I pionted my cursor. Another issue was that; if I add a while loop or for loop or any other structure it would take time and one added it would add a couple of inches away and expand the main program window (Block Diagram) too.
    since then, I started using my company's laptop to develop the code. I have no issues with that lap top till today.
    But now when I tranfer this program back to my desk top. It wont open the Block Diagram and wont let me edit it. When I try to open the block diagram. the window appear black out and the LabView stops working.
    Is this issure ralted to the graphics of my compute or any thing else? Please help me. Thanks
    Mansoor

    There is a maximum size that a VI can be. What that exact size is I don't know. It does sound like you have one HUGE VI. If that is the case you really need to think more about using subVIs. It will make your program much easier to maintain and extend.
    Also, rather than renaming it once a week you should consider using source code contol. Even if you are the only developer it is a much better way to manage your code. SVN is free and very easy to set up. If you do use source code control make sure you separate the compiled code from the source code. This is an option in the VI properties.
    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

  • 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

Maybe you are looking for