Maybe it's just my setup or I'm doing something incorrectly, although George
found nothing wrong in my LOGCFG.DAT file. Maybe it's the individual DX
Packet Cluster and how it formats things?
For me, anyway, a standard DX spot gets echoed to the bandmap and the
little announce window (BTW I like that announce window format because
I can tell who made the announcement [as the Cluster gets spots from
other areas]), but the SH/DX spots don't. This was why I thought I still had
problems with my packet hookup (the middle of a work day doesn't generate
many up-to-the-minute spots!) and asked George for assistance.
After I take a break, it would be great to come back and, as Lee suggests, load
up
the bandmap with SH/DX spots although admittedly the "ageing" might wind up
being
inaccurate. Still, it'll give you an idea of what's going on.
73, Bob AA0CY
----------
From: Lee Hiers, AA4GA[SMTP:aa4ga@contesting.com]
Sent: Monday, January 26, 1998 8:31 AM
To: trlog@contesting.com
Subject: RE: [TRLog] Packet es TR Rig control
On 25 Jan 98, ROBERT WANDERER wrote:
> Tree, any chance of allowing the packet spots obtained via the SH/DX command
> to be reflected in the band map?
I thought they did go to the bandmap. Can't you do a big SH/DX/50 to
load up the band map?
--
Lee Hiers - AA4GA
Cornelia, GA
mailto:aa4ga@contesting.com
--
FAQ on WWW: http://www.contesting.com/trlogfaq.html
Submissions: trlog@contesting.com
Administrative requests: trlog-REQUEST@contesting.com
Problems: owner-trlog@contesting.com
Feature Wishlist: http://web.jzap.com/n6tr/trwish.html
--
FAQ on WWW: http://www.contesting.com/trlogfaq.html
Submissions: trlog@contesting.com
Administrative requests: trlog-REQUEST@contesting.com
Problems: owner-trlog@contesting.com
Feature Wishlist: http://web.jzap.com/n6tr/trwish.html
|