Calling Tcl Scripts in TestStand
Requirements
Filename: readme.doc
Software Requirements
Application Software: NI TestStand Development System 3.5
Reader Comments | Submit a comment »
Thanks for the feedback!
The Tcl Example has been updated to fix the
problems reported.
- Allen Piscitello, National Instruments. allen.piscitello@ni.com - Jun 13, 2007
This needs to be updated. Test Stand 1.0 is
old now.
- Chris , Dallas . - Oct 12, 2004
These example doesn't work with TCL version 8.4 and higher
You have to include two additional
functions "Tcl_FindExecutable
&Tcl_GetNameOfExecutable" and put these
portion of code in the InitInterpreter()
function.
The Tcl_FindExecutable procedure computes
the full path name of the executable file
from which the application was invoked and
saves it for Tcl's internal use. The
executable's path name is needed for several
purposes in Tcl.
void InitInterpreter ()
{
if (!init) { Tcl_FindExecutable
(Tcl_GetNameOfExecutable());
init = 1;
}
- Mesut Sözüçok, Delphi Delco Electronics Europe GmbH. mesut.soezuecok@delphi.com - Jun 4, 2004
more examples would be useful
the example works, however, I could not make
my own script run, looks like test stand
does not wait to tcl to finish, how test
stand knows when Tcl is done interpreting
the script?
Jorge Moreno
Test Engineer
- jorgeraulmoreno@hotmail.com - Aug 21, 2003
Legal
This example program (this "program") was developed by a National Instruments ("NI") Applications Engineer. Although technical support of this program may be made available by National Instruments, this program may not be completely tested and verified, and NI does not guarantee its quality in any way or that NI will continue to support this program with each new revision of related products and drivers. THIS EXAMPLE PROGRAM IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND AND SUBJECT TO CERTAIN RESTRICTIONS AS MORE SPECIFICALLY SET FORTH IN NI.COM'S TERMS OF USE (http://ni.com/legal/termsofuse/unitedstates/us/).
