On 2009-11-13, at 12:11 PM, aoafom92 wrote:

> One way I tried to make this work was to run a report in MLDX rearrange the
columns and then upload to the manual Cab page at www.b4h.net/cabforms but I
can't figure out how to extract the report info in to a usable format.

MacLoggerDX Version 5.10 Beta 22 allows you to export any report as a tab
delimited text file. After you export it you would still have to massage the
data into a format that cabforms can use.

73 de VE3VRW Don Agro

That's right.

Serial number in the right place.

Four exchange items in the sent and received text areas.

Once all that is in place it should convert nicely. Please let me know if it
doesn't!

-- Scott (NE1RD and author of Cab-converter)


--- In cab-converter@yahoogroups.com, "aoafom92" <rick.prather@...> wrote:
>
>
>
> Oh that's no fun!
>
> I would rather do several hours of messing around with different formats to
automate it than spend 20 minutes doing it manually!   :-)
>
> I already have it in MLDX as a separate log so I will get on it!
>
> I assume I need to move the SRN to the correct field and insert the Call sign
in the SRX field so that Cab Converter won't choke on the lack of a call sign?
>
> Thanks,
>
> Rick
> K6LE

Oh that's no fun!

I would rather do several hours of messing around with different formats to
automate it than spend 20 minutes doing it manually!   :-)

I already have it in MLDX as a separate log so I will get on it!

I assume I need to move the SRN to the correct field and insert the Call sign in
the SRX field so that Cab Converter won't choke on the lack of a call sign?

Thanks,

Rick
K6LE

--- In cab-converter@yahoogroups.com, "ne1rd_ham" <ne1rd@...> wrote:
>
> I think you should submit your log!
> :-)
>
> Here's what I would do:
> 1. Export the log into ADIF and import that into a fresh, new MLDX
database/log file.
> 2. There are only 90 entries. If you can do 4 a minute (I just fixed another
log and had about that pace in my effort) you can get the whole thing ship-shape
in 14 minutes or so. You'd have a tough time finding any tool that would get it
done in less than 14 minutes of your time. Ready? Go! See, for 90 entries it is
better just to DO IT.
>
> If you like, I would take a quick pass at it. It it only takes 10 minutes of
my time to get your log in it sounds worth it to me. I just spent 5 minutes on
this message! LOL!
>
> Seriously, give it a shot. Import it into MLDX and see if it doesn't fix
quickly. If you have trouble, send me the ADIF and I'll take a look. You put in
a lot of effort! You should send in your log!
>
> -- Scott (NE1RD and author of Cab-converter)
>
> --- In cab-converter@yahoogroups.com, "aoafom92" <rick.prather@> wrote:
> >
> > I really backed myself in a corner with my SS CW log.
> --snip--
> > Since I wasn't going to submit, I logged the received exchange completely in
the SRX String box and omitted the call sign.   For example:  "163 B 55 NTX".
> --snip--
>

Hi Scott,

On 2009-11-13, at 2:56 PM, ne1rd_ham wrote:

> I don't want to get into a MLDX design discussion but the TAB to move forward
and SHIFT-TAB to move backwards is a reasonable way to deal with this. So, the
following is your best bet IMHO:
>
> In the contest panel:
>
> Command-K (clear all fields, focus left in the call entry area)
> Enter call sign
> Tab Tab
> Enter S/N
> Shift-Tab
> Enter precedence callsign check digits section
> Shift-command-L (to log it)
>
> {repeat for 48 hours}
>
> This is not optimal, but it works. Most other contest interactions have some
variant of this dance. Once you get into the rhythm it isn't as bad as it
sounds.

Thanks to the people who have contributed on the MacLoggerDX Contest list, beta
20 (Just released) has a "Log QSO and Clear Fields" Menu command which you can
attach to any keyboard shortcut you like.

This logs the QSO, clears all the fields and focuses on the Call Sign field.

Contest panel changes in Beta 20...

	 • The Log QSO and Clear Fields menu command allows quick field tabbing and
logging from the Keyboard.
	 • The Call Sign field automatically upcases your typing and will do a lookup
when you tab out of the field. Make sure to set your Call Book to None in the
Lookup Prefs if you are contesting unassisted.
	 • You can show or hide Contest Panel Fields and Labels based on the Contest
Prefs check boxes.
	 • The Map Rcvd popup in the Contest Prefs will automatically fill in some log
fields based on the Rcvd field (SRX_STRING).
	 • The Call Sign field will flash red if the call is already in your log as you
type.


This is a Beta not a full release and it may change as more feedback comes in on
the list.

73 Don Agro VE3VRW

D o g   P a r k   S o f t w a r e   L t d .

email: dagro@...
   www: http://www.dogparksoftware.com
     iChat AV:dogpark@...

I think you should submit your log!
:-)

Here's what I would do:
1. Export the log into ADIF and import that into a fresh, new MLDX database/log
file.
2. There are only 90 entries. If you can do 4 a minute (I just fixed another log
and had about that pace in my effort) you can get the whole thing ship-shape in
14 minutes or so. You'd have a tough time finding any tool that would get it
done in less than 14 minutes of your time. Ready? Go! See, for 90 entries it is
better just to DO IT.

If you like, I would take a quick pass at it. It it only takes 10 minutes of my
time to get your log in it sounds worth it to me. I just spent 5 minutes on this
message! LOL!

Seriously, give it a shot. Import it into MLDX and see if it doesn't fix
quickly. If you have trouble, send me the ADIF and I'll take a look. You put in
a lot of effort! You should send in your log!

-- Scott (NE1RD and author of Cab-converter)

--- In cab-converter@yahoogroups.com, "aoafom92" <rick.prather@...> wrote:
>
> I really backed myself in a corner with my SS CW log.
--snip--
> Since I wasn't going to submit, I logged the received exchange completely in
the SRX String box and omitted the call sign.   For example:  "163 B 55 NTX".
--snip--

I don't want to get into a MLDX design discussion but the TAB to move forward
and SHIFT-TAB to move backwards is a reasonable way to deal with this. So, the
following is your best bet IMHO:

In the contest panel:

Command-K (clear all fields, focus left in the call entry area)
Enter call sign
Tab Tab
Enter S/N
Shift-Tab
Enter precedence callsign check digits section
Shift-command-L (to log it)

{repeat for 48 hours}

This is not optimal, but it works. Most other contest interactions have some
variant of this dance. Once you get into the rhythm it isn't as bad as it
sounds.

-- Scott (NE1RD)

--- In cab-converter@yahoogroups.com, "wb0m@..." <wb0m@...> wrote:
>
> On Nov 13, 2009, at 10:28 AM, ne1rd_ham wrote:
>
> > I'm thinking about what makes sense going forward but this is the
> > way it works today. So, again, just enter all the data as you hear
> > it: precedence, callsign, check digits, section, and Cab-converter
> > will "do the right thing".
>
> So here's a question: would it be possible to re-work Cab-converter to
> take all the need information from the "rcvd" field instead of both
> the "rcvd" and "Rcvd sn" fields? My reasoning is that the Sweeps
> information is transmitted, in order: consecutive serial number,
> precedence, callsign, check and section. The way MLDX v5 is set up now
> you have to get to the to the "rcvd sn" field first info and then get
> back "rcvd" box.
>
> While it's not convenient, if I get into a run or get flustered
> (especially on cw) I just type everything into the "rcvd" box and then
> later transfer the consecutive serial number to the "Rcvd sn" box.
> Of course, the plus side to this that I can double check everything
> for typos and wrong section abbreviations, which is good.
>
> Does this make any sense?
>
> Tnx, as always,
>
> Jeff/wb0m
>

On Nov 13, 2009, at 9:49 AM, David Kaplan wrote:

> Thanks Scott.
>
>
> David, WA1OUI
> On Nov 13, 2009, at 11:28 AM, ne1rd_ham wrote:
>
>
>
>
> David,
>
> The manual entry for this contest describes what you need to put
> into both the sent and received strings. The general idea is to
> capture the information sent in this prescribed order: precedence,
> callsign, check digits, section. It is strange that the contest asks
> that the exchange contains the call sign, but they do and therefore
> we capture it in the exchange field. A sample exchange follows:
>
> "A NE1RD 02 EMA".
>
A correct sample exchange is something like "123 A NE1RD 02 EMA". A
sequential serial number preceeds the information you give. I realize
that the number sent is automatically recorded in the Cabrillo file or
other logging file, but you must send the serial number as well as
receive and record the received sxchange, including the serial number.

This will become clear after a few minutes in the contest. :^)= - Duffey

I really backed myself in a corner with my SS CW log.

I used Skookumlogger and used it's generic QSO party template.  That worked fine
for the contest and I wasn't planning on sending in a log since I was only going
to look for states I needed for the Triple Play award and at the same time get
some comfort level with Skookumlogger.

In the end I had worked 90+ and decided it would be nice to submit the log.

Well, the project has become an interesting challenge!

Since I wasn't going to submit, I logged the received exchange completely in the
SRX String box and omitted the call sign.   For example:  "163 B 55 NTX".

Of course there are at least two things wrong with that since it includes the
number and even though the call sign is omitted I imagine that Cab Converter
would try to strip the call and reject it since it can't find it.

One way I tried to make this work was to run a report in MLDX rearrange the
columns and then upload to the manual Cab page at www.b4h.net/cabforms but I
can't figure out how to extract the report info in to a usable format.

Scott, don't waste any brain cells on this, I just thought you might get a
chuckle out of it.

I am not really concerned about the entry just been playing with this conversion
for the learning experience.

Rick
K6LE


--- In cab-converter@yahoogroups.com, "ne1rd_ham" <ne1rd@...> wrote:
>
>
>
> David,
>
> The manual entry for this contest describes what you need to put into both the
sent and received strings. The general idea is to capture the information sent
in this prescribed order: precedence, callsign, check digits, section. It is
strange that the contest asks that the exchange contains the call sign, but they
do and therefore we capture it in the exchange field. A sample exchange follows:
>
> "A NE1RD 02 EMA".
>
> So, if you are working me in the contest, you would get something like the
above (depending upon my power level, of course). All of this information--even
the call sign--should go into the captured and sent text fields.
>
> Cab-converter will take all this and create a valid (I hope!) Cabrillo file.
Omitting information will cause Cab-converter to discard the entry as
ill-formed.
>
> I'm thinking about what makes sense going forward but this is the way it works
today. So, again, just enter all the data as you hear it: precedence, callsign,
check digits, section, and Cab-converter will "do the right thing".
>
> -- Scott (NE1RD and author of Cab-converter)
>
> --- In cab-converter@yahoogroups.com, David Kaplan <dhkaplan@> wrote:
> >
> > I'm getting myself mentally prepared for my first Sweepstakes next weekend,
and am trying to understand the logistics of logging it all.
> >
> > I understand the verbal exchange that includes my call, and the other
stations call. What I wanted to verify was how it was logged. In reading the
Cab-Converter manual it seems as if the call that is part of the rx string IS
entered in the string field, meaning that I type the received call twice into
MacLoggerDX, once in the call field, and once in the rx string field with the
other info.
> >
> > In looking at the material that Cab-Converter provides, it looks as if the
rx string call is stripped from the output cabrillo and only appears once in the
call field.
> >
> > Is this all correct?
> >
> > Many thanks, and see you on the air.
> >
> > 73,
> >
> > David, WA1OUI
> >
>

David,

The manual entry for this contest describes what you need to put into both the
sent and received strings. The general idea is to capture the information sent
in this prescribed order: precedence, callsign, check digits, section. It is
strange that the contest asks that the exchange contains the call sign, but they
do and therefore we capture it in the exchange field. A sample exchange follows:

"A NE1RD 02 EMA".

So, if you are working me in the contest, you would get something like the above
(depending upon my power level, of course). All of this information--even the
call sign--should go into the captured and sent text fields.

Cab-converter will take all this and create a valid (I hope!) Cabrillo file.
Omitting information will cause Cab-converter to discard the entry as
ill-formed.

I'm thinking about what makes sense going forward but this is the way it works
today. So, again, just enter all the data as you hear it: precedence, callsign,
check digits, section, and Cab-converter will "do the right thing".

-- Scott (NE1RD and author of Cab-converter)

--- In cab-converter@yahoogroups.com, David Kaplan <dhkaplan@...> wrote:
>
> I'm getting myself mentally prepared for my first Sweepstakes next weekend,
and am trying to understand the logistics of logging it all.
>
> I understand the verbal exchange that includes my call, and the other stations
call. What I wanted to verify was how it was logged. In reading the
Cab-Converter manual it seems as if the call that is part of the rx string IS
entered in the string field, meaning that I type the received call twice into
MacLoggerDX, once in the call field, and once in the rx string field with the
other info.
>
> In looking at the material that Cab-Converter provides, it looks as if the rx
string call is stripped from the output cabrillo and only appears once in the
call field.
>
> Is this all correct?
>
> Many thanks, and see you on the air.
>
> 73,
>
> David, WA1OUI
>

I'm getting myself mentally prepared for my first Sweepstakes next weekend, and
am trying to understand the logistics of logging it all.

I understand the verbal exchange that includes my call, and the other stations
call. What I wanted to verify was how it was logged. In reading the
Cab-Converter manual it seems as if the call that is part of the rx string IS
entered in the string field, meaning that I type the received call twice into
MacLoggerDX, once in the call field, and once in the rx string field with the
other info.

In looking at the material that Cab-Converter provides, it looks as if the rx
string call is stripped from the output cabrillo and only appears once in the
call field.

Is this all correct?

Many thanks, and see you on the air.

73,

David, WA1OUI

Members of the Caribbean Buddies 2010 team will mount a DXpedition to St. Lucia
(J6) February 2-10, 2010. Nine operators from eight states will have fixed
operations from a cliff-top villa and portable operations from various points on
the island using CW, SSB, and digital modes. The team consists of the following
operators: Chris Drummond (W6HFP), Budd Drummond (W3FF), B. Scott Andersen
(NE1RD), Dan Gagnon (WZ1P), Steve Galchutt (WG0AT), Mike Greenwood (KC4VG), Guy
Hamblen (N7UN), Paul Van Dyke (KB9AVO), and Weymouth Walker (K8EAB). Licensing
is not yet complete but each operator is expected to receive their owncall sign.
QSL via LoTW, eQSL, or mail to operator's home call (SASE required). See the
DXpedition daily "journal" blog at http://caribbeanbuddies.blogspot.com/ or the
2010 Dxpedition website at http://sites.google.com/site/caribbeanbuddies/ for
new announcements.

I am very sorry you are having trouble. The very fastest way to get this
resolved is to send me your ADIF file and let me take a look at it. Please
forward it to ne1rd -at- arrl -dot- net and I'll see if I can figure out what
happened.

-- Scott (NE1RD and author of Cab-converter)

--- In cab-converter@yahoogroups.com, Richard Cincotta <ki4fw@...> wrote:
>
>
> I've successfully put Cab-convertor to work after each contest for past
several years, but something "unusual" occurred when I tried the version I am
using (1.35) on my SS-CW ADIF file.  Cab-convertor read the data into columns on
the screen, but when I tried to convert it to a cabrillo file, it wrote the
cabrillo header but no QSOs (and wrote the end-of-file marker).  After
Cab-convertor writes this incomplete file, it takes the checkmarks off of all
the data on the screen.
> Does anyone know what I might have done wrong -- or has anyone seen this
occur?
> Thanks for any help,
> Rich, KI4FW
> _________________________________________________________________
> Windows 7: Unclutter your desktop.
>
http://go.microsoft.com/?linkid=9690331&ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL\
_WIN_evergreen:112009
>

Thank you!

:-)

-- Scott (NE1RD and author of Cab-converter)

--- In cab-converter@yahoogroups.com, Don Agro <dagro@...> wrote:
>
>
> On 2009-11-07, at 11:29 AM, ne1rd_ham wrote:
>
> > The question is moot for now (because, as you say, we ignore it in the
current version) but I'm collecting ideas for the next generation of
Cab-converter and I'm seeing what options I have and what might be nice to do.
This was actually on my list to think about (which is why I put all that effort
into standardizing the enumerated list in the proposed ADIF standard...
>
> MacLoggerDX Version 5.19 Beta 7 now has an enumerated popup for Contest ID in
the Contest Prefs Panel. The popup is loaded from a file which contains the
current ADIF (v2.2.3) enumeration but can be updated in the field at any time
with "Update Internet Files".
>
> 73 de VE3VRW Don Agro
>

On 2009-11-07, at 11:29 AM, ne1rd_ham wrote:

> The question is moot for now (because, as you say, we ignore it in the current
version) but I'm collecting ideas for the next generation of Cab-converter and
I'm seeing what options I have and what might be nice to do. This was actually
on my list to think about (which is why I put all that effort into standardizing
the enumerated list in the proposed ADIF standard...

MacLoggerDX Version 5.19 Beta 7 now has an enumerated popup for Contest ID in
the Contest Prefs Panel. The popup is loaded from a file which contains the
current ADIF (v2.2.3) enumeration but can be updated in the field at any time
with "Update Internet Files".

73 de VE3VRW Don Agro

When Cab-Converter supports the ADIF CONTEST_ID tag and there is an accepted
enumeration list in the ADIF spec it will be a simple matter for MacLoggerDX to
replace the Text field with a combo box which would select from the current list
or allow the user to add a new contest ID if a new contest is not in the list.
There is no way that I can think of to ensure that the user remembers to turn it
off for non-contest QSO's.

--- In cab-converter@yahoogroups.com, "ne1rd_ham" <ne1rd@...> wrote:
>
> Bill (W8BC) asked what it was and I gave the best explanation I could. It is
true that Cab-converter does ignore that field now.
>
> In the future, if we were sure that the field was used in such a way that each
contest QSO had the field set to a valid value then we could use it to filter
out non-contest QSOs from the set (sometimes people will make a QSO during a
contest period they do not want to include in the contest submission--this would
be an easy way to identify such QSOs). But, we'd want to be sure that the value
people put in there was something expected (one of the specification-listed
contest identifiers).
>
> The question is moot for now (because, as you say, we ignore it in the current
version) but I'm collecting ideas for the next generation of Cab-converter and
I'm seeing what options I have and what might be nice to do. This was actually
on my list to think about (which is why I put all that effort into standardizing
the enumerated list in the proposed ADIF standard...)
>
> -- Scott (NE1RD)
>
> --- In cab-converter@yahoogroups.com, "ve3vrw" <dagro@> wrote:
> >
> >
> >
> > --- In cab-converter@yahoogroups.com, "ne1rd_ham" <ne1rd@> wrote:
> > > All this below should be filed under the "I'm sure we both know this and
agree but for the benefit of those on the list--here goes:"
> >
> > The point is moot since Cab-Converter ignores the "CONTEST_ID" tag in ADIF
files don't you think ?
> >
>

--- In cab-converter@yahoogroups.com, "w8bc" <wcombs@...> wrote:
>
> > The green "LED" doesn't need a radio connection... it works on lookup.
> I don't think that is technically correct, David. If you enter a contact
without the rig connected and thus get no frequency and maybe other data from
the radio, and then look up the same call, I get no green dot. This was
confirmed by Jeff. If you already have a contact in the log that was put there
when the radio was hooked up to the radio and then look up the same call with
the radio disconnected, you will get the green dot. At least that was our
experience. You can test it by entering the same call twice without the radio
connected--one that is not already in the log.

Dup checking is not directly affected by a connected radio or an internet
connection.

It is not activated by a press of the "Display" button but is active for every
lookup.

If the log entry is missing frequency information then it will not be considered
as a dupe since it is not a QSO worked on any Ham band.

Bill (W8BC) asked what it was and I gave the best explanation I could. It is
true that Cab-converter does ignore that field now.

In the future, if we were sure that the field was used in such a way that each
contest QSO had the field set to a valid value then we could use it to filter
out non-contest QSOs from the set (sometimes people will make a QSO during a
contest period they do not want to include in the contest submission--this would
be an easy way to identify such QSOs). But, we'd want to be sure that the value
people put in there was something expected (one of the specification-listed
contest identifiers).

The question is moot for now (because, as you say, we ignore it in the current
version) but I'm collecting ideas for the next generation of Cab-converter and
I'm seeing what options I have and what might be nice to do. This was actually
on my list to think about (which is why I put all that effort into standardizing
the enumerated list in the proposed ADIF standard...)

-- Scott (NE1RD)

--- In cab-converter@yahoogroups.com, "ve3vrw" <dagro@...> wrote:
>
>
>
> --- In cab-converter@yahoogroups.com, "ne1rd_ham" <ne1rd@> wrote:
> > All this below should be filed under the "I'm sure we both know this and
agree but for the benefit of those on the list--here goes:"
>
> The point is moot since Cab-Converter ignores the "CONTEST_ID" tag in ADIF
files don't you think ?
>

--- In cab-converter@yahoogroups.com, "ne1rd_ham" <ne1rd@...> wrote:
> All this below should be filed under the "I'm sure we both know this and agree
but for the benefit of those on the list--here goes:"

The point is moot since Cab-Converter ignores the "CONTEST_ID" tag in ADIF files
don't you think ?

Don,

All this below should be filed under the "I'm sure we both know this and agree
but for the benefit of those on the list--here goes:"

The ADIF standard has the CONTEST_ID as a string, yes. But the specification
also references a number of "Enumerations", collections of values valid for a
particular field. The ARRL Section (ARRL_SECT) should only have a value from the
"ARRL Section Enumeration", for example. The CONTEST_ID similarly should have a
value only from the "Contest ID" enumeration. These values are type "String" but
the valid string values come only from the enumeration of valid value.

You are also quite correct that the list changes from version to version the
specification. I spent a considerable amount of time in February working on a
proposal for an updated list of contests for ADIF version 2.2.4 (the
specification is still under review) so that the enumeration would be up-to-date
with the latest state QSO parties and other contests that had cropped up over
the years.

From the ADIF 2.2.3 specification:

Name Data Type Enumeration Header Only Description
----    ---- ----   ----------- -----------
----------------------------------------------------------
. . .
CONTEST_ID String Contest ID   QSO Contest Identifier *use enumeration values
for interoperability

Then the specification has collection of "Enumerations" including "ARRL Section
Enumeration", "Award Enumeration", "Band Enumeration", "Contest ID", and so on.

Enumerations
-------------

. . .

Contest ID
----------

Contest-ID Description
----------  -----------
7QP 7th-Area QSO Party
ANARTS-RTTY ANARTS WW RTTY
ANATOLIAN-RTTY Anatolian WW RTTY
AP-SPRINT Asia - Pacific Sprint
ARI-DX ARI DX Contest
ARRL-10 ARRL 10 Meter Contest
ARRL-160 ARRL 160 Meter Contest
ARRL-DX-CW ARRL International DX Contest (CW)
... and so on...

This is lots of minutiae for the average Cab-converter user. The only thing
users need to know is that Cab-converter consumes ADIF files so David and I are
going to try to stay on top of the ADIF Standard Committee efforts. For this
particular field, CONTEST_ID, we're not paying any attention to it. But, for the
other fields we look to the standard to ensure we interpret the contents of the
ADIF file properly.

-- Scott (NE1RD)

--- In cab-converter@yahoogroups.com, "ve3vrw" <dagro@...> wrote:
>
>
>
> --- In cab-converter@yahoogroups.com, "ne1rd_ham" <ne1rd@> wrote:
>
> > The string is supposed to be an instance of a specific list of contest
identifiers as defined in the ADIF standard. For example, ARRL-SS-SSB is the
string for the ARRL Sweepstakes Contest (SSB).
>
> Actually no, CONTEST_ID as defined in the ADIF spec is a string not an
enumeration because the list is constantly growing.
>

--- In cab-converter@yahoogroups.com, "ne1rd_ham" <ne1rd@...> wrote:

> The string is supposed to be an instance of a specific list of contest
identifiers as defined in the ADIF standard. For example, ARRL-SS-SSB is the
string for the ARRL Sweepstakes Contest (SSB).

Actually no, CONTEST_ID as defined in the ADIF spec is a string not an
enumeration because the list is constantly growing.

> The green "LED" doesn't need a radio connection... it works on lookup.
I don't think that is technically correct, David. If you enter a contact without
the rig connected and thus get no frequency and maybe other data from the radio,
and then look up the same call, I get no green dot. This was confirmed by Jeff.
If you already have a contact in the log that was put there when the radio was
hooked up to the radio and then look up the same call with the radio
disconnected, you will get the green dot. At least that was our experience. You
can test it by entering the same call twice without the radio connected--one
that is not already in the log.

Bill
W8BC

--- In cab-converter@yahoogroups.com, David Kaplan <dhkaplan@...> wrote:
>
> Hi Bill,
>
> The green "LED" doesn't need a radio connection... it works on lookup.
> If you look up a call that you've worked before it will start flashing
> until your next lookup...
>
> It does need internet of course, obviously! And you're right about the
> bigger screen...
>
> David, WA1OUI
>
>
> On Nov 6, 2009, at 8:44 PM, w8bc wrote:
>
> Thanks, David. My problem was that I was not connected up to the rig.
> You need some frequency or other data for the green dot to work.
> Thanks for the info about the blue dot. Good to know. Yes, good point
> about the contest helper. Just need a bigger screen now.
>
> Bill
> W8BC
>
> --- In cab-converter@yahoogroups.com, David Kaplan <dhkaplan@> wrote:
>  >
>  > Oh yes,
>  >
>  > The gray dot to the left of the green dot turns blue when you are
>  > connected to a DX Cluster.
>  >
>  > 73,
>  >
>  > David, WA1OUI
>  >
>  > On Nov 6, 2009, at 12:44 PM, w8bc wrote:
>  >
>  > Okay, humor me here Jeff. I can see the dupes in the contest helper
>  > (as Rick says). That works, but what is the little dot to the upper
>  > left of the call sign? Where exactly, what panel or screen are you
>  > seeing this dot in? Don't see any dot, green or otherwise. I
> thought I
>  > had read the manual. Obviously I am getting too old... or am too old.
>  > But humor me anyway. Thanks
>  >
>  > Bill
>  > W8BC
>  >
>  > --- In cab-converter@yahoogroups.com, "wb0m@" <wb0m@> wrote:
>  > >
>  > > Actually, it's pretty easy. Make a new log for the contest and just
>  > > watch the little dot to the upper left of the call sign. If it's
>  > > flashing green, it's a dupe. The info will be at far left. If you
>  > > click on the green dot it will display on the QSO down in the log
>  > > window. I believe for the Sweepstakes, it's a "work 'em only once"
>  > > contest. Now, of course, you are still going to read the manual,
>  > > right....? (hi). GL and hope to see you in the 'test. 73, Jeff/wb0m
>  > >
>  > >
>  > >
>  > >
>  > > On Nov 6, 2009, at 9:44 AM, w8bc wrote:
>  > >
>  > > > Still much to learn about MacLoggerDX before tomorrow's
> context :)
>  > > > Like how the Duplicates function works. Should get there :)
>  > >
>  > > Jeff Beiermann
>  > > WBØM
>  > > Nebraska
>  > >
>  >
>

Thanks, David. My problem was that I was not connected up to the rig. You need
some frequency or other data for the green dot to work. Thanks for the info
about the blue dot. Good to know. Yes, good point about the contest helper. Just
need a bigger screen now.

Bill
W8BC

--- In cab-converter@yahoogroups.com, David Kaplan <dhkaplan@...> wrote:
>
> Oh yes,
>
> The gray dot to the left of the green dot turns blue when you are
> connected to a DX Cluster.
>
> 73,
>
> David, WA1OUI
>
> On Nov 6, 2009, at 12:44 PM, w8bc wrote:
>
> Okay, humor me here Jeff. I can see the dupes in the contest helper
> (as Rick says). That works, but what is the little dot to the upper
> left of the call sign? Where exactly, what panel or screen are you
> seeing this dot in? Don't see any dot, green or otherwise. I thought I
> had read the manual. Obviously I am getting too old... or am too old.
> But humor me anyway. Thanks
>
> Bill
> W8BC
>
> --- In cab-converter@yahoogroups.com, "wb0m@" <wb0m@> wrote:
>  >
>  > Actually, it's pretty easy. Make a new log for the contest and just
>  > watch the little dot to the upper left of the call sign. If it's
>  > flashing green, it's a dupe. The info will be at far left. If you
>  > click on the green dot it will display on the QSO down in the log
>  > window. I believe for the Sweepstakes, it's a "work 'em only once"
>  > contest. Now, of course, you are still going to read the manual,
>  > right....? (hi). GL and hope to see you in the 'test. 73, Jeff/wb0m
>  >
>  >
>  >
>  >
>  > On Nov 6, 2009, at 9:44 AM, w8bc wrote:
>  >
>  > > Still much to learn about MacLoggerDX before tomorrow's context :)
>  > > Like how the Duplicates function works. Should get there :)
>  >
>  > Jeff Beiermann
>  > WBØM
>  > Nebraska
>  >
>