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.

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 programmatically 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.html). 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 .

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

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

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

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 programatically

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

Block diagrams messed up: Win 7 or LabVIEW 1012?

Hi, Everybody --
We just got a new computer for the lab here, and I held off on installing LabVIEW 2012 until after the new machine was installed. All of our computers have been running XP until the new one arrived; it's running Windows 7, and it now has LabVIEW 2012 loaded.
The first time I opened a VI and looked at its block diagram on the new computer, I was floored by how lousy it looked. Icons wereoverlapping, constants and controls were misaligned, the font sizes had changed, and, in general, the whole diagram was a mess. I though it just might have been that one, so I opened others and they all look like they were put together by 5-year olds. (No, I can't drink at work.)
Is this a Windows 7 "feature" or something new with LabVIEW 2012? I haven't had a chance to install or work with 2012 on the remaining XP computer, so I can't do any comparisons here yet.
I have a LOT of VIs written now, and the thought of having to redo all of them so they're readable is giving me the bad kind of palpitations. Is there some way to fix this problem without slogging in and doing all of the realigning, etc., manually?
Thanks a million for your time...
Mark
Solved!
Go to Solution.

Hey, RavensFan!
Thanks for the quick reply. I was afraid it was something like that, but with nothing to compare it to, it was more of a shot-in-the-dark guess.
I've changed a bunch of my VIs already, but I'm thinking that I'll mess with the .ini file and see if it'll reset them, too.
I don't know if you remember, but you wrote to me last year and said that, if the Ravens went 15-1 and lost only to the Texans, that would be fine with you, as long as they got into the playoffs again. Well, you were just slightly off with the season record, but it turns out that you were aiming pretty modestly about the playoffs! Congrats, etc.!
They've been making a big stink here in Houston these days about Ed Reed's not being honest about his injury situation. Nothing is ever easy...
Thanks again for the quick reply (as usual!) --
Mark

LabView application hangs up when scrolling the block diagram

Hi all.
I attached you "Main.vi" that is part of my LabView project. I don't know what's going on, but when I scroll the block diagram to the maximum right, the LabView application hangs up. There are a lot of things in this block diagram because is an outline yet. My plan was to make it more structural, but now I can't do anything because this error don't allow me to edit the diagram.
Please, try to open it (ignore all the dependencies) and check if it hangs up also in your computer.
If it does, is there any way to recover it? It's really important for me because I don't have any backups since two weeks ago...
Regards,
Francisc
Hi all.
I attached you "Main.vi" that is part of my LabView project. I don't know what's going on, but when I scroll the block diagram to the maximum right, the LabView application hangs up. There are a lot of things in this block diagram because is an outline yet. My plan was to make it more structural, but now I can't do anything because this error don't allow me to edit the diagram.
Please, try to open it (ignore all the dependencies) and check if it hangs up also in your computer.
If it does, is there any way to recover it? It's really important for me because I don't have any backups since two weeks ago...
Regards,
Francisco
Attachments:
Main (v3.1).vi ‏257 KB

It didn't hang up on my computer, but it did make me nauseous, luckily I keep a bucket by my desk.
You might have video card issues. Try this: open the VI, and hit Auto Cleanup, then save. Close LabVIEW, reopen. If that does not work, try to get to the far right side by going to the Front Panel, and double clicking something that will take you there. If you get there successfully, use the disable structure to disable ~ 1/8 or more of the diagram on that side. Save, reopen.
Richard

Excel macro error after deploying in Weblogic

Halo,
I have written excel macros and it is working fine.
but if the same file if i try to open from hyperlink after deploying in Weblogic server , I get the error
"error occured initializing the VBA libraries.
If Microsoft Visual Basic for Applications (VBA) was not installed, or was set to Install on first use,
(advertised, or set to install on demand) you may receive this error message.
Depending on the mode of installation used and the rights of the user to change current settings,
it is possible to install VBA through Control Panel, Add/Remove Programs, Microsoft Office, Add or Remove
features. If Visual Basic for Applications is not listed as an installable feature of Office, the administrator
of your system may have disabled it so it is impossible for you to install it. If VBA is not installed,
it is impossible to run VBA applications/projects on this computer. "
1. Even though Excel VBA application is installed in my machine , why am i getting this error.??
2. I would like to know is there any way to open the excel file even though if the excel software is not installed in client machine??
Appreciate your help.
Thanks.

Hi,
I do not see any reason for this to not work.
Is there any difference between the preferences for RX and RXI. Please go to "edit" -> "Preferences" -> "Security(Enhanced)" and uncheck "Enable protected mode at startup".
Are you able to open any pdf from command line with the same command:
"C:\Program Files (x86)\Adobe\Reader 11.0\Reader\AcroRd32.exe" <<PDF_FILE>>
Thanks,
Amish.

Open Block Diagram After Deployment on a Non-LabVIEW PC

Similar Messages

Maybe you are looking for