From 7daa8393abade25c94b5aca693138005e151e6da Mon Sep 17 00:00:00 2001 From: sh123 Date: Mon, 1 Feb 2021 09:30:47 +0200 Subject: [PATCH 1/6] Update README.md --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index ada68d0..f9019c7 100644 --- a/README.md +++ b/README.md @@ -79,7 +79,9 @@ Install via libraries: - `cfg.EnableBeacon` set to `true` to enable periodic beacons specified in `cfg.AprsRawBeacon` with period specified in `cfg.AprsRawBeaconPeriodMinutes` into RF and APRS-IS if `cfg.EnableRfToIs` is enabled # Protocol Compatibility -This project is using classical `AX25` frames over LoRa (as defined in http://www.aprs.org/doc/APRS101.PDF page 12) with given LoRa parameters above and `AX25` frames are encapsulated into `KISS` frames when transferred over serial Bluetooth to phone or PC. It should enable interoperability with classical Linux APRS software and `kissattach`. Some LoRa ARPS implementations transfer plain text APRS messages over LoRa, as a result interoperability with this project is not guaranteed. +- Make sure LoRa sync word and other LoRa parameters match +- **Client** should be interoperable with other clients, which transmit raw text aprs messages, in this case select "TNC (plaintext TNC2)" in APRSDroid protocol options +- **Server** is using classical `AX25` frames over LoRa (as defined in http://www.aprs.org/doc/APRS101.PDF page 12) with given LoRa parameters above and `AX25` frames are encapsulated into `KISS` frames when transferred over serial Bluetooth to phone or PC. It should enable interoperability with classical Linux APRS software and `kissattach`. Some LoRa ARPS implementations transfer plain text APRS messages over LoRa, as a result **Server** interoperability with this project is not guaranteed # 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: From d54d4d491b30b1977af6a809330362e47eb2915d Mon Sep 17 00:00:00 2001 From: sh123 Date: Mon, 1 Feb 2021 09:34:49 +0200 Subject: [PATCH 2/6] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f9019c7..f4b8dac 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, in this case select "TNC (plaintext TNC2)" in APRSDroid protocol options -- **Server** is using classical `AX25` frames over LoRa (as defined in http://www.aprs.org/doc/APRS101.PDF page 12) with given LoRa parameters above and `AX25` frames are encapsulated into `KISS` frames when transferred over serial Bluetooth to phone or PC. It should enable interoperability with classical Linux APRS software and `kissattach`. Some LoRa ARPS implementations transfer plain text APRS messages over LoRa, as a result **Server** interoperability with this project is not guaranteed +- **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 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. Support for plaintext APRS would be added at some point. # 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: From 21c7679fa58c42d1ad5e14cf93765b6fa0fee218 Mon Sep 17 00:00:00 2001 From: sh123 Date: Mon, 1 Feb 2021 09:36:00 +0200 Subject: [PATCH 3/6] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f4b8dac..5eaae0f 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, in this case select "TNC (plaintext TNC2)" in APRSDroid protocol options -- **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 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. Support for plaintext APRS would be added at some point. +- **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, suchas 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. # 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: From 20df297119c20fbee9f96e84ab496182b265dcbb Mon Sep 17 00:00:00 2001 From: sh123 Date: Mon, 1 Feb 2021 09:36:45 +0200 Subject: [PATCH 4/6] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 5eaae0f..72ea676 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, in this case select "TNC (plaintext TNC2)" in APRSDroid protocol options -- **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, suchas 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. Server support for plaintext APRS messages is planned. # 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: From d4cd19fb71095ff2bb7cfd59e42743bcebb89248 Mon Sep 17 00:00:00 2001 From: sh123 Date: Mon, 1 Feb 2021 09:57:45 +0200 Subject: [PATCH 5/6] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 72ea676..b05e154 100644 --- a/README.md +++ b/README.md @@ -80,7 +80,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, in this case select "TNC (plaintext TNC2)" in APRSDroid protocol options +- **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. # Alternative Linux Setup From 480c8197b87add06c1ed19712a2e122c9fc96590 Mon Sep 17 00:00:00 2001 From: sh123 Date: Mon, 1 Feb 2021 10:40:07 +0200 Subject: [PATCH 6/6] 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: