Put OPTION_WINKEY_SEND_BREAKIN_STATUS_BYTE back into all hardware profiles and enabling by default. Not having it activated makes N1MM CQ Repeat paddle sending deactivation not work.
The Open CW Keyer MK2 does not have any circuitry to support a second transmitter. Clearing the pin defines for this non-existent transmitter removes the possibility of the user accidentally having tx2 enabled. A long press of the memory 2 button will set the keyer up for tx2 output and there is no indication that this is the configuration. With no pins for tx2 then inadvertently selecting tx2 is not possible.
Patch the admin 09 command to return a fake version instead of a
different arbitrary value, because Skookum Logger depends on it.
Admin command 9 returns a calibration value on WK1, 0 on WK2, and the
major version on WK3 (according to docs)
Skookum Logger expects a real version to come back on a WK2 device since
that's what the author's device does.
https://groups.io/g/radioartisan/topic/100917839#18017https://groups.io/g/SkookumLogger/topic/100998043#51
Added #define HI_TEXT to make the start-up hard-coded "HI" message configurable (with, for example, the user call-sign).
Co-authored-by: cda <newsletters@christophedavid.org>
Co-authored-by: Anthony Good <anthony.good@gmail.com>
* Update keyer.h
Added 'SOS' prosign
* Update k3ng_keyer.ino
Added 'SOS' prosign
* Update k3ng_keyer.ino
* Update k3ng_keyer.ino
Added prosigns SO and OS
* Update keyer.h
Added prosigns SO and OS
Co-authored-by: Anthony Good <anthony.good@gmail.com>
Previously, when exiting Command Mode the screen was cleared and left blank. The display would then only be restored if you entered a character from the paddles or pressed a memory button.
This code always restores the display as you exit Command Mode. It does this simply by rewriting the saved screen buffer arrays to the display.
Only relevant if FEATURE_DISPLAY is defined.
The code for the for loop was plagiarised from the service_display() function.
Merged Pull Request 108 https://github.com/k3ng/k3ng_cw_keyer/pull/108 from VK2EFL
Adds to the \S CLI listing a display of the current tx's lead and tail times, plus the hang time (in wordspace units) plus the memory repeat time.
Merged Pull Request 109 https://github.com/k3ng/k3ng_cw_keyer/pull/109 from VK2EFL
Adds the option of a memory repeat time between repeated playing of memory 1 when in beacon mode.
Adds the option of having the PTT tail time added to the PTT at the end of each playing of memory 1 when in beacon mode.
* Update k3ng_keyer.ino
Modified the beacon code so that it has options for including the memory repeat time (to space out the repeated playing of memory 1) and the ptt tail time.
To the keyer_features_and_options.h file add two new options
#define OPTION_BEACON_MODE_MEMORY_REPEAT_TIME
#define OPTION_BEACON_MODE_PTT_TAIL_TIME
* Update keyer_features_and_options.h
* Update keyer_features_and_options.h
* Update keyer_features_and_options.h
Keying compensation now displayed in \S status CLI command
Added Q command to FEATURE_COMMAND_MODE: Adjust keying compensation (left paddle = increase, right paddle = decrease)
FEATURE_COMMAND_LINE_INTERFACE \:comp command now displays warning if keying compensation setting is probably too high
Added the \:comp extended command to change keying compensation in the CLI
keying_compensation is now stored in eeprom
NOTE: increasing keying compensation above 35 mS at ~24 WPM causes wonkiness. Probably need to add code to limit this value based on current WPM
k3ng