Can't edit block diagram.

I had been running TestStand and had finished the test and stopped TS. I needed to edit a subVI, one that is several layers deep in the calling sequence. When I try to edit it the white hand appears and I cannot make changes. So I close all sequence files as that usually frees the VI. No good. Close TS, no good. Close the VI and re-open it and still the White Hand of Saruman thwarts me. I tried to close LV and finally had to use Task Manager to kill it. Why does this happen and what should I do different to avoid it? Using version 9.0.1.
Thanks,
jvh

tbob,
since he said that he closed TS, i doubt that this is the solution. Nevertheless, it is a valid point (and good one to know for everyone working with TS) and the first one i thought of too.
So either the OP encountered a bug (so question: how often did this occur?) which presumably was some kind of corruption occuring a single time it seems, or there has to be some other reasons.
I had a similar issue the last couple of days where i wanted to edit a subVI of a X-control and it was not possible to do this until i unloaded the VI which used the X-control. And yes, a surely unlocked the X-control for editing before trying to edit that subVI.......
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Similar Messages

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.

System exec subvi. can't access block diagram for positioning

OK I am back!
my first issue is that for some reason I can no longer attach files here for you all to see...
Second and more to the point is how can I tell the system exec.vi to open where I want it too when access to the block diagram is password protected and I can't seem to make any property nodes for the vi either.
I am using this vi to call the OSK (on screen keyboard) for touch screen panel.
I would have sample to show but see number one...
Solved!
Go to Solution.

Thanks Dennis - again
after posting i made an executible of the project as it stood and put it on my touch panel.
I found that it called it OK and I could just moveit around and resize it as i wanted, just once. then whenever i called up the OSK it was where i left it and the same size.
While this may be a small pain to the end user, I think i will keep it like that for now and just let whoever they are deal with it as part of the initial program protocol.
but what about not being able to add attachments here? do I need an adult?

LabView causes system to lock up when editing block diagram of large application

I am attempting to go through a large application which was written for on a different machine with I/O attached. I am looking at it on a plain PC with no attached hardware. The application loads, I can get into the block diagram, but after viewing it for just a short time the display freezes (including the taskmanager), then the keyboard locks up. The only way out is to cycle the power on the PC. This is running W2K on a 550Mhz pentium III processor with 256MB RAM and a new installation of Win2K with all updates applied. This is with LabView 7.1. I can run smaller subvi's with no problem.
I am new at LabView, so any help is appreciated.
- George

Hi George
what kind of Hardware - IO do you use in the app? are there any DAQ-channel- or VISA-Connection-constants in your diagramm? maybe the problem is not the size of your code but the missing hardware...
best regards
chris
Best regards
chris
CL(A)Dly bending G-Force with LabVIEW
famous last words: "oh my god, it is full of stars!"

LabView Crashes When Editing Block Diagram

When least expected and usually at the most inopportune times the LabView 8.6.1 development environment crashes when I am editing my block diagram. It usually happens when I am moving VI's or wires using the arrow keys. This has happened to me several times. Is anyone else having this problem? Is there a bug fix out there? Attached are some of the windows error logs
Attachments:
lvlog06-17-09-11-01-33.txt ‏2 KB
lvlog06-16-09-15-52-19.txt ‏9 KB
lvlog06-15-09-13-53-20.txt ‏2 KB

There is a known issue with LabVIEW running out of memory slots in it's image table
http://zone.ni.com/devzone/cda/tut/p/id/7324#36543_by_category
I have experienced this issue first hand and it does make LV very unstable with crashes at the most inopportune times.
Try uninstalling those toolkits and drivers that you are not currently using. In my case 8.6.1 became completely stable after that.

Can't see block diagram of an auto-running VI

Hello,
I have an old and dirty VI that runs automatically when opened. I cannot see the block diagram because when I stop it, LabVIEW shuts down. There is probably that 'evil' function Stop LabVIEW at the end.
Is there a way to avoid that behavior?
The VI was written a while back in LabVIEW 7.0.
Thanks for the help!
Vincent
Solved!
Go to Solution.

LV_Pro wrote:
One other possible trick to stop the vi without it exiting might be, on Windows machines, to do a "Ctrl ." (holding the CTRL control key while pressing the "period" key)
Not sure there was a "Book X", don't think the Greeks used Roman numerals! ;-)
I have actually seen cases where this doesn't work. Most of the time it happens when in a producer/consumer architecture where the exit logic is not correct and the loop with the event structure exits and the consumer is waiting for something to happen. I was aware of the "Ctrl ." abort but have been forced to kill LabVIEW because the abort wasn't processed.
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

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

Can we edit the icon that represents our XControl on the block diagram?

I created an XControl in LabVIEW 8.5 (and 8.2.1), and I did add custom icons to all the typedefs and VIs associated with it. However, when I drop it on the front panel, I get a generic-looking icon representation on the block diagram. However, when I create a simple typedef and drop that on the front panel, I get the typedef's icon framed in the datatype-specific border on the block diagram. Perhaps I missed something about how do edit that guy. It's a minor issue, but I'm curious.
Thanks,
Dan Press
PrimeTest Automation

Right click the XControl itself in the project and select Properties. There you'll see an icon that can edit, which will show up on the XControl on a block diagram.
... Michael beat me to it!
Message Edited by Jarrod S. on 08-17-2007 04:39 PM
Jarrod S.
National Instruments
Attachments:
Icon.PNG ‏2 KB

Can we design analog to digital signal conversion block diagram (ADC) in labview

hi every one,i've doubt i.e can we convert function generator output (i.e analog signals) to digital signal in labview......can anyone help me how to create ADC circuit that means ADC Block Diagram in LABVIEW.....please give me solutions for my problem

Hi guru,
from signal generation VIs you get arrays containing float values (aka DBL). Those floats are just digital values made of 0s and 1s…
Any value in your computer is digital!
To provide a solution you need to rephrase your question! What exactly do you expect as result of your operation?
Edit: kkkkkkk ur ckt ???
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

The Block diagram that cannot be edited...

The customer wanted to launch the application ( done in LV7 ) with a shortcut from the desktop and when done with it wanted to close all including the LV environment.
So I made the following changes :
1. Made the application to "Run on Open "
2. Connected the while loop Stop button to the "EXIT" function.
3. Saved and started the application.
Presto!! All worked as expected. Except that I no longer was be able to Edit the block diagram !!
Good - I had a copy of the code before the change and survived the nightmare ....
So the moral : Be very clear of what you are doing before you use the EXIT function.
Just though will share the experience, before somebody makes the fatal mistake as above.
( I have now ordered out my copy of the Application Builder, so that I can have my editable code well away from the customer's PC.)
Raghunathan
Raghunathan
LV2012 to Automate Hydraulic Test rigs.

Here's another way to do it.
Create a directory in your LabVIEW x.x directory named 'wizard', and save the attached VI there. If LabVIEW is running, you'll need to restart it, but then in the 'File' menu, you'll have a new selection named "Supress Run on Open...". Select this and you'll get a browse dialog to select the VI to open. It opens it by reference so it will not run.
This is saved in LabVIEW 6.1, but works fine on 7.0 and 7.1.
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.
Attachments:
Supress Run on Open.vi ‏18 KB

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

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

Urgent Help! How can i execute in the same block diagram two separate labview codes each one with diferent execution timings?

Dear All.
I have 2 application progrlams in the same block diagram. the intention is to use the 2 programs at different excuting time for different application, and each have stop and start button ofcourse i will have master stop. But when i run the program, it only works one program at time , that is the 1st block which i make it active only , when i tried to make active the second block it will not work, only works when i stoped the1st one. So, this it to request ur hlep how can i solve my problem. here i have attached some of my program.
Regards!
Solved!
Go to Solution.
Attachments:
2_block application.vi ‏14 KB

Usually you set up a task that has all the channels from all the modules configured. When a loop starts it reserves that task and the cDAQ can't be used by other loops unless you start and stop tasks.
You can have one loop acquire all the data and if you want certain channels to go to other loops you can use the producer/consumer design pattern. If you wanted a third loop you would add another queue and the third loop would dequeue that data. See attached.
Eric
Attachments:
prod-cons.vi ‏69 KB

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 ǝɥʇ'

Can't edit block diagram.

Similar Messages

Maybe you are looking for