|Download Help (Windows Only)|
Refer to the following resources as you continue building your application in LabVIEW.
To browse example code that demonstrates various uses of the Model Interface API, select Help»Find Examples from LabVIEW to launch the NI Example Finder. Navigate to the Toolkits and Modules folder. To find the examples on disk, you also can browse to the labview\examples\Control and Simulation\Model Interface directory. You can modify an example VI to fit an application, or you can copy and paste from one or more examples into a VI that you create.
To read data from a hardware device and write it to a model inport or write data from a model inport to a hardware device, use driver VIs written for the device. For example, you can use the NI-DAQmx VIs to communicate with an NI DAQ device in your test application. After you install a LabVIEW add-on such as a module, toolkit, or driver, the documentation for that add-on appears in a separate help system you can access by selecting Help»Add-On Help, where Add-On Help is the name of the separate help system for the add-on.
If your application includes a VI that runs on an RT target and VIs that run on the host computer, choose from available remote-communication methods: Exploring Remote Communication Methods.
Developing complex LabVIEW Real-Time applications requires an understanding of how LabVIEW maps to the real-time computing model. Some LabVIEW programming strategies that work well when developing for a general-purpose operating system do not translate to the headless, priority-driven execution model of a real-time operating system (RTOS). For best practices for designing, developing, and deploying applications with the LabVIEW Real-Time Module, refer to the RT Best Practices Portal.
The LabVIEW Real-Time Module and other LabVIEW add-ons add functionality to the LabVIEW development system and must be purchased separately. Refer to the specific module documentation for more information about that product.
You must use a LabVIEW project to build stand-alone applications that you can distribute, as well as to deploy or download files to RT targets. You also must use a project to work with a Windows Embedded Standard, RT, FPGA, or Touch Panel target.