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

Add AX.25 T3 timer to be configurable -- Add notes about other AX.25 parameters to documentation #436

Open
dranch opened this issue Dec 21, 2022 · 0 comments

Comments

@dranch
Copy link
Collaborator

dranch commented Dec 21, 2022

Per our conversation: "A user configurable T3 could be added for completeness. . . . If you think it is important, throw it in the issues tracking so it does not get lost in the clutter."

Also a few reminders just for the documentation side for those users who come from hardware TNCs:

T2 timer: Add the description: " This parameters was removed from the AX.25 specification in v2.2. It is not needed if the protocol stack knows the modem data carrier detect status (which Direwolf does). See the Why-is-9600-only-twice-as-fast-as-1200.pdf document for more explanation.

FRACK: Mention in the User Guide that the max is 15

CHECK: Add this item with the description "Make a periodic check/poll to determine that a connection still exists. Dire wolf does not currently have an option (to configure) this. It is hardcoded to be 300 seconds."

SENDPAC, PACTIME, and CPACTIME: Add these items with the description "These parameters seem to be applicable only to the case where you are talking to a TNC in CONVERS (interactive transmit/receive) mode. Some specified character (typically enter) results in a packet being sent immediately. With both KISS and AGW, applications deal with complete packets, not individual characters so this does not apply to Direwolf's layer."

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