That's exactly what happened. I had configured something that was
interpreted as COM6 was in use.
Because I had selected the K1EL Winkey in the Ports tab, writelog wrote a
cwtype=6 into the [Ports] section of the writelog.ini file, and the MMTTY
plug-in just saw "something = 6" and thought COM6 was in use.
Dick
-----Original Message-----
From: Joe Subich, W4TV [mailto:w4tv@subich.com]
Sent: Sunday, January 06, 2008 9:38 PM
To: dieven@msn.com; writelog@contesting.com
Subject: RE: [WriteLog] FW: FW: WriteLog, MMTTY plug-in, MK2R+,Carrier only
on transmit
Dick,
I can run the MMTTY plug-in on COM6 even with K1EL WinKey selected
as the CW type. Make sure you have not configured something else to
use COM6 in the Writelog Ports Setup dialog.
73,
... Joe, W4TV
> -----Original Message-----
> From: writelog-bounces@contesting.com
> [mailto:writelog-bounces@contesting.com] On Behalf Of Dick Dievendorff
> Sent: Sunday, January 06, 2008 10:06 PM
> To: writelog@contesting.com
> Subject: [WriteLog] FW: FW: WriteLog, MMTTY plug-in,
> MK2R+,Carrier only on transmit
>
>
> I found out that when I select "K1EL winkey" on the Writelog
> Ports tab that
> it sets cwtype=6 in the [Ports] section of writelog.ini. So
> cwtype must be
> the result of selecting one of the CW keyer types on the
> WriteLog Port Setup
> dialog.
>
> My guess is that either writelog or the MMTTY plug-in are scanning the
> writelog.ini file, [Ports] section, and find cwtype=6 and erroneously
> interpret this to mean that "COM6 is in use" and therefore
> won't allow its
> use in RTTYrite.
>
> To test this hypothesis, I changed the RTTYrite Ports tab and microHAM
> Router setting for the FSK port to COM5, and I found that the
> radio buttons
> that were disabled before are now enabled.
>
> So it's just a bug in interpretation of a keyword in the
> [Ports] section
> that can be circumvented by avoiding a COM port number that happens to
> correspond to the keyer type you have. Just another little thing to
> remember...
>
> I'm not sure how to contact SM6SRW, or if it's his bug or something in
> WriteLog.
>
> 73 de Dick, K6KR
>
>
> -----Original Message-----
> From: writelog-bounces@contesting.com
> [mailto:writelog-bounces@contesting.com] On Behalf Of Dick Dievendorff
> Sent: Sunday, January 06, 2008 6:49 PM
> To: 'Joe Subich, W4TV'; writelog@contesting.com
> Subject: Re: [WriteLog] FW: WriteLog, MMTTY plug-in, MK2R+,
> Carrier only on
> transmit
>
> Joe, thanks (again) for your suggestions.
>
> I did find and checked the Strict BPS checkbox on the Ports tab.
>
> I added a couple of characters to each of my RTTY messages in
> the Writelog
> memory setup.
>
> I unchecked Software Generated FSK on the RttyRite Port tab.
>
> The Port (COM6) on the RTTYrite Ports tab matches the COM6 I
> have for FSK in
> the microHAM Ports tab.
>
> However under RTTYrite TU menu, TNC Setup..., MMTTY
> Settings... Misc Tab,
> the Tx Port area has Sound + COM+TxD and Com+Txd radio
> buttons that you're
> telling me I need to select (I agree with you). Those radio
> buttons are
> still disabled. That continues to be the main problem.
>
> I've restarted the computer, which was one suggestion.
>
> When I "Save Configuration" in WriteLog, I get a popup
> indicating that it
> "can't save wave recording file to:", which leads me to
> wonder if there's an
> RTTY mode missing somewhere. I searched in vain for an RTTY
> mode switch.
>
> I did open the writelog.ini file, and found under the [Ports] tab that
> there's a "cwtype=6" statement. I found no other mention of
> "cwtype" in the
> WriteLog help. Hmm. Maybe nothing should =6 in the [Ports]
> section of
> writelog.ini.
>
> When I changed cwtype=6 to cwtype=9 in the writelog.ini file,
> I found the
> Rttyrite TU menu, TNC setup, MMTTY settings, Misc tab, tx
> port area radio
> buttons were now enabled, and I was able to check the bottom
> one and I am
> now sending RTTY.
>
> Maybe I'll be ready in time for the next contest!
>
> Does anyone know what cwtype= means in the [Ports] section of
> writelog.ini?
>
> 73 de Dick, K6KR
>
> -----Original Message-----
> From: writelog-bounces@contesting.com
> [mailto:writelog-bounces@contesting.com] On Behalf Of Joe Subich, W4TV
> Sent: Saturday, January 05, 2008 6:12 PM
> To: dieven@msn.com; writelog@contesting.com
> Subject: Re: [WriteLog] FW: WriteLog, MMTTY plug-in, MK2R+,
> Carrier only on
> transmit
>
>
> Dick,
>
> > When I fire up WriteLog 10.42D and configure the ports, I
> > have selected COM6 in the RTTYrite window and have checked
> > Software generated FSK DTR.
>
> Do not use "Software generated FSK." Treat MK2R+ and Router
> as if they were a hardware UART. Check "strict BPS" on the
> FSK port of Router and add two or three extra spaces at the
> end of the Writelog macro (if using RTTrite).
>
> If using MMTTY, do not use "Software generated FSK." In the
> MMTTY plug-in configuration select "Sound + COM-TxD" or
> "COM-TxD" on the Misc tab or the MMTTY set-up screen. Then
> click "USB Port" and select "C: Limiting Speed" so MMTTY will
> pace the characters properly.
>
> 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 Dick
> Dievendorff
> > Sent: Saturday, January 05, 2008 7:14 PM
> > To: WriteLog@contesting.com
> > Subject: [WriteLog] FW: WriteLog, MMTTY plug-in,
> > MK2R+,Carrier only on transmit
> >
> >
> > Plain MMTTY, without Writelog, will send FSK. So it's
> > something I have
> > wrong between WriteLog, MMTTY Plug-in and MMTTY.
> >
> >
> >
> > From: Dick Dievendorff [mailto:dieven@comcast.net]
> > Sent: Saturday, January 05, 2008 3:46 PM
> > To: 'WriteLog@contesting.com'
> > Subject: WriteLog, MMTTY plug-in, MK2R+, Carrier only on transmit
> >
> >
> >
> > I'm trying (for the first time) to get Writelog, MMTTY, the
> > MMTTY plug-in
> > and an MK2R+ running for a few QSOs before the ARRL RU ends.
> >
> >
> >
> > I can receive RTTY fine.
> >
> >
> >
> > I'm sending carrier only.
> >
> >
> >
> > When I have Writelog shut down, the microHAM router Ports
> > tab, FSK says
> > "COM 6" and the PTT checkbox is checked. When I click Test
> > and listen on
> > another receiver, I can hear FSK. I believe therefore that
> my MK2R is
> > keying the rig (PTT) and shifting frequency (FSK).
> >
> >
> >
> > The radio is an IC-7800 in RTTY mode.
> >
> >
> >
> > When I fire up WriteLog 10.42D and configure the ports, I
> > have selected COM6
> > in the RTTYrite window and have checked Software generated FSK DTR.
> >
> >
> >
> > Under RTTYrite TU type (MMTTY) MMTTY settings, Misc tab, the
> > Tx port shows
> > COM -Txd (FSK) selected, but it's greyed out. AA5LU's very
> > nice tutorial
> > tells me that this is an indication that a port has not been
> > selected. But
> > I think I have selected the Port in the Rttyrite window,
> it's COM6.
> >
> >
> >
> > Obviously I'm missing a step. Can anyone suggest a way to
> get TX FSK
> > working?
> >
> >
> >
> > TU & 73 de Dick, K6KR
> >
> >
> >
> >
> >
> > _______________________________________________
> > WriteLog mailing list
> > WriteLog@contesting.com
> > http://lists.contesting.com/mailman/listinfo/writelog
> > WriteLog on the web: http://www.writelog.com/
> >
> >
>
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web: http://www.writelog.com/
>
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web: http://www.writelog.com/
>
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web: http://www.writelog.com/
>
>
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|