Corrupt block diagram

Hi all,
I have a VI which is able to open and I can even start the front panel, but when trying to open the block diagram, the screens stays white and Labview crashes.
Is anybody able to open the block diagram of this file?
Thank you in advance>
Greetz, Bart
Attachments:
main_v_0_0_1.vi ‏165 KB

Saved for LV2012
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome
Attachments:
main_v_0_0_1.vit ‏113 KB

Similar Messages

Corrupt Block Diagram With Infinite Wires

Hi,
Has anyone every seen a corrupt Block Diagram as shown in the pic? Almost all my wires have stretched to infinity!
I used "Clean up wire" on these wires, but that did nothing.
Ironically, the VI runs -- but I can't develop further with the BD in this state.
Any ideas, please
THANKS PEEPS!
Attachments:
Screenshot 2015-03-26 18.16.56.png ‏78 KB

There is a maximum size that the BD or FP can be. If you are getting close to that size and the cleanup tries to make it bigger odd things can happen. This might explain why nothing happens when you try to clean it up.
http://digital.ni.com/public.nsf/allkb/62D66358BBF8A87186256FC50077FA17
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Why is diagram clean up corrupting my block diagrams?

A couple of times now (you'd think I would learn my lesson...) I've used the Clean Up Diagram option only for it to render my block diagrams completely unreadable. It's happened on two different systems now..
In this latest incident the flat sequence structure and the labels render as normal but the controls and constants are "smeared out" - for example, instead of being the usual small blue boxes the integer constants are rendered as very tall, thin rectangles. The data flow is completely impossible to discern. It's fascinating.
Anyone seen this before and know how to fix it?
Attachments:
reset_clock_frequency.vi ‏16 KB

I've seen something similar before and I believe this occurs when cleanup results in a block diagram that is larger than the maximum space allowed in the block diagram. The VI you provided appears to go from ~-30000 pixels to ~+28000 pixels in the Y-direction, which is dangerously close to that limit. I'm not aware of any way to recover a VI once it's been saved in this state.
This KnowledgeBase article includes additional information on the maximum allowed size of the front panel and block diagram:
KnowledgeBase 3JEEP1ZH: Maximum Size for Front Panel and Block Diagram
http://digital.ni.com/public.nsf/allkb/62D66358BBF8A87186256FC50077FA17
Tom L.

Automatic resizing of controls on block diagram

Hi,
I have control as strict type def and many instances (on block diagram) of this control in several VIs. When I add new element in this control all instances resizes to maximum size and that corrupt layout on block diagram because all structures resizes with that instances. Is there a way to avoid that?
Thanks, andrej

Place it on the front panel of a subVI as an output. Then call that subVI whenever you want the typedef.
You can find more on using typedefs here.
Try to take over the world!

Why Is the Block Diagram Disabled?

What did I do now? Please look at the attached image. A VI that I am using as a subVI in various different programs suddenly started looking like I had used application builder to create an exe file out of it (But I didn't!!). The only options are Start and Run Continuously, and the block diagram is disabled. What did I do to get myself in this mess? How do I undo whatever I did, so I can edit the block diagram again? Any help or suggestions would be greatly appreciated.
Thanks!
Solved!
Go to Solution.
Attachments:
Disabled Block Diagram.png ‏259 KB

Did you ever built a source distribution with the option set to remove the diagrams? In this case, the original must still be around somewhere.
Since LabVIEW 8 you can no longer simply save without block diagram and you would not be able to upgrade such a VI to LabVIEW 2011, which it is now. (details)
Of course it is possible that there is some corruption, but looking at the memory usage, the block diagram is blanked out.
LabVIEW Champion . Do more with less code and in less time .
Attachments:
NoBlockDiagram.png ‏38 KB

DIO Port Config & DIO Port Write Block Diagram Errors (Call Library Function Node:library not found or failed to load)

Hi Guys, need help on this.
I have this LabVIEW program that used to work on the old computer.
The old computer crashes most of the time, so I upgraded the computer
and used its Hard Drive as slave to the new computer.
I have no idea where are its installers since the guy that made the program
is not in my department anymore.
I downloaded all the drivers needed from NI: NIDAQ9.0, NIVISA,NI488.2,
and drivers of some instruments needed in the setup. I'm using LabVIEW8.2.
Everything's fine until I open the LabVIEW program for our testing.
Here goes the error:
   DIO Port Config
   DIO Port Write
Block Diagram Errors
   Call Library Function Node: library not found or failed to load
Attachments:
ErrorList.JPG ‏200 KB

Honestly, I'm a newbie on Labview. I just want this old program to run on the new computer.
The guys that installed the drivers on the old computer are no longer here in my department.
And I have no idea where the drivers are. So I just downloaded the drivers needed for my hardware and instruments.
Here's my hardware: (cards: PCI-DIO-96, PCI-GPIB), (instruments: SCB100,E4407B, HP83623, HP3458, HP8657)
OS: Windows XP Pro
By the way, I have unzipped the TraditionalDAQ drivers. First I tried the 7.4.1, but installation error appeared.
I thought maybe the installer is corrupted, so I downloaded the 7.4.4 and unzipped it.
But, still same installation error appears. I don't understand, both TraditionalDAQ drivers have same installation error.
Now I have tried the DAQmx8.7.2 driver, bu still the DIO Port Config and DIO Port Write have errors.

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

I created boolean references in my main vi block diagram and copied them to my sub vi front panel. when wire my reference in my main vi to one the input node of the sub vi the wire is broken. the error says its a class conflict why?

i created boolean references in my main vi block diagram and copied them to my sub vi front panel. when wire my reference in my main vi to one the input node of the sub vi the wire is broken. the error says its a class conflict why?

Expanding and clarifying what BJD said;
After you create the temporary sub-VI that BJD mentioned, open its front panel and copy the reference control that LV created when it created the sub-VI.
This reference control will be correct class etc that you need. Use the control to replace the original control that you were attempting to wire up.
The technique of "create sub-VI...copy" always works for me.
There is one more thing that you should watch out for.
The mechanical action of the boolean can not be set for latch action when attempting to read the value using a value property node.
Trying to help,
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

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

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

Error cluster constant appears different in two locations on a block diagram

I am a newbie to LabVIEW. I have taken Core 1 & 2 and Machine Vision and I have not com across this before.
The image on the right is obviously an Error cluster constant used in the block diagram to create an Error cluster and wire it to an error out terminal. As far as I can tell the image on the left is about the same thing, but why does it look different? The different appearance causes raises a concern that there is a difference in behavior that I do not understand. LabVIEW help suggets that both are Error constants. When I create a new error constant, it always ends up appearing like the right image above. I have not been able to create someting looking like the image on the left.
Could someone please confirm what the image on the left is on a blck diagram?
Thanks,
Bill
Solved!
Go to Solution.

The image on the left is an error cluster control. It has a front panel presence and can be set either via the front panel or through a property node or local variable. The image on the right is an error cluster constant. It is a static value.
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

In block diagram connecting wire getting blur while saving the VI in LabVIEW 2009

Hello,
I am using Labview 2009, And while I am saving a simple VI connecting wires are getting blurry. What could be the problem?? Is it affect my program while running?
Solved!
Go to Solution.

Go into Tools>>Options, select the Block Diagram page and find the section called Constant Folding. If the CF for wires check box is checked, then this is most likely the reason. You can uncheck the check box and it won't affect the way your code runs.
If this isn't the case, you should upload an image of what it looks like.
Try to take over the world!

ORACLE 8.0.5 on SuSE 5.3 and 6.0 - Corrupt Block

I do some heavy loading (Designer 2000) and I do get similar
errors on 2 different computer with mirrored disks -different
systems - on each one. So I'd like to exclude hardware problems.
it's experimental - so I do not run archives -
Designer on W95 crashes quite often but this should never lead
to corrupted data blocks.
Linux was hanging too - and disk-cache might not have been
written to disk ????? could this be a reason ???
Corrupt block relative dba: 0x01003aa8 file=4. blocknum=15016.
Fractured block found during buffer read
Data in bad block - type:6. format:2. rdba:0x01003aa8
last change scn:0x0000.00014914 seq:0x3 flg:0x00
consistancy value in tail 0x496b0605
check value in block header: 0x0, check value not calculated
spare1:0x0, spare2:0x0, spare2:0x0
would be happy to get some feedback
null

Ferdinand Gassauer (guest) wrote:
: I do some heavy loading (Designer 2000) and I do get similar
: errors on 2 different computer with mirrored disks -different
: systems - on each one. So I'd like to exclude hardware
problems.
: it's experimental - so I do not run archives -
: Designer on W95 crashes quite often but this should never lead
: to corrupted data blocks.
: Linux was hanging too - and disk-cache might not have been
: written to disk ????? could this be a reason ???
: Corrupt block relative dba: 0x01003aa8 file=4. blocknum=15016.
: Fractured block found during buffer read
: Data in bad block - type:6. format:2. rdba:0x01003aa8
: last change scn:0x0000.00014914 seq:0x3 flg:0x00
: consistancy value in tail 0x496b0605
: check value in block header: 0x0, check value not calculated
: spare1:0x0, spare2:0x0, spare2:0x0
: would be happy to get some feedback
Please check first /var/log/messages for any linux errors. It is
likely that if linux crashes and cannot sync to disk that there
might be some corruption problems. For this reason lts of people
would like to see raw device support but apparently Linus is not
willing for some reason...
I assume some hardware relevant problems though
Marcus
null

Corrupt block diagram

Similar Messages

Maybe you are looking for