Low speed when I edit a step when I insert a step, whose edit substep has been specified by a LabVIEW vi.

[jacky Wang]

  I created a step type in Teststand and specfied its "edit" substep with a Labview vi. In labVIEW, I can open that vi very quicky, however, every time when I click "Specify Module..."in that step type's property dialog through Type Pallette windows, it will spend some time on searching file, that's also why I have to wait several time when I insert a step and edit it by right click and choose "edit..." in client sequence file.  For better explanation, I attached a picture here.

  I don't know how to speed up it.

[Adam B.]

Jacky,

I would check your Search Directories by going to Configure >> Search Directories.  When TestStand looks for a VI (whether in a step type or a standard test module), its going to go through this list from the top to the bottom.  Make sure that you have the correct scope on large directories and realize that if you have network directories here, it will also slow things down.  Ideally, any directories where you have majority of your modules would be closer to the top to ensure that you are not digging too deep each time you search for a module.

Adam

[jacky Wang]

Thanks Adam
Yes, I have a long list of search directories. But... to be very frank,I think, for example, LabVIEW vi should has the ability to remember all the sub-modules' paths, thus, everytime when that vi is opened in LabVIEW or Teststand, there's no need to search for those sub-modules. 

Jacky

[RayFarmer]

Hi,

That would be correct assuming you place your VI's and sub VI's in the same place on your target system as your development system. Otherwise its got to go find them, which suggest that the location of the VI's has changed.

Regards

Ray Farmer

[JoseHdz]

The search dialog usually appears whenever the VI is opened using a LabVIEW Run-Time Engine and the VI is not packaged.  What is the setting of the LabVIEW adapter? Is it set to use a LabVIEW Run-Time Engine or the LabVIEW Development System?

I recommend switching the LabVIEW adapter to use the LabVIEW Development System while you are developing your step type.  Once you are done developing the VIs you are using in your step type, you can package them using the TestStand Deployment Utility. 

Hope this helps.