Returns the list of completed data runs that belong to a specific data set.


icon

Inputs/Outputs

  • ci32.png timeout (30 s) —

    timeout specifies the maximum time, in seconds, that this VI waits for reading data from the Citadel database. The default is 30. A timeout value of less than or equal to 0 specifies no timeout, which means this VI waits indefinitely until this VI receives data from the Citadel database.

  • cmclrn.png multicolumn listbox —

    multicolumn listbox is a reference to a multicolumn listbox control that signals this VI to populate the listbox with the information for each data run, excluding the list of traces and the equipment list.

  • cpath.png database URL —

    database URL specifies the computer name and the database name where the Citadel database resides. Enter the database URL in the format \\computer\database.

    For example, if you have a copy of the LabVIEW Datalogging and Supervisory Control (DSC) Module and Citadel service installed on a computer named datalogger and the name of the database on that computer is data, you can access the data on datalogger from another computer by using the path \\datalogger\data. If you provide a database name only, this VI searches for the database on the local computer. If you do not wire database URL, this VI resolves the database URL from the Shared Variable Engine (SVE). If the SVE resolution fails, this VI reads data from the database associated with the default DSC Module process.

  • cstr.png data set information trace —

    data set information trace is the data set in the database for which the run(s) are sought.

  • cbool.png get all runs info? (F) —

    get all runs info? specifies to query each run for a list of traces and equipment. This parameter uses an additional amount of CPU resources when the value is TRUE. If the value is FALSE, this VI queries for a list of traces and equipment in the first run and uses the same query results for all consecutive runs. The default is FALSE.

  • cerrcodeclst.png error in (no error) —

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

  • ipath.png database URL out —

    database URL out returns the computer name and the database name that specify where the Citadel database resides. The format is \\computer\database.

  • i1dcclst.png data runs —

    data runs is complete information for all the data runs found in the data set identified by the data set information trace.

  • istr.png run ID —

    run ID is the run identification value for the data run specified by the application.

  • istr.png description —

    description is the description of the data run that is provided by the application.

  • i1dstr.png traces —

    traces is the list of shared variables used in the data run. The shared variable data is stored in the historical database in a trace.

  • i2dstr.png equipment —

    equipment is the list of equipment used during the data run. This parameter has two values. The first value is the name of the piece of equipment and the second value is the description of the piece of equipment.

  • istr.png user name —

    user name is the name of the user logged into the system when the data run started.

  • iu64.png internal ID —

    internal ID is a unique identifier for a data run. This unique identifier is generated automatically by the system. It is unique within the data set. This identifier allows you to distinguish among multiple data set runs that might have the same run ID value, which you can specify using the Read Data Set Run by ID VI.

  • iatrn.png start time —

    start time is the start time of the data run. This is the time at which the start condition was met.

  • iatrn.png end time —

    end time is the end time of the data run. This is the time at which the end condition was met.

  • ierrcodeclst.png error out —

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

    • Examples

    Refer to the Dataset Marking Demo.lvproj in the labview\examples\lvdsc\Data and Alarm Historical Logging\Dataset Marking Demo directory for an example of using the List Data Set Runs VI.