RTTY
[Top] [All Lists]

Re: [RTTY] FT4JA performance

To: Junior <charlesw_anderso@bellsouth.net>
Subject: Re: [RTTY] FT4JA performance
From: EA2RY <ea2ry@ea2ry.com>
Date: Tue, 12 Apr 2016 00:32:56 +0200
List-post: <rtty@contesting.com">mailto:rtty@contesting.com>
5J0R 80.508 qsos, 10.047 on rtty (12,48%)
;-)


     73's de Roberto
http://www.ea2ry.com
        ¯_(ツ)_/¯

> El 11 abr 2016, a las 23:07, Junior <charlesw_anderso@bellsouth.net> escribió:
> 
> Another good one , over 10 percent , was vu7 and vu4. The op for the most 
> part was NAN VU2NKS on rtty. That's very good for one op working rtty.
> You can find NAN on most days for new bands. I worked NAN on 80m for new band.
> 73
> charles/kk5oq
> 
> -----Original Message-----
> From: RTTY [mailto:rtty-bounces@contesting.com] On Behalf Of Junior
> Sent: Monday, April 11, 2016 10:48 AM
> To: 'John Barber'; 'RTTY Reflector'
> Subject: Re: [RTTY] FT4JA performance
> 
> Specific bands get up to 18 percent per clublog.
> 73
> charles/kk5oq
> 
> -----Original Message-----
> From: RTTY [mailto:rtty-bounces@contesting.com] On Behalf Of John Barber
> Sent: Monday, April 11, 2016 10:23 AM
> To: 'Joe Subich, W4TV'; rtty@contesting.com
> Subject: Re: [RTTY] FT4JA performance
> 
> Right on the nail. 
> 
> The last multi-mode trip I went on ended up with 35K QSOs, 7K on RTTY. That 
> was with just one RTTY op for much of the time and without any priority on 
> the best bands. Peak rates were over 100 per hour for long periods. These big 
> operations with 4 or more stations running should keep 1 station on RTTY all 
> the time, not just work a few hours in the last few days. 
> 
> VK0EK did not use the leaderboard but it was easy to see what was happening 
> in those last days. I checked a list of stations as they were worked, at a 
> time when there were 4 CW stations active and nothing else. Out of 20 
> callsigns, 19 of them already had more than 10 bandslots. There must be a way 
> to let more of the smaller stations get just 1 contact for an ATNO.
> 
> John GW4SKA
> 
> 
> 
> -----Original Message-----
> From: RTTY [mailto:rtty-bounces@contesting.com] On Behalf Of Joe Subich, W4TV
> Sent: 11 April 2016 13:39
> To: rtty@contesting.com
> Subject: Re: [RTTY] FT4JA performance
> 
> 
> By settling for 10% we sell digital DXing short.  I agree that RTTY will 
> probably never reach 33% as there will be very little time and resources 
> given to RTTY on the low bands.  However, those chasing a DXpedition for ATNO 
> or band credit should not care which mode they work.
> 
> A well run DXpedition, with quality RTTY operators, good antennas and decent 
> propagation should be able to generate peak rates of 2 - 3 QSOs per minute, 
> similar to what they can do on other modes.  Getting 20 to 25% RTTY QSOs is 
> only a matter or *expectations* - making DXpedition planners treat RTTY as an 
> integral part of the operation and not as an afterthought as it is in nearly 
> every case and making those who chase DXCC Challenge/Toplist realize they may 
> need to use multiple modes.
> 
> The real problem is the "Leaderboard" ... DXpeditions spend too much time and 
> resources on Phone/CW on the "middle" bands (20/17/15) and not enough 
> resources on balancing opportunities for RTTY (and in some cases low band 
> QSOs).  The goal of any DXPedition should be to allow everyone who desires, 
> one QSO per mode and one QSO per band (between
> 9 and 11 QSOs *maximum*) ... not 20 to 25 "band/mode" slots as we see in many 
> cases with some of the DX Hogs.
> 
> 73,
> 
>    ... Joe, W4TV
> 
> 
>> On 4/11/2016 8:04 AM, EA2RY wrote:
>> Hello to all.
>> 
>> If a survey on the preferred mode (CW, SSB, RTTY) can even select multiple 
>> options, you never reach that 25%.
>> 
>> 10% is a minimum acceptable percentage.
>> 
>> often by own experience, reach those percentages can be tricky, especially 
>> if it is a ATNO for most amateur radio community.
>> 
>> As a radio amateur who has a preference for the RTTY I wish that these 
>> percentages are higher, but I understand there most preferably CW and SSB.
>> 
>> (Sorry for my Google translación english) ;-)
>> 
>>      73's de Roberto
>> http://www.ea2ry.com
>>         ¯_(ツ)_/¯
>> 
>>> El 11 abr 2016, a las 13:46, Joe Subich, W4TV <lists@subich.com> escribió:
>>> 
>>> 
>>>> 10010 RTTY QSOs that is10% of the 100K  Juan de Nova contacts.
>>> 
>>> That's still a long way short of 20 to 25% of contacts that would 
>>> represent a "fair" allocation of resources.
>>> 
>>> 
>>> 73,
>>> 
>>>  ... Joe, W4TV
>>> 
>>> 
>>>> On 4/11/2016 4:48 AM, Jacques Frilley wrote:
>>>> Any RTTY fan operator should vote for FT4JA as the DXpedition of the Year 
>>>> : 10010 RTTY QSOs that is10% of the 100K  Juan de Nova contacts.
>>>> 73 to all
>>>> F2LZ
>>>> 
>>>> ---
>>>> L'absence de virus dans ce courrier électronique a été vérifiée par le 
>>>> logiciel antivirus Avast.
>>>> http://www.avast.com
>>>> _______________________________________________
>>>> 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
> 
> _______________________________________________
> 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>