Installing and Using the VCOM Custom Device API
- Updated2025-01-10
- 1 minute(s) read
Installing and Using the VCOM Custom Device API
The NI:VCOM Custom Device API allows you to programmatically create an instance of the add-on
from a previously exported configuration. This API consists of:
- An example VI
- The NI-VCOM LabVIEW API
- A VI library
Default Installation Path
By default, the API installs in the following
locations:
| File Type | Custom Device API Data Path |
|---|---|
| Example file (.vi) | %Program Files (x86)%\National Instruments\LabVIEW\examples\NI-VCOM\NI-VCOM Custom Device API or %Program Files%\National Instruments\LabVIEW\examples\NI-VCOM\NI-VCOM Custom Device API |
| Function palette (.lvlibp) | %Program Files (x86)%\National Instruments\LabVIEW\vi.lib\NI-VCOM or %Program Files%\National Instruments\LabVIEW\vi.lib\NI-VCOM |
How
to Use the LabVIEW VCOM Custom Device API
Start the example from the default installation location or launch the example from the LabVIEW Example Finder.
Before running the example, set the input variable and paths to the
projects. Based on these variables, two example scenarios are available:
- The first scenario demonstrates how to add an NI:VCOM custom device to an existing project or replace the custom device in an existing project.
- The second scenario creates a completely new system definition file and adds the custom device into the .nivssdf file.
After you execute this example VI, the NI:VCOM custom device is added to the new or existing VeriStand project with all the configurations and dependencies. The VeriStand project is ready to use.