NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

deployment and modelsupport.seq

I use a customized process model in my design.  I'm building the deployment, and I tell the deployment to get the process model and put it into a certain \user folder.  This model, like the default sequential model, references ModelSupport.seq, ModelSupport2.dll, reportgen_xml.seq.  I did not modify these files at all.  Do I have to somehow point to these files in the deployment.  All of those files are already installed on the target machine.
0 Kudos
Message 1 of 2
(3,272 Views)
Hello Mr. Bean,

By default, NI's process models store code module path as a relative path.  So, the path to the ModelSupport2.dll is stored as ModelSupport2.dll instead of C:\Program Files\National Instruments\TestStand 4.0\Components\NI\Models\TestStandModels\ModelSupport2.dll.  TestStand finds this file by appending the relative path name to all of the search directories until it finds a file.  If your target computer has the default search directory of C:\Program Files\National Instruments\TestStand 4.0\Components\NI\ enabled to search through all sub-directories (which it should), then your custom process model should not have a problem locating ModelSupport2.dll and all of the other model support components.

You can also deploy your search directories by including <TestStand>\cfg\TestExec.ini in your workspace (and then in your deployment), as your search directories are stored in TestExec.ini.

Also, "TestStand 4.0" can be replaced with "TestStand <version>" for the above paths.  I hope this helps!
Best Regards,
Software Engineer
Jett R
0 Kudos
Message 2 of 2
(3,245 Views)