You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: