> 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/s2-radio-system-manual/s2-system-description/s2-node/s2-communication-protocol/frame.md).

# Frame

The frame has one or two parts depending on command name header and data.&#x20;

Nodes discard frames longer then 64 bytes.

&#x20;There are UART commands and Radio commands. The UART commands do not result in any radio communication and are handled inside the PC node only. The Radio commands cause radio transmission and the answer from PC node depends on the radio communication result.

Example of UART command frame

| 1      | 2       | 3       | 4   | 5  | 6   | 7    | 8    | 9   |
| ------ | ------- | ------- | --- | -- | --- | ---- | ---- | --- |
| Length | ID Info | Command | GRP | ID | CRC | Data | Data | CRC |
| 09     | 00      | 10      | 01  | 01 | CRC | GRP  | ID   | CRC |

&#x20;

Example of Radio command frame

| 1      | 2       | 3       | 4   | 5  | 6     | 7   | 8      | 9      | 10  |
| ------ | ------- | ------- | --- | -- | ----- | --- | ------ | ------ | --- |
| Length | ID Info | Command | GRP | ID | To ID | CRC | Data   | Data   | CRC |
| 0A     | 11      | 35      | 01  | 01 | 02    | CRC | CAL\_V | CAL\_V | CRC |

### 1.1      Header


---

# 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/s2-radio-system-manual/s2-system-description/s2-node/s2-communication-protocol/frame.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.
