Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -185,7 +185,7 @@ The T-Deck firmware is free to download and most features are available without
- Canada and USA are on **910.525MHz**
- For other regions and countries, please check your local LoRa frequency

In UK and EU, 867.5MHz is not allowed to use 250kHz bandwidth and it only allows 2.5% duty cycle for clients. 869.525Mhz allows an airtime of 10%, 250KHz bandwidth, and a higher EIRP, therefore MeshCore nodes can send more often and with more power. That is why this frequency is chosen for UK and EU. This is also why Meshtastic also uses this frequency.
In UK and EU, 867.5MHz is not allowed to use 250kHz bandwidth and it only allows 2.5% duty cycle for clients. 869.525Mhz allows an airtime of 10%, 250KHz bandwidth, and a higher Effective Isotropic Radiated Power (EIRP), therefore MeshCore nodes can send more often and with more power. That is why this frequency is chosen for UK and EU. This is also why Meshtastic also uses this frequency.

[Source](https://discord.com/channels/826570251612323860/1330643963501351004/1356540643853209641)

Expand Down Expand Up @@ -557,7 +557,7 @@ From here, reference repeater and room server command line commands on MeshCore
**A:** Yes. See the following:

#### 5.14.1. meshcoremqtt
A Python script to send meshore debug and packet capture data to MQTT for analysis
A Python script to send meshcore debug and packet capture data to MQTT for analysis
https://github.com/Andrew-a-g/meshcoretomqtt

#### 5.14.2. MeshCore for Home Assistant
Expand Down
4 changes: 2 additions & 2 deletions docs/payloads.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ Appdata Flags

# Acknowledgement

An acknowledgement that a message was received. Note that for returned path messages, an acknowledgement will be sent in the "extra" payload (see [Returned Path](#returned-path)) and not as a discrete ackowledgement. CLI commands do not require an acknowledgement, neither discrete nor extra.
An acknowledgement that a message was received. Note that for returned path messages, an acknowledgement will be sent in the "extra" payload (see [Returned Path](#returned-path)) and not as a discrete acknowledgement. CLI commands do not require an acknowledgement, neither discrete nor extra.

| Field | Size (bytes) | Description |
|----------|--------------|------------------------------------------------------------|
Expand Down Expand Up @@ -186,4 +186,4 @@ TODO: describe what datagram looks like

# Custom packet

Custom packets have no defined format.
Custom packets have no defined format.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What changed here? The line ending?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ironically, that's a typo from when I copied the finished draft into vscode 🫠