Creates a shared variable of the given name and type in the specified process.

The shared variable that you want to create replaces an existing shared variable if the two shared variables have the same name.


icon

Inputs/Outputs

  • cu16.png set mode

    set mode specifies whether to commit the shared variable immediately or hold the shared variable in memory temporarily.

  • cstr.png process name

    process name specifies the name of the process whose variables this VI creates. This parameter must be a string of numbers and letters with or without spaces.

    Refer to the system tree in the NI Distributed System Manager to view a list of processes. You also can use the Get Process List VI to return a list of process names.

  • cstr.png shared variable name

    shared variable name specifies the name of the shared variable you want to add. You can specify a shared variable in a hierarchy, for example, folder\variable.

  • cenum.png data type

    data type specifies the data type of the variable you want to add.

  • cerrcodeclst.png error in (no error)

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

  • cfxdt.png custom control

    custom control specifies a custom control you create. You must specify custom control if data type is custom.

  • istr.png process name out

    process name out returns the process name you specified.

  • igenclassrntag.png shared variable

    shared variable returns a shared variable indicator for the created variable, which you can wire into property or method nodes to further define the attributes of the variable. The format of shared variable is \\computer\process\shared_variable.

  • ierrcodeclst.png error out

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

  • Create Shared Variable Details

    For optimal performance, set the set mode input of this VI to buffer. Then use the Commit Shared Variables VI to commit multiple shared variables to the SVE simultaneously.

    Note If a configuration file exists, running this VI has no effect on the permanent configuration file for this process.