From 379ae9bc1e61197346d47f1847f091ca747ec9a9 Mon Sep 17 00:00:00 2001 From: GUVWAF Date: Tue, 3 Jan 2023 17:04:03 +0100 Subject: [PATCH 1/5] Add some notes about duty cycle limit --- docs/about/faq.mdx | 5 +++++ docs/blocks/_lora-regions.mdx | 6 +++++- docs/configuration/device-config/lora.mdx | 1 + 3 files changed, 11 insertions(+), 1 deletion(-) diff --git a/docs/about/faq.mdx b/docs/about/faq.mdx index 45c732ef..9b793509 100644 --- a/docs/about/faq.mdx +++ b/docs/about/faq.mdx @@ -119,6 +119,11 @@ Once the node wakes up from sleep, your phone will relay any delayed messages th - Android instructions see: [Android Usage](/docs/software/android/usage#configuration-options) - Python CLI instructions see: [Python Usage](/docs/software/python/cli/usage#changing-settings) +### I am in Europe and my device seems to stop transmitting after a while, what is going on? + +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 or the MeshLog of the iOS app. +To limit traffic, you can consider setting the device metrics and position update intervals higher. Alternatively, you can override the duty cycle limit, but then you will violate the regulations if you are not a HAM operator. + ### Why does only one RAK Meshtastic Starter kit show up in my node list? 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`. diff --git a/docs/blocks/_lora-regions.mdx b/docs/blocks/_lora-regions.mdx index 154dde89..b3ae715a 100644 --- a/docs/blocks/_lora-regions.mdx +++ b/docs/blocks/_lora-regions.mdx @@ -14,4 +14,8 @@ | `IN` | India | | `NZ_865` | New Zealand 865MHz | | `TH` | Thailand | -| `LORA_24` | 2.4 GHz band worldwide | \ No newline at end of file +| `LORA_24` | 2.4 GHz band worldwide | + +:::info +EU_433 and EU_868 have to adhere to an hourly duty cycle limitation of 10%. Your device will stop transmitting if you reach it, until it is allowed again. +::: \ No newline at end of file diff --git a/docs/configuration/device-config/lora.mdx b/docs/configuration/device-config/lora.mdx index bbb7a5c2..6025a954 100644 --- a/docs/configuration/device-config/lora.mdx +++ b/docs/configuration/device-config/lora.mdx @@ -107,6 +107,7 @@ LoRa config commands are available in the python CLI. Example commands are below | lora.modem_preset | `LONG_FAST`, `LONG_SLOW`, `VERY_LONG_SLOW`, `MEDIUM_SLOW`, `MEDIUM_FAST`, `SHORT_SLOW`, `SHORT_FAST` | `LONG_FAST` | | lora.region | `UNSET`, `US`, `EU_433`, `EU_868`, `CN`, `JP`, `ANZ`, `KR`, `TW`, `RU` ,`IN`, `NZ_865`, `TH`, `LORA_24` | `UNSET` | | lora.hop_limit | `1`,`2`,`3`,`4`,`5`,`6`,`7` | `3` | +| lora.override_duty_cycle | `false`, `true` | `false` | From 611a2b769b76957a30c7edecaa3db880c51d38c1 Mon Sep 17 00:00:00 2001 From: GUVWAF Date: Tue, 3 Jan 2023 20:13:51 +0100 Subject: [PATCH 2/5] Remove HAM exception --- docs/about/faq.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/about/faq.mdx b/docs/about/faq.mdx index 9b793509..cc17a7d6 100644 --- a/docs/about/faq.mdx +++ b/docs/about/faq.mdx @@ -122,7 +122,7 @@ Once the node wakes up from sleep, your phone will relay any delayed messages th ### I am in Europe and my device seems to stop transmitting after a while, what is going on? 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 or the MeshLog of the iOS app. -To limit traffic, you can consider setting the device metrics and position update intervals higher. Alternatively, you can override the duty cycle limit, but then you will violate the regulations if you are not a HAM operator. +To limit traffic, you can consider setting the device metrics and position update intervals higher. Alternatively, you can override the duty cycle limit, but then you will violate the regulations. ### Why does only one RAK Meshtastic Starter kit show up in my node list? From 9453e230ac5f7b76fb871854dec3817024e292db Mon Sep 17 00:00:00 2001 From: GUVWAF Date: Wed, 4 Jan 2023 16:58:14 +0100 Subject: [PATCH 3/5] A bit of rephrasing --- docs/about/faq.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/about/faq.mdx b/docs/about/faq.mdx index cc17a7d6..04ffc167 100644 --- a/docs/about/faq.mdx +++ b/docs/about/faq.mdx @@ -121,8 +121,8 @@ Once the node wakes up from sleep, your phone will relay any delayed messages th ### I am in Europe and my device seems to stop transmitting after a while, what is going on? -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 or the MeshLog of the iOS app. -To limit traffic, you can consider setting the device metrics and position update intervals higher. Alternatively, you can override the duty cycle limit, but then you will violate the regulations. +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. ### Why does only one RAK Meshtastic Starter kit show up in my node list? From 4031bc32ba04dbc99f0c5e51c5107699906471b2 Mon Sep 17 00:00:00 2001 From: GUVWAF Date: Wed, 4 Jan 2023 17:05:39 +0100 Subject: [PATCH 4/5] Add section to LoRa config --- docs/configuration/device-config/lora.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/configuration/device-config/lora.mdx b/docs/configuration/device-config/lora.mdx index 6025a954..061a912f 100644 --- a/docs/configuration/device-config/lora.mdx +++ b/docs/configuration/device-config/lora.mdx @@ -67,6 +67,10 @@ This is controlling the actual hardware frequency the radio is transmitting on. For testing it is useful sometimes to force a node to never listen to particular other nodes (simulating radio out of range). All nodenums listed in the ignore_incoming array will have packets they send dropped on receive (by router.cpp) +### Override Duty Cycle Limit + +Setting this true to means that the device will override the hourly duty cycle limit that is induced in Europe, meaning that you will violate the regulations when you reach the limit. Defaults to false, meaning the device will drop all packets once you hit the limit and resume when it is allowed again. + ## LoRa Config Client Availability Date: Thu, 5 Jan 2023 17:32:08 +0100 Subject: [PATCH 5/5] Rephrase LoRa config --- docs/configuration/device-config/lora.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuration/device-config/lora.mdx b/docs/configuration/device-config/lora.mdx index 061a912f..17040556 100644 --- a/docs/configuration/device-config/lora.mdx +++ b/docs/configuration/device-config/lora.mdx @@ -69,7 +69,7 @@ For testing it is useful sometimes to force a node to never listen to particular ### Override Duty Cycle Limit -Setting this true to means that the device will override the hourly duty cycle limit that is induced in Europe, meaning that you will violate the regulations when you reach the limit. Defaults to false, meaning the device will drop all packets once you hit the limit and resume when it is allowed again. +Setting this option to 'true' means the device will ignore the hourly duty cycle limit in Europe. This means that you might violate regulations if the device transmits too much. By default, this option is set to 'false,' which means the device will stop sending data when it reaches the hourly limit and will start again when it is allowed to do so. ## LoRa Config Client Availability