Why is my Application Slow ?

[G.G.K.]

I am using LabView 6.0.2 on both the Test Machine (Win N/T 4.0) and a Notebook Computer Win 2000). I am creating and running a Diagram-less .LLB file on the Test Machine. If I edit the the VI with the main Panel on my Notebook computer and then copy that VI back to the Test Machine, it runs slowly (hangs for 1/2 second on display update in main loop). If I edit the VI ONLY on the Tester then it executes the .LLB very quickly. The Tester is 1024 x 768 & 256 Colors. The Notebook is 1280 x 1024 & 65,000 Colors. Should that even matter ? I copied all files to the notebook, modified MainProcess.VI and copied just that file back to the Test machine and created the Diagram-less LLB. I have to use a back-up file to fix problem because
editing MainProcess.VI on the Test Machine will not make it fast again. What could be corrupted by editting one file on my Notebook computer ? All other features of the Tester work perfectly except slower speed.

[Gorka Larrea]

If you are under windows, then you should put a small wait inside every loop so that the app doesen't hog your processor time. If this doesen't work, try updating your graphic card drivers.
Hope this helps

[G.G.K.]

I have a wait in every loop. I have the latest video drivers. NOTE: The program works just fine UNTIL I modify the MainProcess.vi on a my Notebook Computer and then copy that one VI back to the original computer. What can be changed in a .VI, just by editing the .VI on another computer, that would would make it run slow when returned to the original computer. The change can be as trival change as clearing a Local for a Control a second time, for example. The original .VIs run just fine and can only be editted only on that computer. Same LabView 6.0.2 different O/S's WIN N/T (tester) vs Win 2000 (notebook).

[Doug (CapeFl)]

Do both computers have the same Labview property settings for properties such as Multi-threading and VI/Sub VI priorities? Check each one's properties under File>VI Properties> Execution and then Performance and Disk categories.
Good Luck, Doug

[G.G.K.]

Doug,

I checked the Tools->Options settings for LabView. Two minor differences. I had "Show Connector Dots" ON and "Allow Terminal to be Deleted from Diagram" ON, all other options are identical. I turned off the differences but still when I edit and copy the .VI's back to the Tester it runs 5X slower. All I have to do to "break" the .VI is MOVE something on the Panel and save. I made all kinds of changes ON THE TESTER to the .vi's last week, still running fast. If I ship the tester I will never be able to edit from my Desk. Also, running the .vi's is slow, I don't have to make the Diagram-less .LLB to see the slowness.
I have checked a few of the .vi's Properties (there are 120 .vi's). They are identical so far. All are normal except the main.vi is "Auto-R
un when Loaded".
This program was originally designed under 5.x by an outside contractor, then converted to 6.0 and modified for our tester.Don't know if that matter.s
Thanks for your ideas.

[Doug (CapeFl)]

It sounds like all should work, but...

Time to see if the NI gurus have a theory - Email or call them directly, they may have a cure. If I think of other ideas, I'll reply. Good Luck, Doug

[G.G.K.]

Doug,
Just for the fun of it, I replaced the 1 Meg ISA Video Card with a 4 Meg PCI Video card in the Tester. I Loaded the new drivers. I can now edit the .VI's at my Desk, copy them back to the Tester and have the Tester run FAST!!!! The Electrical Engineer had installed a 1 Meg ISA Video Card becuase we have successfully used this card on previous LabView 5.x Testers. We called SIIG and we do have the most recent Driver for the 1 Meg Video Card. Evidently there is some weird quirk. LabView says it supports anything that Win N/T supports, well not quite in this case

Thanks for your help.

[Doug (CapeFl)]

Great...