Clarification for EnableXcpOn

Clarification about changing variables org.fmi_standard.fmi_ls_xcp.EnableXcpOn[Tcp|Udp]Ip #47
modelica · May 14, 2024 · 9535f7e · 9535f7e
1 parent 4e2eea0
commit 9535f7e
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/index.adoc b/docs/index.adoc
@@ -395,7 +395,7 @@ The configuration variables are duplicated for both transport layers, TCP and UD
 The FMU shall only provide the corresponding variables for the protocols it supports.
 
 Without knowing the concrete XCP slave implementation the importer cannot know if the different protocols can be used in parallel or only exclusively.
-In the case the XCP service is not multi-session capable and both of the variables `org.fmi_standard.fmi_ls_xcp.EnableXcpOn[Tcp|Udp]Ip` are set to `true`, the FMU must return an error in the corresponding setter function and provide a meaningful error message.
+In the case the XCP service is not multi-session capable and both of the variables `org.fmi_standard.fmi_ls_xcp.EnableXcpOn[Tcp|Udp]Ip` are set to `true`, the FMU must return an error in the corresponding setter function and provide a meaningful error message when exiting `Configuration Mode`.
 This information may also be provided in the `documentation` directory inside the FMU.
 
 The importer of an FMU is responsible for keeping all occurrences of the port number consistent, i.e., in both the FMU configuration and in the A2L file.