> 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/menu_-_administration/application_settings_-_transmission_groups.md).
# Application settings… - Transmission groups
Normally, the requests for measurements sent over radio using S2 PC nodes are transmitted one after the other. For big systems, with multiple radio PC nodes and many radio sensor nodes the whole polling procedure may take long time to perform, and to shorten that time, transmission groups can be used.
If transmission groups are enabled, the system may send radio requests via its radio PC nodes in parallel so radio nets from separate groups are polled at the same time.
This function can only be used if radio nodes from the separate groups are set in such a way that their radio nets don’t interfere over radio.
To enable the transmission groups select ‘Enable’ box.
## Create/edit transmission groups.
Click ‘New group…’, enter group name and click OK. To edit select the group and click ‘Edit…’.
## Assigning radio PC nodes to transmission groups
After the groups are created, drag the PC nodes to the groups of your choice. Please remember the PC nodes which may interfere over radio must be in the same group.
Click ‘Apply’ and sign to save the new settings.
Please note you have to restart the Boomerang service on the server to apply the changes.
---
# 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/menu_-_administration/application_settings_-_transmission_groups.md?ask=&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.