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:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
