Replies: 2 comments 1 reply
-
You're right, one would expect that to work, and it's pretty essential functionality for TCP KISS support. It's definitely in scope for implementation. |
Beta Was this translation helpful? Give feedback.
1 reply
-
this PR fixes the beaconing: #618 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I see that the regular KISS interface that uses ports supports id_callsign, and I figured that I would try copying the id_callsign and id_interval stanza from the manual to the TCP KISS Interface. As far as I can tell, it doesn't seem to support it. Would it be in scope for id_callsign to be supported by the TCP KISS Interface?
Beta Was this translation helpful? Give feedback.
All reactions