kopia lustrzana https://github.com/lora-aprs/LoRa_APRS_iGate
readme changes
Peter Buchegger
rodzic
d9e6127d5c
commit
a96eab3652
59
README.md
59
README.md
|
|
@ -1,18 +1,24 @@
|
|||
# LoRa APRS iGate
|
||||
|
||||
|
||||
|
||||
[](https://app.codacy.com/gh/lora-aprs/LoRa_APRS_iGate?utm_source=github.com&utm_medium=referral&utm_content=lora-aprs/LoRa_APRS_iGate&utm_campaign=Badge_Grade_Dashboard)
|
||||
|
||||
The LoRa APRS iGate will work with very cheep hardware which you can buy from amazon, ebay or aliexpress.
|
||||
Try it out and be part of the APRS network.
|
||||
|
||||
**There is a german [quick start](https://www.lora-aprs.info/docs/LoRa_APRS_iGate/quick-start-guide/) page! Take a look ;)**
|
||||
|
||||
|
||||
|
||||
## Blog posts and Youtube videos from other Hams
|
||||
|
||||
* [OE1ROT](https://www.aronaut.at/2020/11/lora-aprs-gateway-mit-esp32-boards/) (blog post - german) 14.11.2020
|
||||
* [DL7AG](http://online.dl7ag.de/lora-aprs-dl7ag-10/) (blog post - german) 08.11.2020
|
||||
* [Manuel Lausmann - iGate](https://www.youtube.com/watch?v=C7hfVe32pXs) (youtube - german) 06.11.2020
|
||||
* [Manuel Lausmann - Tracker](https://www.youtube.com/watch?v=clIlTEFbWLk) (youtube - german) 02.11.2020
|
||||
* [OE1ROT](https://www.aronaut.at/2019/12/lora-aprs-tracker-mit-ttgo-t-beam-433mhz/) (blog post - german) 09.12.2019
|
||||
|
||||
## Supported boards
|
||||
|
||||
You can use one of the Lora32 boards without changings :
|
||||
You can use one of the Lora32 boards without changings:
|
||||
|
||||
* Heltec WiFi LoRa 32 V1 (433MHz SX1278)
|
||||
* Heltec WiFi LoRa 32 V2 (433MHz SX1278)
|
||||
|
|
@ -34,7 +40,9 @@ Here are some amazon-de links for some example boards:
|
|||
This boards cost around 20 Euros, they are very cheap and perfect for an LoRa iGate.
|
||||
Keep in minde: you need a 433MHz version!
|
||||
|
||||
## Compiling
|
||||
## Compiling and configuration
|
||||
|
||||
**There is a german [quick start](https://www.lora-aprs.info/docs/LoRa_APRS_iGate/quick-start-guide/) page! Take a look ;)**
|
||||
|
||||
### How to compile
|
||||
|
||||
|
|
@ -45,12 +53,42 @@ The best success is to use PlatformIO (and it is the only platform where I can s
|
|||
* When installed click 'the ant head' on the left and choose import the project on the right.
|
||||
* Just open the folder and you can compile the Firmware.
|
||||
|
||||
## Configuration
|
||||
### Configuration
|
||||
|
||||
* You can find all nessesary settings to change for your configuration in **data/is-cfg.json**.
|
||||
* To upload it to your board you have to do this via **Upload File System image** in PlatformIO!
|
||||
* To find the 'Upload File System image' click the PlatformIO symbol (the little alien) on the left side, choos your configuration, click on 'Platform' and search for 'Upload File System image'.
|
||||
|
||||
## Branches in this repository and version system
|
||||
|
||||
This Firmware is developed in a rolling release system: everyday a new release could be created. But there are still rules where new pull requests has to go and and how the version system looks like.
|
||||
|
||||
### Branches
|
||||
|
||||
There are 2 main branches:
|
||||
* *master* and
|
||||
* *develop*
|
||||
|
||||
The *master* branch has all releases and is the most stable one. With the different tags you can jump to different versions or if you take the most current master branch you will just get the last version. There will be no side releases which are branch of from master. If there is a bugfix version it will be done directly on the master branch and a tag will be generated with a new version.
|
||||
|
||||
The *develop* branch is used for new feature development. It will be also used to stabilize the current development to create a new stable version (merge request to *master* branch). **Again:** all new development (pull requests) has to go directly into the *develop* branch!
|
||||
|
||||
### Version system
|
||||
|
||||
If the *develop* branch is stable enough for a new release it will be merged with a pull request to the *master* branch and a new version will be generated.
|
||||
|
||||
The versions are based on this settings:
|
||||
* major: the current year (2 digits)
|
||||
* minor: the current week of the year
|
||||
* patch: if there is a patch for an release, just increment the number, otherwise 0
|
||||
|
||||
*example*: a new release will be created on the 11/14/2020, this version numbers will be used:
|
||||
* major: 20
|
||||
* minor: 46
|
||||
* patch: 0
|
||||
|
||||
so the version will be: 20.46.0
|
||||
|
||||
## Future plans
|
||||
|
||||
* [x] show time until next beaconing
|
||||
|
|
@ -72,7 +110,7 @@ Look at my other project: a [LoRa Tracker](https://github.com/peterus/LoRa_APRS_
|
|||
|
||||
### Here are some peculiarities of the different boards
|
||||
|
||||
* TTGO T-Beam V1
|
||||
* TTGO T-Beam V1
|
||||
|
||||
When adding a 0,96" OLED display direct to the board you have to be careful, there are two different pinout
|
||||
versions on the market.
|
||||
|
|
@ -81,10 +119,3 @@ A direct mount of the [other display](pics/display-wrong.jpg) is not possible wi
|
|||
The 'wrong' display works too but you have to change VCC and GND by wire !
|
||||
|
||||
feel free to add hints!
|
||||
|
||||
## Blog posts and Youtube videos from other Hams
|
||||
|
||||
* [OE1ROT](https://www.aronaut.at/2020/11/lora-aprs-gateway-mit-esp32-boards/)
|
||||
* [DL7AG](http://online.dl7ag.de/lora-aprs-dl7ag-10/)
|
||||
* [Manuel Lausmann - Tracker](https://www.youtube.com/watch?v=clIlTEFbWLk)
|
||||
* [Manuel Lausmann - iGate](https://www.youtube.com/watch?v=C7hfVe32pXs)
|
||||
|
|
|
|||
Ładowanie…
Reference in New Issue