K3 will not go into XMIT with MMTTY.EXTFSK

[Jay Kobelin]

As expected, the last stumbling block in preparing for the Dxpedition is RTTY. I am using WinTest which up to this point has been very east to setup.

I can't get the K3 to go into XMIT. Hit F1 (CQ T33A) in WinTest and it sings it annoying tones, MMTTY TX button goes ACTIVE, the RTTY XMIT pattern for the CQ appears and then drops off along with the TX button going inactive. So MMTTY appears to be OK

I would assume EXTFSK should be talking to the same COM port as the K3 is on but EXTFSK say Status NG in nice RED LETTERS when I select the K3 COM assignment (COM 10) in EXTFSK.

Looks like EXTFSK not getting to the K3

MMTTY and EXTFSK are both responsive (software wise).

CW messages key the K3 (and send the data) when placed in CW mode (CW = DTR and PTT = RTS) therefore we are controlling the PTT line via the 232/USB cable which appears to be functional

WinTest shows the following active ports

COM1
COM3
COM 6
COM10

Per the Device Manager
COM1 = "Communications port"
COM 3=  Printer (LPT1)
COM 6 = USB serial (Winkeyer assigned here)
COM10 = USB serial (K3 assigned here)

MMTTY
TX set port to EXTFSK
MISC COM -TxD (FSK)


K3
Set to FSK D
(no audio line connected yet as that's just data)
K3 set to  COM10
DTR=CW
RTS=PTT

EXTFSK module
FSK =TXD
PTT=RTS
COM 10 comes up as a NOGO but this needs to talk to the K3 port (COM 10 here) --- no?

COM1 & COM 3 are  the only ports that shows Status as OK but they, as expected, do nothing but show a conflict message.

Our Winkeyer is running on COM 6..operating fine

Need a little help ..

Tnx in advance
Jay
W2IJ
______________________________________________________________
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

[Don Wilhelm-4]

Jay,

Those applications must send ASCII over the same port that is connected
to the K3.
Do you have other applications running?  Only one application at a time
can open a COM port.
If two or more applications attempt to share the same COM port, the
second one will fail to connect.
If you do need to share one com port with 2 or more applications, you
can use LP-Bridge (google) to create virtual ports - the application
connects to a virtual LP-Bridge port and LP-Bridge connects to the K3.

73,
Don W3FPR

On 1/27/2013 1:08 PM, Jay wrote:

> As expected, the last stumbling block in preparing for the Dxpedition is RTTY. I am using WinTest which up to this point has been very east to setup.
>
> I can't get the K3 to go into XMIT. Hit F1 (CQ T33A) in WinTest and it sings it annoying tones, MMTTY TX button goes ACTIVE, the RTTY XMIT pattern for the CQ appears and then drops off along with the TX button going inactive. So MMTTY appears to be OK
>
> I would assume EXTFSK should be talking to the same COM port as the K3 is on but EXTFSK say Status NG in nice RED LETTERS when I select the K3 COM assignment (COM 10) in EXTFSK.
>
> Looks like EXTFSK not getting to the K3
>
> MMTTY and EXTFSK are both responsive (software wise).
>
> CW messages key the K3 (and send the data) when placed in CW mode (CW = DTR and PTT = RTS) therefore we are controlling the PTT line via the 232/USB cable which appears to be functional
>
> WinTest shows the following active ports
>
> COM1
> COM3
> COM 6
> COM10
>
> Per the Device Manager
> COM1 = "Communications port"
> COM 3=  Printer (LPT1)
> COM 6 = USB serial (Winkeyer assigned here)
> COM10 = USB serial (K3 assigned here)
>
> MMTTY
> TX set port to EXTFSK
> MISC COM -TxD (FSK)
>
>
> K3
> Set to FSK D
> (no audio line connected yet as that's just data)
> K3 set to  COM10
> DTR=CW
> RTS=PTT
>
> EXTFSK module
> FSK =TXD
> PTT=RTS
> COM 10 comes up as a NOGO but this needs to talk to the K3 port (COM 10 here) --- no?
>
> COM1 & COM 3 are  the only ports that shows Status as OK but they, as expected, do nothing but show a conflict message.
>
> Our Winkeyer is running on COM 6..operating fine
>
> Need a little help ..
>
>

______________________________________________________________
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

[Richard Ferch]

Don, that will not work. EXTFSK does not send ASCII over the radio
control port. What it does is use bit-banging techniques to twiddle the
TxD line on a serial port whose UART will not go slow enough to key 45
baud RTTY (that includes most USB-to-serial adapters). The port EXTFSK
uses cannot be shared using LP-Bridge, and MMTTY cannot use the radio
control port to key FSK RTTY, with or without help from EXTFSK.

73,
Rich VE3KI


W3FPR wrote:

> Those applications must send ASCII over the same port that is connected to the K3. Do you have other applications running? Only one application at a time can open a COM port. If two or more applications attempt to share the same COM port, the second one will fail to connect. If you do need to share one com port with 2 or more applications, you can use LP-Bridge (google) to create virtual ports - the application connects to a virtual LP-Bridge port and LP-Bridge connects to the K3.

______________________________________________________________
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

[Don Wilhelm-4]

Sorry, I did not know that.  That means it should ideally work through a
real serial port and must use the "one transistor" keying interface to
translate the TxD RS-232 levels to TTL - then feed the TTL output to the
FSK pin on the K3 ACC connector.

73,
Don W3FPR

On 1/27/2013 2:47 PM, Richard Ferch wrote:

> Don, that will not work. EXTFSK does not send ASCII over the radio
> control port. What it does is use bit-banging techniques to twiddle
> the TxD line on a serial port whose UART will not go slow enough to
> key 45 baud RTTY (that includes most USB-to-serial adapters). The port
> EXTFSK uses cannot be shared using LP-Bridge, and MMTTY cannot use the
> radio control port to key FSK RTTY, with or without help from EXTFSK.
>
> 73,
> Rich VE3KI
>
>
> W3FPR wrote:
>
>> Those applications must send ASCII over the same port that is
>> connected to the K3. Do you have other applications running? Only one
>> application at a time can open a COM port. If two or more
>> applications attempt to share the same COM port, the second one will
>> fail to connect. If you do need to share one com port with 2 or more
>> applications, you can use LP-Bridge (google) to create virtual ports
>> - the application connects to a virtual LP-Bridge port and LP-Bridge
>> connects to the K3.
>
> ______________________________________________________________
> 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
>

______________________________________________________________
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