RTTY
[Top] [All Lists]

Re: [RTTY] Dupes how to handle

To: "Alejandro V. XE1EE" <xe1ee@telmexmail.com>, RTTY-reflektorn <rtty@contesting.com>
Subject: Re: [RTTY] Dupes how to handle
From: trevor dunne <trevor_dunne@yahoo.com>
Reply-to: trevor dunne <trevor_dunne@yahoo.com>
Date: Mon, 13 Feb 2012 23:43:22 +0000 (GMT)
List-post: <rtty@contesting.com">mailto:rtty@contesting.com>
I will have a look at Writelog, I use Ham radio deluxe for my day to day 
logging but that soon is to be a commerical sw at a cost so I want to try the 
other options available to me.
 
I used to use logger 32 but found HRD better, I reinstalled Logger32 on Friday 
to see what the newer version was like and it killed N1MM on me I had to go to 
a restore point on my PC to get N1MM to work again so Logger32 is now in the 
bin. there was some panic in the shack a few hours before the contest I can 
tell you.
 
I also decided to move the Rig after an hour of the contest at 1am on Saturday 
morning, I lost over an hour making new patch cables and amp keying cables but 
it was alot more comfortable to use the rig. nothing like last minute prep.

Thanks
Trevor
EI2GLB


________________________________
From: Alejandro V. XE1EE <xe1ee@telmexmail.com>
To: trevor dunne <trevor_dunne@yahoo.com>; RTTY-reflektorn 
<rtty@contesting.com> 
Sent: Monday, 13 February 2012, 23:29
Subject: Re: [RTTY] Dupes how to handle

Yes i saw your pileup and it was huge, there was another EI station calling 
also and don't know why he had less clients.

FSK is better than AFSK, still you can use autotune function of you're running 
mmtty + N1MM logger. I have a ProIII and it works just like yours, with a very 
narrow filter and a good performance on a crowded frequency.

If you have the chance, try Writelog, i'ts a great software,  I knew it thanks 
to XE2K, once I started using it, I quit using MixW and N1MM, as well as AFSK 
is no longer in my shack hi. It works great as a everyday program to work/log 
Dxpeds and so on.

Looking forward to work you soon, 73!

*********************
XE1EE
Alejandro Valdez O.
DXCC RTTY, SSB & CW
Mixed, 10, 15, 20 & 40
WAS, TPA & WAC
www.dxxe.org
www.qsl.net/xe1ee
Twiter: @xe1ee
***********************

+++++ No mas SPAM ++++++
No me envíes cadenitas, oraciones y demás correos sin mi autorización.
Do not send me prays, chain letters and others without my permission.
** No trees were killed in the sending of this message but a large number of 
electrons were terribly inconvenienced**


--------------------------------------------------
From: "trevor dunne" <trevor_dunne@yahoo.com>
Sent: Monday, February 13, 2012 5:08 PM
To: "Alejandro V. XE1EE" <xe1ee@telmexmail.com>; "RTTY-reflektorn" 
<rtty@contesting.com>
Subject: Re: [RTTY] Dupes how to handle

> Sorry I missed you Alejandro, I had some very big pile ups on 15m, It made me 
> feel like a DX station at times. I struggle to get a decode when there is 
> lots of stations calling, I guess everyone does,
> 
> Two items that bugged me during the contest when I was runnig were
> 
> 1. Stations calling very much off my freq, I use a Icom 756 pro2 in FSK/RTTY 
> mode, with the filter at 250hz and some stations were over 100hz off from me. 
> It was a constant job adjusting the RIT to tune in some stations.
> 
> 2. When 2 or 3 stations call, I would stack there calls in N1MM so that once 
> I finished with the 1st I would go WXXX TU NOW KXXX ur 599 XXXX XXXX and so 
> on, but the amount of times the 2nd station didn't respond, I guess EI2 was 
> not rare enough to hang around 20 seconds for,
> 
> I had no problems with QRM as the Filters are very sharp on the Pro. Have to 
> say that N1MM is a great tool this was my 2nd big contest with it and I have 
> still a lot to learn but I can't see myself ever trying to do ASFK again.
> 
> Thanks
> Trevor
> EI2GLB
> 
> 
> ________________________________
> From: Alejandro V. XE1EE <xe1ee@telmexmail.com>
> To: trevor dunne <trevor_dunne@yahoo.com>; RTTY-reflektorn 
> <rtty@contesting.com>
> Sent: Monday, 13 February 2012, 22:33
> Subject: Re: [RTTY] Dupes how to handle
> 
> Hello Trevor
> 
> Well, I have a macro who checks the call against the current contest log, if 
> it is a dupe sends Call QSO B4 XE1EE QRZ, if not just sends the serial number 
> and I keep going, I never work dupes.
> 
> By the way..  you where here 5/9 (on 15 meters) and never heard me :( and I 
> was running 300 watts.
> 
> Here's the macro I use (on Writelog)
> 
> %R%C %BQSO B4%RXE1EE QRZ%E%B 599 %N3 %N3%E
> 
> 73!
> 
> *********************
> XE1EE
> Alejandro Valdez O.
> DXCC RTTY, SSB & CW
> Mixed, 10, 15, 20 & 40
> WAS, TPA & WAC
> www.dxxe.org
> www.qsl.net/xe1ee
> Twiter: @xe1ee
> ***********************
> 
> +++++ No mas SPAM ++++++
> No me envíes cadenitas, oraciones y demás correos sin mi autorización.
> Do not send me prays, chain letters and others without my permission.
> ** No trees were killed in the sending of this message but a large number of 
> electrons were terribly inconvenienced**
> 
> 
> --------------------------------------------------
> From: "trevor dunne" <trevor_dunne@yahoo.com>
> Sent: Sunday, February 12, 2012 10:02 AM
> To: "RTTY-reflektorn" <rtty@contesting.com>
> Subject: [RTTY] Dupes how to handle
> 
>> Whats the correct procedure to handle dupe in any contest but mainly WPX RTTY
>> 
>> I have a few QSO's that I thought were good but the other station called me 
>> again and when I said QSO B4, I wasn't in there log,
>> 
>> Do I just delete the first bad QSO and log the 2nd one ???
>> 
>> How does that affect my serial number count as there will be missing QSO's 
>> in the log ???
>> 
>> 
>> Thanks
>> Trevor
>> EI2GLB
>> 
>> 
>> ________________________________
>> _______________________________________________
>> 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>