From 480c8197b87add06c1ed19712a2e122c9fc96590 Mon Sep 17 00:00:00 2001 From: sh123 Date: Mon, 1 Feb 2021 10:40:07 +0200 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index b05e154..10b0004 100644 --- a/README.md +++ b/README.md @@ -81,7 +81,7 @@ Install via libraries: # Protocol Compatibility - Make sure LoRa sync word and other LoRa parameters match - **Client** should be interoperable with other clients, which transmit raw text APRS messages if bluetooth client sends them in this format to the modem -- **Server** supports only classical `AX25` frames over LoRa (as defined in http://www.aprs.org/doc/APRS101.PDF page 12). It should enable interoperability with classical Linux APRS software, such as Xastir with `kissattach`. Some LoRa ARPS implementations transfer plain text APRS messages over LoRa, as a result **Server** will not be able to process these messages and gate them to APRS-IS, also clients won't be able to decode messages gated from APRS-IS to RF by the server. Server support for plaintext APRS messages is planned. +- **Server** supports only classical `AX25` frames over LoRa (as defined in http://www.aprs.org/doc/APRS101.PDF page 12). It should enable interoperability with classical Linux APRS software, such as Xastir with `kissattach`. Some LoRa ARPS implementations transfer plain text APRS messages over LoRa, as a result **Server** will not be able to process these messages and gate them to APRS-IS, also clients won't be able to decode messages gated from APRS-IS to RF by the server # Alternative Linux Setup It is possible to use modem **in client mode** with other generic Linux ax25/aprs tools, such as `xastir`, use next procedure to set it up: