oe3cjb / ttgo-t-beam-lora-aprs Goto Github PK

Just updated to e2077e4, THANK YOU so much for adding pressure to the weather data!

I have been using 'WX_TRACKER' mode so that every-other TX would include battery voltage. But in hopes of prolonging battery life, switched to 'WX_FIXED' mode to turn off the GPS.

I would still very much like to see battery voltage in the telemetry, and discovered:

#define HW_COMMENT // send Alt und Battery Voltage, UNcomment if you want to send it

... so with that UNcommented, I was hoping to see battery voltage in the APRS message.

Unfortunately, while MY_COMMENT text comes through fine, I never see any mention of battery voltage.

Here is how my messages are appearing on APRS-IS:

2021-05-30 14:05:15 EDT: K4KDR-13>APRS,qAS,K4KDR-14:!3746.70N/07736.55W_.../...g...t069r...p...P...h59b10223_433.775 LoRa APRS + WX

... am I missing a step, or not understanding the proper use of HW_COMMENT?

For reference, when I was using 'WX_TRACKER' mode, the battery voltage was reported perfectly under SSID 'K4KDR-4'.

2021-05-29 20:12:45 EDT: K4KDR-4>APRS,qAS,K4KDR-14:!/;E4O:pzU_!!H/A=000274 Batt=3.50V_433.775 LoRa APRS + WX

Thank you VERY much for any assistance!

-Scott, K4KDR

Hi, I was wondering about the on-the-wire-format of LoRa packets containing APRS.

It looks like this code is generating the header, consisting of:

• verbatim "<"
• sender's ID (byte) - is that ever initialized anywhere?
• 0x01 byte

What is the meaning of the "<" and of the 0x01? It looks like the regular LoRa header is four bytes (to, from, ID, flags) - why is the APRS header shorter? Why are we not using to=0xff (broadcast)?

Hi, i got plenty of T-Beam around, and i'm wondering if it's possible to attach more the one DS18b20 probe like we do on ESP Easy.
Either on different Gpio nor same one as a daisy chain (1Wire)
I need to monitor several temps around the Node .

Thanks in advance

Hi, When I set Tracker mode setting to 1, 2 or 3 it boots up in mode Tracker (=0). Set #define DONT_USE_FLASH_MEMORY on or off has no effect. It boots in Tracker mode (no WX). Only when I push the middle button on my V1 T-Beam (no Oled) for 10 Seconds I see it switching (in the terminal screen) to WX-Tracker and WX report becomes visible in APRS.fi. But when I restart the T-Beam by plug in the power, it boots up in Tracker mode (no WX).

(PA1SDB-7 iGate - PA1SDB-9 mobile - PA1SDB-8 WX)

73s Peter

Hello Christian,
In advance I was able to show you that the T-Beam did boot up in "Tracker / WX mode". Terminal data did show that, and indeed the WX broadcast did pop up in APRS.fi. Unfortunately the Tracker broadcast does not show up anymore. It does show up when I set Tracker mode to 0.

So:
PA1SDB-9 tracker is silence
PA1SDB-8 WX transmits every 15 minutes.

#define DONT_USE_FLASH_MEMORY
#define TRACKERMODE 1
#define CALLSIGN "PA1SDB-9"
#define WX_CALLSIGN "PA1SDB-8"
#define LONGITUDE_PRESET "0651,18E"
#define LATIDUDE_PRESET "5319.14N"
#define APRS_SYMBOL ">"

73s Peter

Just found this multisensor board, would be nice to implement it into software.

Dear Christian,
I try to flash some of the new T-Beam boards with the new Powerchip.
All boards not working anymore.
They hang up while try to TX.
Any idea whats the issue?
Regards Dan DL6OW

An option would be great to use the chosen APRS_SYMBOL with normal callsign while using WX-Tracker Mode and use only WX SSID and WX symbol while using WX_Move and WX_Fixed

Hi, by using GPIO 4 the onboard LED can be used for TX LED and an external LED can be connected, too. Rev. 1

Hi, is it possible to decode the received coordinates and show them in the displaytext?

Hallo Christian, ich habe nur eine kleine Änderung, damit es ein paar weniger warnungen gibt...just refactoring
TTGO_T-Beam_LoRa_APRS.zip