> For the complete documentation index, see [llms.txt](https://support.onegiantleap.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.onegiantleap.co.nz/legacy-features/gps-sync-box.md). # GPS Sync Box ## For what length of time will the sync remain valid? Located inside every power meter is a Real Time Clock (RTC) which accurately keeps tracks of Coordinated Universal Time (UTC) since the last sync took place with a GPS Sync Box. The RTC is accurate to ±0.432 Second/Day over the entire temperature range from -45°C to +85°C. In other words, the RTC will drift no more than ±0.432 over the course of 24 hours, even if the temperature varies significantly throughout the day. We have defined it such that a sync will be considered expired if 6 hours or more have elapsed since that sync occurred. This equates to a worse case drift of ±0.108 seconds which closely lines up with the 100Hz High Speed Data sampling period of 0.100 seconds. ## How often will the power meter search for a sync? Searching for an active GPS Sync Box consumes power, so we want to limit the time the power meter spends searching for one.\ \ If the power doesn't currently have a valid sync, then it will start search more frequently - more specifically, the power meter will begin a short search (for 5 seconds) every 60 seconds. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://support.onegiantleap.co.nz/legacy-features/gps-sync-box.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.