Hello Sonet -
The only way that it would be possible for the TScvirun.prj to open and work with this function any different from the numericlimit test function is if there is a breakpoint somewhere in the C-file. Certainly, if hitting F5 in CVI resumes the execution then it sounds like breakpoint behavior. If you open the project and look at the C-file and do not see any visible breakpoints, one thing you might try is to investigate the master breakpoint manager window at Run>>Breakpoints to see if they are listed there.
If no breakpoints are visible anywhere but it still seems to be pausing on a line of code, you can rebuild your tscvirun.prj from the default as a way of resetting all the files. (In TestStand Configure>>Adapters, select CVI, put in an abso
lute path for the tscvirun.prj and select 'Rebuild').
The next time you run with the tscvirun.prj it will add your c-file and compile it.
Alternate ways of running this file could be to create an object file for it, or to build it into a DLL. Once the DLL is created, you can debug it from CVI rather than TestStand, check in the User Manual's chapter 13 starting on page 14 for details.
--Regards
Elaine R.
National Instruments
http://www.ni.com/support
