Test Executive Still Uses Default Callbacks Even Though I Specify a Path to the Custom Callback in the SequencePrimary Software: LabVIEW Toolkits>>Test ExecutivePrimary Software Version: 5.1 Primary Software Fixed Version: N/A Secondary Software: N/A
Problem: I have made a modification to the Test Report Callback.vi. I save the modified VIs under a new .llb named personal callback.llb. If I now in edit mode go to "Sequence Options »Sequence VIs" and change the path to the Test Report Callback.vi to point to my modified one in \personal callback.llb, then it still uses the default one specified in the "testexec.ini" file when I run the sequence. The only way I can get the Test Executive to use my modified VI is to change the path in the testexec.ini file, but that modification affects all sequences. Solution: The reason for this is that the default callbacks specified in testexec.ini are always loaded into memory when the Test Executive starts. If a sequence specifies alternate callbacks, then those VIs are loaded at the time the sequence is loaded. Of course, if one of the alternate callbacks has the same name as a callback which is already loaded (regardless of whether the path is different), the VI which is already loaded is used. This is because LabVIEW cannot have different VIs with the same name in memory at the same time, even if their paths are different. If you change your custom callback's name from Test Report Callback.vi to something else, you should see the problem go away. Related Links: Attachments:
Report Date: 12/11/1997 Last Updated: 06/14/2004 Document ID: 14A7KSEW |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
