WriteLog
[Top] [All Lists]

Re: [WriteLog] WriteLog Digest, Vol 124, Issue 1

To: <writelog@contesting.com>
Subject: Re: [WriteLog] WriteLog Digest, Vol 124, Issue 1
From: "nrsmith" <nrsmith@citlink.net>
Date: Mon, 1 Apr 2013 12:45:02 -0500
List-post: <writelog@contesting.com">mailto:writelog@contesting.com>
This really seems like a lot of trouble to install my Writelog that has been working perfectly for years, and trying to figure out how to run this new 2tone program. I have down loaded the new version of Writelog and have the XMMT.ocx already on my contest computer from Don, AA5AU several weeks ago.

Will this thing work with just regular soundcards and FSK operation. Can someone explain this is simple terms as I am sure there a lot of guys out there like me that is totally confused.

Nick
w4gkm
----- Original Message ----- From: <writelog-request@contesting.com>
To: <writelog@contesting.com>
Sent: Monday, April 01, 2013 10:42 AM
Subject: WriteLog Digest, Vol 124, Issue 1


Send WriteLog mailing list submissions to
writelog@contesting.com

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.contesting.com/mailman/listinfo/writelog
or, via email, send a message with subject or body 'help' to
writelog-request@contesting.com

You can reach the person managing the list at
writelog-owner@contesting.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of WriteLog digest..."


Today's Topics:

  1. Fresh installation (Jim McDonald)
  2. MMTTY/2Tone (Gary AL9A)
  3. Re: Fresh installation (Ed Muns)
  4. Re: MMTTY/2Tone (now Hardware generated FSK with microKEYER)
     (Ed Muns)
  5. Re: MMTTY/2Tone (now Hardware generated FSK with microKEYER)
     (Joe Subich, W4TV)
  6. K3 fix for Flex (Jerry Pixton)
  7. Can not switch TNC??? (Jerry Pixton)
  8. Re: MMTTY/2Tone (now Hardware generated FSK with microKEYER)
     (Steve AI9T)


----------------------------------------------------------------------

Message: 1
Date: Sun, 31 Mar 2013 21:21:37 -0500
From: "Jim McDonald" <jim@n7us.net>
To: "'Writelog Reflector'" <writelog@contesting.com>
Subject: [WriteLog] Fresh installation
Message-ID: <002b01ce2e7f$a3ffd5e0$ebff81a0$@net>
Content-Type: text/plain; charset="US-ASCII"

I just renewed my subscription, and I'd like to make a fresh installation of
my full program.

How do I install WL on my Windows 7/64 system in a folder other than Program Files (x86)? I tried to do that with the installer but it didn't work. Do
I have to uninstall the existing installation?

73, Jim N7US







------------------------------

Message: 2
Date: Sun, 31 Mar 2013 21:37:34 -0800
From: "Gary AL9A" <al9a@mtaonline.net>
To: "Writelog Reflector" <writelog@contesting.com>
Subject: [WriteLog] MMTTY/2Tone
Message-ID: <41D9595133004EA591EA75530E02D3F8@AL9APC>
Content-Type: text/plain; charset="iso-8859-1"

I seem to have hit a bit of a stumbling block...

Downloaded WL V11.10G and installed the new update. I already had XMMT.ocx registered on my Vista machine because of an earlier install of N1MM a couple of years ago. Cleared out my RttyRite section in the ini file and then followed Don's directions on his web page. I can get both MMTTY and 2Tone to run using the ocx option on the TU Type menu, but there is something not right in both instances. When sending a macro the text appears to jump instantly onto the RttyRite screen, but the transmission is a problem. Either the TX drops out right away after just a few characters are sent or it sends a part of the string then hangs up for a couple of seconds and sends more of the macro then hangs up again. Sometimes it takes several seconds to TX to turn off despite having %E at the end of the macro. This happens with both 2Tone and MMTTY under ocx control. It sounds like those K3 ops who are using a CW paddle to key their RTTY transmissions.

When I switch back to the MMTTY plug in choice in the TU Type menu it transmits normally again. The only thing I notice that is different is that with the ocx option selected in the Ports drop down list there are three FSK keying options. The last one in the list is checked - Hardware FSK. I have the microHAM Router software running and use the MK II for FSK. Is there a setting somewhere I'm missing in RttyRite, MMTTY, 2Tone or Router? Not sure where to go or what to try next.

73,
Gary AL9A


------------------------------

Message: 3
Date: Mon, 1 Apr 2013 03:15:33 -0700
From: Ed Muns <w0yk@msn.com>
To: "'Writelog Reflector'" <writelog@contesting.com>
Subject: Re: [WriteLog] Fresh installation
Message-ID: <BLU0-SMTP44585C8C874F682C6CA120190DE0@phx.gbl>
Content-Type: text/plain; charset="us-ascii"

First uninstall any current installations of WriteLog. Until you do so, the
program uses the location of the current install.  I don't know how to
override that, but there may be a way. However, if there is no installation on the computer, then the new installation will give you a chance to change
the default location of Program Files (x86).

Ed W0YK


Jim N7US wrote:
How do I install WL on my Windows 7/64 system in a folder
other than Program Files (x86)?  I tried to do that with the
installer but it didn't work.  Do I have to uninstall the
existing installation?



------------------------------

Message: 4
Date: Mon, 1 Apr 2013 04:03:36 -0700
From: Ed Muns <w0yk@msn.com>
To: "'Writelog Reflector'" <writelog@contesting.com>
Cc: 'Gary AL9A' <al9a@mtaonline.net>, 'Jim McDonald' <jim@n7us.net>
Subject: Re: [WriteLog] MMTTY/2Tone (now Hardware generated FSK with
microKEYER)
Message-ID: <BLU0-SMTP382CEB15E91CF15B573757290DE0@phx.gbl>
Content-Type: text/plain; charset="us-ascii"

This is similar to Jim N7US's experience he posted yesterday and its taken
me this long to register what the issue might be.  I saw the same symptoms
on a friend's system that used the original microKEYER, but the problem may
be the same.

The short answer is that you must go into the microHAM Router and check
"Strict BPS" when you use Rttyrite's Hardware generated FSK. This may slow the data rate a bit, though Joe mentioned it was not as bad as he previously
thought.

The long answer ...

I forget why this isn't a problem with the MMTTY Plug-in.  Perhaps the
Plug-in gets the COM port number from Rttyrite's Port menu but still uses
MMTTY's FSK facility.  But, then I can't explain why this avoids the USB
buffering problem in the Router that Strict BPS gets around. Perhaps some
detail that differs between Rttyrite's hardware FSK and MMTTY's.  Joe will
know.

An alternative, if you use MMTTY as your main decoder/encoder, is to select "None" in the Rttyrite Port menu and use the MMTTY FSK feature, setting the
COM port number on the TX tab of the MMTTY Options window.

If using 2Tone for the main decoder, you must use Rttyrite's FSK facility
since there is not true FSK capability. If you use Hardware generated FSK, set "Strict BPS" in the Router. If you use Software generated FSK, it only
works with 45.45 Baud (60 wpm) RTTY.

And, finally, there is the option of using 2Tone's "Pseudo FSK" mode but
this requires a special hardware interface.  It is described in the 2Tone
PDF:

"TX FSK: The Pseudo FSK setting outputs a 5KHz tone on both left and right
channels of the selected
sound card. Tone is on for space and off for mark. A suitable detector
circuit can be found at
http://www.w1hkj.com/FldigiHelp-3.20/PseudoFSK.html but use 0.1uF in place
of 0.5uF. The output
connects to the FSK input of the rig. Search & Pounce: as the transmit
frequency does not change
with AFC, tune the rig so the small vertical AFC lines are co-incident with
or very close to the long
vertical lines. Not doing this will result in off frequency transmission."

When Joe resurfaces, he may have further comment.  Let me know if this
helps.

Ed W0YK

Gary AL9A wrote:
I seem to have hit a bit of a stumbling block...

Downloaded WL V11.10G and installed the new update.  I
already had XMMT.ocx registered on my Vista machine because
of an earlier install of N1MM a couple of years ago. Cleared
out my RttyRite section in the ini file and then followed
Don's directions on his web page.  I can get both MMTTY and
2Tone to run using the ocx option on the TU Type menu, but
there is something not right in both instances.  When sending
a macro the text appears to jump instantly onto the RttyRite
screen, but the transmission is a problem.  Either the TX
drops out right away after just a few characters are sent or
it sends a part of the string then hangs up for a couple of
seconds and sends more of the macro then hangs up again.
Sometimes it takes several seconds to TX to turn off despite
having %E at the end of the macro.  This happens with both
2Tone and MMTTY under ocx control.  It sounds like those K3
ops who are using a CW paddle to key their RTTY transmissions.

When I switch back to the MMTTY plug in choice in the TU Type
menu it transmits normally again.  The only thing I notice
that is different is that with the ocx option selected in the
Ports drop down list there are three FSK keying options.  The
last one in the list is checked - Hardware FSK.  I have the
microHAM Router software running and use the MK II for FSK.
Is there a setting somewhere I'm missing in RttyRite, MMTTY,
2Tone or Router?  Not sure where to go or what to try next.



------------------------------

Message: 5
Date: Mon, 01 Apr 2013 09:04:50 -0400
From: "Joe Subich, W4TV" <lists@subich.com>
To: writelog@contesting.com
Subject: Re: [WriteLog] MMTTY/2Tone (now Hardware generated FSK with
microKEYER)
Message-ID: <515985F2.4020900@subich.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed


The short answer is that you must go into the microHAM Router and
check "Strict BPS" when you use Rttyrite's Hardware generated FSK.
This may slow the data rate a bit, though Joe mentioned it was not
as bad as he previously thought.

Ed is correct ...

When "C: Limiting Speed" is selected in MMTTY's "USB Port" dialog, MMTTY
paces its FSK output - that is it sends one character to the
serial port every 165 ms.  This allows MMTTY to know what has been
sent (more importantly if there is still data to be sent) so it knows
when to drop PTT.  This is necessary because the system level drivers
for USB hardware have very large buffers that can not be disabled.
Software that does not use some form of pacing gets confused and either
sends too many diddles or drop PTT early (or both).

The equivalent to "limiting speed" in the Eltima VSPAX used in microHAM
Router is "strict BPS" which only sends a single character at a time to
Router.  Unfortunately, because the VSPAX is dealing with 8 bit data
instead of 5 bit (7.5 bit with start/stop bits) data, it calculates the
character rate at 176 (22 x 8) ms instead of 165 msec which results in
a slightly "slow" data (equivalent to 5N2 instead of 5N1.5).

When using "Hardware generated FSK" in WriteLog one must use "strict
BPS" in Router.  With MMTTY the alternative is to set no FSK port in
RTTYrite and configure MMTTY to generate the FSK.

Now that I have returned from my trip to Ohio for my mother's 90th
birthday, I will update the WriteLog examples for all of the microHAM
"Keyer" interfaces to document the new MMTTY interface and the option
of "Hardware generated FSK" with "Strict BPS" or MMTTY with "C:
Limiting Speed".  I had not expected a release while I was gone!

73,

   ... Joe, W4TV


On 4/1/2013 7:03 AM, Ed Muns wrote:
This is similar to Jim N7US's experience he posted yesterday and its taken me this long to register what the issue might be. I saw the same symptoms on a friend's system that used the original microKEYER, but the problem may
be the same.

The short answer is that you must go into the microHAM Router and check
"Strict BPS" when you use Rttyrite's Hardware generated FSK. This may slow the data rate a bit, though Joe mentioned it was not as bad as he previously
thought.

The long answer ...

I forget why this isn't a problem with the MMTTY Plug-in.  Perhaps the
Plug-in gets the COM port number from Rttyrite's Port menu but still uses
MMTTY's FSK facility.  But, then I can't explain why this avoids the USB
buffering problem in the Router that Strict BPS gets around. Perhaps some
detail that differs between Rttyrite's hardware FSK and MMTTY's. Joe will
know.

An alternative, if you use MMTTY as your main decoder/encoder, is to select "None" in the Rttyrite Port menu and use the MMTTY FSK feature, setting the
COM port number on the TX tab of the MMTTY Options window.

If using 2Tone for the main decoder, you must use Rttyrite's FSK facility
since there is not true FSK capability. If you use Hardware generated FSK, set "Strict BPS" in the Router. If you use Software generated FSK, it only
works with 45.45 Baud (60 wpm) RTTY.

And, finally, there is the option of using 2Tone's "Pseudo FSK" mode but
this requires a special hardware interface.  It is described in the 2Tone
PDF:

"TX FSK: The Pseudo FSK setting outputs a 5KHz tone on both left and right
channels of the selected
sound card. Tone is on for space and off for mark. A suitable detector
circuit can be found at
http://www.w1hkj.com/FldigiHelp-3.20/PseudoFSK.html but use 0.1uF in place
of 0.5uF. The output
connects to the FSK input of the rig. Search & Pounce: as the transmit
frequency does not change
with AFC, tune the rig so the small vertical AFC lines are co-incident with
or very close to the long
vertical lines. Not doing this will result in off frequency transmission."

When Joe resurfaces, he may have further comment.  Let me know if this
helps.

Ed W0YK

Gary AL9A wrote:
I seem to have hit a bit of a stumbling block...

Downloaded WL V11.10G and installed the new update.  I
already had XMMT.ocx registered on my Vista machine because
of an earlier install of N1MM a couple of years ago. Cleared
out my RttyRite section in the ini file and then followed
Don's directions on his web page.  I can get both MMTTY and
2Tone to run using the ocx option on the TU Type menu, but
there is something not right in both instances.  When sending
a macro the text appears to jump instantly onto the RttyRite
screen, but the transmission is a problem.  Either the TX
drops out right away after just a few characters are sent or
it sends a part of the string then hangs up for a couple of
seconds and sends more of the macro then hangs up again.
Sometimes it takes several seconds to TX to turn off despite
having %E at the end of the macro.  This happens with both
2Tone and MMTTY under ocx control.  It sounds like those K3
ops who are using a CW paddle to key their RTTY transmissions.

When I switch back to the MMTTY plug in choice in the TU Type
menu it transmits normally again.  The only thing I notice
that is different is that with the ocx option selected in the
Ports drop down list there are three FSK keying options.  The
last one in the list is checked - Hardware FSK.  I have the
microHAM Router software running and use the MK II for FSK.
Is there a setting somewhere I'm missing in RttyRite, MMTTY,
2Tone or Router?  Not sure where to go or what to try next.

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



------------------------------

Message: 6
Date: Mon, 01 Apr 2013 15:23:28 +0000
From: Jerry Pixton <jpixton@shentel.net>
To: writelog@contesting.com
Subject: [WriteLog] K3 fix for Flex
Message-ID: <5159A670.4070203@shentel.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Gang,

The slight change to the K3 rig driver allows the Flex 3000 and the Flex
5000 (with RX2 turned off, if installed) to work as many of the hardware
rigs we are used to using in the past. Split comes on when the VFO B is
selected for transmit focus by Writelog.

If you have a Flex, try it

Jerry, W6IHG
--
-----------------------------------------------
Dr. Jerry R. Pixton, PIXOS Designs
http://www.shentel.net/pixosdesigns/RadioTuner/
jpixton@shentel.net
-----------------------------------------------


------------------------------

Message: 7
Date: Mon, 01 Apr 2013 15:32:43 +0000
From: Jerry Pixton <jpixton@shentel.net>
To: writelog@contesting.com
Subject: [WriteLog] Can not switch TNC???
Message-ID: <5159A89B.3070204@shentel.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Has anyone else had a problem with 11.10 and changing TNCs?

Tried 11.10 yesterday (to try the new K3 rig driver), Windows 7, and the
regular rttyrite/mmtty plugin windows I always use. When I try to change
the TNC from mmtty to Stereo Sound Board AFSK to use the cw receiver,
mmtty dies and I get a rttyrite MFC error. Have to use the Task Manager
to get back to Writelog to start over.

Had to uninstall 11.10 and go back to 11.08 so mmtty plugin would work.

What did I miss? I see all the chatter re 2Tone but nothing that
indicates that mmtty plug-in might not work??? I was using the same
writelog.ini file that I used with 11.08.

Jerry, W6IHG
--
-----------------------------------------------
Dr. Jerry R. Pixton, PIXOS Designs
http://www.shentel.net/pixosdesigns/RadioTuner/
jpixton@shentel.net
-----------------------------------------------


------------------------------

Message: 8
Date: Mon, 01 Apr 2013 11:42:15 -0400
From: Steve AI9T <steve@ai9t.com>
To: writelog@contesting.com
Subject: Re: [WriteLog] MMTTY/2Tone (now Hardware generated FSK with
microKEYER)
Message-ID: <5159AAD7.5030504@ai9t.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

I am noticing that when I turn on strict bps it slows way down. I can
really hear the difference. I'm using the MKII

I have the same thing going on as AL9A and K7US

I didn't notice it yesterday but I didn't have much time to play with
it. I also have removed the normal MMTTY plugin since trying it yesterday.

--
73

Steve AI9T

http://www.ai9t.com

AI9T DX Cluster

Version 4 AI9T   Telnet: dxc.ai9t.com port 7300
Version 6 AI9T-2 Telnet: dxc.ai9t.com port 7373 (CW + Skimmer)




On 4/1/2013 9:04 AM, Joe Subich, W4TV wrote:

The short answer is that you must go into the microHAM Router and
check "Strict BPS" when you use Rttyrite's Hardware generated FSK.
This may slow the data rate a bit, though Joe mentioned it was not
as bad as he previously thought.

Ed is correct ...

When "C: Limiting Speed" is selected in MMTTY's "USB Port" dialog,
MMTTY paces its FSK output - that is it sends one character to the
serial port every 165 ms.  This allows MMTTY to know what has been
sent (more importantly if there is still data to be sent) so it knows
when to drop PTT.  This is necessary because the system level drivers
for USB hardware have very large buffers that can not be disabled.
Software that does not use some form of pacing gets confused and either
sends too many diddles or drop PTT early (or both).

The equivalent to "limiting speed" in the Eltima VSPAX used in microHAM
Router is "strict BPS" which only sends a single character at a time to
Router.  Unfortunately, because the VSPAX is dealing with 8 bit data
instead of 5 bit (7.5 bit with start/stop bits) data, it calculates the
character rate at 176 (22 x 8) ms instead of 165 msec which results in
a slightly "slow" data (equivalent to 5N2 instead of 5N1.5).

When using "Hardware generated FSK" in WriteLog one must use "strict
BPS" in Router.  With MMTTY the alternative is to set no FSK port in
RTTYrite and configure MMTTY to generate the FSK.

Now that I have returned from my trip to Ohio for my mother's 90th
birthday, I will update the WriteLog examples for all of the microHAM
"Keyer" interfaces to document the new MMTTY interface and the option
of "Hardware generated FSK" with "Strict BPS" or MMTTY with "C:
Limiting Speed".  I had not expected a release while I was gone!

73,

   ... Joe, W4TV


On 4/1/2013 7:03 AM, Ed Muns wrote:
This is similar to Jim N7US's experience he posted yesterday and its
taken
me this long to register what the issue might be.  I saw the same
symptoms
on a friend's system that used the original microKEYER, but the
problem may
be the same.

The short answer is that you must go into the microHAM Router and check
"Strict BPS" when you use Rttyrite's Hardware generated FSK. This may
slow
the data rate a bit, though Joe mentioned it was not as bad as he
previously
thought.

The long answer ...

I forget why this isn't a problem with the MMTTY Plug-in. Perhaps the
Plug-in gets the COM port number from Rttyrite's Port menu but still
uses
MMTTY's FSK facility.  But, then I can't explain why this avoids the USB
buffering problem in the Router that Strict BPS gets around. Perhaps
some
detail that differs between Rttyrite's hardware FSK and MMTTY's.  Joe
will
know.

An alternative, if you use MMTTY as your main decoder/encoder, is to
select
"None" in the Rttyrite Port menu and use the MMTTY FSK feature,
setting the
COM port number on the TX tab of the MMTTY Options window.

If using 2Tone for the main decoder, you must use Rttyrite's FSK
facility
since there is not true FSK capability.  If you use Hardware
generated FSK,
set "Strict BPS" in the Router.  If you use Software generated FSK,
it only
works with 45.45 Baud (60 wpm) RTTY.

And, finally, there is the option of using 2Tone's "Pseudo FSK" mode but
this requires a special hardware interface.  It is described in the
2Tone
PDF:

"TX FSK: The Pseudo FSK setting outputs a 5KHz tone on both left and
right
channels of the selected
sound card. Tone is on for space and off for mark. A suitable detector
circuit can be found at
http://www.w1hkj.com/FldigiHelp-3.20/PseudoFSK.html but use 0.1uF in
place
of 0.5uF. The output
connects to the FSK input of the rig. Search & Pounce: as the transmit
frequency does not change
with AFC, tune the rig so the small vertical AFC lines are
co-incident with
or very close to the long
vertical lines. Not doing this will result in off frequency
transmission."

When Joe resurfaces, he may have further comment.  Let me know if this
helps.

Ed W0YK

Gary AL9A wrote:
I seem to have hit a bit of a stumbling block...

Downloaded WL V11.10G and installed the new update.  I
already had XMMT.ocx registered on my Vista machine because
of an earlier install of N1MM a couple of years ago. Cleared
out my RttyRite section in the ini file and then followed
Don's directions on his web page.  I can get both MMTTY and
2Tone to run using the ocx option on the TU Type menu, but
there is something not right in both instances.  When sending
a macro the text appears to jump instantly onto the RttyRite
screen, but the transmission is a problem.  Either the TX
drops out right away after just a few characters are sent or
it sends a part of the string then hangs up for a couple of
seconds and sends more of the macro then hangs up again.
Sometimes it takes several seconds to TX to turn off despite
having %E at the end of the macro.  This happens with both
2Tone and MMTTY under ocx control.  It sounds like those K3
ops who are using a CW paddle to key their RTTY transmissions.

When I switch back to the MMTTY plug in choice in the TU Type
menu it transmits normally again.  The only thing I notice
that is different is that with the ocx option selected in the
Ports drop down list there are three FSK keying options.  The
last one in the list is checked - Hardware FSK.  I have the
microHAM Router software running and use the MK II for FSK.
Is there a setting somewhere I'm missing in RttyRite, MMTTY,
2Tone or Router?  Not sure where to go or what to try next.

_______________________________________________
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/




------------------------------

Subject: Digest Footer

_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog


------------------------------

End of WriteLog Digest, Vol 124, Issue 1
****************************************

_______________________________________________
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>