TestStand 4 & Windows 7

TestStand (4.0.1) on Windows 7
When launching the TestStand (4.0.1) version selecter I get the error "HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\VISUALSTUDIO\8.0\CLR VERSION could not be found in the system registry" code: -17003.
I then click on this and the TestStand version says it has changed correctly. Then I click on 'launch' and get the error message "Sequence Editor path not found".
What is going on, is TestStand compatible with Windows 7? What has microsoft got to do with TestStand 4?
TestStand 2.0 works on Windows 7 via the version selecter.

I have a couple of theories, not sure which it is.
1) Perhaps you installed 2.0 and it was working because of this, not because of version switching.
2) Newer versions of TestStand have a manifest in the exes that keeps them from being virtualized (with regards to UAC) by the OS (not sure if 4.0.1 had these or not, but if you are writing your own UI and your UI has a manifest that specifies an access level (all newer versions of Visual Studio add this by default) then your process won't get virtualized), virtualization is the OSes way of maintaining backwards compatibility with older programs. It lets them think they are writing to the registry or protected directories even though they are really writing to virtualized versions of these only seen by that program. It doesn't always work though because sometimes things really need to be done to the real version of something and not the virtualized version.
Either way, running TestStand and Version Switcher as Admin will likely allow older versions to work on the newer OSes (though it's not officially supported). Note that older versions of Visual Studio also recommend being run as admin on Vista and Windows 7. Until Vista came out, it was typical for Windows programs to expect to be run with administrator privileges and be able to write to the program files directory.
For more info on UAC virtualization see:
http://blogs.msdn.com/b/patricka/archive/2009/12/14/tales-of-application-compatibility-weirdness-dem...
Hope this helps,
-Doug

Similar Messages

Save File dialog from dll is not appearing to the front of TestStand window

Hi all,
I am calling a C#.net dll from a step in TestStand sequence. A function is called which pops up a Save File dialog. This Save File dialog is appearing only behind other windows. There is an overload for the showDialog function that takes the owner form as argument. My dll doesnot have a form. I would like to know how can I pass the TestStand form as owner to this Save File dialog object.
Thanks in advance

Biju,
You can build create the implement the IWin32Window interface and get the handle of TestStand window. I have created an example you can check out.
Regards,
Song Du
Systems Software
National Instruments R&D
Attachments:
Class1.cs ‏1 KB

Minimize teststand window programmatically?

How do I get teststand to minimize it's execution window programmatically within a sequence step? How do I mess with any of the window propertys like making it always on top, maximizing, floating, etc...

Hi,
Are you talking about the sequence editor? To do this you need to use the Windows API to perform functions on windows. You can call into the User32.lib and call functions such as CloseWindow (minimize) to manipulate the Windows on the screen. Not sure how you would get about minimizing an execution window inside the parent sequence editor window, but I would think it should be possible. Consult MSDN for more information.
Bob

How can I create a popup panel in a CVI DLL and keep it on top of the calling TestStand application window?

When I create a panel in CVI and use InstallPopup() to display it, the user can set the focus to the main TestStand window, which causes my popup to disappear underneath it.
I'm guessing I need the popup to be a child window of the main application window. I've tried passing the Engine.AppMainHWnd handle as the parentHandle argument in LoadPanelEx(), but this causes an error, as it is not a valid handle.
Also, if I call another DLL function from a control callback within my popup, which creates another popup, on closing the second popup both disappear and the program is stuck in the RunUserInterface() of the first popup.
This seems a simple requirement, yet I don't seem to be able to find a straightforward way to achieve it.

Steve,
I think this is more a TestStand question than a CVI question.
To use a CVI popup with TestStand, you should call TS_StartModalDialog() before InstallPopup().
When you quit your popup panel, you should call RemovePopup () and then TS_EndModalDialogAndDiscard().
The TSModalData must be the same for Start and End Modal dialog.
Bruno

TestStand 4.1.1 vi search path

    This is so low-level I'm almost embarassed to ask. I'm using TestStand 4.1.1 over LabView 8.6, both of which are licensed as full development systems.
In order for our organization to make better use of (non-NI or Labview) source control, we've created a common directory structure for several developers over several large TestStand/LabView projects. This includes areas for "common VIs" that are reused across projects. So I'm in the process of migrating a rather complex project into a new directory structure. The sequences and VIs in question were working perfectly under TestStand 4.0/LabView 8.5 prior to this attempted migration.
   My test sequences (and sub-sequences) can't seem to find needed VIs, even though they exist in directories that are included in the search paths I configured. (An annoying sub-problem is that TestStand appears to "hang" while the LabView interface underneath the TestStand window is prompting for a VI's location. I have to click the LabView item in the Windows menu bar to get LabView "on top" and see what the problem is.)
   I've already added several paths to both the LabView and TestStand VI search paths, and I've even checked the "search subdirectories" box, but the items are not being found. It's going to take weeks to lead TestStand and LabView by the nose to find all this stuff.
   I can't believe this would really be a bug. I tried searching the forums for an answer and had no luck. I can't be the first one with such a problem, so help me out with some search terms so I don't have to clutter the forum with such basic stuff. Thanks.
-M

trosier, Neurotika,
It appears as if LabVIEW is having trouble finding your VIs, not TestStand. When TestStand loads the VI you have designated as a code module into memory, if you have the LabVIEW development environment designated in the LabVIEW adapter settings, we tell LabVIEW to load the VI via its ActiveX interface.
If TestStand is unable to find the top-level VI, you will see a dialog like this:
If LabVIEW is unable to find a sub-VI, you will see a dialog like this:
Notice that the TestStand dialog has an additional checkbox at the bottom that allows you to select an absolute path. Also notice that TestStand specifies what file its looking for in the Files of Type box while LabVIEW allows you to choose All LabVIEW Files. Which dialog are you seeing?
Another way to test this is to try to open one of your VIs from disk (by double-clicking on it). If you get a Searching for SubVIs dialog, then it is LabVIEW that can not find the dependencies.
Or if you open the specify module pane of the sequence editor, if TestStand cannot find the top-level VI, you will see a file not found warning like this:
If TestStand can find the file, but LabVIEW cannot find a sub-VI, then you will not get a warning or error until the VI is loaded.
The reason that this matters is that TestStand and LabVIEW do not share their search directory lists. If you have moved files, you will need to know which application cannot find its files.
Message Edited by Josh W. on 04-23-2009 11:27 AM
Josh W.
Certified TestStand Architect
Formerly blue
Attachments:
subVI not found by LabVIEW.JPG ‏31 KB
TestStand file not found.JPG ‏7 KB
VI not found by TestStand.JPG ‏31 KB

Using KeyFocus in TestStand

My LabView VI in the attachment sets string input box key-focused and waits for a text input scanned in. The VI stops running when a user presses ok button. When the VI runs in LabView environment, KeyFocus wroks fine. But, when it runs as a TestStand step in a sequence file, the KeyFocus feature does not work. I will always have to click on the text box first. This is a problem when a user forgot to click on and try to scan in. Attached files are the VI and the sequence file. I simplified to make my point. Please, advise how I can use the KeyFocus feature in TestStand/LabView environment as is in LabView only environment.
Attachments:
getKeyFocus.vi ‏33 KB
Sequence File1.seq ‏14 KB

Hi LegalEngineer,
Unfortunately you have stumbled across a bug within TestStand. There is a problem where the TestStand window gets set to the front most window right after the LabVIEW front panel launches which causes the control to lose its keyfocus. I made a slight modification to your VI that should provide a workaround. Let me know if you still have the problem with this VI.
Pat P.
Software Engineer
National Instruments
Attachments:
getKeyFocus.vi ‏33 KB

Teststand step to call a new instance of Teststand environment

I'm trying to create a troubleshooting step and I would like this step to be able to open a new instance of the Test Stand environment. If the troubleshooting step is encountered, i would want the current sequence to pause execution, open a new Test Stand sequence that will allow the engineer to perform troubleshooting steps from a parallel TestStand window, and when the troubleshooting test stand environment is closed to return to the calling sequence.
[DL]
Solved!
Go to Solution.

Hello Daniel,
I think your best bet would be to just have the steps break on failure so you can then troubleshoot from within TestStand. If you open a new instance of TestStand you will not really be able to troubleshoot the sequence you just ran, it will be troubleshooting a new sequence.
Best Regards,
Adam G
National Instruments
Applications Engineer

DLL Modal window in the background

Hi all!
I have a Borland C++ made DLL, which creates a modal window. The DLL function hasn't got any teststand specific parameters, since it is designed for general use.
My problem is the following: I have a sequence, where I put i.e. a built-in message popup (modal) before the DLL function call. In this case my modal window is in the background, and the focus is on the teststand window.
I've read the application notes dealing about this problem, but the solution written down there is via parameter passing the engine object (in my case this couldn't be done, because my DLL function is not just for teststand).
Could anyone please help me in the problem?
Thanks
Dave

Dave,
Could you add the SeqContext parameter, but ignore it if it's zero? Then non-TestStand uses could just pass in a zero and it would ignore the TestStand specific code that makes the dialog modal to the TestStand execution it was called from. Another way might be to create two versions of the function, one for TestStand that includes the SeqContext, and one for non-TestStand use, and that one statically sets the SeqContext to zero and ignores the TestStand modal functions. This method is similar to the many of the 'FunctionName' and 'FunctionNameEx' functions that allow for different uses of the same functionality (although all the examples I tried looking for where examples of obsolete (deprecated) functions).
I can't think of any other way you could do this without adding parameters.
-Jack

TestStand always load previously used file on startup

Hi,
I have a problem with my TestStand operator interface (Full featured CVI). When I open TestStand, it loads previously used sequence file by default. How could I turn it OFF.
In my Station Options, Preferences tab, Re-load last workspace at startup was not selected,which I expect Teststand not to load the previous workspace.
The only solution to avoid this problem sofar is Whenever I finish, I have to close the sequence file first and then the teststand window. But this is not possible all the time.
Has anybody have the same problem??
Thanks
mama007

Two issues with that:
a) You would need to get a reference to the ApplicationMgr from your sequence. The next version of TestStand will provide an easy way to get the ApplicationMgr, so this problem will go away. Before the next version, it might not be practical to do this without modifying the OI.
b) By the time your sequence runs, the files are already loaded. The setting change would apply to the next launch of you operator interface, but you would have to explicitly close all the open files when you first changing the setting. In the next version, when you are able to get the ApplicationMgr, this will be doable in one line simple line of code or in one step in a sequence.

Make Window Modal from SubVI

I have a VI which I want to make modal to TS so I am using the Start/Stop Modal Dialog VIs. Now, I also have a set of preconditions and a bunch of code which I will include in this and several VIs more so I decided to make a subVI that includes the StartModal VI + all the repeated operations, is there a way to do this? (using a sort of caller vi property in labvi) so far in the tests I've made LV/TestStand always make modal the VI that in which Start/Stop Modal VIs are directly placed...
Suggestions? ideas??
Attachments:
ModalVI.PNG ‏9 KB

I think the link has died - and I can't find where it's been moved to - it was a few years ago!!
Just to check - you have a VI in LV that you want to make modal to the TestStand window (UI or sequence editor), but it's not the launched VI from TestStand and it's not the VI that contains the "Start Modal"
In other words, TS calls LV VI which decides if it should call another VI based on decisions and it's that other VI that needs to be modal.
In TestStand 2014, the Start Modal vi has an extra input compared to previous versions where you can wire in a reference to the VI you want made modal (don't wire it and it assumes the current VI).
Does that help?
If you're in an older version, then I believe the Engine methods for RegisterModalWindow, UnregisterModalWindow, NotifyStartOfModalDialog and NotifyEnd Of ModalDialog should exist.
E.g. http://zone.ni.com/reference/en-XX/help/370052K-01/tsapiref/reftopics/engine_registermodalwindow_m/
You obviously need to get the HWND for the VI you've launched but this should be fairly easy :
http://digital.ni.com/public.nsf/allkb/136F6B1F34CBB76E852563FC007AEFC7
The example pointed to here used FindWindow or FindWindowEx to get the HWND based on the titlebar name from User32.dll
http://digital.ni.com/public.nsf/allkb/1B733F0C719BF70386257372002F847D
Thanks
Sacha
// it takes almost no time to rate an answer

How do I programatically open a LabView Front panel?

I want to use a test stand variable (perhaps a sequence global) to control whether certain VIs open their front panels, and wait for subsequent operator interaction. Can I get there using the API and something like this: "Step_TSInfoProp.TSInfo_StepAdditions.LVStep_ModulePathProp" ?
I tried passing a boolean to the VI and then having it optionally open its own front panel using the VI Server, but I could not see it because it would always be behind the TestStand Window.

Sean, The reason for doing this is that the client wants a "debug level" control of some sort. If set below some value, the VIs just do their thing, take their measurements, report, or whatever and go on their way blindly as what we expect a good test sequence to do. However when this value is set above some level (the threshold may be different for various categories of tests) the VI becomes interactive. This would allow an operator to see a measured value, and possibly tinker with the instrument parameters or the UUT, before continuing on. This might be similar to a single step command, but not necessarily pausing at every step. Inside of the VI I can test the value of the variable (either passed in through the connector pane or via the sequence context) and thus decide whether to be interactive or silent. I can also use the VI server to open my front panel or not. But in doing so, even though I try to make the VI panel frontmost, it is hidden by Teststand. If the VI attribute is "dialog" then it does show up on top of everything else, but unfortunately does so even when I don't tell it to open at all.
PC

Error Loading a VI of a sequence in operator interface (Error Code -18002)

I am deploying a teststand sequence using LabVIEW adapter. After deploying, while running this sequence in operator interface in the deployment computer, I get an error saying that a particular step could not be loaded. This step calls a DIO initialization VI which basically uses DIO Port Config.vi from Traditional DAQ 7.4.4 version. Please see the attached image.
Software Versions Used: Teststand 4.0.1f1, LabVIEW 8.5, Traditional DAQ 7.4.4, Simple OI shipped with Teststand, windows XP
From couple of links from www.ni.com, I did following actions in my development computer:
1. Compile All the VI in LV 8.5 using Mass Compile including Traditional DAQ LLBs, simple operator interface etc.
2. Check if any VI or step is not broken.
After getting the error, I tried opening the same sequence in sequence editor in deployment computer (I am also including sequence editor with the deployment utility), I checked DIO Initialization step. I see the warning in step indicating that the VI is either broken or one of its sub is not located. I tried using Reload VI Prototype, it asks for LVDAQ.dll which is also bundled in my deployment files. After specifying this dll, I can run this sequence without errors but after I exit from sequence editor, it does not save the changes and I get the same error in Operator interface as well in sequence editor after re launching. Also I dont want to reload VI prototype as I dont expect some to do this change after deploying the testsequence.
Kindly help.
Thanks in advance.
Nirmal
Attachments:
Auto_Cal_18002 Error11.JPG ‏25 KB

I found solution for this. While creating the workspace for my sequence and other files, I used to include all the files including the LabVIEW VIs. Doing this, DIO Config VI seemed getting confused while searching for LVDAQ.DLL in the deployment computer.
I tried only including the test sequence and letting the teststand deployment utility select the VIs from the specified directory resolved this issue. I observed that in this case, all the sub vi and the support dlls gets placed in the support and data folder respectively. This resolved the issue.
Regards,
Nirmal

Is it possible to sort or filter the switch routes under the switching tab?

In Teststand 3.1, is it possible to filter the switch routes under the switching tab in Action Properties? Since I have a large amount of routes that have been created in Switch Executive, how can I filter out some of the routes from the "Routes to Connect" section?

The TestStand Switching does not provide any inherent filtering capabilities. You do have a couple of options, however.
(1) NI-Switch provides the ability to set up route connections in
different groups. The Switch Page in TestStand allows you to
select Routing groups as well as specific Routes. It may be
easier for you to organize your Connections as groups and choose
between different groups.
(2) The Property page also allows you to build route connection
string and use that string for your Switching actions. It
may be easier for you to build a Route string and easily change that
string rather than selecting your routes everytime from within the
TestStand window.
Good Luck!
Tyler T.
Applications Engineer
National Instruments

WIN64 or _WIN64 or _NI_mswin64_

I have some code that is almost identical for 32- and 64-bit application.
Which is the best definition for selection (using #if ):
WIN32 and WIN64, or
_WIN32 and _WIN64, or
__WIN32__ and __WIN64__, or
_NI_mswin32_ and _NI_mswin64_
I am using CVI2010 on Windows 7 x64.
I build only only for WIndows (Windows XP 32, and 32- and 64-bit for Windows 7)
Sometimes I use the Windows SDK as provided by CVI.
Regards, Jos
Solved!
Go to Solution.

Hello again,
For more info to get insight I found another links which are given below.
http://zone.ni.com/reference/en-XX/help/370051T-01/cvi/programmerref/multiplatformprogguidelines/
http://zone.ni.com/reference/en-XX/help/370051T-01/cvi/programmerref/porting32bitto64bit/
http://forums.ni.com/t5/NI-TestStand/Windows-XP-64-bit/td-p/688790/page/3
Regards,
Hossein

Is there a way to use the find/replace tool to select the actual step in the TestStand sequence instead of just listing matching values in the find window?

The purpose of this is to be able to select many steps that are scattered throughout a sequence so I can change the step type one time. I could do this now, but it would take me 30 minutes to click through the sequence and select all of the steps before I'd even change the step type because there are different steps inbetween the ones I want to select. I wouldn't be able to just use the shift key to select multiple steps because of that. I have about 500 steps I need to select, so it would be worth it to find an automated way to do that.
Unless there's a way to change a step type from a numericlimittest to an action step type from the find/replace window???

I ended up using ActiveX calls in TestStand to find the steps I wanted and change the step type to Action. See attached example sequence.
Attachments:
Convert NumericLimitTest to Action step type example.seq ‏9 KB

Wait While Windows Configures TestStand

Hello everyone,
I'm having a problem when I launch TestStand in a couple of Deployment stations, I keep getting the "Please Wait While Windows Configures TestStand 4.1" message everytime I start the User Interface. I followed the instructions of this KB but that didn't fix the problem. Any ideas on how to proceed?
[Using TestStand4.1/LabVIEW 8.6]
Thanks in advance,
<<-N->>
Message Edited by << - N - >> on 01-19-2009 11:59 AM
Solved!
Go to Solution.
Attachments:
ni.jpg ‏17 KB

Hi Matt,
Thanks for your help, please see the answers below:
1. Have you ever allowed the progress bar to complete?
If so, what happens after it completes?
Yes, I have. After it completes TestStand starts normally
but if we close it and restart it the same problems would come again.
2. Are you using multiple versions of TestStand on these
deployment stations?
No, we are use only one version of TestStand 4.1
3. Have you tried uninstalling and reinstalling the
software?
No, I only try reinstall (use the repair mode) without
uninstall.Also , every time I open the MAX
and expand the "software" to see the NI software message, the same
problem will happen again

TestStand 4 & Windows 7

Similar Messages

Maybe you are looking for