General Labview Programming

[GaryWong]

Hi Programmer,

I am new to Labview.

I received a "large" program for study purpose.

Large in terms of UI(3x1080pix to fit) and program size (main.vi 2MB in size).

It makes it difficult to read and study, example, selecting "Case" and "Stacked Sequence Structure", need few seconds to load. Any object or line move from diagram screen will need time to refresh.

Saving the program even longer. I am using a 32bit / 4 core I5 Laptop.

My question.

The "Slow" is it due to Large Diagram?

or Huge main.vi program?

Will creating more sub VI can solve the "Slow" issue?

Will placing the tools closer, smaller diagram will help?

Thanks,

Newbie .. 

[udka]

Since you didn't ask your program specific questions it is difficult to analyze why it slow.
-One can be to look into here: Slow Front Panel or Block Diagram Response in LabVIEW http://digital.ni.com/public.nsf/allkb/862567530005F09C8625667B00044B35
-To your other question about VI execution speed and SubVI effect read this : https://zone.ni.com/reference/en-XX/help/371361H-01/lvconcepts/vi_execution_speed/

[PalanivelThiruvenkadam]

It depends on your system configuarion as well.

The problem you are facing is Slow as well as readability issue

(If LabVIEW Program is coded with proper standards you most probably wont face such issues)

First go through the LabVIEW Basics as well as standards, then probably you can change the Program

Ideally Block diagram Logic should be Limited to single page hope your current program has many pages which makes you to scroll and due to slower you are facing problem.

[Blokk]

"I am new to Labview.

I received a "large" program for study purpose."

Bad. You will not learn any good from a bad design (stacked sequence structure is often a good indicator of bad programming skills). About usual programming mistakes / bad design, a good read is here: http://www.ni.com/newsletter/51735/en/

Forget this VI, and look for proper learning resources! Do you have LV licence? You should go through the Core 1, 2, 3 online learning material. Check it here: http://ni.com/myni/self-paced-training

[Ben]

---

@Blokk wrote:

"I am new to Labview.

I received a "large" program for study purpose."

Bad. You will not learn any good from a bad design (stacked sequence structure is often a good indicator of bad programming skills). About usual programming mistakes / bad design, a good read is here: http://www.ni.com/newsletter/51735/en/

Forget this VI, and look for proper learning resources! Do you have LV licence? You should go through the Core 1, 2, 3 online learning material. Check it here: http://ni.com/myni/self-paced-training

---

Ditto that!

My thoughts exactly!

If you do decide to stick with the bad example... feel free to ask here about suggestions to "make it better" and post the code you have (then cover your head).

Ben

[altenbach]

---

@GaryWong wrote:

I received a "large" program for study purpose.

Large in terms of UI(3x1080pix to fit) and program size (main.vi 2MB in size).

---

3x1080 pixels is only 3240 total pixel area which is not much except for the lenght and very unusual aspect ratio.

Nobody just "receives" a large program. Who gave it to you? What are you supposed to do with it? (just study? learn bad programming practices? improve it?)

Are there diagram comments explaining the code? Are things arranged logically?

How much do you  know about LabVIEW? Have you done all the basic tutorials or did they just throw you onto the shark infested deep end without teaching you to swim first?

---

@GaryWong wrote:

I am new to Labview.

It makes it difficult to read and study, example, selecting "Case" and "Stacked Sequence Structure", need few seconds to load. 

---

Do NOT study it. Just from the description all you can possibly learn are bad coding habits. Just delete it and do the regular tutorials.

---

@GaryWong wrote:

Saving the program even longer. I am using a 32bit / 4 core I5 Laptop.

My question.

The "Slow" is it due to Large Diagram?

or Huge main.vi program?

Will creating more sub VI can solve the "Slow" issue?

Will placing the tools closer, smaller diagram will help? 

---

Yes, Creating subVIs will improve compile time. Placing items closer will not.

What is the code complexity?

Where does the 2MB come from (diagram, code, data, etc).

(VI properties...Memory usage...Compiled code complexity).

What is the LabVIEW version?

What are the compiler settings (tools...options...environment...compiler).

How much memory does your computer have? (is "32bit" the OS or the LabVIEW bitness?)

Is the version of the VI the same as your LabVIEW version and if not, did you save it in the new version yet?