TestStand 3.5 step run mode ingnored during execution

Hi,
I am seeing a problem in Teststand 3.5 to do with the step run mode. I have a sequence which i have a number of steps that i have set the run mode to skip. However when i execute the sequence some of the run mode skip settings are ignored, by this i mean that they are set back to run mode normal.
It is always the same test steps that this happens with, one step is a numeric limit test and one is a CVI dll multi numeric limit test call. I have tried saving the sequence under a different name in case the sequence has somehow corrupted but this made no difference.
Has anyone seen this before?

Hi,
Is it possible to post an example highlighting this problem?
regards
Ray Farmer
Regards
Ray Farmer

Similar Messages

Can I set the "step run mode" -property with the property loader

Is it possible to set the "step run mode"-property by using the property loader to "Skip" , "Normal" or "Force PASS" ...in TestStand 3.0 ?

I turned on Station Options>>Preferences>>Show Hidden Properties and then exported the Step.TS.Mode property to a limits file. I then added a PropertyLoader step and it functioned correctly.
Note that importing a hidden TS subproperty makes an edit to the sequence file, even if done at runtime. Thus if you later save the file, you might end up inadvertently saving the last imported values. This isn't necessarily a problem if the values in the file are always overwritten by a property loader step.
(btw, I tested this in 4.0, but I'm hopeful it would also work in 3.0)

Error at step Run ABAP Reports during system copy in HPUX

Hi experts,
During system copy from Prodcution to Development i am facing the following errror at step
Run ABAP Reports
INFO 2009-03-18 03:57:36
Information for application function INST_EXECUTE_REPORT copied to local Repository.
INFO 2009-03-18 03:57:36
Function module INST_EXECUTE_REPORT set successfully.
INFO 2009-03-18 03:57:36
Executing function call INST_EXECUTE_REPORT.
ERROR 2009-03-18 03:57:38
FRF-00025 Unable to call function. Error message: Exception condition "WRITE_FAILED" raised. .
INFO 2009-03-18 03:57:38
RFC connection closed.
ERROR 2009-03-18 03:57:38
MUT-03025 Caught ERfcExcept in Modulecall: Exception condition "WRITE_FAILED" raised..
ERROR 2009-03-18 03:57:38
FCO-00011 The step runRADDBDIF with step key |NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_ABAP_Reports|ind|ind|ind|ind|2|0|runRADDBDIF was executed with status ERROR .
Please let me know the solution
Thanks & Regards,
Arun

This seems to be related with permission to write in /usr/sap/trans
Read,
Re: Run ABAP Reports error during ECC 6.0 installation on Win2003 with Oracle
Exception condition "WRITE_FAILED" raised during installation 4.0
and
Install error at Phase 33
Regards
Juan

MySQL query works fine for Debug mode not during regular run mode

Hello fellow Java gurus,
I'm very much confused at the moment. I have an Java application that populates and accesses a MySQL database. It's a little complicated to explain but basically I've got a few threads that manipulate it. The database itself can handle multiple client connections.
Now, my first SQL query determines whether records exist within a particular timeframe, since one of my columns is a time of arrival (toa). This works fine in debug and normal run mode. My second SQL query is only executed once the first query returns true, which occurs 100% of the time. The second query is very similar, however, has the very weird behaviour of working the way I want it during debugging mode, but doesn't work at all during normal run mode. I really do not understand. I've tried running the 2nd query using the same connection and also a different connection as to the 1st query but it really doesn't make a difference to the non-working outcome.
If anyone has any ideas as to as to why this is happening, please help me. Any feedback would be greatly appreciated. I am desperate at the moment.
Kind regards,
Mitch.

Sorry everyone, I've been able to solve it. My boolean variables were being set to their opposite values! Silly me.... cheers anyway....

Menu bar shows when I stop the error 8 occur during run mode of .exe file

when error 8 occured and I click on "stop"
option rather that "continue".then vi stop and file,edit menu shows. in
exe RUN mode,this is also happend so what is the solution for not
seeing the menu bar when i stop the error 8 option in run time. it
should be stop as it is condition..

Hi Milap,
have you read my comment in your other thread?
This error message pops up when you don't have programmed any error handling!
Well, you use "Write to spreadsheet file" for saving your data. Look inside this function (and it's subvi "Write Spreadsheet string") to see how to use low level file functions. After the "Open/Create/Replace File" you have to check for any error (like error 8)...
Message Edited by GerdW on 06-26-2008 10:44 AM
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Loading test steps during execution

Hello,
I am using the operator interface from the example. I have modified to suit my application. I run the test using the Single Pass entry point. I have 46 steps in my main sequence. When I press the Single pass execution, Initially it takes a lot of time (I think it compiles all the steps) to start the actual execution.
Why does it take long time to start execution? Is it possible to configure test stand such that it compiles each step as and when it reaches it?
Regards
Gopal

Hey Gopal,
As Ray said, TestStand does not actually compile your modules. That being said, most likely this load time that you're seeing at the beginning of execution is due to your load options set to load the module when execution begins. If you go to the step properties, notice under "Run Options" there's a "Load Option" drop-down. You can look at the help for a description of this property, but in general this setting refers to when the module is loaded into memory. For time-critical tests, you would want to load either at the beginning of execution or when the sequence file is loaded (as this would extract the load time from the step so that the step could be executed quickly); this is especially important if you are looping on a particular step. There is an option to "Load dynamically" as well. With this option, you would see a slight delay before each step during which its module is loaded - rather than a longer delay at the beginning (in which all step modules are loaded).
Note that the default is "Preload when execution begins"; that is why I'm guessing that this is responsible for the delay that you're seeing.
Thanks,
Andy McRorie
NI R&D

Can I change "Skip Mode" to "Run Mode" on all sequences, recursively?

I want to make sure that none of my sequences steps are in Skip Mode, but I have many layers of sequences now.
Is there some way to un-skip everything without tediously opening every sub-sequence?

Hello
bmihura,
I have attached a zip file below that sets the run mode for
every step within a single sequence file. If you would like to add this
utility to the tools menu of TestStand, simply select Tools >> Customize
>> Add. In the window that appears select Sequence for the item
type, then select the ChangeRunMode.seq sequence file and specify the
MainSequence in the sequence input. Next click ok twice and you will have
this utility added to your Tools menu. This sequence file was saved in
TestStand 3.1 and TestStand 3.5.
Bob, there is no information in the TestStand class that
directly shows you how to create an application that changes the run
mode. The information taught in the class should provide the tools
necessary to write code similar to what I have posted.
The discussion forums are a great way to find solutions to
the problems encountered in TestStand. As you can see, National
Instruments employees are constantly providing help to customers on the forums.
Regards,
Jesse O
Applications Engineering
National Instruments
Jesse O. | National Instruments R&D
Attachments:
ChangeRunMode.zip ‏81 KB

Stuck with run mode

Hi
I am stuck with run mode on one of my VI (I can't edit it or even see the diagram). here's what I verified
1. tools>option>miscellaneous> I uncheck "Open VIs in run mode"
2. I hit Ctrl+M, it is still in run mode
3. I close LabVIEW and reopen, it's still in run mode
4. I check the VI file type, it's not a read only
Do u have any idea about how I can go back to edit mode to modify the diagram? I'm using LabVIEW 7.1
Thanks

Without having the VI in front of me it is difficult to say exactly what settings you have turned on.
I would suggest trying the following things to get your VI out of run mode.
1) Ensure that "Open VIs in Run Mode" is turned off in Tools->Options->Miscellaneous
2) Open the VI by dragging it into another block diagram and double clicking on it
3) With the VI open hold down control and press the '.' key. This is the same as pressing the "Abort" button.
4) Hold down control and press 'M' to switch out of run mode
If you can reproduce the behavior in a VI which you are able to post on the forum, I am sure we will be able to figure out what steps are needed to edit the VI.
Scott Yellig
Applications Engineer
National Instruments

Disable a test socket during execution (Batch Mode)

We are running a Batch Model with Batch Synchronization. I am wondering if it is at all possible to totally disable one or more of the test socket during execution. I know that the opening screen allows you to choose which sockets are active, but in the event that something goes astray like the RS-485 communication is non-responsive, I would like to disable one or more at anytime during the test. Thank you in advance for any ideas you come up with.
Regards
Scott
Environment: TestStand 2010
Solved!
Go to Solution.

I am not aware of how to stop a socket which is already running and facing an error midway.
But this setting will ensure that the socket is disabled for the next runs.
1) Override the preBatch callback.
2) Call this statement in the current executing thread to stop the socket from next run. ( precondition = on error)
RunState.Caller.Parameters.ModelData.TestSockets[RunState.TestSockets.MyIndex].Disabled=True

Evaluating NaN Comparison Type in TestStand Numeric Limit Step

I'm using a 4070 DMM to return Resistance Measurements to a TestStand numeric Limit step. How can I use a comparison type when the LabView vi returns NaN (Not a Number). I want the step to pass as long as the Resistance Measurement is > GT some value.

NAN comparison in expressions and limit tests works as follows
(NAN > x) == false
(NAN == x) == false
(NAN < x) == false
(NAN == NAN) == true
To summarize, a NAN is neither greater or less than another number and is only equal to another NAN.
If you want NAN to fail and measurement > some_limit to pass, then just use the > (GT) operator.
If you want NAN to also pass, then you need to check for it separately. You can do this dozens of ways. Here are a few:
a) Use a pass/fail step with an expression like: Locals.x > 10 || Locals.x == NAN
b) Use two limit steps, one to check for NAN and one to check the limit. Use preconditions to specify the NAN check only runs for the NAN value and the limit check only runs for non-NAN values. This will ensure
the measurement makes it to the report.
c) If NAN is your instruments way of returning "resistance too high to measure", then you could transform the NAN into an INF in the data source expression and then use a GT limit. Example data source expression:
Step.Result.Numeric == NAN ? INF : Step.Result.Numeric

Design mode: Error during component layout. Choose Design Refresh to refresh design mode.

Description Resource Path Location Type
Design mode: Error during component layout. Choose Design > Refresh to refresh design mode. etPlayer.mxml /etPlayer/src Unknown Problem
Refreshing wont work..
any ideas?

Some elements can cause the design view to break, it recently happened to me and this was my solution.
I began by commenting out most of the visual elements from code and going back and forth to design view to try and get it working.
Finally I narrowed it down to the "ToggleButtonBar" component. After I commented this line out the design view was up and running.
This might not be the solution but it will get you back up and running.

How to set pre conditions to set the run mode to skip or normal?

Could you please let me know how can I set a precondition based on a local variable so when the variable is 1 I can skip a test or when it is zero I programatically set the run mode to normal.
Thanks

I have a case where I use the Pre-Condition to skip some steps (subsequence call) for a specific test) if that test has run successfully already.
This is handled in a 'SequenceFilePostStep", thus the "RunState.Caller....".
The Precondition is set to 'False' so it won't run.
'Set the Precondition on the next step to "False 'Remove" (The remove is to indicate that it will be removed later so it's not saved in the sequence file.)
Locals.sPreviousPrecondition1 =RunState.Caller.Sequence.Main[RunState.Caller.RunState.NextStepIndex].Precondition,
RunState.Caller.Sequence.Main[RunState.Caller.RunState.NextStepIndex].Precondition ="False 'Remove"& Locals.sPreviousPrecondition1
The "False 'Remove" needs to be removed later, or it will be saved in the file and remain. This is accomplished later with:
'Need to copy the contents to a Local variable, manipulate it to remove the "False 'Remove" string then re-assign back into the Precondtion
Locals.sPreviousPrecondition1 = RunState.Caller.Sequence.Main[RunState.Caller.RunState.PreviousStepIndex].Precondition,
Locals.sPreviousPrecondition1 = SearchAndReplace(Locals.sPreviousPrecondition1,"False 'Remove","",0),
RunState.Caller.Sequence.Main[RunState.Caller.RunState.PreviousStepIndex].Precondition =Locals.sPreviousPrecondition1
Mike

Method of debugging in form run mode...

Hello.. fellows...
I use forms6 and i am beginner,
so i have a problem in debugging
How can i process debugging in run mode
i execute forms6 module in debug mode
and make break point in procedure
in menu, there are many icons(step into, step over, step out.. etc) but all of this
icon are not available.
how can i resolve this problem
i am beginner .. please.. help me.!!
thanks for reading..
null

yoyolk wrote:
I guess I did not express my question correctly. What I meant is I can use a while loop to create a dynamic interface. I can activate or disable a variable (control) by push the green botton before I hit the RUN button to continuously execute the VI. However, when I activate the control, for some reason I can not change its value. I just wonder how I can change the value of a control in such a dynamic interface.
A couple of red flags here:
As others have said, since you don't show the labels on the diagram, we cannot tell what's what. We also cannot see what's in the other frames of the sequence. Please attach the actual VI instead.
Your "disabled" property is either 1 (disabled), or 2 (disabled&grayed out), never zero (enabled). Unless it is enabled, you cannot operate it!
What is the point of your while loop that seems to spin at near infinite rate while consuming all CPU, rewriting he same properties over and over again. A property remains set until changed to something else, thus they only need to be written when the property needs to change.
.... and what's the purpose of the stacked sequence, just to hide code even more?
LabVIEW Champion . Do more with less code and in less time .

Enabling/Disabling of stop button for Tomcat in MyEclipse in Run mode.

Hi,
I am very perplexed by the behavior of the Server option in MyEclipse 4.1.1 over Eclipse 3.1.2 using Tomcat 5.5.17.
When I start the server in Debug mode, the behavior is just fine. i.e. the stop button/option gets enabled and the Start button/option gets disabled when I start the Tomcat server.
But in the Run mode, the Start option does not get disabled and the Stop option does not get enabled when I start the server, so I have to guess/rely on the console to see if an instance is already running.
If anyone is having the same issue/behavior, and did something to correct it, please respond or point me in the right direction.
I have already:
1) Downloaded a new instance of both Eclipse and MyEclipse
2) Created the whole workspace again after deleting the .metadata
3) Tomcat is a part of our configuration management software so everyone uses the same version.
Edited by: nimraj on Apr 3, 2008 7:17 AM

Hi Sumit,
just add one more attribute of type wdy_boolean, and bind this attribute to readonly property of button by coding.
then as per your cell value set the attribute value, below is the some sample code.
METHOD wddoinit .
DATA: lv_node TYPE REF TO if_wd_context_node,
        lt_mara TYPE ig_componentcontroller=>elements_mara,
        wa_mara TYPE ig_componentcontroller=>element_mara.
SELECT matnr
         ersda
         ernam
         mtart
         matkl
         meins FROM mara INTO CORRESPONDING FIELDS OF TABLE lt_mara
                                 WHERE meins = 'GM' OR meins = 'CCM'.
SORT lt_mara BY meins.
lv_node = wd_context->get_child_node( name = wd_this->wdctx_mara ).
LOOP AT lt_mara INTO wa_mara.
    IF wa_mara-meins = 'GM'.
      wa_mara-readonly = 'X'.
    ELSE.
      wa_mara-readonly = ' '.
    ENDIF.
    MODIFY lt_mara FROM wa_mara TRANSPORTING readonly.
    lv_node->bind_structure( SET_INITIAL_ELEMENTS = ABAP_FALSE
                              new_item = wa_mara ).
ENDLOOP.
lv_node->bind_table( new_items = lt_mara ).
ENDMETHOD.
Regards
Srinivas

Labview opens all VIS in Run mode

LV2013 PDS is opening all VIs in Run Mode. This is a global problem, not specific to one or a specific number of VIs.
If I create a new VI, save it, close it and re-open it, it's in Run Mode, not Edit mode. Nothing is set to Run When Opened, nothing is set to be locked without a password.
It's only on this installation; if I take my code to another machine, there's no issue.
I have deleted the labview.INI file, but the behavior repeats itself.
Any ideas?

Jed_Davidow wrote:
SCC is not configured; I use perforce, but it's not configued to use it or to treat read-only as locked. I have also checked out all the filed ahead of time with P4, so LV never sees them locked. The folders themselves are not read-only.
Also, I have created VIs outside of my P4 folder, and I have the same trouble.
Example:
Launch LV: Create a blank VI (comes up in Edit mode).
Save to Desktop (not within P4 control) as test.VI
Close
Open test.VI ---> It's in Run Mode
I have never seen this happen before.
Neither have I
I'll assume a reboot was attempted and did not change anything. I would attempt a repair of LabVIEW from the control panel and another restart.
Jeff

TestStand 3.5 step run mode ingnored during execution

Similar Messages

Maybe you are looking for