I agree. I never thought it was, except for the style sheet making the new security settings unhappy for some reason.
Are there any plans to migrate the report viewing tool to full support by NI? Microsoft is most likely going to deprecate IE sometime, in favor of Edge. We have never been able to get any other browser to work. Edge, Firefox, Chrome or Safari.
Can you elaborate more on what you mean by the report viewing tool?
In TestStand 2019, which will be in beta in the upcoming weeks, TestStand will have the capability to generate PDF reports natively.
At our factory I need to change the process model, eg. how to extract the part number.
When I change the process model, must I avoid changing the call backs(eg. preUUTloop) in the process model or is it recommended to put the change in the call back?
With the old property loader format there was an option with "Skip Rows Beginning With:" which I used to tag property values with requirements. There doesn't seem to be an equivalent with the new file format, is there any syntax to add comments that won't cause an error when the file is loaded?
I am fighting with the same problem.
Is there a way to do this by Teststand API?
I have a TS2012 sequence that is running with the Test UUTs Execution Entry Point within a modified Sequential Model. The sequence has a number of Numeric Limit Tests that execute conditionally (occasionally for some test runs they will be skipped).
For a single Test UUTs execution; the behaviour we are seeing is that for the first UUT, a particular Numeric Limit Test is run and returns a measurement. My issue is that if now a second UUT is run and that the Numeric Limit Test that returned a measurement value for the first UUT is conditionally skipped, the step status says Skipped (as expected) but the measured value displayed by TS is the same value as returned for the first UUT.
It looks to me like the ResultList is not being cleared correctly at the end of a run and as a consequence contains and displays data from a previous run.
We have modified the Sequential Model so it is possible we have accidentally deleted the step that stops this sort of thing from happening. Outside of that any suggestions about why this happens and any solutions to stop it would be greatly appreciated.
Steve
I m facing problem with windows update but ur solution is not working for me can us suggest another way.
Several releases ago in one of the data add on packages, there was an XML viewer provided by NI. I think it was part of "NI TestStand Toolkit for Large Application Development" , but not sure if this was just a sequence file viewer and did not handle style sheets for log files.
If it does not support it, I guess my question simply drops to what viewers are supported? RIght now I can only get IE to work. BTW, our IT group loaded 1803, and now cannot view the log files, and they are now digging into why.
My guess is that it's something you've done to the process model. When I run a multi-numeric step and skip it (even on the 2nd or 3rd Test UUTs run) it doesn't display any measurements. It just says skipped with no data showing.
Any way you can reproduce using the default model?
BTW- I did confirm that it does indeed retain the values from run to run and if skipped will retain the last value. So if you display the data then you will get the old values. However, as I mentioned, default model doesn't display measurement data if the step is skipped.
Hi,
I just installed and started to use TestStand to create testbenches using different VI's. Everything works fine, except for the fact that when there is any error in any VI of the sequence, this is not displayed and the TestStand continues the execution of the tests as if nothing happened.
For example, one error could be that a file I want to open in the VI is not found (this error is correctly displayed in Labview by a pop-up window, without using Simple Error Handler or similar).
However, if I run the VI in TestStand, the error won't be displayed and the execution continues.
The option Configure --> Station Options --> Execution --> On Run-Time Error is set to Show Dialog Box.
Is there any reason why this happens?
Thank you
Are you connecting the error out of your VI to Step.Result.Error?
Hi,
I'd like to modify the default filename format in the report options utility.
The default is SeqFileName_Report[Time][Date]_00001.xml.
I'd like to add a variable to the string
SeqFileName_Report[TestPoint][Time][Date]_00001.xml
Which callback to I need to use to modify that and how do I do it?
Thanks
Curt
No, the errors are not connected to anything. When an error occurs, the execution of the VI stops and the error window pops out (in Labview). This does not happen in Teststand.
Do I need to connect the errors? This is not convenient for me, because I will be using already designed VI's that don't have the errors connected, and therefore I will need to modify all those VI's.
If you want TestStand to display the error then you need to pass the error from LabVIEW to TestStand. Otherwise, how does TestStand know that an error occured? To TestStand your VI is a black box. It can feed inputs and get outputs. Anything that happens inside the VI stays in the VI.
Hope this helps,
I am pleased to announce that we plan to release a beta version of TestStand 2019 in the latter half of January. Additions to TestStand’s features include:
A full list of all new features will be available in the beta documentation, which will be available when the beta begins. Although the TestStand 2019 beta software is not available yet, I encourage you to pre-sign up for the beta now so that you can access the software immediately once the beta opens.
To sign up for TestStand Beta, complete the following steps:
Registration does not necessarily guarantee you a position in the beta program. Determination of acceptance into the program is up to the sole discretion of National Instruments.
A follow up email will be sent when the beta is available for download. I look forward to working with you during this Beta, and please let me know if you have any questions!
Roxy
Automated Test Software R&D
I understand. I'll try then to output the errors.
It is not very convenient for me because I am using already designed VI's (from other people) which work well, but don't have a well designed error structure. This forces me to modify all these VI's.
Thank you for your explanation.
Hi,
There are two options, and what suits you best depends on the nature of your application.
Scenario 1:
If you plan to or are developing multiple different test sequences that will all share this common functionality. It is preferred to modify the process model itself.
See Modifying Process Model Sequence Files
Scenario 2:
If you plan to add this functionality only to a small subset of test sequences. You can override process model callbacks using model callbacks
Using Callbacks in NI TestStand
I hope this answered your question.
Cheers!
//Marcus Bengths
Hi Adam,
You can try using this syntax to comment property: http://zone.ni.com/reference/en-XX/help/370052N-01/tsapiref/reftopics/propertyobject_comment_p/
It is from 2014 but it might still apply to the new file format.
Kind regards,
Kelly
The situation is like this:
All of our test at the factory will use the same proces model(seq,batch,par.).
At the start of a test, we override the callback 'PreUUTloop' to initialize the HAL measure instruments.
The problem now is that you cannot add or remove parameters in de 'PreUUTLoop' of the process model because it will not be compatible with the tests, which are previous made, which override the callback 'PreUUTLoop'.
