The easiest way to do this would be to use the Additional Results
setting on the step. Additional results allows for the logging of
parameter values underneath the Locals.ResultList[] variable. Also,
please see my post to one of your previous posts about how you might want to consider using Post-Substeps and storing parameter information in step variables rather than using the default code module like you are. If you switched to storing parameters (both inputs and outputs) as custom step varaibles then you won't need to rely on or use additional results and can instead just look at the corresponding step properties which store the data.
Please see the source code and step type definition for some of the step types that come with TestStand, like the messagepopup steps and numeric limit steps for examples.
-Doug
Message Edited by dug9000 on 04-19-2010 02:56 PM
