> For the complete documentation index, see [llms.txt](https://docs.influxtechnology.com/support_guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.influxtechnology.com/support_guides/k-series-product-manual/k-series-product-manual/k-box-product-manual/configuring-the-k-box/using-the-k-cal-software/configuring-the-digital-channels/cycle-duration-measurement.md).

# Cycle Duration Measurement

To measure the duration of a cycle, select Cycle Duration in the drop-down box:

<figure><img src="https://1039220062-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRhWtYvkHNZy7Jvdnc3wk%2Fuploads%2FQdCKCY0TIK7zCUgoKB2m%2Fimage.png?alt=media&amp;token=4fbaf690-37d4-4fa4-9ae8-2fff4b852cc6" alt=""><figcaption></figcaption></figure>

Frequency can then be calculated using the following formula:

#### F = 1 / T

In this case, this frequency is NOT average frequency. It is instantaneous frequency.

The KBox will wait until the cycle measurement is finished before sending a CAN message with the duration. If the cycle duration is long, the messages may be sent slower than the selected Rate.   &#x20;

If the Cycle duration is shorter than the time between messages set by the Rate, the duration will be re-calculated before being sent.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.influxtechnology.com/support_guides/k-series-product-manual/k-series-product-manual/k-box-product-manual/configuring-the-k-box/using-the-k-cal-software/configuring-the-digital-channels/cycle-duration-measurement.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
