mirror of
https://github.com/meshtastic/meshtastic.git
synced 2025-03-05 21:00:08 -08:00
Merge branch 'master' into i18n
This commit is contained in:
commit
2380fb98f2
|
@ -27,8 +27,8 @@ Minimum requirement is Android 5 (Lollipop 2014, first BLE support), however And
|
||||||
|
|
||||||
- Empty Cloud - Queued on the app to be sent to your device.
|
- Empty Cloud - Queued on the app to be sent to your device.
|
||||||
- Up Arrow - Queued on the device to be sent over the mesh.
|
- Up Arrow - Queued on the device to be sent over the mesh.
|
||||||
- Check Mark - Delivered over the mesh.
|
- Check Mark - At least one other device on the mesh confirmed it received the message.
|
||||||
- Cross Mark - Error.
|
- Cross Mark - No confirmation was received after the default three retransmissions.
|
||||||
|
|
||||||
### How can I clear the message history?
|
### How can I clear the message history?
|
||||||
|
|
||||||
|
@ -96,6 +96,10 @@ Hold down the left PWR button for about 10 seconds and the display should turn o
|
||||||
|
|
||||||
Push the left PWR button for about 1 second.
|
Push the left PWR button for about 1 second.
|
||||||
|
|
||||||
|
### Functionality of the T-Beam Buttons ###
|
||||||
|
|
||||||
|
[T-Beam Buttons](/docs/hardware/devices/tbeam/buttons) explained here
|
||||||
|
|
||||||
### Where do I purchase the device hardware?
|
### Where do I purchase the device hardware?
|
||||||
|
|
||||||
Each [supported device](/docs/hardware/devices/tbeam) has a "Purchase Link".
|
Each [supported device](/docs/hardware/devices/tbeam) has a "Purchase Link".
|
||||||
|
|
|
@ -7,8 +7,8 @@ sidebar_position: 2
|
||||||
|
|
||||||
## How it works
|
## How it works
|
||||||
|
|
||||||
When you send a message on your Meshtastic companion app, it is relayed to the radio using Bluetooth. That message is then broadcast by the radio three times over a certain interval in order to create redundancy for lost packets.
|
When you send a message on your Meshtastic companion app, it is relayed to the radio using Bluetooth. That message is then broadcasted by the radio. If it hasn't received a confirmation from any other device after a certain timeout, it will retransmit the message up to three times.
|
||||||
|
|
||||||
When a receiving radio captures a packet, it checks to see if it has heard that message before. If it has it ignores the message. If it hasn't heard the message, it will rebroadcast it at a certain interval three times.
|
When a receiving radio captures a packet, it checks to see if it has heard that message before. If it has it ignores the message. If it hasn't heard the message, it will rebroadcast it.
|
||||||
|
|
||||||
For each message a radio rebroadcasts, it marks the "hop limit" down by one. When a radio receives a packet with a hop limit of zero, it will not rebroadcast the message.
|
For each message a radio rebroadcasts, it marks the "hop limit" down by one. When a radio receives a packet with a hop limit of zero, it will not rebroadcast the message.
|
Loading…
Reference in a new issue