Bill (et al), No, you do not need a TU - although MMTTY requires a single-transistor circuit for keying the rig from serial port of the computer (MMTTY uses an identical single transistor circuit that DX4WIN uses for PSK keying.
My installation runs DX4WIN with CW and PSK, and interfaces to MMTTY for RTTY. All of this can be done in a single computer with a single sound card - but since either DX4WIN/PSK or MMTTY/RTTY must "control" the sound card, you obviously cannot have the DX4WIN PSK window open at the same time you have the MMTTY software program running. You will get a message "Error starting the soundcard: Device already allocated.". Since I never run RTTY and PSK simultaneously (?) I do not see this as a disadvantage. After two years of running MMTTY and four years of using DX4WIN, I have managed to get the two working together in a way that best matches my needs (your mileage may vary...). 1. FOR EVERYDAY RTTY RAG-CHEWING, I run DX4WIN and MMTTY as separate programs. This means that I rely on the macros in MMTTY [which are more plentiful and full-featured than those in DX4WIN] for my QSOs, and then manually enter the data into DX4WIN for logging - and simply live with the inconvenience of manually recording the QSO info in the log. With this configuration -- without any changes, adjustments, or plugging/unplugging -- I can switch between SSB, RTTY, PSK and CW modes. Also, by controlling the RTTY QSO from within MMTTY, I have a much more pleasant "keyboard" experience - with typeahead buffers, backspace/delete keys, and other benefits. 2. FOR RTTY CONTESTING, I do not want to duplicate-enter data between MMTTY and DX4WIN- I want high speed operation with a limited set of RTTY macros in DX4WIN controlling the QSOs. To accomplish this, I cross-connect the two programs inside one computer using the MixW null modem freeware that allows two programs to talk to each other in/out a pair of phantom serial ports. A disadvantage of this arrangement is that the keyboard functions (backspace/delete, especially) from DX4WIN are a little funky - but as long as you are only sending short bursts of messages and macro-controlled transmissions, who cares? The big advantage is speed and simplicity - logging, contest counts, duplicate callsigns, and macros are all driven from one program - DX4WIN. In this configuration, MMTTY is used as a "background" RTTY engine. NOTE: The MixW null modem freeware only works on Windows 2000 and XP. If you are running an older operating system you will need to have two spare "real" serial ports to make MMTTY and DX4WIN talk to each other, using a null modem cable (plus a third serial port for rig keying from MMTTY). Finally - I have documented this configuration in a couple of files that describe all the settings and the macro strings that I use. Send me an email and I will gladly forward them to you. -larry K8UT ----- Original Message ----- From: "Bill Henderson" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Wednesday, January 01, 2003 8:19 AM Subject: [Dx4win] MMTTY > Hi > > Daft question but I am suffering from a bit of alcohol induced pain. > > Can you use dx4win with the likes of MMTTY or do you need a RTTY terminal unit? > > Bill GM0VIT > > --- StripMime Report -- processed MIME parts --- > multipart/alternative > text/plain (text body -- kept) > text/html > The reason this message is shown is because the post was in HTML > or had an attachment. Attachments are not allowed. > Please post in Plain-Text only.--- > _______________________________________________ > Dx4win mailing list > [email protected] > http://mailman.qth.net/mailman/listinfo/dx4win >
