Elecraft

Fwd: Elecraft post acknowledgement

Classic

List

Threaded

2 messages Options

Joe N9OK

Fwd: Elecraft post acknowledgement

73, Joe N9OK

Some progress and an observation.

I went thru KE7X's handy tutorial about how to make things work, and I had
temporary success. Here's the process, paraphrased:
* Ensure that MENU:MIC SEL is set to LINE IN and MENU:MIC+LIN is OFF
* Optionally, set CONFIG:AFSK TX to FIL On. This adds a 400 Hz transmit
audio filter to the AFSK signal to improve transmit signal-to-noise.
* Hold TEST to put the K3S into transmit test mode. The TX icon will start
to flash.
* You may have to adjust the Main menu's VOX GN to get the audio from the
computer to reliably key the transmitter.
* If you are in transmit test mode, hold TEST to return to normal transmit.
Note that all these settings were already set up correctly, but I carefully
went thru the process and toggled each item off the correct setting, then
back on.

So, things were working perfectly, where I could transmit diddles directly
from MMTTY. However, after I rebooted, things did not work after that.

Proper operation was achieved again by modifying this menu pick: DATA MD:
AFSK A:45 bps <-- modify to 75pbs. Now I can transmit again. Put it back to
45 where it belongs. I can still transmit at that point.

What can cause this? Any ideas?

Thanks to all those who provided ideas and assistance, both within the
reflector and outside it.

73, Joe N9OK

On Sun, Mar 15, 2020 at 12:49 PM Joe N9OK <[hidden email]> wrote:

> Rich - yes, my MIC input is correctly set to Line In.
>
> 73 Joe N9OK
>
>
> "In the Main Menu do you have:
>
> MAIN = MIC SEL = LINE IN set ?
>
> I think that is what fixed mine.
>
> Rich
>
> K3RWN"
>
> 73, Joe N9OK
>
>
> On Sun, Mar 15, 2020 at 12:46 PM <[hidden email]> wrote:
>
>> Your message entitled
>>
>> Re: K3 w/KIO3B has confusing RTTY transmit behavior
>>
>> was successfully received by the Elecraft mailing list.
>>
>> List info page: http://mailman.qth.net/mailman/listinfo/elecraft
>> Your preferences:
>> http://mailman.qth.net/mailman/options/elecraft/n9ok%40myjdk.com
>>
>

______________________________________________________________
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]

Joe N9OK

K3 w/KIO3B has confusing RTTY transmit behavior

Sorry... I posted this and it went to the wrong topic line. If there's a
web interface for this reflector I'd rather use it. Right now using email
interface. Sorry for the double posting.

73, Joe N9OK

Some progress and an observation.

I went thru KE7X's handy tutorial about how to make things work, and I had
temporary success. Here's the process, paraphrased:
* Ensure that MENU:MIC SEL is set to LINE IN and MENU:MIC+LIN is OFF
* Optionally, set CONFIG:AFSK TX to FIL On. This adds a 400 Hz transmit
audio filter to the AFSK signal to improve transmit signal-to-noise.
* Hold TEST to put the K3S into transmit test mode. The TX icon will start
to flash.
* You may have to adjust the Main menu's VOX GN to get the audio from the
computer to reliably key the transmitter.
* If you are in transmit test mode, hold TEST to return to normal transmit.
Note that all these settings were already set up correctly, but I carefully
went thru the process and toggled each item off the correct setting, then
back on.

So, things were working perfectly, where I could transmit diddles directly
from MMTTY. However, after I rebooted, things did not work after that.

Proper operation was achieved again by modifying this menu pick: DATA MD:
AFSK A:45 bps <-- modify to 75pbs. Now I can transmit again. Put it back to
45 where it belongs. I can still transmit at that point.

What can cause this? Any ideas?

Thanks to all those who provided ideas and assistance, both within the
reflector and outside it.

73, Joe N9OK

On Sun, Mar 15, 2020 at 12:49 PM Joe N9OK <[hidden email]> wrote: