[Feature Request]: Add start conditions for a McePosTable entry about mlx-examples HOT 3 OPEN

About the InterlockFlags of McePosTableIO, should the robot stops on True or False ?

I figured that "True" = "Yes" = "I want interlock".
So True should stop the robot.
And a default False would allow the robot to move.

But we could also consider "True" = "the robot can move".

Which would be the most natural option ?

from mlx-examples.

When runnig McePosTable step by step (nMode = 2), how should-we handle the bStep rising edge ?

Scenario 1:

• Wait for bStep
• If Interlock, then wait
• Resume trajectory

Scenario 2:

• If Interlock then wait
• Wait for Step
• Resume trajectory

Scenario 3:

• Wait for bStep
• If Interlock, then wait
• Wait for bStep
• Resume trajectory

from mlx-examples.

About the InterlockFlags of McePosTableIO, should the robot stops on True or False ?

I figured that "True" = "Yes" = "I want interlock". So True should stop the robot. And a default False would allow the robot to move.

But we could also consider "True" = "the robot can move".

Which would be the most natural option ?

Perhaps we could consider the following naming, which might be less confusing than interlock:

• Io data type
  • input: add Array of n conditions
  • Output: add Array of n missingConditions
• PosTable entry data type
  • add Array of n startConditions

from mlx-examples.