On 3/8/2018 10:58 AM, Jeff Stai wrote:
hi Gary - Ed's right. If I were to just give you a direction, go back
to MMTTY by itself and make sure it is working correctly in AFSK or
FSK, whichever you do.
In addition, make sure that you are not trying to do "radio control"
from the stand alone version of MMTTY (Option -> Setup MMTTY -> TX ->
Radio command).
If you have configured MMTTY for radio control using the same port as
WriteLog will use for radio control, you will *certainly* get a port
conflict when you try to start the RTTYrite window using MMTTY with
either the old "plug-in" or new ".ocx" interfaces.
If you normally use radio command with MMTTY in stand-alone mode, create
another directory and copy only MMTTY.exe, EXTFSK.dll or ETFSK64.fsk (if
you use EXTFSK to support a USB based serial port), USERPARA.ini,
MMTTY.chm and XMMT.ocx into the new directory. Then when asked for the
path to MMTTY/XMMT.ocx, *USE THE NEW DIRECTORY*. Note: this is the same
procedure (creating a new directory) that one would use to create two
MMTTY windows in RTTYrite.
73,
... Joe, W4TV
On 3/8/2018 10:58 AM, Jeff Stai wrote:
hi Gary - Ed's right. If I were to just give you a direction, go back to
MMTTY by itself and make sure it is working correctly in AFSK or FSK,
whichever you do. I would then suggest using MMTTY as your first RTTYrite
window, before trying anything else.
Nex, you're new to V12 of Writelog so as a first step I'd make sure you
understand how editing writelog.ini works in the new version.
Then I would do this so that you start completely from scratch:
http://www.rttycontesting.com/tutorials/writelog/clearing-rttyrite/
This will make sure you don't have any previous settings hanging around to
give you COM port errors etc.
Then carefully follow the steps here to install xmmt.ocx and then MMTTY:
http://www.rttycontesting.com/tutorials/writelog/xmmt-support-for-mmtty-2tone/
and
http://www.rttycontesting.com/tutorials/writelog/mmtty-setup/
73 jeff wk6i
On Thu, Mar 8, 2018 at 7:09 AM, Ed Muns <ed@w0yk.com> wrote:
A Com port is only used for FSK, but you mention choosing AFSK below. So
first of all, decide which transmission method you are going to use: FSK or
AFSK. What did you use in the past with WL version 11?
Next, decide if you will use MMTTY's FSK or AFSK feature or if you will use
the Rttyrite native FSK or AFSK. Which one of these four choices requires
a
different configuration.
If you are trying to use AFSK transmission, then go into the MMTTY Options
menus and select 'None' for the Com port.
The Windows error message about the Com port not being available means that
you have a Com port selected in MMTTY (and, are therefore trying to setup
for FSK) that is in use by another device or that Windows thinks is
assigned
to some interface. Make sure nothing is using the Com port number you want
to use for your FSK interface. Sometimes, Windows will say a Com port is
in
use only because it saved that configuration from a prior use of that Com
port number. In that case, you can just ignore the message and use that
number. Windows will then reassign it to your current interface, though it
may take an exit and reload of WL and/or Windows.
Rest assured that WL 12 works fine, just as WL 11 did, for either FSK or
AFSK RTTY transmission. But, of course, it has to be configured correctly.
Ed W0YK
-----Original Message-----
From: WriteLog [mailto:writelog-bounces@contesting.com] On Behalf Of Gary
Gross
Sent: 06 March, 2018 22:03
To: writelog@contesting.com
Subject: [WriteLog] Need RTTY help with version 12.23j
Back in January I purchased V12.23j after running version 11 for many years
without any problems. I haven't been able to get my rtty running
successfully yet. I usually run MMTTY with writelog rittywrite for RTTY.
Every time I click my mouse on the call sign entry box my ritty screen
disappears. I had previously asked for help with this problem and was told
to download and register xmmt.ocx and delete the original mmtty plug in
module which I also did. Still no luck. If I change TU mode in the ritty
screen to xmmt.ocx I receive a com port not available message. If I choose
Soundboard AFSK in the TU section I get the same results, the ritty screen
still goes away. Please help. Thank-you. Gary KE6QR
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
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/
|