limit steps

[dht]

Hi , I'm using TS 3.1 and LV7.1 .
I have a VI which reads the value of step.limits.low and step.limits.high via the sequencer context and get properties methods.

This vi is called by a numeric limit step type within a flow ( loop) step in TS, the values of step.limits.low and step.limits.high are forced to different values within the loop.

The Edit Limits TAB has this entered in the data source window:
Step.Limits.Low = Locals.TempWindowLow ,Step.Limits.High = Locals.TempWindowHigh
the locals being defined in a Fx step previous.

The problem I have is that the VI gets the default test limits ( ie the relevant fixed ones ) on the first iteration of the loop, and is subsequently one behind on later iterations.However the report shows that the limits are correct by the time the results comparism in TS takes place.

So the issue is probably in the order at which things happen when calling the vi, the Step.Limits.Low being evaluated after the properties have been sent to the VI.

Has anyone any experience of this, and possible work arounds?.
thanks dht

[James_Grey]

For a numeric limit step, the data source expression gets evaluated as part of the status expression, thus, as you saw, it happens after the module is called. Move your limit initialization expression to the PreExpression on the Expressions tab of the step properties dialog box.