Change client sequence file when Ctrl F5

I have a teststand 2010 and labview 2011 based test system. I have modified the 'Single Pass' sequential model so that when Ctrl+F5 is pressed, 'main sequence' from a self test sequence is run, not the 'main sequence' from the currently loaded test sequence. It all seems to work but when the test report is created it contains the name of the loaded test sequence, not the name of the self test sequence...
Is there a way in teststand to say that the client sequence is the self test sequence not the test sequence loaded into teststand when Ctrl+F5 was pressed, therefor the report filename will contain the name of the self test sequence not the name of the current loaded test sequence ???
Any help or pointers would be very helpful...
Cheers
Derren Price
Solved!
Go to Solution.

Rather than modifying the model to change which sequence is called, you should modify it to change the client sequence file. Look at the DynamicClientSequenceFile example in the TestStand examples directory.
Hope this helps,
-Doug

Similar Messages

How can I restore FileGlobals in a Client Sequence File that is reloaded?

Hi,
I'm using TS2.0.1f1 and dynamic client files (search "DynamicClientModel" to see an example) in order to load different test sequences depending on what product should be tested.
We do something like this,
newseq = IEngine.GetSequenceFile(...)
Execution.ClientFile = newseq
Do testing
IEngine.ReleaseSequenceFileEx(newseq)
Goto
The first time a client sequence file is loaded it will copy the default FileGlobals from RunState.ProcessModelClient.Data.FileGlobalDefaults (TS does this automatically).
The problem though is that after calling ReleaseSequenceFileEx() the actual sequence isn�t really disposed. Since when we later start over with another prod
uct that uses the same client sequence file the GetSequenceFile() call returns the same copy that was used before and doesn�t copy the FileGlobals from RunState.ProcessModelClient.Data.FileGlobalDefaults, there by the second time the same sequence file is used, the FileGlobals don�t have there default values.
So, to get back to the subject, how can I make sure that the second time around the FileGlobals have there default values?
(Keep in mind that all this is done within the same execution of the processmodel.)
I�ve included a short demonstration of this in the attached zip file.
Any help appreciated.
Cheers,
Hans
Attachments:
TestModelFileGlobals.zip ‏12 KB

Hi Scott,
Thanks for the answer, I had been thinking about option nr 1 in particular but that would require more changes than I'm prepared to do right now.
I tried option nr 2, but instead of adding that line to the client sequence file I made the copy operation in the process model like this.
Execution.ClientFile = Locals.ClientSeq
Locals.ClientFileGlobalsRef = Execution.GetFileGlobals(Locals.ClientSeq)
Locals.SerializedCopy = ""
[RunState.ProcessModelClient.Data.FileGlobalDefaults] PropertyObject.Serialize(Locals.SerializedCopy, "Test", 0)
[Locals.ClientFileGlobalsRef] PropertyObject.Unserialize(Locals.SerializedCopy, "Test", 0)
This seems to do the trick, although option nr 2 does seem a bit like doing things the way they weren't
supposed to be done.
Regarding option nr 1, are there any �Best Practice� documents, guides or examples on how one should best manage Engine and Execution lifetimes? Or to put it differently when to spawn new Executions and or Engines during the span of working with several units of the same product type and/or different product types?
Cheers,
Hans

How to get the loaded client sequence file path/name?

I added a step in Process model, and wanted to get currently loaded client sequence file name/path. I used the variable of "SequenceFile.Path" but then I realized what I would get is the process model file path, not loaded client sequence file path/name. How can I get loaded client sequence file path/name?
Thanks!
Jacky

I dont understand what you are trying to achieve. Can you provide more information.
If you are trying to dynamically load and run a client sequence file at run time you need to make a couple of calls to the TS API from inside the process model, Engine.GetSequenceFileEx to get a reference to your sequence identified by its pathname, and then Execution.ClientFile to tell the process model which sequence you want to run.
Steve
There are 10 types of people in the world that understand binary, those that do and those that don't.

Reload sequence file when changes on disk

Hi,
I wrote a custom user interface based on the TestStand (TS) Operator Interface. When I run a sequence file on it and I edit it in the TS editor and I restart an execution, it seems to keep loading the first one when I launch the execution. The only way I can do this is by restarting the GUI.
I read a lot and tried many things and I can’t figure out what do I need to do to have the sequence file reload from disk on the 2nd execution after changes has been made.
I tried many thing and it seems to work when I release the seq file 2 times (!). But, as expected, the 2nd time it get released, I get an error that the file was unloaded from the TestStand Engine. And the weird thing is that I don’t get the error when I run the 1st time or I don’t make changes to the seq file.
Do you see anything wrong? Or have another suggestion how I could achieve that?
Can I see which seq files are in the internal cache? That could be useful to debug.
Thank you.
A code snippet in C# is in attachement.
Attachments:
C#-code.rtf ‏2 KB

A few more ideas:
1) Are you perhaps using this file path with an ApplicationMgr or SequenceFileViewMgr API? You need to make sure that this file is not open by the ApplicationMgr or assigned to a sequencefileviewmgr as well. The applicationmgr or sequencefileviewmgr likely have a strong reference to the sequence file if you have assigned it or opened it with one of their APIs. You might want to try switching entirely to the applicationmgr APIs instead of using the engine APIs as that's probably less likely to lead to conflicts between the two.You could try ApplicationMgr.OpenSequenceFile() and ApplicationMgr.CloseSequenceFile().
2) Have you tried this with a simple, empty sequence file and simple default Sequential process model to verify that it's not related to anything in the sequence file you are running or any code elsewhere in your application? It's possible for code in the sequence or process model itself to be calling GetSequenceFile or GetSequenceFileEx.
3) Have you tried adding a delay between WaitForEndEx() and ReleaseSequenceFileEx()? This is not that likely to be the cause, but perhaps there is additional code required to execute in the execution thread after WaitForEndEx returns before the sequence file can be unloaded. If you add a small delay (i.e. Thread.Sleep(1000) between those lines of code it might work. This would not explain why the file couldn't be reloaded when you use GetSequenceFileEx with the UpdateFromDisk flag though so probably is not the problem.
I tried to reproduce this problem in the sequence editor by running an
execution with a sequence file, closing the sequence file, overwriting
it with a different sequence file and reopening it and I was unable to
reproduce the problem. I got the new file opened as expected. This is
the equivalent situation since there is a completed execution still
open. The sequence editor does not use the Unload flag on
ReleaseSequenceFileEx, but it does use the UpdateFromDisk flag on
GetSequenceFileEx() and it seems to work, correctly loading the new
version of the file in this case. So there must still be something different in your case. I suspect that it's not the execution that has the extra reference in your case, but something else, perhaps the ApplicationMgr or SequenceFileViewmgr.
Also, as a side issue, if you are writing a custom UI, I'd recommend using UIMessages to determine when an execution completes rather than WaitForEndEx(). Basically handle the ApplicationMgr.UIMessageEvent and look for UIMsg_EndExecution and check that the execution associated with the UIMessage is the one you care about. Using the UIMessage like this has a couple of advantages:
1) It allows your UI to go back to executing in it's main message processing loop (Some things will not work correctly without this).
2) It gives you the potential to track and handle running multiple executions in parallel. Just look for and track the multiple UIMessages that such executions generate.
Please let us know if any of these ideas helps or if you are able to figure out the cause of the problem. If you are still unable to get it working and can't figure out the cause, please attach an example program and sequence files which reproduce the issue.
Hope this helps,
-Doug
Message Edited by dug9000 on 03-02-2010 10:03 AM
Message Edited by dug9000 on 03-02-2010 10:04 AM

What is the best method for saving the client sequence file revision in the database \ report?

I'm trying to figure out the best way to store the sequence file Revision in the database. That is, if I have the Revision (SequenceFile.AsPropertyObjectFile.Version), where (e.g. what table / field) should I put it if I'm using the SQL Server schema that ships with TestStand? How do I get it there?
Certified LabVIEW Architect
Wait for Flag / Set Flag
Separate Views from Implementation for Strict Type Defs
Solved!
Go to Solution.

Ok LabBEAN,
Here is my tutorial. It is actually easier than I thought:
Step 1: Configure>>Database Options and uncheck the Disable Database Logging.
Step 2: Click the Data Link tab
Step 3: Make sure the Connection String Expression is pointing to the right location. Should be a public directory with a .mdb file if you are using TestStand defaults. Click the View Data button to verify. It should open the Database Viewer so you can look at the tables. Leave the Database Viewer open.
Step 4: Click the Schemas tab
Step 5: With the Generic Recordset (NI) selected click the Duplicate button.
Step 6: You should now see a copy of that schema. In the Name box name it MyRecordset and make sure it is checked
Step 7: Click the Statements tab and highlight STEP_SEQCALL. NOTE: you must always do this before clicking on the Columns/Parameters tab
Step 8: Click the Columns/Parameters tab
Step 9: Highlight the SEQUENCE_FILE_PATH item and click the Copy Button
Step 10: Highlight the new entry and change the Name to SEQUENCE_FILE_VERSION
Step 11: MOST CRITICAL STEP: Change the Expression to RunState.Engine.GetSequenceFileEx(Logging.StepResult.TS.SequenceCall.SequenceFile, 107, ConflictHandler_Error).AsPropertyObjectFile.Version It is better to do it this way because you never now where a sequence file call will be made and not all sequence calls are made to the model client sequence.
Step 12: Hopefully you left the Database Viewer open from Step 3. Go to it.
Step 13: Right click the STEP_SEQCALL and select Add Column.. Name the new column: SEQUENCE_FILE_VERSION. Basically you need a column that matches the one you created back in the Columns/Parameters tab. Set it up with the same type and size. NOTE: there is an alternate way to do this using the Execute SQL View in the Database Options but you need to create it. You can create it from the Schemas tab back in TS by clicking the Build .sql File.. button.
Step 14: Back in TestStand click OK to save and close the Database Options.
Now run your sequence and you will see the new data in your database.
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

Photoshop Elements 7 - format changes to temp file when saved

When I open a file in the edit screen (quick edit) and then edit the file -- when I close it (and agree to replace the current image), it closes as a temp file and I lose the jpg file? It does state that the image "Could not save as ..... because the file is already in use or was left open." Then I close it and the jpg is gone. Is there some setting I have to change? I just want to make changes and then save as the same file so I only have the new, edited image? I know I have done this before.
I am using Vista and Photoshop elements 7. I had elements 4 before and this never happened. In fact, I used my elements 7 before and it never happened.
Thanks for any help.

Please explain more as if your new file is not created properly or it is not recognized as a supported file format. In later case you will see some unsupported file format icon when you save the file and check its file icon.
Also when you save the file, a jpeg settings dialog box comes up. Make sure you select appropriate settings.
If you find that its just the unsupported file, then try opening the file with File->open As and choose jpeg and see if its opening.
Also try open with after right click the image icon and browse and choose PSE as a default app for opening a file.
-garry

Fonts changed to Unix files when saved to a remote server

Hi all, I read an archived thread regarding this, but not sure if my situation is related somehow. The issues others have had was that their font files were converted to Unix files at 0KB, when stuffed.
My issue is I backed up fonts (PS and TT) from my Mac to a remote server (PC based). When that server is accessed by Mac users, some saw the file as a Unix file at 0KB. However, there were some (including myself) that saw the actual font file.
That was a few months ago, we've retired that server since, but before doing so I transferred all the fonts to a new server. It's now a raid drive run off a Mac Xserve. After the transfer, I checked to see if the fonts were still okay, and they were showing full Mac file (no Unix). I didn't go into the new server for a couple of months, but when I did I noticed that all the fonts had been changed to Unix files. Some were at 8KB, others at 60KB. But no 0KB files. +Note: because the initial transfers was a success, the original files from the old server were deleted along with it. So there is no way of retrieving the original files. As well, were were running 10.4.10 with the original server and files. Switched to 10.5.x when files were transferred to the new server.+
I've tried the tips here (using the Terminal method and the FileUtilsCM script) http://discussions.apple.com/message.jspa?messageID=6041364 but to no avail. I'd hate to think these fonts are scrap. As they were all purchased (and there's a whole load of them). Any input in saving these files would be of great help.
Thanks in advance.

The real font information is stored in a resource fork, not the data fork fo the file. Depending type type of file system you copied them to, how you copied them, and what method you are using to look at them, you may not be seeing the resource fork.
You can see more detail about files usng a Terminal command such as
ls -leaO@ file
If there is a resource fork, it will be displayed.
If the file system was not a Mac OS X external file system, then you might want to look for a file with a similar name only starting with a leading period to make it invisible to the Finder
ls -leaO@ /the/directory/with/your/fonts

How do I stop Photoshop CS6 from asking to save changes to a file when closing the file, after "savi

I save a lot of files to "save for web". After saving PS asks if I want to save changes to the original file. I never want to save the changes to the original. Since the default is to change the file I am afraid I will accidentally OK the change without wanting to. I would like it to stop asking and just not save it. Is there a way?

Stephen Douge wrote:
I never want to mess with originals. I am asking because I want to make sure I stated the question properly in the first place. Thanks.
Then don't work on the original open the file using Photoshop menu file>open once its in Photoshop as a document dupe the document and close the original document. Photoshop will just close the original and not ask it you want to save the original document for no changes were made to it. You could easily record an action to automate this process. The first step in the action would be an inserted menu item menu File>Open. The second step Duplicate Document, third step select previous document the fourth and final step close. The action would look like this recorded Work in the dupe and save it under the name you want to where you want it saved. The First step is an interactive you will be able to open any file Photoshop has support for that you have access to.

Type List Order Numbers (typelistordernum) change when opening a sequence file in Test Stand

Could you please shed light on the reasons a sequence file changes upon opening in the Test Stand development environment?
Comparing the file before and after, I see that the typelistordernum changed on a few custom types that we defined for the program. .
To clarify the environment, I am using two work stations running the same version of Test Stand. The workstations are kept in sync using Sugar Sync. One would expect that a file saved on one workstation could be loaded on the other work station with no change.
This also happens on files that we pull from version control (GIT). Once opened, they change, which presents a serious problem in avoiding version conflicts and keeping track of real changes.
Test Stand Version: 4.5.1

ATE Coder wrote:
In fact it turns out that conflict resolution is fairly hard to resolve.
For instance, changing a type (add a comment) changes its time stamp. As a result, all sequence files referring to this type are now in conflict.
On testing, Test Stand does not seem to flag these. So, they could be pushed into the repositories as is.
Opening the sequence files on another machine (after pulling to code from repositories), Test Stand detects a conflict that in fact is no conflict at all. Now all these files need to be checked in and pushed up and then pulled down. This increases the chances of code conflicts many folds and seems to be totally superfluous.
Turning off automatic conflict resolution does not seem to resolve this issue.
It would seem that for some reason (inertia?), NI pulled into Test Stand the same tight versioning it uses in LabVIEW. While in LabVIEW, where, in fact, one is editing compiled code, thins might add some value, Test Stand sequences are actually XML file -- source code, which call for a much more relaxed code versioning or none at all as making sure the code works as part of the debugging process and cannot be handled properly by 'versioning'.
I think you might not be using automatic conflict resolution the way it is intended.
Are you using type palette files? If not, I highly recommend you do so. If you put the highest version of your types in a type palette file, use the default automatic conflict resolution settings, and distribute or deploy the type palette file to everywhere where the type is being used, you do not have to resave all of your sequence files everytime the type changes. Sequence files with older versions of the type will be automatically updated when they are loaded on machines that have the latest version in a type palette. This is what automatic conflict resolution does, it automatically/silently updates the types in the sequence files when they are loaded. No need to resave everything before hand. If you have trouble getting this working, let me know exactly what you are doing and what problems you are having and I will hopefully be able to suggest an alternative way of managing types that will not have those problems.
Hope this helps,
-Doug

Changing Station Options with a Sequence File

Hi,
Is there a way to modify the "Debug options" located under "Preferences" tab in Station Options in TestStand by running a sequence file? I would like to disable the default "Report Object Leaks" option located under "Debug options"
Also, can I disable Report Generation located under "Report Options" by running a sequence file?
Response is appreciated. Thanks.

Hi,
Dont forget that the Report Options are set before the main process model loops.
If you wanted to disable the report once you are into the Client sequence file, you might beable to affect the Local copy of the ReportOptions by using RunState.Caller.RunState.Locals.ReportOptions
Regards
Ray Farmer
Regards
Ray Farmer

Stop Excel changing a file when opened

Is there a way to stop Excel (and possibly Word too) changing the Excel file when you open it, and then close it without saving.
Excel updates the last opened date, and does not change the update date. Like this: http://spreadsheetpage.com/index.php/oddity/who_last_opened_that_file/
I do not want this to occur as I have a sync'ing system which creates unessisary noise, and it also causes sync issues and merge conflicts for changes that are not changes.
Can you turn it off?

Hello ,
Thank you for your question.
I am trying to involve someone familiar with this topic to further look at this issue.
Thanks
George Zhao
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click "[email protected]"

Questions about "Diff Sequence File With..." function

Hello,
I've started working on a project where I'm maintaining a piece of older code written by a since-departed employee of my company. It's a TestStand 3.0 sequence file calling on Labview 7.0 code. The thing is, there were two of these installations done at different times and, somewhere in the woods between stations 1 & 2, the code base diverged. Part of it was due to not being able to get exact duplicate hardware for the PXI chassis and part was, apparently, due to the fact the client used the 2 machines to test different UUT models.
So, I'm looking at copies of the installed code base on the two machines using the diff feature in TestStand. (If it makes a difference, I'm doing this viewing in TestStand 3.5 since TS3.0 has mysteriously gone corrupt on me at the moment on my main development computer and, if memory serves, you have to uninstall all the later version of TS to reinstall an older version. An altogether fun process, no doubt, but a little time consuming.)
Anyway, the first thing I notice is that very many of the sequence steps have different Step Properties.Step ID values that look something like this: "ID#:2vMTp0db002mQDXArddRSA". Messing with the diff screen showed an option to "Ignore Unique Step Ids" which got rid of these. Regarding these unique step ID's: When are they generated and do they remain constant on a particular machine? Beyond mere curiosity, I wonder because another diff is in some of the "On Pass Target" or "On Custom Condition True Target" under certain Step Properties and the value under there looks suspiciously like those unique ID's (i.e. ""ID#randomstuff""). Are these all dynamically updated at runtime or will I break something by changing those (say if I copy a sequence from one version overwriting it in the other)?
So, I filtered the unique ID's out. The next large area of difference is that many, but by no means all, Labview VI calls have a difference under Step Properties > Flexible Labview Adapter Properties > ViCall > Connector Pane Checksum > Value. Also, in a few other instances, ViCall > error out > Connector Number is different as well. Does this indicate a different underlying VI?
There are a few other differences, but I can interpret those. My goal is to get one sequence file for both machines so the code will be easier to maintain. I do think that some of the VI's with different Connector Pane Checksums may be different between the two installations since one of the different hardware components required a different driver library. This leads to a third question, what does it take to use identical sequence files when the underlying VI's might differ? Is it just the interface needs to be the same? Like the connector pane has the same geometry and data types for the exposed inputs and outputs?
Thanks for any help,
Mike
Solved!
Go to Solution.

I just got off the phone with NI support, so no worries on the answers.
Short versions:
The unique ID's are regenerated when a sequence is copied.
Teststand doesn't need higher versions uninstalled to reinstall an earlier copy.
Connector Pane Checksum implies a different underlying VI, but having the same connector geometry/inputs/outputs/types should allow you to have a different VI for different installations without different sequence files.
Still waiting to hear back from support on whether the goto pointers get updated properly when a sequence or portion of a sequence is copied.

How to get the Runstate variable of an external sequence called from the Client Sequence through Sequencecall?

Hi,
I need to change the runtime high and lo limit values of all the tests of the client sequence file before running it. My sequence file is having a SequenceCall which calls an external sequence. Can anyone tell me how to change/access the High and lo limit values of the external sequence test steps?
Thanks,
Jeyan

Doug,
I used the property loader method but I could not load the limits of any sub sequence call calling an external sequence file.
I took the FlowRate_test.seq example from the NI Example folder "C:\Documents and Settings\All Users\Documents\National Instruments\TestStand 4.2.1\Examples\PropertyLoader\LoadingLimits\LimitsFromExcelFile\UsingCVI". I created a sequence called PumpTest.seq in the same folder path. I then moved the Pump Test step from the FlowRate_test.seq to the PumpTest.seq. Now created a sequence call in the FlowRate_test.seq and called the PumpTest.Seq as the module path. When I execute the FlowRate_test.seq , I get the error as shown below:
Attached is the Flowrate_Test.seq and the PumpTest.seq which should be there in the folder path "C:\Documents and Settings\All Users\Documents\National Instruments\TestStand 4.2.1\Examples\PropertyLoader\LoadingLimits\LimitsFromExcelFile\UsingCVI".
Let me know whether I am doing something wrong in this method.
My idea is to alter the runstate variable High and Low of Pump Test in the PumpTest.seq and then run the Flowrate_Test.seq.
Attachments:
PumpTest.seq ‏6 KB
FlowRate_test.seq ‏11 KB

How to load the sequence file from the process model?

Does anyone have an example process model that loads a sequence file? The out-of-the-box process models assume the sequence file is already loaded. I want the process model to identify the UUT type and load the appropriate sequence file based on that.

Mark,
A better solution to your question can be accomplised if you have TestStand 2.0.
Within the entry point of a process modle you can set the client sequence using Execution.ClientFile(). This is a new method of TestStand 2.0. It was specifically designed so that you could dynamically set the client sequence within the process model.
Currently the entry points in the default process models (i.e. Test UUTs and Single Pass) are configured to Show Entry Point When Client File Window is Active. This means that you must open and have active a client sequence file before you can execute one of the entry point. You probably do not want this implementation if you are going to set the client file during the entry point execution. To change this you will need to go the sequence properties of your entry point (while the sequence is open select Edit>>Sequence Properties), switch to the Model tab of the entry point's property dialog box, and enable Show Entry Point For All Windows. The entry point will then appear whether or not you have an open sequence file active.
You will need to add at least 3 steps to your entry point sequence that all use the ActiveX Automation Adapter. Remember that MUST disable Record Results for any step you add to the process model. The 3 steps will perform the following tasks:
1) Obtains a sequence file reference of the file that you want to be the client sequence file. You will need to use the Engine.GetSequenceFileEx method. You will need a local variable (ActiveX data type) in which to store the sequence file reference.
2) Set the client sequence file using the Execution.ClientFile property.
3) Close the reference to the client sequence file in the Cleanup step group of your entry point sequence using Engine.ReleaseSequenceFileEx
I am attaching a SequenceModel.seq file (the default process model in TestStand 2.0) in which we have modified the TestUUTs entry point as described above.
Note that you'll be prompted to enter the path to your client sequence file. This is a message popup that you can delete and it was added for your review only.
Good luck in your project,
Azucena Perez
National Instruments
Attachments:
sequentialmodel.seq ‏164 KB

How to add process model results to the sequence file results?

After my sequence file runs, I would like to add some additional results using the process model. I need to log my equipment list which is obtained by the process model. Alternatively, I could add a sub-sequence to the end of each of my sequence files for doing this, but that would create maintenance problems if I ever needed to change the way equipment is logged. Does anyone know a way to (1) append process model results to the sequence file results or (2) force each client sequence file to call a sub-sequence before returning to the process model.

Mark -
The report and database process model routines expect a single subsequence step result that invoked MainSequence. This result contains the results from the sequence call.
In TestStand after the process model root sequence call to MainSequence is performed, the property Locals.ResultList[0] is the MainSequence result. The subproperty Locals.ResultList[0].TS.SequenceCall.ResultList contains the results from the steps in MainSequence.
One option is to create a subsequence call in the process model that logs the equipment info in the results for its steps. The call to the subsequence should not be checked to record results.
This subsequence would have a parameter called ResultList. The Result type does not exist in the Insert menu, so you can only create the parameter by copying the empty Locals.ResultList and pasting it in the parameters. Then change its type from By Value to By Reference.
In the setup of the subsequence, add the following steps which do not record results. These steps rename the Locals.ResultList parameter to ResultListOrig, and then create a new Locals.ResultList alias property that really references Parameters.ResultList. This way any additions to the Locals.ResultList really append to the Parameter.ResultList.
Setup
Step: "Rename Locals.ResultList"
StepType, Adapter: Action, Active-X
Description:
Action, Set PropertyObject.Name = "ResultListORIG"
Record Results: False
Step: "Create Alias in Locals"
StepType, Adapter: Actioin, Active-X
Description:
Action, Call PropertyObject.SetPropertyObject ("ResultList",
0x201 ' Not Owning and Create, Parameters.ResultList)
Record Results: False
In the Main steps, you add your equipment info steps which record results.
In the Cleanup steps you undo the steps performed in Setup.
Cleanup
Step: "Delete Alias in Locals"
StepType, Adapter: Action, Active-X
Description:
Action, Call PropertyObject.DeleteSubProperty ("ResultList",
0x400 ' Refer to Alias)
Record Results: False
Step: "Rename Locals.ResultListORIG"
StepType, Adapter: Action, Active-X
Description:
Action, Set PropertyObject.Name = "ResultList"
Record Results: False
I have attached a TS 2.0 version of SequentialModel.Seq that has a AppendResults subsequence in it and this is invoked after MainSequence in Single Pass entry point.
Hope this helps...
Scott Richardson (NI)
Scott Richardson
National Instruments
Attachments:
SequentialModel.Seq ‏174 KB

Change client sequence file when Ctrl F5

Similar Messages

Maybe you are looking for