Skip to content

Commit 18d7a24

Browse files
author
Daniel Becker
committed
add note to change enum
Signed-off-by: Daniel Becker <[email protected]>
1 parent 421f02b commit 18d7a24

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

doc/spec/motion_request_inputs.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,6 @@ OSMPMotionRequestIn
2424
* Each motion request input shall be defined as a notional discrete binary input variable with `@causality="input"` and `@variability="discrete"`.
2525
* The MIME type of the variable shall specify the `type=MotionRequest` as part of the MIME type parameters.
2626
* Motion request data shall be encoded as `osi3::MotionRequest`.
27-
* The motion request passed to the FMU must contain one of the available ``OutputOptions``. In addition to the enumerator, the corresponding ``DesiredState`` or ``Trajectory`` has to be set, respectively.
27+
* The motion request passed to the FMU must contain one of the available ``OutputOptions`` (**rename**). In addition to the enumerator, the corresponding ``DesiredState`` or ``Trajectory`` has to be set, respectively.
2828
* The guaranteed lifetime of the motion request protocol-buffer pointer provided as input to the FMU shall be from the time of the call to `fmi2SetInteger` that provides those values until the end of the following `fmi2DoStep` call.
2929

doc/spec/motion_request_outputs.adoc

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -18,12 +18,12 @@ OSMPMotionRequestOut
1818

1919
**Rules**
2020

21-
* If only one motion request input is configured, the prefix shall only be `OSMPMotionRequestOut`.
22-
* If more than one motion request input is configured, the prefix shall be extended by an array index, for example, `OSMPMotionRequestOut[1]` and `OSMPMotionRequestOut[2]`.
21+
* If only one motion request output is configured, the prefix shall only be `OSMPMotionRequestOut`.
22+
* If more than one motion request output is configured, the prefix shall be extended by an array index, for example, `OSMPMotionRequestOut[1]` and `OSMPMotionRequestOut[2]`.
2323
* Array indices shall start at 1 and shall be consecutive.
24-
* Each motion request input shall be defined as a notional discrete binary input variable with `@causality="input"` and `@variability="discrete"`.
24+
* Each motion request output shall be defined as a notional discrete binary output variable with `@causality="output"` and `@variability="discrete"`.
2525
* The MIME type of the variable shall specify the `type=MotionRequest` as part of the MIME type parameters.
2626
* Motion request data shall be encoded as `osi3::MotionRequest`.
27-
* The motion request passed to the FMU must contain one of the available ``OutputOptions``. In addition to the enumerator, the corresponding ``DesiredState`` or ``Trajectory`` has to be set, respectively.
28-
* The guaranteed lifetime of the motion request protocol-buffer pointer provided as input to the FMU shall be from the time of the call to `fmi2SetInteger` that provides those values until the end of the following `fmi2DoStep` call.
27+
* The motion request passed to the FMU must contain one of the available ``OutputOptions`` (**rename**). In addition to the enumerator, the corresponding ``DesiredState`` or ``Trajectory`` has to be set, respectively.
28+
* The guaranteed lifetime of the motion request protocol-buffer pointer provided as output to the FMU shall be from the time of the call to `fmi2SetInteger` that provides those values until the end of the following `fmi2DoStep` call.
2929

0 commit comments

Comments
 (0)