-
Notifications
You must be signed in to change notification settings - Fork 49
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
RTTY via Lora - ocasionally hangs? #48
Comments
And confirmation that it does seem to happen in the PiInTheSky repo code too, this was a fresh clone:
pisky file at the time of this test: https://github.com/KevWal/pits/blob/9b311566ed028844e216c5c01564b6923b776baa/boot/pisky.txt Cheers |
And back on my code base, turning off RTTY via Lora it runs fine for an hour, turning RTTY back on it breaks straight away:
Turning off Uplink mode, and leaving RTTY on and it runs fine. With a more sensible ratio of Lora RTTY to Lora packets (1 to 10), aslong as you dont happpen to start it near the top of a minute, it will run fine for some time:
But as soon as a RTTY happens near the top of a minute it gives up:
Cheers |
Hi
I ocasionally see transmissions stop at the point when an RTTY via LORA transmission occours close to an Uplink period.
This is using a home made PITS board - https://github.com/KevWal/Pi-in-the-Sky-Project/tree/main/Hardware/V4 and also on code modified in a number of ways - https://github.com/KevWal/pits/tree/develop , so I appretiate that could be a cause of the problem [now demonstarted on a fresh PiInTheSky repo clone]. However I don't believe I have changed anything that could cause this and have been seeing it since I started using RTTY via Lora which was before many of the changes.
It usually happenes if I started the tracker code around the Uplink time, but I now have an instance of the issue 15mins into the running:
Infact, if I set RTTY via Lora tx to happen regularly I can make the issue happen much more repeatably:
Let me see if I can reproduce this on the repo code.
Thanks very much
Kevin
The text was updated successfully, but these errors were encountered: