LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW 8 very slow to edit large VI

Hi,

now finally LV 8.5 is out and unfortunatly I do not have it........
did someone do a test on a large VI within an project to see if LabView now can edit large VI´s?

thanks for any help

tom
0 Kudos
Message 31 of 40
(2,909 Views)
Hi Tom,
The problem isn't completely fixed in LabVIEW 8.5 however the performance should be greatly improved.  I opened a very large file within a project and only experienced slight delays but nothing on the order of 8-10 seconds. If you have some spare time you could always download the trial version of LabVIEW 8.5 to see if it might be worth upgrading.
Eric A.
National Instruments
Distributed I/O Product Support Engineer
0 Kudos
Message 32 of 40
(2,884 Views)
" I opened a very large file ..."
 
Please define "very large file"
 
Application that use more than 400 VI's are common around my shop with the LARGE applications being 700+.
 
So what does "very large file" mean in the context of your previous posting?
 
Thank you,
 
Ben
Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 33 of 40
(2,871 Views)
Hi Ben,
I file I was experimenting with only used about 50 VI's, so I suppose it would be quite small by your standards.  The VI did exhibit the same slow editing time that everyone has been complaining about when I opened it in LabVIEW 8.2.  When I opened the VI in LabVIEW 8.5, the time it took to drop down a new VI was considerably smaller.
Eric A.
National Instruments
Distributed I/O Product Support Engineer
0 Kudos
Message 34 of 40
(2,844 Views)
May I ask how all of you with really large VI-structures cope with this problem? Are you still using 7.1? Or do you just put up with it and increase the coffee consume?
-DB
0 Kudos
Message 35 of 40
(2,831 Views)
Hi,
answer is very simple - see Reply 20  WORKAROUND: Don´t use the project explorer
tom
0 Kudos
Message 36 of 40
(2,824 Views)

In addition to the note above we have avoided this issue because of the nature of our applications.

Since our apps don't know the targets we will interact with, we avoid using the Shared Variables and rely on traditional methods (TCP/IP, Datasockets, etc.) to share data. I have not seen slow edits in app's that don't use the Shared Variables. This is just my personal observation.

Trying to help,

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 37 of 40
(2,811 Views)
Hi
 Where can I get the lab view program for IQS 12004B lab view program?
0 Kudos
Message 38 of 40
(2,791 Views)


@120341 wrote:
Hi
 Where can I get the lab view program for IQS 12004B lab view program?


You've hijacked the thread by posting a question into a thread that has nothing to do with what you are asking.  Please repost you questions in a new message thread.
0 Kudos
Message 39 of 40
(2,770 Views)

In my experience with main vi's > 700kb in LabVIEW 8.2 and 8.5 on a 1.3 GHz Pentium 4 with 2 Gb RAM, editing speed is reasonable - about a second to add/delete objects and wires.  Then I recently experienced a sudden, severe slowdown with one such vi.  The same edit operations that used to take one second now consistently took 15 seconds.  The aforementioned suggestions in this thread for correcting the problem were ineffective or irrelevant for my situation with one exception.  I believe my problem is similar to one where a developer fixed his problem by replacing a particular control (an enum in his case).  I was able to trace my problem to (defective?) property nodes for two graph controls using this troubleshooting procedure:

1. Delete front panel controls one-at-a-time until editing speed is restored on the block diagram.  Note which control you deleted just before speed was restored.

2. Reload the vi and delete just the troublesome control.  Check editing speed.

3. If editing is still slow, continue deleting controls one-at-a-time from the set of controls deleted originally until editing speed is restored and the second problematic control has been identified.

4. Proceed in a similar manner to identify additional problematic controls if necessary.

In my case, I next reloaded the vi, and deleted just the property nodes of the two troublesome controls.  Speed was restored once the last property node was deleted.  The problem returned once I began recreating property nodes (once the 2nd node was created), however, so the final solution was to recreate the controls AND the property nodes.

Larry

0 Kudos
Message 40 of 40
(2,630 Views)