RTTY
[Top] [All Lists]

Re: [RTTY] VK0EK RTTY Update

To: "'Larry Gauthier \(K8UT\)'" <k8ut@charter.net>, "'Martin Berube'" <ve2nmb@gmail.com>, <rtty@contesting.com>
Subject: Re: [RTTY] VK0EK RTTY Update
From: "John Barber" <john@bordertech.co.uk>
Date: Mon, 11 Apr 2016 00:57:31 +0100
List-post: <rtty@contesting.com">mailto:rtty@contesting.com>
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 have something that shows 
your full QSO, the previous activity, timestamps, the lot. Saving them with 
callsign and frequency helps e.g. FT4JA 14090.JPG as the file name.
John GW4SKA

-----Original Message-----
From: RTTY [mailto:rtty-bounces@contesting.com] On Behalf Of Larry Gauthier 
(K8UT)
Sent: 10 April 2016 22:13
To: Martin Berube <ve2nmb@gmail.com>; rtty@contesting.com
Subject: Re: [RTTY] VK0EK RTTY Update

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 callsigns 
immediately before and after my contact. I have been able to successfully 
negotiate with QSL managers when I present the exact frequencies and times of a 
QSO where their logged callsign differed from mine by a character. 
Sometimes they've even made me wait a few months to see if anyone with the 
busted call "claimed" the QSL - but it is worth it for those rare ones.

-larry (K8UT)
-----Original Message-----
From: Martin Berube
Sent: Sunday, April 10, 2016 2:54 PM
To: rtty@contesting.com
Subject: Re: [RTTY] VK0EK RTTY Update

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, Martin VE2NMB

2016-04-10 13:28 GMT-04:00 Jim Lawrence <jim.w7ct@gmail.com>:

> 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 blantant DQRM, 
> but, that's another story.
>
> I was lucky enough to get both FT4JA and VK0EK on RTTY:-)  Just didn't 
> realize how lucky I was:-) until I started reading this thread.
>
> 73
>
> Jim W7CT
>
>
> On 4/10/2016 11:06 AM, WW3S wrote:
>
>> On 4/10/2016 11:45:10 AM, Don Hill AA5AU (aa5au@bellsouth.net) wrote:
>>> RTTY is now mainstream. There are more RTTY operators now than ever 
>>> before as there has been an explosion in RTTY operators in the past 
>>> 10-15 years.
>>>
>>> Don AA5AU
>>>
>>> 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 giving his call, 
>> they respond to a SP6, and the same K5, over and over and 
>> over.....and he’s not the only one....I can understand if one has 
>> lite copy, and they come back to a similar call, but there nothing 
>> similar about OZ8A and a K5.....eventually, the guy works him, so he 
>> thinks the method he is using is correct, but it isnt.....I know Ed 
>> has written some articles on the subject, but how do we get them into 
>> the right publications, websites so the offenders read them ?
>>   _______________________________________________
>> RTTY mailing list
>> RTTY@contesting.com
>> http://lists.contesting.com/mailman/listinfo/rtty
>>
>
> _______________________________________________
> RTTY mailing list
> RTTY@contesting.com
> http://lists.contesting.com/mailman/listinfo/rtty
>
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty 

_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty

_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty
<Prev in Thread] Current Thread [Next in Thread>