Various Issues Using LabWindows/CVI Test Executive 2.01
Primary Software: LabWindows/CVI Add-ons>>Test Executive
Primary Software Version: 2.0.1
Primary Software Fixed Version: N/A
Secondary Software:
Problem: Are there any issues that I should be aware of when using LabWindows/CVI Test Executive, Version 2.01?
Solution: The following information is from the readme.txt file:
It is recommended that you do NOT install LabWindows/CVI Version 2.01 on top of a previous versions of the Test Executive.
After Installation- It is recommended that you recompile any tests previously compiled for an earlier version of the Test Executive Toolkit.
- (Windows 95/NT Only) The structure packing for the tTestData and tTestError structures is now consistent for all compatibiliy modes under Windows 95/NT. The "#pragma pack(8)" statement was added to the txengine.h header file.
- (Windows 95/NT Only) The Test Executive Toolkit expects the calling convention of tests in a sequence to be "__cdecl". If you set your default calling convention to __stdcall, you must use the __cdecl qualifier on tests called by the Test Executive. You can do this by using the TX_TEST macro located in txengine.h.
- If you are using LabWindows/CVI 3.1, you must use interim versions of the toolbox and inifile instrument drivers that contain some new functionality available in the LabWindows/CVI 4.0.1 versions. The interim versions will be installed into the toolkit's /toolbox/ subdirectory.
- (Windows 95/NT Only) If you are using the Base Package of the LabWindows/CVI 4.0.1 for Windows 95/NT, you will need to use the additional import libraries located in the tookit's /sdk/ subdirectory.
- The Test Executive Toolkit standalone executable has been created using LabWindows/CVI version 4.0.1 "msvc" compatibility mode. You must rebuild the executable using the testexec.prj project file if using a different compatibility mode.
- When opening the example sequence files, you will be asked to update the file paths. By clicking on the 'Yes' button the Test Executive updates the paths and prompts you to save the changes.
- (Windows 95/NT Only) If you plan to use the Test Executive Toolkit with an external compiler, please refer to Chapter 5 of the Test Executive Toolkit Manual for further details.
- (Windows 95/NT Only) The CallVB Addon example ActiveX DLLs are compiled with Microsoft Visual Basic version 5.0. These DLLs import the Visual Basic Library MSVBVM50.DLL. This library file is distrubuted with this toolkit. The CallVB example ActiveX DLLs must be registered with the operating system as ActiveX DLLs. This can be done by using the "register.exe" located in the \callvb\ subdirectory. When the DLL is not registered properly, the TXCALLVB DLL will return one of the following OLE errors:
- OLE Error 800401f3 = Invalid class string
- OLE Error 80020006 = Unknown name
Note: The ActiveX DLLs executed by the CALLVB Addon cannot display Visual Basic forms.
- (Windows 95/NT Only) The CallVI Addon is created with LabVIEW 4.1. Any LabVIEW Test Executive VI test must be built with the same version of LabVIEW that is used to build txcallvi.exe.
- (Windows 3.1 Only) Windows 3.1 has limited stack space. This limit prevents the Test Executive Toolkit from loading and executing more than a depth of seven hierachical subsequences. Using the Test Executive as a standalone executable will increase the available stack space.
- (HP-UX only) The static library file ./txengine/txlib/txengine.a is not distributed with the installation because of its size. You must use the ./txengine/txengine.mak file to rebuild the static library before using this toolkit.
Changes to Documentation- The Test Executive Toolkit Reference Manual (PN 320863B-01) incorrectly specifies the TXFUNC qualifier for the prototype for a test or pre/post function. The qualifier should be TX_TEST. (Pages 2-6, 4-1, 4-4).
Related Links:
Attachments:
Report Date: 11/11/1997
Last Updated: 10/23/2002
Document ID: 13A7ET72
