Encrypted results in TestStand

[gerrynag]

I want to display and store encrypted test results using TestStand. I would prefer not to have the result encryption done in the VI doing the measurement, but to have a dedicated VI or dll doing the encryption.
I would also like to use encrypted test limits, (stored in file), which would need to be decrpyted before being passed to measurement VI.
What is the best way of doing this in TestStand ?

[Elaine_R.]

Hello Gerry -

One thing that I might suggest is to build a VI into your process model. There is a point immediately after your 'TestReport callback' step and before the 'Write UUT Report' step where you have the entire report text as a string variable. If you are talking about encrypting the whole file, this would be the ideal point to pass the string to VI and then write the modified value to the file.

If all you are interested in is writing a normal file with encrypted measurement values or something of the like, your best bet is to modify the actual report generation, probably by using a model callback such as "ModifyReportEntry" since one of the input parameters to the callback will be the 'completed' string for one particular test in the report body.


Let me know if neither of these ideas were what you were asking about. It may be that I just didn't understand the question.

Regards,
Elaine R.
National Instruments
http://www.ni.com/support

[gerrynag]

Hello Elaine,

What you are suggesting is not quite what I am after, as it only seems to affect the Report Generation.
I also need the result (and limits) to be encrypted at the test step stage, so that if anyone was to pause the program, they would not be able to look at the result and limit variable values and see the un-encrypted values.
I was thinking of having an de-encyption VI just before each test step that would de-encrypt the encrypted limits and pass them to the test VI and an encyption VI just after each test step that would encrypt the test results.
But, not sure the best way to do this.
As for the Report Generation, it would only be the results and limits that need to be encrypted.

So would be grateful for any suggestions.

Regards,

G
erry