Vi stops in operator interface

Hello,
i have the following problem:
i made a custom steptype (TS3.0) that has been running fine for a while. Since a few month the vi (LV7.1.1) stops in the operator interface (only there, in the sequence editor it is ok). The frontpanel pops up (this is not ok) and the vi waits before i hit the button "back to executer". Then in the operator interface i must hit "continue execution" and the sequence runs normally. This problem occures only at the frist start of the sequence.
any ideas?
greetings
schwede

Hi schwede,
first, let me make sure I understand what the problem is:
You created a custom step type that runs a LV7.1.1 VI and use that in your sequence. It all worked fine until a while ago.
Now at every first call of the custom step, the front panel of the VI pops up and executes, then waits for you to manually close it. Once it is closed, you have to manually start the sequence again. The sequence can then keep on running correctly.
Please let me know if I understand that correctly.
One question that would come to mind is, did anything on the machine change between the time where it worked and the time where it didn't? Can you think of any software upgrades that might have been installed?
Regards,

Similar Messages

Can anyone explain the odd behaviour of the CVI Operator Interface?

This is probably really related to CVI in general, but I think people should be aware of this behaviour. If tracing is enabled and a program executing, moving the mouse cursor over the Menu bar area of the Operator Interface program increases the execution of the test program dramatically. Anywhere else slows it down! Could this have any effect during critical test runs? Is there a way to force the fast execution. (i.e. to disable whatever message processing is going on when the mouse cursor is over the rest of the window?)

Brian,
You did not mention what is the CVI operator interface that you are using. In the Simple CVI OI, which is located at \Examples\OperatorInterfaces, the behavior you mentioned may occur.
It is mainly because it uses a CVI timer to poll UIMessages, and the Timer Control runs in the same thread as the User Interface (CVI Panels). Because they both run in the same thread, when you move your mouse Windows handles the mouse move and repaint any window if necessary. While doing this, it stops all the other tasks that is running in the same thread, which means, the timer stops to tick and UIMessages are not handled for some time. In addition, the TestStand Engine executes synchronously with UIMessage handling, so if msg
s are not handled the Engine pauses the execution.
Finally, there is an example that ships with CVI under
\Samples\Toolbox\AsyncDem.prj that shows how to use asynchronous timers. In other words, a timer that runs in a different thread different than User Interface. I also modified the Simple CVI OI to use this asynchronous timer, check the attached zip file.
Regards,
Roberto P.
Applications Engineer
National Instruments
www.ni.com/support
Attachments:
Simple_CVIAsync.zip ‏176 KB

Why are my LabView Dialog Boxes no longer modal when using the Example LabVIEW Operator Interfaces?

Hello,
I have a step in my sequence that pops up a modal LabVIEW dialog box. My LabVIEW vi uses the TestStand - Start Modal Dialog.vi and TestStand - Stop Modal Dialog.vi as described in the example and it works as advertised when I'm using the TestStand Development environment however when I use the sample Operator Interfaces distributed with TestStand the Dialog boxes lose focus. I have the VI Properties->Window Appearance set to Dialog and have followed all of the instructions I could find for making a dialog modal. I've also reviewed all the documentation I could get my hands on including previous posts on this board and didn't see anything obvious.
Does anyone have any suggestions as to what I may be missing? Has anyone else experienced this problem and come up with the solution?
I am using LabVIEW 8.0 along with TestStand 3.5.
Thanks,
RG

Hi RG,
Running the example modal dialog in the teststand3.5 examples folder and using labVIEW8.0, I notice that when the Dialog is displayed its not active, but it is modal to the OI. Clicking on the Dialog panel makes it active. If you try to click on the OI panel behind, you can not. Is this what you are seeing?
I am using the Full labVIEW IO as supplied with TestStand and the example VI in the modal dialog folder is as supplied.
The LabVIEW Adapter is still configured to use the active labVIEW developement environment.
If I run the same example, only this time using LabVIEW7.1, the Dialog panel is active.
There is a patch to take it to labVIEW8.01, at this moment in time I am not sure what the update fixes.
There does seem to be a problem with TestStand3.5 (engine) and LabVIEW 8.0.
Regards
Ray Farmer
Regards
Ray Farmer

Sequence stopped on user interface when a sequence error happens on a step. Is possible to change this?

I'd like to know if when developing an user interface over TS using MFC, if a sequence error occurs, I get an error on the user interface and the sequence stops without giving any other option. Is possible to continue the sequence, and show as failed the sequence that caused the error?
Dani

hello Daniel -
If you are talking about the behavior of the simple operator interface example for MFC, then the reason why the error immediately causes a 'skip to clean-up' is because it is set explicitly in the code for the error case. To fully handle the error (as the sequence editor would), you would want to modify the case where the error is detected and perhaps tap into the TestStand API for Engine.DisplayRunTimeErrorDialog( ). If you are able to view the C code written for the full version of the CVI operator interface, you may want to use that as an example of how to completely handle every error.
An alternative is always to handle errors yourself. If you are interested in knowing strategies for such customizations I recommend you look into the shipping examp
les and downloadable programs for sequences leveraging the PostStepRunTimeError callback.
Regards,
Elaine R.
National Instruments
http://www.ni.com/ask

Error Generated by DIO Port Read when using a compilied Operator Interface

When using a compilied version of an TestStand Operator interface, a Vi that reads the status of a port on a PCI-6602 board stops working. Within this VI a sub VI called Read DIO Port brings back an error -10007. But when I use the un compilied version of the operator interface there is no problem with the VI.
Why is this so?
Attachments:
Get_SIU_Switch_States.vi ‏58 KB

I have tried to simulate this issue and I have not been able to replicate your issue.
I know the -10007 occurs when you try and create/use a resource index that is not possible i.e if your referencing channel 9 and the device only has 8 channels.
Have you managed to overcome this issue yet?

Add limits and results columns to Operator Interface

Hi,
I am using TS 4.0.1 and CVI 2009. I want to modify the CVI Operator Interface to display columns with the test result and the high and low limits. I tried to modify the properties of the SequenceView control on the operator interface by adding columns, but the changes are not seen when I run theOI.
How can this be done?
Thanks
John

John,
the display of the requested information depends on the "binding" of the control. The SequenceView control can be connected as SequenceView (ConnectSequenceView of the Sequence File View Manager) or as ExecutionView (ConnectExecutionView of the Execution View Manager). The later connection displays the result during execution like this:
But it will only display during execution, not during edit time! (Result is always a runtime property because why should a test sequence return any results during edit time??)
Limits are displayed in the description of the NI steptypes like seen here:
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Remove step icons from CVI Operator Interface to improve execution performance

The CVI Operator Interface updates the icons for each step (lower right) when tracing is enabled. Can these be stopped but the steps still visable and would this improve execution performance.

Hi Dave,
I take it you are using the old style Teststand Operator Interface.
The only way would be to modify the code in the exedisp.c, in UpdateOnStepChange() function. Just comment out the SetCtrlBitmap() function there are two calls in this function.
As to whether it is going to make a noticable different in performance, well that depends on the spec of the controller (PC), graphics card etc. you are using. But you probably wouldn't notice any diference.
Before you make any changes, copy the sub-folders from the NI folder to the User folder and work from the User folder.
Regards
Ray FarmerMessage Edited by Ray Farmer on 05-07-2005 06:29 PM
Regards
Ray Farmer

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 use the T. S. operator interface I need to add pass fail and error

Hello:
I am using Labview 6.1 and Test Stand 2.0
I have made some modification to a copy of the T.S. Labview operator interface. How do I get the pass/fail or error from test stand to be pass to LabView so I can tell the operator that the unit pass or fail the test. I do not want to use the Test UUTs. I want this to be very low operator response.
Message Edited by Toro on 02-28-2006 01:52 PM

Not sure if this is available in the earlier versions of TestStand, but I think so.
You could post a UI Message, from your execution entry point in the process model, to your User Interface indicating the pass/fail/error status when a test run is complete. You will need to handle the UI Message in your Operator Interface. See TestStand II Customisation course notes for handling UI Messages.
The data passed in the UI Message can be anything you like, the UI Message handler in the User Interface will have to process the message and update the display as required.
Hope this helps
Steve
Message Edited by SercoSteve on 03-01-2006 10:02 AM
There are 10 types of people in the world that understand binary, those that do and those that don't.

How can I get RTE information in operator interface (LV) from TS API?

Hi!
I have operator interface in Labview and use TS API to run tests.
I would like to eliminate RTE dialog and to show error messages directly in front panel control.
I have created callback for TS Application Manager BreakOnRTE event.
It works good and I can lock dialog apearance.
But if I try to get ErrorObject from event parameter (execution) is is empty (has no error information).
But this parameter is real execution which contains step with RTE.
When I allow the dialog appearance in this callback, it contains RTE information.
Where can I get error information from this callback or get it any another way?
Thanks in advance for any assistance.
Solved!
Go to Solution.

I have found the way to get RTE from callback BreakOnRunTimeError of ApplicationMgr.
This way is:
Execution->GetThread[0]->GetSequenceContext[0]->GetRuntimeErrorMessageEx().
It was not clear for me: all Error fields in step and Sequence are not filled yet on callback time.
Only the context method can return error message.
The question is closed.

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

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

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

Adobe Edge Animate CC 2014.1 is totally not working. It stop working after 5min. Sometimes is stops the operating system.

Adobe Edge Animate CC 2014.1 is totally not working. It stop working after 5min. Sometimes is stops the operating system. On on mac OS X Yosemite. macbook pro i7 2013.
I reinstalled it not helping.
Message was edited by: Daniel Boguszewski

UPDATE
i have ulpaded 2 animation ( one normal and one Responsive ) in 2 different server here the link
www.eclipseadv.com/maliRP/maliRP.html
Untitled
via SAFARI or CHROME on MAC all OK
but via IPAD ( SAFARI, CHROME and MERCURY) i didn't see the video, just the animation of the BUTTON and the link if i click on it (not in Mercury), like in the content viewer.

I get the error message in QuickTime "operation stopped the operation is not supported for this media" most times when I try and export an .AVI file as something else (.m4v). I have not touched the file in any way (no trimming, clipping or other editing)

I get the error message in QuickTime "operation stopped the operation is not supported for this media" most times when I try and export an .AVI file as something else (e.g. .m4v). I have not touched the file in any way (no trimming, clipping or other editing), all I want QuickTime to do is export the file in a compressed format. Bizzarely, if I shutdown and open QuickTime many times I can occasionally export a clip as another format (maybe one in 10 times). I have seen that other users have had a similar problem after clipping files in QuickTime but this seems to be a slightly different bug in that all I do is open the file and then try and export the file as is - either way, this is a very annoying bug

@Z_B-B, thank you for taking the time to respond to my cry for help. However, the link you supplied does not address the problem: I am not trying to export from Final Cut Pro to QuickTime, I am trying to export from QuickTime to the rest of the world (like people's iPhones and Ipads) in .m4v format (so I am not emailing my freinds such huge files).
If I were to spend hundreds of Dollars on a copy of Final Pro I could export directly from there and not have to bother with QuickTime, but I do not take enough video clips to justify the cost. I must say that I never had any of these problems before I decided to switch from Snow Leopard to Mountai Lion.

Why do I not see a 'busy' indicator in the operator interface?

Hi all,
Ok, probably a stupid question, but here goes.
I can run my tests (mostly VIs) in the teststand LV operator interface without problem. In fact, they run quite well. The problem is, when the user initially hits the 'single pass' button to begin testing, there is about a 20-30 second delay before the actual VI front panel appears, ready for testing. During this time, there is no signal that the operator interface is doing anything. No hourglass, no indicator whatsoever. The problem is that several users have continued to click the 'single pass' button, which causes more than one instance of the VI to open, and slows the testing down, and confuses the operator.
When I play with the LV operator in
terface on MY pc (not the test pc) I DO see an hourglass when I press the 'single pass' button.
Does anyone know where it went on my test machine? The test machine is a Win98. I'm using TS v2.0.1 and LV v6.1
Not a big deal, but would be nice to fix another user complaint!
Thanks in advance,
Dave Neumann

Nick,
I'm using the shipped version of the operator interface -- I haven't made any alterations to it at all.
I compiled the test engine in Teststand and then used the setup.exe and .cab files to install it on the test machine. When I did the compile, I included the 'common vi' folder (where the busy indicator vi is located on my development machine).
Any other questions, let me know.
Thanks again for your help.
Dave

Problem in Teststand Operator Interface

I am facing problems when i try to run my sequence file from TestStand Operator Interface for LabVIEW. It gives either all tests as failed or skipped but the same sequence file when i execute from TestStand Sequence Editor it gives me correct results. I am not able to figure out what is the problem?? Somebody worked with teststand operator interface please help me to solve the problem.
Regards
Subramania Bharathi.

Hi,
Which version of TestStand and LabVIEW are you using.
Are you using a Customised LabVIEW Operator Interface or are you using the default version?
If you can provide a example of your Test Sequence File to help identify your problem.
Regards
Ray Farmer
Regards
Ray Farmer

Vi stops in operator interface

Similar Messages

Maybe you are looking for