LabVIEW 2011 Block Diagram/Front 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

Similar Messages

Problème de blocage écran block diagram et front panel

Bonjour,
Je ne sais pas pourqoi, après avoir chargé Labview 2013 (après avoir utilisé LabVIEW 2012 SP1), dès que j'ai un block diagram ou front panel sur l'écran, je n'arrive plus à les manipuler après la première action.
Pour y arriver de nouveau, il faut que je réduise toutes les fenêtres LabVIEW puis que je réactive celle qui m'intéresse. Je peut alors faire une seule action puis il faut que je recommence l'opération de réduction-agrandissement.
Où est l'erreur, dans Windows (7), dans LabVIEW, dans une commande qui s'est mal faite ?
Le problème ne se résouds pas si je redémarre mon PC.
Peut-être faut-il que je désinstalle et que je réinstalle tout.
Quelqu'un a-t-il déjà renconté ce problème ?
Merci pour vos réponses.
JPV67

Bonjour et merci pour votre réponse.
J'essaie de me dépatoiller de ce problème avec l'aide du service support [(Reference#7411882) Phone Support E-Mail].
Malheureusement l'opération de désinstallation et de réparation qui m'a coûté 4h n'a pas abouti car j'ai toujours le même problème.
Pour simplifier cela commence par ça :
c'est l'écran d'accueil de LabVIEW.
Si j'attends quelques instants avant de cliquer sur CLOSE de la fenêtre WELCOME to LabVIEW, je ne peut plus le faire !
Même l'activation de la croix X de fermeture de cette fenêtre ne marche pas !
Pour y arriver, il faut alors que je réduise cet écran puis que je le restaure et seulement alors je peux fermer cette petite fenêtre !
Par ailleurs j'ai ce phénomène :
Je ne sais pas pourquoi, après avoir chargé Labview 2013 [Version 13.0.1f2 (32 bits)] sur Windows7, après avoir utilisé LabVIEW 2012 SP1 sans problème, dès que j'ai un block diagram ou front panel sur l'écran, je n'arrive plus à les manipuler après la première action.
Pour y arriver de nouveau, il faut que je réduise toutes les fenêtres LabVIEW puis que je réactive celle qui m'intéresse. Je peut alors faire une seule action puis il faut que je recommence l'opération de réduction-agrandissement.
J'ai en fait le même problème avec la page d'accueil de LabVIEW qui devient inactive après la première action.
Cela se produit sur le PC fixe.
J'ai une licence site Université qui a été enregistrée.
En espérant que vous aurez une solution...Cordialement,
JPV67

Block diagram, front panel messed up

Why do block diagrams and front panel controls get bunched up and screwed up when you open vi's on different computer with different labview versions.
Can anything be done to prevent this?
Does everybody have this issue?
Thanks,
Dustin

You can _try_ to address this issue by right clicking on the vi's icon when it is open in the edit mode, select "VI properties", select "Window Size". Under this selection there are two selections that _may_ help, they are supposed to partially address the issue you are describing. I never had much luck with them in the past, have to admit I have tried them in a while, try to find out what the target system's resolution is and develop the code in that resolution.
Putnam
Certified LabVIEW Developer
Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5
LabVIEW Champion

LabVIEW exits while editing block diagram unexpectantly

Hi all, while editing block diagram in LabVIEW 2010, I have experience some strange behaviour from the software. I have two monitors, one has the front panel of main VI and the other - block digram of the specifed VI. When I switch from block diagram to front panel, and vice versa, every now and then the LabVIEW exits unexpectantly without the notice. Upon restarting the program again I get the undo.cpp error. I have attached the error log for my clarification on the type error that I am dealing with. Does anyone have any ideas why this is occuring? Thanks in advance for your help.
Viktar
Attachments:
lvlog2010-09-17-09-35-46.txt ‏2 KB

Thanks for all the responses.
I was using an existing VI as template to create a new program. There were nested loops in the original program and I needed the logic for the outter loops only for the new program. After deleting many objects in the 'yes' case in the inner loop, I was left with many loose wires in the 'no' case. And that's when my problem started, when I was trying to delete them. Yes, I tried rebooting my PC and that did not help. The problem seemed to get progressively worse, as crashing started to happen even when I was only selecting a wire. But somehow I was later able to select one wire, delete it, and did a save. Then I went to the next wire, and so on. My program is now cleaned up and I'm ready to go on. I will experiment more when the problem returns.
Thanks again.

Exporting block diagram image

Hi
I'm in the middle of writing a report that discusses the LabVIEW program I've been working on, I was wondering how I export an image of the block diagram and front panel to include in my report? I hoped it would simply be a case of copy and then paste into clip art or similar but LabVIEW only lets you copy individual objects.
Please help!

I prefer to simply get the FP and BD image using invoke nodes. The attached simple demo (LabVIEW 7.1) will ask for a VI, then create PNG images of the front panel and block diagram of any VI you select. The image of it's diagram below was just created with it.
Modify as needed!Message Edited by altenbach on 06-02-2005 05:54 PM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
GetVIImages_BD.png ‏9 KB
GetVIImages.vi ‏60 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

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

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.

Bug: Front Panel objects relative position change when placing merge VI onto Block Diagram

I've posted a bug report on LAVA, here:
http://forums.lavag.org/Front-Panel-objects-relative-position-change-when-placing-merge-VI-onto-Bloc...
If someone at NI can reproduce, can I please get a CAR #?
Thanks,
-Jim
Solved!
Go to Solution.

Donovan B wrote:
Hi Jim,
After my previous post, I also saw this behavior, so I decided to do another test. If there are no decorations in the VI set to “Merge VI” (“Place VI Contents” for LabVIEW 8.5 and later) the controls and indicators are still not selected when dropping the VI from the Functions palette. I checked this behavior back to LabVIEW 7.1 and it is consistent throughout that controls and indicators are not selected. (Consequently, so is the fact that when decorations are present they don’t maintain the relative position).
I am not sure if this would be better suited as a CAR or product suggestion since it has been this way that long, but it does not appear to be related to the fact that decorations are present in the Merge VI. It does seem strange that the decorations are selected though. Looks like the best way to work around this is to drop the VI from the Controls palette. Hopefully, it’s not too much of a hassle.
Hi Donovan,
Thanks for checking in.
> I checked this behavior back to LabVIEW 7.1 and it
is consistent throughout that controls and indicators are not
selected. (Consequently, so is the fact that when decorations are
present they don’t maintain the relative position).
This just means that not many people use this feature. However, now that VIPM Professional makes it so easy to edit the palettes, I'm sure that others will start complaining that this doesn't work as they expect.
> I am not sure if this would be better suited as a CAR or product suggestion
since it has been this way that long, but it does not appear to be
related to the fact that decorations are present in the Merge VI.
Just look up the functional specifications for this feature and see if all objects are supposed to be selected.
But seriously, is there a reason that only the FP decorations are selected? Surely this would be documented somewhere, if there was a good reason for this current (IMO, buggy) behavior.
> It
does seem strange that the decorations are selected though. Looks like
the best way to work around this is to drop the VI from the Controls
palette. Hopefully, it’s not too much of a hassle.
That's not a reasonably work-around, IMO. It doesn't make sense to drop Block Diagram components onto the Front Panel. For example, this bug affects the JKI State Machine. It doesn't make sense to drop a State Machine onto the Front Panel.
So, I'd file it as a CAR/bug, and then wait to see how LV R&D feels about it. If they can find some valid reason for why Controls and Indicators shouldn't be selected, then that's fine (and hopefully someone will explain it to me).
Thanks,
-Jim

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.

What is the best way to keep the block diagram/ front panel clean?

Hello,
I am relatively new to Labview so I'm not able to tell if I'm overcomplicating my programs or making my block diagram too cluttered. I was wondering if there were some ways to tell whether I could simplify my programming just by looking at it (perhaps only experience helps for these things) ?
I have attached my VI here. Currently, it has the capability to monitor the voltage and current from two motors. On display, you can see a indicator with the voltage and current values and there are charts toward the bottom that can display waveforms from different motors with a drop down menu.
The front panel is rather clean in my novice opinion, but the block diagram seems messy to me, just at first glance. I foresee a problem occuring in the future however. In the future, I will have to scale the VI to monitor 50 motors. All the programming will be the same as the one I have now, except it will have 50 indicators and unfortunately 50 times pretty much everything. I would like to avoid this, but I'm not sure how I could.
I am using a USB 6009. I am using its four differential inputs to monitor the voltage and current of two motors. In the future, I will be getting more DAQ units (25 total because 2 motors can be monitored for each DAQ). The new DAQs will help will help with more resource space, but I think complicate things with the additional potential of 24 more DAQ Assistants (as used in my code).
Thanks for any help you might be able to provide!

It usually is mainly experience that will teach you the best methods to make your code look pretty. I don't know anyone who is proud of their first from-scratch application. There are a few resources out there to help with best practices, like this group on ni.com, but you'll learn the most from your own development.
Your front panel looks great. FPs in general are really up to you. You can make it look as ugly or pretty as you want. When you have some duplicate controls and indicator groups, you should utilize clusters and arrays to simplify. You could use a little bit of cleanup in that regard, but not much. Also, personally, I hate reading red text unless it's a warning of some sort.
Your block diagram could use some cleanup in a modularity sense. You have a lot of repeated code, which you could consolidate in to a subVI that is used in multiple locations, or in a For loop. A general rule of thumb is to keep your block diagram within a single monitor. You shouldn't have to scroll. Your application is pretty simple, so it's hard to mess it up
Here are some specifics about your block diagram:
Right click your terminals on the block diagram and uncheck "View As Icon". You're welcome.
Duplicate operations on each waveform "(x*2-4)/16": create subVI and/or run the waveforms through a For loop.
You do a lot of 2-element arrays and then indexing. Just replace those with a Select node based on the numeric.
All of your code is running every time, including your property nodes at the bottom, which is unnecessary. As you learn LabVIEW architectures, you will learn how to bypass this with initialization and exiting code, but for now you should put a case structure around those for only when the motor numbers change.
I'm not sure how you're timing your main loop, but you should put a delay in there because you don't need the DAQmx node to be pulling as fast as your CPU will allow.
There are free intro videos you can watch to learn what NI would suggest in terms of coding and teach you some of the basic features and such. Here's a three hour course, and here's a six hour course.

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

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 make Microsoft Wireless Intellemouse Explorer 2.0 horizontally scroll my LabVIEW block diagrams using the tilting wheel?

I bought this expensive mouse in high hopes that I could use the tilt wheel left/right to scroll horizontally, but it does not do it! Vertical scrolling works great. LabVIEW 7.0. Please help! I'm tired of going to the horizontal scroll bar on my block diagrams!

This doesn't exactly answer your question, but if you use the auto tool, press and hold and you get the Scrolling Tool. That will let you drag the diagram or panel around quickly.
Ed
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

Image of the front panel and block diagram

Hi,
I need to get some info from the block diagram but I don't have labview in my computer. can some one please open it and post a picture of both front panel and block diagram.
It may not open properly, but that is okay.
Thanks,
Sujay.

Here you go

LabVIEW 2011 Block Diagram/Fr​ont Panel reacts slowly

Similar Messages

Maybe you are looking for

LabVIEW 2011 Block Diagram/Front Panel reacts slowly