Skip to content

Commit

Permalink
Small fixes
Browse files Browse the repository at this point in the history
  • Loading branch information
Benedikt Menne authored and Benedikt Menne committed Jan 22, 2025
1 parent e4a8d96 commit 0ad42d8
Showing 1 changed file with 3 additions and 4 deletions.
7 changes: 3 additions & 4 deletions docs/2____common_concepts.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down

0 comments on commit 0ad42d8

Please sign in to comment.