> 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/boomerang-2-system-administrator-manual/nodes_and_sensors.md).

# Nodes and sensors

A PC node is a unit that delivers measuring data to the Boomerang system. The Boomerang system uses different types of PC nodes. In general they can be divided into two groups, basing on the communication method used, which are network TCP/IP or radio transmission. The only PC Node using radio transmission is PC Node supporting S2 and LCR. All other PC nodes are using TCP/IP network communication.

To add a PC Node select “View – Show PC nodes” from the main menu.

![](https://800956157-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvyGt5xgoAU3kZytuvW1J%2Fuploads%2Fgit-blob-10c4a719b4faeed36b5e9ae48debfc19cb175e57%2Fimage152.png?alt=media)

Right click in the system tree view area and select “Add PC-Node” from the context menu.

A “Choose PC node…” dialog appears.

![](https://800956157-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvyGt5xgoAU3kZytuvW1J%2Fuploads%2Fgit-blob-ac52dc8c4f7aaa5d14a5230ef3cf0d6fffbba59c%2Fimage153.png?alt=media)

Select the type of PC node to install and click OK. This will open PC node settings form. The settings forms for different PC node types are described in details below.


---

# 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/boomerang-2-system-administrator-manual/nodes_and_sensors.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.
