Remove forum link, finish overview page

This commit is contained in:
apt105 2021-04-14 21:01:15 +01:00
parent 632c7a6051
commit 4c45d98f6f
4 changed files with 12 additions and 15 deletions

View file

@ -91,7 +91,3 @@ Ideas for external hardware:
* This won't directly support an passive (normal) speaker as it does not generate any audio wave forms.
* This currently only supports the esp32. Other targets may be possible, I just don't have to test with.
* This plugin only monitors text messages. We won't trigger on any other packet types.
## Need more help?
Go to the [Meshtastic Forum](https://meshtastic.discourse.group) if you have any questions or to share how you have used this.

View file

@ -4,4 +4,13 @@ title: Plugins overview
sidebar_label: Overview
---
There are a number of plugins that have been integrated into the device firmware. These can be turned on using the Meshtastic python command line program. Please note that these plugins require the device to be rebooted once they have been enabled for them to start running.
There are a number of plugins that have been integrated into the device firmware. These can be turned on using the Meshtastic python command line program. Please note that these plugins require the device to be rebooted once they have been enabled for them to start running.
These plugins are currently integrated into the firmware:
* Range test - Allows automated testing of communication range of nodes
* External notifications - Allows a speaker, LED or other device to indicate when a message has been received
* Serial - Allows messages to be sent across the mesh by sending strings across a serial port
These plugins are currently in development:
* Store and forward - Allows a node to store messages and resend them to nodes that have intermittant connection to the mesh
* Environment measurement - Allows a node to measure it's local environment and report across the mesh

View file

@ -133,7 +133,3 @@ Q: Can I use this as a sender while on battery power?
Q: Why is this operating on incoming messages instead of the existing location discovery protocol?
* This plugin is still young and currently supports monitoring just one port at a time. I decided to use the existing message port because that is easy to test with. A future version will listen to multiple ports to be more promiscuous.
## Need more help?
Go to the [Meshtastic Forum](https://meshtastic.discourse.group) if you have any questions or to share how you have used this.

View file

@ -36,9 +36,5 @@ This won't happen any time soon.
## Known Problems
* Until the plugin is initilized by the startup sequence, the TX pin is in a floating state. Device connected to that pin may see this as "noise".
* Will not work on NRF and the Linux device targets.
## Need help?
Go to the [Meshtastic Forum](https://meshtastic.discourse.group) if you have any questions or to share how you have used this.
* Until the plugin is initilized by the startup sequence, the TX pin is in a floating state. Device connected to that pin may see this as "noise".
* Will not work on NRF and the Linux device targets.