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
Luos engine have been made for simple microcontrollers. Since version 3.0.0, Luos have been unleashed and able to run anywhere and use any network.
Historically to manage timestamping Luos was considering that no synchronization was available among the nodes. This is not true anymore because some advanced network can rely on time synchronization.
Describe the expected behavior of the feature
To be able to benefits from these synchronized network we have to be able to remove the latency based timestamping and use a plain date instead. This need to be a phy choice depending on it's capabilities.
this will be a boolean value stored in the luos_phy_t struct. This boolean will change the behavior of the Phy_ComputeMsgTimestamp, instead of computing the differential value we will just return the plain timestamp.
The text was updated successfully, but these errors were encountered:
Details
Luos engine have been made for simple microcontrollers. Since version 3.0.0, Luos have been unleashed and able to run anywhere and use any network.
Historically to manage timestamping Luos was considering that no synchronization was available among the nodes. This is not true anymore because some advanced network can rely on time synchronization.
Describe the expected behavior of the feature
To be able to benefits from these synchronized network we have to be able to remove the latency based timestamping and use a plain date instead. This need to be a phy choice depending on it's capabilities.
this will be a boolean value stored in the
luos_phy_t
struct. This boolean will change the behavior of thePhy_ComputeMsgTimestamp
, instead of computing the differential value we will just return the plain timestamp.The text was updated successfully, but these errors were encountered: