@madielfilho had constructed an example in RoboChart where in the definition of a Controller (ControllerDef) an input event of the controller is connected to a state machine reference (StateMachineRef) and the conection is marked as asynchronous. My understanding is that this attribute plays no role on such connections between controller and state machine. In the RoboChart semantics indeed there is no special treatment for the attribute -- it's just renaming. And similarly, in RoboSim this information is passed throuhg via registerRead/registerWrite as appropriate in either direction. However, there is no WFC ruling use of this attribute in this case.
@madielfilho had constructed an example in RoboChart where in the definition of a Controller (ControllerDef) an input event of the controller is connected to a state machine reference (StateMachineRef) and the conection is marked as asynchronous. My understanding is that this attribute plays no role on such connections between controller and state machine. In the RoboChart semantics indeed there is no special treatment for the attribute -- it's just renaming. And similarly, in RoboSim this information is passed throuhg via registerRead/registerWrite as appropriate in either direction. However, there is no WFC ruling use of this attribute in this case.