LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW 8 very slow to edit large VI

Hi tomker,

At this point I recommend you get back into contact with NI-Germany. If there is a bug for this issue, they will be able to work with you directly and file it as necessary.

Michael K.

| Michael K | Project Manager | LabVIEW R&D | National Instruments |

0 Kudos
Message 21 of 40
(4,277 Views)

Michael,

This sounds odd.

Are you (NI) suggesting the customer contact NI?

We have been complaining about slow edit in LV 8.X since day -1 and now the fix is going to be depending on the customer voluntarily doing something?

This sounds like my Ford dealer responding to my complaint about poor performance by suggesting that I call Ford. Smiley Surprised

Can't NI talk to NI?

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 22 of 40
(4,264 Views)
Hi Michael,
Hi Ben,

well - I did already contact NI-Germany on this. Actually the described workaround came from them.
They did get the complete project for testing. For NI: the SRQ is 397870
Also the LV version is original 8.20 - not the German one.

Thanks - I do hope to get fast help on this

tomker


0 Kudos
Message 23 of 40
(4,247 Views)
Hi there,

I just want to confirm what has been said here. My "main"-VI has about 25 event cases and uses 3d-graphs. While programming this app I could feel how the editor kept getting slower and slower. It now takes 2 sec for each action. I don't think this behaviour is linked to a specific function on control. That's more than annoying!
I'm working with LV8.01 at the moment. I have 8.20 on my desk but didn't feel bored enough to install it.
But 8.20 doesn't fix that bug, right?
Please put some effort into fixing that problem!!! Smiley Mad
-DB
0 Kudos
Message 24 of 40
(4,228 Views)
Hello all,

This was reported to R&D (#4586SIKM) for further investigation. A possible workaround is opening the VI without opening the project.


Thank you for the feedback.

Michael K. | Applications Engineer

| Michael K | Project Manager | LabVIEW R&D | National Instruments |

0 Kudos
Message 25 of 40
(4,137 Views)
Hi,
well thats the same as the Reply Number 20.
Annoying is:
if you open without the project you can´t do any change on the shared vars.

tomker
0 Kudos
Message 26 of 40
(4,113 Views)
I recently upgraded from LabView 7.1 to LabView 8.01 and have also found that when working with block diagrams, the
response is extremely slow - up to 10 secs just to erase a wire.  Things speed up without the project explorer (ie 5 secs for
delete a wire) but the applications I run have extensive use of shared variables thus at some point, I have to run the
Project Explorer to access these and again the block diagram is very slow to update.  Even moving a shared variable
from one part of the block diagram to the other causes the CPU usage to run at 98%-100% for 5+ seconds.  When trying to
run the VI, usually 30 seconds at least are required for the database to read the opc infomation and the subsequent
update rates (though set at 500 ms) take seconds.  In its present form, LabView 8 is unusable for any of my applications
and I will have to revert to LabView 7.1 where all responses are quite fast.
 
                   B. Veilleux
 
                  PTX Corp
0 Kudos
Message 27 of 40
(3,954 Views)
Hi bveilleux,
NI told me, that there are big improvements in the DSC module if you go from 8.01 to 8.20.
Is it possible for you to test your application with 8.20?
thanks
tomker


0 Kudos
Message 28 of 40
(3,932 Views)
The workaround suggested here to edit the vi with the project explorer does not work for LV-RT Targets.  Is there any status on #4586SIKM?
Message 29 of 40
(3,491 Views)

Hi,

R&D is aware of and working on that CAR. It is related to a few others. There isn't a patch as of yet, but they are working on it. Thanks!

Stephanie

0 Kudos
Message 30 of 40
(3,448 Views)