Use the example project and source files located in the <TestStand Public>\Examples\Toolkits\ATMLTDTranslator\Code Generator\CVI directory as a starting point for implementing a LabWindows/CVI function that calls a specific code generator callback.

Use a function prototype for each callback the LabWindows/CVI custom code generator uses. Refer to the individual callback topics for more information about the LabWindows/CVI function prototype for each callback.

Complete the following steps to use the example project and source files to generate complete LabWindows/CVI code modules:

1. In LabWindows/CVI, open <TestStand Public>\Examples\Toolkits\ATMLTDTranslator\Code Generator\CVI\CVICodeGenerator.prj.
2. Build the project to generate the dll.
3. In TestStand, select Tools»Configure ATML TD Translator to launch the ATML Test Description Translator Configuration dialog box.
4. Click the Code Module Settings tab and enable the LabWindows/CVI option.
5. Click the Browse button next to the Path to Custom Code Generator DLL control and browse to the path of the dll you built in step 2.
6. Click OK to close the ATML Test Description Translator Configuration dialog box.
7. Close all open sequence files.
8. In TestStand, select File»Open File to launch the File Open dialog box.
9. Browse to <TestStand Public>\Examples\Toolkits\ATMLTDTranslator\Translator\Test Description 1.0\Computer 1.0.xml.
10. Click Open to translate the TD instance document to a TestStand sequence file and a set of LabWindows/CVI code modules.
11. Review the translated sequence file and the generated code modules.
    Note If an <Action> or <Test> element contains a child element of the OperationConnect, OperationRead, or OperationDisconnect type, the translator creates new Connect, Read, or Disconnect functions and precedes each function name with the name of the source <Action> or <Test> element. For each element of the OperationConnect, OperationRead, or OperationDisconnect type that exists under a parent <Action> or <Test> element, the translator updates the function body with a call to the newly created functions. The example demonstrates how to insert a new parameter named UUID, which TestStand passes to the code module, and how to change the flags of the Step and Sequence elements to non-editable and non-deletable, respectively.