Get involved

Become part of the MeshCore network

Companion and/or Repeater

There are two ways to participate in the MeshCore network: as an active participant with a Companion, or by providing infrastructure with repeaters.

The choice is yours

Decide how you want to participate.

Settings

The 868 MHz frequency band is used.
It can be used without an amateur radio license under certain conditions.

Here in this region, the “EU/UK Narrow” preset is used. This corresponds to the following settings:

Frequency

869.618 MHz – This is the frequency used throughout most of Europe and the United Kingdom.

Bandwidth

62.5 kHz – This is the standard setting used throughout most of Europe and the United Kingdom.

Spreading factor

8 – This is the standard setting used throughout most of Europe and the United Kingdom.

Coding rate

8 – This is the standard setting used throughout most of Europe and the United Kingdom.

Regions and Scopes

MeshCore introduces “region-based scoping” (available from version 1.10.0) to limit packet distribution to specific geographic or logical areas, thereby reducing network congestion in large networks.

The concept of scopes and regions

The concept of regions and scopes is very simple:

Repeaters define the regions for which they are responsible.
Companions are called region scopes.
Scopes can be retrieved from repeaters in the area or entered manually.
In each channel, you can set a scope on the Companion
and thus specify in which region the message should be distributed.
When receiving a message, each repeater looks in the message header to see
whether it should distribute the message to the region defined by the scope.
If it does not know the region, the message is discarded.

Regions are defined using Region CLI commands, enabling localized flooding and targeted messaging. This is essential for scaling networks beyond the capabilities of peer-to-peer systems.

MeshCore regions and areas Main functions

Region definition: Users can create, update, and remove regions such as #MyRegion using the command region put {name} {parent}.
Scope control: The flood scope feature restricts packet transmission to specific regions by using %<scope> or % before the region name (e.g., command%#Region).
Region management: Commands such as region get search for regions, region list displays configured regions, and region save saves these settings.
Allowable flooding: region allowf enables the “flood” (F) permission for specific regions, which is crucial for controlling message propagation, while region denyf removes this permission.
Global scope: The * symbol is used to represent the global or default scope.