> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/win-gateway-installation-manual/node-information/sensor-read-period.md).

# Sensor Read Period

The SensorReadPeriod field defines the node logging interval.

<figure><img src="https://2429681196-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0vLm0km8knyJJgcLOzxB%2Fuploads%2FDGcLUqInLOCfSaBDcpUw%2Fimage.png?alt=media&amp;token=a6adc0dc-f745-4cef-ab0d-51fe274583ab" alt=""><figcaption></figcaption></figure>

This value can be set from the gateway interface, but please remember that Boomerang will not be in sync with this setting and will overwrite it with its own value if this is changed in Boomerang.&#x20;

| Value | Log interval |
| ----- | ------------ |
| 0     | 5 sec        |
| 1     | 10 sec       |
| 2     | 15 sec       |
| 3     | 30 sec       |
| 4     | 1 min        |
| 5     | 2 min        |
| 6     | 5 min        |
| 7     | 10 min       |
| 8     | 15 min       |
| 9     | 30 min       |
| 10    | 1 hour       |

&#x20;

The shortest log interval in Boomerang is 1 minute (value = 4).&#x20;

A node can be set temporarily to 15 or 30 seconds for RSSI measurements or other tests, but such settings must not be used in normal operation.

To set the SensorReadPeriod click on the “Write” button on that row, enter the new value, and click “Ok”. The value will be updated the next time the node communicates with the gateway.


---

# 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://help.boomerang3.com/win-gateway-installation-manual/node-information/sensor-read-period.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.
