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

Precise time sync through BLE mesh. #7331

Closed
hgijeon opened this issue May 3, 2018 · 5 comments
Closed

Precise time sync through BLE mesh. #7331

hgijeon opened this issue May 3, 2018 · 5 comments

Comments

@hgijeon
Copy link

hgijeon commented May 3, 2018

Timer of the devices can be shifted as times goes by.
It would be great if IoT devices are automatically synchronizing time from each other.
Is it possible to keep sub-millisecond precision sync between the devices?

@leodesigner
Copy link

leodesigner commented May 5, 2018

Found related blog post:
https://devzone.nordicsemi.com/b/blog/posts/wireless-timer-synchronization-among-nrf5-devices
In the Bluetooth mesh model specification page 160 'Time and Scenes client model' is a possibility to implement time sync procedure. So it might be the right way.

@raveslave
Copy link

I'd like to get in touch with someone that's got experience implementing similar things that could be up for making this happen.

Except for the sync itself, I believe we need an autonomous handover to ensure stability even if the device acting as master leaves. ref: IEEE 1588 BMC (best master clock)

@carlescufi
Copy link
Member

CC @pabigot

@sslupsky
Copy link
Contributor

sslupsky commented Mar 9, 2020

Could this topic be expanded to encompass time synchronization using methods other than BLE? For instance, NTP, GPS, LoRa, 802.15.4e, RTC, etc?

Also, I just determined that there is no zephyr api to set the system clock. So, for the use case where you boot your device and want to manually set the clock to the local time (or some other arbitrary time), there doesn't appear to be an API for this?

@pabigot pabigot removed their assignment Mar 13, 2020
@github-actions
Copy link

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

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

8 participants