- 41. Re: [RTTY] RTTY - Slow computer problems (score: 1)
- Author: Richard Ferch <ve3iay@storm.ca>
- Date: Sun, 23 Sep 2012 21:08:17 -0400
- Dick, A few ideas: Do you see any other symptoms at the same time, such as a slowdown in the software's response to frequency changes on the rig, or a slowdown in the rig's response to commands from
- /archives//html/RTTY/2012-09/msg00111.html (11,121 bytes)
- 42. Re: [RTTY] Rude contesters (score: 1)
- Author: Richard Ferch <ve3iay@storm.ca>
- Date: Thu, 04 Oct 2012 07:04:46 -0400
- Gary, In AFSK, you should always have NET on when you are S&Ping, in order to guarantee that your transmit and receive frequencies are the same. If you leave NET off, unless you are attentive to the
- /archives//html/RTTY/2012-10/msg00105.html (11,079 bytes)
- 43. Re: [RTTY] The Problem with AFSK ... (score: 1)
- Author: Richard Ferch <ve3iay@storm.ca>
- Date: Sat, 19 Jan 2013 17:06:56 -0500
- Do K3s key click using FSKD or 590s using FSK? Yes. For the K3, the evidence has been published; the K3 is capable of producing cleaner RTTY (lower levels of key clicks) in AFSK than it is in FSK: 1
- /archives//html/RTTY/2013-01/msg00235.html (11,193 bytes)
- 44. Re: [RTTY] AFSK Tips (score: 1)
- Author: Richard Ferch <ve3iay@storm.ca>
- Date: Mon, 28 Jan 2013 08:12:53 -0500
- My suggestion would be slightly different from Bill's: 1. If you are running, keep AFC on and NET off. If you don't mind using RIT to tune in off-frequency callers, turn AFC off as well. 2. If you ar
- /archives//html/RTTY/2013-01/msg00300.html (8,743 bytes)
- 45. Re: [RTTY] Dash vs space, more beat this to death (score: 1)
- Author: Richard Ferch <ve3iay@storm.ca>
- Date: Mon, 11 Feb 2013 15:25:55 -0500
- I think that this is incorrect. As I remember, USOS is enabled on the receiver's end and adds the extra LTRS on space. I don't believe that the transmitting station sends a LTRS character along with
- /archives//html/RTTY/2013-02/msg00247.html (8,171 bytes)
- 46. Re: [RTTY] Dash vs space, more beat this to death (score: 1)
- Author: Richard Ferch <ve3iay@storm.ca>
- Date: Mon, 11 Feb 2013 20:26:38 -0500
- I think you're right. If I recall correctly, when a space is detected by either the transmitter or receiver, they each reset themselves back to FIGS case, but no actual FIGS character is sent. The s
- /archives//html/RTTY/2013-02/msg00261.html (10,016 bytes)
- 47. Re: [RTTY] 75 Baud ... RigExpert ... (score: 1)
- Author: Richard Ferch <ve3iay@storm.ca>
- Date: Sun, 15 Sep 2013 09:24:57 -0400
- Comments/answers in-line below. Figured I'd start here. Want to play in 75-baud BARTG tomorrow. Have a new Rigexpert TI5 which supports FSK. The problem is that the TI5 uses different fake com ports
- /archives//html/RTTY/2013-09/msg00064.html (11,916 bytes)
- 48. Re: [RTTY] 75 Baud ... RigExpert ... (score: 1)
- Author: Richard Ferch <ve3iay@storm.ca>
- Date: Sun, 15 Sep 2013 10:01:25 -0400
- As a follow-up to my previous post: In answer to This isn't the whole story. First, yes it is possible to set "PTT & FSK" to the FSK port; the "No" was in response to the "then use the Radio Command
- /archives//html/RTTY/2013-09/msg00065.html (8,864 bytes)
- 49. Re: [RTTY] Clipped calls (score: 1)
- Author: Richard Ferch <ve3iay@storm.ca>
- Date: Mon, 11 Nov 2013 11:37:37 -0500
- If you mean that you are not seeing what the other station sends, rather than that the first character of your own messages is not being transmitted, that makes it sound as if your system is not retu
- /archives//html/RTTY/2013-11/msg00052.html (7,992 bytes)
- 50. Re: [RTTY] 2Tone text window not showing (score: 1)
- Author: Richard Ferch <ve3iay@storm.ca>
- Date: Wed, 26 Feb 2014 12:35:13 -0500
- Dick, Since you said "text window", and since you are also using MMTTY, I will assume you are using 2Tone in one of the additional RX windows in N1MM Logger, and it is N1MM Logger's Additional RX win
- /archives//html/RTTY/2014-02/msg00325.html (8,675 bytes)
- 51. Re: [RTTY] RTTY N1MM Logger questions (score: 1)
- Author: Richard Ferch <ve3iay@storm.ca>
- Date: Mon, 12 May 2014 06:54:10 -0400
- Dick, Some of the filtering you want can best be done at the cluster node you are connected to - for example, you may be able to set the cluster to report only skimmer spots, or only non-skimmer spot
- /archives//html/RTTY/2014-05/msg00061.html (8,877 bytes)
- 52. Re: [RTTY] RTTY reversebeacon spotting network wow! (score: 1)
- Author: Richard Ferch <ve3iay@storm.ca>
- Date: Mon, 29 Sep 2014 11:29:43 -0400
- In addition to the S&P stations being spotted, there were also some running stations who did not leave spaces on the end of their CQ messages so that their call signs showed up multiple times with ex
- /archives//html/RTTY/2014-09/msg00126.html (9,310 bytes)
- 53. Re: [RTTY] RTTY reversebeacon spotting network wow! (score: 1)
- Author: Richard Ferch <ve3iay@storm.ca>
- Date: Mon, 29 Sep 2014 14:03:27 -0400
- After consulting the list of strings that the RTTY skimmer recognizes (see <http://wz7i.com/cw-skimmer/rtty-skimmer.html>) and thinking a bit more, I think I know what it is about the CQing style tha
- /archives//html/RTTY/2014-09/msg00133.html (9,335 bytes)
- 54. Re: [RTTY] CR/LF, SP, or something better for RTTY (score: 1)
- Author: Richard Ferch <ve3iay@storm.ca>
- Date: Fri, 03 Oct 2014 15:14:27 -0400
- I'm confused by all of this concern about CRLF and scrolling, I guess because I've never used N1MM. In writelog the window doesn't scroll, it wraps around - meaning when the last line in the window
- /archives//html/RTTY/2014-10/msg00058.html (9,438 bytes)
- 55. Re: [RTTY] N1MM Logger+ RTTY macro question (score: 1)
- Author: Richard Ferch <ve3iay@storm.ca>
- Date: Mon, 4 Jan 2016 17:33:16 -0500
- Dick, Salvo has hit the nail on the head. You need to look at both F5 and F2 messages. When you are using ESM, pressing Enter to send the exchange while you are running sends both F5 and F2. You can
- /archives//html/RTTY/2016-01/msg00035.html (8,518 bytes)
This search system is powered by
Namazu