Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+Simple\s+thing\s+that\s+seemed\s+to\s+improve\s+my\s+S\&Ping\s*$/: 25 ]

Total 25 documents matching your query.

1. [RTTY] Simple thing that seemed to improve my S&Ping (score: 1)
Author: Michael Rapp <mdrapp@gmail.com>
Date: Sun, 7 Feb 2016 18:31:23 -0600
I had one of those beginner "light bulb" moments for me during the XE contest. This was the first contest in which I've operated that accuracy was very important; if you logged a QSO incorrectly, you
/archives//html/RTTY/2016-02/msg00056.html (8,383 bytes)

2. Re: [RTTY] Simple thing that seemed to improve my S&Ping (score: 1)
Author: Jerry Flanders <jeflanders@comcast.net>
Date: Sun, 07 Feb 2016 20:28:48 -0500
At 07:31 PM 2/7/2016, Michael Rapp wrote: ... While S&Ping, something that dramatically improved my accuracy was to never give my exchange unless I had a high degree of confidence that the running st
/archives//html/RTTY/2016-02/msg00057.html (8,474 bytes)

3. Re: [RTTY] Simple thing that seemed to improve my S&Ping (score: 1)
Author: "Jeff AC0C" <keepwalking188@ac0c.com>
Date: Sun, 7 Feb 2016 19:52:13 -0600
Correct me if I'm wrong, but it's the responsibility of the other guy to get your call right. You are not penalized if he gets your call wrong in a log check. You are only penalized if you get his ca
/archives//html/RTTY/2016-02/msg00058.html (8,817 bytes)

4. Re: [RTTY] Simple thing that seemed to improve my S&Ping (score: 1)
Author: Ron W7FIA <fia@clouddancer.com>
Date: Sun, 7 Feb 2016 19:32:41 -0800 (PST)
To me, that is the 'true' purpose of contesting. r _______________________________________________ RTTY mailing list RTTY@contesting.com http://lists.contesting.com/mailman/listinfo/rtty
/archives//html/RTTY/2016-02/msg00059.html (8,091 bytes)

5. Re: [RTTY] Simple thing that seemed to improve my S&Ping (score: 1)
Author: Bill Turner <dezrat@outlook.com>
Date: Sun, 7 Feb 2016 19:43:53 -0800
-- ORIGINAL MESSAGE --(may be snipped) REPLY: What you say above is fine if you and the run station are the only ones on the frequency, but it sometimes happens that two stations come back to the run
/archives//html/RTTY/2016-02/msg00060.html (7,943 bytes)

6. Re: [RTTY] Simple thing that seemed to improve my S&Ping (score: 1)
Author: Ron W7FIA <fia@clouddancer.com>
Date: Sun, 7 Feb 2016 19:56:45 -0800 (PST)
We don't need to be old to utilize Google I love a good April Fools joke r _______________________________________________ RTTY mailing list RTTY@contesting.com http://lists.contesting.com/mailman/l
/archives//html/RTTY/2016-02/msg00061.html (8,281 bytes)

7. Re: [RTTY] Simple thing that seemed to improve my S&Ping (score: 1)
Author: Jerry Flanders <jeflanders@comcast.net>
Date: Sun, 07 Feb 2016 23:19:31 -0500
You are not penalized if he gets your call wrong in a log check. You are only penalized if you get his call wrong. 73/jeff/ac0c www.ac0c.com alpha-charlie-zero-charlie But if you need DX/whatever cre
/archives//html/RTTY/2016-02/msg00062.html (10,709 bytes)

8. Re: [RTTY] Simple thing that seemed to improve my S&Ping (score: 1)
Author: "Jim W7RY" <w7ry@centurytel.net>
Date: Sun, 7 Feb 2016 20:37:15 -0800
Agreed! Dont hold my time hostage because you THINK I have your call wrong. Just because I have sent it to you wrong, doesn't mean I haven't corrected the log after I have logged the contact. Band co
/archives//html/RTTY/2016-02/msg00063.html (9,958 bytes)

9. Re: [RTTY] Simple thing that seemed to improve my S&Ping (score: 1)
Author: "john@kk9a.com" <john@kk9a.com>
Date: Mon, 8 Feb 2016 08:55:54 -0500
In most contests you do not loose points if the other station incorrectly copies your callsign. Personally I do not like when someone holds the report hostage. On most modes sending your call twice b
/archives//html/RTTY/2016-02/msg00064.html (9,866 bytes)

10. Re: [RTTY] Simple thing that seemed to improve my S&Ping (score: 1)
Author: Michael Rapp <mdrapp@gmail.com>
Date: Mon, 8 Feb 2016 09:11:45 -0600
Thanks for the advice all....this clarifies things for me. I think I phrased my not giving my report unless I had a high degree of confidence the running station had my report a little poorly. I didn
/archives//html/RTTY/2016-02/msg00065.html (10,164 bytes)

11. Re: [RTTY] Simple thing that seemed to improve my S&Ping (score: 1)
Author: Ron W7FIA <fia@clouddancer.com>
Date: Mon, 8 Feb 2016 12:23:29 -0800 (PST)
as someone said eariler, it's an imperfect dance seems like you nailed that one repeating your initial double call is probably the move no report yet, but this is just once and then play or move on
/archives//html/RTTY/2016-02/msg00066.html (10,166 bytes)

12. Re: [RTTY] Simple thing that seemed to improve my S&Ping (score: 1)
Author: "Jeff AC0C" <keepwalking188@ac0c.com>
Date: Mon, 8 Feb 2016 14:31:29 -0600
Beyond the gentlemen's point of a possible DXCC entry, there is no benefit to making sure the OTHER guy has your call right. It's rare for me to find a new RTTY country in the middle of a contest but
/archives//html/RTTY/2016-02/msg00067.html (11,589 bytes)

13. Re: [RTTY] Simple thing that seemed to improve my S&Ping (score: 1)
Author: "John Barber" <john@bordertech.co.uk>
Date: Mon, 08 Feb 2016 16:18:14 -0500
If I see the other guy send my call wrong once I don't worry. If he sends it wrong twice, he probably needs to correct it. Not my problem ... but out of courtesy to another contester, who has taken t
/archives//html/RTTY/2016-02/msg00068.html (12,054 bytes)

14. Re: [RTTY] Simple thing that seemed to improve my S&Ping (score: 1)
Author: Robert Chudek - K0RC <k0rc@citlink.net>
Date: Mon, 8 Feb 2016 20:16:59 -0600
*/"I'd really like to watch some of the Single Op wizards"/* I don't know that I qualify as a "wizard", but I do have 50+ years of RTTY under my belt. One of the things I haven't seen mentioned is li
/archives//html/RTTY/2016-02/msg00070.html (11,639 bytes)

15. Re: [RTTY] Simple thing that seemed to improve my S&Ping (score: 1)
Author: Jim Preston <jpreston1@cox.net>
Date: Mon, 15 Feb 2016 08:22:56 -0800
It depends on the contest. There are a few contests ( I can't remember which ones) that do penalize you if the the other station gets your call wrong. This is usually mentioned in the rules. Also, if
/archives//html/RTTY/2016-02/msg00097.html (10,172 bytes)

16. Re: [RTTY] Simple thing that seemed to improve my S&Ping (score: 1)
Author: Jim Preston <jpreston1@cox.net>
Date: Mon, 15 Feb 2016 08:25:32 -0800
Jim, But if you haven't corrected it in your log, and you do have my call wrong, then you lose credit for that contact. By sending the correction, I am trying to help you, not me. 73, Jim N6VH Band c
/archives//html/RTTY/2016-02/msg00098.html (9,967 bytes)

17. Re: [RTTY] Simple thing that seemed to improve my S&Ping (score: 1)
Author: "Jim W7RY" <w7ry@centurytel.net>
Date: Mon, 15 Feb 2016 09:35:40 -0800
Jim... Just because the logging software sent it wrong, doesn't mean that I haven't corrected it in my log. And I haven't wasted time sending corrections back and forth. 73 Jim W7RY Jim, But if you h
/archives//html/RTTY/2016-02/msg00100.html (11,128 bytes)

18. Re: [RTTY] Simple thing that seemed to improve my S&Ping (score: 1)
Author: "Ed Muns" <ed@w0yk.com>
Date: Mon, 15 Feb 2016 14:38:21 -0400
Actually, you should always send a callsign correction. Some of the CQ contests are requiring this now in the rules, in reaction to some entrants who clean their log post-contest by using outside dat
/archives//html/RTTY/2016-02/msg00101.html (12,391 bytes)

19. Re: [RTTY] Simple thing that seemed to improve my S&Ping (score: 1)
Author: Robert Chudek - K0RC <k0rc@citlink.net>
Date: Mon, 15 Feb 2016 15:28:50 -0600
A quick question, Jim. . . If you worked P5AA and he sent your call wrong, what would you do? 73 de Bob - KØRC in MN And I haven't wasted time sending corrections back and forth. 73 Jim W7RY Jim, But
/archives//html/RTTY/2016-02/msg00105.html (12,159 bytes)

20. Re: [RTTY] Simple thing that seemed to improve my S&Ping (score: 1)
Author: <john@kk9a.com>
Date: Mon, 15 Feb 2016 19:58:08 -0500
Yes it's a good practice and even required in some CQ contests. For corrections I used a separate macro "{his callsign} QSL KK9A CQ" instead of "TU KK9A CQ". It works pretty smoothly unless the other
/archives//html/RTTY/2016-02/msg00109.html (9,865 bytes)


This search system is powered by Namazu