kopia lustrzana https://github.com/sh123/esp32_loraprs
Updated README
sh123
commit
1c421e5269
53
README.md
53
README.md
|
|
@ -1,17 +1,25 @@
|
|||
# LoRa APRS ESP32 APRSDroid bluetooth modem, LoRa APRS-IS RX/TX iGate with digirepeater
|
||||
Amateur radio ESP32 based LoRa APRSDroid KISS Bluetooth modem, LoRa APRS-IS RX/TX iGate server over WiFI plus digirepeater
|
||||
|
||||
|
||||
# LoRa APRS ESP32 KISS APRSDroid bluetooth modem, LoRa APRS-IS RX/TX iGate with digipeater
|
||||
Amateur radio ESP32 based LoRa APRSDroid KISS Bluetooth modem + LoRa APRS-IS RX/TX iGate server over WiFI + digipeater
|
||||
|
||||
Can be used in two modes:
|
||||
- **as a LoRa APRS client**, you need to use APRSDroid application (https://aprsdroid.org), connect to the modem using bluetooth, data will be re-transmitted through the LoRa radio, this is similar to APRSDroid micromodem - https://unsigned.io/micromodem/, received data will be sent back to the APRSDroid using bluetooth. By having two clients you can not only send your position, but also send and receive APRS messages.
|
||||
- **as a LoRa APRS iGate server**, which connects to your WiFI and forwards received LoRa APRS positions into the APRS-IS network, it also reports client signal level, by appending it into the APRS comment, so you can see your signal reports in different locations (could be enabled or disabled). It also supports:
|
||||
- **APRS-IS to RF gating**, so it is possible to enable it together with the filter in the config
|
||||
- **LoRa APRS KISS client over bluetooth**
|
||||
- you need to use **APRSDroid** application (https://aprsdroid.org), connect to the modem using bluetooth, data will be re-transmitted through the LoRa radio, this is similar to APRSDroid micromodem - https://unsigned.io/micromodem/, received data will be sent back to the APRSDroid using bluetooth. By having two clients you can not only send your position, but also send and receive APRS messages
|
||||
- it is also possible to use **other KISS APRS clients** over Bluetooth serial, just use `rfcomm` on Linux to setup serial over Bluetooth and put up AX25 interface with `kissattach`, then use any existing Linux APRS clients, such as `Xastir` or even run `TCPIP` over AX25
|
||||
- **LoRa APRS iGate RX/TX server over WiFi + Digipeater**
|
||||
- **RF to APRS-IS gating**, it will connect to your WiFI and will forward received APRS positions from RF LoRa into the APRS-IS network, it also reports client signal level, by appending it into the APRS comment, so you can see your signal reports in different locations (could be enabled or disabled from config). This way, it is also possible to setup portable iGate by connecting to your mobile phone's hotspot and provide power from the phone USB port by using OTA cable
|
||||
- **APRS-IS to RF gating**, it is possible to enable it together with the filter in the config, so APRS-IS data will be forwarded to RF
|
||||
- **RF digirepating** for `WIDEn-n`, `TRACEn-n` new style paths, for `TRACE` will insert own callsign before digipeating
|
||||
- Own station periodic beacon announcement to APRS-IS and RF
|
||||
- **Beaconing**, own station periodic beacon announcement to APRS-IS and RF
|
||||
|
||||
# Compatible Boards
|
||||
All work was done on ESP32-WROOM with custom made LoRa shield, if your ESP32 board is compatible then it should work, but there might be need to redefine pinouts to LoRa module if it differs (see further description in Software Setup section)
|
||||
All work was done on ESP32-WROOM with custom made LoRa shield, if your ESP32 board is compatible then it should work, but there might be need to redefine pinouts to LoRa module if it differs (see further description in Software Setup section), currently pinouts are connected from LoRa to ESP32-WROOM as (SS/RST/DIO0 could be redefined in loraprs_service.h):
|
||||
|
||||
- SS: GPIO_5
|
||||
- RST: GPIO_26
|
||||
- DIO0: GPIO_14
|
||||
- MOSI: GPIO_23/VSPI_MOSI
|
||||
- MISO: GPIO_19/VSPI_MISO
|
||||
- SCK: GPIO_18/VSPI_SCK
|
||||
|
||||
# Software Dependencies (install via libraries)
|
||||
- Arduino ESP32 library: https://github.com/espressif/arduino-esp32
|
||||
|
|
@ -24,25 +32,25 @@ All work was done on ESP32-WROOM with custom made LoRa shield, if your ESP32 boa
|
|||
- set `cfg.IsClientMode` to `false` if you are planning to run server mode for APRS-IS iGate / Digipeater
|
||||
- for server mode fill `cfg.WifiSsid` and `cfg.WifiKey` with your WiFI AP data
|
||||
- for server mode fill `cfg.AprsLogin` and `cfg.AprsPass` with APRS-IS login callsign and pass
|
||||
- for server mode fill `cfg.AprsFilter`, see http://www.aprs-is.net/javAPRSFilter.aspx for various formats
|
||||
- for server mode fill `cfg.AprsFilter`, see http://www.aprs-is.net/javAPRSFilter.aspx for various formats, do not include `filter` directive, just space separated values
|
||||
- change `cfg.LoraFreq` if you are planning to use different frequency or if planning to calibrate clients, currently it is set to **433.775MHz** as per https://vienna.iaru-r1.org/wp-content/uploads/2019/01/VIE19-C5-015-OEVSV-LORA-APRS-433-MHz.pdf
|
||||
- if you are planning to use different esp32 pinouts then modify loraprs.h
|
||||
- lora module SS, **CfgPinSs**, pin 5
|
||||
- lora module RST, **CfgPinRst**, pin 26
|
||||
- lora module DIO0, **CfgPinDio0**, pin 14
|
||||
- if you are planning to experiment with different bandwidths/spread factors then modify loraprs.h, with current parameters APRS packet time on air is around **2 seconds** to decode with as lower level as possible, use https://github.com/tanupoo/lorawan_toa to make calculations
|
||||
- lora bandwidth `cfg.LoraBw`, 125 kHz
|
||||
- if you are planning to use different esp32 pinouts then modify loraprs_service.h
|
||||
- lora module SS, **CfgPinSs**, GPIO_5
|
||||
- lora module RST, **CfgPinRst**, GPIO_26
|
||||
- lora module DIO0, **CfgPinDio0**, GPIO_14
|
||||
- if you are planning to experiment with different bandwidths/spread factors then modify values in `initializeConfig()`, with current parameters APRS packet time on air is around **2 seconds** to decode with as lower level as possible, use https://github.com/tanupoo/lorawan_toa to make calculations
|
||||
- lora bandwidth `cfg.LoraBw`, 125 kHz (also tested with 20.6 KHz and SF9 with frequency correction)
|
||||
- lora spread factor `cfg.LoraSf`, 12 (should decode down to -20dB, choosen with the goal for minimum signal decode)
|
||||
- lora coding rate `cfg.LoraCodingRate`, 7
|
||||
- lora output power `cfg.LoraPower`, 20 (max 20 dBm ~ 100mW, change to lower value if needed)
|
||||
- sync word `cfg.LoraSync`, 0x3f
|
||||
- consider minimum decode level based on on BW + SF 
|
||||
- consider minimum decode level based on on BW + SF and required throughput 
|
||||
- use 80 MHz ESP32 frequency in Arduino SDK, it will prolong battery life when operating portable, higher CPU speed is not required, there are no CPU intensive operations
|
||||
- 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 `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 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
|
||||
- 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. Use it either on client side to tune all clients to server frequency if TX is enabled on iGate side or to tune server to single client for test purposes
|
||||
- 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
|
||||
|
|
@ -54,21 +62,24 @@ All work was done on ESP32-WROOM with custom made LoRa shield, if your ESP32 boa
|
|||
# Test Results
|
||||
|
||||
- Antennas
|
||||
- Client: rubber duck antenna or mobile antenna on a car roof
|
||||
- Server: 7 element UHF yagi indoors
|
||||
- Client: rubber duck, halo, mobile antenna on a car roof
|
||||
- Server: 7 element UHF yagi indoors, vertical on the roof
|
||||
- With such low power it is very important to have antenna SWR close to 1, many rubber duck antennas are claimed to be 433MHz, but they do not resonate at that frequency at all or resonate only when attached to its native large handheld transceiver, which has enough metal inside to behave like a counterpoise, these antennas have SWR 2 or higher. Check your antenna on antenna analyzer before using, add counterpoise if needed or better to use dipole or halo home made antenna for that matter
|
||||
- Range (20 KHz channel width and 9 spreading factor, also got similar results with 125 kHz and 12 SF)
|
||||
- **About 7 km** when server is 30m above the ground and client is 2m above the ground with rubber duck antenna or inside a car
|
||||
- **About 13 km** when server is 30m above the ground and client is at some higher point ~40m above the ground with rubber duck antenna
|
||||
- **About 17km** maximum (non-reliable) between base and mobile station with antenna on the car roof
|
||||
- **About 20km** over the sea between base and handheld
|
||||
- Signal levels
|
||||
- Successful decodes down to **-19.75dB** below the noise floor when using compressed APRS coordinates (smaller packets, about 50 bytes, 32 bytes without PATH, speed, altitude), see APRSDroid discussions on compressed corrdinates support and custom branches
|
||||
- Successful decodes down to **-19.75dB** below the noise floor when using compressed APRS coordinates (smaller packets, about 50 bytes, **32 bytes without PATH, speed, altitude**), see APRSDroid discussions on compressed corrdinates support and custom branches
|
||||
- https://github.com/ge0rg/aprsdroid/pull/159
|
||||
- https://github.com/ge0rg/aprsdroid/issues/170
|
||||
- https://github.com/sh123/aprsdroid/tree/aprsdroid_compressed
|
||||
- https://github.com/sh123/aprsdroid/tree/aprsdroid_compressed_gradle
|
||||
- Polarization
|
||||
- Using **horizontal polarization** improves successful decoding probability and receiving range
|
||||
- Interference
|
||||
- Monitor your planned frequency, such as 433.775 MHz for ISM device activity, if there is strong interference from other users tune up or down it to minimize interference
|
||||
- Weather
|
||||
- Rain and high humidity levels decrease signal level by about **~3-6 dB**
|
||||
|
||||
|
|
|
|||
|
|
@ -28,8 +28,8 @@ void initializeConfig() {
|
|||
cfg.AprsPort = 14580;
|
||||
cfg.AprsLogin = "NOCALL-10";
|
||||
cfg.AprsPass = "12345";
|
||||
cfg.AprsFilter = "r/35.60/139.80/25";
|
||||
cfg.AprsRawBeacon = "NOCALL-10>APZMDM,WIDE1-1:!0000.00N/00000.00E#LoRa 433.775MHz/BW125/SF12/CR7/0xf3";
|
||||
cfg.AprsFilter = "r/35.60/139.80/25"; // multiple filters are space separated
|
||||
cfg.AprsRawBeacon = "NOCALL-10>APZMDM,WIDE1-1:!0000.00N/00000.00E#LoRA 433.775MHz/BW125/SF12/CR7/0x3f";
|
||||
cfg.AprsRawBeaconPeriodMinutes = 20;
|
||||
|
||||
// bluetooth device name
|
||||
|
|
@ -40,7 +40,7 @@ void initializeConfig() {
|
|||
cfg.WifiKey = "<wifi key>";
|
||||
|
||||
// configuration flags and features
|
||||
cfg.EnableAutoFreqCorrection = true; // automatic tune to any incoming packet frequency
|
||||
cfg.EnableAutoFreqCorrection = false; // automatic tune to any incoming packet frequency
|
||||
cfg.EnableSignalReport = true; // signal report will be added to the comment sent to aprsis
|
||||
cfg.EnablePersistentAprsConnection = true; // keep aprsis connection open, otherwise connect on new data only
|
||||
cfg.EnableRfToIs = true; // send data from rf to aprsis
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ struct Config
|
|||
String AprsHost; // aprs server hostname, rotate.aprs2.net
|
||||
String AprsLogin; // aprs callsign to use, e.g. MY0CAL-1
|
||||
String AprsPass; // aprs login password
|
||||
String AprsFilter; // aprs filter, see http://www.aprs-is.net/javAPRSFilter.aspx
|
||||
String AprsFilter; // aprs filter, see http://www.aprs-is.net/javAPRSFilter.aspx, do not include filter directive, just space separated values
|
||||
String AprsRawBeacon; // aprs string for server beacon, e.g. NOCALL-1>APZMDM,WIDE1-1:!0000.00N/00000.00E#LoRA 433.775MHz/BW125/SF12/CR7/0xf3
|
||||
int AprsRawBeaconPeriodMinutes; // aprs beacon period
|
||||
|
||||
|
|
|
|||
Ładowanie…
Reference in New Issue