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

Time sync in two cFS in different processors? #35

Open
jongyeob opened this issue Sep 22, 2020 · 2 comments
Open

Time sync in two cFS in different processors? #35

jongyeob opened this issue Sep 22, 2020 · 2 comments

Comments

@jongyeob
Copy link

Hello,

One of cFS is a time server and the other is a time client.
They are connected by SBN.

Can the server deliver the time tone message to the client?
Can the client synchronize its own time to the server time tone?

I want to make sure this can be a possible scenario.

Thanks,
JY

@CDKnightNASA
Copy link
Contributor

With a low frequency (like 1hz) you could send tone messages over SBN, but most SBN protocols are non-deterministic and you'll end up with latency even with deterministic protocols as other traffic goes through the same pipes. You'll probably want to use a separate path/architecture for time synchronization.

@skliper
Copy link

skliper commented Sep 22, 2020

The "tone" is typically a pulse on a serial line or similar sent by the server, which the client processes with an interrupt (records what it thinks is current time). Then the "time at tone message" is sent by the server in a CCSDS message over whatever interface is appropriate (sounds like SBN in your case, but could be CI or any other way to publish on the client SB). When the "time at tone message" is received the client would typically correct it's current understanding of time based on the difference between the "time at tone message" and the time it recorded when the "tone" was sensed. There's a decent amount of complexity in the details of this process (could be a "time will be" at the next tone message vs "time was" at the last message, there's internal correction factors to handle tone latencies, there's gradual time correction vs immediate step, etc) but this is the general concept.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants