Hello Daniel,
Tried your suggestion, but it didn't work. Started playing around with the device name vs the resource name, got inconsistent results. Decided to try to build the string in a previous step, assign it to a local variable, the call that variable when needed. Seems to work now. Still not sure why I couldn't call it directly, but I can work with it this way. Thanks.
GSinMN
Thanks for the follow-up and the idea!
Unfortunately I still got an XML file after adding a ReportOptions callback to my sequence with DisableReportGeneration set to true.
Hi,
I am currently doing some design on a customer system using a model plugin sequence to integrate their process control system and keep standard Test Stand Models. I am however having some problems enabling an engine callback e.g. ProcessModelPostStep in the model plugin sequence. I can enable it in the Sequence File Callbacks... dialog, but it will never get called. It works fine in the Sequentialmodel, but I thought that the idea with the model plugins was to have customization separated from the standard model. Is there a way to indicate that an engine callback should be called or can the Process Model Callbacks only be called from the process model?
My model plugin sequence is created with the Advanced option in the Result Processing... dialog.
Hi,
Inside a LabVIEW TestStep I need to log an, at the start of the execution of the test-step, unknown number of additional results. These results are id's to other DB-table's and making them part of the step-results makes it easier to query the results together afterwards (this way each entry in the STEP_RESULT-table can be related to a number of entries inside PROP_RESULT-table which point to entries in other not standard TestStand tables.
Using the sequenceContext inside the LabVIEW-TestStep it's possible to log additional results into the Step-result container using the AdditionalResults.Insert method : SeqContext.Step.AdditionalResults.CustomResults.Insert("result)
I already noted that a Clear-method needs to be executed before starting to log additional results because else the results are appended to results from a previous run and are visible in the Additional Results View inside the Step-settings in the sequence Editor. This last behaviour makes me think I might have the wrong solutions and will take performance during execution. I would think they are only visible during run-time as temporary variables.
Are there other ways to add programmaticaly additional results inside a test-step?
Is there a way to programmaticaly set the data-type of the AdditionalResults.CustomResult? Now it's always logged in the PROP_RESULT-table as String (TYPE_NAME-field).
Thanks,
Roger
Just want to clarify some things for readers of this thread:
1) If you copy and paste a step, the newly created step gets a new, unique id. I'm pretty sure it's been this way as long as step ids have existed in teststand. You can see this directly if you turn on "Show Hidden Properties" in the station options Preferences tab and look at Step.TS.Id in the variables view.
2) If you cut and paste rather than copy and paste then the unique ids are preserved since that is really a move operation.
3) If you are programmatically cloning/copying a step, you need to call Step.CreateUniqueStepId() on the copy before inserting it into a sequence to guarantee you have a new unique step id for the step.
4) If you refer to steps by id rather than name, then you can have duplicate names and still refer to specific steps. That is why preconditions use the step id by default. Here's an example of using a step id:
RunState.Sequence.Main["ID#:PHf5NngRb0+OVNYzTGhTSC"].Result.Status == "Failed"
5) The expression browser dialog will actually show the name as a comment when you view the expression (even if you don't have such a comment in the actual expression):
RunState.Sequence.Main["ID#:PHf5NngRb0+OVNYzTGhTSC"/* Unique Id of 'Statement' */].Result.Status == "Failed"
Hope this helps clarify things,
-Doug
Hello aparab,
can you please explain it a little bit for me,
or modify the attached TS 2013 Sequence to show what you mean?
Thanks a lot
Hello,
when running a testplan it may happen that the user presses the stop-button. Then all instruments are still turned on.
Is there a callback-function that executes once the stop-button is pressed where i can cleanup my instruments?
If i would put the steps in the "normal" cleanup then it executes always but i want a special sequence that only runs if the stop-button was pressed.
Thanks for help
TM
Plug-ins currently don't support that directly.
Depending on what you need to do, you might be able to use the Model Plugin - OnTheFly Step Results entry point with a maximum number of results per call of 1.
If not, I heard a mention of someone who was working around this by dynamically adding and removing the callbacks they needed from the model file. I did not hear how well this worked out for them, but it sounded like it might be doable.
- James
Hallo Alexander,
I want to convey that only when the option in Result Processing is enabled then only I get the Sequencefile post resultlistentry callback activated.
Here is an example that works for me. If I run it single pass with a report enabled, I don't get a report.
Hi BRBASTS,
What do you mean, "analyze the answer"? You should be able to do something with the result of Step.StdOutput.Text in TestStand via the use of TestStand API expressions. No code module required.
TestStand 2012 Help: Expressions:
http://zone.ni.com/reference/en-XX/help/370052K-01/tsfundamentals/infotopics/bldgblocks_expressions/
In the future, you'll have better luck getting a response from the community if you create a new forum and add a link to another for reference (if needed). This forum is almost 5 years old.
Thanks!
I created a long term test designed to continuously test a product over time under various conditions. The test runs normally for about 2-3 days, and will then hang for an indefinite period of time.
TestStand is still running normally, I can break the execution, examine variables, and then resume, but the test still does not move on. Its as if TestStand hits some sort of wall or limit and refuses to continue executing any more steps.
I have reporting disabled along with the record results from each step option (I've run into issues of TestStand running out of memory on long term tests without disabling the results recording in the past).
Has anybody else experienced a similar issue or have an idea of where to start finding a solution? Apart from it not moving on to the next steps, everything else in TestStand and the sequence itself seems to be as expected. The issue was first found in TestStand 2013, and I recently upgraded to 2014, where the problem still persists.
I am calling LabVIEW HTTP PostBuffer.vi from TestStand. The buffer is a string. The protocol for the device uses quote characters:
"a=getavalue&j={"index": "test" }"
This results in an error in TestStand. because it is only expecting a quote at the beginning and end of the value.
Any ideas on how to deal with this?
Actually TS.Starttime is:
Time at which the step began executing, specifically the number of seconds since the TestStand Engine initialized.
So it just starts over at 0 when you start teststand, it isn't actually the date and time. I may resort to updating a variable I create, with some sort of step callback perhaps.
use the backslash \
"a=getavalue&j={\"index\": \"test\" }"
Thanks!
Hello aparab,
i have greated a StationGlobals ReportActivated and fill this global in the callback
ReportOptions with the the flag, if the report generation is disabled or not.
In the SequenceFilePostResultListEntry a if structure is insert that ckecks the flag.
Hope this helps.
Thanks for the clear example. I was not aware that the Parameter had to be set in a step execution in order to make the setting effective.
Hello,
While attempting to write a custom XML translation (XSL) for a TestStand result XML file, I found that the XML header would get corrupted and the string "; charset=iso-8859-1" would be inserted in the XML header. When the tag "omit-xml-declaration" is set to "yes", the first line of my XML output file still has the string "; charset=iso-8859-1" inserted into the first line. I think this may have something to do with the default TS reportgen_xml.seq sequence. Does anyone have any ideas?
XSL Source (just the beginning)
<?xml version="1.0" encoding="UTF-8"?><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:msxsl="urn:schemas-microsoft-com:xslt" id="TS14.0.0"><xsl:namespace-alias stylesheet-prefix="xsl" result-prefix="#default"/> <xsl:namespace-alias stylesheet-prefix="msxsl" result-prefix="#default"/> <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes" omit-xml-declaration="no" />
XML Source (just the beginning)
<?xml version="1.0" encoding="iso-8859-1" ?><?xml-stylesheet type="text/xsl" href="C:\Program Files (x86)\National Instruments\TestStand 2014\Components\Models\TestStandModels\StyleSheets\myNewStylesheet.xsl"?><Reports><Report Type='UUT' Title='UUT Report' Link='-1-2014-10-7-10-22-44-592' UUTResult='Failed' StepCount='8'><Prop Name='UUT' Type='Obj' TypeName='UUT' Flags='0x0'><Prop Name='SerialNumber' Type='String' Flags='0x0'><Value></Value></Prop><Prop Name='UUTLoopIndex' Type='Number' Flags='0x0'><Value>1</Value></Prop><Prop Name='CriticalFailureStack' Type='Array' LBound='[0]' HBound='[0]' ElementType='Obj' Flags='0x0'>
XML Output: (first line)
<?xml ve; charset=iso-8859-1rsion="1.0"?>
Thanks,
Aaron
