WriteLog
[Top] [All Lists]

Re: [WriteLog] RTTY INTERFACE

To: "'W7RY'" <w7ry@centurytel.net>, <writelog@contesting.com>
Subject: Re: [WriteLog] RTTY INTERFACE
From: "Joe Subich, W4TV" <w4tv@subich.com>
Date: Sun, 16 Jul 2006 23:45:57 -0400
List-post: <mailto:writelog@contesting.com>
Jim, 

> Why shift all the blame to Writelog?  

Who is blaming Writelog? 

> Why doesn't MicroHAM take some take some responsibility?

 Since when should microHAM be responsible to add features not provided 
by a program's author (in this case the author of the MMTTY plug-in for 
Writelog)?  microHAM supports EXTFSK (that support was ADDED in USB II - 
it does not exist in the previous USB Interface) but the MMTTY plug-in 
for WriteLog does not support EXTFSK for ANY device. . 

> How about MicroHAM adds another virtual com port and decode 
> and utilize "TXD" for an FSK output? 

That's what is done in the microcontroller based devices (microKEYER 
and DigiKeyer).  However, USB Interface II is a simple USB to Serial 
UART with no practical way to remap I/O lines.  

The line mapping can be done in Router *EVENTUALLY* but since that 
function is not included in the third party virtual port code, doing
so will require a large commitment of programmer hours (programmer 
days) to write a custom VSP.  That programming time is simply not 
available or justifiable for a low cost, low margin product.   

150% of the available programmer hours are currently committed 
to completing the SO2R products and a major update to Router with 
added features for microKEYER.  Following that, the priority will 
be making Router work with Vista and 64 bit operating systems. 

The real solution to FSK using USB to serial adapters from Writelog 
and the MMTTY plug-in is to enable EXTFSK using MMTTY.INI instead of 
a port passed from RTTYrite as is done with the other applications.  
The issue is not unique to USB Interface II ... it effects EVERY USB 
-> Serial adapter (other than the few adapters that directly support 
five bit codes) used with the MMTTY plug-in.  

73, 

   ... Joe Subich, W4TV 
       microHAM America 
       http://www.microHAM-USA.com 
       http://groups.yahoo.com/group/microHAM 
       support@microham.com 
 

 

> -----Original Message-----
> From: writelog-bounces@contesting.com 
> [mailto:writelog-bounces@contesting.com] On Behalf Of W7RY
> Sent: Sunday, July 16, 2006 10:03 PM
> To: writelog@contesting.com
> Subject: Re: [WriteLog] RTTY INTERFACE
> 
> 
> How about MicroHAM adds another virtual com port and decode 
> and utilize "TXD" for an FSK output?  
> 
> Why shift all the blame to Writelog?  Why doesn't MicroHAM take some
> take some responsibility?
> 
> 
> 73
> Jim W7RY
> 
> 
> -----Original Message-----
> From: writelog-bounces@contesting.com
> [mailto:writelog-bounces@contesting.com] On Behalf Of Joe Subich, W4TV
> Sent: Sunday, July 16, 2006 9:51 AM
> To: 'Ed'; writelog@contesting.com
> Subject: Re: [WriteLog] RTTY INTERFACE
> 
> 
> Ed, 
> 
> As I responded to Froggy on the microHAM support e-mail: 
> 
> > Writelog and the MMTTY plug-in do not support EXTFSK.  The MMTTY 
> > plug-in does not read the "active" port from MMTTY.INI - instead 
> > it takes the port selection from Writelog (notice that the MMTTY 
> > set-up TX tab has no "PTT Port" selection).  Writelog does not 
> > provide an EXTFSK option on the RTTYrite "Ports" menu.
> >  
> > Writelog's internal "Software FSK" is limited to the TxD line 
> > (which USB Interface II uses for CAT) and the MMTTY plug-in 
> > cannot independently select EXTFSK, USB II does not support FSK 
> > with Writelog (it does with MMTTY alone or MMTTY when used with 
> > other software including Logger32, DX4Win, DXLab Suite/WinWarbler, 
> > and N1MM Logger). 
> 
> This not a "fault" of any software or hardware ... simply a lack 
> of a common interface.    
> 
> The potential solutions are: 
>   1) the ability of Writelog to use DTR for "software FSK" 
>   2) adding the capability to map TxD to DTR in microHAM Router 
>      to support the Writelog Software FSK 
>   3) modifying the (third party) MMTTY plug-in for Writelog to 
>      allow specifying the output (PTT) port directly in the 
>      plug-in (using MMTTY.INI) 
>   4) Adding EXTFSK as a choice in the RTTYrite "Ports" list so 
>      EXTFSK can be passed to the plug-in. 
> 
> In the meantime, USB Interface II will work with WriteLog and 
> the MMTTY plugin if MMTTY is configured for AFSK (Sound + COM-TxD). 
> 
> 73, 
> 
>    ... Joe Subich, W4TV 
>        microHAM America 
>        http://www.microHAM-USA.com 
>        http://groups.yahoo.com/group/microHAM 
>        support@microham.com 
>  
> 
> 
> 
> > -----Original Message-----
> > From: writelog-bounces@contesting.com 
> > [mailto:writelog-bounces@contesting.com] On Behalf Of Ed
> > Sent: Sunday, July 16, 2006 11:11 AM
> > To: writelog@contesting.com
> > Subject: Re: [WriteLog] RTTY INTERFACE
> > 
> > 
> > K8fu@aol.com wrote:
> > > I'm seeking recommendations for an interface unit that will 
> >  work with
> > > WriteLog for MMTTY in FSK.
> >  
> > > My first choice was the MicroHAM USB ll............... but 
> > it  will not support WriteLog.
> > ----------------
> > Well, I bought the Microham USB II about a month ago, and it does OK
> > on everything with Writelog except RTTY. Rig will key, and 
> MMTTY shows
> > messages but absolutely no shift on the carrier. All other 
> modes work
> > OK.
> > 
> > Friend and I have spent about 10 hours trying to fix it with no go.
> > Also downloaded the EXTFSK file and installed it, but no 
> help. Virtual
> > ports set up by the software work fine.
> > 
> > Just about ready to junk the thing. Went back to my 
> homebrew interface
> > for the NAQP, and it worked fine.
> > 
> > Oh, rig is an OMNI VIB+, WL 10.54, and tower computer.
> > 
> > Would be interested in something that WORKS!
> > 
> > 73
> > Ed

_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/

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