LabVIEW V'sI containing TestStand API saved on different Windows versions

Hi.
I have a question regarding saving and loading of LabVIEW VI's that contains calls to the TestStand API in different versions of Windows:
Can it be true that if I create such a VI in e.g. 64 bit Windows 7 and then load it in 32 bit Windows 7 or XP with the exact same versions of LabVIEW and TestStand, the VI will need to be recompiled?
I am currently using LabVIEW 2012 SP1 f9 and TestStand 2012 SP1 f1.
Best regards
Jens Christian Andersen.
Best regards
Jens Christian Andersen.
CLA, CTA

Hi,
If the labview version is same then it need not be re compiled.
It will work with different versions of Windows (for both bitness 64\32 OS)
Ravi

Similar Messages

How to build a TestStand 2012 workspace ( insert a project / insert a folder) programmatically using LabVIEW 2012 and the TestStand API.

Hi everybody!
I am just trying to find out how to create a TestStand workspace … in LabVIEW using the TestStand API.
To create a new workspace was quite easy. Unfortunately I am not successful to insert a new or existing project to the workspace.
Furthermore I have to insert a folder from disk to the new or existing project in the way that I can use an absolute path for the directory …
Maybe someone had already solved this problem, in any case I am thankful for any hint.
Greetings from Germany,
Norbert

Have you find out how to add a folder to a project? I'm looking for this to... I tried WorkspaceObject.NewFolder[Name]whitout success...
For creating Workspace and project see the newer resolved thread I created.
Martin

Application Developed in LabVIEW 8.20 (on WIn XP) will run on Windows Vista?

Hello:
I'm developing an application in LabVIEW 8.20 on Windows XP, I've
tested the executable (*.exe) on Windows XP with no problems, however,
my client is migrating the OS of their PCs to Windows Vista and I've
been asked if the application will work on Vista or not.
For my application, I'm using LabVIEW 8.20, Fieldpoint 5.0.1 and
LabVIEW RT 8.20, and a Fieldpoint controller cFP-2100 with several I/O
modules.
Does somebody know if the application may work or not?
I hope I've been clear enough. Any help is appreciated.
Thanks in advance!
Robst
Robst - CLD
Using LabVIEW since version 7.0

Robst wrote:
Hello:
I'm developing an application in LabVIEW 8.20 on Windows XP, I've
tested the executable (*.exe) on Windows XP with no problems, however,
my client is migrating the OS of their PCs to Windows Vista and I've
been asked if the application will work on Vista or not.
For my application, I'm using LabVIEW 8.20, Fieldpoint 5.0.1 and
LabVIEW RT 8.20, and a Fieldpoint controller cFP-2100 with several I/O
modules.
Does somebody know if the application may work or not?
I hope I've been clear enough. Any help is appreciated.
LabVIEW 8.2 is basically VISTA compatible and the applciation itself is therefore very unlikely to cause any problems. I frequently have developed LabVIEW applications under one Windows version and distributed it to users employing a different Windows version and never really had serious trouble with that.
What can be tricky sometimes is giving support for installation of IO drivers such as Fieldpoint since there can be subtle dfferences to how the different installation steps are supposed to be between Windows versions. But usually if you have a user who is familiar with installing software under his OS version (and can read some installation documentation) there are very few problems to expect.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Teststand API in LABVIEW

Hello Friends,
In the sequence editor , i am able to get the TestStand API RunState.Step.Module.AsLabVIEWModule.RemoteHost = ""
But i am not able to get the same Teststand API properties in Labview with sequence Context. Herewith in attached the image for your ref.
Anyone knows how i can get the above teststand API in LABVIEW.
Thanks
Prithivi
Attachments:
Labview Teststand API properites1.JPG ‏51 KB

Hi Prithivi,
you have to cast the Module Reference to LabVIEWModule Type before you can use it. Following document will be useful to you:
How Can I Programmatically Access Information about a Code Module that a Step Executes (e.g. Name, Path)?
http://digital.ni.com/public.nsf/allkb/ADC6909C20E27D4886256E94005424E3?OpenDocument
Regards
MY
Attachments:
LVModule.JPG ‏17 KB

Teststand api Creating/deleting Users

Hi,
I am using Teststand API with Labwindows and i have a problem with creating/deleting Users.
In fact, to explain easily my problem when you use the full-featured Teststand with the "CreateDeleteUsers.seq" sequence and create a user, then close the full-featured Teststand, you loose your new users in the previous opening.
Whereas, with the Teststand 4.0, with the same "CreateDeleteUsers.seq", when you close, it propose to save the changed file "UserManagement" (Users.ini) and everything's fine...
And as i am using a Labwindows project to login/logout to teststand, i am using TS_... functions i can't find a way to save or to have this save popup to keep my users.
I hope that i am clear, and that someone will be able to help me !

Hello,
As you could see in the following KB: How Can I Edit and Save Changes for the Current User? you have to get the users file as a PropertyObjectFile as it's done in the CreateDeleteUsers sequence, and then use two methods, IncChangeCount() wich is also already done in the example sequence, and the SaveFileIfModified().
See attached file below for the example sequence changed with the file saving.
Regards,
Olivier L. | Certified LabVIEW Developer
Attachments:
CreateDeleteUsersAndSave.seq ‏11 KB

TestStand API External Component Modified Since Last VI Save

I'm using TestStand 3.5 with LabVIEW, and deploying my code across multiple stations. The code is managed by Perforce (source code control). I'm keeping the stations identical by installing NI software from the same CDs (which I'll refer to as an "Original Station"), but it seems that over time the TestStand API will somehow be externally modified ("Modified Station"), which causes LabVIEW to recompile the VI. The Explain Changes dialog box states "VI recompiled. External component modified since last VI Save." If I save the recompiled changes on a Modified Station and submit the changes, an Original Station opening the VI will then recompile VI, stating that an external component has been modified since the last VI save. If I resave the VI on an Original Station, then the next time I open it on a Modified Station the recompile will occur.
This is problematic, because there will be a performance hit if LabVIEW has to recompile when opening VIs. In addition, it makes debugging difficult, because LabVIEW will prompt to save changes on all the VIs if they were saved on a different station state. Not to mention the unnecessary copies made in the source code control to maintain the history of the recompiling.
My current solution is to reinstall TestStand on all the Modified Stations. I set any TestStand strict typedefs that I use to non-strict typdefs, mass compile the TestStand addon folder in vi.lib, and then the station becomes an Original Station again. Overtime, it will modify itself and turn into a Modified Station. Since these stations are at multiple sites, it is very inconvenient to manage.
My questions are the following:
1. What is causing this external modification? Is there anyway to prevent it, so that the installation and code will not get modified so that all will remain Original Stations?
2. If it is not preventable, how can I force all stations to become a Modified Station, so at least they are all the same?
I've attached LabVIEW 8.5 VIs that demonstrate the VI differences. I've observed this behavior in LabVIEW 7.1 and 8.2 previously. If anyone also experience this behavior or has a work around, please post to this thread. If NI has insight on what is causing this behavior and how to prevent it, it will help me out greatly.
Thanks!
Attachments:
test_recompile_original_lv85.vi ‏7 KB
test_recompile_modified_lv85.vi ‏7 KB

Wilbur,
Do you have more than one version of TestStand or LabVIEW on the stations? Switching the active version of TestStand changes the registered version of the TestStand API which I believe is the external change that forces a recompile. If version switching is the cause of the problem you could prevent these changes by not sharing any TestStand VIs between different versions of TestStand. If each version of TestStand has its own VIs then a VI is compiled against one and only one engine version.
-Rick Francis

TestStand API in C#

Hi,
we develop a software in C# which uses the TestStand API.
we note that TestStand API allocates memory at the first execution of a TestStand sequence
All the memory of this first execution is not deallocate at the end.
why ?
Is it a problem with Active X technology ?
Is it a conserved memory for the next execution ?
Is it possible to not have this comportment ?
For information, we have deactivated the generation of the TestStand report.
Thanks for the answers
Best regards

There is memory allocated when an execution is run for many different reasons. Please be more specific as to which memory you are referring. Choose one of the following (or add your own if I have forgotten one).
1) Memory used by result collection (to store results under Locals.ResultList while an execution is running). These are typically freed once the process model is done processing them typically for report generation or database logging. By default the process model processes them between runs of the mainsequence on the UUT. These results are also freed when the execution completes (i.e. stops running). If you are not using a process model or do not need results for specific steps or sequences you can disable result collection on a per-step, per-sequence, or global basis.
2) Memory used to keep the sequences and executions themselves in memory. These datastructures stay in memory as long as you have a reference to them. One additional twist with .NET is that you might not think you have a reference to them, but you really still do because .NET hasn't gotten around to garbage collecting the references yet. You can force garbage collection as follows with the following code:
        public static void DoSynchronousGCForCOMObjectDestruction()
           // To make sure activex refs are synchronously released
           // we need to call GC.Collect() and GC.WaitForPendingFinalizers()
           // at least twice, according to the following document:
           // http://msdn.microsoft.com/en-us/library/aa679807%28v=office.11%29.aspx
           // The reason we have to do it twice is that the the first call
           // might just sweep the objects into generation 2 rather than collecting
           // them immediately.
           GC.Collect();
           GC.WaitForPendingFinalizers();
           GC.Collect();
           GC.WaitForPendingFinalizers();
3) Memory used by code modules being loaded. This memory is freed when the step settings on your code modules say to unload your modules, but the behavior is somewhat different depending on the adapter. Some adapters can unload code modules on a per-code module basis, but the .NET adapter can only unload code modules when all code modules and .NET objects created by the .NET adapter are no longer supposed to be loaded or referenced. That is because in .NET the only way to unload code modules is to unload the appdomain containing them. TestStand uses a single appdomain for the .NET adapter and unload that appdomain when all .NET code modules referenced by the adapter are unloaded and all .NET references gotten from those code modules into TestStand are no longer in scope.
Hope this helps explain things.
-Doug

Load a VI (including TestStand API) in TestStand

He,
I'd like to load a VI in TestStand without LabVIEW.
LabVIEW Version 8.5
TestStand Version 4.0
The PC with TestStand just have LabVIEW Runtime Engine 8.5, and the VI is used to import data in station globals; Also, This VI calls TestStand API and TestStand Engine.
On a PC with LabVIEW and TestStand, all is OK.
But, on a PC with Runtime only, even if I configure Adapters in TestStand and Select LabVIEW Run time 8.5, an error message is displayed (unable to load VI ... )
I have tested with a simple VI (dialog box), all is ok;
But with VIs thaht called API TestSTand, error is displayed
Do you have an idea ?
Thank you for your responses
Solved!
Go to Solution.

Yes, I understand that you use TestStand in development system and the VIs are in an llb there. What I ASKED was where you placed the TestStand VIs on the runtime only pc. It sounds like you did not place them anywhere. If you didn't, how do you think the top level VI is going to work? You don't think that these VIs are included in the runtime engine do you? They are not. Only the LabVIEW primatives are in the runtime engine.
You should really consider using the deployment tool.

How do you get a handle to a TestStand API SequenceCallModule Object?

I am trying to programatically specify the SequenceName for a sub sequence, created using the TestStand API called from LabView. SequenceName is a property of the SequenceCallModule object but I cant see how to get the object handle.
Can anyone help?
Regards
Steve
There are 10 types of people in the world that understand binary, those that do and those that don't.

Hi,
you can actually do this. I was speaking to Steve yesterday on this :
starting with the handle to the appropriate step (I've done it in the attached sequence file in TS, but should translate nicely to LV)
so I use the sequence to get the step by name
I can then get the step.module
then using the TESTAND ADAPTER API (and not the Teststand API)
I can use the module returned above with the SequenceCallModule class from the TestStand AdapterAPI then. (you have to know ahead of time what the appropriate module / adapter type is otherwise it will have problems)
Hope that helps
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer
Attachments:
3_0 using adapter specific sequencecallmodule.seq ‏39 KB

Is it possible to call a VI that is inside a LabVIEW executable from a TestStand sequence?

I have created a custom TestStand operator interface and have modified the default sequential process model to display a UUT information dialog that prompts for more information than just the UUT serial number. This UUT information dialog is a LabVIEW VI. To distribute the operator interface, I build it into an executable. As part of the build process, I make a copy of the UUT information dialog VI (which is part of my operator interface project) and place it in the same folder as the executable. I have then configured the sequential process model to call the dialog VI from this location. It would be really nice if I could embed the UUT information dialog VI inside the operator interface executable so that I could distribute just an executable instead of an executable and separate VIs. Is this possible? In other words, is it possible to call a VI that is inside a LabVIEW executable from a TestStand sequence just like a standard LabVIEW VI call?

Ryan,
The dialog that you've created isn't being directly called by the OI at all and shouldn't need to be included in the same directory as the OI for distribution. Since you are modifying the PreUUT of the default process model, you will give the path to the VI in that step, create a deployment and then manually copy the VI to the directory referenced in the step. The VI is considered a support file for the process model and is not related to the OI at all.
Test Engineer - CTA

Activating locks using TestStand API

Hello,
I have a question... how do I lock and unlock a lock, created in TestStand, in Visual Basic (by using the teststand API)?
Greetz Jan Toebes

Hello,
To understand you correctly you are trying to perform a lock or unlock through Visual Basic. For this you have to use the synchronization server, which has a different API for itself. You can get more information about this under "TestStand Supplemental Reference Help" section in the TestStand Help.
For simplicity sake, lets assume that you have a lock step created in teststand and you want to perform an unlock using Visual Basic.
To perform this task, you need the SyncManager. This is the main class for all Synchronization objects. This class helps manage the creation and sharing of the different Synchronization objects between threads. You must create all Synchronization objects using this class.
To get the appropriate instance of the TestStand Synchronization Manager call the Engine.GetSyncManager TestStand API method. The Engine.GetSyncManager method returns the TestStand Synchronization Manager for the appropriate process based on the name of the Synchronization object. So the call would be
SyncManager = Engine.GetSyncManager(* Name_of_the_lock_Step)
where the Name_of_the_Step is the actual name of the lock step that we created in TestStand. The "*" before that indicates that this lock step was created in a separate thread and is being shared.
Now Mutex is the class that implements the Lock synchronization and is used to implement the Lock step type in TestStand. So using the SynCManager will get an instance of this Mutex class by using:
Mutex = SyncManager.GetMutex(* Mame_of_the_lock_step)
Now using Mutex you can perform an unlock by using:
Mutex.EarlyUnlockMutex ( threadId)
Please refer to the help for more information regarding these functions. I hope this helps.
SijinK
National Instruments

Visual Studio TestStand API runtime enable/disable XML reporting file creation

I am looking for a Visual Studio C# solution to selectively disable creation of the report generation XML file using the TestStand API.
These XML files are useful for active troubleshooting for technicians, but wind up cluttering important directories with useless information most of the time.
I am aware that the XML file creation can be disabled through the TestStand Sequence Editor menu item Configure | Result Processing | Output Name Report | Enabled unchecked option.
This is helpful, but:
1. I have not found a way to check-uncheck this feature at runtime.
2. I do not believe that this would be an effective solution for my instal-less Base Deployment Paradigm.
Any help or ideas would be appreciated!
Solved!
Go to Solution.

Thank you for the quick and concise response James_Grey!
This is useful, complete, and implementable but not exactly what I was hoping for.
I was hoping to be able to enable/disable the XML file creation for the currently executing instance of the engine prior to sequence start.
I would rather not disable reporting through a configuration file that would effectively disable it for all uses of TestStand until it was re-enabled again.
Are my expectations unrealistic?
Does anyone have any idea how creation of the XML file can be enabled/disabled for an active instance of the engine prior to sequence start through the API without altering the file based configuration of TestStand?
I have seen some postings around 2008 that indicate this can be done, but I was unsuccessful implementing those solutions in TestStand 2013.

TestStand API: Set relative path

Dear NI community!
Could someone help, please, with the following - is there is some option to set file path to code modules, inside test sequence, to have relative, but not absolute path? I add programmatically code modules to sequence steps, but currently they have absolute path. Is it possible to change it to relative with TestStand API?
Thanks in advance.
Solved!
Go to Solution.

I was wrong. It's possible to manually cut path to file (according to Search Directories of TestStand). Then code modules will be added with relative pathes. But one should be careful - path should be cut correctly.
For example, I have full path
E:\Development\source code\supplementary\TestVIs\Code Modules\Service\Print.vi
My Search Directory is
E:\Development\source code\supplementary\TestVIs\
So, I need to cut like this:
Code Modules\Service\Print.vi
and without slash at the beginning!
Then it will be OK.

TestStand API terminate all notification

I've developed a LabWindows based user interface using the TestStand UI controls and the TestStand API. I have a sequence file that has several cleanup steps, some of which take a while to finish. One function of the user interface is an Emergency Stop button. When this is pressed, an Engine.TerminateAll is issued via the API. The test fixture has 8 sockets which are using the Batch Model TestUUts entry point. Is there any easy way via callback or other means of knowing when all the terminations have completed. I would like to display a popup telling the operator to wait while the cleanup steps are being carried out. I also want to disable the START button and reenable it when the terminations are complete.
I am launching the execution with TS_EngineNewExecution and I can get the id. I tried to wait until I saw this execution end with the ApplicationMgr EndExecution event or the Execution VIew Manager EndExecution event but I saw a bunch of exection id's except the one that I was looking for. It may be my fault but I wanted to ask and see what is the best approach for what I am trying to accomplish.
John

Hey John,
Your method will work, and your assumptions are partially
correct. If you look in the Batch Process Model, inside of the
Cleanup Step Group of Test UUTs there are steps that tell all
TestSocket executions to stop. There is also a wait step that
forces the Process Model execution to wait until all of the TestSocket
executions have terminated. There are going to be multiple EndExecution
events because it is going to occur for each execution that finishes
whether it is the Process Model execution or one of the TestSocket
executions. However, the Process Model will always be after all of the
TestSocket executions have completed.
Another thing to keep in mind is that this is only happening because it
is built into the process model. Normally if you spawn off a new
execution it is separate from your original execution, and the new
execution would not terminate by calling the terminate method on your
original execution. You would have to either do a terminate on
each execution or use the terminate all method of the application
manager. Hope this helps to clear things up a little.
Pat P.
Software Engineer
National Instruments

[svn:fx-trunk] 5321: -remove textLayout_textField.swc because textLayout. swc should now contain the API from it

Revision: 5321
Author: [email protected]
Date: 2009-03-16 08:50:51 -0700 (Mon, 16 Mar 2009)
Log Message:
-remove textLayout_textField.swc because textLayout.swc should now contain the API from it
and updated the build scripts to reflect the removal
-changing the name of the textlayout rsls. Removed the build number from the swf and swz so that they won't have to be removed from src each time we take a new build. Use tlf.properties to get the correct build number
checkintests: pass
qa: yes - need to make sure that textlayout.swc contains everything from the swc's that have been removed
Modified Paths:
flex/sdk/trunk/build.xml
flex/sdk/trunk/frameworks/libs/textLayout.swc
flex/sdk/trunk/frameworks/projects/flex4/build.xml
flex/sdk/trunk/frameworks/projects/framework_textLayout/build.xml
flex/sdk/trunk/frameworks/projects/wireframe/build.xml
flex/sdk/trunk/in/tlf/tlf.properties
Added Paths:
flex/sdk/trunk/in/tlf/textLayout.swf
flex/sdk/trunk/in/tlf/textLayout.swz
Removed Paths:
flex/sdk/trunk/frameworks/libs/textLayout_textField.swc
flex/sdk/trunk/in/tlf/textLayout_391.swf
flex/sdk/trunk/in/tlf/textLayout_391.swz

LabVIEW V'sI containing TestStand API saved on different Windows versions

Similar Messages

Maybe you are looking for