开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育

Re: sBitx CW keyer problems and idea for solution #sBitx #sBITX_v3 #cw #firmware


 

?
The problems with CW keying seemed to be multfactorial:
a)? the 10-20 Hz polling loop is far too slow for CW in the 20's or 30's
b)? the Linux operating system itself is not a real-time operating system (and thus could throw in delay)
c)? there are potentially unnecessary delay() slow-downs in the t/r switching routines that can chop off first element.
?
Using an EXTERNAL keyer (like the K1EL systems, which I have, and have also built a slew of arduino-based equivalents) does not solve the problem, in fact it can potentially make it worse because of the polling architecture.? ?In my personal experience, I had to give up on an external keyer and return to the internal, because while still very flawed, it was far better than external.
?
Ashhar recommended some kind of GPIO memory mapping (I don't know anything about it) and others recommended an interrupt-driven rewrite.
The 64bit code was tested by W4GSN and still had some of these same problems.
?
#1? What is the current status?? ?Has any available software/image fixed this problem?
#2? ?Is anyone working on it?
?
I'm away at our ancient family retreat where I depend on an sBitx and I was just having a horrible time holding a CW QSO at 20wpm using a Bencer paddle.? ? Meanwhile (sorry, rubbing it in....) my homebrew Arduino-Winkeyer emulator and an old Heathkit SB102 and a $7 homebrew hardware-store paddle work quite well!!? ?Surely this can be mitigated.? ? The SB102's receiver can't hold a candle to the amazing sBitx.....but the simple analog transmitter works (If i tweak the bandswitch rotary JUST right, it will produce output power also!)? ?
?
?
Thanks!
Gordon Gibby KX4Z
?

Join [email protected] to automatically receive all group messages.