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

setclock doesn't get time messages #243

Open
Nanoseb opened this issue May 13, 2018 · 1 comment
Open

setclock doesn't get time messages #243

Nanoseb opened this issue May 13, 2018 · 1 comment
Labels
bug lowlevel
Milestone
WRSC 2018

Comments

@Nanoseb
Copy link
Member

Nanoseb commented May 13, 2018

Setting the clock via GPS with setclock doesn't seems to work if the node was run before. We just waited for a while and it didn't found any time message (we had a gps fix). Maybe the time messages is turned off via the ublox messages we send when running the gps node.
I think the best way to do that would be to activate time messages at the beginning of setclock.
@Nanoseb Nanoseb changed the title setclock fails when ros have been launched before setclock doesn't get time messages May 13, 2018
@Nanoseb
Copy link
Member Author

Nanoseb commented May 13, 2018

after reading the code it seems that time messages are already being activated at the beginning of setclock. So something else happened or we just didn't wait for long enough.

@Nanoseb Nanoseb added this to the WRSC 2018 milestone May 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug lowlevel
Projects
None yet
Milestone
WRSC 2018
Development

No branches or pull requests
1 participant
@Nanoseb