> For the complete documentation index, see [llms.txt](https://sdk.twelite.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sdk.twelite.info/en/twelite-net-api-expl/nettowkunitsuite/netto-1.md).

# RelayNet

TWELITE NET has a LayerTree network as a relay network.

A LayerTree network is a relay network designed for efficient upstream delivery. LayerTree\_mininodes, which are solely for transmission, are also part of the LayerTree network.

## Basic principles

* There is only one parent unit and all communication is centralised in the parent unit.
* As a general rule, the direction of delivery is from the end node to the upper level and finally to the parent machine.
  * Downward delivery from the parent unit is by broadcast communication.
  * Communication between sub-units and repeaters is only possible after delivery to the parent unit.
  * However, it is possible to send directly between nodes that are within radio range by specifying their addresses.
* The transponder predetermines its own number of levels.
* Connect to a repeater within radio range that is higher in the hierarchy than your own (the repeater with the lower hierarchy number).
* By using LayerTree Mininodes, which do not have a destination repeater but only transmit, they can act as sensor nodes with very low battery consumption. (App\_Tag)

![](/files/-LCXu_-U5HGL9oUdRssx)

(RED) : Parent node

(YELLOW `n`) : Child node which can relay. (`n` represents number of layer)

(Blue) : Child node which can work with sleeping.

## About layers

The parent machine is numbered 0 and can number its layers up to 63.

![](/files/-LCXwAmtt8qKqGN_USgU)

It is OK to skip numbers as long as they are in ascending order.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sdk.twelite.info/en/twelite-net-api-expl/nettowkunitsuite/netto-1.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.