Send Trlog mailing list submissions to
trlog@contesting.com
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.contesting.com/mailman/listinfo/trlog
or, via email, send a message with subject or body 'help' to
trlog-request@contesting.com
You can reach the person managing the list at
trlog-owner@contesting.com
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Trlog digest..."
Today's Topics:
1. Fw: [Orion] Couple of questions (john, ke5c)
2. glitch (Tod - ID)
3. Back from HC8 (Tree)
4. Mode change in bandmap (Thomas R. Williams)
5. Display of actual QSO totals (Charlie Ocker)
----------------------------------------------------------------------
Date: Sun, 7 Dec 2003 11:42:35 -0600
From: "john, ke5c" <ke5c@hot.rr.com>
To: <trlog@contesting.com>
Cc: Tom Whiteside - N5TW <tomw@ecpi.com>
Subject: [Trlog] Fw: [Orion] Couple of questions
Message-ID: <001901c3bce9$80534ad0$6401a8c0@athlon14>
Content-Type: text/plain;
charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: list
Message: 1
This happened twice while I was operating (about 16 hours total). It's like
TR is getting bad data from the Orion. Fortunately N5TW has lots of
protection and an Alpha which simply trips out very quickly when it sees the
high SWR. VFOB was tuning the subreceiver when this happened. The
transmitter was connected to VFOA, and the VFO lock was on. This would be an
issue in a multiband contest where TR drives the antenna and bandpass
selection. I've noticed the frequency display goes aways for several seconds
at a time, and this also suggest that communication is not rock-solid.
73, John
I'll post more later on our experience using the Orion on the ARRL 160M
contest later - it was great BTW... But a couple of questions that come to
mind now:
First off, we had problems with TR not seeing the radio a times. Didn't
happen often enough to pin it down but seemed to happen when tuning the sub
rx vfo (not sure about the main rx - mainly we were leaving that alone and
did not observe this happen when we did) and when hitting the space bar to
mark a station in the band map when doing search and pounce. This "funny"
resulted in TR turning off the transmit antenna which is a BAD thing!
Worked around it by selecting the antenna manually which was no biggie in a
single band contest. I'd like to see if others are seeing this - I plan
to send this in to TR and TT for their information...
(-----snip-----)
Tom Whiteside
N5TW Georgetown, TX
------------------------------
Date: Sun, 7 Dec 2003 12:56:18 -0600
From: "Tod - ID" <tao@skypoint.com>
To: <trlog@contesting.com>
Subject: [Trlog] glitch
Message-ID: <200312071150609.SM00203@scanmail2.cableone.net>
Content-Type: text/plain;
charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Precedence: list
Message: 2
I think this has been discussed previously --
=20
Can anyone give me a clue as to when so I can check the archives.
=20
I noticed a few times this weekend in the 160 contest that when I used =
the
band sheet to jump to a frequency where someone was calling CQ I got =
CW-USB
for the CW setting . Normally I use CW-LSB and would have expected that =
my
CW setting would not be changed. Is there a setting that governs this? =
Any
ideas of what I should look for?=20
=20
Thanks in advance for any help.
=20
Tod, K=D8TO
------------------------------
Date: Sun, 7 Dec 2003 13:26:36 -0600
From: Tree <tree@kkn.net>
To: trlog@contesting.com
Subject: [Trlog] Back from HC8
Message-ID: <20031207192636.GA25780@kkn.net>
Content-Type: text/plain; charset=us-ascii
MIME-Version: 1.0
Precedence: list
Message: 3
Finally getting on top of e-mail since my return from HC8.
Had a nice time down there - and the K1EA network option worked very well
during the contest. One feature I added while down there was adding a
note to the log when someone makes an edit with CT. The note will indicate
which previous QSO should be removed. Then the corrected QSO is logged.
A utililty has been added to POST that will clean the log up by removing
the appropriate QSOs and the notes. I am next going to add a sort routine
to get the log back into chronological order. This routine will also merge
several logs (in Cabrillo) and remove duplicates. These new features will
be in the next release.
I think I have been convinced to add an option to increase the size of the
editable log window to 10 QSOs - and also make the "virtual" editable log
bigger - maybe 20 QSOs. This will allow many of the edits that come across
the network to be handled in real time and allow for greater editing
capability with TR itself. At HC8N, we would often log 5 QSOs within a few
seconds of each other.
I am still digesting all of the other messages on the reflector. I think
some of the bandmap stuff can be cleaned up pretty easily, and while the
radio interfaces seem to be working better, I am still thinking of a major
change to the way it all works to help improve reliability.
One of the real bummers about CT going to freeware is that the revenue for
TR Log has plumented. Not much we can do about that, but it would really
help if everyone who isn't a life member is good about sending in your
yearly $15. Also, please encourage those who are using the program without
buying their own copy to fork up the $$$. It isn't that much and will help
insure that the program continues to be enhanced. Thanks.
Hope everyone has a good holiday season.
73 Tree N6TR
tree@kkn.net
------------------------------
Date: Mon, 8 Dec 2003 08:43:39 -0500
From: "Thomas R. Williams" <n2cu@magtrol.com>
To: <trlog@contesting.com>
Subject: [Trlog] Mode change in bandmap
Message-ID: <000801c3bd91$496e9f80$7b0ea8c0@twilliams>
Content-Type: text/plain;
charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Precedence: list
Message: 4
Maybe someone has already addressed this...=20
When using the band map to jump to a station, my FT1000MP changes modes =
from CW to LSB. The stations got into the bandmap correctly as I was =
S&P'ing my way along in the 160m contest.=20
Here's the catch... it doesn't seem to happen when I select a station =
from the first (left hand) column, just from the second column of calls.
Using the latest version. Previous version used (6.72) didn't do this.
73,
Tom N2CU <><
------------------------------
Date: Mon, 08 Dec 2003 08:07:56 -0700
From: Charlie Ocker <N9CO@aol.com>
To: TR Log Reflector <trlog@contesting.com>
Subject: [Trlog] Display of actual QSO totals
Message-ID: <3FD493CC.7040701@aol.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: list
Message: 5
During this past weekend's ARRL 160 contest, I had TR (v6.74) configured
to "work dupes in run mode" because it was quicker and easier to work
'em again than to send the "qso b4" message.
I noticed, however, that the running QSO total included these dupes.
The on-going score calculation was correct, as expected.
I think it would be very useful if the displayed QSO total did not show
dupes. It would give the operator a better idea of how he/she is
actually doing. Correct me if I'm wrong; I've been using TR since v3.83
way back in the early 90's and seem to recall that the displayed QSO
total used to work this way.
FWIW, I had something like 40 dupes in my log. Many of these stations
called me repeatedly. I don't know if this is normal for 160 contesting
or not. Maybe they were casual ops who didn't use logging software?
73,
Charlie N9CO
------------------------------
_______________________________________________
Trlog mailing list
Trlog@contesting.com
http://lists.contesting.com/mailman/listinfo/trlog
End of Trlog Digest, Vol 12, Issue 8
************************************