Hints and tips for setting up W1FB & MMTTY

PLEASE NOTE: It would be far better to change to Writelog or N1MM!

After changing the shack PC, I found that I was suffering with stray RF, so decided to try and get MMTTY to work with the WF1B contest software. I had always wanted to try this, but just never got around to making the necessary null-modem cable. Besides, my setup had always worked well enough, and I am not keen on changing something that works!

I used to have a P200 with 40MB RAM and a 1GB HDD, but after changing my main PC, I had a spare P200MMX with 64 MB RAM and a 3GB HDD. While I was doing this, I wanted to try using two monitors with W98SE, and that worked fine. I used two 4MB PCI graphics cards to do this, which made life a bit easier for me. If you want to try it, it is not as difficult as it appears if you read the Microsoft help files! If you have an AGP card, and add a PCI card, the PCI card will become the primary card, unless you have a more recent BIOS that allows you to change this. If you still have PCI graphics, then adding another PCI card (at least 4MB) should make it all happen.

Using the two monitors allowed me the possibility of running the WF1B software on the main screen, and running the DX Cluster and MMTTY on the other.

I used the setup shown here to run the ANARTS RTTY contest over the weekend of 9/10 June 2001, and made 251 QSO's for 1.4 million points.

It is also necessary to have enough COM ports to do the job as well! I installed an extra two, giving me a total of 4 available COM ports. This may seem excessive, but they are all used.

COM1 is for my Yaesu CAT interface; COM4 is the DX Cluster; and COM2 and COM3 are used for this project.

You need a good null-modem cable before you go any further, and the picture here shows you the links you need to make using 9 way D connectors.



I am not saying that this is the correct way to wire a null-modem cable, but it works for me!

I used short pieces of wire to link pins 7 and 8, and also pins 6, 1 and 4 at each end.

Before you go any further, I suggest that you make backup copies of MMTTY and of WF1B, just in case anything goes wrong.

Just to be on the safe side, I created copies of each folder on my hard drive, and now I have one copy of MMTTY for WF1B, and a copy of WF1B for use with MMTTY. If I ever need to go back to my original TNC, I only need to use the other folders for this. It does save having to change the INI files of each program.



Setting up MMTTY

The next thing to do is to set up MMTTY with TNC Emulation.

Open the copy of MMTTY you are going to use, and click on OPTION, and then TNC EMULATION.
















Make sure you have the port settings as shown above.

They are 9600 Baud, 8 bits, NO parity, 1 stop bit, and also XON/XOFF is ticked.

I also have LOCAL ECHO set to ON, but you may need to experiment with this.

You must select a COM port here! PLEASE NOTE: I have used COM 3 for my setup. You will need to select an appropriate port. Once you have this done, click OK.

This next picture shows the SETUP option, and here you will see that I have set AFC as fixed, which keeps the SHIFT set at 170Hz.













Below you can see the settings I have used. However, they are up to you!












I personally find the "lower" tones better, so that is what I have set.

I have also turned AFC off, as this makes sure MMTTY does not try and tune in a station close to the one I want.

As AFC is off, this also has the effect of turning off NET. I have REVerse set, as I always operate in USB.

You will need to set whatever is best for you concerning tones and sideband.

When I first got all this going happily, I found that my transmitted signal was broken, and sounded very stuttered.

I also noticed "LOST" in the spectrum window. If you have read the TNC EMULATION document, you will note that it says that you can cure this by increasing the soundcard buffer.

Click on OPTION, SETUP MMTTY, and click on the MISC tab.

Here, you will see that you can increase the soundcard buffer.

The default is 1024, and I increased mine to 4096, and that cured the problem for me.

















That is about it for MMTTY, although you may wish to play around with some of the settings.

Setting up WF1B

There isn't much to do here, other than set the COM PORT that the fake KAM will be on.
Make sure the settings match those set in MMTTY of 9600 8N1 and XON/XOFF.
Again, my port is COM 2, but you will need to select the appropriate port for your own use.
This is what your Port setting in RTTY.INI should look like:


Now, when you start WF1B, select KAM as the TNC type, and you should start to see WF1B decoding signals.

If you are only using one monitor, you may want to resize the WF1B window, and then move the MMTTY window down so that you see the tuning scope. It is up to you to find a suitable layout!

Note that if you wish, you are able to send text or macros directly from MMTTY.

With a bit of thought, you may well be able to use this to your advantage in a contest!

Points to Note:

I did notice that when I tuned around, the scope in MMTTY seemed a bit slower that I am used to.

This may have been because of the way I set things up, but I will have to check that out.

Please do NOT tell me that I have got various settings wrong, or that the null-modem cable is not correct!

This is what I tried, and the way I got it going. It works for me! If it doesn't work for you,
then I can only suggest that you go and study the documents available, and come up with something better.

However, I am willing to concede that some settings could be modified for better usage.

I must give thanks to Jan Ditzian, KX2A, and Bill Musa, K5YG who conspired to write the TNC EMULATION document. And also many thanks to Mako JE3HHT for making it all possible in the first place.




Any comments or suggestion, please send to

phil (at) gu0sup (dot) com