Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+DXP38\s+vs\s+MMTTY\s+tuning\s+faceoff\s*$/: 16 ]

Total 16 documents matching your query.

1. [RTTY] DXP38 vs MMTTY tuning faceoff (score: 1)
Author: wa9als@starband.net (WA9ALS - John)
Date: Mon, 24 Sep 2001 22:13:34 -0500
If you're interested, please take a look at http://www.qsl.net/wa9als/dxp38.gif This is print from a RTTY signal on 20M awhile ago. It sounded fairly weak; Although I didn't get a look at the S-meter
/archives//html/RTTY/2001-09/msg00281.html (8,947 bytes)

2. [RTTY] DXP38 vs MMTTY tuning faceoff (score: 1)
Author: w2ki@amsat.org (John Hirth)
Date: Tue, 25 Sep 2001 09:54:08 -0400
John, The first thing I notice is that at the time of the image your MMTTY demodulator was not set for 2125 Hz Mark. Notice the "2093" in the "Mark" box in the control panel. This is the frequency to
/archives//html/RTTY/2001-09/msg00286.html (10,782 bytes)

3. [RTTY] DXP38 vs MMTTY tuning faceoff (score: 1)
Author: dhill@cprk.com (Hill, Don)
Date: Tue, 25 Sep 2001 10:16:06 -0500
Despite MMTTY not being properly "tuned", it still out copied the DXP38 (in this situation). For anyone using WriteLog and not subscribed to the WriteLog reflector, I've added pages to my WriteLog si
/archives//html/RTTY/2001-09/msg00287.html (12,566 bytes)

4. [RTTY] DXP38 vs MMTTY tuning faceoff (score: 1)
Author: faunt@panix.com (Doug Faunt N6TQS +1-510-655-8604)
Date: Tue, 25 Sep 2001 13:03:02 -0400 (EDT)
I think we've discussed this before. The DXP38 tuning indicator sucks. I use a HAL RTTY=1 with mine, which works much better,although I find the cross display an affectation. 73, doug X-Sender: 32350
/archives//html/RTTY/2001-09/msg00288.html (11,410 bytes)

5. [RTTY] DXP38 vs MMTTY tuning faceoff (score: 1)
Author: kchen@apple.com (Kok Chen)
Date: Tue, 25 Sep 2001 11:57:48 -0700
I have had moderate luck with a software tuning indicator which resembles the KAM display. In fact, it is my preferred software indicator (much faster than using a spectrum display like MMTTY). I use
/archives//html/RTTY/2001-09/msg00291.html (10,341 bytes)

6. [RTTY] DXP38 vs MMTTY tuning faceoff (score: 1)
Author: jcoleman@ebbtide.micro.uiuc.edu (Jim Coleman)
Date: Tue, 25 Sep 2001 14:25:56 -0500
I use Writelog with DXP38 and use a spectrum analyzer program called GSpec http://www.mrx.com.au/gspec_readme.htm I make this into a small window under the RTTY window. It allows quick tuning because
/archives//html/RTTY/2001-09/msg00292.html (9,779 bytes)

7. [RTTY] DXP38 vs MMTTY tuning faceoff (score: 1)
Author: w2ki@amsat.org (John Hirth)
Date: Tue, 25 Sep 2001 15:56:45 -0400
With regard to tuning displays in general and MMTTY as an example, I'm sure that by now everyone knows that MMTTY also has an X-Y tuning indicator window that you can open with or instead of the FFT
/archives//html/RTTY/2001-09/msg00293.html (8,323 bytes)

8. [RTTY] DXP38 vs MMTTY tuning faceoff (score: 1)
Author: w7why@harborside.com (Tom Osborne)
Date: Sun, 23 Sep 2001 15:37:35 -0700
Hi John I see you didn't have the MMTTY display set to "ham" It looks like the afc is turned off, but still not set up for 2125-2295. The mark frequency is 2093. Is that the frequency difference betw
/archives//html/RTTY/2001-09/msg00298.html (7,998 bytes)

9. [RTTY] DXP38 vs MMTTY tuning faceoff (score: 1)
Author: mobile.workshop@guernseytelecoms.com (Mobile Workshop)
Date: Wed, 26 Sep 2001 08:30:24 +0100
Hi all, Well, this may sound daft, (and I am sure it is!!) BUT, I use 1275/1445 mark/shift, (USB of course), and find that I can tune by ear almost all of the time. When I first started using MMTTY,
/archives//html/RTTY/2001-09/msg00302.html (10,489 bytes)

10. [RTTY] DXP38 vs MMTTY tuning faceoff (score: 1)
Author: w7ti@dslextreme.com (Bill Turner)
Date: Wed, 26 Sep 2001 09:27:05 -0700
<snip> _________________________________________________________ Daft? Not at all. When you maintain the same shift and lower the tones, the percentage separation between them becomes larger and more
/archives//html/RTTY/2001-09/msg00305.html (9,107 bytes)

11. [RTTY] DXP38 vs MMTTY tuning faceoff (score: 1)
Author: kchen@apple.com (Kok Chen)
Date: Wed, 26 Sep 2001 09:56:30 -0700
How about transmitting at 2 kHz and aurally tuning at 1 kHz (or even lower?) One can even convert a 2 kHz centered FSK signal to a 1 kHz centered one with a PeeCee without modifying the rig. Insertin
/archives//html/RTTY/2001-09/msg00306.html (9,324 bytes)

12. [RTTY] DXP38 vs MMTTY tuning faceoff (score: 1)
Author: w2up@mindspring.com (Barry )
Date: Wed, 26 Sep 2001 13:10:03 -0400
I tune by ear 95% of the time, using the high tones (guess I'm a few years younger than you low tone guys, and can still hear up there, hi). As a matter of fact, I find tuning by ear most helpful on
/archives//html/RTTY/2001-09/msg00307.html (10,305 bytes)

13. [RTTY] DXP38 vs MMTTY tuning faceoff (score: 1)
Author: w7ti@dslextreme.com (Bill Turner)
Date: Wed, 26 Sep 2001 10:53:02 -0700
_________________________________________________________ For me, a scope is the best. My trusty old KAM was retired years ago to do nothing more than drive my little 3" Tektronix scope sitting on to
/archives//html/RTTY/2001-09/msg00308.html (8,892 bytes)

14. [RTTY] DXP38 vs MMTTY tuning faceoff (score: 1)
Author: FireBrick" <w9ol@billnjudy.com (FireBrick)
Date: Wed, 26 Sep 2001 12:54:32 -0500
Would that "prolonged exposure to loud high audio frequencies" refer to an xyl's voice?
/archives//html/RTTY/2001-09/msg00309.html (8,491 bytes)

15. [RTTY] DXP38 vs MMTTY tuning faceoff (score: 1)
Author: jflanders2@home.com (Jerry Flanders)
Date: Wed, 26 Sep 2001 14:12:45 -0400
I used a scope with my ST-6 (as a front end for PK-232) until recently. I have since started using the "xy scope" on the MMTTY display and find it almost the same. Only _slightly_ slower. I probably
/archives//html/RTTY/2001-09/msg00310.html (9,379 bytes)

16. Fw: [RTTY] DXP38 vs MMTTY tuning faceoff (score: 1)
Author: artinian@siol.net (Marijan Miletic, S56A)
Date: Wed, 26 Sep 2001 22:30:10 -0000
This is a multi-part message in MIME format. --=_NextPart_000_0087_01C146DA.CD19CEC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit I overlooked missing reflector addr
/archives//html/RTTY/2001-09/msg00314.html (19,777 bytes)


This search system is powered by Namazu