TestStand Debugging of CVI

I have a CVI 7.1 project (.prj). I also have a TestStand 3.1 sequence that calls numerous functions within the various CVI source files. Without TestStand, I cannot run my CVI project (I think). But when I load my seq in TestStand and select Test UUT, I get an error that says
Error loading Step Pass/Fail Test ...
Unable to get Standard CVI Step Module address for DepotInitialize.
DepotInitialize is the routine I'm trying to call in the Setup tab of TestStand's sequence editor.
What I'm wondering is, how can I debug to see where the problem is occurring? Within CVI, I can either create a Release or Debug executable, but if my project consists only of files that perform specific tests, and therefore (the .prj) contains no main, how do I step into the code and test it.
What I've been trying to do is deploy using TS. I created a TS workspace that contains two TS .tpj files. The first points to my app .prj, .lib, .seq. The second points to TestStand's .exe, .ico, .uir files. I'm not sure if this is correct.
I'm confused on the relationship between TS and CVI .prj files. If I open my seq in TS, how does it know if I've built the CVI project as debug or release.
I just want to be able to step through my code. How do I do that.

Ray,
I am finally trying to debug my app, and I'm running into problems. I opened my LabWindows/CVI project and changed the Build::Configuration to Debug (from Release). I then went to Run:pecify External Process and entered the C:\teststand\bin\seqedit.exe (although for me it's in a slightly different location). When I select Run:ebug seqedit.exe, the TestStand sequence editor opens. I browse to the location of my sequence. When I select OK, a second TestStand and CVI instance open. In the second TestStand, my sequence steps appear. I select F5 to Test UUTs and I receive an error saying
Sequence 'MainSequence' in the file 'LMBSU_TestStand.seq' could not be executed.
Error loading step 'Pass/Fail Test' of sequence 'MainSequence' in the file 'LMBSU_TestStand.seq'. Unable to connect to tscvirun.dll in the CVI project. Make sure that tscvirunn_supp.c is in your project and that the project is runnable. Error Code -17711. Source 'TSAPI'.
My CVI project has tscvirun_supp.c in the project. I ran this two ways - once without rebuilding the DLL and once with. The second time, the DLL created had a different name (it had dbg in the name). Any suggestions?

Similar Messages

Understanding TestStand Debug Deployment License

After reading the License Agreement and the TestStand Help section on licenses I still would like an explanation as to exactly what the license does and does not allow. My understanding is with a TestStand Debug/Deployment license I can install TestStand on a machine, let's call it the development machine, and also install TestStand on another machine, my production machine. The development machine is where I would develop applications to deploy onto my production machine. The production machine is where I would actually test my products. The production machine can also be used as a platform to debug my deployed applications. If this is true then can I develop any additional tests on the production machine, e.g. I found a problem in the sequence so I need to add a new sequence to correct the error? Or I found a problem with a LabVIEW VI and I need to create a new VI to correct it. Can I develop VI's and sequences on the production machine or do I need to develop on the development machine transfer the files over to the production machine and hope it works (this type of process could prove to be very time consuming and tedious)?

Thanks for the info. Now what about LabVIEW. Here are some options I'm considering:
1. Run a LabVIEW Runtime Engine on the production machine and a FDS of LabVIEW on the development machine. In turn run a TestStand Deployment license on the production machine. This seems the most cost effective method. The problem I'm having is some VI's are developed in LabVIEW 6i, 7.0, and 7.1 and the LabVIEW 7.0 RT Engine does not work with TestStand 3.1. It seems only the LabVIEW 7.1 RT Engine will work with TestStand 3.1. But I don't have a LabVIEW 7.1 development license (not sure how the 7.1 VI's came to be, before my time). I've also thought of using standalone LabVIEW applications but the only license I have for Application Builder is from LabVIEW 6i PDS from the Developer's Suite. If TestStand 3.1 is suppose to work with any LabVIEW RT engine then I'm doing something wrong.
2. Run a LabVIEW Development/Deployment license with a TestStand Development/Deployment license. This is the most expensive method but the easiest to implement.
3. Run a LabVIEW FDS and a TestStand Deployment license on the production machine.
A finally question, does NI make available a TestStand Run-time Engine that is available as a free download, similar to the LabVIEW Run-Time Engine?

Teststand debug cvi

CVI 7.1.0
TestStand 3.0
application: TestExec
I have been compiling and debugging without any problem, but suddenly I can't debug my testexe. I can debug other apps and if I move my project to another machine I can debug there (although it is running CVI 7.0 and Testand 3.0).
After compiling and linking I press Shift+F5 and CVI acts as if it is going to bring up testexec but it then disappears completely. I have tried setting break on first statement but it never gets there.If I execute the exe with Ctrl+F5 it runs fine. I have noticed that there is data in the debug output window, it is difficult to copy it all because it scrolls so fast but I managed to copy the following. This listing was long so I have omitted some lines.
[ff0,1c0] LDR: Real INIT LIST for process c:\Program Files\National Instruments\TestStand 3.0\OperatorInterfaces\User\Full-Featured\CVI\TestExec.exe pid 4080 0xff0
... lines omitted...
NAME - InitializeCriticalSectionAndSpinCount
[ff0,1c0] LDR: WINSPOOL.DRV loaded - Calling init routine at 73004D00
[ff0,1c0] LDR: SHLWAPI.dll loaded - Calling init routine at 77F651FB
NAME - CreateTimerQueue
... lines omitted...
[ff0,1c0] LDR: COMCTL32.dll loaded - Calling init routine at 5D0932DA
NAME - InitializeCriticalSectionAndSpinCount
... lines omitted...
[ff0,1c0] LDR: SHELL32.dll loaded - Calling init routine at 7C9E7376
... lines omitted...
[ff0,1c0] LDR: Real INIT LIST for process c:\Program Files\National Instruments\TestStand 3.0\OperatorInterfaces\User\Full-Featured\CVI\TestExec.exe pid 4080 0xff0
[ff0,1c0] C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll init routine 773D42B3
[ff0,1c0] LDR: comctl32.dll loaded - Calling init routine at 773D42B3
... lines omitted...
[ff0,1c0] LDR: comdlg32.dll loaded - Calling init routine at 763B1AB8
[ff0,1c0] LDR: ole32.dll loaded - Calling init routine at 774FD0A1
[ff0,1c0] LDR: OLEAUT32.dll loaded - Calling init routine at 77121558
[ff0,1c0] LDR: cvirte.dll loaded - Calling init routine at 685E0BA8
... lines omitted...
f0,1c0] LDR: Real INIT LIST for process c:\Program Files\National Instruments\TestStand 3.0\OperatorInterfaces\User\Full-Featured\CVI\TestExec.exe pid 4080 0xff0
[ff0,1c0] C:\WINDOWS\system32\psapi.dll init routine 76BF10F1
[ff0,1c0] LDR: psapi.dll loaded - Calling init routine at 76BF10F1
NAME - EnumProcesses
NAME - EnumProcessModules
NAME - GetModuleFileNameExA
[ff0,1c0] LDR: Real INIT LIST for process c:\Program Files\National Instruments\TestStand 3.0\OperatorInterfaces\User\Full-Featured\CVI\TestExec.exe pid 4080 0xff0
(1) [cvi.DLL] C:\Program Files\National Instruments\CVI71\cvi.DLL (0) deinit 0
(1) [psapi.dll] C:\WINDOWS\system32\psapi.dll (0) deinit 76bf10f1
[ff0,1c0] LDR: Real INIT LIST for process c:\Program Files\National Instruments\TestStand 3.0\OperatorInterfaces\User\Full-Featured\CVI\TestExec.exe pid 4080 0xff0
[ff0,1c0] C:\WINDOWS\system32\uxtheme.dll init routine 5AD71626
[ff0,1c0] LDR: uxtheme.dll loaded - Calling init routine at 5AD71626
[ff0,1c0] LDR: Real INIT LIST for process c:\Program Files\National Instruments\TestStand 3.0\OperatorInterfaces\User\Full-Featured\CVI\TestExec.exe pid 4080 0xff0
[ff0,1c0] C:\WINDOWS\system32\MSCTF.dll init routine 747213A5
[ff0,1c0] LDR: MSCTF.dll loaded - Calling init routine at 747213A5
NAME - NtQueryInformationProcess
NAME - CtfImmCoUninitialize
NAME - CtfImmLastEnabledWndDestroy
NAME - CtfImmSetCiceroStartInThread
NAME - CtfImmIsCiceroStartedInThread
NAME - CtfImmIsCiceroEnabled
NAME - CtfImmIsTextFrameServiceDisabled
NAME - CtfImmEnterCoInitCountSkipMode
NAME - CtfImmLeaveCoInitCountSkipMode
NAME - ImmGetDefaultIMEWnd
NAME - ImmReleaseContext
NAME - ImmNotifyIME
NAME - ImmSetConversionStatus
NAME - ImmGetConversionStatus
NAME - ImmGetProperty
NAME - ImmGetOpenStatus
NAME - ImmGetContext
NAME - ImmSetOpenStatus
NAME - ImmInstallIMEA
NAME - ImmGetDescriptionA
NAME - ImmGetDescriptionW
NAME - ImmGetIMEFileNameA
NAME - ImmGetIMEFileNameW
NAME - ImmSetHotKey
NAME - GetUserDefaultUILanguage
NAME - GetClipboardSequenceNumber
NAME - GetSystemMetrics
NAME - MonitorFromWindow
NAME - MonitorFromRect
NAME - MonitorFromPoint
NAME - EnumDisplayMonitors
NAME - GetMonitorInfoA
NAME - EnumDisplayDevicesA
NAME - MsgWaitForMultipleObjectsEx
NAME - VirtualProtect
NAME - VirtualQuery
NAME - __CreatePtrInfoForCommandLine
NAME - malloc
NAME - VirtualProtect
NAME - VirtualQuery

Thanks for moving this post to the TestStand forum so other customers can find it.
The issue will be answered in this post: http://forums.ni.com/ni/board/message?board.id=180&message.id=22807
Message Edited by Mist on 05-02-2006 10:26 AM
Josh W.
Certified TestStand Architect
Formerly blue

Updating of TestStand data from CVI Callback

How do I update the variables in TestStand from a callback function in LabWindows. In the attached file the use must press the pass or fail button. This action is received in the callback function in CVI where I call the TS_PropertySetValBoolean method in TestStand. The variables are updated and the notification is processed but only when the close button is pressed. If the update conditions are removed the Notification event is sent correctly (when either pass/fail is pressed).
Attachments:
TS_NewThread.zip ‏15 KB

Hi Steven,
Not sure I understand your problem.
When you press the Pass button the Pass/Fail step passes and when you press the Fail button the Pass/Fail step fails. (therefore your FileGlobals is being updated correctly).
Don't know why you have the Set Notification after the Pass/Fail step as you have nothing running waiting on this action.
The MainSequence is then left waiting to complete and this does happen until you close the new thread by closing your GUI.
Regards
Ray Farmer
Regards
Ray Farmer

Passing a struct from TestStand to LabWindows/CVI

I am passing a struct to a dll written in CVI.
Here is the problem: The code is written in CVI (c code) if I use "struct MyStruct *MyData" as the parameter definition in the dll TestStand works fine. But if I define my struct using a typedef (i.e. typdef struct MyStruct) then use MyStruct *MyData as the parameter TestStand throws a warning.
I an using the C\C++ adaptor.
It is too late in the programming effort to go back and remove the typedef.
So, how do I get TestStand to accept the typedef?
Thanks
Carmine
Solved!
Go to Solution.

In ANSI C, the struct names and type names belong to separate namespaces. You can declare structs several different ways:
1) struct structName { int x; };
2) typedef struct { int x; } typedefName;
3) typedef struct structName { int x; } typedefName; // Note: structName can be same as typedefName.
I'm assuming you are using the 2nd example above in which case LabWindows/CVI automatically generates a struct name (something like __unknown_1) that Testand uses.
Although you said it is too late to remove the typedef, can you add a struct name as in example 3 above? You can use the same name as the typedefName and TestStand will recognize it.

How to know pro-grammatically variable type(string ,numeric ....) of TestStand variable using CVI

Hi,
how to know pro-grammatically variable type(string ,numeric ....) of TestStand variable using Labwindows CVI.
Thanks
Mukesh Kumar

Mukesh,
You could use the TS_PropertyGetType() function in CVI to do this. Here is a reference page for the GetType function--you can see that it returns a PropertyValueType which will indicate which type the PropertyObject (variable) is. In CVI, you'll find this function in the NI TestStand API 2013 instrument methods, under PropertyObject > Static Properties.
Hope it helps, and let us know if you have any more questions about it!
Daniel E.
TestStand Product Support Engineer
National Instruments

How do I retrieve a teststand stepname from CVI

I am trying to retrieve the step name for the current step I am executing from CVI. I have tried using TS_PropertyGetValString (stepobj, NULL, "Step.Name",0, &tempstr) with no luck.

Hi,
attached is an example of retrieving the Step Name.
Hope this helps
Regards
Ray Farmer
Regards
Ray Farmer
Attachments:
GetStepName.c ‏2 KB

Teststand cvi probleme de callback

Bonjour,
J'utilise TestStand(2013) en mode Batch parallel et mon interface utilisateur est gérée par CVI(2012).
Quand j'ai besoin d'informations provenant de l'utilisateur, Teststand appel une de mes DLL CVI.
Au debut de ma sequence (dans le model option) Je viens demander plusieurs informations à l'utilisateur et les échange entre teststand et cvi se passent très bien.
Lorsque mes socket sont créés j'arrive bien à mettre à jour mon interface graphique via CVI, mais mes Callback ne fonctionne plus.
Par exemple je souhaite seulement attendre l'appui par l'utilisateur sur un bouton de commande.
J'utilise donc le RunUserInterface dans ma fonction, que ma callback vient acquitter lors de l'appui sur le bouton.
Le problème est que l'appui sur le bouton ne fonctionne pas. Cela ressemble un peu à un problème de gestion des événements.
Une chose étrange est que lorsque je passe en mode debug sur CVI, ma callback fonctionne correctement.
Je voudrai savoir si quelqu'un a déjà rencontré cette situation ou si quelqu'un à une idée?

Bonjour,
avez-vous déjà essayé ceci ?
Error Code 145 - ActiveX Control Not Registered in LabWindows/CVI
http://digital.ni.com/public.nsf/allkb/9894BE2B832B7FDE86256ECD00041172?OpenDocument
Aurelie

Intermittent problem with TestStand calling CVI DLL calling MSCV DLL

Sorry about cross post, but I am not sure which group is best to address
this issue.
Setup:
Windows 2000 SP1
TestStand 2.01f
CVI 6.0
MSVC++ 6.0 SP5
Problem:
I have a CVI Test Library DLL that contains test functions called by
TestStand using the C/CVI adapter. The CVI Test Library DLL in turn makes
several calls to another DLL written in MSVC++. I am experiencing an
intermittent problem with one of the MSVC functions. The problem ~appears~
to be stack related, but I am not sure. Among other things, this MSVC
function accepts a const char * argument that is a TestStand lookup string.
The function uses this string to access the TestStand API.
What happens is this: Everything works fine. I then recompile the CVI DLL
after making some mod, then run. The MSVC++ DLL asserts that the const char
* arg passed by the CVI DLL is NULL. However, this is not the case if I
single step through the CVI code. It has happened both with passing
variables as the const char * argument and as hardcoded strings literals, so
its not that I am actually passing NULL. The other argument to this
function is the TestStand sequence context dispatch pointer (LPDISPATCH
pobjSequenceContextDisp) and it always ~appears~ to be passed correctly.
The problem is frustrating and hard to debug because I can not
deterministically reproduce it. The problem ~never~ appears when I debug my
MSVC++ DLL in Visual Studio. And it only occasionally appears otherwise.
The problem, when it appears, always appears on the first run after
recompiling the CVI DLL, though the problem does not happen after ~every~
recompilation. I'd say it happens 1 in 6 times after a recompile.
Recompiling the exact same code does not always make the problem disappear.
If I change the CVI code (code that has nothing to do with the argument
itself though) and recompile the problem almost always goes away. Selecting
'Mark all for compilation' and rebuilding does not make the problem go away.
Only tweaking the CVI code and recompiling does (usually).
Whats more, the problem appears:
* With the CVI DLL built as Debug or Release mode.
* With the CVI default calling convention set to __stdcall or __cdecl.
* With the C/CVI TestStand adapter set to run in-process or external
instance of CVI.
The problem appears to be some sort of stack or argument passing problem
between CVI and MSVC, though thats just a guess based on the symptoms. I
have quadruple checked the calling conventions of all declared functions.
The CVI DLL functions all use TX_TEST (which resolves to __cdecl). The MSVC
DLL functions all explicitly use __stdcall. Is there a problem with calling
__stdcall MSVC functions from a __cdecl CVI function?
I can find no other memory leaks or indications of memory corruption
elsewhere in either the CVI or MSVC DLLs. Its only this one function that
exhibits this strange 'null const char *' problem.
Can anyone offer any ideas about what may be causing this problem? Anything
else I should check/verify?
Regards,
Joe

Silvius,
> Although I'm not sure if any of the following are the real cause of
> your problem, I have the following suggestions:
Thanks for the reply. At this point any and all suggestions are welcome...
> 1. There could be a problem with calling
> __stdcall MSVC functions from a __cdecl CVI function. As a workaround
> wrap the _cdecl call inside a _stdcall call that is exposed or
> exported to TestStand or vice-versa. This can be a problem because if
> _cdecl is used, the calling function is responsible for cleaning up
> the stack and if _stdcall is used, the called function is responsible
> for cleaning up the stack.
I was under the impression that as long as everything was explicitly and
consistently declared, you could safely mix cdecl and stdcall f
unction
calls. Is it bad to do this? Is this a known issue with the CVI compiler?
I've never seen a problem with doing this under MSVC++.
I'll try wrapping them in cdecl calls for CVI - though we have a
depressingly large number of stdcall functions in the MSVC DLL ;-). They
need to remain stdcall in the DLL because we also call them from Visual
Basic.
> 2.Don't mix Debug version of one DLL with the Release version of the
> other DLL. I had some bad experiences doing this and both DLLs where
> developed in MSVC. Allways use either Debug either Release versions of
> DLLs.
I verified that the MSVC DLLs were either ALL Debug or Release. I too have
seen nasty problems when MSVC Debug and Release is mixed.
One thing I had not thought of until your reply: What about mixing CVI Debug
DLLs with MSVC Release DLLs? Have you ever seen issues with doing this?
Thanks!
Joe

How to load programmatically from CVI the specific sequence file in TestStand 3.1

I am trying to implement TestStand from Windows/CVI 3.1. I need to insert a specific sequence file in TestStand, with all other sequences unloaded. I used TSUI_ApplicationMgrCloseAllSequenceFiles() and TSUI_ApplicationMgrOpenSequenceFile(), but after Username/Password prompt, the TestStand loaded all the old sequences. How to eliminate this?

Hello,
I created a function that calls those two methods. When I made a simple CVI button and in a callback for it, I call my function, it does successfully close all open sequencefiles and then load the one I specified; however, it does not work when I call the function just before the call to RunUserInterface! I am very surprised by this and will be bringing it up with our R&D department. There is a simple work-around. Instead of closing all open sequencefiles at the beginning of the OI, close them at the end instead. I have modified the full-featured OI for you and tagged in the code where I made changes. This should do exactly what you want (you may want to change the code around to make it a little cleaner...I left more in code in than I needed for instructive purposes). Please let me know if you have any questions about this. Take care!
Regards,
Aaron B.
National Instruments
Attachments:
TestExec.c ‏55 KB

I am getting the message error when trying to run the labwindowa/CVI adapters for debug

See attachments for error message and teststand settings. I am running testand 4.0.1
It was working before and suddenly it crash and then I am getting that error message every time
Regards
Attachments:
ErrorLoadCallback.jpg ‏32 KB
ErrorLoadCallback2.jpg ‏134 KB

It seems that something might still be corrupted or not registered properly. Have you tried running the TestStand Version Selector to re-select your current version of TestStand as the active version?
Also, you mentioned that it crashed and now things aren't working. What exactly occurred when it crashed? Was this just TestStand freezing, or did the entire system freeze or crash? Did you see an error message of any kind?
If the version selector doesn't help things, I would suggest a reinstall of TestStand (and possibly CVI, but let's start with TestStand). To clarify, we want to do an uninstall/reinstall rather than a repair, because the repair will only replace missing files. If a file is corrupted, the uninstall/reinstall should replace it.
Let us know how it goes!
Daniel E.
TestStand Product Support Engineer
National Instruments

TestStand how to check debug mode

I want to close the execution windows when done, and for this i've inserted a statement at the begining of the process model : RunState.Execution.TypeMask = RunState.Execution.TypeMask + 0x10. But i would like it to be executed only in debug mode.
How can i check TestStand debug mode ?
JMC
JMCe

I've found my answer : i've a boolean "IsEditor", updated with an ActiveX action :
Object reference : RunState.Engine
Automation Server: TestStand API
Object class : Engine
Get Property : ApplicationIsEditor.
There are a lot of methods and properties accessible with ActiveX, but not so easy to find !
JMC
JMCe

Setting requirements on a TestStand step through the API using CVI

I'm generating TestStand sequences using CVI.
I have no problem to create new sequences, new steps, add parameters, set comments...
But I haven't found how to add requirements on a step.
Could someone give me the function(s) to call on the TestStand API to do this ?
thank you
Vincent

Hey VCourousse,
You need to get the Step.Requirements as a property object, Get the Links object from that and then SetValStringByOffset. Links is an array of elements in the Requirements property.
Here's what it'd look like:
PropObjectReq = Step.Requirments
PropObjectLinks = PropObjectReq.GetProperyObject("Links", 0)
PropObjectLinks.SetValStringByOffset (elementinRequirements, 0, NewValue)
Hope that gets you on the right path.
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

Tutorial on teststand user interface to cvi

I haven't used the CVI to TestSand User Interface since 2004. I've been put on an upgrade project to go from Windows 2000 to Winows 7, TestStand 3.0 to TestStand 2010, and CVI 7 to CVI 2010. Now I have to make the old UI work.
Are there any good tutorials out there on the CVI user interface for TestStand?
More specifically, I'm trying to figure out why the TS_EngineGetResourceString doesn't work now? (more specifically how does TS_EngineGetResourseString work)
Thanks
"Lockheed" Joe
Testing Blog"

Hey Joe,
Here are some great resources for you to check out on building user interfaces. The first link is an example and the second is more of a general discussion on interface development. If the forums ever don't suffice, you may be able to find more information by searching NI's website for 'Cvi User interface TestStand'. Just another great spot to check for answers.
Simple CVI User interface for TestStand
Best Practices for NI TestStand User Interface Development
Hope this helps,
Luke W

Unable to include Operator Interface in TestStand deployment

Hello. I have created a test system using TestStand 3.5.
There is only one sequence file, and this sequence calls several VIs
that I have created in LabVIEW 8.0. I would like to distribute
this test system to a target computer, which will then run the default
Operator Interface. No bells and whistles, just plain and
simple. However, I'm running into problems.
First, I created a Workspace file in TestStand. I then added a
Project to it. In the Project, I added all necessary files for my
project (the sequence file as well as all of the custom VIs).
Then I proceeded to follow the TestStand reference manual in order to
deploy my system.
For reference, text in italics is the reference guide and text in bold is my comments.
Deploying the TestStand Engine
1. Launch the TestStand Deployment Utility by selecting Tools»Deploy
TestStand System from within the sequence editor.
I did this, and set up my build how I wanted it.
2. On the System Source tab, enable the Deploy Files in TestStand User
Directories option.
This option collects files from the <TestStand>\...\User
directories, so that any customizations that you have made to process
models, step types, language strings, and so on, will be distributed to
the target computer.
I did this, and copied my Operator Interfaces\NI folder to Operator
Interfaces\User. This would assure (I hope) that I would have the
default operator interfaces included in my project.
3. On the Installer Options tab, enable the Install TestStand Engine
option.
Done.
4. On the Installer Options tab, click Engine Options to launch the
TestStand Engine Options dialog box, which you use to select the
TestStand components that should be present in the installer.
Done. Everything is checked.
In the TestStand Engine Options dialog box, expand Operator
Interfaces»Full-Featured in the tree view.
a. Click the X next to LabWindows/CVI to include the
Full-Featured LabWindows/CVI Operator Interface in the engine
installation. The X should become a green checkmark.
b. Click OK to accept the new settings and close the dialog box.
This is where things go wrong. There is NO Operator Interfaces box in my tree view. It simply doesn't exist.
I've tried several different builds using different strategies.
I've done builds with the CVI operator interface in the User directory,
and I've also tried copying over the files manually. On the
target computer, I've always gotten either an error message (Could not
open the TestStand Engine), or else TestStand opens in evaluation
mode. In both cases, my custom VIs and sequence files are nowhere
to be seen. Can anyone shed some light on this? It's
driving me a bit crazy!
Thanks very much,
Brett Gildersleeve

Hi Brett,
Whenever you deploy your TestStand application to target machines, you will always needs a license. The licenses for distributing TestStand are different than for distributing LabVIEW and LabWindows/CVI code modules.
LabVIEW does not require you to purchase any run-time licenses for a deployment system. You can even run LabVIEW VIs in VI format (not executables) from TestStand without using the development environment and without an additional license.
In order to run LabWindows/CVI code modules, you will need the LabWindows/CVI Run-Time engine which is also available free of charge.
Regarding TestStand, you will need a license for each machine that runs a TestStand sequence. TestStand has three types of licenses which are the TestStand Development System License, the TestStand Debug Deployment Environment License, and the TestStand Base Deployment Engine License.
TestStand Development System License
The TestStand Development System License is required for any test sequence development and/or editing of existing TestStand sequence files that you perform within the TestStand Sequence Editor or programmatically using the TestStand API.
TestStand Debug Deployment Environment License
The TestStand Debug Deployment Environment License gives you maximum flexibility for deploying TestStand and LabVIEW, LabWindows/CVI, and Measurement Studio-based systems. This license allows you to install the development versions of TestStand, LabVIEW, LabWindows/CVI, and Measurement Studio, along with any corresponding add-on toolkits, so that you can debug your test application on your deployed test station. This license does not include the ability to perform any development tasks within the TestStand Sequence Editor or programmatically using the TestStand API.
The TestStand Debug Deployment Environment License has debugging capabilities including settings breakpoints, monitoring variable values, and stepping into test code directly from the TestStand sequence.
(Note: This license does not provide the software but rather gives you the right to install a previously purchased piece of software on the target machine.)
TestStand Base Deployment Engine License
The TestStand Base Deployment Engine License is the minimum license required for all deployed TestStand-based applications. This license allows you to deploy the TestStand Engine, a TestStand Operator Interface, and TestStand sequence files to the single test station for which the license is applicable.
The TestStand Base Deployment Engine License provides simple sequence debugging capabilities, including setting breakpoints and single stepping through test sequences in your Operator Interface. You cannot save sequences and open the sequence editor.
I hope this clears things up.
Best Regards,
Jonathan N.
National Instruments

TestStand Debugging of CVI

Similar Messages

Maybe you are looking for