Skip to content

Migration of the optional SteadyState phase in OSC 1.X SyncronizeAction

The current migration example of the SynchronizeAction was probably designed for OSC 1.0. From OSC v1.1 it is possible to specify a final "steady state" phase for the controlled entity.

  • Example 1: Reach final speed 10 meters from the destination.
  • Example 2: Reach final speed 3 seconds before arrival to the destination.

Todo:

  1. Identify or create a mapping of the 1.X steady state
  2. Update the migration guideline and potentially the 2.X standard

(Clarification regarding steady state: Since the action entity can't be controlled during the (optional) final steady state, the synchronization might be slightly off in the end. I.e. the action entity might be either a bit early or late compared to the monitored entity which might change speed during this final phase. Conclusion being that steady state should be kept to a minimum needed.)