kopia lustrzana https://github.com/sh123/esp32_loraprs
Update README.md
rodzic
21c7679fa5
commit
20df297119
|
@ -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:
|
||||
|
|
Ładowanie…
Reference in New Issue