FLDigi and external CW paddle

[u***@public.gmane.org]

Using FLDigi with a Signalink USB and Yaesu FT897D under Ubuntu. FLRig works fine, and FLDigi has been working very nicely for PSK31. I am trying to get into CW and have a basic question about how FLDigi is designed to function.
Lets say I just finished a PSK31 session in Digital mode on the radio, and want to do CW. I change modes on my radio to CW and find a frequency to operate. When I operate the paddle attached to radio, it does some very bizarre things, like there is a delay, or some feedback going on. If I terminate hamlib rig control within FLDigi, then all is good, I can use CW normally. But I lose many FLDigi functions.
I suspect I have something set up improperly in the settings, but might be missing something else entirely as to how I should be operating FLDigi. I want to use FLDigi to assist in decoding CW, and like the software to track frequencies while I tune for logging purposes. Also, using the waterfall to select a signal is very nice. I just want to be able to use my external paddle. The paddle right now is attached to the keyer input of the radio.
With Hamlib enabled, FLDigi can send and receive CW using the macros just fine with the radio in USB.

Thanks for your help
Jeff
AF5PI

[Ed]

Post by u***@public.gmane.org
Using FLDigi with a Signalink USB and Yaesu FT897D under Ubuntu.
FLRig works fine, and FLDigi has been working very nicely for PSK31.
I am trying to get into CW and have a basic question about how FLDigi
is designed to function. Lets say I just finished a PSK31 session in
Digital mode on the radio, and want to do CW. I change modes on my
radio to CW and find a frequency to operate. When I operate the
paddle attached to radio, it does some very bizarre things, like
there is a delay, or some feedback going on. If I terminate hamlib
rig control within FLDigi, then all is good, I can use CW normally.
But I lose many FLDigi functions. I suspect I have something set up
improperly in the settings, but might be missing something else
entirely as to how I should be operating FLDigi. I want to use
FLDigi to assist in decoding CW, and like the software to track
frequencies while I tune for logging purposes. Also, using the
waterfall to select a signal is very nice. I just want to be able to
use my external paddle. The paddle right now is attached to the
keyer input of the radio. With Hamlib enabled, FLDigi can send and
receive CW using the macros just fine with the radio in USB.
Thanks for your help Jeff AF5PI

What you want to do is not possible with fldigi. CW with fldigi is still
a digital modem and selected from the dropdown menu to select the CW
modem. You can use work arounds, but the time and effort are not worth
it. CW with fldigi is macros or keyboard.

Ed W3NR

[Andrew O'Brien]

I can use my paddles with my rig and just use Fldigi for decode. Fldigi in
CW mode, rig in CW mode, paddles connected...no sending via Fldigi
http://www.youtube.com/embed/f6SAKIi8cD0?vq=hd1080 , In the video you see
me move off frequency and just send my call for illustration purposes. I
use the Fldigi to DXLAB bridge and use Commander rather than Flrig.
Andy K3UK

Post by Ed

Post by u***@public.gmane.org
Using FLDigi with a Signalink USB and Yaesu FT897D under Ubuntu.
FLRig works fine, and FLDigi has been working very nicely for PSK31.
I am trying to get into CW and have a basic question about how FLDigi
is designed to function. Lets say I just finished a PSK31 session in
Digital mode on the radio, and want to do CW. I change modes on my
radio to CW and find a frequency to operate. When I operate the
paddle attached to radio, it does some very bizarre things, like
there is a delay, or some feedback going on. If I terminate hamlib
rig control within FLDigi, then all is good, I can use CW normally.
But I lose many FLDigi functions. I suspect I have something set up
improperly in the settings, but might be missing something else
entirely as to how I should be operating FLDigi. I want to use
FLDigi to assist in decoding CW, and like the software to track
frequencies while I tune for logging purposes. Also, using the
waterfall to select a signal is very nice. I just want to be able to
use my external paddle. The paddle right now is attached to the
keyer input of the radio. With Hamlib enabled, FLDigi can send and
receive CW using the macros just fine with the radio in USB.
Thanks for your help Jeff AF5PI

What you want to do is not possible with fldigi. CW with fldigi is still
a digital modem and selected from the dropdown menu to select the CW
modem. You can use work arounds, but the time and effort are not worth
it. CW with fldigi is macros or keyboard.
Ed W3NR

[u***@public.gmane.org]

Thanks for the reply Andrew. When you were doing that video, did you have Hamlib initialized, or were you just using FLDigi strictly for decoding?
I am also been able to operate this way. The problems only start when I try to have Hamlib initialized for rig control so I get the nice frequency tracking features etc. When I key up manually, the rig chokes. I am wondering if there is a jumper setting within my Signalink USB box that may be causing this interaction. Not a show stopper to turn off the Hamlib before doing manual CW, but it would be nice to know if other people are able to operate manually.
Jeff
AF5PI

[Michael Wrenn]

I am also able to send CW directly through the radio while FLDigi decodes
in the background. However, I have FLDigi setup to use XML-RPC to
communicate with FLRig. I am using a Rigblaster as my soundcard interface.

In my current setup, FLRig and CQRLog fight over the connection to the
radio, so I usually don't run FLRig, and therefore, FLDigi is just blindly
decoding without any data from the rig.

I can't figure out why you would be experiencing any issues just because a
piece of software is communicating with the rig. If FLDigi is not telling
the rig to transmit, then any form of manual PTT should work fine.

I will have to try running FLDigi tonight with Hamlib engaged and see if I
can replicate this. It is very interesting.

Seven Three,

Michael - K5WRN
http://www.qrz.com/db/K5WRN

Post by u***@public.gmane.org
Thanks for the reply Andrew. When you were doing that video, did you have
Hamlib initialized, or were you just using FLDigi strictly for decoding?
I am also been able to operate this way. The problems only start when I
try to have Hamlib initialized for rig control so I get the nice frequency
tracking features etc. When I key up manually, the rig chokes. I am
wondering if there is a jumper setting within my Signalink USB box that may
be causing this interaction. Not a show stopper to turn off the Hamlib
before doing manual CW, but it would be nice to know if other people are
able to operate manually.
Jeff
AF5PI

[u***@public.gmane.org]

UPDATE
After extensive trial and error I was able to determine that my radio is exhibiting vary strange behavior on just one band, 20m. With Hamlib initialized, I can do CW with RF Power set at about 15 or less. With Hamlib off,I can run the RF Power up to about 70, at which point I get the same problem. The radio beeps, the CW tone sounds distorted, and the little "running man" dude appears on the radio display. This behavior does not appear on any other band, or any other mode. I can do full power SSB, PSK digital modes, with or without Hamlib engaged at any power level on the other bands of my radio. My 20m antenna is my best tuned antenna and has an SWR of less than 1.2. I also have an LDG 897 autotuner attached, so I figured I could rule out an antenna problem.

Initially I thought there may be a low voltage issue when transmitting at higher leveles, since I run a dual 12v deep cycle battery setup charged by solar, and the voltage obviously dips lower when keying. I bought an MFJ voltage booster to hold the voltage at a constant 13.8 volts and I get the same problem. Not low supply voltage.
I am still curious though why having Hamlib active seems to lower the RF Power point at which the radio glitches. Very strange.
Jeff
AF5PI

[Aaron Taddei]

Jeff,
What happens when you swap from Hamlib to rig control in fldigi?

72
Aaron Taddei
N5STS
SKCC #11152
NAQCC #7120
FPQRP #3358

Post by u***@public.gmane.org
UPDATE
After extensive trial and error I was able to determine that my radio is
exhibiting vary strange behavior on just one band, 20m. With Hamlib
initialized, I can do CW with RF Power set at about 15 or less. With
Hamlib off,I can run the RF Power up to about 70, at which point I get
the same problem. The radio beeps, the CW tone sounds distorted, and
the little "running man" dude appears on the radio display. This
behavior does not appear on any other band, or any other mode. I can do
full power SSB, PSK digital modes, with or without Hamlib engaged at any
power level on the other bands of my radio. My 20m antenna is my best
tuned antenna and has an SWR of less than 1.2. I also have an LDG 897
autotuner attached, so I figured I could rule out an antenna problem.
Initially I thought there may be a low voltage issue when transmitting
at higher leveles, since I run a dual 12v deep cycle battery setup
charged by solar, and the voltage obviously dips lower when keying. I
bought an MFJ voltage booster to hold the voltage at a constant 13.8
volts and I get the same problem. Not low supply voltage.
I am still curious though why having Hamlib active seems to lower the RF
Power point at which the radio glitches. Very strange.
Jeff
AF5PI

[u***@public.gmane.org]

Hi Aaron,
I was beginning to think that maybe some part of my radio output was blown on the 20m band. So I disconnected everything from radio including the LDG 897 tuner and tested radio. All works fine all modes, all power. Then plugged in LDG 897 tuner, and still good.
Next up was the SIgnalink USB, no problems. The last thing I hooked up was the USB-62 CAT cable. BINGO! , there is the problem. For some reason this cable was causing the errors on 20m in CW mode. Can't explain it, but I can duplicate it every time. The cable is evil.
Have read elsewhere about some potential pin connection issues with this cable, so I will do some more reading. In the meantime at least I can run the rig without CAT control and all is well.

Jeff
AF5PI

[Michael A. Thissell]

Jeff - Does this only happen on 20 meters? Have you tried to decode
CW on other bands?

mike w7xw



On 23 Mar 2014 12:16:17 -0700

Post by u***@public.gmane.org
Hi Aaron,
I was beginning to think that maybe some part of my radio output was
blown on the 20m band. So I disconnected everything from radio
including the LDG 897 tuner and tested radio. All works fine all
modes, all power. Then plugged in LDG 897 tuner, and still good.
Next up was the SIgnalink USB, no problems. The last thing I hooked
up was the USB-62 CAT cable. BINGO! , there is the problem. For
some reason this cable was causing the errors on 20m in CW mode.
Can't explain it, but I can duplicate it every time. The cable is
evil. Have read elsewhere about some potential pin connection issues
with this cable, so I will do some more reading. In the meantime at
least I can run the rig without CAT control and all is well.
Jeff
AF5PI

[Ing. Pavel Milanes Costa]

Hi...

Sorry for the late answer, I had in the past a kind of trouble like
yours, the culprit was a USB-SERIAL adaptor, mine jump crazy after the
RF was in the air ONLY on certain bands... I think the ARK chip inside
it is very sensitive to RF... (yes, cheap adaptor, but the only one I
can get here at that time) I had the luck to swap it for other with
other kind of chipset... problem solved...

73

Post by u***@public.gmane.org
Hi Aaron,
I was beginning to think that maybe some part of my radio output was
blown on the 20m band. So I disconnected everything from radio
including the LDG 897 tuner and tested radio. All works fine all
modes, all power. Then plugged in LDG 897 tuner, and still good.
Next up was the SIgnalink USB, no problems. The last thing I hooked
up was the USB-62 CAT cable. BINGO! , there is the problem. For
some reason this cable was causing the errors on 20m in CW mode.
Can't explain it, but I can duplicate it every time. The cable is evil.
Have read elsewhere about some potential pin connection issues with
this cable, so I will do some more reading. In the meantime at least
I can run the rig without CAT control and all is well.
Jeff
AF5PI

[mm0fmf]

Post by u***@public.gmane.org
The last thing I hooked up
was the USB-62 CAT cable. BINGO! , there is the problem. For some
reason this cable was causing the errors on 20m in CW mode.

RF feedback. Try winding a few turns of the USB-62 lead on a ferrite
ring. You may need to experiment with where the ring goes, rig end or up
by the USB dongle body.

My USB keyboard would die when I used more than 5W on 10MHz or 18MHz. I
wound 3 turns of the cable on the first ferrite out of the junk that the
USB plug would pass through. Job done.

YMMV

Andy
MM0FMF

[u***@public.gmane.org]

I bought a couple of snap-on chokes today and put them on. I think I am on the right track now. I put one on each end of the USB cable. The problem did not completely go away, but I could definitely push a higher RF output before the problem hit. One other issue is the USB Dongle on the USB end does not fit the laptop because of its thickness, so I have to use a short USB extension cable. I think if I get some more chokes to put on THAT cable as well then I will get the problem under control.

Jeff
AF5PI

[Ernie D]

Hey Jeff,

I remember reading somewhere that the Q of snap on chokes is
considerable lower than that of a toroid because of the break in the
ferrite material. Twice the turns would be required. As the snap-on
choke is working somewhat, It might be worth your while to get some
toroids of appropriate material (43) which has a Mu of 850. According to
the ARRL RFI Book, Its optimum frequency attenuation is from 14 MHZ to
450 Mhz. Purchase toroids large enough to wrap multiple turns.
--
73 From Ernie D

AA1AD | CN87ug

Post by u***@public.gmane.org
I bought a couple of snap-on chokes today and put them on. I think I
am on the right track now. I put one on each end of the USB cable.
The problem did not completely go away, but I could definitely push a
higher RF output before the problem hit. One other issue is the USB
Dongle on the USB end does not fit the laptop because of its
thickness, so I have to use a short USB extension cable. I think if I
get some more chokes to put on THAT cable as well then I will get the
problem under control.
Jeff
AF5PI