mudhorn/meshtastic
1
0
Fork 0
mirror of https://github.com/meshtastic/meshtastic.git synced 2025-02-02 08:42:11 -08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge branch 'master' into faq-info-about-ham-interoperability

Browse source
This commit is contained in:
withoutgettingwet 2025-01-26 22:05:22 -06:00 committed by GitHub
parent 19e5749e54 cea5258045
commit ad89884747
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
25 changed files with 550 additions and 59 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

77
blog/2025/January/meshtastic-site-planner-introduction.mdx Normal file
View file

@ -0,0 +1,77 @@
---
title: "Meshtastic Site Planner, an Open Source Tool to Optimize Your Mesh Deployments"
description: "Learn to use the new Meshtastic Site Planner, a free and open-source utility that lets you run advanced physics models to quickly plan the best placements for your Meshtastic nodes."
slug: meshtastic-site-planner-introduction
authors: Starwatcher
tags: ["meshtastic", "site planner", "deployments"]
date: 2025-01-17T12:00
hide_table_of_contents: false
image: "/img/blog/meshplanner-demo.png"
---
A well-placed Meshtastic device can have incredible range, but planning the best deployment often requires software which is proprietary, expensive, and difficult to use. [The Meshtastic Site Planner](https://site.meshtastic.org) is a new, open-source tool that allows you to easily run accurate predictions of your device range in different locations. This tool builds on sophisticated and proven radio propagation models and creates a modern, intuitive application that everyone can freely use.
{/* truncate */}
## Predicting Range ⛰️📡
### Terrain and Why It Matters
Terrain is the number one limitation for Meshtastic signals. Whether you're trying to chat with friends, plan radio deployments for disaster recovery, or even break records set from the edge of space ([range tests](https://meshtastic.org/docs/overview/range-tests/)), the terrain is ultimately the upper limit on range. The best way to increase it is to move your antenna higher, which can mean using the local terrain or placing nodes on towers. Some of the most impressive mesh networks use both approaches to transmit over long distances, but predicting the expected coverage can still be challenging.
The key is having software that knows the elevation of the terrain around your location and can also simulate effects like signal attenuation through air and scattering by obstacles. Before now, these calculations relied on hard to use software. The terrain datasets were also massive (terabytes of images) and not simple to interpret.
The Meshtastic Site Planner solves these problems by building on SPLAT!, a program written by amateur radio operator John Magliacane (KD2BD). Terrain data is automatically streamed as needed, so you don't need to find and store datasets on your computer. The models, optional settings, and data processing are handled behind a modern web UI that produces beautiful simulation maps showing where your signals can be received.
### Radio Waves and Obstacles
Besides terrain, obstructions like buildings, trees, and even weather can block or weaken radio signals. These obstacles scatter and absorb energy, reducing the strength of the signal before it reaches your receiver. How can you ensure your signal gets through without needing detailed maps of every obstacle?
Fortunately, the Site Planner solves this by allowing you to input the average height of obstructions (called "clutter"). These models use decades of research to forecast how far reliable signals can travel based on environmental conditions. By selecting a reliability threshold (e.g., 90 percent), you can ensure your node has a high likelihood of covering the predicted range.
This approach is widely used in professional radio planning for cell towers, broadcast systems, and microwave internet links. The Meshtastic Site Planner brings this capability to your mesh network. Simply enter the average height of obstacles in your area—such as 10 meters for an urban environment—and the software handles the rest.
By accounting for obstacles, the Site Planner creates realistic coverage maps, helping you optimize placement and ensure consistent connectivity in challenging environments.
### Antennas and Sensitivity
Terrain and obstacles aren't the only factors that limit range—signal strength also fades with distance. Once it becomes too faint, the receiver can't decode it. The Meshtastic Site Planner accounts for these limits, allowing you to create maps tailored to your hardware and channel.
- **Receiver Sensitivity**: Simulate based on your radio’s threshold for decoding weak signals.
- **Antenna Gain**: Adjust for different antenna types to see how they affect coverage and range.
- **Cable Loss**: Account for real-world inefficiencies like signal loss in cables and connectors.
By customizing these parameters, the Site Planner produces accurate, realistic predictions for your specific setup, whether it's a handheld node or a high-power base station.
## Using the Link Planner
The Meshtastic Site Planner is designed for simplicity, making it accessible even if you're not a radio engineer or amateur radio operator. The default settings were carefully chosen to provide accurate predictions for your Meshtastic network right out of the box.
### Getting Started
Using the Meshtastic Site Planner is as easy as:
1. **Clicking on the Map**: Choose the location of your transmitter by simply clicking on the map.
2. **Setting Key Parameters**: Enter your antenna height, select the appropriate frequency for your region (see the list here: [Meshtastic Radio Settings](https://meshtastic.org/docs/overview/radio-settings/)), and adjust any other settings if needed.
3. **Running the Simulation**: Hit "Run Simulation," and within seconds, you'll see a color-coded map showing the predicted signal strength over distance.
### Visualizing Coverage
The output map uses colors to indicate signal strength, helping you quickly identify areas with strong or weak coverage. You can fine-tune the simulation by adjusting parameters like transmitter power, antenna gain, and clutter height to reflect your actual deployment conditions.
### Simulating Multiple Radios
One of the powerful new features of the Site Planner is the ability to add multiple radios to your simulation. This allows you to model overlapping coverage areas for larger networks. For example, you can simulate how two Meshtastic radios placed strategically in Calgary, Alberta, Canada, can cover the northern half of the city. By combining their coverage areas, you can ensure seamless connectivity for your mesh network.
![Two node mesh covering Calgary, Alberta](/img/blog/siteplanner_two_sites.png)
### Tailored to Your Needs
Whether you're planning a small, localized deployment or a larger network spanning multiple locations, the Meshtastic Link Planner adapts to your requirements. Adjust settings, test configurations, and visualize the results—all with a few clicks.
With the Site Planner, optimizing your mesh network has never been easier.
## Contributions Welcome
Future releases will include point-to-point link quality estimates, terrain visualization, and presets tailored to specific meshtastic devices. We're actively looking for contributors to help get these implemented, so feel free to send a pull request!

7
blog/authors.yml
View file

@ -34,3 +34,10 @@ MeshtasticSolutions:
name: Meshtastic Solutions
url: https://meshtastic.com
image_url: https://github.com/meshtastic-solutions.png
Starwatcher:
name: Matthew Patrick
title: "Data Scientist"
url: https://github.com/mrpatrick1991
socials:
linkedin: https://www.linkedin.com/in/matthew-patrick-97996528a/
github: mrpatrick1991

73
docs/about/faq.mdx
View file

@ -10,17 +10,19 @@ import { FaqAccordion } from "/src/components/FaqAccordion";
import { FaqStructuredData } from "/src/components/FaqStructuredData";
export const Faq = {
"general": [
general: [
{
title: "Where can I get additional help, ask questions, or bond with the Meshtastic community?",
title:
"Where can I get additional help, ask questions, or bond with the Meshtastic community?",
content: `This site (which has a great search function) is the preferred place for up-to-date documentation. Many of our users and developers hang out on the [Meshtastic Discord](https://discord.gg/ktMAKGBnBs) server where you may connect with like-minded people.`,
},
{
title: "How can I contribute to Meshtastic?",
content: "Everyone contributes in a different way. Join the [Meshtastic Discord](https://discord.gg/ktMAKGBnBs) and introduce yourself. We're all very friendly. If you'd like to pitch in some code, check out the [Development](/docs/developers) menu on the left. If you'd like to contribute financially, please visit our page on [Open Collective](https://opencollective.com/meshtastic) or you may choose to [sponsor a developer](https://github.com/sponsors/meshtastic). Check out [Contributing](/docs/contributing/) for more details.",
content:
"Everyone contributes in a different way. Join the [Meshtastic Discord](https://discord.gg/ktMAKGBnBs) and introduce yourself. We're all very friendly. If you'd like to pitch in some code, check out the [Development](/docs/developers) menu on the left. If you'd like to contribute financially, please visit our page on [Open Collective](https://opencollective.com/meshtastic) or you may choose to [sponsor a developer](https://github.com/sponsors/meshtastic). Check out [Contributing](/docs/contributing/) for more details.",
},
],
"firmware": [
firmware: [
{
title: "Can I update my node's firmware over the mesh?",
content: `No, Meshtastic does not support OTA updates over LoRa. Please visit [Flash Firmware](/docs/getting-started/flashing-firmware/) for update options.`,
@ -34,9 +36,10 @@ export const Faq = {
content: `Firmware should be kept up to date. While it is not necessary to update whenever a new release comes out it's a good idea to follow the Discord Server and Forums linked in the [Introduction](/docs/introduction/#contributors) where developers may advise the community about important updates. The Meshtastic [firmware releases page](https://github.com/meshtastic/firmware/releases) on Github has a summary of what has changed in each release.`,
},
],
"android": [
android: [
{
title: "What versions of Android does the Meshtastic Android App require?",
title:
"What versions of Android does the Meshtastic Android App require?",
content: `Minimum requirement is Android 5 (Lollipop 2014, first BLE support), however at least Android 6 (Marshmallow 2015) is recommended as Bluetooth is more stable. While Android 5/6 are officially supported by Meshtastic, it is _not_ recommended that you purchase devices with these versions due to their limited OS support and limited battery life due to age. Many newer models exist that are very affordable. A good resource to use when researching affordable devices is the [LineageOS Supported Devices List](https://wiki.lineageos.org/devices/).`,
},
{
@ -53,13 +56,15 @@ export const Faq = {
content: `Long press any message to select and show the menu with "delete" and "select all" buttons.`,
},
{
title: "After a fresh firmware install, my node is not connecting via Bluetooth. What should I do?",
title:
"After a fresh firmware install, my node is not connecting via Bluetooth. What should I do?",
content: `Try forgetting the Bluetooth connection from the Android Bluetooth Settings menu. Re-pair and try again. This is a security measure and there is no workaround for it. It prevents apps and other accessories from spoofing an existing accessory by un-pairing and "re-pairing" themselves without the users' knowledge.`,
},
],
"apple": [
apple: [
{
title: "What version of iOS/iPadOS/macOS does the Meshtastic App Require?",
title:
"What version of iOS/iPadOS/macOS does the Meshtastic App Require?",
content: `The Meshtastic Apple app supports the last two major versions of iOS, iPadOS or macOS.`,
},
{
@ -67,23 +72,27 @@ export const Faq = {
content: `See [Apple Apps](/docs/software/apple/installation)`,
},
{
title: "After a fresh firmware install, my node is not connecting via Bluetooth. What should I do?",
title:
"After a fresh firmware install, my node is not connecting via Bluetooth. What should I do?",
content: `Try forgetting the Bluetooth connection from the iOS/iPadOS/macOS System Settings. Re-pair and try again. This is a security measure and there is no workaround for it. It prevents apps and other accessories from spoofing an existing accessory by un-pairing and "re-pairing" themselves without the users' knowledge.`,
},
{
title: "Do the Apple applications provide an indication if the message was acknowledged on the mesh?",
content: 'Yes, when the message is sent you will first see a `Waiting to be acknowledged...` status beneath the message. If the message is acknowledged by a node on the mesh this will update to `Acknowledged` in orange, which turns into grey when sending a direct message and the intended recipient acknowledged it. If no nodes have responded it will indicate `Max Retransmission Reached`. If there is an error, the status will update to the appropriate error. Additionally, you can long press on the message and select `Message Details` to view the date/time sent, if ack was received and the time ack was received or the error (if there was one).',
title:
"Do the Apple applications provide an indication if the message was acknowledged on the mesh?",
content:
"Yes, when the message is sent you will first see a `Waiting to be acknowledged...` status beneath the message. If the message is acknowledged by a node on the mesh this will update to `Acknowledged` in orange, which turns into grey when sending a direct message and the intended recipient acknowledged it. If no nodes have responded it will indicate `Max Retransmission Reached`. If there is an error, the status will update to the appropriate error. Additionally, you can long press on the message and select `Message Details` to view the date/time sent, if ack was received and the time ack was received or the error (if there was one).",
},
],
"channels": [
channels: [
{
title: "How do I share my Meshtastic Channel with other people?",
content: `Your Meshtastic client (Android, Apple, Web, or Python) will provide you a URL or QR code. You can email, text or print this URL or QR code and share it with people you want to join your Meshtastic Channel.`,
},
],
"python": [
python: [
{
title: "How do I find out more about installing (and using) Meshtastic via command line?",
title:
"How do I find out more about installing (and using) Meshtastic via command line?",
content: `[See our guide here](/docs/software/python/cli/installation).`,
},
{
@ -92,10 +101,11 @@ export const Faq = {
},
{
title: "What if I'm still having issues on Windows 10?",
content: "It's been reported that `App execution aliases` might conflict with one another and prevent python3 from being able to run properly. There is an example of a fix located [here](https://github.com/meshtastic/Meshtastic-gui-installer/issues/154).",
content:
"It's been reported that `App execution aliases` might conflict with one another and prevent python3 from being able to run properly. There is an example of a fix located [here](https://github.com/meshtastic/Meshtastic-gui-installer/issues/154).",
},
],
"devices": [
devices: [
{
title: "How do I turn off an ESP32 T-Beam based device?",
content: `Hold down the left PWR button for about 10 seconds and the display should turn off.`,
@ -113,7 +123,8 @@ export const Faq = {
content: `Each [supported device](/docs/hardware/devices/index.mdx) has a "Purchase Link".`,
},
{
title: "I have my hardware. How do I install the firmware and any required drivers?",
title:
"I have my hardware. How do I install the firmware and any required drivers?",
content: `[See our guide here](/docs/getting-started).`,
},
{
@ -133,32 +144,32 @@ export const Faq = {
content: `See [Device Power Configuration](/docs/configuration/radio/power) options.`,
},
{
title: "I am in Europe and my device seems to stop transmitting after a while, what is going on?",
title:
"I am in Europe and my device seems to stop transmitting after a while, what is going on?",
content: `Europe has an hourly duty cycle limit of 10% in the frequency band that Meshtastic uses. It might be that you hit this limit if you are sending a lot. You can confirm this by checking whether you see duty cycle limit errors in the serial log, Mesh Log (Apple apps) or Debug Panel (Android).
To limit traffic, you can consider setting the device metrics and position update intervals higher. Alternatively, the device can be configured to override the duty cycle limit, but then you will violate the regulations.`,
},
{
title: "Why does only one RAK Meshtastic Starter kit show up in my node list?",
content: "There was a bug where Meshtastic Starter kits were sent out with the same MAC address. With a single MAC address the devices all report as being the same device. Without the battery connected, flash the starter kit device(s) to any firmware > 1.2.59 and then do a factory reset, disconnect and reconnect the board and run `meshtastic --info`.",
title:
"Why does only one RAK Meshtastic Starter kit show up in my node list?",
content:
"There was a bug where Meshtastic Starter kits were sent out with the same MAC address. With a single MAC address the devices all report as being the same device. Without the battery connected, flash the starter kit device(s) to any firmware > 1.2.59 and then do a factory reset, disconnect and reconnect the board and run `meshtastic --info`.",
},
],
"ham": [
ham: [
{
title: "What is the benefit of using a ham license with Meshtastic?",
content: `
If you use your ham radio license with Meshtastic, consider both the privileges and restrictions:
#### Privileges
- Increased Transmit Power
- Up to 10W transmit power in the United States! [47 CFR 97.313(j)](https://www.ecfr.gov/current/title-47/chapter-I/subchapter-D/part-97#p-97.313(j))
- Up to 10W transmit power in the United States! [47 CFR 97.313(j)](<https://www.ecfr.gov/current/title-47/chapter-I/subchapter-D/part-97#p-97.313(j)>)
- Higher Gain Antennas
#### Restrictions
- Plain-Text Only
- On amateur radio bands, encryption is illegal. [FCC Part 97.113.A.4](https://www.ecfr.gov/current/title-47/chapter-I/subchapter-D/part-97/subpart-B/section-97.113#p-97.113(a)(4))
- On amateur radio bands, encryption is illegal. [FCC Part 97.113.A.4](<https://www.ecfr.gov/current/title-47/chapter-I/subchapter-D/part-97/subpart-B/section-97.113#p-97.113(a)(4)>)
- Lack of Privacy
- As a ham operator, it is a requirement that you identify yourself by your call sign periodically when transmitting. Your call sign will be publicly transmitted at least once every 10 minutes at minimum. [FCC Part 97.119.A](https://www.ecfr.gov/current/title-47/chapter-I/subchapter-D/part-97/subpart-B/section-97.119#p-97.119(a))
- As a ham operator, it is a requirement that you identify yourself by your call sign periodically when transmitting. Your call sign will be publicly transmitted at least once every 10 minutes at minimum. [FCC Part 97.119.A](<https://www.ecfr.gov/current/title-47/chapter-I/subchapter-D/part-97/subpart-B/section-97.119#p-97.119(a)>)
`,
},
{
@ -167,7 +178,7 @@ If you use your ham radio license with Meshtastic, consider both the privileges
- On Android navigate to Radio configuration -> User and set Long name to your Ham Radio callsign, then activate the slider for 'Licensed amateur radio'.
- On iPhone navigate to Settings -> User and set Long Name to your Ham Radio callsign, then activate the slider for 'Licensed Operator'.
- Instructions for Enabling ham License from the Python CLI can be found [here](/docs/software/python/cli/usage#ham-radio-support).
`,
`,
},
{
title: "Why aren’t licensed and unlicensed modes interoperable? Is this a planned feature?",
@ -175,7 +186,7 @@ If you use your ham radio license with Meshtastic, consider both the privileges
Amateur radio regulations differ significantly across countries, with many prohibiting the use of encryption. Additionally, regulations in some countries restrict licensed operators from relaying messages from unlicensed stations or transmitting messages from licensed stations without including a call sign. These restrictions make interoperability highly impractical, if not impossible. Consequently, interoperability between these modes is not a planned feature.`,
},
],
"mesh": [
mesh: [
{
title: "Does Meshtastic use LoRaWAN?",
content: `No, Meshtastic uses LoRa peer to peer (p2p), which allows much more flexibility in how LoRa is utilized compared to LoraWan. Our messaging and position updates are far too "random" compared to LoRaWAN requirements.`,
@ -189,7 +200,7 @@ Amateur radio regulations differ significantly across countries, with many prohi
content: `There is a [community project](https://github.com/a-f-G-U-C/Meshtastic-ZPS) that has worked out how to accomplish this.`,
},
],
"modules": [
modules: [
{
title: "What are Modules?",
content: `Modules are features that expand the basic device functionality and/or integrate with other services.`,

5
docs/community/local-groups.mdx
View file

@ -141,6 +141,11 @@ us on [Discord](https://discord.com/invite/ktMAKGBnBs) to add your group.
- [Meshtastic Japan Community](https://www.facebook.com/share/g/BQCGxZhw9SxFQja8/?mibextid=K35XfP)
## Latvia
- [Meshtastic Latvija](https://mesh.dodies.lv)
- [Meshtastic Latvija Matrix Space](https://matrix.to/#/#meshtastic-lv:matrix.org)
## Lithuania
- [Meshtastic Lietuva](https://www.facebook.com/groups/1122509422249414)

2
docs/configuration/radio/lora.mdx
View file

@ -65,7 +65,7 @@ Maximum number of hops. This can't be greater than 7. Default is 3 which should
### Transmit Power
If zero then, use default max legal continuous power (i.e. something that won't burn out the radio hardware)
If zero, then use default max legal continuous power (i.e. something that won't burn out the radio hardware)
In most cases you should use zero here. Units are in dBm.

4
docs/development/device/http-api.mdx
View file

@ -19,12 +19,12 @@ This is a mini-spec on a HTTP API which can be used by browser based clients to
## Request headers
- `Content-Type: application/x-protobuf`
- Indicates protobuf content (Meshtatic protobufs)
- Indicates protobuf content (Meshtastic protobufs)
## Response headers
- `Content-Type: application/x-protobuf`
- Indicates protobuf content (Meshtatic protobufs)
- Indicates protobuf content (Meshtastic protobufs)
- `X-Protobuf-Schema: <URI to the .proto schema file>`
- Not required but recommended for documentation/reflection purposes

11
docs/development/firmware/building.mdx
View file

@ -22,6 +22,17 @@ Meshtastic uses [PlatformIO](https://platformio.org), a development environment
If you want to build the RP2040 targets and get a 'Filename too long' error on Windows, please refer to [the Platformio documentation for this toolchain](https://arduino-pico.readthedocs.io/en/latest/platformio.html#important-steps-for-windows-users-before-installing)
:::
## Update the Build Environment
1. Change to `firmware` folder
```shell
cd firmware
```
2. Gather the latest changes to the [Meshtastic Firmware](https://github.com/meshtastic/firmware) repository and [submodules](https://github.com/meshtastic/firmware/blob/master/.gitmodules)
```shell
git pull --recurse-submodules
```
## Build
1. Open the newly cloned folder in [Visual Studio Code](https://code.visualstudio.com). If you do this for the first time, this can take quite some while as PlatformIO will download all the necessary tooling and libraries. Also if platformio is not installed, VSCode will ask you to install it, probably requiring a restart of the program.

2
docs/hardware/devices/chatter/index.mdx
View file

@ -14,7 +14,7 @@ Chatter V2.0 sports:
- an i2c port to easily connect a GPS
- a different routing
Both versions are fully supported by Meshastic with the same firmware.
Both versions are fully supported by Meshtastic with the same firmware.
The Meshtastic firmware works with the stock hardware, however, the LLCC68 LoRa chip cripples the RF capability of the device. As is, the Chatter can only communicate on the Medium-Slow channel.
Switching the chip with the pin-compatible and more capable Heltec RA62 (as mentioned in this Github issue https://github.com/meshtastic/firmware/issues/2896) unlock the full potential of the device.

33
docs/hardware/devices/index.mdx
View file

@ -66,6 +66,14 @@ RAK14001 RGB LED<br/>
RAK12013 Radar Sensor<br/>
RAK13800 Ethernet Module<br/>
### [WisMesh](./rak-wireless/wismesh/)
| Name | MCU | Radio | WiFi | BT | GPS |
| :----------------------------------------------------------------------- | :------- | :----- | :--: | :-: | :-: |
| [WisMesh Pocket V2](./rak-wireless/wismesh/pocket/?pocket=pocketv2) | nRF52840 | SX1262 | NO | 5.0 | YES |
| [WisMesh Pocket Mini](./rak-wireless/wismesh/pocket/?pocket=pocket-mini) | nRF52840 | SX1262 | NO | 5.0 | NO |
| [WisMesh TAP](./rak-wireless/wismesh/tap.mdx) | nRF52840 | SX1262 | NO | 5.0 | YES |
## LILYGO®
### [T-Beam](./lilygo/tbeam/)
@ -92,14 +100,15 @@ All-in-one unit with E-Ink screen, GPS and battery in injection-molded case. Fea
Inexpensive basic ESP32-based boards.
| Name | MCU | Radio | WiFi | BT | GPS |
| :------------------------------------------------ | :------- | :--------------------------- | :----------: | :-: | :-: |
| [LoRa32 V1](./lilygo/lora/?t-lora=v1) | ESP32 | SX127x | 2.4GHz b/g/n | 4.2 | NO |
| [LoRa32 V1.3](./lilygo/lora/?t-lora=v1.3) | ESP32 | SX127x | 2.4GHz b/g/n | 4.2 | NO |
| [LoRa32 V2.0](./lilygo/lora/?t-lora=v2.0) | ESP32 | SX127x | 2.4GHz b/g/n | 4.2 | NO |
| [LoRa32 V2.1-1.6](./lilygo/lora/?t-lora=v2.1) | ESP32 | SX127x | 2.4GHz b/g/n | 4.2 | NO |
| [LoRa32 V2.1-1.8](./lilygo/lora/?t-lora=v2.1-1.8) | ESP32 | SX1280 | 2.4GHz b/g/n | 4.2 | NO |
| [LoRa32 T3-S3 V1.0](./lilygo/lora/?t-lora=S3-v1) | ESP32-S3 | SX1262<br/>SX1276<br/>SX1280 | 2.4GHz b/g/n | 5.0 | NO |
| Name | MCU | Radio | WiFi | BT | GPS |
| :------------------------------------------------ | :------- | :-------------------------------------- | :----------: | :-: | :-: |
| [LoRa32 V1](./lilygo/lora/?t-lora=v1) | ESP32 | SX127x | 2.4GHz b/g/n | 4.2 | NO |
| [LoRa32 V1.3](./lilygo/lora/?t-lora=v1.3) | ESP32 | SX127x | 2.4GHz b/g/n | 4.2 | NO |
| [LoRa32 V2.0](./lilygo/lora/?t-lora=v2.0) | ESP32 | SX127x | 2.4GHz b/g/n | 4.2 | NO |
| [LoRa32 V2.1-1.6](./lilygo/lora/?t-lora=v2.1) | ESP32 | SX127x | 2.4GHz b/g/n | 4.2 | NO |
| [LoRa32 V2.1-1.8](./lilygo/lora/?t-lora=v2.1-1.8) | ESP32 | SX1280 | 2.4GHz b/g/n | 4.2 | NO |
| [LoRa32 V3.0](./lilygo/lora/?t-lora=v3.0) | ESP32 | SX127x | 2.4GHz b/g/n | 4.2 | NO |
| [LoRa32 T3-S3 V1.0](./lilygo/lora/?t-lora=S3-v1) | ESP32-S3 | SX1262<br/>SX1276<br/>SX1280<br/>LR1121 | 2.4GHz b/g/n | 5.0 | NO |
### [T-Deck](./lilygo/tdeck/)
@ -115,6 +124,14 @@ Standalone device with screen and keyboard
| :----------------------------- | :------- | :----- | :--: | :-: | :-: |
| [T-Watch S3](./lilygo/twatch/) | ESP32-S3 | SX1262 | YES | 5.0 | NO |
### [T-Lora C6](./lilygo/tlorac6/)
| Name | MCU | Radio | WiFi | BT | GPS |
| :----------------------------- | :------- | :----- | :--: | :---: | :-: |
| [T-Lora C6](./lilygo/tlorac6/) | ESP32-C6 | SX1262 | YES | 5.0\* | NO |
\* Support for Bluetooth in the ESP32-C6 modules is not yet available in the Meshtastic firmware.
## HELTEC®
### [LoRa 32](./heltec-automation/lora32/)

11
docs/hardware/devices/lilygo/index.mdx
View file

@ -36,7 +36,8 @@ Inexpensive basic ESP32-based boards.
| [LoRa32 V2.0](./lora/?t-lora=v2.0) | ESP32 | SX127x | 2.4GHz b/g/n | 4.2 | NO |
| [LoRa32 V2.1-1.6](./lora/?t-lora=v2.1) | ESP32 | SX127x | 2.4GHz b/g/n | 4.2 | NO |
| [LoRa32 V2.1-1.8](./lora/?t-lora=v2.1-1.8) | ESP32 | SX1280 | 2.4GHz b/g/n | 4.2 | NO |
| [LoRa32 T3-S3 V1.0](./lora/?t-lora=S3-v1) | ESP32-S3 | SX1262<br/>SX1276<br/>SX1280 | 2.4GHz b/g/n | 5.0 | NO |
| [LoRa32 V3.0](./lora/?t-lora=v3.0) | ESP32 | SX127x + TCXO | 2.4GHz b/g/n | 4.2 | NO |
| [LoRa32 T3-S3](./lora/?t-lora=S3-v1) | ESP32-S3 | SX1262<br/>SX1276<br/>SX1280<br/>LR1121 | 2.4GHz b/g/n | 5.0 | NO |
## [T-Deck](./tdeck/)
@ -52,3 +53,11 @@ Standalone device with screen and keyboard.
| Name | MCU | Radio | WiFi | BT | GPS |
| :---------------------- | :------- | :----- | :--: | :-: | :-: |
| [T-Watch S3](./twatch/) | ESP32-S3 | SX1262 | YES | 5.0 | NO |
## [T-Lora C6](./tlorac6/)
| Name | MCU | Radio | WiFi | BT | GPS |
| :---------------------- | :------- | :----- | :--: | :-: | :-: |
| [T-Lora C6](./tlorac6/) | ESP32-C6 | SX1262 | YES | 5.0* | NO |
\* Support for Bluetooth in the ESP32-C6 modules is not yet available in the Meshtastic firmware.

2
docs/hardware/devices/lilygo/lora/gpio.mdx
View file

@ -7,7 +7,7 @@ sidebar_position: 2
## GPIO IO12
For the Lora V2.1-1.6 and V2.1-1.8, Shorting IO12 to ground will progress through the screen pages and/or wake up the device. A simple push switch can be added for this purpose.
For the Lora V2.1-1.8, Shorting IO12 to ground will progress through the screen pages and/or wake up the device. A simple push switch can be added for this purpose.
<img src="/img/hardware/lora32-v2-1.6-button.webp" width="400" align="left" />

60
docs/hardware/devices/lilygo/lora/index.mdx
View file

@ -13,14 +13,15 @@ Further information on the LILYGO® LoRa devices can be found on LILYGO®'s [Git
<Tabs
groupId="t-lora"
queryString="t-lora"
defaultValue="v1"
defaultValue="S3-v1"
values={[
{label: 'Lora V1', value: 'v1'},
{label: 'Lora V1.3', value: 'v1.3'},
{label: 'Lora V2.0', value: 'v2.0'},
{label: 'Lora T3S3', value:'S3-v1'},
{label: 'Lora V3.0', value:'v3.0'},
{label: 'Lora V2.1-1.6', value:'v2.1'},
{label: 'Lora V2.1-1.8', value:'v2.1-1.8'},
{label: 'Lora T3S3-V1.0', value:'S3-v1'}
{label: 'Lora V2.0', value: 'v2.0'},
{label: 'Lora V1.3', value: 'v1.3'},
{label: 'Lora V1', value: 'v1'}
]}>
<TabItem value="v1">
@ -31,7 +32,7 @@ Not recommended with a battery! These boards contain the wrong component in the
:::
:::caution
This board is still in production but for various reasons not recommended for new purchases or for unattended installations. Firmware support is phased out. If in doubt, choose the Lora V2.1-1.6 or Lora T3S3 board.
This board is still in production but for various reasons not recommended for new purchases or for unattended installations. Firmware support is phased out. If in doubt, choose the Lora T3S3 board.
:::
- **MCU**
@ -71,7 +72,7 @@ Not recommended with a battery! These boards contain the wrong component in the
:::
:::caution
This board is still in production but for various reasons not recommended for new purchases or for unattended installations. Firmware support is phased out. If in doubt, choose the Lora V2.1-1.6 or Lora T3S3 board.
This board is still in production but for various reasons not recommended for new purchases or for unattended installations. Firmware support is phased out. If in doubt, choose the Lora T3S3 board.
:::
- **MCU**
@ -109,7 +110,7 @@ Not recommended with a battery! These boards contain the wrong component in the
:::
:::caution
This board is still in production but for various reasons not recommended for new purchases or for unattended installations. Firmware support is phased out. If in doubt, choose the Lora V2.1-1.6 or Lora T3S3 board.
This board is still in production but for various reasons not recommended for new purchases or for unattended installations. Firmware support is phased out. If in doubt, choose the Lora T3S3 board.
:::
- **MCU**
@ -149,6 +150,10 @@ This board is still in production but for various reasons not recommended for ne
Early versions of these boards contained the wrong component in the LiPo battery charging circuit allowing the battery to be overcharged. Boards purchased after 2021, unless the version is T3_v1.6 20180606, should not have this issue.
:::
:::caution
This board is still in production but for various reasons not recommended for new purchases or for unattended installations. Firmware support is phased out. If in doubt, choose the Lora T3S3 board.
:::
- **MCU**
- ESP32 (WiFi & Bluetooth)
- **LoRa Transceiver**
@ -157,6 +162,7 @@ Early versions of these boards contained the wrong component in the LiPo battery
- 433 MHz
- 868 MHz
- 915 MHz
- a variant of this board has a Temperature controlled oscillator (labelled TCXO) for improved frequency stability
- **Connectors**
- Micro USB
- Antenna: SMA antenna connector
@ -193,6 +199,10 @@ Early versions of these boards contained the wrong component in the LiPo battery
## Lora v2.1-1.8
:::caution
This board is still in production but for various reasons not recommended for new purchases or for unattended installations. Firmware support is phased out. If in doubt, choose the Lora T3S3 board.
:::
- **MCU**
- ESP32 (WiFi & Bluetooth)
- **LoRa Transceiver**
@ -218,15 +228,47 @@ Early versions of these boards contained the wrong component in the LiPo battery
</TabItem>
<TabItem value="v3.0">
## Lora v3.0
:::caution
This board is using a first generation Semtech chip and is therefore not recommended for new purchases. Firmware support is phased out. If in doubt, choose the Lora T3S3 board.
:::
- **MCU**
- ESP32 (WiFi & Bluetooth)
- **LoRa Transceiver**
- Semtech SX127x with TCXO for improved frequency stability
- **Frequency options**
- 433 MHz
- 868 MHz
- 915 MHz
- **Connectors**
- USB-C
- Antenna: IPEX antenna connector
### Features
- Built in 0.96 inch OLED or 2.13 inch E-Paper display
- Power and Reset switches, User Button
- microSD connector
- Solar panel and battery connector, includes solar charging circuit (CN3065)
- QUIIC for UART and I2C each
- No GPS
</TabItem>
<TabItem value="S3-v1">
## Lora T3S3 v1.0
## Lora T3S3 v1.0, v1.1 and v1.2
- **MCU**
- ESP32-S3 (WiFi & Bluetooth)
- **LoRa Transceiver**
- Semtech SX1262
- Semtech SX1276
- Semtach LR1121 (Sub-GHz and LORA_24 dual band)
- Semtech SX1280 with PA (Region LORA_24 worldwide use)
- **Frequency options**
- 868 MHz

27
docs/hardware/devices/lilygo/tlorac6/index.mdx Normal file
View file

@ -0,0 +1,27 @@
---
id: lora
title: LILYGO® T-Lora C6
sidebar_label: T-Lora C6
sidebar_position: 6
---
The T-Lora C6 is a compact, low-cost, and easy-to-use LoRa device. It is based on the ESP32-C6 and SX1262 LoRa transceiver.
## Specifications
- **MCU**
- ESP32-C6 (WiFi & Bluetooth 5 LE)
- **LoRa Transceiver**
- Semtech SX1262
- **Frequency options**
- 915 MHz
- 868 MHz
- **Connectors**
- USB-C
- Antenna: Internal PCB antenna
## Features
- User button and Reset switch
- 3D-printed lid
- no GPS

2
docs/hardware/devices/linux-native-hardware/linux-native-hardware.mdx
View file

@ -204,7 +204,7 @@ This will give you a detailed view of the service status and any potential error
By following these steps, you set up a systemd service for meshtasticd that will start automatically at boot and restart if it crashes. You can manage it using the standard systemctl commands (start, stop, restart, status, etc.).
#### View Logs of Mesthastic
#### View Logs of Meshtastic
To view the log output of the meshtasticd service, use the below command to read them out of the system journal.
```shell

20
docs/hardware/devices/rak-wireless/index.mdx
View file

@ -9,7 +9,7 @@ sidebar_position: 1
Modular hardware system with Base, Core and Peripheral modules including the low-power and solar ready nRF52840-based Meshtastic Starter Kit (19007 & 4631).
### [**WisBlock Core Modules**](./wisblock/core-module/)
### [WisBlock Core Modules](./wisblock/core-module/)
| Name | MCU | Radio | WiFi | BT | GPS |
| :-------------------------------------------------- | :------- | :----- | :----------: | :-: | :----: |
@ -17,19 +17,19 @@ Modular hardware system with Base, Core and Peripheral modules including the low
| [RAK11200](./wisblock/core-module?rakcore=RAK11200) | ESP32 | add-on | 2.4GHz b/g/n | 4.2 | add-on |
| [RAK11310](./wisblock/core-module?rakcore=RAK11310) | RP2040 | SX1262 | NO | NO | add-on |
### [**Base Boards**](./wisblock/base-board/)
### [Base Boards](./wisblock/base-board/)
[RAK5005-O](./wisblock/base-board?rakbase=RAK5005-O)<br/>
[RAK19007](./wisblock/base-board?rakbase=RAK19007)<br/>
[RAK19003](./wisblock/base-board?rakbase=RAK19003)<br/>
[RAK19001](./wisblock/base-board?rakbase=RAK19001)<br/>
### [**WisBlock Displays**](./wisblock/screens/)
### [WisBlock Displays](./wisblock/screens/)
[RAK1921](./wisblock/screens?rakscreens=OLED)<br/>
[RAK1400](./wisblock/screens?rakscreens=E-Ink)<br/>
### [**WisBlock Peripherals**](./wisblock/peripherals/)
### [WisBlock Peripherals](./wisblock/peripherals/)
[RAK1910](./wisblock/peripherals?rakmodules=GPS) GPS<br/>
[RAK12500](./wisblock/peripherals?rakmodules=GPS) GPS<br/>
@ -42,3 +42,15 @@ RAK14001 RGB LED<br/>
[RAK1906](./wisblock/peripherals?rakmodules=Sensors&sensors=RAK1906) Environment Sensor<br/>
RAK12013 Radar Sensor<br/>
RAK13800 Ethernet Module<br/>
## [RAK WisMesh](./wismesh/)
RAK WisMesh is a series of ready-to-use Meshtastic devices designed for seamless deployment. Unlike the WisBlock modular system, which allows users to build and customize their own devices, WisMesh devices provide pre-built, purpose-driven solutions that eliminate the need for assembly or additional configuration.
### [WisMesh Devices](./wismesh/)
| Device Name | Type | Features |
| ----------------------------------------------------------- | --------- | --------------------------------------------------------------------- |
| [WisMesh Pocket V2](./wismesh/pocket/?pocket=pocketv2) | Handheld | Compact, built-in display with GPS, and battery-powered |
| [WisMesh Pocket Mini](./wismesh/pocket/?pocket=pocket-mini) | Handheld | Ultra-compact, lightweight, and battery-powered |
| [WisMesh Tap](./wismesh/tap) | Versatile | Touchscreen, multi-functional, weather-resistant, and battery-powered |

16
docs/hardware/devices/rak-wireless/wismesh/index.mdx Normal file
View file

@ -0,0 +1,16 @@
---
id: wismesh
title: RAK WisMesh Devices
sidebar_label: WisMesh
sidebar_position: 2
---
RAK WisMesh is a series of ready-to-use Meshtastic devices designed for seamless deployment. Unlike the WisBlock modular system, which allows users to build and customize their own devices, WisMesh devices provide pre-built, purpose-driven solutions that eliminate the need for assembly or additional configuration.
## WisMesh Device Lineup
| Device Name | Type | Features |
| --------------------------------------------------- | --------- | -------------------------------------------------------------------- |
| [WisMesh Pocket V2](./pocket/?pocket=pocketv2) | Handheld | Compact, built-in display with GPS, and battery-powered |
| [WisMesh Pocket Mini](./pocket/?pocket=pocket-mini) | Handheld | Ultra-compact, lightweight, and battery-powered |
| [WisMesh Tap](./tap) | Versatile | Touchscreen, multi-functional, weather-resistant, and batter-powered |

166
docs/hardware/devices/rak-wireless/wismesh/pocket.mdx Normal file
View file

@ -0,0 +1,166 @@
---
id: pocket
title: RAK WisMesh Pocket Devices
sidebar_label: Pocket
sidebar_position: 1
---
import Tabs from "@theme/Tabs";
import TabItem from "@theme/TabItem";
The WisMesh Pocket line offers compact, ready-to-use Meshtastic devices designed for seamless communication in a LoRa mesh network. Built for portability and reliability, these devices eliminate the need for assembly or configuration, providing a straightforward and efficient way to stay connected. Whether for personal use or large-scale deployments, the WisMesh Pocket series delivers versatile solutions for reliable off-grid messaging.
<Tabs
groupId="pocket"
queryString="pocket"
defaultValue="pocketv2"
values={[
{label: 'Pocket V2', value: 'pocketv2'},
{label: 'Pocket Mini', value: 'pocket-mini'},
{label: 'RAK19026', value: 'rak19026'}
]}>
<TabItem value="pocketv2">
:::info
WisMesh Pocket V2 is an updated version of the WisMesh Pocket. It features a newly designed base board with improved voltage regulator and battery circuit to comply with the European CE requirements and uses an RP-SMA antenna connector to comply with FCC requirements.
The WisMesh Pocket V1, while still supported, is no longer available for purchase.
:::
- **Base Board**
- [RAK19026](/docs/hardware/devices/rak-wireless/wismesh/pocket/?pocket=rak19026)
- **MCU**
- [RAK4630 (nRF52840)](https://docs.rakwireless.com/product-categories/wisduo/rak4630-module/overview/)
- Bluetooth BLE 5.0
- Very low power consumption
- **LoRa Transceiver:**
- SX1262
- **Frequency Options:**
- 868 MHz
- 915 MHz
- 920 MHz
- 923 MHz
- **Connectors:**
- USB-C
- RP-SMA
### Features
- RAK19026 WisBlock Base Board
- Improved voltage regulator with USB over-voltage protection
- Improved battery charger, control with NTC temperature sensors
- Improved location of the sensor slots
- 1.3” OLED display
- GNSS location module onboard
- Acceleration sensor onboard
- 3200 mAh Rechardable battery
### Resources
- Firmware file: `firmware-rak4631-X.X.X.xxxxxxx.uf2`
- Further information on the WisMesh Pocket V2 can be found on the [RAK Documentation Center](https://docs.rakwireless.com/product-categories/meshtastic/wismesh-pocket-v2/).
- Purchase Links:
- US
- [Rokland - US915 Mhz](https://store.rokland.com/products/wismesh-pocket)
- International
- [RAK Wireless Store](https://store.rakwireless.com/products/wismesh-pocket)
- [RAK Wireless Aliexpress](https://www.aliexpress.us/item/3256808087883682.html)
![RAK Pocket V2](/img/hardware/rak/pocket-v2.webp)
</ TabItem>
<TabItem value="pocket-mini">
The WisMesh Pocket Mini is an ultra-compact, lightweight Meshtastic device without a built-in display or GPS, designed for low-power, long-lasting portable mesh communication.
- **Base Board**
- [RAK19003](/docs/hardware/devices/rak-wireless/wisblock/base-board?rakbase=RAK19003)
- **MCU**
- [RAK4631 (nRF52840)](/docs/hardware/devices/rak-wireless/wisblock/core-module?rakcore=RAK4631)
- Bluetooth BLE 5.0
- Very low power consumption
- **LoRa Transceiver:**
- SX1262
- **Frequency Options:**
- 868 MHz
- 915 MHz
- 920 MHz
- 923 MHz
- **Connectors:**
- USB-C
### Features
- On/Off switch
- 2 sensor slots
- Internal PCB Antenna for LoRa
- Internal BLE Antenna
- 1000mAh battery
### Resources
- Firmware file: `firmware-rak4631-X.X.X.xxxxxxx.uf2`
- Further information on the WisMesh Pocket Mini can be found on the [RAK Documentation Center](https://docs.rakwireless.com/product-categories/meshtastic/wismesh-pocket-mini/).
- Purchase Links:
- US
- [Rokland - US915 Mhz](https://store.rokland.com/products/rakwireless-wismesh-pocket-mini-all-in-one-meshtastic-handheld-915-mhz-radio-with-lora-antenna)
- International
- [RAK Wireless Store](https://store.rakwireless.com/products/wismesh-pocket-mini)
![RAK Pocket Mini](/img/hardware/rak/pocket-mini.webp)
</ TabItem>
<TabItem value="rak19026">
The RAK19026 WisMesh Base Board serves as the foundation for the WisMesh Pocket line and is also available separately for users who want to build their own Meshtastic device. It includes an onboard GNSS module, acceleration sensor, user button, and battery disconnect switch, providing additional built-in features while maintaining a compact and easy-to-assemble design.
### Variants
The RAK19026 is available in three variants:
- OLED Mounted with GNSS and Motion Sensor
- GNSS and Motion Sensor with Unsoldered OLED
- Without OLED with GNSS and Motion
All variants include the following features:
- **MCU**
- [RAK4630 (nRF52840)](https://docs.rakwireless.com/product-categories/wisduo/rak4630-module/overview/)
- Bluetooth BLE 5.0
- Very low power consumption
- **LoRa Transceiver:**
- SX1262
- **Frequency Options:**
- 868 MHz
- 915 MHz
- 920 MHz
- 923 MHz
- **Connectors:**
- USB-C
- U.FL/IPEX for LoRa
### Features
- Improved voltage regulator with USB over-voltage protection
- Improved battery charger, control with NTC temperature sensors
- Improved location of the sensor slots
- GNSS location module onboard
- Acceleration sensor onboard
### Resources
- Firmware file: `firmware-rak4631-X.X.X.xxxxxxx.uf2`
- Further information on the WisMesh Base Board can be found on the [RAK Documentation Center](https://docs.rakwireless.com/product-categories/meshtastic/wismesh-base/overview/).
- Purchase Links:
- US
- [Rokland - US915 Mhz](https://store.rokland.com/products/rakwireless-wismesh-baseboard-rak19026-oled-mounted-gnss-motion-sensor-pid-115125)
- International
- [RAK Wireless Store](https://store.rakwireless.com/products/wismesh-baseboard-rak19026)
![RAK19026 WisMesh Baseboard](/img/hardware/rak/rak19026.webp)
</ TabItem>
</ Tabs>

46
docs/hardware/devices/rak-wireless/wismesh/tap.mdx Normal file
View file

@ -0,0 +1,46 @@
---
id: tap
title: RAK WisMesh Tap
sidebar_label: Tap
sidebar_position: 2
---
The WisMesh TAP is a Meshtastic device equipped with a touch screen featuring an on-screen keyboard that's built on the WisBlock RAK19007 Base Board and RAK4631 nRF52 core module in an IP65-rated enclosure. This makes it perfect for reliable off-grid communication during activities like exploring, hiking, or testing other remotely deployed devices, all without needing a phone.
- **Base Board**
- [RAK19007](/docs/hardware/devices/rak-wireless/wisblock/base-board?rakbase=RAK19007)
- **MCU**
- [RAK4631 (nRF52840)](/docs/hardware/devices/rak-wireless/wisblock/core-module?rakcore=RAK4631)
- Bluetooth BLE 5.0
- Very low power consumption
- **LoRa Transceiver:**
- SX1262
- **Frequency Options:**
- 868 MHz
- 915 MHz
- 920 MHz
- 923 MHz
- **Connectors:**
- USB-C
- SMA
### Features
- 320 x 240 TFT touch screen
- 3200 mAh rechargeable battery
- GNSS location module onboard ([RAK12500](/docs/hardware/devices/rak-wireless/wisblock/peripherals?rakmodules=GPS))
- External RAK Blade 2.3 dBi LoRa antenna
- Internal bluetooth antenna
- Versatile- use as a portable handheld or pick a mounting solution
### Resources
- Firmware file: `firmware-rak_wismeshtap-X.X.X.xxxxxxx.uf2`
- Further information on the WisMesh TAP can be found on the [RAK Documentation Center](https://docs.rakwireless.com/product-categories/meshtastic/wismesh-tap/overview/).
- Purchase Links:
- US
- [Rokland - US915 Mhz](https://store.rokland.com/products/rakwireless-wismesh-tap-touchscreen-915-mhz-handheld-or-mountable-unit-lora-gps)
- International
- [RAK Wireless Store](https://store.rakwireless.com/products/wismesh-tap)
![RAK WisMesh Tap](/img/hardware/rak/wismesh-tap.webp)

45
docs/software/site-planner/index.mdx Normal file
View file

@ -0,0 +1,45 @@
---
id: siteplanner
title: Meshtastic Site Planner
sidebar_label: Meshtastic Site Planner
sidebar_position: 5
description: Overview of Meshtasticator Site Planner - for making predictions of radio range which account for physics and terrain
---
The Meshtastic Site Planner is a open-source web utility for predicting node range and coverage. It can be found on site.meshtastic.org, and the source code is maintained at https://github.com/meshtastic/meshtastic-site-planner.
## Getting Started
1. Go to the [official version](https://site.meshtastic.org) or run a development copy and open the tool in a web browser.
2. In `Site Parameters > Site / Transmitter`, enter a name for the site, the geographic coordinates, and the antenna height above ground. Refer to the Meshtastic regional parameters (https://meshtastic.org/docs/configuration/region-by-country/) and input the transmit power, frequency, and antenna gain for your device.
3. In `Site Parameters > Receiver`, enter the receiver sensitivity (`-130 dBm` for the default `LongFast` channel), the receiver height, and the receiver antenna gain.
4. In `Site Parameters > Receiver`, enter the maximum range for the simulation in kilometers. Selecting long ranges (> 50 kilometers) will result in longer computation times.
5. Press "Run Simulation." The coverage map will be displayed when the calculation completes.
Multiple radio sites can be added to the simulation by repeating these steps. The other adjustable parameters default to sensible choices for meshtastic radios, but you can change them if your project uses different hardware.
## Understanding Results
The Meshtastic Site Planner creates a color-coded map of where your radio signal will reach, given the terrian and simulation parameters. The expected signal strength (RSSI) can be read from the colorbar. Regions with a strong signal (predicted RSSI > -110 dBm) have a stronger chance of sucessfully receiving and sending signals. In areas with a low RSSI (< 125 dBm), obstacles may limit communication reliability. You can adjust the signal cutoff threshold under `Receiver > Sensitivity Limit`. Minimum signal thresholds depend on the radio chipset and presets, and are approximately as follows:
| **Preset** | **Bandwidth (kHz)** | **Spreading Factor (SF)** | **Coding Rate** | **Sensitivity (dBm)** |
|-------------------|---------------------|---------------------------|-----------------|-----------------------|
| **ShortTurbo** | 500 | 7 | 4/5 | -117 |
| **ShortFast** | 250 | 7 | 4/5 | -121 |
| **ShortSlow** | 250 | 8 | 4/5 | -124 |
| **MediumFast** | 250 | 9 | 4/5 | -127 |
| **MediumSlow** | 250 | 10 | 4/5 | -130 |
| **LongFast** | 125 | 11 | 4/5 | -133 |
| **LongModerate** | 125 | 11 | 4/8 | -136 |
| **LongSlow** | 125 | 12 | 4/8 | -137 |
| **VeryLongSlow** | 62.5 | 12 | 4/8 | -141 |
## Limitations
The Site Planner uses terrain data from the NASA SRTM (Shuttle Radar Topography) mission. This elevation dataset is accurate to around 90 meters, and does not account for obstructions such as buildings or trees. You can estimate the effect of random obstructions by entering their average height in `Environment > Clutter Height`. It is a good idea to always verify predictions from this tool using real-world testing.

BIN
static/img/blog/meshplanner-demo.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 3.3 MiB

BIN
static/img/blog/siteplanner_two_sites.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 3.8 MiB

BIN
static/img/hardware/rak/pocket-mini.webp Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 13 KiB

BIN
static/img/hardware/rak/pocket-v2.webp Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 14 KiB

BIN
static/img/hardware/rak/rak19026.webp Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 57 KiB

BIN
static/img/hardware/rak/wismesh-tap.webp Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 25 KiB