TTGO-T-Beam-LoRa-APRS

WiFi Settings

Enable Wifi

Network

WiFi SSID

WiFi Password

TXPWR as STA

AUTO AP Password

TXPWR as AP

NTP Server

Enable TNC-Server

Enable GPS-Server

APRS Settings

Transmission Settings

Main Frequency [MHz]

Speed

Enable LoRa transmitter

Enable LoRa receiver

TX power [dBm]

Automatic CodeRate adaption on TX

Filter src-calls or calls in digipath on receiption

Add SNR and RSSI to path. '*': only if heard direct (recommended for many usecases). '~': not recommended; better let user decide with Q-addressing

More info for SNR/RSSI path encoding see documentation section below

SNR/RSSI-encoding on kiss: compatible to APRS-IS?

Station Settings

Callsign and SSID

Relay Path

Symbol Table

Symbol

Altitude ratio [%]

Send Course/Speed along with Altitude

Show Comment

Ratelimit adding comment text

Comment

Show Battery

Telemetry Settings

Enable Self Telemetry

Self Telemetry Interval [s]

Self Telemetry Sequence

Self Telemetry Relay Path

Fixed Beaconing Settings

Fixed Beacon

Fixed Beacon Interval [s]

Latitude

Longitude

Smart Beaconing Settings

Min interval [s]

Max interval [s]

Min speed [km/h]

Max speed [km/h]

Course change [degrees]

Turn Slope [degrees]

Turn Time [seconds]

GPS enabled

Accept own positions via KISS

Allow GPS sleep while own positions received via KISS

Additional settings for secondary frequency:
EXPERIMANTAL - USE WITH CARE!

Secondary Frequency [MHz] (for cross-repeating or listening transmissions from igates)

TX power on secondary frequency [dBm]

Speed on secondary frequency

RX on frequencies (Only honored, if we are NOT configured as WIDE1 or WIDE2 digi. If set to both frequencies: Ratio depends on how many packets are received on each qrg in a 10min window; we stay 20s on one qrg.)

Current RX Frequency:

Additional settings for mode repater:
EXPERIMANTAL - USE WITH CARE!

LoRa Repater Mode

Digipeat heard stations from MAIN frequency to which frequencies (If LoRa Repeater Mode has not been set to off)

TX our beacon from this device or from-kiss to frequencies (Only honored, if we are configured as WIDE1 or WIDE2 digi)

APRS-IS settings

Enable APRS-IS connection

Server Name

TCP Port

Callsign (optional)

Password (required)

Filter (optional)

TX our beacon to APRS-IS

Gate APRS-IS traffic to frequencies (Will be '3rd-party encoded'. Be careful - do not flood our slow main frequency! Use filters..)

Connection status

Device Settings

OLED Display enabled

Bluetooth enabled

LED signaling

Adjust CPU frequency (MHz)

Reboot every n hours

Auto power off

Auto power off delay [s]

Display show RX time [s]

Display timeout [s]

Current Position

Uptime of Device [min]

Satellite & Batt Info

Received

Time (UTC)	Frame	RSSI	SNR

Actions

Update

Click here to view your configuration.

Documentation

Tooltip

If you navigate your mouse over an input field / button, you see a detailed description what it does / which values are expected.

Info for SNR/RSSI path encoding

If enabled, add SNR and RSSI in path on receiption, prefixed with 'Q'. Examples:
SNR 23 RSSI -73 -> Q2373
SNR -03 RSSI -104 -> QA3K4
SNR -13 RSSI -114 -> QB3L4
Still testing, if it behaves good to our network.
Use with care; resulting longer path consumes a bit more airtime.

User key functions (hardware buttons):

short press

If OLED is enabled and OLED is OFF:

a short press will wake it up and show current data (as "Display Timeout" seconds

If OLED is disabled or OLED is ON:

with GPS-FIX immediate sending of a frame with the position from the GPS
without GPS-FIX, immediate sending of the frame with the position saved in the configuration

long press

toggle on or off WiFi and WebServer

Tips for reducing power (Usage as tracker only):

WiFi OFF

be aware, that aprs-is connection depends on the Webserver and will stop working). Hack: long-pressing the (GPS) button switches ON/OFF the GPS. When switching GPS ON, the webserver-config is also set to value 1
select option 0 to disable WiFi & APRS-IS
select option 1 to disable WiFi if a bluetooth client is connected in between 60s on boot (recommended for portables, and for LORA32_21 devices)

LoRa Receiver OFF:

reduces power consumption, if you just use the device as a tracker

Fixed Beacon off:

Smart Beaconing is activated, if there is no fixed beacon

Hardware notices

TTGO LoRa32 V2.1 (aka T3 V1.6.1)

Hardware limitation: if bluetooth is enabled and BT-client is connected, WIFI (-> Web-Server) does not work anymore.
You'll see the red LED while booting turned on for 60s as indicatior for waiting for BT-clients. Hack: firmware compiled with -e ttgo-lora32-v2.1 and bluetooth configuration variable is set to enabled, now listens on boot up to one minute for your bluetooth device to connect.
If a bluetooth device connects, it does not start the Web-Server. Else, it closes SerialBT port and starts the Web-Server on LORA32_21 devices.
See also: new feature for switching WIFI off (i.e. if you use the device as portable tracker), if you don't need it: Webserver eats abt 80mA..
How to switch the Webserver on again, please read the long-press button (GPS) section.