Mike,
?
Thank you for the very detailed explanation.? It is a good guide? for me to use whenever I'm following the code.? Thank you for taking the the time to provide it.
?
As I understand it, my zBITX is a sBitx dressed up in a new set of clothes.? A core sBitx that is integrated with a nice large Touch Screen LCD and? packaged in a new enclosure.? The zBITX may also add some additional features, but since I do not have a sBitx, I would not recognize them..
?
My first reaction is : Wow, that is a lot of sophisticated software to respond to a Straight Key being pressed and generate a continuous RF carrier while that key is being held down.? That is long way from how a Pixie II works.? ?It seems that the process to generate simple manual Straight Key CW is really entwined with the software needed for respond to paddle inputs and produce computer generated characters at a pre-defined speed (ie a CW keyer).? However, if it remains in Transmit Mode, it works OK most of the time.
?
The problem that I and others are having is the cw_delay, which is capped out at 1000ms.? Once that times out, and it drops out of Transmit Mode, the device goes off and gets busy with 'other stuff' and does not always respond to the next Key Down hardware input in a timely fashion? While my published experiment, which bypassed a lot of that 'other stuff' was successful, it wasn't enough.? ?Finding the parameter that caps cw_delay at 1000ms has been like looking for a needle in a haystack.? ?I have kind of set that aside for now.? ?As time permits, I am going to explore using Interrupts for the key input pins to obtain get immediate response to key down events when it is in the CW Mode.
?
I'm not part of the zBITX or sBitx design team.? I'm just a zBITX purchaser who likes to use straight key CW.? I would rather do something that will get mine working in the mode that I like to use rather than just shelve it.
?
72,
Jody - K3JZD? ? ? ?
