Deploys the variables in one or multiple LabVIEW project libraries into the Shared Variable Engine (SVE) on the host computer. The variables are in a running state. This operation is available only on the host computer, so any VIs contained in the project libraries remain unaffected. You must manually select the polymorphic instance to use.

Note To deploy a library that has variables bound to a remote target, you must bind the variables by using the NI Publish-Subscribe Protocol (NI-PSP).

Use the pull-down menu to select an instance of this VI.


icon

Inputs/Outputs

  • cpath.png library path —

    library path specifies the path to the LabVIEW project library (.lvlib) file that contains configuration information for the shared variables and I/O servers you want to deploy into the SVE. Enter the full path to the .lvlib file, such as C:\data\data1.lvlib. If you enter only the filename of the .lvlib file, LabVIEW loads the file from the directory in which the VI that calls the Deploy Libraries VI resides.

  • cerrcodeclst.png error in (no error) —

    error in describes error conditions that occur before this node runs. This input provides standard error in functionality.

  • ierrcodeclst.png error out —

    error out contains error information. This output provides standard error out functionality.

    • Deploy Libraries Details

    To deploy a library that has variables bound to another library, use the Deploy Libraries (Multiple) VI to deploy the libraries. Because the Deploy Libraries (Single) VI cannot verify which libraries have been deployed, avoid using the Deploy Libraries (Single) VI inside a For Loop that auto-indexes an array of libraries you want to deploy.

    If you want to use the Deploy Libraries VI in a built application to deploy project libraries to a SVE on a target computer, do not build the project libraries into the application. Instead, the project libraries must reside outside the built application in a directory on the target computer. Refer to the Building a DSC Module Application topic for more information about modifying a project library in a built application using the LabVIEW Datalogging and Supervisory Control (DSC) Module.

    Note If you deploy libraries programmatically that contain both shared variables and VIs, LabVIEW generates error code 1 and does not deploy the libraries to the engine. Deploy the libraries manually to avoid the error.

    Examples

    Refer to the following VIs for examples of using the Deploy Libraries VI:

    • labview\examples\lvdsc\Data and Alarm Historical Logging\DSC Alarms Demo\DSC Alarms Demo.lvproj
    • labview\examples\lvdsc\Data and Alarm Historical Logging\Dataset Marking Demo\Dataset Marking Demo.lvproj
    • labview\examples\lvdsc\Data and Alarm Historical Logging\Alarm Web Service Client Demo\Alarm Web Service Client Demo.lvproj
    • labview\examples\lvdsc\Distributed System Connectivity\Modbus Fundamentals\Modbus Fundamentals.lvproj
    • labview\examples\lvdsc\Distributed System Connectivity\Modbus Simulator\Modbus Simulator.lvproj