> 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/uart.md).

# UART

The UART connector is used to connect the node to B2 server or S2GW when the node is used as a PC node.

In case of a measuring S2 node, it is used as an interface to S2 S2IOG2 module, incubators and some other sensor types handled by the S2 family. The details can be found in [S2 node types](https://help.boomerang3.com/s2-radio-system-manual/s2-system-description/s2-node/s2-node-types.md).

## UART settings

| Parameter  | Value |
| ---------- | ----- |
| Bit rate:  | 9600  |
| Data bits: | 8     |
| Stop bit:  | 1     |
| Parity:    | Even  |

## &#x20;Connector

The connector type is modular socket 4/4.

<figure><img src="https://196065439-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDnSLeSlKbF06gUExzr9m%2Fuploads%2FjB90dpcbQEIsz5mpEfSG%2Fimage.png?alt=media&amp;token=fafc1a74-b56f-48a8-92b6-33a4174bed74" alt="" width="197"><figcaption></figcaption></figure>

| Pin number | Signal              |
| ---------- | ------------------- |
| 1          | GND                 |
| 2          | RXD, RS-232C levels |
| 3          | TXD, RS-232C levels |
| 4          | GND                 |


---

# 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/uart.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.
