Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+VK0EK\s+RTTY\s+Update\s*$/>

Results:

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

Total 15 documents matching your query.

1. [RTTY] VK0EK RTTY Update (score: 1): Author: "Don Hill AA5AU" <aa5au@bellsouth.net>; Date: Sun, 10 Apr 2016 10:45:10 -0500; I just received email from Arliss, W7XU, that the 30 meter antenna has been taken down and there will be no more 30M RTTY in anticipation of their departure "sometime tomorrow" due to approaching bad; /archives//html/RTTY/2016-04/msg00092.html (7,299 bytes)
2. Re: [RTTY] VK0EK RTTY Update (score: 1): Author: "WW3S" <ww3s@zoominternet.net>; Date: Sun, 10 Apr 2016 12:46:17 -0400; they worked a lot last evening, but then condx were better....I saw the first spot from a N1 aboout 0140 or so, and saw the corresponding call on DXA....never a whisper, and few, if any logged, on DX; /archives//html/RTTY/2016-04/msg00093.html (8,784 bytes)
3. Re: [RTTY] VK0EK RTTY Update (score: 1): Author: "WW3S" <ww3s@zoominternet.net>; Date: Sun, 10 Apr 2016 13:06:05 -0400; That being said, how do we educate these newer ops on pileup etiquette? (if it is all newer ops?).....listening to the 4W pileup, trying to find the qsx, and they give a DL6 a 599 and K5 keeps givin; /archives//html/RTTY/2016-04/msg00094.html (7,895 bytes)
4. Re: [RTTY] VK0EK RTTY Update (score: 1): Author: Jim Lawrence <jim.w7ct@gmail.com>; Date: Sun, 10 Apr 2016 11:28:23 -0600; Not only RTTY. CW and SSB pileups are the same. Some guys just never stop calling. I won't say I have never done it, but, if you heard me do it, it was a mistake on my part. Then there is the blantan; /archives//html/RTTY/2016-04/msg00095.html (8,493 bytes)
5. Re: [RTTY] VK0EK RTTY Update (score: 1): Author: Bill Turner <dezrat@outlook.com>; Date: Sun, 10 Apr 2016 11:52:13 -0700; -- ORIGINAL MESSAGE --(may be snipped) REPLY: Keep in mind, this is how jammers work these days, and not just RTTY. They pretend to be a legitimate station that is just "confused" shall we say, ignor; /archives//html/RTTY/2016-04/msg00100.html (8,528 bytes)
6. Re: [RTTY] VK0EK RTTY Update (score: 1): Author: Martin Berube <ve2nmb@gmail.com>; Date: Sun, 10 Apr 2016 14:54:04 -0400; I was able to work VK0EK last night. The info Dom shared was very helpful. tnx again! Unfortunately, i beleive they got my callsign wrong. Didn't copy FT4JA at all last on 30m. Maybe next time. 73, M; /archives//html/RTTY/2016-04/msg00101.html (10,261 bytes)
7. [RTTY] VK0EK RTTY Update (score: 1): Author: "G3YYD" <g3yyd@btinternet.com>; Date: Sun, 10 Apr 2016 15:14:43 -0500; TX7EU at the start of their RTTY did exactly that. They called you on your frequency. This meant there was no static frequency that could be DQRM. It made the pile up spread out by having to listen t; /archives//html/RTTY/2016-04/msg00105.html (8,452 bytes)
8. Re: [RTTY] VK0EK RTTY Update (score: 1): Author: "Ed Muns" <ed@w0yk.com>; Date: Sun, 10 Apr 2016 12:43:20 -0700; The majority of people who might benefit from these threads and other sources of suggested operating technique are not in the audience. We're mostly preaching to the choir. The best way to reach ever; /archives//html/RTTY/2016-04/msg00107.html (9,733 bytes)
9. Re: [RTTY] VK0EK RTTY Update (score: 1): Author: "V Sidarau" <vs_otw@rogers.com>; Date: Sun, 10 Apr 2016 15:54:24 -0400; It can only work if the DX signal is strong enough. However in most cases the DX is weak, while callers are way stronger and numerous. Hence the whole idea of split. Copying a weak DX signal on "your; /archives//html/RTTY/2016-04/msg00108.html (9,615 bytes)
10. Re: [RTTY] VK0EK RTTY Update (score: 1): Author: "Larry Gauthier $K8UT$" <K8UT@charter.net>; Date: Sun, 10 Apr 2016 17:12:57 -0400; Martin, Unfortunately, i beleive they got my callsign wrong. We've probably all had this happen at least once. When I suspect that they logged my call incorrectly, I make a note in my log of the call; /archives//html/RTTY/2016-04/msg00112.html (12,657 bytes)
11. Re: [RTTY] VK0EK RTTY Update (score: 1): Author: "John Barber" <john@bordertech.co.uk>; Date: Mon, 11 Apr 2016 00:57:31 +0100; Another useful method is to hit the 'print screen' button immediately after the contact, then save the picture. I do this with any contact that needs confirming even if it looks perfect. This way you; /archives//html/RTTY/2016-04/msg00115.html (13,502 bytes)
12. Re: [RTTY] VK0EK RTTY Update (score: 1): Author: Bill Turner <dezrat@outlook.com>; Date: Sun, 10 Apr 2016 17:11:10 -0700; -- ORIGINAL MESSAGE --(may be snipped) REPLY: While that is a good suggestion, I think there might be an even better way - QST magazine. Write a good, reasonable, informative article and QST will pri; /archives//html/RTTY/2016-04/msg00117.html (8,606 bytes)
13. Re: [RTTY] VK0EK RTTY Update (score: 1): Author: Dave Cole <dave@nk7z.net>; Date: Sun, 10 Apr 2016 17:14:54 -0700; John, That is one hell of a good idea! THANK YOU! -- 73's, and thanks, Dave (NK7Z) For software/hardware reviews see: http://www.nk7z.net For MixW support see: https://groups.yahoo.com/neo/groups/mi; /archives//html/RTTY/2016-04/msg00118.html (15,761 bytes)
14. Re: [RTTY] VK0EK RTTY Update (score: 1): Author: Bill <bmarx@bellsouth.net>; Date: Sun, 10 Apr 2016 20:50:57 -0400; For many years I simply copied the callsign of the person working the DX after me and if it was still on the screen the one before me, not to prove it but to help find my call in the log. That was du; /archives//html/RTTY/2016-04/msg00120.html (9,423 bytes)
15. Re: [RTTY] VK0EK RTTY Update (score: 1): Author: Martin Berube <ve2nmb@gmail.com>; Date: Mon, 11 Apr 2016 13:35:03 -0400; Hello everybody! I got my callsign corrected today in the log. That was quick. There is a "Contacs Us" link in their web page: https://vk0ek.freshdesk.com/support/tickets/new This is how I contacted; /archives//html/RTTY/2016-04/msg00134.html (10,435 bytes)

Current List: 1 - 15
Page: [1]