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

Fix broken links

Browse source
This commit is contained in:
Garth Vander Houwen 2022-07-03 11:46:00 -07:00
parent f88f23ccd1
commit 92ea05e5d3
4 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/developers/Firmware/module-api.mdx
View file

@ -80,6 +80,6 @@ All other values are reserved.
If you would like to use protocol buffers to define the structures you send over the mesh (recommended), here's how to do that. If you would like to use protocol buffers to define the structures you send over the mesh (recommended), here's how to do that.
- Create a new .proto file in the protos directory. You can use the existing [remote_hardware.proto](https://github.com/meshtastic/Meshtastic-protobufs/blob/master/remote_hardware.proto) file as an example. - Create a new .proto file in the protos directory.
- Run "bin/regen-protos.sh" to regenerate the C code for accessing the protocol buffers. If you don't have the required nanopb tool, follow the instructions printed by the script to get it. - Run "bin/regen-protos.sh" to regenerate the C code for accessing the protocol buffers. If you don't have the required nanopb tool, follow the instructions printed by the script to get it.
- Done! You can now use your new protobuf just like any of the existing protobufs in meshtastic. - Done! You can now use your new protobuf just like any of the existing protobufs in meshtastic.

2
docs/developers/contributing.mdx
View file

@ -30,7 +30,7 @@ The [Meshtastic-device](https://github.com/meshtastic/Meshtastic-device) is wher
## Modules ## Modules
[Modules](/docs/software/modules) are also implemented mainly in the Meshtastic-device repo above. Typically, you would add functionality in the protobufs repo and the device repo to implement module functionality. You probably also want to have some client/device use/interact with the module and that is where the Device support comes into play. [Modules](/docs/settings/moduleconfig) are also implemented mainly in the Meshtastic-device repo above. Typically, you would add functionality in the protobufs repo and the device repo to implement module functionality. You probably also want to have some client/device use/interact with the module and that is where the Device support comes into play.
## Device Support ## Device Support

2
docs/faq/modules.mdx
View file

@ -12,7 +12,7 @@ Modules are features that expand the basic device functionality and/or integrate
### What modules do we have available? ### What modules do we have available?
A list of available modules is available [here](/docs/software/modules). A list of available modules is available [here](/docs/settings/moduleconfig).
### I'd like to write a module. How do I get started? ### I'd like to write a module. How do I get started?

2
docs/hardware/antenna/testing.mdx
View file

@ -17,7 +17,7 @@ As mentioned, while stating the obvious, the simplest way of performing a test i
- Change aerials, repeat, and evaluate results. - Change aerials, repeat, and evaluate results.
:::note :::note
The [range test module](/docs/software/modules/range-test-module) has been designed for exactly this purpose. It allows one node to transmit a frequent message, and another node to record which messages were received. This data is saved and can be imported to applications such as Google Earth. The [range test module](/docs/settings/moduleconfig/range-test) has been designed for exactly this purpose. It allows one node to transmit a frequent message, and another node to record which messages were received. This data is saved and can be imported to applications such as Google Earth.
::: :::
On the topic of testing - performing your own testing and providing feedback is the lifeblood of Meshtastic and open source projects. On the topic of testing - performing your own testing and providing feedback is the lifeblood of Meshtastic and open source projects.