10-04-2010 09:07 AM - edited 10-04-2010 09:08 AM
I have a VI that returns a Boolean pass/fail which maps into step.result.passfail. I return another hex value from the same VI that only needs to be logged on the datasheet, but has no pass/fail status. It comes back via a telnet connection as a string. If I convert it to a number I can use the null type adapter and call it a numeric limit test with a comparison type of none and it will get logged on the data sheet without any pass fail consequences. It would be simpler just to pass back the string and have it logged. In fact this is a general case, there may be many times I just want something returned from a VI to be logged on the data sheet without any checking. What testStand tool/object/gizmo could one use?
Thanks,
jvh
10-04-2010 09:47 AM
Tool/object/gizmo to use is an Action Step
The Action step calls code modules that do not perform tests but, instead, perform actions necessary for testing, such as initializing an instrument. By default, Action steps do not pass or fail. The step type does not modify the step status. Thus, the status for an Action step is Done or Error unless the code module specifically sets another status for the step or the step calls a subsequence that fails.
You can use the TestStand - Evaluate.vi code module template to create a VI that includes a ReportText indicator.
10-04-2010 12:39 PM
@Phillip Brooks wrote:
Tool/object/gizmo to use is an Action Step
Action Step
The Action step calls code modules that do not perform tests but, instead, perform actions necessary for testing, such as initializing an instrument. By default, Action steps do not pass or fail. The step type does not modify the step status. Thus, the status for an Action step is Done or Error unless the code module specifically sets another status for the step or the step calls a subsequence that fails.
You can use the TestStand - Evaluate.vi code module template to create a VI that includes a ReportText indicator.
OK, thanks. Where would I find this VI?
Just looked at some legacy code here. Seems like text was reported up via Step.Result.ReportText
10-04-2010 12:52 PM
I don't know if your 'data sheet' is a custom report, but for the default report you can add parameter values to the report by using Step Settings>>Properties>>Additional Results>>Parameters.
In the next version of TestStand you will be able to the same thing by clicking a "log" checkbox next to a parameter.
10-04-2010 01:10 PM - edited 10-04-2010 01:11 PM
jvh75021 wrote
OK, thanks. Where would I find this VI?
<TestStand Public Directory>\AdapterSupport\LabVIEW\TestStand - Evaluate.vi
@jvh75021 wrote:
Just looked at some legacy code here. Seems like text was reported up via Step.Result.ReportText
Our group has been using LabVIEW/TestStand since 5.0/1.0 days and many of our legacy code/sequences still use the Test Data cluster. This is a typedef found in
vi.lib\AddOns\TestStand\_TSLegacy.llb\LabVIEW Test - Test Data.ctl
10-05-2010 10:33 AM
What James said is probably your best option. To clarify:
1) use a pass/fail step for your boolean.
2) use the additional results setting on the step to log the parameter you wish to show in the report.
Hope this helps,
-Doug