Date   
I think I have QSL labels set to print. I can find NO button to push to tell the labels to print?!

Email Service
 

Please tell me where I give that instruction to DXKeeper.

 

I have all the QSL sent box set to R for the labels I wish to print.

 

What do I do now?

 

Thanks

 

Jack ak7o

 

Sent from Mail for Windows 10

 

Re: Commander - ICOM 7300 - Waterfall problem

Rick Ellison
 

You need to change the baud rate on the radio and then open Commander and change it there..

 

73 Rick n2AMG

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Joseph Willis via Groups.Io
Sent: Saturday, September 14, 2019 7:15 PM
To: DXLab@groups.io
Subject: [DXLab] Commander - ICOM 7300 - Waterfall problem

 

Hello Dave and others - I have successfully connected DXLAB Commander to my computer from my Icom 7300 for everything except the Waterfall screen.  The documentation explains that I need to set the baud rate at 115200 (Silicon Labs CP210X) port.  However, when I try to bump up the speed from 9600 on the Config tab in Commander, I lose the connection, even though I previously set the port to 115200 on my computer !  Googling, I found this on the Silicon Labs web site:

"Icom radios use the version 6.xxx drivers.  Windows update has installed the Universal Windows Driver.  This drivers reports a maximum baud rate of 23800 when used with Microsoft .NET", but there is no fix. 

Have others been able to overcome this limitation with their 7300's ?

Thank you, 
VE2CY


Virus-free. www.avast.com

Commander - ICOM 7300 - Waterfall problem

Joseph Willis
 

Hello Dave and others - I have successfully connected DXLAB Commander to my computer from my Icom 7300 for everything except the Waterfall screen.  The documentation explains that I need to set the baud rate at 115200 (Silicon Labs CP210X) port.  However, when I try to bump up the speed from 9600 on the Config tab in Commander, I lose the connection, even though I previously set the port to 115200 on my computer !  Googling, I found this on the Silicon Labs web site:

"Icom radios use the version 6.xxx drivers.  Windows update has installed the Universal Windows Driver.  This drivers reports a maximum baud rate of 23800 when used with Microsoft .NET", but there is no fix. 

Have others been able to overcome this limitation with their 7300's ?

Thank you, 
VE2CY

Re: myQTH

Email Service
 

Simple thank you!
Jack AK7O

Sent from XFINITY Connect App



------ Original Message ------

From: Frank G4HBI via Groups.Io
To: DXLab@groups.io
Sent: September 14, 2019 at 11:56 AM
Subject: Re: [DXLab] myQTH

YOU WILL FIND THE ANSWER IN ADVANCED DOWN AT THE BOTTOM LEFT

Sorry about the caps
Frank G4HBI

 




--
Using Opera's mail client: http://www.opera.com/mail/

Re: myQTH

Frank G4HBI
 

YOU WILL FIND THE ANSWER IN ADVANCED DOWN AT THE BOTTOM LEFT

Sorry about the caps
Frank G4HBI

 




--
Using Opera's mail client: http://www.opera.com/mail/

myQTH

Email Service
 

Please tell me how to set EVERY log entry in my DXKeeper Log “myQTH” to DN40bq. For some reason that cell flashes every time I go back thru my log t find a QSO when I want to enter a QSL received.

 

Thank you

Jack ak7o

 

Sent from Mail for Windows 10

 

Re: Yaesu User-Defined Controls

Dave AA6YQ
 

+ AA6YQ comments below

Does anyone know whether any of the Commander user-defined controls
available on the DXLab website are usable with the new FTDX-101D or MP?

+ The FTDX-101 CAT instruction set is similar to those of the FTDX 3000, 5000, and 9000, but with one more digit in commands and responses that convey frequencies. If there's a user-defined control for the older radios that you'd like to try with your 101, I suggest that you check each CAT command in the control to see if the 101 will accept it.

73,

Dave, AA6YQ

Re: Log maintenance questions

Dave AA6YQ
 

+ AA6YQ comments below

 

Hello Dave and all....I currently have one log file with just over 9600 Qs in it spanning many years

of operation with both contest logs and normal operating Qs in it. I have held and used 3 different

callsigns through my ham career so the log has a mix of Qs using the 3 calls (all were in same QTH).

I also have a paper logbook which I am hoping to enter into this log manually in the near future to make

the log in DXLab more complete. Here are my questions:

 

1.       For the sake of chasing awards ie WAS WAC or DXCC  do all the contacts have to come from the same callsign

or can they be a mixed variety across the 3 calls I used?? Will ARRL allow this? (sorry, not a DXLab question)

 

2.       Is using the Auxiliary pane in the Log QSOs tab the easiest way to put the correct callsign against any Qs I manually

add to the log?? Is that the only place to add my used call as I input each old qso?

 

3.       If I added another column to my main Log QSOs screen to display the callsign I used, what would the adif name be

for that?? Operator?

 

Any help or suggestions are appreciated.

 

+ The same 3 questions were posted on September 9:

<
https://groups.io/g/DXLab/message/187580>

+ My response is here:

<
https://groups.io/g/DXLab/message/187581>

 

     73,

 

            Dave, AA6YQ

Yaesu User-Defined Controls

Jan C. Robbins
 

Does anyone know whether any of the Commander user-defined controls available on the DXLab website are usable with the new FTDX-101D or MP?  Any info much appreciated!  73 to all.

Jan N0JR

Log maintenance questions

Ted Boerkamp
 

Hello Dave and all....I currently have one log file with just over 9600 Qs in it spanning many years

of operation with both contest logs and normal operating Qs in it. I have held and used 3 different

callsigns through my ham career so the log has a mix of Qs using the 3 calls (all were in same QTH).

I also have a paper logbook which I am hoping to enter into this log manually in the near future to make

the log in DXLab more complete. Here are my questions:

 

1.       For the sake of chasing awards ie WAS WAC or DXCC  do all the contacts have to come from the same callsign

or can they be a mixed variety across the 3 calls I used?? Will ARRL allow this? (sorry, not a DXLab question)

 

2.       Is using the Auxiliary pane in the Log QSOs tab the easiest way to put the correct callsign against any Qs I manually

add to the log?? Is that the only place to add my used call as I input each old qso?

 

3.       If I added another column to my main Log QSOs screen to display the callsign I used, what would the adif name be

for that?? Operator?

 

Any help or suggestions are appreciated.

Thank you

73

 

Ted VE3SS

 

 

 

New SpotCollector

Mike NA5U <mike@...>
 

Dave et al,
The pre-release version of SpotCollector is running well. The whole suite is running like a well oiled clock 😊. Thanks for your help.
73,
Mike
NA5U

Re: Clublog QSO's missing

Carl - WC4H
 

It is possible that your QSO partner uploaded the QSO with some different information (mode, time, etc.)  causing him not to find a match.

I would not lose sleep over it, specially if you see the QSO when you search your clublog.

73.
Carl - WC4HG

Re: Thank you's & apologies

Carl - WC4H
 

No sweat Bill.  Glad that you were able to sort it out.

73.
Carl - WC4H

Re: Spot Collector and Bearing to DX

Steve
 

Thanks Dave !!!
Best 73, Steve KH6CT

Re: Spot Collector and Bearing to DX

Dave AA6YQ
 

+ AA6QY comments below

I think I once had Spot Collector set up to display the bearing from my QTH to the DX station. I selected the Azmiuth field and gave it the caption Bearing, but nothing displays. Am I having another Senior Moment ??

+ Take a look at

< https://www.dxlabsuite.com/dxlabwiki/SpotDatabaseDisplayAzimuth>

73,

Dave, AA6YQ

Spot Collector and Bearing to DX

Steve
 

I think I once had Spot Collector set up to display the bearing from my QTH to the DX station.  I selected the Azmiuth field and gave it the caption Bearing, but nothing displays.  Am I having another Senior Moment ??
Steve KH6CT

Re: Thank you's & apologies

Dave AA6YQ
 

+ AA6YQ comments below

On Thu, Sep 12, 2019 at 10:56 AM, Bill Stravinsky wrote:

What both of you needed to tell me was "hey dummy, there are separate panels for normal QSLing and Online Qsling", hi.  After I still didn't see that I tried
to justify the way I was doing things.  I won't even tell you how I was sending Lotw requests in the beginning then along came EQsl and ClubLog.  That was
2 or 3 years ago when I started to use DXL.  I wound up with my own system using only some of the features of DXL.
 
Anyway, late last night after replying to Dave's latest email, I looked hard at the process and saw what you both were trying to convey to me.  I had a small
amount of Lotw & EQsl requests that I had to edit so they would stop showing up when I hit "add requested" and now have a clean slate.  From now on I will
do it the way it was intended to be done.  Even though how I was accomplishing it was working it was still a jury rigged process on my part.  My next batch of
online QSL requests will be done how you tried to show me.
 
I did manage to figure out the process for making labels to attach to my cards for normal QSLing and tested it on regular printer paper.  It appears it should
work and I have a little over 300 cards that need labels.  I will be trying to use the program the way it was laid out to do, hi.
 
Thanks again and sorry I acted a little bull headed.  Maybe I'll become a DXL power user yet, hi.

+ There's no need to apologize, Bill. As you posted, there are often several ways to accomplish a task in DXLab, and it's a natural tendency to stick with the first one you find that works. However, it is also natural to point out a "better way" when one is available, and that what happened in this thread. 

+ To see all of the items recorded with each QSO, take a look at

<https://www.dxlabsuite.com/dxkeeper/Help/Items.htm>

       73,

             Dave, AA6YQ

Thank you's & apologies

Bill Stravinsky
 

On Wednesday, September 11, 2019, 11:00:08 PM EDT, Dave AA6YQ <aa6yq@...> wrote:


+ AA6YQ comments below

Its not just for Lotw.  I also upload to EQsl and ClubLog so every contact I either work casually or import from n1mm I have set to "Set select in imported QSO to Y".
I have to manually set select to Y but the majority of my operating is contesting so it gets set automatically when I import.  Then when I have several hundred Q's ready to upload to those 3 sources I just hit Sel to filter the log for all the Y's and do all the uploading.

+ Carl WC4H is right, Bill. After importing an ADIF file, you can

1. On the Main window's QSL tab,

1a. set the "QSL Via" panel to LoTW

1b. click the "Add Requested" button

1c. click the "Upload to LoTW" button

1d. set the "QSL Via" panel to eQSL.cc

1e. click the "Add Requested" button

1f. click the "Upload to eQSL.cc" button

2. On the Main window's "Check Progress" tab, click the "Club Log" panel's Upload button

+ The above procedure will upload your new QSOs to LoTW, eQSL, and Club Log.

+ Note that you can configure DXKeeper to automatically upload each newly-logged QSO to LoTW, eQSL, and Club Log.


Also, I use the QSL status setting to R to mark Q's to make QSL labels so your idea wouldn't work in my case.

+ The above procedure in no way interferes with DXKeeper's ability to print QSL labels.

        73,

                  Dave, AA6YQ



Carl and Dave,

What both of you needed to tell me was "hey dummy, there are separate panels for normal QSLing and Online Qsling", hi.  After I still didn't see that I tried
to justify the way I was doing things.  I won't even tell you how I was sending Lotw requests in the beginning then along came EQsl and ClubLog.  That was
2 or 3 years ago when I started to use DXL.  I wound up with my own system using only some of the features of DXL.

Anyway, late last night after replying to Dave's latest email, I looked hard at the process and saw what you both were trying to convey to me.  I had a small
amount of Lotw & EQsl requests that I had to edit so they would stop showing up when I hit "add requested" and now have a clean slate.  From now on I will
do it the way it was intended to be done.  Even though how I was accomplishing it was working it was still a jury rigged process on my part.  My next batch of
online QSL requests will be done how you tried to show me.

I did manage to figure out the process for making labels to attach to my cards for normal QSLing and tested it on regular printer paper.  It appears it should
work and I have a little over 300 cards that need labels.  I will be trying to use the program the way it was laid out to do, hi.

Thanks again and sorry I acted a little bull headed.  Maybe I'll become a DXL power user yet, hi.

Bill
K3WJV



Re: Clublog QSO's missing

Dave AA6YQ
 

+ AA6YQ comments below

snip<
In response to your answer .. I am lazy, so when I click upload to Clublog that's the end of it. I do not change QSO's on clublog because I have neither the time or the inclination to do so - DXKeeper is my "bible" and I do not need to change a QSO there because my CW is faultless - it's the others!

+ There's no need to manually change a QSO's Club Log status; I was just pointing out that this is a way that a QSO's Club Log status might be made incorrect.

73,

Dave, AA6YQ

Re: Clublog QSO's missing

David A92GE
 

I am always amazed by your prompt responses. I don't respond so fast in my day job !!  I'm sure DXKeep er is not your day job!
In response to your answer .. I am lazy, so when I click upload to Clublog that's the end of it. I do not change QSO's on clublog because I have neither the time or the inclination to do so - DXKeeper is my "bible" and I do not need to change a QSO there because my CW is faultless - it's the others!  No this is a mystery to me because the QSO was accurately logged  - mode - time - etc. (the usual errors)  so even if the QSO did not get uploaded the first time, I am clicking upload to clublog maybe once or twice a day and eventually it should have gone through or been flagged as dupe. As you suggest I will pass this thread of conversation to Clublog.


73
David
A92GE