Teststand OI

Hello,
I've built a VI which captures events from a third-party software.
When one of these event fire I have a case structure which needs to run a specific TestStand sequence with several input parameters and to receive the output message from this sequence.
The simple OI found in TestStand example library is an "overkill" for my purpose.
I have built the attached VI which loads TS engine->login->load sequence file->load sequence.
The problem is that this VI doesn't execute the loaded sequence.
I have also tried to use the testexec.exe to load and run the sequence as follows:
TestExec.exe -run MainSequence C:\Users\gigasv01\Desktop\TestStandPlugin\QD980\QD980_rx.seq -SilentMode -exportlog:C:\Users\gigasv01\Desktop\TestStandPlugin\QD980\RunRes.mht -quit
Using this command line interface the sequence is executed properly but I still get the user login message and the execution doesn't quit when completed.
I prefer to use the first method I mentioned (VI for calling the TS sequence), but the command line will answer my needs if the login message can be suppressed and the execution will quit+capturing the sequence result.
Thank you,
Attachments:
RunTSsequence.vi ‏33 KB

Hello,
Thank you for the reply.
I have solved the issue by performing the following steps:
1. Add windows user to the TestStand user manager and set automatic login with this user
2. User a built in exe.vi to run the command line: fullpath\TestExec.exe /run SequenceName SequenceFullPath\SequenceFile.seq /quit
3. Add a text file output step in the sequence which exports the results of every run to this text file which then is parsed for results.
I do think that what you propose is a more elegant solution but I have little experience with creating TestStand treads to listen for the events in the VI.
Please send me the example you mentioned with this TestStand-LabVIEW events exchange mechanism.
Thank you,

Similar Messages

How can I create a Teststand (1.0.3 or 2.0) distribution without having all of the VIs (6.0.2 or 6.1) in the same directory?

How would I create a Teststand distribution of LabVIEW VIs and maintain the test VI directory structure that I want?
I know that I have to use the application builder to build the custom operator interface, configure it as an ActiveX server, and launch the Teststand engine installation.
The only problem that I have is using the VI packager which puts all of the test code and sequences in a single directory.
This gets quite messy. There are just over 1000 files in the neatly orgainzed directory structure that I have now. (this includes support files, dll's and such)
I have read brief appnotes on configuring the ini file(s) to use
the vi search path that I want, but have not been able to get this to work. Maybe I'm not updating the correct ini? or have to include each subdirectory?
I have currently upgraded from LabVIEW 6.0.2 to 6.1
I am currently using Teststand 1.0.3
I have not upgraded to Teststand 2.0 yet because I have not decided if I want to build at this revision or go through the extra work to mass compile Teststand at LabVIEW 6.1, install the LabVIEW 6i VI Packager Fix, and update the new Teststand LV operator interface with my changes.
At present, I'm not getting the results I want and am quickly running out of time. I have to deliver the project by the 14th of July 2002.
Sorry for the long question and thanks for you help.

Hi,
I dont think the problem is really related to using the VI Packager but more to how the OI interface applications relates to labVIEW File constants.
If you are using the LabVIEW as the ActiveX Server then there should be no problems. But if you are using the Runtime LabVIEW server such as 'TestStandLVRTS' then the file constant would return different paths.
eg for the Default Path you would get 'C:\TestStand\Components\User\RuntimeServers\LabVIEW' instead of 'c:\Program Files\National Instruments\LabVIEW'.
Attacted is an example to show how to change these paths when using your runtime server. Unzip this into your teststand examples folder
Put the INI file in the location of the \user\runtimeservers\labview folder.
Change the labview adapter t
o use TestStandLVRTS.exe. You can run the example sequence from either the OI or seqeditor.
I hope this helps
Regards
Ray Farmer
Regards
Ray Farmer
Attachments:
UsingLVOI.zip ‏20 KB

Can I Suppress Conflicting Names Messages in the TestStand Deployment Log?

I have a deployment that is being built via a command line calling the deployment utility. It is all being done with a script. I then use the deployment log for information to e-mail to myself and others about the build. I am getting conflicting name messages for VIs in the Labview Reports library that is shipped from NI. There are a lot of message about VIs being renamed because of this. Is there a way of suppressing these messages so real information can be observed and not missed because of all this spam? I don't want to have a real problem over looked because of these messages being generated about items that are not in my control. Thanks in advance for any help.
Troy

What version of TestStand, and LabVIEW are you using? Have you seen How to Successfully Deploy a TestStand System with LabVIEW 8.6 and Report Generation Toolkit ?
Richard S -- National Instruments --Applications Engineer -- Data Acquisition with TestStand

Using Host and FPGA.vi in Teststand

Does anyone know how to use the Host and FPGA vi's in Teststand?? A National App Engr told me I have to call the Project that the vi is in to get all the functionality of the FPGA. How do you call a Project in Teststand??
Thanks

Ensure you are using the TestStand version 2010 or above. Create a new instance of a sequence and add a LabVIEW action step to it. Go to Module panel and browse for a LabVIEW project as displayed below.

How to externally trigger the execution of TestStand with a start and abort button through a digital interface?

Hello,
I'm Currently evaluating TestStand as an alternative for an in-house developed Test Sequencer.
To start our own Test Sequencer we use a small box, connected to a DIO board. The box has a start button and an abort button. The box also has a pass, a fail and a running led.
The interface with this box is made via some digital lines of a PCI-DIO-96.
In our own Test Sequencer we have groups named Init, Run, Abort, Exit.
The Init group is executed at startup (only once). It is used to initialize all the HW and SW. -> I guess this is the Pre UUT Loop callback in TestStand.
The Exit group is only executed once at the end of the day when the application is terminated. It is used to free all the used hardware and cleanup all the resources. This probably is the Post UUT Loop Callback in TS.
When a product needs to be tested, the operator presses the "start" button which triggers our own Test Sequencer and the run and abort group are being executed (first the run group, afterwards the abort group).
When the product is being tested the "running led" of the little box lights up to indicate to the operator that the application is running. (only when the run and abort group are running)
The Run group has all the functional tests in it. (MainSequence)
The abort group is used to put everything back in it's original state after the test on this single product is done. (Post UUT)
When executing the tests and something goes wrong (operator gets stuck in a clamper, ...) the operator can still press the abort button and then the execution immediately jumps from the currently executing step in the run group to the first step of the abort group. So, when something goes wrong, immediately the abort group is called.
At the end of the run and abort group, if no errors occured, the "pass led" lights up. If one or more steps went wrong the "fail" led lights up.
This setup can also be used to test multiple product in parallel. At that time all the different parallel testers have such a small box which contains a "start" and "abort" button and a pass, fail and running led. (it is possible that they are all connected to the same PCI-DIO-96 board. )
My question:
Is it possible to do something similar like this in Teststand? If yes, is there an example available that shows me how to do this in TestStand? (externally trigger the execution of TestStand)
Typically, in the Init group (Pre UUT Loop) the digital interface box gets initialised.
In the Close group (Post UUT Loop) the digital interface box is taken out of scope.
Note: The PCI-DIO-96 board to which the digital interface box is connected will also be used in the rest of the developed application (MainSequence, ...)
What's really important for me is that I can create a process model that all the application developers in our organisation can use. I really don't want any of the application developers (limited software experience) to mess around in all the features of TestStand.
For them it's important that they just add the function DigitalInterfaceBoxInit () in the Pre UUT Loop Callback and the DigitalInterfaceBoxClose () in the Post UUT Loop Callback, and then everything works!
It is important that the appliation developers do not have to create any global variables, other functions, synchronisations, parallel sequences, ... in TestStand. All this needs to be done with a simple call to the DigitalInterfaceBoxInit function.
Thanks in advance for all the help!
Best Regards,
Dennis Vanotterdijk
[email protected]

Dennis-
Your application sounds very well suited to TestStand's abilities. I am also quite impressed with your knowledge of how TestStand's architecture is arranged when you are still just considering whether or not to use it.
I think that TestStand would work really well for you in this application. Like you mentioned it will provide you with a form of standardization for your application developers to work from. It also provides the flexibility for you to add your custom routines in many different places. TestStand also makes parallel and batch testing much easier in TS 2.0 so that you could develop one test for your product and execute different instances of it in parallel to test multiple products at once.
As for your specific question about how to c
ontrol TestStand using a DIO board. I think this is very feasible and should not be too difficult. Since TestStand provides you the ability to create a custom operator interface your operator interface could monitor the status of your DIO board and launch/abort executions based on the read values. Usually the executions are launched/aborted when a button on the GUI is pressed however, I do not see any thing different about basing the action on a DI signal vs a mouse click. I am sure your application is more involved than this high level description but from the sounds of it I think it is very possible to do with TestStand.
Based on my experience of building test systems with TestStand and your description of the application, I would feel very confident in using TestStand to achieve all the goals you mentioned. If you have further detailed questions on how one of your features might be implemented, feel free to contact one of our Application Engineers or email us at www.ni.com/ask
and we would be glad to help you.
Best regards,
Richard McDonell
National Instruments

Best way to get UUT result to Custom TestStand UI

Hello,
I am trying to get the results of my UUT to my custom UI. I am already using the EndExecution Callback to tell my UI when the UUT is finished executing. I was hoping ot use that same callback VI to tell my UI the result of the execution.
The EndExecution callback includes a reference to the execution. I figured I could read the "ResultStatus" Property, which seems to report "Passed" or "Failed" correctly, but if I terminate execution, it is still returning "Passed", when I would expect it to return "Terminated".
Does anybody have any thoughts on what I am doing wrong or what might be a better way to do this? I thought of just using a UI Message, but then that requires me to modify the client sequence and post the UI message with the results. I'd rather have this work for all client sequences.
Solved!
Go to Solution.

I think you are looking for handling the UIMsg_ModelState_TestingComplete user interface message.
Refer to the help:
UIMsg_ModelState_TestingComplete–(Value: 34) TestStand process models post this message to the user interface after the MainSequence in the client sequence file returns control to the model. If the execution is not a batch controller or a parallel controller, the stringDataParam parameter specifies the UUT result status. If the execution is a batch controller or a parallel controller, the value of the stringDataParam parameter is Done. The numericDataParam parameter specifies the test-socket index. The activeXDataParam parameter contains a reference to the sequence context for the process model sequence file that posts the message.
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

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

I am trying to have some LabVIEW code called in a New thread exit when the testStand sequence terminates

I have a Sequence that launches a sequence in a New Thread that happens to launch some LabVIEW code. The problem is when the LabVIEW code finishes, it will not close even when the TestStand sequence terminates. Is there a way to tell this LabVIEW code to Exit, I've tried the Quit LabVIEW function, but that causes a C++ RunTime Error. The LabVIEW code does end though, and it is set in the VI properties to:
Checked - Show Front Panel When Called
Checked - Close Afterwardds if originally closed
The sequence call that the LabVIEW code is launched from has the following options:
- New Thread
Unchecked - Automatically wait for the thread to complete at the end of the current sequence
Unchecked - Initially Suspended
Unchecked - Use single threaded apartment
Any clues on this would be appreciated.

Hi ADL,
Everything should close correctly if you check the checkbox "Automatically wait for the thread to complete at the end of the current sequence" in the thread settings.
With it unchecked, I am seeing the behavior you are.
Gavin Fox
Systems Software
National Instruments

TestStand won't load vi in runtime

I'm runing LabVIEW 2011 version 11.0f2. TestStand 2010 SP1.
We tried deploying a packed library to a test system but the run-time will not load the VI. Depending on the VI selected, we get a variety of different errors with the ! in teststand saying it can't load the module. The beginning always says that the module can't be loaded with the Runtime Engine version 11.0. Then usually stuff about the file can't be found and other crazy stuff. Hard to capture them all because I don't see a way to copy and paste the info because you have to hover over the ! to get the error info. Sure would be nice to get at that info so it could be copied to the clipboard!!!
I've been replicating the issue on my development PC with the adapter set to runtime engine instead of develoment system. It will load fine in development. It will load find in runtime if I browse to the file directly (IE. not in the packed library). But once I build the packed library, we get the error.
I should mention we are using Classes inside our packed libraries. We've been doing this for quite some time without issue. I can point to any number of other packed libraries we've build with the runtime without issue.
I then decided to try to replicate with a new library. It is a shell of a library and class. I've attached it here. I get the same behavior. will load if development and if direct to VI in runtime but not in the packed library VI.
I was just fiddling with TestStand and found that if I select Advanced Settings and check Always Run VI in LabVIEW Run-Time Engine, it will load. But if I uncheck that, it will not. WTF?
Can anyone see if I have something hosed or doing something wrong. If we're set to use runtime adapter, we shouldn't have to set the step to use the runtime??? And since we've done this many times before without issue, I have no idea what the problem is. I haven't changed anything lately and can build older packed libraries we've had setup and have them work. But for some reason this new very empty and basic one won't... at a loss.
Attachments:
Library.zip ‏30 KB

I did the mass compile. same issue. Although since I started from a brand new project from the 2011 environment with almost nothing in it, I don't see how that would've done much anyway. But all efforts worth a shot. The zip file I attached here was made with the following steps. When I get to the end of this procedure, I get the red exclamation point... This should not happen... I have since uninstalled all NI software (even hunted down all residual components I could find that aren't automatically uninstalled or deleted) and still get the same problem. I tried going to 2011 SP1, same problem.
Close labview and teststand
open labview
create new project
right click and create new library (leave all names as whatever labview defaults to)
right click library and create new class
Open class control and add a string (don't change name)
close class control - Save to a temporary folder somewhere
Save all - put all files into the same temporary folder with default names of labview
right click class and create new VI
put the class as an input and an output in that VI
wire the class input to the class output
save the VI into the same temporary folder as "Test.vi"
create new packed library build
change location to the same temporary folder, leave all other names the same
source file to the library you just created
enable debugging
Build the packed library
save all and exit labview completely
Start teststand
Configure - Adapters
with labview selected - press configure button
Select radio button for LabVIEW Run-time engine
OK
DONE
Add labview action step
select the VI by browsing to the temporary folder and selecting the packed library then the Test.vi inside that packed library
Select use an absolute path
Does the VI prototype load? or does it have flashing red exclamation point???
Attachments:
Test.zip ‏30 KB

VI front panel does not pop up in teststand

HI,
I am new to teststand and would like to seek helps on my application.
I have a sequence file consists of several steps. in the SETUP, I have a step to acquire input from the user on which test to run. Having said that, when i run the sequence, i do not see the checkbox test pop up automatically. How do i configure it to pop up the VI automatically.
Also, How do we control the sequence if the user select 3 test cases? using (if) flow control in teststand?
Please advise.
Regards,
Alfred Tan
Attachments:
checkbox test.vi ‏7 KB
NH3 teststand.seq ‏19 KB
Turn on Port 1.vi ‏38 KB

Hi HansWi,
Sorry for the late reply.
Thanks for the VI pop up solution. Now the VI can pop up when i call the VI.
I am using "case" in teststand, I still have error message when i run the sequence. Also, The sequece does not follow the checkbox value that checked by the user.
Please advise.
Attachments:
teststand case.zip ‏196 KB

What is the best way to open close and pass instrument handles from labview in teststand parallel model?

I have a number of test systems that use a parallel model with labview. We have a good number of instruments(PXI).
What is the prefered method for open,closing and passing instrument handles in teststand using labview?
Solved!
Go to Solution.

Hi,
No, Below is a bit from the Session Manager Help
Currently, Session Manager supports the following instrument session types:
IVI Sessions—Use an IVI session to obtain the C-based instance handle for an IVI logical or virtual instrument name. NI Session Manager does not support IVI-COM drivers at this time. When IVI-COM drivers are available, you can use an IVI session to obtain an ActiveX interface reference to an IVI-COM driver.
VXIplug&play Sessions—Use a VXIplug&play session to obtain a C-based instance handle for a VXIplug&play logical or virtual instrument name. Configure VXIplug&play names in the <VXIplug&play directory>\<Platform directory>\NISessionMgr.ini file.
VISA Sessions—Use a VISA instrument session to obtain a C-based viSession handle to a VISA resource or logical name. Configure VISA logical names in the <VXIplug&play directory>\<Platform directory>\NISessionMgr.ini file.
Custom Sessions—Use a custom session to create a data container object that shares ActiveX objects you create or other data between software components you write. Use the Attach and Get methods to attach data to and retrieve data from a session. A custom session does not initialize, close, or own an instrument handle. The data you share with a custom session does not have to be instrumentation related. You can create a custom session with any name you request.
Regards
Ray Farmer
Regards
Ray Farmer

TestStand Simple OI does not close properly

Hi there.
We have build a test system that is running TestStand 4.2 and the code modules are created with LabVIEW 9.0. The SW is running on a PC with Windows XP.
We are currently using TestStand Simple Operator Interface (LabVIEW version) to run the tests, and it is with the Operator Interface that we are having a problem.
If we use the TestExec.exe file that came with the TestStand installation everything works fine. But we need to make some modifications to OI and if we open the project file and recompile the OI, then the OI will not close properly. It seems to shutdown the testengine and stop execution of the VI, but the window does not disappear until we move the mouse.
When I open the project file LabVIEW informs me that the project was last saved in version 7.1.1 and we are now running 9.0.
Can anyone tell me what is holding the window on the screen until there is activity on the mouse?
Solved!
Go to Solution.

I was looking through TestStand 4.2 known issues, and I found this:
ID# 148697
LabVIEW User Interface might hang when using LabVIEW events
A LabVIEW User Interface that registers ActiveX callbacks and uses an event structure might hang when the user interacts with a LabVIEW control or indicator. The hang is rare, but when it occurs, TestStand User Interface (UI) Controls remain responsive, but all LabVIEW User Interface elements appear frozen.
Workaround: Activate another application and reactive the LabVIEW User Interface.
Not exactly the same as I am experiencing but sounds similar - Does anyone know more about this issue?

How can I Generate two different reports from single execution of Test cases in NI teststand

Hi,
My requirement is to generate two different reports from NI teststand. One for the Logging of error descriptions and the other report is by default generated by the Teststand. How can i generate a txt file that contains error descriptions other than that mentioned in the default report?
Solved!
Go to Solution.

Do you need to do that just for these two sequences but not for other sequences? I don't see a problem to use SequenceFilePostStepRuntimeError. Create this callback in both sequence files and configure them to log into the same file. SequenceFilePostStepRuntimeError callback is called after each step of the sequence file if it has runtime error. You can access the calling step error information via RunState.Caller.Step.Result.Error property. Take a look to attached example.
The "other way" is useful if you need to log errors not for every step of the sequence file, but for some of them. This is more complex, because you need to create a custom step types for these steps. For the custom step you can create substeps (post-step in your case) which will be executed every time after step of this type executed. Then, this is you job to determine if error happened in the step, acces to step's error information is via Step.Result.Error property.
Also, be aware that step's post-expression is not executed in case of error in the step.
Sergey Kolbunov
CLA, CTD
Attachments:
SequenceFilePostStepRuntimeError_Demo.seq ‏7 KB

Reporting mechanism on HTML report file, using TestStand 2012 SP1

Hi,
I am using TestStand 2012 SP1, where the reporting mechanism is configured to be in HTML format.
I am not getting the full report of the sequence file which is executed, however I get a part of it printed on the HTML file.
The following are the configured "Report options",
===========
Contents Tab:
===========
Report Format : HTML Document
Default Numeric Format : %$.13f
Include Step Result: Checked
              Result Filtering Expression : Result.Status=="Failed"
              Include Test Limits : Checked
              Include Measurements : Checked
              Include Arrays : Insert Table
              Filter : Include All
Include Execution Times : Checked
On-The-Fly Rporting and Only Display Latest Results : Checked
Select a Report Generator for producing the Report Body : DLL
===========
Report File Pathname Tab:
===========
Generate Report File Path : Checked
       File Name/Directory Options : Specify Report File Path by Expression
       Report File Path (Sequential Model) :
                        StationGlobals.TopLevelReportPath
                        +RunState.ProcessModelClient.AsPropertyObjectFile.DisplayName+"Report_[<FileDate>]<Unique>.<FileExtension>"
Please let me know a solution to this problem.
Thanks,
Dharani

Jason,
Thankyou for replying.
Yes, I need only the steps which had failed to print on the report file.
The problem what I am facing is, if there are 10 failed steps, the report is not printed for all.
Also the order of printing is not correct for the first step and the last step which is printed on the report file.
I had used "Post Expression" for printing data for all the failed steps. Normally these post expressions should be printed beneath the step in the report file.
However,
1) For the first step which is printed on the html file, the post expression gets printed just above the step and also it gets printed beneath the step.
2) For the last step which is printed on the html file, the post expression is not printed beneath the step.
Please let me know if i need to provide some more information.
Thanks,
Dharani

How to call a CString array from TestStand

I have a C++ DLL that uses a CString array, CString myString[ ], that I need to pass back to TestStand 4.0 for inclusion in my results database.
In the TestStand module definition the parameter argument Description comes up as a CStriing pointer (CString*) instead of a CStringArray.
When I put my array of strings into the Value Expression I get an error: Expected String, found Array of Strings.
I have no trouble passing just a string pointer but that's not working either.
Can someone help?
Thanks,
Steve S

Hi Steve,
I don't think that you can pass a CString Array from C++ DLL to TestStand 4.0 directly.
But you can do it another way: concatenate all Strings by a delimit in your CString Array to build a new String, then pass it to TestStand. In TestStand you can separate those Strings by the delimit, and rebuild a String Array.
For example:
// If this is your CString Array.
CString myString[] = {"AAA", "BBB", "CCC"};
// Build a new String in your C++, and pass it to TestStand.
char *myNewString = "AAA~BBB~CCC";
// Separate myNewString and build an Array in TestStand...
Hope that can help you!
Message Edited by My NI on 11-29-2007 11:34 AM
Regards
MY

How can I query TestStand Database quickly?

Hello everybody
I have a performance issue with default TestStand database what puzzled me for long time.
In default database TestStand organize the different test item to different table, if I want to query a test record according to a special Serial Number, the query will look into UUT_RESULT at first to find a GUID then forward to the other table to find a series of GUID bound with this SN which will be used to go into different tables like a numeric values table or pass_fail table to find out the result of each test step.
Half a year ago, we have a small tool embeded with customized TestStand Interface to access this SQL Server 2005 Express database to fetch a SN and all its test results details for faulty analysis. Recently I found it will cost me more than 2 minutes to fetch all related test results of one SN, I tried to write some query in SQL SERVER management studio to get the same thing, the case is still there. And also I check the tables, all tables are already indexed, so I'm quite confused.
Did someone meet similar thing with me? Can you provide some suggestion on this?
*The best Chinese farmer*

What exactly is the query that you are using? Depending on how many records you are attempting to retrieve, two minutes may not be unreasonable. If the database is on a network share, if others are attempting to do similar, large queries, can also affect performance. Making your query into a stored procedure could save some time.

Teststand OI

Similar Messages

Maybe you are looking for