DataBaseOperation in the TestStand

Hello,
I try to use Database Functions from the TestStand 2010 f1(4.5.0.330). My DataBase is MS Access 2010.
It goes well to open data base by "Open Database" action and to OpenSQL Statement as far as it is used without parameteres. I see that the correct number of records was read. For my test sequence I need it of cours with parameters and put Database Operation after building SQL Statement. Although the Database view shows me proper tables and LabView VI build with DataBase elements is able to get data which I search, Database Operation in Test Stand doesn't work.
Looking for possible error sources I studied TestStand Help for Database Operation and found out that it doesn't correspond to the appearence of the step. The picture of the step settings is attached and an extract of the corresponding help page is also attached as a Word file. Maybe somebody knows, where I can get the proper Help?
Thank you in advance
Attachments:
DataBaseOperation.jpg ‏100 KB
DataBaseOperationHelp.docx ‏17 KB

Yes, I did and the picture and Help file, which I attached is just that which opens by pressing of a corresponding button. I suppose that the Help a little bit old. Maybe NI will update it one day.
I found out what I shall set in this window by simply trying and executin, the sequence works now!
Thank you for your answer

Similar Messages

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

How can I set defaults in the TestStand's step settings Labview Advanced Settings tab to run a VI on a remote PC?

I am accessing a VI many times which is run on a remote PC.
When I click Step Settings, click on the Module tab, then click on the Labview Advanced Settings, there is are options for running a VI on a remote PC.
An annoyance is having to enter the remote host, remote VI path, port number and timeout settings every time I created a step to call the VI in the tests. These are a constant, or at least the rule by far rather than the exception. The TestStand step settings default is the VI does not run on a remote PC (unticked) and there are of course no IP addresses etc as defaults. So if I make a minor change to the tests such as the remote VI location, I have to manually change it is every occurrence of the VI being called. This is very time consuming and is prone to human error.
Is there a way I can preset these settings so that every time I call a Labview module, these defaults are invoked without me having to set them every time?
I guess a workaround is to have the VI run in a subsequence, so that the settings are made just once, but I would prefer not to have to do that.
regards to the NI community,
Dave
Solved!
Go to Solution.

Hi,
What you can do if you are using TS4.x is create your first step, then add it to the Template List. Then use the step from the template list when you require similar steps. See User Manual Chapter 3-6.
Regards
Ray Farmer
Regards
Ray Farmer

Silent Install of the TestStand Engine 2.0.1

I am trying to do an unattended install of the TestStand Engine 2.0.1. I am using the "-noprompt" switch which makes the install silent except at the very end I get a dialogue box that say "You must reboot this computer...". I am also using InstallShield Professional 6.0 from which I launch then NI TestStand 2.0.2 engine.
Does anyone have a solution to do a completely silent install?
Thanks...Eric

Eric,
In general, we don't support creating silent installers because InstallShield isn't our development product. However, I have some information that may be of help. A normal (non-silent) installation receives the necessary input from the user in the form of responses to dialog boxes. As you know, a silent installation does not prompt the user for input. A silent installation must get its user input from a different source. That source is the InstallShield Silent Response File (.iss file). A response file contains information similar to that which an end user would enter as responses to dialog boxes when running a normal setup. InstallShield Silent reads the necessary input from the response file at run time.
The format of response files resembles that of
an .ini file, but response files have .iss extensions. A response file is a plain text file consisting of sections containing data entries. There are two ways in which you can create an InstallShield Silent Response File: you can run the setup and have InstallShield record and create the response file for you, or you can write the response file from scratch. It should be possible for you to create a response file that would contain a newline to confirm the reboot prompt. Your InstallShield documentation should provide more information regarding how you should create the response file.
If you have any more questions, let us know.
Regards,
Shannon R.
Applications Engineer
National Instruments

How to send data to labview code at run time while using with (or executing the sequence)the teststand

Hello
I am new to the Teststand.
I am using labview8.0 with teststand 3.1
I have developed some labview codemodules as vi's without using the teststand utility library pallete
Now i have to run them in teststand.
While executing them(as a sequence) in teststand,i need to enter the data to the labview code at run time.For this labview front panel should appear as GUI or popup (while executing).Is it possible to do this without using teststand pallete.
or i need to change the code with teststand pallete(i think it is difficult now to change the code)
Plz provide a solution to this problem
Also one more,how and where to use the 'pass by reference' option
Thanks and Regards
Mudigondla

Hi,
see your other post http://forums.ni.com/ni/board/message?board.id=330&message.id=13914
Also, you can, specify to display the front panel of your VI when you specify your VI in your sequence file.
There are examples, for dialog panel using LabVIEW, in the examples folder of TestStand and on the NI Web Site.
Regards
Ray Farmer
Regards
Ray Farmer

How can I set the TestStand Engine tracing options to be on or off through automatically within my sequence file?

Hello,
I am looking for a way, where I do not have to set the Station Options manually. I want to make sure that whenever someone is running my sequence, the sequence should make sure that the "Tracing Enabled" options gets disabled somehow. I know the tracing option is actually a setting of the TestStand engine, but I want to implement it within my sequence.
Please let me know if this is doable. If yes, what will be the best approach?
Thanks and Regards,
Niraj
Solved!
Go to Solution.

Depends on why you want to disable tracing. One of these might work for you:
1) Lock the file as not viewable.
2) Set RunState.Tracing to false as the first step in your sequence (still get the first trace message for the sequence though)
3) On sequence calls to the sequence set the sequence call trace setting to disabled. (not enforced though).
Hope this helps,
-Doug

How to eliminate an instance of "entering a sequence call" from the teststand report

I am using TestStand 4.2 and I am using a long sequence with several sub-sequences. In these subsequences I am getting test results that I would like to place in the TestStand report. Currently, in order to do this I have to check the "Record Result" option in the "Run Options" of the sequence call properties which displays an "Entering sequence call" mark on the report. Is there any way that I can get rid of this marker and still record information from the sub sequence?
Solved!
Go to Solution.

Hello,
You should have a look a these documents:
http://digital.ni.com/manuals.nsf/websearch/2B14FB1CD4FF25CA862577AE00554FC7
http://zone.ni.com/devzone/cda/tut/p/id/7958
Regards,
Rodéric L
Certified LabVIEW Architect

Can any one tell me how to include the company logo and some poictures into the Teststand report

1. Can any one tell me how to include the company logo and some pictures into the Teststand report?
2. How to include the waveforms into the report?

http://zone.ni.com/devzone/cda/epd/p/id/3619
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

"The TestStand service did not start up promptly"

I have a LabView Operator Interface startup problem with TS 4.1. If
the OI is started immediately after system boot the operator may get apopup error from TestStand:
"The TestStand service did not start up promptly"
The
TestStand Service has a dependency on RPC so if either does not startup
before the operator launches the OI, he gets the message. If he
dismisses the message there is no further error i.e. the software
continues to work OK.
The real problem is the end user does not like this message and wants it removed.
Any suggestions how I can get rid of this message?
Only ideas I can see at the moment - either to have some kind of
delay timer on startup (this would need to be around 1-2 mins after
boot
on the system in question to stop it happening) or perhaps some LabView
code to poll the status of the TestStand service somehow so that we
wait for service to start before the OI communicates with testStand -
and thus the
popup does not occur.

The service should not normally take any significant amount of time to startup. There are some issues with service startup that we have noticed in some cases, but I don't remember the details. I will try and find out and get back to you. In the meantime, or as a possible solution, you can use the Windows SDK to check the status of the service and to wait until it is running. I'm not sure if the following can be directly translated into LabVIEW dll calls, but it would definitely be possible to create a C/C++ dll with the following code in it and call it from LabVIEW (If you do not have access to a C/C++ compiler and/or would like me to, I can probably build a dll with this code in it for you):
int MakeSureServiceIsRunning(void)
    SERVICE_STATUS serviceStatus;
    SC_HANDLE hService = NULL;
    SC_HANDLE hSCM = NULL;
    // Put variable into a good initial state for return value.
    serviceStatus.dwCurrentState = SERVICE_START_PENDING;
    hSCM = OpenSCManager(NULL, NULL, SC_MANAGER_CONNECT);
    if (hSCM == NULL)
        goto Error;
    hService = OpenService(hSCM, "National Instruments TestStand Service", SERVICE_QUERY_STATUS);
    if (hService == NULL)
        goto Error;
    do
        if(!QueryServiceStatus(hService, &serviceStatus))
            goto Error;
        if(serviceStatus.dwCurrentState != SERVICE_RUNNING)
            Sleep(100); // don't just do busy waiting, give up cpu time to other threads.
    while(serviceStatus.dwCurrentState == SERVICE_START_PENDING);
Error:
    if (hService != NULL)
        CloseServiceHandle(hService);
    if (hSCM != NULL)
        CloseServiceHandle(hSCM);
    if (serviceStatus.dwCurrentState == SERVICE_RUNNING)
        return 1;
    else
        return 0; // An error occurred, or service is in an unexpected state.
Or alternatively, if you want to do the polling inside of LabVIEW you could just do the following in the C/C++ dll:
int GetTestStandServiceStatus(unsigned int *serviceStatusReturnResult)
    SERVICE_STATUS serviceStatus;
    SC_HANDLE hService = NULL;
    SC_HANDLE hSCM = NULL;
    hSCM = OpenSCManager(NULL, NULL, SC_MANAGER_CONNECT);
    if (hSCM == NULL)
        goto Error;
    hService = OpenService(hSCM, "National Instruments TestStand Service", SERVICE_QUERY_STATUS);
    if (hService == NULL)
        goto Error;
    if(!QueryServiceStatus(hService, &serviceStatus))
        goto Error;
    *serviceStatusReturnResult = serviceStatus.dwCurrentState;
    CloseServiceHandle(hService);
    CloseServiceHandle(hSCM);
    return 1; // success
Error:
    if (hService != NULL)
        CloseServiceHandle(hService);
    if (hSCM != NULL)
        CloseServiceHandle(hSCM);
    return 0; // An error occurred. Perhaps TestStand service isn't registered.

How to change the TestStand directroy name?

Hi,
I'm interested to change the TestStand directroy name to 'TestStand' instead of 'TestStand 3.0' or 'TestStand 3.1'.
I'm facing a problem with this name. Here is an explanation:
Right now we have TS3.0 and TS3.1 installed on several computers. We work on projects that share modules (like GPIB). These modules are in a ClearCase system, so each one of us can use them and modify them. These modules call to some TS files like 'tsutil.fp' (which is located on the C drive). As a result of different TS names, the project which formerly called a file in TestStand 3.0 directory is now looking for the same file in TestStand 3.1 directory which it doesn't find...
Can you advice me how to modify the TestStand directory name to 'TestStand'?.
Thanks
Rafi

In TestStand, if you go to the Configure>>Search Directories menu, you can add user defined paths to search directories. You have the option to add/remove/move up and move down the search directories. However these options are valid only for user defined search directories. The paths to directories that come shipped with TestStand cannot be removed or moved up/down. In your case, I would suggest that you create a custom path to the directory where you want to search and move it right to the top of the list using the "move up" button. In this way that particular directory will be searched first.
Thank you
Nandini Subramaniam
Applications Engineer
National Instruments

Output on LabVIEW the TestStand step results

Hi,
I'm building on LabVIEW 8.5 a simple TestStand User Interface.
My sequences return some values but I don't know how to output them on LabVIEW.
I was thinking of a table to store the results.
Any hints on how I'm able to do so?
I apreciate all the help.
Thanks in advance.
Regards,
Daniel Coelho
Daniel Coelho
VISToolkit - http://www.vistoolkit.com - Your Real Virtual Instrument Solution
Controlar - Electronica Industrial e Sistemas, Lda

Use the TesStand ExecutionView Manager available in the TestStand tool pallet of LabVIEW and the Execution View. Then when you call our test code (dll, LabVIEW, CVI or what ever) and the return values are returned to the step.Result container based on the type of step. The ExecutionView Manager will automatically display the return value in the Execution View indicator on front panel, if it is a string, a number or a Boolean or etc.
Look at "C:\Program Files\National Instruments\TestStand 4.1\UserInterfaces\Simple\LabVIEW" as a starting point.
Notice that there is not any code that reads the return value from the test steps and displays it. The TestStand Engine automatically does it for you. Using the ExecutionView Manager and the Execution View, your LabVIEW user interface will not know when a test step is run or what the return values are without setting up events to trap UI messages from the TestStand Engine.
If all you need is to see the return value and results this is the way to go.
Omar

How to access the Requirements property (& subproperties) of steps and sequences with the TestStand API

The concept of associating teststand objects to unit requirements for traceability purposes was added to TS 3.5, and I need to find out how to access the array of strings used to store unit requirements in step objects, sequence objects and sequencefile objects. The teststand help file points out that the requirements list of a sequencefile object is accessible using the PropertyObjectFile interface, and also points out that Requirements is a property of the sequence and step classes. Furthermore it implicitly states that the requirements property has a Links subproperty which is an array of strings, but that is pretty much the extent of the documentation on this new feature so far. There seems to be no expression function available to get to those requirements either.
I know that this feature was added to allow TestStand to interface with RG, and I am planning on using RG, but I would also like to do things with the requirements information within TestStand.
Anyone?

Are you talking about the Requirements Gateway? It is a separate product from NI that will do what you are looking for. I haven't used it so I am not sure of the API chain to make it work. Take a look and see if that is what you were thinking of.
Hope that this helps,
Bob Young
Sorry, I just re-read your original post and see that you are looking to also use the Requirements Gateway, so you obviously know about it. I don't know what the API changes were that made it work so I am not going to be much help.
Sorry about posting before getting the correct information from the original.
Bob Young
Message Edited by Bob Y. on 08-24-2006 04:54 PM
Bob Young - Test Engineer - Lapsed Certified LabVIEW Developer
DISTek Integration, Inc. - NI Alliance Member
mailto:[email protected]

How will I be able to make the TestStand UI objects into XP theme?

Hi, I am using TestStand UI in .net, How will I be able to make the UI objecys of TestStand to adapt the XP theme?
Is there any example code that you can give me? Thanks!
Solved!
Go to Solution.

The shipped TestStand .NET Operator Interface has a manifest file included in the project. This manifest file includes the Micrsoft.Windows.Common-Controls which is needed to identify the XP theme that has been configured on the operating system. In the shipped .NET Operator interface, this .manifest file is being embedded into the executable and formats the TestStand Operator Interface to display the XP theme that has been configured on the operating system. in the shipped TestStand 4.1.1 Operator Interface, the manifest file is embedded into the executable in a Project post-build event.
There are three things that the manifest file is required to have in order to allow the TestStand Operator Interface executable to adapt to the XP theme. They are as follows:
The manifest file must have the same name as the executable. For example, if your executable is named MyExecutable.exe, your manifest file is required to have the name MyExecutable.exe.manifest.
The manifest file must include the Micrsoft.Windows.Common-Controls in order to identify the XP theme that has been configured on the operating system.
The manifest file must reside in the same directory as the executable.
If you are building on an existing Operator interface that ships with TestStand 4.1.1, make sure that the manifest file meets these two requirements. If it does you can test that the theme is properly adapting by selecting Debug»Start Without Debugging.
If this works properly, you can rest assured that when building a release version of the TestStand Operator Interface, it will adapt to the XP theme that has been configured on the operating system.
NOTE: that you can only test this feature if you launch the executable without debugging because this allows the executable to run its own process. If you run the executable with debugging, the Visual Studio environment will host the process and will not allow the manifest file to be embedded into the executable.
-Adri
Message Edited by Adri K. on 03-04-2009 04:15 PM
Adri Kruger
National Instruments
LabVIEW Product Marketing
Attachments:
matching names.jpg ‏27 KB
debug.jpg ‏20 KB
manifest.jpg ‏65 KB

The TestStand Engine cannot be initialized. Path not found.

Hi, up until now i installed and removed TestStand 3.5 3 times in a row, just to always get this message (see subject) when i try to start the Sequence Editor. I even uninstalled all NI-Software i had on this laptop to reinstall the whole package... Nothing worked. Now i wonder, is there anything i am doing wrong ? What can i do to get TestStand running ?
Well, on that message when i hit OK, another message
The sequence editor cannot start up. Unable to create the TestStand Engine.
Hitting OK on that message again just terminates the sequence editor leaving me with a blank screen.
Any ideas whats wrong ?
best regards and thanks in advance,
Ingo
Solved!
Go to Solution.

Ingo -
Sorry for your frustration. Your idea to uninstall and reinstall should typically work. The second message is just a result of the first error, so we need to figure out what path is not found, and it is unclear why this is occurring. I tried to force my copy of TestStand 3.5 to fail in a similiar way by messing around with the installation and I could not find a way to cause the "Path not found" error. I got many other more detailed errors, but I have been unable to duplicate your message.
Some questions:
1) What operating system are you using?
2) Are you installing to the default location under Program Files? Are you using a network path in any way?
3) Do you have write authority to the the installation locations on you system?
4) Are you logged in as an administrator when installing, restarting, and launching the sequence editor.
5) Have you manually messed with any of the registry settings under HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\TestStand\3.5, where something is incorrect?
6) Have you added any User components under the TestStand directory that might somehow load and cause an issue?
If you currently have an installation on the system, you could quickly try to clear out the Cfg directory under TestStand, so that it generates new copies of these files.
Message Edited by Scott Richardson on 11-20-2008 12:38 PM
Scott Richardson
National Instruments

When building deployment, install reportgen_txt.seq but when removing program don't remove reportgen_txt.seq from the TestStand\Components\Models\TestStandModels directory?

Basically I want to install a custom reportgen_txt.seq file to the TestStand Dir\Components\Models\TestStandModels upon installation of the program but when I remove the program from my computer I want to keep the custom reportgen_txt.seq file...Right now when I remove the program, the custom reportgen_txt.seq file is also removed...
Anyone have any thoughts besides having to have a second deployment to install the file?
PLEASE HELP!!! And thanks in advance
Solved!
Go to Solution.

I went ahead and implemented using the custom commands, worked like a charm!! Thank you Thank you!
I just added a custom command using the xcopy function (see below). I needed three files to be copied over to specific directories once they were installed in the install directory. My three configured files were:
reportgen_txt.seq
Users.ini
TestExec.ini
Attachments:
customcommand.JPG ‏55 KB

DataBaseOp​eration in the TestStand

Similar Messages

Maybe you are looking for

DataBaseOperation in the TestStand