Skip to content
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

Cant hear my own digipeats #363

Open
al0apsk31 opened this issue Jan 11, 2024 · 1 comment
Open

Cant hear my own digipeats #363

al0apsk31 opened this issue Jan 11, 2024 · 1 comment

Comments

@al0apsk31
Copy link

Hello,

I have a digipeater at my home station. It consists of a 2M Transceiver, PC and Direwolf modem. I can use this to hear my own digipeats with a Kenwood d74. This works fine.

I try to use APRSdroid, a Mobilinkd TNC3 and a Retevis RA89 Txcvr to send a position report. Position reports are received by Direwolf, it is then digipeated by the home station but not decoded in APRSdroid. When I use the APRSDroid/Mobilnkd/RA89 on the main USA network (144.390) all of my own position reports are received, digipeated and decoded by APRS droid just fine.

To summarize...the APRS Droid setup works on the 144.390 side of things but not on the home digipeater. Again, the home digipeater behaves perfectly with a Kenwood d74. So I'm at a loss. I hope I explained this well enough to be understood.

Thanks for Reading. Greg, AL0A

@al0apsk31
Copy link
Author

Upon further trouble shooting, I've found that the issue is related to the T/R switching recovery time on the particular radio. The Radio does not return to full receive fast enough to hear the its own digipeated position report packet. Thus, the packet is cut off. My Kenwood style T/R switching is fast. The Retevis has a discernible delay.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant