LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

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

0 Kudos
Message 1 of 5
(2,928 Views)

Graphics card could play a part.  So can CPU.  What version of LabVIEW are you using?  How big is this VI?  Are you using subVIs?  From your description, it sounds like you just have a huge, monolithic VI.



There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 2 of 5
(2,915 Views)

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
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
0 Kudos
Message 3 of 5
(2,909 Views)

 Thank you guys. I am planning to develope more subVIs to tackle this issue. Further I am planning to use the source code control. I hope when I start setting up the source code control, I will need more help from you guys.

0 Kudos
Message 4 of 5
(2,894 Views)

@MansoorEE wrote:

 [...] Further I am planning to use the source code control. I hope when I start setting up the source code control, I will need more help from you guys.


Regarding source code control I really like Matthew Kelton's blog series on that topic. This is useful to get an overview. And the issues that LabVIEW developers usually face (or will face).  If your company doesn't use source code control yet, you will have to make a decision which one to use ...

0 Kudos
Message 5 of 5
(2,878 Views)