You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello
I have a question regarding the clocks in the high cut.
In the ls bus it says that the output clocks should be periodic or aperiodic.
"The output Clock type, periodic or aperiodic, is defined by the sending FMU. This allows the FMU (or better the exporting tool) to balance the accuracy and performance of its network communication:" [4.2.2. Clock Variables]
This means that they are timebased. But according to the FMI 3 standard, only triggered clocks can be output clocks. See FMI 3 standard [2.2.8.2. Clock Types] . Or am I misunderstanding something in relation to the clocks at Hig Cut?
Thank you very much.
The text was updated successfully, but these errors were encountered:
Pierre: the FMI standard refers to "input" and "output" w.r.t. who does the clock ticking, not w.r.t the information flow
Markus: Can we change "output" to Tx?
Klaus: for high cut we do not have "Tx".
Pierre: We need to have some good name for it in the text. I can try to make a proposal
(Klaus: we have some "implicitely introduced" terms, such as "sending FMU".)
Hello
I have a question regarding the clocks in the high cut.
In the ls bus it says that the output clocks should be periodic or aperiodic.
"The output Clock type, periodic or aperiodic, is defined by the sending FMU. This allows the FMU (or better the exporting tool) to balance the accuracy and performance of its network communication:" [4.2.2. Clock Variables]
This means that they are timebased. But according to the FMI 3 standard, only triggered clocks can be output clocks. See FMI 3 standard [2.2.8.2. Clock Types] . Or am I misunderstanding something in relation to the clocks at Hig Cut?
Thank you very much.
The text was updated successfully, but these errors were encountered: