mirror of
https://github.com/meshtastic/meshtastic.git
synced 2024-11-09 23:24:10 -08:00
Merge pull request #1382 from pdxlocations/role-images
This commit is contained in:
commit
b585b0873f
|
@ -15,6 +15,9 @@ It is strongly recommended to keep your [ROLE](/docs/configuration/radio/device#
|
||||||
- `CLIENT` nodes efficiently repeat and route packets as needed.
|
- `CLIENT` nodes efficiently repeat and route packets as needed.
|
||||||
- They use smart delays for rebroadcasting, improving network stability.
|
- They use smart delays for rebroadcasting, improving network stability.
|
||||||
|
|
||||||
|
![Client Node Example](/img/configuration/client.webp)
|
||||||
|
*One example of a 'Client' node. Photo credit: Cully@KBOXLABS*
|
||||||
|
|
||||||
### Avoid `ROUTER`and `REPEATER`
|
### Avoid `ROUTER`and `REPEATER`
|
||||||
|
|
||||||
Using `ROUTER` or `REPEATER` roles unnecessarily can cause serious network issues:
|
Using `ROUTER` or `REPEATER` roles unnecessarily can cause serious network issues:
|
||||||
|
@ -27,6 +30,9 @@ These roles are for very specific applications. Before changing from `CLIENT`, c
|
||||||
|
|
||||||
Remember: A network of `CLIENT` nodes with a small number of well-placed `ROUTERS` is usually the most efficient and stable configuration.
|
Remember: A network of `CLIENT` nodes with a small number of well-placed `ROUTERS` is usually the most efficient and stable configuration.
|
||||||
|
|
||||||
|
![Router Node Example](/img/configuration/router.webp)
|
||||||
|
*One example of a 'Router' node. Photo credit: Cully@KBOXLABS*
|
||||||
|
|
||||||
## (Not) Sharing Your Location
|
## (Not) Sharing Your Location
|
||||||
|
|
||||||
Telemetry is shared over your [PRIMARY channel](/docs/configuration/radio/channels#role). This means that if your node has acquired GPS coordinates from an integrated GPS chip, or from your mobile device, your coordinates will be sent to the mesh over this channel, using it's defined encryption (if any).
|
Telemetry is shared over your [PRIMARY channel](/docs/configuration/radio/channels#role). This means that if your node has acquired GPS coordinates from an integrated GPS chip, or from your mobile device, your coordinates will be sent to the mesh over this channel, using it's defined encryption (if any).
|
||||||
|
@ -70,6 +76,8 @@ If you would like your nodes to include/expand the "public" mesh, you must use t
|
||||||
|
|
||||||
It is **strongly** recommended to leave your [MAX HOPS](/docs/configuration/radio/lora#max-hops) set to 3 unless you're sure you need more (or less) to reach your destination node. Unnecessarily high hop counts often lead to network issues.
|
It is **strongly** recommended to leave your [MAX HOPS](/docs/configuration/radio/lora#max-hops) set to 3 unless you're sure you need more (or less) to reach your destination node. Unnecessarily high hop counts often lead to network issues.
|
||||||
|
|
||||||
|
![Hop Count Image](/img/configuration/max-hops.webp)
|
||||||
|
|
||||||
## Chat Channels and LoRa Frequency Slots
|
## Chat Channels and LoRa Frequency Slots
|
||||||
|
|
||||||
Previously, Meshtastic used the word "channels" to define two different configuration properties: Messaging Channels & LoRa Channel Numbers. However, this could lead to confusion since "channels" was being used to refer to two distinct concepts. To clarify the distinction, the decision was made to change "LoRa Channel Number" to "LoRa Frequency Slot".
|
Previously, Meshtastic used the word "channels" to define two different configuration properties: Messaging Channels & LoRa Channel Numbers. However, this could lead to confusion since "channels" was being used to refer to two distinct concepts. To clarify the distinction, the decision was made to change "LoRa Channel Number" to "LoRa Frequency Slot".
|
||||||
|
|
BIN
static/img/configuration/client.webp
Normal file
BIN
static/img/configuration/client.webp
Normal file
Binary file not shown.
After Width: | Height: | Size: 140 KiB |
BIN
static/img/configuration/router.webp
Normal file
BIN
static/img/configuration/router.webp
Normal file
Binary file not shown.
After Width: | Height: | Size: 155 KiB |
Loading…
Reference in a new issue