|
Hello Everyone,
?
I've configured a Winkeyer Mini to run my TS-590SG using N1MM software.??
?
Everything is functioning as expected, with one exception.
?
Whenever the paddle keys are pushed or a function key is pushed, there is no morse code being transmitted.? Only a sidetone for the time duration set by the speed, which is 26 wpm.
?
Why don't I hear morse code being transmitted?
?
I hear code using the ARCP-590G software from Kenwood.? I also hear it and can transmit when using the Demo or Tools software suites.? Whenever a Function Button or either paddle is pushed, it only emits a long dash, almost as if it's acting like a straight key.
?
Break-in is on.? VOX is on, but doesn't have to be.? Everything has been configured per the manual.
?
My configuration is
- HP Laptop Windows 10
- Winkey Mini with updated CH340 driver and latest firmware
- Latest N1MM software update
- TS-590SG
- ZN-9ZX Paddle
?
Thanks for your help and hope to work you soon!
|
The sidetone comes from the SG. I have an SG and get the sidetone. If the radio is keying and the correct menu settings for sidetone are set and the Winkey is plugged into the STRAIGHT KEY JACL and NOT the paddle jack it will work Does for me? and always has. I am not at the radio so do not? know the menu options but look at the CW setup portion in the manual. ? Outlook LT Gil W0MN Hierro Candente Batir de Repente 44.08226 N 92.51265 W EN34rb ? ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Scott Novinger - AA9SN via groups.io
Sent: Wednesday, February 12, 2025 7:12 AM
To: [email protected]
Subject: [k1elsystems] Only Hearing Sidetone when Function Keys or Paddle is pressed? I've configured a Winkeyer Mini to run my TS-590SG using N1MM software.?? Everything is functioning as expected, with one exception. Whenever the paddle keys are pushed or a function key is pushed, there is no morse code being transmitted.? Only a sidetone for the time duration set by the speed, which is 26 wpm. Why don't I hear morse code being transmitted? I hear code using the ARCP-590G software from Kenwood.? I also hear it and can transmit when using the Demo or Tools software suites.? Whenever a Function Button or either paddle is pushed, it only emits a long dash, almost as if it's acting like a straight key. Break-in is on.? VOX is on, but doesn't have to be.? Everything has been configured per the manual. - Winkey Mini with updated CH340 driver and latest firmware - Latest N1MM software update Thanks for your help and hope to work you soon! -- W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP Laptop
|
It's
unclear what you mean by "Only a sidetone for the time duration ..."
means, Scott. 1.? The WK "KEY" output must go to the straight key
input on the transceiver.? Not familiar with the 590SG but often radios
will have a KEY jack [often a 1/4" phone jack] and a PADDLE [often a
2-circuit mini phone jack].? Some will only have one 2-ckt jack -- all
three wires used for paddle and tip-ring used for straight key and the
WK.? Which configuration is active is set somewhere in the radio menu
tree. 2.? In most cases, VOX must be ON for the radio to key and
produce sidetone & power. 3.? Remove the keying cable from
the WK [but NOT the radio] and short the two wires.? If the radio keys
normally with power out and sidetone, something is amiss with the WK
configuration.? If the radio does not key and produce power and
sidetone, either the connection to the radio is incorrect, the radio is
misconfigured in the menu, or both. The secret to troubleshooting
is to isolate the problem.? Electrically, the WK keying output is just a
short/no-short ... just like a straight key.
73,
Fred ["Skip"] K6DGW
Sparks NV DM09dn
Washoe County
Wednesday,
February 12, 2025 5:11 AM
Hello Everyone,
?
I've configured a Winkeyer Mini to run
my TS-590SG using N1MM software.??
?
Everything is functioning as expected,
with one exception.
?
Whenever the paddle keys are pushed or a
function key is pushed, there is no morse code being transmitted.? Only
a sidetone for the time duration set by the speed, which is 26 wpm.
?
Why don't I hear morse code being
transmitted?
?
I hear code using the ARCP-590G
software from Kenwood.? I also hear it and can transmit when using the
Demo or Tools software suites.? Whenever a Function Button or either
paddle is pushed, it only emits a long dash, almost as if it's acting
like a straight key.
?
Break-in is on.? VOX is on, but doesn't
have to be.? Everything has been configured per the manual.
?
My configuration is
- HP Laptop Windows 10
- Winkey Mini with updated CH340 driver
and latest firmware
- Latest N1MM software update
- TS-590SG
- ZN-9ZX Paddle
?
Thanks for your help and hope to work
you soon!
|
Not sure if this is of benefit, but I had the same issue with my TS-890S.? Also, I am using the Winkeyer and not the mini.? I did get the same long dash when pushing paddle.? What solved it for me was to connect the Winkeyer to my transmitter as if it were a straight key and not a paddle.? Meaning my paddle connects to the Winkeyer paddle port, but the winkeyer connects to my transmitter rear port configured as a straight key.? Both the winkeyer and the mini drives the transmitter in the manner of a straight key.? So, is your connecting cable to the transmitter made as shown on page 7 of the user manual?
Also, my VOX needs to be on like Skip mentioned.
On Wed, Feb 12, 2025 at 14:54 Fred ["Skip"] Jensen via <k6dgwnv= [email protected]> wrote:
It's
unclear what you mean by "Only a sidetone for the time duration ..."
means, Scott. 1.? The WK "KEY" output must go to the straight key
input on the transceiver.? Not familiar with the 590SG but often radios
will have a KEY jack [often a 1/4" phone jack] and a PADDLE [often a
2-circuit mini phone jack].? Some will only have one 2-ckt jack -- all
three wires used for paddle and tip-ring used for straight key and the
WK.? Which configuration is active is set somewhere in the radio menu
tree. 2.? In most cases, VOX must be ON for the radio to key and
produce sidetone & power. 3.? Remove the keying cable from
the WK [but NOT the radio] and short the two wires.? If the radio keys
normally with power out and sidetone, something is amiss with the WK
configuration.? If the radio does not key and produce power and
sidetone, either the connection to the radio is incorrect, the radio is
misconfigured in the menu, or both. The secret to troubleshooting
is to isolate the problem.? Electrically, the WK keying output is just a
short/no-short ... just like a straight key.
73,
Fred ["Skip"] K6DGW
Sparks NV DM09dn
Washoe County
Wednesday,
February 12, 2025 5:11 AM
Hello Everyone,
?
I've configured a Winkeyer Mini to run
my TS-590SG using N1MM software.??
?
Everything is functioning as expected,
with one exception.
?
Whenever the paddle keys are pushed or a
function key is pushed, there is no morse code being transmitted.? Only
a sidetone for the time duration set by the speed, which is 26 wpm.
?
Why don't I hear morse code being
transmitted?
?
I hear code using the ARCP-590G
software from Kenwood.? I also hear it and can transmit when using the
Demo or Tools software suites.? Whenever a Function Button or either
paddle is pushed, it only emits a long dash, almost as if it's acting
like a straight key.
?
Break-in is on.? VOX is on, but doesn't
have to be.? Everything has been configured per the manual.
?
My configuration is
- HP Laptop Windows 10
- Winkey Mini with updated CH340 driver
and latest firmware
- Latest N1MM software update
- TS-590SG
- ZN-9ZX Paddle
?
Thanks for your help and hope to work
you soon!
|
is the Moni on in the the 590sg
Dave Garber VE3WEJ / VE3IE
On Wed, Feb 12, 2025 at 3:39?PM Mark Redlinger via <mredlinger74= [email protected]> wrote: Not sure if this is of benefit, but I had the same issue with my TS-890S.? Also, I am using the Winkeyer and not the mini.? I did get the same long dash when pushing paddle.? What solved it for me was to connect the Winkeyer to my transmitter as if it were a straight key and not a paddle.? Meaning my paddle connects to the Winkeyer paddle port, but the winkeyer connects to my transmitter rear port configured as a straight key.? Both the winkeyer and the mini drives the transmitter in the manner of a straight key.? So, is your connecting cable to the transmitter made as shown on page 7 of the user manual?
Also, my VOX needs to be on like Skip mentioned.
On Wed, Feb 12, 2025 at 14:54 Fred ["Skip"] Jensen via <k6dgwnv= [email protected]> wrote:
It's
unclear what you mean by "Only a sidetone for the time duration ..."
means, Scott. 1.? The WK "KEY" output must go to the straight key
input on the transceiver.? Not familiar with the 590SG but often radios
will have a KEY jack [often a 1/4" phone jack] and a PADDLE [often a
2-circuit mini phone jack].? Some will only have one 2-ckt jack -- all
three wires used for paddle and tip-ring used for straight key and the
WK.? Which configuration is active is set somewhere in the radio menu
tree. 2.? In most cases, VOX must be ON for the radio to key and
produce sidetone & power. 3.? Remove the keying cable from
the WK [but NOT the radio] and short the two wires.? If the radio keys
normally with power out and sidetone, something is amiss with the WK
configuration.? If the radio does not key and produce power and
sidetone, either the connection to the radio is incorrect, the radio is
misconfigured in the menu, or both. The secret to troubleshooting
is to isolate the problem.? Electrically, the WK keying output is just a
short/no-short ... just like a straight key.
73,
Fred ["Skip"] K6DGW
Sparks NV DM09dn
Washoe County
Wednesday,
February 12, 2025 5:11 AM
Hello Everyone,
?
I've configured a Winkeyer Mini to run
my TS-590SG using N1MM software.??
?
Everything is functioning as expected,
with one exception.
?
Whenever the paddle keys are pushed or a
function key is pushed, there is no morse code being transmitted.? Only
a sidetone for the time duration set by the speed, which is 26 wpm.
?
Why don't I hear morse code being
transmitted?
?
I hear code using the ARCP-590G
software from Kenwood.? I also hear it and can transmit when using the
Demo or Tools software suites.? Whenever a Function Button or either
paddle is pushed, it only emits a long dash, almost as if it's acting
like a straight key.
?
Break-in is on.? VOX is on, but doesn't
have to be.? Everything has been configured per the manual.
?
My configuration is
- HP Laptop Windows 10
- Winkey Mini with updated CH340 driver
and latest firmware
- Latest N1MM software update
- TS-590SG
- ZN-9ZX Paddle
?
Thanks for your help and hope to work
you soon!
|
Guys,
?
Thanks so much for your help.
?
I figured out a solution to the problem, albeit maybe not the 'best' solution.
?
On a whim, I reverted to the earlier WKMini firmware which uses the FTDI drivers.? This solved the problem.
?
When I upgraded to the CH340USB driver and associated firmware, I think what was happening was each time the WKMini was recognized, Windows would install the original FTDI drivers, even though I disabled the 'Device on COM 3' (WKMini) and uninstalled the associated drivers.
?
When I get time, I'm going to see if I can figure out a way to not have Windows automatically install those FTDI drivers.? I want to see if the CH340 solution will work with my WKMini.? Unless the new WKMini devices are hardware dependent on the new drivers, in theory, it should work.
?
If anyone else has experience with this, I'd be happy to discuss this with you.
?
Again, I appreciate this community and everyone's help trying to solve this problem.
?
Cya soon!
--
V/r,
?
Scott?
AA9SN
|
On Thu, Feb 13, 2025 at 06:51 AM, Scott Novinger - AA9SN wrote:
?
On a whim, I reverted to the earlier WKMini firmware which uses the FTDI drivers.? This solved the problem.
?
When I upgraded to the CH340USB driver and associated firmware, I think what was happening was each time the WKMini was recognized, Windows would install the original FTDI drivers, even though I disabled the 'Device on COM 3' (WKMini) and uninstalled the associated drivers.
?
When I get time, I'm going to see if I can figure out a way to not have Windows automatically install those FTDI drivers.? I want to see if the CH340 solution will work with my WKMini.? Unless the new WKMini devices are hardware dependent on the new drivers, in theory, it should work.
?
If anyone else has experience with this, I'd be happy to discuss this with you.
?
The WKMini devices are hardware dependent.??
?
The WKMini Rev. A is an FTDI-based device: ?
?
The WKMini Rev. B is a CH340-based device: ?
?
Both my Rev. A unit and Rev. B unit are clearly labeled on the bottom for differentiation.
?
Hope this clarifies things a bit.
?
Tim Raymer
73 de N0UI?
?
|
Be careful which version of firmware you install, the ch340 version will appear to run on a FTDI WK and vice versa but you will have subtle problems. That’s why there are separate versions. Hard to believe people will do stuff like this. It’s a good way to brick the keyer.?
Another thing, usb driver selection is governed solely by a negotiation between windows and the usb interface. This happens before the WK IC finishes its initialization. So monkeying around with firmware versions is futile. In other words, if windows sees an FTDI device it loads the FTDI driver. Same for CH340.
I hope others don’t get ideas and start swapping versions around, I have enough trouble to deal with.
toggle quoted message
Show quoted text
On Feb 24, 2025, at 2:57?PM, Raymer, Timothy via groups.io <taraymer@...> wrote:
? On Thu, Feb 13, 2025 at 06:51 AM, Scott Novinger - AA9SN wrote:
?
On a whim, I reverted to the earlier WKMini firmware which uses the FTDI drivers.? This solved the problem.
?
When I upgraded to the CH340USB driver and associated firmware, I think what was happening was each time the WKMini was recognized, Windows would install the original FTDI drivers, even though I disabled the 'Device on COM 3' (WKMini) and uninstalled the associated drivers.
?
When I get time, I'm going to see if I can figure out a way to not have Windows automatically install those FTDI drivers.? I want to see if the CH340 solution will work with my WKMini.? Unless the new WKMini devices are hardware dependent on the new drivers, in theory, it should work.
?
If anyone else has experience with this, I'd be happy to discuss this with you.
?
The WKMini devices are hardware dependent.??
?
The WKMini Rev. A is an FTDI-based device: ?
?
The WKMini Rev. B is a CH340-based device: ?
?
Both my Rev. A unit and Rev. B unit are clearly labeled on the bottom for differentiation.
?
Hope this clarifies things a bit.
?
Tim Raymer
73 de N0UI?
?
|
Gilbert Baron
Fred ["Skip"] Jensen
Steve K1EL