Veristand EngineVeriStand 引擎是管控整套系统时序、以及下位机与上位机之间通信的执行机制。VeriStand 引擎执行硬件输入输出、运行模型、程序流程、报警功能与测试任务并根据模型运行结果和硬件输入输出数据计算通道表内数值。该引擎既可在仿真模式下运行于台式电脑也可作为嵌入式应用程序运行在实时RT系统中。VeriStand 引擎包含多个定时循环这些循环借助实时RT先进先出缓冲区在循环间传输数据。每个循环负责执行指定任务并被分配相应优先级。用户无法修改引擎循环的优先级与核心任务但可自定义循环相关运行参数例如执行速率。系统定义文件存储了 VeriStand 引擎的各项配置参数。下图展示了 VeriStand 引擎的工作原理。VeriStand Directories and AliasesVeriStand uses directories and aliases for project files, models, and custom devices.The following tables list paths to common VeriStand directories by operating system. The heading before each table indicates how NI documentation refers to the directory. For directories with aliases listed, the alias is the text that appears with a relative path in an API or XML file. This text defines the directory that the path is relative to.Note: The aliases in this topic refer to locations on disk and are not related to aliases you define for channels in a system definition file.Common DataAlias:To Common Doc DirOperating systemPathWindowsPublic Documents\National Instruments\NI VeriStand xxxxNote: xxxx is the VeriStand version number.Application DataAlias:To Application Data DirFor internal use only. Certain custom device development tools, including Custom Device XML and the Device Properties VIs, can reference this directory. However, NI recommends you avoid storing or modifying files in this directory.Operating systemPathWindowsApplication Data\National Instruments\VeriStandBaseAlias:To BaseOperating systemPathWindowsProgram Files\National Instruments\VeriStand xxxxNote: xxxx is the VeriStand version number.Custom Device Engine DestinationAlias: NoneOperating systemPathPhar Lap/ETSC:\ni-rt\NIVeristand\custom devices\custom device name\Model FrameworkAlias: NoneOperating systemPathWindowsC:\VeriStand\xxxx\ModelInterfaceVeriStand .NET ReferenceUse .NET APIs to programmatically control software operations.Note: These APIs are documented in the VeriStand .NET API Help.APIAssemblyDescriptionExecution APINationalInstruments.VeriStand.ClientAPI (in NationalInstruments.VeriStand.ClientAPI.dll)Automates the operation of an VeriStand application on the target. For example, you can read and write channel data, control running models, configure alarm states and read data from alarms, and access Workspace tools.System Definition APINationalInstruments.VeriStand.SystemDefinitionAPI (in NationalInstruments.VeriStand.SystemDefinitionAPI.dll)Automates the operation and configuration of a system definition file. This API performs the same operations as configuring the file in the System Explorer window.Stimulus Profile Definition APINationalInstruments.VeriStand.StimulusProfileDefinitionApi (in NationalInstruments.VeriStand.RealTimeSequenceDefinitionApi.dll)Automates the operation and configuration of stimulus profiles. This API performs the same operations as configuring stimulus profiles in the Stimulus Profile Editor.Real-Time Sequence Definition APINationalInstruments.VeriStand.RealTimeSequenceDefinitionApi (in NationalInstruments.VeriStand.RealTimeSequenceDefinitionApi.dll)Automates the operation and configuration of real-time sequences. This API performs the same operations as configuring real-time sequences in the Stimulus Profile Editor.Data Types APINationalInstruments.VeriStand.Data (in NationalInstruments.VeriStand.DataTypes.dll)Represents data types and resources used by VeriStand.You can access these assemblies from any .NET-compatible programming language or environment, including LabVIEW and NI TestStand.ASAM XIL API - Generic Simulator InterfaceVeriStand includes a Generic Simulator Interface for the Framework, MAPort and EESPort based on the 2.1 version of the ASAM XIL StandardThe Association for Standardization of Automation and Measuring Systems (ASAM) is an organization that facilitates interoperability between measurement and automation testing tools from different vendors.Use the MAPort to read and write data and to capture and generate signals in the simulation model. The EES port provides a general API for electrical error simulation. The Framework is an abstraction layer above the testbench.Note: Although the EESPort and MAPort use the 2.1 version of the ASAM XIL API, they have their functionality implemented for the 2.0.1 API version. The TargetScript in MAPort also implements the 2.1 API.Locate example VeriStand ASAM XIL testbench and framework files in Common Data\Examples\DotNet4.6.2\ASAM XIL.