Elecraft

fldigi KX3 question

Classic

List

Threaded

5 messages Options

Terry

fldigi KX3 question

I am new to fldigi. I am using the SignaLink USB to interface between my
KX3 and computer. I have my KX3 connected to fldigi using Hamlib rig
control. That seems to work fine tracking the VFO and placing software into
the right mode when I change it on the KX3. First, could someone tell me
what power output I should be using for psk31, RTTY, and some of the other
digital modes supported by fldigi? I do have the KXPA100 if I need more
than 10 watts power.

I can receive digital modes just fine. I am still trying to identify the
various sounds other than PSK31 and RTTY which were the predominant ones I
used about 9 years ago before my hiatus from Ham Radio.

I turned my power down to three watts just to make sure I was not
overdriving anything. I tried PSK31 and RTTY on transmit. The KX3 went
into transmit mode when pressing the TX button. When I press the RX button,
the transmit of the baudot idle string for example in RTTY stops, but the
red transmit light stays lit. I have to manually press the XMIT button to
turn off the transmit light. Same thing happens in PSK31. I must be
missing some setting in fldigi and I hope someone can tell me how to get the
KX3 to go back into receive mode.

Thanks,

73's,

Terry, N7TB

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Don Wilhelm-4

Re: fldigi KX3 question

Terry,

What data submodes are you using?

Fldigi is a soundcard oriented application and you should be using DATA
A for PSK and AFSK for RTTY. If you are trying to use data submodes of
PSKD or FSKD, you will receive just fine, but transmit will not happen
with Fldigi.

Typically, PSK will work fine at low power levels, but the RTTY folks
tend to run at higher power levels. You may manage on RTTY at 5 watts,
but the full 100 watts from the KXPA100 will give you better success rates.

Note that the default bandwidth for DATA A and AFSK A data submodes is
narrow on the KX3. You will want to widen the bandwidth to give you a
full waterfall display on Fldigi. Click on the signal of interest to
decode it and you should transmit on that frequency.

Fldigi does not have an idle timeout, and that is what is telling me you
are trying to work with Fldigi in PSK D or FSK D data submodes. Those
work from characters entered via the paddles keying CW or in ASCII
characters from KX3 Utility terminal tab, but will not work with the
audio tones provided by Fldigi. Use DATA A mode for PSK and other
digital modes, and AFSK A for RTTY work.

73,
Don W3FPR

On 3/28/2016 7:06 PM, Terry Brown wrote:

> I am new to fldigi. I am using the SignaLink USB to interface between my
> KX3 and computer. I have my KX3 connected to fldigi using Hamlib rig
> control. That seems to work fine tracking the VFO and placing software into
> the right mode when I change it on the KX3. First, could someone tell me
> what power output I should be using for psk31, RTTY, and some of the other
> digital modes supported by fldigi? I do have the KXPA100 if I need more
> than 10 watts power.
>
>
>
> I can receive digital modes just fine. I am still trying to identify the
> various sounds other than PSK31 and RTTY which were the predominant ones I
> used about 9 years ago before my hiatus from Ham Radio.
>
>
>
>

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

K1BRA

Re: fldigi KX3 question

> On Mar 28, 2016, at 7:46 PM, Don Wilhelm <[hidden email]> wrote:
>
> Note that the default bandwidth for DATA A and AFSK A data submodes is narrow on the KX3.

Another one for the ‘Feature Request’ list. The “audio” data submode bandwidths are way too narrow out of the box. Does anyone have any idea why this is? I’m not sure I see much of a reason for any audio filtering at all other than the traditional 3K roofing filter. The downstream PC is going to do its own audio filtering at the DSP level before decoding the data anyway.

For the OP: If you like to tweak hardware, there are a number of performance improvements that can be made to the SignaLink USB hardware. Out of the box, its got a pretty high noise floor and is susceptible to noise on the USB +5 line, which directly feeds the onboard amp bias network without NO filtering. http://www.frenning.dk/OZ1PIF_HOMEPAGE/SignaLinkUSB-mods.html is a good place to start if you’re interested in better performance from your SignaLink.

Tim Henrion
KC1EOQ

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

Don Wilhelm-4

Re: fldigi KX3 question

Tim,

The default bandwidths are to work well with the internal decoder where
you tune to the desired signal with the VFO,
If you are using a computer application, widen the bandwidth and let the
software application do the decoding.

73,
Don W3FPR

On 3/28/2016 8:57 PM, Tim Henrion wrote:

>
>> On Mar 28, 2016, at 7:46 PM, Don Wilhelm <[hidden email]
>> <mailto:[hidden email]>> wrote:
>>
>> Note that the default bandwidth for DATA A and AFSK A data submodes
>> is narrow on the KX3.
>
> Another one for the ‘Feature Request’ list. The “audio” data submode
> bandwidths are way too narrow out of the box. Does anyone have any
> idea why this is? I’m not sure I see much of a reason for any audio
> filtering at all other than the traditional 3K roofing filter. The
> downstream PC is going to do its own audio filtering at the DSP level
> before decoding the data anyway.
>
> For the OP: If you like to tweak hardware, there are a number of
> performance improvements that can be made to the SignaLink USB
> hardware. Out of the box, its got a pretty high noise floor and is
> susceptible to noise on the USB +5 line, which directly feeds the
> onboard amp bias network without NO filtering.
> http://www.frenning.dk/OZ1PIF_HOMEPAGE/SignaLinkUSB-mods.html is a
> good place to start if you’re interested in better performance from
> your SignaLink.
>
>

K1BRA

Re: fldigi KX3 question

> On Mar 28, 2016, at 9:56 PM, Don Wilhelm <[hidden email]> wrote:
>
> Tim,
>
> The default bandwidths are to work well with the internal decoder where you tune to the desired signal with the VFO,
> If you are using a computer application, widen the bandwidth and let the software application do the decoding.
>
> 73,
> Don W3FPR
>

Hi Don,
While I understand that *some* of the data submodes are for decoding data on-board the radio, the “audio data modes” are specifically for getting audio data onto and off of the radio (i.e. no on-board decoding). When in AUDIO A data submode, the radio should be passing as much of the audio bandwidth through as the roofing filter being used would allow so that the computer software can see the entire passband.

Quoting the manual:
-----
Many audio-generated data transmissions can be heard on the bands, using PSK31, RTTY, Pactor, Olivia, MFSK, JT65 and other modes. A computer, sound card, and appropriate software are normally used. DATA A mode is provided for this purpose. Unlike SSB modes, DATA A disables compression and RX/TX EQ. Upper sideband is the default.
——

DATA A mode specifically disables compression and EQ to keep the radio from dorking with the TX/RX audio. It should be disabling audio bandwidth filtering as well, as there is no valid premise for the radio making assumptions about the audio being passed. Pretty much all digital decoding software allows multi-decode across the entire audio passband. The wideband Olivia modes can require up to 2Khz of audio bandwidth. Having the radio artificially impose audio bandwidth filtering narrower than the roofing filter bandwidth is pointless and counterproductive.

Tim Henrion
KC1EOQ

> On 3/28/2016 8:57 PM, Tim Henrion wrote:
>>
>>> On Mar 28, 2016, at 7:46 PM, Don Wilhelm < <mailto:[hidden email]>[hidden email] <mailto:[hidden email]>> wrote:
>>>
>>> Note that the default bandwidth for DATA A and AFSK A data submodes is narrow on the KX3.
>>
>> Another one for the ‘Feature Request’ list. The “audio” data submode bandwidths are way too narrow out of the box. Does anyone have any idea why this is? I’m not sure I see much of a reason for any audio filtering at all other than the traditional 3K roofing filter. The downstream PC is going to do its own audio filtering at the DSP level before decoding the data anyway.
>>
>> For the OP: If you like to tweak hardware, there are a number of performance improvements that can be made to the SignaLink USB hardware. Out of the box, its got a pretty high noise floor and is susceptible to noise on the USB +5 line, which directly feeds the onboard amp bias network without NO filtering. http://www.frenning.dk/OZ1PIF_HOMEPAGE/SignaLinkUSB-mods.html <http://www.frenning.dk/OZ1PIF_HOMEPAGE/SignaLinkUSB-mods.html> is a good place to start if you’re interested in better performance from your SignaLink.
>>
>>
>