Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+RTTY\s+Now\s+trashy\s+signals\s*$/: 15 ]

Total 15 documents matching your query.

1. Re: [RTTY] RTTY Now trashy signals (score: 1)
Author: Mark <n2qt@verizon.net>
Date: Tue, 08 Jan 2013 16:17:50 -0500
Absolutely. There are the over driven afsk signals that show up as double shift width, the ones that show up with reverse shift (maybe inadequate unwanted sideband suppression), the fuzzy tones (alth
/archives//html/RTTY/2013-01/msg00122.html (12,339 bytes)

2. Re: [RTTY] RTTY Now trashy signals (score: 1)
Author: Kok Chen <chen@mac.com>
Date: Tue, 08 Jan 2013 13:36:23 -0800
Check out what a bit-banged FSK ("EXTFSK") from a slow Windows machine sounds like. You might be surprised :-). Yeah, those are keying sidebands from the unwaveshaped RTTY signals. Same mathematics a
/archives//html/RTTY/2013-01/msg00123.html (8,874 bytes)

3. Re: [RTTY] RTTY Now trashy signals (score: 1)
Author: "Joe Subich, W4TV" <lists@subich.com>
Date: Tue, 08 Jan 2013 16:47:50 -0500
And far too many AFSK users run their sound cards "sliders up full" into mic inputs that clip even before the mic gain control. With clipping in the mic input any wave shaping in the AFSK modem is l
/archives//html/RTTY/2013-01/msg00124.html (8,675 bytes)

4. Re: [RTTY] RTTY Now trashy signals (score: 1)
Author: Al Kozakiewicz <akozak@hourglass.com>
Date: Tue, 8 Jan 2013 19:54:21 -0500
________________________________________ From: RTTY [rtty-bounces@contesting.com] On Behalf Of Joe Subich, W4TV [lists@subich.com] Sent: Tuesday, January 08, 2013 4:47 PM To: rtty@contesting.com Subj
/archives//html/RTTY/2013-01/msg00128.html (9,572 bytes)

5. Re: [RTTY] RTTY Now trashy signals (score: 1)
Author: "aflowers@frontiernet.net" <aflowers@frontiernet.net>
Date: Tue, 8 Jan 2013 18:40:43 -0800 (PST)
  For those who haven't seen what Dave is talking about,  I've isolated the spectra of several RTTY signals from this past weekend that are numbered for comparison here:   http://www.frontiernet.net/
/archives//html/RTTY/2013-01/msg00134.html (8,047 bytes)

6. Re: [RTTY] RTTY Now trashy signals (score: 1)
Author: "Kenny Young" <ab4gg@comcast.net>
Date: Wed, 9 Jan 2013 06:54:37 -0500
I would want to see what my signal looked like to make sure that it is clean. I also agree with pointing out the calls with good signals so that we could get a little help if needed. Kenny, ab4gg   F
/archives//html/RTTY/2013-01/msg00144.html (8,691 bytes)

7. Re: [RTTY] RTTY Now trashy signals (score: 1)
Author: "aflowers@frontiernet.net" <aflowers@frontiernet.net>
Date: Wed, 9 Jan 2013 07:28:23 -0800 (PST)
Al,   I respectfully disagree in small detail (and please forgive me if I misunderstood).  I think everyone owns equal responsibility for his or her signal *regardless of the process creating it*.  W
/archives//html/RTTY/2013-01/msg00155.html (10,001 bytes)

8. Re: [RTTY] RTTY Now trashy signals (score: 1)
Author: Al Kozakiewicz <akozak@hourglass.com>
Date: Wed, 9 Jan 2013 11:08:33 -0500
Don't underestimate the importance of the words "in the sense that"! While we are all ultimately responsible for operating to a set of acceptable standards, the FSK operator has no choice to make in
/archives//html/RTTY/2013-01/msg00156.html (11,453 bytes)

9. Re: [RTTY] RTTY Now trashy signals (score: 1)
Author: "aflowers@frontiernet.net" <aflowers@frontiernet.net>
Date: Wed, 9 Jan 2013 09:03:08 -0800 (PST)
Fair enough, Al!  I've had my coffee now...   Here's a very simple way that might get at the crux of the issue.  Let's say that signal number #3 was your signal (yes, this was recorded off the air t
/archives//html/RTTY/2013-01/msg00157.html (13,927 bytes)

10. Re: [RTTY] RTTY Now trashy signals (score: 1)
Author: Mark <n2qt@verizon.net>
Date: Wed, 09 Jan 2013 12:29:00 -0500
Several years ago the cw guys went through this same thing with key clicks. As you may recall the popular ft1000 was a particular offender. So what happened A hardware fix was identified and most ope
/archives//html/RTTY/2013-01/msg00159.html (10,438 bytes)

11. Re: [RTTY] RTTY Now trashy signals (score: 1)
Author: "Jeff Blaine" <keepwalking188@yahoo.com>
Date: Wed, 9 Jan 2013 11:56:41 -0600
Al, You have a great point. And I think it's worse because you are assuming that once some "standard" is established, then guys will be able to measure it the same way, and as we can see in the PSK c
/archives//html/RTTY/2013-01/msg00160.html (16,521 bytes)

12. Re: [RTTY] RTTY Now trashy signals (score: 1)
Author: Al Kozakiewicz <akozak@hourglass.com>
Date: Wed, 9 Jan 2013 15:33:23 -0500
What got me thinking was an incident that happened during a RTTY contest last year. Someone called (several times!) on my 20m run frequency to tell me that I was splattering real bad. I run FSK with
/archives//html/RTTY/2013-01/msg00164.html (16,959 bytes)

13. Re: [RTTY] RTTY Now trashy signals (score: 1)
Author: Bill Turner <dezrat1242@yahoo.com>
Date: Wed, 09 Jan 2013 12:50:58 -0800
REPLY: Wow... fascinating graphs, Andy. Great job!! I wonder if somehow it might be possible to arrange on-the-air tests where a person could transmit a few seconds of data and have a graph like thos
/archives//html/RTTY/2013-01/msg00165.html (8,577 bytes)

14. Re: [RTTY] RTTY Now trashy signals (score: 1)
Author: "Ron Kolarik" <rkolarik@neb.rr.com>
Date: Wed, 9 Jan 2013 15:18:38 -0600
To take it one step further, how about a network of SDR receivers with the GUI available on the internet. Hint: they are out there already. The only thing I can see that may be a problem is standards
/archives//html/RTTY/2013-01/msg00166.html (10,170 bytes)

15. Re: [RTTY] RTTY Now trashy signals (score: 1)
Author: Robert Chudek - K0RC <k0rc@citlink.net>
Date: Wed, 09 Jan 2013 15:37:09 -0600
Hello Ron... I would be happy to get on and provide a test signal. QRZ says you are in Lincoln NE. I am about 50 miles NE of Minneapolis, MN. The path calculator says we are about 375 miles apart as
/archives//html/RTTY/2013-01/msg00167.html (11,172 bytes)


This search system is powered by Namazu