NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Sequence editor lag when selecting steps

Solved!
Go to solution

Greetings all -

 

I am running into some issues lately with sequence editor (TS 4.1 / LV 8.6) where selecting certain steps will literally take up to 30 seconds to load (instead of the normal 1 or 2 secs)...it seems to affect niswitch related steps the most, but pretty much all the steps seem to take a good while. It seems this is compounded if i shift-select many steps at once - e.g. if i pick 4 steps, it will literally stall out for 2 straight minutes before i can change step options. Seqedit.exe is pulling 100% of CPU during this time as well.

 

I will add that i actually have two identical setups, and this is only affecting one of them....

 

I think it's safe to assume that sequence editor is probably doing some sort of searching or something, however i would expect that once the VI is loaded into memory (let's say niswitch.llb/connect channels), that it would be fine for the rest of the time i spend editing....any advice on what exactly it's doing?

 

other than this taking a long time, nothing is technically "broken" and my sequences work fine, but my development time is insane now because i'm spending 80% of my time sitting waiting for sequence editor to spring back to life!

 

Thanks!

 

- Kris

0 Kudos
Message 1 of 4
(3,963 Views)
One quick thing to check is your search paths (Configure>>Search Directories). Check if you have added any paths that are on network drives or that search sub-directories. If so, move those to the end of the list.
0 Kudos
Message 2 of 4
(3,961 Views)
Solution
Accepted by topic author ktaugher
If your VIs have I/O controls connected to the connector pane, you might be hitting the same problem described in this thread http://forums.ni.com/ni/board/message?board.id=330&thread.id=23845.  You might need to patch LabVIEW 8.6.
0 Kudos
Message 3 of 4
(3,955 Views)

thanks guys - i'll give those a shot

 

i also forgot to mention that out of the 2 cloned machines i'm working on (both 4.1 / 8.6), the one that has the issue was actually upgraded from 4.0/8.5 - the other one was a fresh install

0 Kudos
Message 4 of 4
(3,951 Views)