Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[NEW FEATURE] Timestamping management allowing synchronized network, or not. #444

Closed
nicolas-rabault opened this issue Jul 21, 2023 · 0 comments · Fixed by #435
Closed
Assignees
Milestone

Comments

@nicolas-rabault
Copy link
Member

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 the Phy_ComputeMsgTimestamp, instead of computing the differential value we will just return the plain timestamp.

@nicolas-rabault nicolas-rabault added this to the 3.0.0 milestone Jul 21, 2023
@nicolas-rabault nicolas-rabault linked a pull request Sep 18, 2023 that will close this issue
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants