|Download Help (Windows Only)|
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.
|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.|
|Incremental Update Complete the steps in the Calling a LabWindows/CVI Custom Code Generator DLL during an Incremental Update tutorial for information about using a LabWindows/CVI custom code generator DLL when you incrementally update a previously translated sequence file.|