mirror of
https://github.com/meshtastic/meshtastic.git
synced 2025-03-05 21:00:08 -08:00
revert all
This commit is contained in:
rcarteraz
parent
137a961b03
commit
272eec9341
|
|
@ -134,11 +134,12 @@ export const Faq = {
|
|||
},
|
||||
{
|
||||
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.`,
|
||||
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`.`,
|
||||
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": [
|
||||
|
|
@ -149,55 +150,55 @@ If you use your ham radio license with Meshtastic, consider both the privileges
|
|||
#### 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))
|
||||
`,
|
||||
},
|
||||
{
|
||||
title: "How do I set my ham call sign?",
|
||||
content: `
|
||||
},
|
||||
{
|
||||
title: "How do I set my ham call sign?",
|
||||
content: `
|
||||
- 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).
|
||||
`,
|
||||
},
|
||||
],
|
||||
"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.`,
|
||||
},
|
||||
{
|
||||
title: "Will Meshtastic work with (insert LoRa service)",
|
||||
content: `Meshtastic uses LoRa peer to peer (p2p), which has allowed us to customize how we use the protocol. Likely it will not work with the service you have in mind, but it may be possible to build a bridge between services using MQTT. That will require further development outside the scope of this project to implement.`,
|
||||
},
|
||||
{
|
||||
title: "Can I locate a device via triangulation?",
|
||||
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": [
|
||||
{
|
||||
title: "What are Modules?",
|
||||
content: `Modules are features that expand the basic device functionality and/or integrate with other services.`,
|
||||
},
|
||||
{
|
||||
title: "What modules do we have available?",
|
||||
content: `A list of available modules is available [here](/docs/configuration/module).`,
|
||||
},
|
||||
{
|
||||
title: "I'd like to write a module. How do I get started?",
|
||||
content: `API documentation for creating modules is available [here](/docs/development/device/module-api).`,
|
||||
},
|
||||
`,
|
||||
},
|
||||
],
|
||||
};
|
||||
"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.`,
|
||||
},
|
||||
{
|
||||
title: "Will Meshtastic work with (insert LoRa service)",
|
||||
content: `Meshtastic uses LoRa peer to peer (p2p), which has allowed us to customize how we use the protocol. Likely it will not work with the service you have in mind, but it may be possible to build a bridge between services using MQTT. That will require further development outside the scope of this project to implement.`,
|
||||
},
|
||||
{
|
||||
title: "Can I locate a device via triangulation?",
|
||||
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": [
|
||||
{
|
||||
title: "What are Modules?",
|
||||
content: `Modules are features that expand the basic device functionality and/or integrate with other services.`,
|
||||
},
|
||||
{
|
||||
title: "What modules do we have available?",
|
||||
content: `A list of available modules is available [here](/docs/configuration/module).`,
|
||||
},
|
||||
{
|
||||
title: "I'd like to write a module. How do I get started?",
|
||||
content: `API documentation for creating modules is available [here](/docs/development/device/module-api).`,
|
||||
},
|
||||
],
|
||||
};
|
||||
|
||||
<FaqStructuredData faqs={Faq} />
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue