When nSmPosTable jumps from a motion state (10 to 29) to state 99 because of an error (Sts_ER on any FB), FB's enable input suddenly goes to False without clearing MLX.InternalData.WritePacket.CommandRequest.
Expected behavior
Transition to state 99 should keep the previous aEnable signals untouched.
So still enabled FB can end their process as usual.
PosTable version
v0.3.0
Current behavior
When
nSmPosTable
jumps from a motion state (10 to 29) to state 99 because of an error (Sts_ER
on any FB), FB'senable
input suddenly goes toFalse
without clearingMLX.InternalData.WritePacket.CommandRequest
.Expected behavior
Transition to state 99 should keep the previous
aEnable
signals untouched. So still enabled FB can end their process as usual.