Read Data Set Run by ID VI
- Updated2024-11-20
- 6 minute(s) read
Extracts data for one or more data runs whose run ID or internal ID match the ID specified by the run ID or internal ID input.

Inputs/Outputs
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.
internal ID
—
internal ID is the 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 application–defined run ID value.
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.
data set information trace
—
data set information trace is the data set in the database for which the run(s) are sought.
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.
run ID
—
run ID is the specific data run from which to extract data. This value can be empty if you use the internal ID input. If more than one data run has the same run ID, this VI returns all matching data set runs. If both run ID and internal ID are specified, this VI uses the internal ID.
error in (no error)
—
error in describes error conditions that occur before this node runs. This input provides standard error in functionality.
matching data sets
—
matching data sets is complete information for all matching data runs found in the data set.
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.
first match data
—
first match data contains data for the traces that are part of the first data run whose run ID or internal ID matches the supplied run ID or internal ID. Note Data for string shared variables is not returned.
first match run ID
—
first match run ID is the run ID value of the first matching data run.
error out
—
error out contains error information. This output provides standard error out functionality.
all matches
—
all matches is data for all the data runs whose ID matched the run ID parameter. If the internal ID was used, this array contains only one element.
|
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 Read Data Set Run by ID VI.
timeout (30 s)
—
internal ID
—
database URL
—
data set information trace
—
get all runs info? (F)
—
error in (no error)
—
matching data sets
—
run ID
—
traces
—
equipment
—
internal ID
—
start time
—
database URL out
—
timestamps
—
data
—
error out
—