From c042747fff1ab96b913709bfacf886371019ded5 Mon Sep 17 00:00:00 2001 From: sh123 Date: Sun, 14 Jun 2020 01:29:18 +0300 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index faeb750..14b65ae 100644 --- a/README.md +++ b/README.md @@ -39,7 +39,7 @@ All work was done on ESP32-WROOM with custom made LoRa shield, if your ESP32 boa - note, that there a is **significant frequency drift** on temperature changes for different modules - you need to use **external TCXO** if you are planning to use modules for narrow bandwidths less than 125 kHz - or calibrate clients based on server frequency drift report by changing `cfg.LoraFreq`, for example, let client and server run for an 30-60 minutes and if server reports err: -1500, then set client frequency to about 1000 kHz less, e.g. instead of 433.775 set it to 433.774, this will give couple of additional dB - - alternatively automatic calibration could be done on server side by enabling automatic frequency correction by setting `cfg.EnableAutoFreqCorrection` to **true**, might be suitable for experiments where only one client is operating + - alternatively automatic calibration could be done on server or client side by enabling automatic frequency correction by setting `cfg.EnableAutoFreqCorrection` to **true**, might be suitable for experiments where only one client is operating or if server broadcast messages, so clients can correct their frequency - other useful options are - `cfg.EnableSignalReport` set to `true` to enable signal report, it will be added as a comment to APRS-IS submitted location - `cfg.EnablePersistentAprsConnection` set to `false` to avoid keeping connection open to APRS-IS