NI Current Value Table by NI - Toolkit for LabVIEW Download
| Version | 3.3.0.13 |
| Released | May 19, 2016 |
| Publisher | NI |
| License | NI Sample Code License |
| LabVIEW Version | LabVIEW>=10.0 |
| Operating System | Windows, Mac, and Linux |
| Used By | nevstop_3rdparty_dependencies |
| Project links |
Description
Machine control, automation, and application monitoring are typically all developed as independent processes running on one or more systems. Each process performs a distinct task but share a set of common data or variables which allow successful completion of all application tasks.
The Current Value Table (CVT) serves as the central data component and can be used in a wide range of applications. It allows application components to share a common data repository and have direct access to the most up-to-date value of any variable used between components. Using this architecture, one component in the application can handle all of the I/O operations, for example, and share the I/O data variables or tags with other application components. Application operations such as alarm detection, user interface updates, process logic, etc. can then be handled by separate processes, sharing the same data repository.
The CVT implementation is a two layer hierarchy consisting of core VIs and API VIs. The core contains all the functionality of the CVT, including the data storage mechanism and additional service functions. The API VIs provide access to the CVT functionality. You can choose from three groups of API functions that each provide slightly different access to the CVT and vary in flexibility, performance, and ease-of-use.
System Requirements
Application Software: LabVIEW Full Development System 2010 or later
Detailed Description: Current Value Table (CVT) Reference Library
http://zone.ni.com/devzone/cda/epd/p/id/5326
Support for Current Value Table Reference Library
http://forums.ni.com/t5/Components/Current-Value-Table-CVT/m-p/583424
Release Notes
Added support for array data types.
Fixed bug where Read and Write functions could attempt to access the wrong index if the CVT was cleared and reinitialized after Read and Write functions are called such that a tag with the same name is present at a different index.
If Read/Write Index or Static Read/Write functions are used, this fix is not present to preserve maximum performance on these functions. If using these functions, do not reinitialize the CVT with a differently-ordered set of tags without resetting the entire application.
Post an Idea
Post a Resource