At execution, all the useful configuration and result of all Modbus Steps is added to the report. So, the configuration that appears in the report is what you have configured from the edit configuration step dialog box of each Modbus Steps, and the data read or wrote by the step is also in the report.
The entire configuration of each step can be defined by expression in the pre-expression of a step, for example if you need to configure dynamically some or all parameters of the step. You can access all configuration variables in Step.Configuration container of the step, and these parameters will be put in the report. See tips bellow for example.
|
|
Tip For example, for the Open TCP step, you can configure with a pre-expression the connection name by accessing the variable Step.Configuration.IPAddress with a pre-expression like “Step.Configuration.IPAddress = FileGlobals.Resources.IPAddress ” |
|
|
Tip You can use expression in the pre-expression of a step to configure data to be written by the step from your TestStand variables. For example: for the Write Single Register (F06) step, the step has a Step.Configuration.RegisterValue variable that you can use in the pre-expression of the step to set data at execution. Example of pre-expression: Step.Configuration.RegisterValue = Locals.MyDataToWrite |
In the same way, if a step executes a read operation, the read data are added to the report. All the steps doing a read operation have in the Step.Result container a numeric (array if multiple data) corresponding to the data read in Modbus and a string representation of these data used for the report.
|
|
Tip You can use expression in the post-expression of a step to get data to be read by the step into your TestStand variables. For example: for the Read Input Registers (F04) step, the step has a Step.Result.RegistersValue variable that you can use into the post-expression of the step. Example of post expression: Locals.MyData = Step.Result.RegistersValue |
See Also
