From 0ad42d84e23fb0ec7054df1a2faba34ffd801a81 Mon Sep 17 00:00:00 2001 From: Benedikt Menne Date: Wed, 22 Jan 2025 15:19:17 +0100 Subject: [PATCH] Small fixes --- docs/2____common_concepts.adoc | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/2____common_concepts.adoc b/docs/2____common_concepts.adoc index 8880f74c..136835e2 100644 --- a/docs/2____common_concepts.adoc +++ b/docs/2____common_concepts.adoc @@ -7,11 +7,10 @@ FMUs may choose to only support one abstraction layer providing only the corresp However, for versatility, having FMUs capable of communicating on both abstraction layers is more convenient for users. In both the Physical Signal Abstraction and the Network Abstraction layer, the exchange of network data takes place via FMI variables. -In the case of the Physical Signal Abstraction, a separate FMI variable of the respective type is created for each network signal in a frame. -The network signals are structured via the PDU and frame hierarchy by using FMI 3.0 Terminals. +In the case of the Physical Signal Abstraction, a separate FMI variable of the respective type is created for each network signal to transfer. +The network signals are structured via a PDU and frame hierarchy by using FMI 3.0 Terminals. Within the Network Abstraction, the bus is simulated using a separate, bus-specific protocol. -This protocol is exchanged between the various network FMUs using binary FMI variables. - +This protocol is exchanged between the various FMUs using binary FMI variables. Since network communication is not continuous but time discrete, FMI 3.0 Clocks are used to indicate when network data is sent or received. While the values and semantic of the Clock variables are clear, the binary frame variables are opaque to the importer but have internal structure to implement the transport mechanism of the specific network technology.