Go to file
Christian OE3CJB Bauer 86a5e6b87b install doc 2020-01-30 16:15:56 +01:00
img install doc 2020-01-30 16:15:56 +01:00
include LoRa APRS Tracker 2018-11-25 21:07:34 +01:00
lib LoRa APRS Tracker 2018-11-25 21:07:34 +01:00
src install doc 2020-01-30 16:15:56 +01:00
.gitignore LoRa APRS Tracker 2018-11-25 21:07:34 +01:00
.travis.yml LoRa APRS Tracker 2018-11-25 21:07:34 +01:00
INSTALL.md install doc 2020-01-30 16:15:56 +01:00
README.md release of Version 1.2 2020-01-02 20:13:30 +01:00
platformio.ini lots of new features :-) 2019-11-22 14:22:31 +01:00

README.md

First of all I want to thank OE1ACM Bernd for his approval to use his code for my experiments.
He is the author of BG_RF95!

If you want to discuss with other LoRa APRS interested persons join the growing community at the LoRa-APRS Telegram group

USER GUIDE of TTGO T-Beam LoRa APRS V1.2:
Attention: a new HW Version is available - if you use the old version uncomment "// #define T_BEAM_V0_7" and comment out "#define T_BEAM_V1_0".You can recognize the new Rev1.0-Boards at their three push buttons instead of two at the older boards - both versions are now supported.
As the new board only has two LEDs for the GPS and battery charger I've moved the TX Led to PIN 33 - please use a LED with reasonable resistor of 470R.

You can now do an immediate TX beacon if you press the key for 2secs - use this for testing purposes.

Callsign setting:
Now two possibilities are implemented:
1st) enter your callsign in the file TTGO_T-Beam_LoRa_APRS_config.h and replace the OE1XYZ-0 with your data with 6 characters plus SSID-
in case of shorter callsign use "SPACES" and extend up to total length of 6 characters
2nd) if you leave the config-file unchanged, you will run into a simple setup routine at the very first boot and you will be asked to enter your callsign and SSID(s).
Once the callsign is programmed you can reenter the programming mode by pressing the BUTTON for 5secs while switching on the tracker.

The MODE of the tracker can now be changed by pressing the button 10secs!
This can be done now without connected display but with a mounted TX LED.
The modes are
TRACKER ... LED blinks 1x - normal APRS tracker
WX&TRACKER ... LED blinks 2x - alternate transmission of normal position packet and WX packet (if DHT22 is mounted)
WX-MOVE ... LED blinks 3x - only WX packets are sent but with position from GPS
WX-FIXED ... LED blinks 4x - only WX packets are transmitted but with fixed position given in Header-File

The fixed position is used for a fixed weather station, e.g. without GPS signal.

Possible symbols are
Weather Station (1x blink), Car (2x blink), Runner (3x blink), Bicyle (4x blink), Motorcycle (5x blink)
The symbol can now be changed without attached display - during normal operation press the key for 3secs and you will enter the setup routine. The first value to set is now the symbol and the currently selected symbol is represented by blinks of the TX LED. Once the one needed blinks, just press the key for short moment. After that you will be asked if you want to continue the setup routine (which only makes sense with a connected display) or if you want to stop and so the new symbol will be stored in the NVS memory.
2x TX LED blinks represent "yes" to leave the setup - press here the key to leave the setup - please do so if you don't have a display attached.
1x TX LED blinks represent "no" to continue with the setup - press here the key to continue the setup - please do so if you have a display attached.

for DHT22 I used the library from https://github.com/beegee-tokyo/DHTesp, as the standard library gives to many wrong readings

new features:

  • immediate TX with short key press
  • course changes of >30° will cause a TX beacon
  • code optimized and cleaned
  • preset of callsign and SSID in file TTGO_T-Beam_LoRa_APRS_config.h --- this is the only you should change - if you are not familiar with programming ;-)
  • corrected format of speed, course and height to be shown correctly in aprs.fi and aprsdirect.com
  • Smart Beaconing - the maximum period can be set in the config-file - the minimum period is limited to 60sec, the calculation is based on speeds between 0 and 50 km/h, the default is smart beaconing is off with a minimium period setting of 60secs
  • usage of shorter callsigns is now also possible - fill up with SPACES up to 6 characters please
  • support of new power management chip AXP192