Running LabWindows/CVI OSA-RTS Toolset
NI TestStand - ATML Translator Configuration
Generated Sequence File Settings
Code Module Settings
Schemas - set location / version
ATML Pad Options
LabWindows / CVI Options
Building the LabWindows/CVI Code Modules
1. Navigate to C:\OSA-RTS\ATML Demo\ATML and delete the .seq file ATMLDemo4(2017)_v1.seq
2. Navigate to C:\OSA-RTS\ATML Demo\ATML\CVI_ATMLDemo4(2017)_v1 delete CVISrcFile.c and CVISrcFile.h
3. In TestStand select File > Open File, Select Files of Type = ATML Test Description Files first, then open C:\OSA-RTS\ATML Demo\ATML\ATMLDemo4(2017)_v1
Allocating Driver Capability to the ATML Signals
There are two ways to allocate the Driver capability to the ATML Signals using the 1641 Signal Translator, manually or using a script in the ini file. We will look at using the ini file in this example.
1. Run the executable 1641SignalTranslator.exe, located in C:\OSA-RTS\TOOLSET\BIN.
2. Modify the ATML_Demo.ini file to account for the directory structure you are using.
3. Load in the ini file, it should automatically select the relevant xml files.
4. Check Coerce STDBSC Namespace and Exclude ATML comments. Select the CVI file to Parse: C:\OSA-RTS\ATML Demo\ATML\CVI_ATMLDemo4(2017)_v1\CVISrcFile.c and let the program process the command. It should load up NewWaveX to do the processing.
5. Allocation is complete when indicated as below with the “Finished CVI file” message. Select “Save Parsed File” and in the “Save CVI File As” dialog, enter a unique filename such as CVISrcFile(Allocated).c.
Completing the Test Program
Once the CVI file has been allocated, then load the CVI project CVIPrjFile.prj & perform the following modifications:
1. Exclude CVSrcFile.c from the project.
2. Include CVSrcFile(allocated).c into the project.
3. In the “Instrument Files” section of the CVI project tree, add the following library files:
The project should now look like this
4. In “Options->Environment” select “Include Paths…” and add the include paths for the folders “CVI Support files” and “__CVI Support files”.
5. Build the LabWindows/CVI project to generate the dll CodeModule.dll.
6. Exit and close LabWindows/CVI.
7. The Sequence file together with the CodeModule.dll can now be used to test the Hardware UUT. We used a DynaTec ATEC Test system for this.
8. Run the sequence file and follow the test procedure instructions.
9. Once complete an xml results file is created that can be conveniently viewed in a web browser. This gives a run down of the various Tests Passed or Failed, and the various numerical results collected.