byDagaror04-19-201604:34 AM - edited 01-30-201710:51 AM
NI VeriStand 2015 has introduced the support of Linux targets (x64 and ARM). This document pretends to lead you step by step how to modify the custom device source code so you can run it on targets Linux RT.
The changes are at Custom Device Source Code LabVIEW Project Level and at file XML level.
LabVIEW Custom Device Source Code
Create a new custom device by following this steps or take an already implemented custom device.
Add an offline Linux RT Target to the LabVIEW project as it is described here
Add the RT Driver VI.vi under the Linux RT Target. (Do not canceled from LabVIEW Project My System side)
Add “Engine” Source Distribution to Build Specifications by right-clicking Build Specifications >>New>>Source Distribution.
Name it as Engine.
Local destination path must create a folder called “Built” at same location path than the custom device folder. The path must be like this: C:\...\Built\Custom Devices\”Name Custom Device”
Target destination directory:
Add the RT Driver VI.vi as “Always Included” on the Source Files category.
Source File Settings Category: Select destination for RT Driver VI.vi to the Destination Directory.
Additional Exclusions settings:
Add a post build action. You find a VI called “Copy.LLB to NI VeriStand” attached. It should be executed after you build the LLB in order to copy the LLB under <Public Documents>\National Instruments\NI VeriStand 20xx\Custom Devices. The path from step 5 b. above must be as it is described, otherwise the Copy.LLB to NI VeriStand.vi does not work.
Add the supportedTarget to the file XML how it is showed in the screenshot. VeriStand will translate to Linux path format (/C/ni-rt/VeriStand/Custom Devices/Custom Device/Custom Device Linux_x64Engine.llb) during deploy process.