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

Regularly store real time and real time offset #222

Open
Tracked by #199
PatrickKa opened this issue Dec 18, 2023 · 0 comments
Open
Tracked by #199

Regularly store real time and real time offset #222

PatrickKa opened this issue Dec 18, 2023 · 0 comments

Comments

@PatrickKa
Copy link
Contributor

PatrickKa commented Dec 18, 2023

Description

Every 10 s or something, the real time offset is read from the persistent state and published. After that, the current real time is saved to the persistent state. This tries to mitigate the loss of real time information after a reset of the COBC. What makes all of this tricky is that the function for updating the real time estimation also wants to change the time offset (see #223). A topic can, however, only have a single publisher. Maybe there is some other Rodos construct that is better suited for this.

Edit: As I already wrote in #199, I don't think that we need a topic or a separate thread. We just need to make sure that the real time offset and the estimated real time are stored regularly as persistent variables. This could be done in the telemetry thread, which needs to touch all persistent variables anyway.

@PatrickKa PatrickKa changed the title Add real time thread Regularly store real time and real time offset Aug 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant