Swiss MeshCore Settings
These are the currently recommended settings to use with any MeshCore nodes in Switzerland. Nothing of this is mandatory, we just believe that this will result in the best performing mesh network and hope that it helps getting a solid experience with MeshCore right from the start.
Every user is responsible himself for his nodes and needs to make sure he is in full compliance with the legal restrictions and compliance given by the Swiss state and specifically the BAKOM.
We have switched over to a LoRa configuration which is summarised / named "Narrow". For more details or if you have any questions, make sure to check out our Swiss MeshCore Community here.
General Settings
These are the settings we recommend to use on all MeshCore nodes, no matter what role they are.
It is extremely important to configure the regions correctly on both repeaters and companion nodes. All details and settings can be found here:
2-Byte – To uniquely identify repeaters, we recommend setting Path Hash Mode to 2-Byte.
On the companion node, you can find this directly in the MeshCore app under Experimental Settings.
On repeaters, you can query and configure it via Remote Management with these commands:
get path.hash.mode
set path.hash.mode 1
Repeaters
These are the additional settings to the "General Settings" above which we recommend to use on all MeshCore Repeater nodes.
There are two settings here for the repeaters to advertise themselves automatically, the Zero-Hop-Advert and the Flood-Advert.
Zero-Hop-Advert: 0 Minutes - Zero means no zero-hop adverts get sent. It's usually not needed since flood adverts already cover this.
Flood-Advert: 49 Hours - To keep the traffic on the mesh low, we recommend to set this to an absolute minimum of 24 hours, 49 hours is even better.
10 – With release 1.15.0, the duty cycle was implemented correctly. To comply with the maximum allowed legal limit of 10% on the 869.618 MHz frequency we use, it is essential to configure it correctly:
get dutycycle
set dutycycle 10
0.5 Seconds - Local repeaters with short range (personal repeaters, balcony, rooftop, etc.)
1.0 Seconds - Repeaters with medium range (regional repeaters, high-rise, hills, etc.)
2.0 Seconds - Backbone repeaters with long range (mountain peaks, towers, etc.)
get txdelay
set txdelay 1.0
Repeaters will eventually be picked up by the automatic map-updater we have running and get automatically added to the map if they are within range.
Room Servers
These are the additional settings to the "General Settings" above which we recommend to use on all MeshCore Room Server nodes.
There are two settings here for the room servers to advertise themselves automatically, the Zero-Hop-Advert and the Flood-Advert.
Zero-Hop-Advert: 0 Minutes - Zero means no zero-hop adverts get sent. It's usually not needed since flood adverts already cover this.
Flood-Advert: 49 Hours - To keep the traffic on the mesh low, we recommend to set this to an absolute minimum of 24 hours, 49 hours is even better.
10 – With release 1.15.0, the duty cycle was implemented correctly. To comply with the maximum allowed legal limit of 10% on the 869.618 MHz frequency we use, it is essential to configure it correctly:
get dutycycle
set dutycycle 10
0.5 Seconds - Local repeaters with short range (personal repeaters, balcony, rooftop, etc.)
1.0 Seconds - Repeaters with medium range (regional repeaters, high-rise, hills, etc.)
2.0 Seconds - Backbone repeaters with long range (mountain peaks, towers, etc.)
get txdelay
set txdelay 1.0