Skip to content

Move nanosec docs from legacy #55

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

Open
eiriksm wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Move nanosec docs from legacy #55

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/en/docs/watchfaces/nanosec.md → content/en/docs/using/nanosec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: "Calibration with Nanosec"
linkTitle: "Calibration with Nanosec"
weight: 8
weight: 120
---

You can include the Finetune and Nanosec faces in your Sensor Watch firmware to achieve exceptionally high accuracy within 10 seconds per year.
Expand Down Expand Up @@ -152,4 +152,4 @@ This is what the various correction profiles do.

**P3**: Like P2, both static and dynamic correction, but using an empirically measured cubic formula.

**P4**: Custom settings for a specific crystal, using values that you can edit in the source code. You need to determine these values yourself; your crystal is unlikely to match what you find in the source code.
**P4**: Custom settings for a specific crystal, using values that you can edit in the source code. You need to determine these values yourself; your crystal is unlikely to match what you find in the source code.