Update README.md

README.md

@@ -38,8 +38,13 @@ All work was done on ESP32-WROOM with custom made LoRa shield, if your ESP32 boa
 - uses LoRa **built-in checksum** calculation to drop broken packets
 - 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 **LORAPRS_FREQ**, 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
+  - 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
+ - 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
+   - **[INACTIVE YET]** `cfg.EnableIsToRf` set to `true` to forward APRS-IS traffic to RF
+   - **[INACTIVE YET]** `cfg.EnableRepeater` set to `true` to enable packet repeater
 
 # Test Results
 ![alt text](images/setup.png)