[WT-support] K3NG Keyer

Bob Wilson, N6TV n6tv at arrl.net
Tue Jan 26 19:53:02 CET 2021


Sorry, you said you already tried that.

Sounds like the K3NG emulation isn't as good as a real WinKey V2 chip.

73,
Bob, N6TV


On Tue, Jan 26, 2021 at 10:52 AM Bob Wilson, N6TV <n6tv at arrl.net> wrote:

> In the WKSETUP menu in Win-Test, did you check the box "Enable Winkey V2
> Additional Features"?
>
> I would power everything off or use the "RESET" before connecting
> Win-Test, and connect Win-Test first; I don't know what state Logger32
> might have left the K3NG keyer in.
>
> 73,
> Bob, N6TV
>
>
> On Tue, Jan 26, 2021 at 10:04 AM Franck <f4cib at free.fr> wrote:
>
>> Hi Bob,
>> Already commented out.
>> Recognized as Winkey 2 with Logger32 and CW keying ok, but still init
>> error.
>>
>> 73 de Franck, F4CIB
>>
>> ----- Mail original -----
>> De: "Bob Wilson, N6TV" <n6tv at arrl.net>
>> À: "Win-Test Reflector" <support at win-test.com>
>> Envoyé: Lundi 25 Janvier 2021 22:12:15
>> Objet: Re: [WT-support] K3NG Keyer
>>
>>
>>
>> You might need to comment out this line to make it work.
>>
>>
>> #define OPTION_WINKEY_STRICT_HOST_OPEN
>>
>>
>> Of course look in Windows Device Manager to make sure you are selecting
>> the correct COM port. Just unplug the keyer to see which COM port
>> disappears.
>>
>>
>>
>>
>>
>> 73,
>> Bob, N6TV
>>
>>
>>
>> On Mon, Jan 25, 2021 at 11:57 AM Franck < f4cib at free.fr > wrote:
>>
>>
>> Hi Bob,
>> Yes Winkey and defaults settings do not work here 1200 8N2 handshake
>>
>> 73 de Franck, F4CIB
>>
>> ----- Mail original -----
>> De: "Bob Wilson, N6TV" < n6tv at arrl.net >
>> À: "Win-Test Reflector" < support at win-test.com >
>> Envoyé: Lundi 25 Janvier 2021 19:51:47
>> Objet: Re: [WT-support] K3NG Keyer
>>
>>
>>
>> Did you set COM10's Device name to WinKey in Win-Test Interface
>> Configuration? Did you set the baud rate to 1200 baud? Just click the "Use
>> WinKey Defaults" button to set 1200,8,N,2 Handshake, Handshake. and restart
>> everything.
>>
>>
>>
>> 73,
>> Bob, N6TV
>>
>>
>>
>> On Mon, Jan 25, 2021 at 10:31 AM Franck < f4cib at free.fr > wrote:
>>
>>
>> Hi All,
>> struggling with my K3NG keyer and Win-Test.
>>
>> I compile K3NG keyer with last up to date firmware (2021-01-24)
>> Keyer options used:
>> #define FEATURE_COMMAND_LINE_INTERFACE // Command Line Interface
>> functionality
>> #define FEATURE_WINKEY_EMULATION // disabling Automatic Software Reset is
>> highly recommended (see documentation)
>> #define OPTION_PRIMARY_SERIAL_PORT_DEFAULT_WINKEY_EMULATION // Use when
>> activating both FEATURE_WINKEY_EMULATION and FEATURE_COMMAND_LINE_INTERFACE
>> #define OPTION_INCLUDE_PTT_TAIL_FOR_MANUAL_SENDING
>> #define OPTION_EXCLUDE_PTT_HANG_TIME_FOR_MANUAL_SENDING
>> #define OPTION_WINKEY_STRICT_HOST_OPEN // require an admin host open
>> Winkey command before doing any other commands
>> #define OPTION_WINKEY_2_SUPPORT // comment out to revert to Winkey
>> version 1 emulation
>> #define OPTION_WINKEY_INTERRUPTS_MEMORY_REPEAT
>> #define OPTION_WINKEY_2_HOST_CLOSE_NO_SERIAL_PORT_RESET // (Required for
>> Win-Test to function)
>> #define OPTION_WINKEY_IGNORE_LOWERCASE // Enable for typical K1EL
>> Winkeyer behavior (use for SkookumLogger version 1.10.14 and prior to
>> workaround "r" bug)
>> #define OPTION_PROG_MEM_TRIM_TRAILING_SPACES // trim trailing spaces from
>> memory when programming in command mode
>> #define OPTION_DIT_PADDLE_NO_SEND_ON_MEM_RPT // this makes dit paddle
>> memory interruption a little smoother
>> #define OPTION_CW_KEYBOARD_CAPSLOCK_BEEP
>> #define OPTION_DO_NOT_SEND_UNKNOWN_CHAR_QUESTION
>> #define OPTION_EXCLUDE_EXTENDED_CLI_COMMANDS
>> #define OPTION_DISPLAY_MEMORY_CONTENTS_COMMAND_MODE
>>
>> On Win-Test side, Keyer connected to COM10 set to Winkey 8N2 DTR set
>> always to 1, RTS always to 0 (tried as well default which are handshake for
>> both)
>> Options, Winkey configuration unchanged (i tried also winkey v2 features
>> enabled):
>> All unticked but paddle watchdog, Iambic A, PTT, 752Hz, tail&lead 50ms,
>> fixed tail, synchronized by WT only
>>
>> And i got Winkey Device init Error on the status area
>>
>> Can anyone share with me his settings ?
>>
>> 73 de Franck, F4CIB
>> _______________________________________________
>> Support mailing list
>> support at win-test.com
>> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>>
>> _______________________________________________
>> Support mailing list
>> support at win-test.com
>> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>> _______________________________________________
>> Support mailing list
>> support at win-test.com
>> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>>
>> _______________________________________________
>> Support mailing list
>> support at win-test.com
>> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>> _______________________________________________
>> Support mailing list
>> support at win-test.com
>> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20210126/d713d809/attachment.html>


More information about the Support mailing list