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.

Sign up for GitHub

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

Jump to bottom

Do not broadcast rx data that is identified as corrupt in TDoA 3 #31

Closed
krichardsson opened this issue May 30, 2018 · 0 comments
Closed

Do not broadcast rx data that is identified as corrupt in TDoA 3 #31

krichardsson opened this issue May 30, 2018 · 0 comments
Milestone
2018.10

Comments

@krichardsson
Copy link
Contributor

The clock correction logic indicates if the rx time of a packet seems to be good or corrupt. If the RX time seems dodgy, do not include it in the remote anchor data in the next broadcast packet.
The idea is to not forward bad data to the rest of the system.
krichardsson added a commit that referenced this issue May 30, 2018
@krichardsson
#31 Do not broadcast bad RX timestamps
ac61ff1
@ataffanel ataffanel added this to the Next version milestone Oct 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2018.10
Development

No branches or pull requests
2 participants
@krichardsson @ataffanel