Have a winkeyer USB keyer and it was working fine. I was messing with some comm ports but not the one for the keyer. Also was testing the keyer with K1EL's tet program (WKTools 5.3). It found the keyer on Comm 3 and downloaded all the settings.
Now, log4om doesn't seem to recognize the keyer nor the key which is connected to it. As is right now can't generate cw. I've rebooted computer and still no joy. Tested after closing log4om with N1MM+ and works fine.
I'm sure I've done something stupid in my fumbling around.
I've run out of ideas. Any help?
Op system is W10
Yes, the comm port shows up under device manager
Thanks
Ron
N4XD
Lost Winkeyer support
Re: Lost Winkeyer support
Ron,
What version of Log4OM are you using?
What version of Log4OM are you using?
73 - Nolan Kienitz - KI5IO
Plano, TX
Plano, TX
Re: Lost Winkeyer support
Just upgraded to the latest version 2.25.0.0
Issue started with the version just before it.
Thanks
ron
Issue started with the version just before it.
Thanks
ron
- G4POP
- Log4OM Alpha Team
- Posts: 10879
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Lost Winkeyer support
No you said the issue started with you messing with com port settings, try checking the com port setting in the Winkeyer settings, make sure it matches the NEW winkeyer port
73 Terry G4POP
Re: Lost Winkeyer support
Terry, thanks. Poorly worded by me. Meant to say issue didn't start with the new version. So not an issue with that upgrade.
Ron
Ron
Re: Lost Winkeyer support
Update: Went through config and created a completely new configuration. Still same issue. And the keyer still works without issue with N1MM+ to key the radio. Seems issue is with log4om?
Re: Lost Winkeyer support
Ron,
Have you looked in your logfile after attempting to set the WK ports, etc.?
Help / Open Log File
It will open a text file that you can scroll through and see tasks and responses.
You might have to select a Debug or Trace log level to see much more granular data that might help provide clues.
FYI I also use a WK USB device and am on same version of Log4OM as you and it is working FB.
Remember that the port for Log4OM to your rig for CAT control is "not" the same port as you use for the WK USB. Make sure you have not accidentally selected the same port for both rig and WK USB.
Have you looked in your logfile after attempting to set the WK ports, etc.?
Help / Open Log File
It will open a text file that you can scroll through and see tasks and responses.
You might have to select a Debug or Trace log level to see much more granular data that might help provide clues.
FYI I also use a WK USB device and am on same version of Log4OM as you and it is working FB.
Remember that the port for Log4OM to your rig for CAT control is "not" the same port as you use for the WK USB. Make sure you have not accidentally selected the same port for both rig and WK USB.
73 - Nolan Kienitz - KI5IO
Plano, TX
Plano, TX