-
-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v22.46.0 & v22.20.0 not working with TBeam v1.0 on 33cm #228
Comments
Hi Doug, I have an iGate/Digi up for LoRa APRS on 70cm to complement 2m and am just starting to set up for 33cm. I saw you have a couple nodes up already advertising 33cm operation. There seems to be some consensus for 70cm LoRa APRS, but I did not see any clear standards for 33cm except to copy the non-ham stuff. What frequency and LoRa config are you running? Although our coverage is far apart, maybe if we follow/create a standard, anyone in between can follow suit. Once I get this up on the Heltec, I will try the TBeam. I already have APRS loaded on a T-Echo, but won't know if it is working right until I get the next one loaded. I will let you (and Peter) know if I find any bugs. 73 de W1OT |
I set my frequency to 915.775Mhz. As far as the config. Everything is the
same as 70cm. I wanted to keep it simple for converting from one band to
another.
Good luck!! 73
…On Mon, Jul 29, 2024, 3:38 PM Ken Chilton ***@***.***> wrote:
Hi Doug,
I have an iGate/Digi up for LoRa APRS on 70cm to complement 2m and am just
starting to set up for 33cm. I saw you have a couple nodes up already
advertising 33cm operation. There seems to be some consensus for 70cm LoRa
APRS, but I did not see any clear standards for 33cm except to copy the
non-ham stuff. What frequency and LoRa config are you running? Although our
coverage is far apart, maybe if we follow/create a standard, anyone in
between can follow suit.
Once I get this up on the Heltec, I will try the TBeam. I already have
APRS loaded on a T-Echo, but won't know if it is working right until I get
the next one loaded. I will let you (and Peter) know if I find any bugs.
73 de W1OT
—
Reply to this email directly, view it on GitHub
<#228 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AX7AIB56HRYX2AXEROY6FW3ZO2K3NAVCNFSM6AAAAABLU5JZDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJWG42TINZUGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I tried updating my TBeams today and discovered an odd behavior .
I have two pairs of TBeams: One pair on 70cm and another pair on 33cm:
I-Gate v22.14.0 and Tracker v22.19.0 - Everything works fine on both pairs.
Updated both pairs to:
I-Gate v22.46.0 - 33cm doesn't working
- 70cm works fine
Downgraded the I-Gate on the 33cm I-Gate back to v22.14.0 - Works fine.
Updated the I-Gate to v22.20.0 - Doesn't work.
Again, downgraded the I-Gate on the 33cm back to v22.14.0 - Works fine.
This is the problem I am seeing. The I-Gate doesn't receive the Tracker's beacons. I am using the exact same JSON configuration across the different versions. The I-Gate will log on to the APRS servers and report it's status.
During the upgrade/downgrade process. I 'erased flash' and 'clean' the build. I also removed the battery and USB power to ensure I was starting with a completely blank TBeam.
The text was updated successfully, but these errors were encountered: