The error came on a older x86_64 KUbuntu desktp
homebrew computer, with the motherboard sound card, and no PTT
setting (VOX).? Direwolf has "no clue' how the PTT is being
handled.
Ok.. that takes the iffy Raspberry Pi USB stack out of the running.
In fact, the
testing was originally started with no radio connected at all.?
How can the PTT be on for too long when thd non-connected radio
has no connection to Direwolf to be measured (timed)?
When no PTT is configured, it's assume you're using VOX or using a
sound device like a Signalink that asserts PTT for you.? Per the
previous thread found via Google, if you look at like 910 at:
??
You can see where this message is coming from but it's not totally
clear why you're seeing this.? I would argue that ANY 64bit x86
machine should be more than fast enough but maybe it's under a lot
of other load or something?? I've personally never seen this error.
--David
KI6ZHD
