Consider the following recommendations and requirements for editing VIs when you decide whether to use stand-alone VIs in a TestStand system:

  • NI recommends that you save all code modules in one version of LabVIEW. VIs saved in different versions of LabVIEW cannot share data when executed using the LabVIEW Run-Time Engine (RTE).
  • Loading multiple stand-alone VIs can negatively impact performance, especially if the test sequences load VIs dynamically.
  • Using multiple stand-alone VIs can result in name conflicts. LabVIEW does not support loading multiple VIs with the same name from different locations. Use LabVIEW project libraries and packed project libraries to add a namespace to the VIs and avoid name conflicts.
  • NI does not recommend editing packaged VIs on a deployed system because unexpected errors, such as broken VIs or run-time errors, can occur. NI recommends rebuilding and redeploying the deployment image in this situation. Analysis and instrument drivers are examples of VIs that use project libraries.