NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Logging local variables in database.

I used to be able to log a Local variable into the database by changing my schema with an extra column with the function Locals.Variable defined in the schema. That same sequence does not work in TestStand 3.5. Is there something different I should be doing in 3.5 compared to TS 3.0?
0 Kudos
Message 1 of 5
(4,117 Views)
Hi HPatel,

I can't think of any difference in TestStand 3.0 and 3.5 that should affect database logging.  Without seeing your sequence and database options, I'm not sure what the cause is (what do you mean by "does not work") but I would suggest making sure the properties for the local variable are correct. Try following the steps outlined in this knowledgebase article to see if sheds any light on the issue.

Have a great day,

Ecleamus Ricks, Jr.
National Instruments
Applications Engineer
0 Kudos
Message 2 of 5
(4,092 Views)
Thank you for the reference to the article. It looks like I would have to modify the Process Model which would change my other sequence files that use this process model. What I have done is used a LogToDatabase callback in my sequence file and created the variable in Locals of this callback. I have checked both options of Allow Propagation from Caller and Propagate to Subsequence for this variable in the LogToDatabase callback. I also had to copy the Main step from the Process Model LogToDatabase callback into my sequence LogToDatabase callback so the database logging is executed. This worked without changing the Process Model.

In TestStand 3.0, I was able to create a local variable in my sequence without needing any callback and just use that local variable in the database logging. That same sequence failed to work in TestStand 3.5. I'm not sure if the Allow Propagation from Caller and Propagate to Subsequence are new options for the 3.5 version, but I guess I have to do it differently in 3.5 to log the local variable in a database.

Thanks again for your help.
0 Kudos
Message 3 of 5
(4,081 Views)
Hi Eclamus,

is the same procedure applicable to the local variable created in process model it self in PreUUT Callback?



as i have created some local variables in Pre UUT and trying to log the same to the Database (SQL Server).


0 Kudos
Message 4 of 5
(3,877 Views)
Hello Original,

If you have a (local) variable in the process model, you will need to pass this variable to the "LogToDatabase" sequence as a parameter.  You can do this by modifying the parameter list of the "LogToDatabase" sequence in Database.seq to reflect this new variable.  After you pass the variable to "LogToDatabase" function, you will need to set the Configure » Database Option to include this new variable in the database.  This is only a brief overview of the "Logging a New UUT Property to a Database in TestStand" found at http://digital.ni.com/public.nsf/websearch/F5ADBC61222343B586256CE00055E6D6?OpenDocument.   Please see this document for a detailed description.  I hope this helps!
Best Regards,
Software Engineer
Jett R
0 Kudos
Message 5 of 5
(3,818 Views)