This worked for us during the ARRL DX CW, M/2. We assigned a TR identifier
to each station (we used L for left and R for right). We also TR-networked
the stations so that both stations had log entries from both stations (and
thus the multiplier info, etc). POST was used to first extract only
L-entries from the L log and only R-entries from the R log. Then POST was
used to merge those two results into one log, RETAINING station ID. Bottom
line when all done is the Cabrillo log did indeed have a 0 or 1 in the
rightmost column to indicate the station. Contacts in the Cabrillo log were
ordered by GMT timestamp. Worked like a charm, but care was required so
that station ID was not lost and the logs were not scrambled when done. :-)
Gary W2CS (@NY4A)
| -----Original Message-----
| From: owner-trlog@contesting.com [mailto:owner-trlog@contesting.com]On
| Behalf Of Tree N6TR
| Sent: Tuesday, March 20, 2001 12:56 PM
| To: TRLOG@contesting.com; whhendrick@home.com
| Subject: Re: [TRLog] Cabrillo for M/2
|
|
|
| > How are M/2 identifying their TX1 and TX2 when making a Cabrillo file? =
| > When I run the Cabrillo routine and look at the file there is
| nothing to =
| > tell the two transmitters apart.
|
| It's in the Cabrillo spec - a number (0 or 1) at the end of the QSO
| entry.
|
| Someone told me this was working with TR - but it has been over a
| year since I looked at it. You probably need to have the
| computer ID setup to show A or B for each rig.
|
| Tree
|
| --
| FAQ on WWW: http://www.contesting.com/FAQ/trlog
| 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/FAQ/trlog
Submissions: trlog@contesting.com
Administrative requests: trlog-REQUEST@contesting.com
Problems: owner-trlog@contesting.com
Feature Wishlist: http://web.jzap.com/n6tr/trwish.html
|