Chapter 2Wrapping Drivers and Math Libraries 1,Target Distribution 1,Guide2-4ni.comYou still need to create a subVI for the block diagram before you can use FuncList.dat, but the VI can be empty except for the necessary controls and indicators corresponding to the parameters for the function.TipConsider first creating a subVI with a Call Library Function Node or an Inline C Node to make debugging the input and outputs of the function easier. After you get the subVI working correctly in an application, you then can modify the FuncList.dat file with the substitute code to improve the performance of the application.Refer to the LabVIEW Embedded Development Module Porting Guide, available by selecting Start»All Programs»National Instruments»LabVIEW»LabVIEW Manuals and opening EMB_Porting_Guide.pdf, for more information about FuncList.dat.Naming VIsVI names do not have the same limitations as C function names, so make VI names descriptive. Descriptive names make it easy to identify and use a VI on a block diagram. National Instruments also strongly recommends that you create unique filenames for VIs. One way you can make sure a filename is unique is to preprend a short name or abbreviation to the VI name. In addition to keeping VI names unique, adding an identifier to the VI name also helps end users find a VI that is specific to your target. For example, the filenames for Analog Devices Blackfin targets start with BF to keep the names unique and easily identifiable.