Configuration Tool Reference Design Library
This application component includes a library of VIs that allows an integrator to define and manage properties in configuration-driven applications. It also provides a configuration property editor utility that also serves as an example program.
Version and Installation Instructions
configtool.zip - This version is compatible with LabVIEW 7.1 Please refer to the readme document in configTool.zip for installation instructions.
configtoolv2.zip - This version is compatible with LabVIEW 8.2 or later. It includes performance improvements for large applications and is packaged as an installed component.
configtoolv3.zip - This version is compatible with LabVIEW 8.2.1 or later. It includes some new features and a minor change to the API. See the enclosed ReadMe file for more information.
The Configuration Tool library provides an API for:
• Loading configuration properties from a file
• Saving configuration properties to a file
• Getting, setting, adding and deleting properties
• Copying configuration properties
The API VIs are accessible from the LabVIEW user library menu.
The configuration editor is accessible from the LabVIEW Tools menu.
For a detailed discussion of the library and examples, please read the document "Implementing Configuration Files for Computer Based Data Acquisition Systems (link attached below).
|Implementing Configuration Files for Computer Based Data Acquisition Systems|
Application Software: LabVIEW Professional Development System 7.1
Application Software: LabVIEW Professional Development System 8.2.1
Application Software: LabVIEW Professional Development System 8.2
Reader Comments | Submit a comment »
After installing the tool for LV 2009, I
wanted to install it for LV 2010 on the same
machine, however the installer refuses to do
so as it probably sees that the toolkit is
Would just copying the new content under
- Laurent M., BSI. email@example.com - Jul 29, 2011
Why does the data type have to be included in the property name?
The data type should automatically be appended (e.g. _DBL) to the property name, and not have to be included as part of the name (when calling). We know what type of write we are doing based on the vi we are using, so it should be appended on write, and not have to be specified on a read.
- Jul 11, 2007
Why does the close config data vi obliterate the header?
Labview 8.2.1 1. Why does the close config data vi obliterate the header? 2. Surely the comments/header (following ;) should be ignored (and not destroyed when data is added) - comments are permitted in cfg files.
- Jul 11, 2007