You are here: NI Home > Support > Product Reference > Manuals > LabVIEW 8.6 Microprocessor SDK Help

Complete the following steps to configure the target syntax for a new target.

1. Copy labview\examples\TargetSyntax to your target directory in labview\Targets. Features that the LabVIEW C Generator does not support are already included in the VIs that determine the target syntax.
   1. LVEDefaultNumericType.ctl determines the default data type of front panel controls. For example, if you are creating an integer-only target and want the default data type for numeric controls to be a 32-bit signed integer numeric, create a custom int32 control.
   2. LVEUnsupportedNodes.vi determines which nodes the target does not support.
   3. LVEUnsupportedFunctions.vi determines which functions the target does not support.
   4. LVEUnsupportedTypes.vi determines which data types the target does not support.
   5. LVEUnsupportedVIs.vi determines which subVIs the target does not support.
2. Edit the VIs described in step 1 by placing unsupported features on the block diagram of the appropriate VI. Save the VI.

   Note  For targets with very limited functionality, you also can create a VI that contains only the features that the target can support. Name supported functionality VIs LVESupportedxx.vi where xx follows the naming convention of the unsupported VIs.

3. Select Tools»Microprocessor SDK»Configure Target Syntax to open the Configure Target Syntax dialog box.
4. On the Nodes tab, add the unsupported nodes.
   1. Navigate to and select LVEUnsupportedNodes.vi, which is the VI that contains the unsupported nodes.
   2. (Optional) Navigate to and select the VI that contains the supported nodes.
   3. Place a checkmark in the Unspecified nodes are unsupported checkbox if you are using both unsupported and supported VIs and you want nodes to be unsupported if the nodes are not in either VI.
5. On the Functions tab, add the unsupported functions.
   1. Navigate to and select LVEUnsupportedFunctions.vi, which is the VI that contains the unsupported functions.
   2. (Optional) Navigate to and select the VI that contains the supported functions.
   3. Place a checkmark in the Unspecified nodes are unsupported checkbox if you are using both unsupported and supported VIs and you want functions to be unsupported if the functions are not in either VI.
6. On the Data Types tab, add the unsupported data types.
   1. Navigate to and select LVEUnsupportedTypes.vi, which is the VI that contains the unsupported data types.
   2. (Optional) Navigate to and select the VI that contains the supported data types.
   3. Place a checkmark in the Unspecified nodes are unsupported checkbox if you are using both unsupported and supported VIs and you want data types to be unsupported if the data types are not in either VI.
7. On the SubVIs tab, add the unsupported subVIs. Unsupported subVIs must be the labview\vi.lib directory.
   1. Navigate to and select LVEUnsupportedVIs.vi, which is the VI that contains the unsupported data types.
   2. (Optional) Navigate to and select the VI that contains the supported subVIs.
   3. Place a checkmark in the Unspecified nodes are unsupported checkbox if you are using both unsupported and supported VIs and you want subVIs to be unsupported if the subVIs are not in either VI.
8. On the Default Type tab, navigate to and select LVEDefaultNumericType.ctl, which is the custom control that contains the default data type.
9. (Optional) On the Misc. tab, adjust the settings for maximum recursion depth, variable support, and so on. You usually can keep the default miscellaneous settings.
   1. Enter a maximum recursion depth for supported data types in the Max Type Depth box. For example, a cluster of an array of integers has a type depth of 3. A cluster of an array of a cluster of strings has a type depth of 4. A value of -1 ignores the maximum type depth.
      
      Setting the Max Type Depth to prevent nested types from being recursive, which is not permitted by MISRA (The Motor Industry Software Reliability Association) automotive coding standards.
   2. Enter the maximum number of dimensions for arrays in the Max Array Dimensions box. A value of -1 ignores the maximum array dimension.
      
      Setting the Max Array Dimensions to 1 to restrict users to only optimized 1D array operations, which can increase application performance.
   3. Place a checkmark in the Support global variables checkbox if the target supports global variables.
   4. Place a checkmark in the Support local variables checkbox if the target supports local variables.
   5. Select the Errors break the VI radio button if you want target syntax errors to break the VI.
   6. Select the Errors are considered warnings and do not break the VI radio button if you want LabVIEW to consider target syntax errors as warnings rather than errors.
10. Enter the directory path to the target in the Location of target field.
11. Click the Generate button to create TargetSyntax.xml, which is the file LabVIEW uses to check target syntax, in the target directory you specified in step 10.
12. Click the Save button to save the TargetSyntax.xml file. You must save the file as TargetSyntax.xml for LabVIEW to recognize the target syntax for your target.

Note  Clicking the Generate button does not automatically save the TargetSyntax.xml file. You must click the Save button to save the file.

My Profile | Privacy | Legal | Contact NI   © 2009 National Instruments Corporation. All rights reserved.   |