Log4OM

i will be damned if that serial winkeyer works...
i've tried almost every command available...

Come on Daniele it is possible, you can do it
As i workaround i wrote a small program myself which controls the Winkey2 and creates an ADIF file of the QSO's made, then i let Log4OM monitor this ADIF. So communicating with a Winkey2 via the serial port is possible.

can you send me your init sequence?
I'm struggling what is wrong in my sequence... it seems something is not appreciated

Since i made a very simple program, just sending macro's. There is not much initializing going on.
I open the port with 1200 8N1 , wait half a second and send: 0x00 0x02 to get the Winkey2 into hostmode, i wait for the response from the winkey2 with its revision number. (0x19 in my case.)

After that i set the pot speed range by sending: 0x05 0x10 0x20 0x00

Then i can send morsecode by sending UCase Ascii to the comport.

A 0x10 is send to interrupt ongoing morse sending.

Furter the program is watching the comport for: Sending busy or not , paddle busy and speedpot change's

Al is documented in the WK2 datasheet, had no big trouble to get ik working with the information from the datasheet

Yep, i have a bit more complex init... i should check what i can remove from the common area of initalization between WK1 2 and 3.

Thanks for sharing

IW3HMH wrote:Yep, i have a bit more complex init... i should check what i can remove from the common area of initalization between WK1 2 and 3.

Thanks for sharing

Good news ......maybe we can get Winkey2 to work on the next release?

Aldo, i don't know
I've tried for months that *%#$&* thing

IW3HMH wrote:Aldo, i don't know
I've tried for months that *%#$&* thing

I know Daniele, you will figure it out!! No rush whenever you have the time.

Thank you for all your efforts.

73

Since the winkey bug is not yet crushed i share my own contraption here. it is a very simple program with macro keys to send CW and log the QSO in Log4OM.

Your warranty for this software ends before the download is finished , just so you know. Use it at your own risk. (works fine here)

It uses the ADD message via UDP . make sure in the communicator - inbound settings - UDP port 2236 is on

Modify Winkey-2.cfg to your own need, but do not change the order or format (not much fault checking here)

https://davervel.home.xs4all.nl/WK4OM.zip