mirror of
https://github.com/meshtastic/meshtastic.git
synced 2024-11-13 17:14:25 -08:00
Merge branch 'master' into patch-1
This commit is contained in:
pdxlocations
GitHub
commit
3fe1ebb42f
|
|
@ -11,24 +11,19 @@ The device config options are: Role, Serial Output, and Debug Log. Device config
|
||||||
|
|
||||||
## Device Config Values
|
## Device Config Values
|
||||||
|
|
||||||
### Role
|
### Roles
|
||||||
|
| Device Role | Description | Best Uses |
|
||||||
Sets the role of the node.
|
| -------------- | ------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
|
||||||
|
| CLIENT | App connected or stand alone messaging device. | General use for individuals needing to communicate over the Meshtastic network with support for client applications. |
|
||||||
Acceptable values:
|
| CLIENT_MUTE | Device that does not forward packets from other devices. | Situations where a device needs to participate in the network without assisting in packet routing, reducing network load. |
|
||||||
|
| CLIENT_HIDDEN | Device that only broadcasts as needed for stealth or power savings. | Use in stealth/hidden deployments or to reduce airtime/power consumption while still participating in the network. |
|
||||||
| Value | Description |
|
| TRACKER | Broadcasts GPS position packets as priority. | Tracking the location of individuals or assets, especially in scenarios where timely and efficient location updates are critical. |
|
||||||
|:----------------:|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|
|
| LOST_AND_FOUND | Broadcasts location as message to default channel regularly for to assist with device recovery. | Used for recovery efforts of a lost device. |
|
||||||
| `CLIENT` | Client (default) - This role will follow the standard routing rules while also allowing the device to interact with client applications via BLE/Wi-Fi (Android/Apple/Web). |
|
| SENSOR | Prioritizes broadcasting GPS position packets. | Deploying in scenarios where gathering environmental or other sensor data is crucial, with efficient power usage and frequent updates. |
|
||||||
| `CLIENT_MUTE` | Client Mute - Same as a client except packets will not hop over this node, does not contribute to routing packets for mesh. |
|
| TAK | Optimized for ATAK system communication, reduces routine broadcasts. | Integration with ATAK systems for communication in tactical or coordinated operations. |
|
||||||
| `ROUTER` | Router - Mesh packets will prefer to be routed over this node. The assumption is that Router-type devices will be placed in locations with a height/range/antenna advantage, and therefore have better overall coverage. This node will not be used by client apps. The BLE/Wi-Fi radios and the OLED screen will be put to sleep. Please note: Due to the preferred routing, this role may cause higher power usage due to more frequent transmission. |
|
| REPEATER | Infrastructure node for extending network coverage by relaying messages with minimal overhead. Not visible in Nodes list. | Best positioned in strategic locations to maximize the network's overall coverage. Device is not shown in topology. |
|
||||||
| `ROUTER_CLIENT` | Router Client - Hybrid of the Client and Router roles. Similar to Router, except the Router Client can be used as both a Router and an app connected Client. BLE/Wi-Fi and OLED screen will not be put to sleep. |
|
| ROUTER | Infrastructure node for extending network coverage by relaying messages. Visible in Nodes list. | Best positioned in strategic locations to maximize the network's overall coverage. Device is shown in topology. |
|
||||||
| `REPEATER` | Repeater - Mesh packets will prefer to be routed over this node. This role eliminates unnecessary overhead such as NodeInfo, DeviceTelemetry, and any other mesh packet, resulting in the device not appearing as part of the network. As such, direct messaging this node is not available, as it will not appear in your nodes list which results in a cleaner mesh network. Channel and modem settings of the mesh packets being repeated must be identical to the repeater's configuration. Please see Rebroadcast Mode for additional settings specific to this role. |
|
| ROUTER_CLIENT | Combination of both ROUTER and CLIENT. Not for mobile devices. | Devices in a strategic position for priority routing that need to also serve as a standard CLIENT. |
|
||||||
| `TRACKER` | Tracker - For use with devices intended as a GPS tracker. Position packets sent from this device will be higher priority. Smart Position Broadcast will default to the currently configured settings. When used in conjunction with power.is_power_saving = true, nodes will wake up, send position, and then sleep for position.position_broadcast_secs seconds. |
|
|
||||||
| `SENSOR` | Sensor - For use with devices intended to primarily collect sensor readings. Telemetry packets sent from this device will be higher priority, broadcasting every five minutes. When used in conjunction with power.is_power_saving = true, nodes will wake up, send environment telemetry, and then sleep for telemetry.environment_update_interval seconds. |
|
|
||||||
| `TAK` | TAK - Used for nodes dedicated for connection to an ATAK EUD. Turns off many of the routine broadcasts to favor CoT packet stream from the Meshtastic ATAK plugin -> IMeshService -> Node. |
|
|
||||||
| `CLIENT_HIDDEN` | Client Hidden - Used for nodes that "only speak when spoken to." Turns off all of the routine broadcasts but allows for ad-hoc communication. Still rebroadcasts, but with local only rebroadcast mode (known meshes only). Can be used for clandestine operation or to dramatically reduce airtime / power consumption |
|
|
||||||
| `LOST_AND_FOUND` | Lost and Found - Used to automatically send a text message with current position at frequent intervals to the primary channel for the device: "I'm lost! Position: lat / long" |
|
|
||||||
|
|
||||||
#### Role Comparison
|
#### Role Comparison
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -0,0 +1,48 @@
|
||||||
|
---
|
||||||
|
id: update-techo-bootloader
|
||||||
|
title: How to Update the LilyGo T-Echo Bootloader to the Latest Version
|
||||||
|
sidebar_label: Update T-Echo Bootloader
|
||||||
|
sidebar_position: 5
|
||||||
|
---
|
||||||
|
|
||||||
|
If you're experiencing issues with updating or flashing newer versions of the Meshtastic firmware, and your LilyGo T-Echo is not running the latest bootloader version (0.6.1), updating the bootloader may resolve these problems.
|
||||||
|
|
||||||
|
To check which version of the bootloader your device is running, place the device into DFU mode by double-pressing the reset button. Then, open the mounted drive that appears on your computer and check the INFO_UF2.TXT file.
|
||||||
|
|
||||||
|
## Updating bootloader
|
||||||
|
|
||||||
|
Below are the steps to update your bootloader.
|
||||||
|
|
||||||
|
### Method 1: Using the UF2 File (Recommended)
|
||||||
|
|
||||||
|
1. Download the Latest UF2 Bootloader File for the T-Echo from [Github](https://github.com/meshtastic/firmware/blob/master/bin/update-lilygo_techo_bootloader-0.6.1_nosd.uf2).
|
||||||
|
2. Connect your LilyGo T-Echo to your computer via USB.
|
||||||
|
3. Activate bootloader mode by quickly double pressing the RESET button on your T-Echo. The device should appear as a removable drive on your computer.
|
||||||
|
4. Drag and drop the .uf2 file you downloaded into the T-Echo's drive. The device will automatically update the bootloader and reset.
|
||||||
|
5. Once the device resets, the update is complete. Your T-Echo is now running the latest bootloader version and you can proceed with [flashing the firmware](/docs/getting-started/flashing-firmware/nrf52/drag-n-drop/).
|
||||||
|
|
||||||
|
### Method 2: Using adafruit-nrfutil
|
||||||
|
|
||||||
|
Should flashing the UF2 file to update your bootloader fail, you can use adafruit-nrfutil.
|
||||||
|
|
||||||
|
:::info
|
||||||
|
|
||||||
|
These instructions assume you have python and pip already installed. If you do not, please install the latest verion of python (which includes pip) from [Python.org](https://www.python.org/downloads/).
|
||||||
|
|
||||||
|
:::
|
||||||
|
|
||||||
|
1. Open a terminal or command prompt and install adafruit-nrfutil by running:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
pip install adafruit-nrfutil
|
||||||
|
```
|
||||||
|
|
||||||
|
2. Obtain the lilygo_techo_bootloader-0.6.1.zip package from [Github](https://github.com/meshtastic/firmware/blob/master/bin/lilygo_techo_bootloader-0.6.1.zip).
|
||||||
|
3. Connect your LilyGo T-Echo to your computer via USB.
|
||||||
|
4. In the terminal or command prompt, navigate to the directory where you downloaded the bootloader zip package and execute the following command, replacing /dev/ttyACM0 with the correct port for your device (Windows users might use COMx):
|
||||||
|
|
||||||
|
```bash
|
||||||
|
adafruit-nrfutil --verbose dfu serial --package lilygo_techo_bootloader-0.6.1.zip -p /dev/ttyACM0 -b 115200 --singlebank --touch 1200
|
||||||
|
```
|
||||||
|
|
||||||
|
5. Once the process finishes, the update is complete. Your T-Echo is now running the latest bootloader version and you can proceed with [flashing the firmware](/docs/getting-started/flashing-firmware/nrf52/drag-n-drop/).
|
||||||
|
|
@ -51,7 +51,7 @@ Modular hardware system with Base, Core and Peripheral modules including the low
|
||||||
[RAK13002](./rak/peripherals?rakmodules=IO) IO<br/>
|
[RAK13002](./rak/peripherals?rakmodules=IO) IO<br/>
|
||||||
RAK14001 RGB LED<br/>
|
RAK14001 RGB LED<br/>
|
||||||
RAK12002 RTC<br/>
|
RAK12002 RTC<br/>
|
||||||
[RAK1910](./rak/peripherals?rakmodules=Sensors&sensors=RAK1901) Temperature and Humidity Sensor<br/>
|
[RAK1901](./rak/peripherals?rakmodules=Sensors&sensors=RAK1901) Temperature and Humidity Sensor<br/>
|
||||||
[RAK1902](./rak/peripherals?rakmodules=Sensors&sensors=RAK1902) Barometric Pressure Sensor<br/>
|
[RAK1902](./rak/peripherals?rakmodules=Sensors&sensors=RAK1902) Barometric Pressure Sensor<br/>
|
||||||
[RAK1906](./rak/peripherals?rakmodules=Sensors&sensors=RAK1906) Environment Sensor<br/>
|
[RAK1906](./rak/peripherals?rakmodules=Sensors&sensors=RAK1906) Environment Sensor<br/>
|
||||||
RAK12013 Radar Sensor<br/>
|
RAK12013 Radar Sensor<br/>
|
||||||
|
|
|
||||||
|
|
@ -1,5 +1,5 @@
|
||||||
import { Protobuf, Types } from "@meshtastic/js";
|
import { Protobuf, Types } from "@meshtastic/js";
|
||||||
import React, { useEffect } from "react";
|
import React, { useEffect, useState } from "react";
|
||||||
|
|
||||||
interface Region {
|
interface Region {
|
||||||
freqStart: number;
|
freqStart: number;
|
||||||
|
|
@ -273,18 +273,18 @@ const modemPresets = new Map<
|
||||||
|
|
||||||
export const FrequencyCalculator = (): JSX.Element => {
|
export const FrequencyCalculator = (): JSX.Element => {
|
||||||
const [modemPreset, setModemPreset] =
|
const [modemPreset, setModemPreset] =
|
||||||
React.useState<Protobuf.Config.Config_LoRaConfig_ModemPreset>(
|
useState<Protobuf.Config.Config_LoRaConfig_ModemPreset>(
|
||||||
Protobuf.Config.Config_LoRaConfig_ModemPreset.LONG_FAST,
|
Protobuf.Config.Config_LoRaConfig_ModemPreset.LONG_FAST,
|
||||||
);
|
);
|
||||||
const [region, setRegion] =
|
const [region, setRegion] =
|
||||||
React.useState<Protobuf.Config.Config_LoRaConfig_RegionCode>(
|
useState<Protobuf.Config.Config_LoRaConfig_RegionCode>(
|
||||||
Protobuf.Config.Config_LoRaConfig_RegionCode.US,
|
Protobuf.Config.Config_LoRaConfig_RegionCode.US,
|
||||||
);
|
);
|
||||||
const [channel, setChannel] = React.useState<Types.ChannelNumber>(
|
const [channel, setChannel] = useState<Types.ChannelNumber>(
|
||||||
Types.ChannelNumber.PRIMARY,
|
Types.ChannelNumber.Primary,
|
||||||
);
|
);
|
||||||
const [numChannels, setNumChannels] = React.useState<number>(0);
|
const [numChannels, setNumChannels] = useState<number>(0);
|
||||||
const [channelFrequency, setChannelFrequency] = React.useState<number>(0);
|
const [channelFrequency, setChannelFrequency] = useState<number>(0);
|
||||||
|
|
||||||
useEffect(() => {
|
useEffect(() => {
|
||||||
const selectedRegion = RegionData.get(region);
|
const selectedRegion = RegionData.get(region);
|
||||||
|
|
@ -344,6 +344,12 @@ export const FrequencyCalculator = (): JSX.Element => {
|
||||||
))}
|
))}
|
||||||
</select>
|
</select>
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
|
<div className="flex gap-2 mb-4">
|
||||||
|
<label className="font-semibold">Number of channels:</label>
|
||||||
|
<input type="number" disabled={true} value={numChannels} />
|
||||||
|
</div>
|
||||||
|
|
||||||
<div className="flex gap-2">
|
<div className="flex gap-2">
|
||||||
<label>Channel:</label>
|
<label>Channel:</label>
|
||||||
<select
|
<select
|
||||||
|
|
@ -358,10 +364,6 @@ export const FrequencyCalculator = (): JSX.Element => {
|
||||||
</select>
|
</select>
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
<div className="flex gap-2">
|
|
||||||
<label className="font-semibold">Number of channels:</label>
|
|
||||||
<input type="number" disabled={true} value={numChannels} />
|
|
||||||
</div>
|
|
||||||
<div className="flex gap-2">
|
<div className="flex gap-2">
|
||||||
<label className="font-semibold">Channel Frequency:</label>
|
<label className="font-semibold">Channel Frequency:</label>
|
||||||
<input type="number" disabled={true} value={channelFrequency} />
|
<input type="number" disabled={true} value={channelFrequency} />
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue