Ex: Re: [CabConverter] Late to the Party?


mguerin@...
 

Thanks Dave. I logged them in MLDX. Can I import an ADIF to RumLog, and then convert them?

Michael Guerin

On Mar 8, 2021, at 05:05, Dave W0DCX via groups.io <cwqrp73@...> wrote:

I tried using CC but found an easier way to submit Cabrillo logs from my Mac. I now use RUMLogNG to record my contest QSOs. It will then do a conversion to Cabrillo just fine. I successfully submitted a ARRL DX contest log just fine this way. My general logging program is Aether, so then I just export my RUMLog contest QSOs as an ADIF and then import into my main Aether log. I do it this way because the current Aether does not export to an acceptable Cabrillo file (hopefully future versions will fix this).

Hope this is useful,

Dave W0DCX





CAUTION: This email was not sent from a Cal Poly Pomona service. Exercise caution when clicking links or opening attachments. Please forward suspicious email to suspectemail@...<mailto:suspectemail@...>.


Dave W0DCX <cwqrp73@...>
 

Hi Michael,

I believe that you can import into RumLog though I have not done it yet. Give it a try! RumLog is free, I think.

My Mac OS is Big Sur and I found that using MLDX plus CC to be awkward enough that I chose to find another plan. RumLog seems to work okay.

Good Luck!

Dave

On Mar 8, 2021, at 8:33 AM, Michael W. Guerin <mguerin@...> wrote:

Thanks Dave. I logged them in MLDX. Can I import an ADIF to RumLog, and then convert them?

Michael Guerin
On Mar 8, 2021, at 05:05, Dave W0DCX via groups.io <cwqrp73@...> wrote:

I tried using CC but found an easier way to submit Cabrillo logs from my Mac. I now use RUMLogNG to record my contest QSOs. It will then do a conversion to Cabrillo just fine. I successfully submitted a ARRL DX contest log just fine this way. My general logging program is Aether, so then I just export my RUMLog contest QSOs as an ADIF and then import into my main Aether log. I do it this way because the current Aether does not export to an acceptable Cabrillo file (hopefully future versions will fix this).

Hope this is useful,

Dave W0DCX





CAUTION: This email was not sent from a Cal Poly Pomona service. Exercise caution when clicking links or opening attachments. Please forward suspicious email to suspectemail@...<mailto:suspectemail@...>.




Michael W. Guerin <mguerin@...>
 

THANKS ALL. Since I only had 40 contacts for the check log I decided to use ARRL’s utility (on the contest page) and just typed them in. For future contesting I’ll just get RUMLOG. Decades in and still learning, but thanks for the the support and suggestions. 73 W6MVT

Michael Guerin

On Mar 8, 2021, at 15:01, Dave W0DCX via groups.io <cwqrp73@...> wrote:

Hi Michael,

I believe that you can import into RumLog though I have not done it yet. Give it a try! RumLog is free, I think.

My Mac OS is Big Sur and I found that using MLDX plus CC to be awkward enough that I chose to find another plan. RumLog seems to work okay.

Good Luck!

Dave

On Mar 8, 2021, at 8:33 AM, Michael W. Guerin <mguerin@...> wrote:

Thanks Dave. I logged them in MLDX. Can I import an ADIF to RumLog, and then convert them?

Michael Guerin
On Mar 8, 2021, at 05:05, Dave W0DCX via groups.io <cwqrp73@...> wrote:
I tried using CC but found an easier way to submit Cabrillo logs from my Mac. I now use RUMLogNG to record my contest QSOs. It will then do a conversion to Cabrillo just fine. I successfully submitted a ARRL DX contest log just fine this way. My general logging program is Aether, so then I just export my RUMLog contest QSOs as an ADIF and then import into my main Aether log. I do it this way because the current Aether does not export to an acceptable Cabrillo file (hopefully future versions will fix this).

Hope this is useful,

Dave W0DCX





CAUTION: This email was not sent from a Cal Poly Pomona service. Exercise caution when clicking links or opening attachments. Please forward suspicious email to suspectemail@...<mailto:suspectemail@...>.








CAUTION: This email was not sent from a Cal Poly Pomona service. Exercise caution when clicking links or opening attachments. Please forward suspicious email to suspectemail@...<mailto:suspectemail@...>.