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

[uxrce_dds_client] RTT too high for timesync #22382

Closed
dakejahl opened this issue Nov 16, 2023 · 3 comments
Closed

[uxrce_dds_client] RTT too high for timesync #22382

dakejahl opened this issue Nov 16, 2023 · 3 comments

Comments

@dakejahl
Copy link
Contributor

Describe the bug

Just updated to main and now I am seeing this message every 3.5 seconds on the dot.

WARN  [timesync] RTT too high for timesync: 24 ms

I'm running the bridge on serial at 921600.

To Reproduce

Flash main

Expected behavior

No periodic warnings

Screenshot / Media

WARN [timesync] RTT too high for timesync: 18 ms
WARN [timesync] RTT too high for timesync: 18 ms
WARN [timesync] RTT too high for timesync: 24 ms
WARN [timesync] RTT too high for timesync: 24 ms
WARN [timesync] RTT too high for timesync: 23 ms
WARN [timesync] RTT too high for timesync: 18 ms
WARN [timesync] RTT too high for timesync: 19 ms
WARN [timesync] RTT too high for timesync: 18 ms
WARN [timesync] RTT too high for timesync: 19 ms
WARN [timesync] RTT too high for timesync: 19 ms
WARN [timesync] RTT too high for timesync: 18 ms
WARN [timesync] RTT too high for timesync: 19 ms
WARN [timesync] RTT too high for timesync: 22 ms
WARN [timesync] RTT too high for timesync: 18 ms
WARN [timesync] RTT too high for timesync: 22 ms
WARN [timesync] RTT too high for timesync: 28 ms
WARN [timesync] RTT too high for timesync: 18 ms
WARN [timesync] RTT too high for timesync: 14 ms
WARN [timesync] RTT too high for timesync: 23 ms

Flight Log

no log

Software Version

main

Flight controller

ark_fmu-v6x_default

Vehicle type

None

How are the different components wired up (including port information)

No response

Additional context

No response

@dakejahl
Copy link
Contributor Author

Might be related to #22399

@tstastny
Copy link

@bkueng

@beniaminopozzan
Copy link
Member

@dakejahl , you are right.

The issue was introduced by #22302 and it is now being investigated in #22399

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

3 participants