-
Notifications
You must be signed in to change notification settings - Fork 18
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
Feature Request: TX Watchdog Timer #5
Comments
Does pressing the reset button on the TNC when it hits this condition stop
the radio from transmitting?
Kind Regards,
Rob Riggs WX9O
Mobilinkd LLC
…On Mon, Oct 23, 2023 at 11:38 AM Ben Kuhn ***@***.***> wrote:
I occasionally run in to an issue where the TNC will get stuck in TX and
need to be reset. I'm reasonably sure this is due to RFI somewhere, but
I've never been able to track it down and no amount of ferrite beads help.
It happens on my mobilinkd as well as several NucleoTNCs. The documentation
suggesting ferrite beads on the cable between the radio and TNC suggest I'm
not the first to see this. My current work-around is a TOT set on the
radio, but the TNC still needs to be reset once entering this condition.
As a workaround, and for HT use, etc... where rf conditions may be out of
the user's control, it would be a nice feature to have a user-configurable
TX watchdog timer to reset the TNC after a user-defined period of time in
TX--user defined so it doesn't mess with M17 voice QSOs.
Thanks for your consideration.
—
Reply to this email directly, view it on GitHub
<#5>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABD64DG2BEYQE4N5ZVVTXITYA2MQBAVCNFSM6AAAAAA6MLTSTKVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE2TONJXGA3TAMY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I will let you know next time I see this happen. |
Ok, thanks.
…On Thu, Oct 26, 2023 at 8:00 AM Ben Kuhn ***@***.***> wrote:
I will let you know next time I see this happen.
—
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABD64DHDFO22EMJFKW3JLUTYBJNF7AVCNFSM6AAAAAA6MLTSTKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBRGA3TMMRVGM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I occasionally run in to an issue where the TNC will get stuck in TX and need to be reset. I'm reasonably sure this is due to RFI somewhere, but I've never been able to track it down and no amount of ferrite beads help. It happens on my mobilinkd as well as several NucleoTNCs. The documentation suggesting ferrite beads on the cable between the radio and TNC suggest I'm not the first to see this. My current work-around is a TOT set on the radio, but the TNC still needs to be reset once entering this condition.
As a workaround, and for HT use, etc... where rf conditions may be out of the user's control, it would be a nice feature to have a user-configurable TX watchdog timer to reset the TNC after a user-defined period of time in TX--user defined so it doesn't mess with M17 voice QSOs.
Thanks for your consideration.
The text was updated successfully, but these errors were encountered: