RTTY
[Top] [All Lists]

Re: [RTTY] Intel NUC, anyone?

To: <rtty@contesting.com>
Subject: Re: [RTTY] Intel NUC, anyone?
From: "Dave AA6YQ" <aa6yq@ambersoft.com>
Date: Fri, 27 Oct 2017 16:20:14 -0400
List-post: <mailto:rtty@contesting.com>
>>>AA6YQ comments below

-----Original Message-----
From: RTTY [mailto:rtty-bounces@contesting.com] On Behalf Of Joe Subich, W4TV
Sent: Friday, October 27, 2017 2:11 PM
To: rtty@contesting.com
Subject: Re: [RTTY] Intel NUC, anyone?


 > Not clear on how MMTTY (in N1MM or in WinWarbler or by itself) talks  > to 
 > it, but clearly that hasn't stopped others.

MMTTY *does not* talk to tinyFSK or equivalent.  You treat it as an "External 
Modem" (like PK232 or KAM) in N1MM, WinWarbler, etc..
If your software can not transmit on one device and receive on another, you're 
out of luck with tinyFSK since it has no receive
capability.

>>>To be clear, WinWarbler simultaneously displays RTTY decoded by up to three 
>>>sources: the MMTTY engine, the 2Tone engines, and one
of GRITTY, your transceiver's built-in RTTY demodulator, or an external modem 
(KAM, PK232, MFJ, SCS, etc). If you configure
WinWarbler to use tinyFSK to transmit FSK, then you're limited to displaying 
RTTY decoded by the MMTTY and 2Tone engines.

       73,

              Dave, AA6YQ

_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty

<Prev in Thread] Current Thread [Next in Thread>