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

KISS Mode / Handling Delays #240

Closed
jcrix opened this issue Jan 6, 2020 · 3 comments
Closed

KISS Mode / Handling Delays #240

jcrix opened this issue Jan 6, 2020 · 3 comments

Comments

@jcrix
Copy link

jcrix commented Jan 6, 2020

I could be going about this wrong. But I've built a BBS using direwolf as the sound modem. Everything works well for the most part. But I have no way to tell went direwolf actually transmitted my packet. Which clearly causes timing issues. Is there a better way to go about this? It would be nice if there was a way to track when a packet actually transmits so I could probably build this event driven wise. Like a mode we could put it in so that when a packet to be transmitted is submitted direwolf would responds OK when it actually transmits. Or error if something bad happens.

@ab0tj
Copy link
Contributor

ab0tj commented Jan 6, 2020

This is probably more of a feature request than an issue, but I'll add a "me too" to this. This would be a useful thing to have with the way I use direwolf for an APRS tracker.

@wb2osz
Copy link
Owner

wb2osz commented Jan 7, 2020

Look in the Dire Wolf User Guide, section 9.4.6, KISS "set hardware" command.

There is a command to obtain the current number of frames sitting in the transmit queue. Does this help?

@jcrix
Copy link
Author

jcrix commented Jan 7, 2020

I tested the command. Yes this should work for what I need. Thanks!

@jcrix jcrix closed this as completed Jan 19, 2020
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

3 participants