[LOGic] DESECHEO K5D

[N6FM Ben]

With respect to the beam heading, yes, we know where it is. But, we buy
software like this, as well as rotor hardware interfaces, etc.,  partially
for the convenience of not having to point the antenna manually (dragging a
pointer around) long or short path, then clicking the button to start it,
all the while we're trying to find out where he's listening and tuning up 5
or so we can have a reasonable chance to get him. 

If our beam had been elsewhere when the spot was received, it is much more
convenient and (in my humble opinion), a wiser use of the program to
pre-configure it so that only pressing a button will start the rotator. 

I want to get the most out of the software that I purchase as I can.
Changing the DXCC as part of the log entry process when a better alternative
exists that will obviate that requirement is well worth the effort. 

I have not had a problem with updates.  

Ben





-----Original Message-----
From: logic-bounces at mailman.qth.net [mailto:logic-bounces at mailman.qth.net]
On Behalf Of J.A. Wolf, MD, K6JW
Sent: Friday, January 30, 2009 2:51 PM
To: LOGic is open to all radio amateurs for discussion of
LOGicloggingprogram
Subject: Re: [LOGic] DESECHEO K5D

Understood. If you want the spot log to be correct, then you would want to 
do this. Of course, when you see K5D spotted, you'll know what it is, 
anyway, but I do see your point. As for the beam heading, I'd guess we all 
pretty much know where the island is. One other consideration: If Dennis 
doesn't mimic what you're doing in the prefix table, the next version won't 
be compatible with the change you make. So, instead of us doing this 
individually, Dennis, if you're reading all this, how about making the 
change so ALL users will get the correct information before the DXpedition 
begins?
--Jeff, K6JW


----- Original Message ----- 
From: "N6FM Ben" <n6fm at oregonfast.net>
To: "'LOGic is open to all radio amateurs for discussion of 
LOGicloggingprogram'" <logic at mailman.qth.net>
Sent: Friday, January 30, 2009 10:33
Subject: Re: [LOGic] DESECHEO K5D


> That takes time, plus you want your beam to point in the correct
> direction...
>
> And, I want my spot log to reflect the correct info...
>
> Ben
>
> -----Original Message-----
> From: logic-bounces at mailman.qth.net [mailto:logic-bounces at mailman.qth.net]
> On Behalf Of J.A. Wolf, MD, K6JW
> Sent: Friday, January 30, 2009 10:23 AM
> To: LOGic is open to all radio amateurs for discussion of
> LOGicloggingprogram
> Subject: Re: [LOGic] DESECHEO K5D
>
> Since this is going to be a unique, one-time callsign in all probability 
> for
>
> the entity, why not just enter the DXCC and zone info manually when you 
> work
>
> the DXpedition? Won't that do the job, or am I missing something?
> --Jeff, K6JW
>
>
>
> ----- Original Message ----- 
> From: "K0DAN" <k0dan at comcast.net>
> To: <logic at mailman.qth.net>
> Sent: Thursday, January 29, 2009 22:37
> Subject: [LOGic] DESECHEO K5D
>
>
>> With Desecheo K5D about to go QRV, I'm trying to set up the prefix table,
>> etc., to make Logic recognize the special call.
>>
>> Every time I try this on my own, because I think I know how to do it,
>> something goes wrong.
>>
>> So far I have added K5D to the KP5 prefix, with dates of 2/12/09-2/26/09.
>>
>> Is that all ther is to it (other than working them)?
>>
>> Any assistance greatly appreciated.
>>
>> Tnx es 73
>>
>> Dan
>> K0DAN
>>
>> _______________________________________________
>> LOGic mailing list
>> LOGic at mailman.qth.net
>> http://mailman.qth.net/mailman/listinfo/logic
>>
>
> _______________________________________________
> LOGic mailing list
> LOGic at mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/logic
>
> _______________________________________________
> LOGic mailing list
> LOGic at mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/logic
> 

_______________________________________________
LOGic mailing list
LOGic at mailman.qth.net
http://mailman.qth.net/mailman/listinfo/logic