search

richonguzman / LoRa_APRS_Tracker

LoRa APRS Tracker with Tx and Rx capabilities, Messages, Wx, Winlink and more...
MIT License
168 stars 45 forks source link

Long TX on boot and manual TX on TTGO-T-BEAM #100

Closed wisp-engineer closed 1 month ago

wisp-engineer commented 1 month ago

Bug: On first boot after unit gets valid GPS signal, first TX takes ~35 seconds to complete, Not seen the unit do any further smart beaconing, doing a manual TX (central button short press) it does same where it takes 35s to TX

Expected behavior: Normally TX takes approx 2-5s on average

WhatsApp Image 2024-05-14 at 13 19 18_c874b2fe

Desktop OS: Win11 Pro PlatformIO Version: 1.89.1 Firmware Version: 14-05-2024

Board name: LILYGO TTGO T-BEAM-v1_2

Board has had a complete erase and rebuild, still present

richonguzman commented 1 month ago

this is very strange as I've been testing it here with V.1, V1.2, HELTEC WirelessTracker and other DIY boards and all handle it like a normal message

should we check in detail the filesystem configuration?

wisp-engineer commented 1 month ago

Sure, can send over a copy of the conf.json for what I used for the tracker - no other variables anywhere else were changed, e.g. open VSS, created fresh download, let it update platform.io "as normal" , once settled added in the adjusted variables where needed (callsign, comment etc) most of the other settings left to default certainly for Freq and smart beaconing

richonguzman commented 1 month ago

Sure, can send over a copy of the conf.json for what I used for the tracker - no other variables anywhere else were changed, e.g. open VSS, created fresh download, let it update platform.io "as normal" , once settled added in the adjusted variables where needed (callsign, comment etc) most of the other settings left to default certainly for Freq and smart beaconing

if you have telegram look for me (the same user as here on github) to see in detail your case

wisp-engineer commented 1 month ago

Issues now resolved, wiping / full erase of flash and rebuilding, leaving default "NOCALL-7" config on and building, then adding in "simple" fields like 1 callsign no other changes - upload, test, clear then add in the next conf changes e.g. comment and other secondary/tertiary SSID's with comments, then lastly "other" field for adding batteryinfo and changing from android to iphone

Issue no longer presented and was TX'ing at normal rate and being received on local igate showing raw packets and comments

thanks for input Ricardo for sense checking