LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Labiew wire is very slow

Solved!
Go to solution

Thanks @gerd and @thols

/Y

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 21 of 27
(1,173 Views)

If you haven't tried this already, try creating a brand new VI and pasting the contents of the offending VI into the new one. 

---------------------
Patrick Allen: FunctionalityUnlimited.ca
0 Kudos
Message 22 of 27
(1,156 Views)

@pallen wrote:

If you haven't tried this already, try creating a brand new VI and pasting the contents of the offending VI into the new one. 


Just to clarify a bit, that means the block diagram contents, not the front panel!

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 23 of 27
(1,148 Views)

hey Crossrulz,

You are right,so the code goes to 7.4, the code in't quite complex but yes, quite a lot of duplicated code which unfortunately i cannot find out a way to avoid that duplicate right now, 

I tried to decrease the limit but seems no obvious change.

That pretty frustrating 

 

Eric

 

0 Kudos
Message 24 of 27
(1,124 Views)

I actually tried to delete some VI and i can see the slow problem can be avoid significantly. 

that's say it is a problem with my code structures, 

but all my other if case have almost the same structure as i posted in the first page, 

there is no several layer vi in those two if case 

Message 25 of 27
(1,122 Views)

@ericyuan wrote:

hey Crossrulz,

You are right,so the code goes to 7.4, the code in't quite complex but yes, quite a lot of duplicated code which unfortunately i cannot find out a way to avoid that duplicate right now, 


Step one would be to create a sub-vi of that code so you only have a few instances of a vi.

/Y

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 26 of 27
(1,098 Views)
Solution
Accepted by ericyuan

@ericyuan wrote:

quite a lot of duplicated code which unfortunately i cannot find out a way to avoid that duplicate right now


2 options:

1. For things that are the same in every case of a Case Structure, it should be moved to be outside of the case structure.

2. Other random duplicate code should be turned into a subVI which you can call from many places.

 

Both of those will help reduce your complexity.


GCentral
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
Message 27 of 27
(1,075 Views)