Table Of Contents

VeriStand File Extensions

Last Modified: August 31, 2020

VeriStand projects use a variety of file types.

Use the following table to find information on a file extension.

File extension Description
.bt1 A batch stimulus profile file created using VeriStand 2009, 2010, or NI Dynamic Testing Software 1.0.
.cah Calibration History file.
.csv Comma Separated Values file.
.dbc Database file that describes signals and associated messages for a collection of controller area network (CAN) nodes.
.depvs Support file that lists any dependencies of a compiled model. This file ensures the dependencies deploy to real-time targets.
.dll Shared library. VeriStand requires that models be compiled into a dynamic link library (DLL) before they can run on a Phar Lap RT target.
.et1 A step-based stimulus profile file created using VeriStand 2009 or NI Dynamic Testing Software 1.0.
.et2 A table-based stimulus profile file created using VeriStand 2009 or NI Dynamic Testing Software 1.0.
.fpgaconfig FPGA Configuration file. XML-based file that specifies the content of direct memory access first-in-first-out memory buffers (DMA FIFOs).
.ini Standard Windows configuration settings file.
.ldf A local interconnect network (LIN) description file.
.llb A LabVIEW VI library (LLB). Custom devices that run in VeriStand consist of LabVIEW VIs distributed in LLBs.
.lvbitx LabVIEW-generated bitfile. Defines the available I/O on the FPGA. A bitfile is a compiled version of an FPGA VI.
.lvlib LabVIEW project library. A collection of LabVIEW VIs, type definitions, shared variables, palette files, and other files, including other project libraries. For example, the VeriStand LabVIEW APIs are organized into project libraries.
.lvmodel Compiled model that runs on Windows PCs. Generate models from a LabVIEW VI or simulation subsystem.
.lvmodelso Compiled model that runs on Linux x64 or Linux ARM. Generate models from a LabVIEW VI or simulation subsystem.
spd-note-note
Note  

You must install additional software to enable LabVIEW models for targets running a Linux Real-Time OS. For more information about how to use LabVIEW models with Linux, visit the NI website. VeriStand is not supported on x64 Intel-based cDAQ controllers running NI Linux Real-Time.

.lvproj LabVIEW project file. A LabVIEW file type you can use to build custom devices for VeriStand.
.m Text-based m-script file that initializes variables and can provide other information needed by models.
.mdl Model you developed in the MathWorks Simulink® simulation environment.
.ncd NI-CAN database. Database file that describes signals and associated messages for a collection of CAN nodes.
.ncl NI-XNET logfile. Binary file for the storage of CAN, FlexRay, and LIN data.
.nivscal Calibration file deployed to targets. Binary file that VeriStand deploys, and then deletes when the project is undeployed.
.nivscf Calibration file on host. XML-based file you can import a .nivscf file into other projects to reuse the calibrations.
.nivsmacro Macro file. A recording of the commands sent to the target.
.nivsproj Legacy VeriStand project file.
.nivsprj VeriStand project file.
.nivsscreen VeriStand screen file.
.nivssdf VeriStand system definition file.
.nivsseq Real-time sequence.
.nivsseqt Real-time sequence template.
.nivsstimprof Stimulus profile.
.nivsstimproft Stimulus profile template.
.nivstest A stimulus profile file created using VeriStand 2009, 2010, or NI Dynamic Testing Software 1.0.
.out Shared library.
.tdms Technical Data Management Streaming file. A binary measurement file that contains waveform data. Stores descriptive information at the file, group, and channel levels. When you run a stimulus profile file using the Stimulus Profile Editor, VeriStand logs data to a TDMS file.
.vi LabVIEW Virtual Instrument.
.xml Extensible Markup Language file. VeriStand requires a corresponding XML file for any custom device that you add to a project. An XML file might also refer to a Stimulus Profile Editor test results file or a FIBEX file, a database storage file for use with the XNET Database Editor.
.xsd XML Schema Document file. This file determines the validity of that XML file. It contains a set of rules to which the corresponding XML document must adhere in order to be considered valid according to that schema. VeriStand ships with .xsd files that you can use to validate FPGA configuration files and custom device XML files.

Recently Viewed Topics