All of the command parameters on DUT_MotionStage are currently left at their existing values after a reset. This can be confusing and it can also allow other bugs to surface in a dangerous way e.g. if there is other code that is trying to force bExecute to TRUE and enabling another move to the same bad position.
Here are all the proposed parameter default/reset value combinations:
nCommand := 3 (absolute move)
nCmdData := 0 (no data)
fPosition := current position
fVelocity := minimum of configured manual slow velocity, configured max velocity
All of the command parameters on
DUT_MotionStage
are currently left at their existing values after a reset. This can be confusing and it can also allow other bugs to surface in a dangerous way e.g. if there is other code that is trying to forcebExecute
toTRUE
and enabling another move to the same bad position.Here are all the proposed parameter default/reset value combinations:
nCommand
:= 3 (absolute move)nCmdData
:= 0 (no data)fPosition
:= current positionfVelocity
:= minimum of configured manual slow velocity, configured max velocity