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

TBEACON frames not copied to TCP KISS #203

Closed
AlyBadawy opened this issue Mar 31, 2019 · 2 comments
Closed

TBEACON frames not copied to TCP KISS #203

AlyBadawy opened this issue Mar 31, 2019 · 2 comments

Comments

@AlyBadawy
Copy link

Not sure if this is a bug or was done intentionally, but the beacons generated by the Direwolf configuration file, are not copies on the TNC KISS port. all other beacons (from TCP KISS) are sent to audio, and all other received on audio are copied to the TCP KISS port.

The reason why I am asking, is I am using another software (APRX) as the core of the aprs engine, and direwolf as a KISS TNC. however, I need to beacon the location based on GPS from direwolf. this happens on the audio side, out to radio and then to RF. I am still interested in i-gating that beacon via the internet through APRX.

Ideas?

@AlyBadawy AlyBadawy changed the title TBEACON frames not copies to TCP KISS TBEACON frames not copied to TCP KISS Mar 31, 2019
@wb2osz
Copy link
Owner

wb2osz commented Mar 31, 2019

Look in the User Guide, Beaconing section, "SENDTO" option.
You can use "R" and a number to simulate reception from the specified channel.
This is sent to the attached applications (KISS or AGW network interface) as if they were received over the radio.

@AlyBadawy
Copy link
Author

Perfect. Exactly what I needed. Thanks a lot.

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

2 participants