> For the complete documentation index, see [llms.txt](https://docs.holybro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.holybro.com/radio/microhard-radio/point-to-multipoint-setup-with-microhard-radio.md).
# Point-to-Multipoint Setup with Microhard Radio
## Sample Wiring Diagram
{% hint style="info" %}
Note that the above Diagram shows RTK connection, but the telemetry connections apply to normal GPS as well.
{% endhint %}
## Point to Multipoint Connection Using Microhard Radio
### Telemetry Radio Setup
First, Select one of the Radios as the Master, and the other Radios as the Remote. Use the [Pico configurator](/radio/microhard-radio/download.md) to set the Master to PMP Master mode, and change the baud rate to 57600. As shown in the figure below:
1. Select PMP Master
2. Click Default Unit
3. Select 57600 baud rate
4. Click PGM/Save.
Pico Configuator - Master
Then, set all the Remote Radios to PMP Remote mode, and change the baud rate to 57600. As shown below:
1. Select PMP Remote
2. Click Default Unit
3. Confirm that the Network Address is consistent with the Master
4. Set a unique Unit Address different for each Remote Radio.
5. Select 57600 baud rate
6. Click PGM/Save.
Pico Configuator - Remote
### Flight Controller Settings
Connect the flight controller via USB and set an ID for each flight controller that is different from other flight controllers.
**For PX4 firmware**, the MAV\_SYS\_ID parameter should be set
**For Ardupilot firmware**, the SYSID\_THISMAV parameter should be set
Use the Master Radio to connect to the ground station (QGC/MissionPlanner), and the Remote Radio to connect to the flight controllers. \
\
If using RTK system, wait for the Base Survey-in to distribute the RTCM data of a Base to multiple Rover after powering on.
---
# 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://docs.holybro.com/radio/microhard-radio/point-to-multipoint-setup-with-microhard-radio.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.
