Rather than assail the "60M chicken" here tying up bandwidth. The next
question what would be a BETTER FORUM to get the ARRL's attention and
change their mind set on their "60M EGG"?

All
 I would not suppose to speak for AA6YQ, but he has made his position on this clear several times in the past.
When ARRL recognizes 60M QSO's for DXCC , then DX LAB will follow suit ...and NOT until.
Rather than assail the "60M chicken" here tying up bandwidth. The next question  what would be a BETTER FORUM to get the ARRL's attention and change their mind set on their "60M EGG"?
Dave
NR1DX
On 11/19/2020 1:28 PM, F.R. Ashley wrote:

NR1DX and others...

Lately I have been trying to finish off 80 meter DXCC and stuck around
the 90 confirmed mark.�� I haven't been seeing much DX on 80M FT8 lately
so for the heck of it I went to 60M, and man, the band was jammed with
DX stations!� Now I know why I'm not seeing much on 80.

Back in January I was in St. Kitts and when I called CQ on 60 it sounded
like half of EU answered and I ran a string of EUs for a few hours.� I
know the V4 prefixed helped a lot but I was surprised at the amount of
interest on 60 meters seeing how none of the QSO's are good for any
awards. I had several direct QSL requests for a card.� Perhaps they have
worked everything on all the other bands and looking for a new thrill, hi.

73 Buddy WB4M

On 11/18/2020 9:39 PM, Dave / NR1DX wrote:

Was just curious.� I know you your position on ARRL and the band and
am not here to debate it

FT8 has put 60M on the map so to speak .You can work the "equivalent"
of DXCC on 60M FT8 5357 these days in a matter of months (I am at 125
after a year

When I started DXLab this morning, Spot Collector came up with a pop-up with lots of text and Enter your callsign. I couldn't read the text as it was mostly greyed out, but I entered my callsign anyhow.

+ That window is displayed on startup when SpotCollector attempts to retrieve your callsign from the Windows Registry and finds it empty. The text displayed in black font on a gray background is

SpotCollector relies on DXCC, eQSL, LoTW, and USAP databases that are updated at varying frequencies. DXLab's DXView application will notify you when database updates are available, and download them with a mouse click. If you haven't directed the DXLab Launcher to install DXView, consider doing so.

If you do not install DXView, up-to-date databases can be downloaded into SpotCollector's Databases folder from the Auxiliary Files column of the table in http://www.dxlabsuite.com/download.htm#AvailableReleases

(My excuse: I was doing this prior to my first coffee of the day).
When DXLac was all running (all modules except PF enabled) I noticed I was getting no spots.  Checking SC config, I found that all 4 spot sources had reset to the defaults and the auto boxes were not checked.
While it was relatively simple to retrieve and enter the credentials of my usual spot sources, I'd prefer not to have to repeat this. 
Any clues as to why this happened? 

+ Either you inadvertently cleared the the "Operator Callsign" setting in the upper right corner of the Configuration window's General tab, or Windows suffered a lost of information from the Windows Registry; check the Windows Event Logs to see if a hardware or software failure was recorded around the time this occurred.

     73,

            Dave, AA6YQ

The Spot collector email alarm is very helpful. When SC is restarted, for example after an update of databases, the alarm is no longer enabled, the enable box is no longer checked. Does anyone else experience this behavior? What can be done to keep the box checked?

+ If you're referring to the Enable box in the upper-left corner of the Configuration window's "Email alarm" tab, that setting is saved at shutdown and restored at startup like every other SpotCollector setting. SpotCollector only disables this option if an attempt to send a message fails, and the following retry also fails; when that happens, the words "Email notification disabled" appear in the Main window's title bar.

             73,

Hi Dave.

Create a script with these lines for 60m WAS:
delete <ReportsFolder>60m_WAS*.txt
filter Band = '60m'
Report us_states <ReportsFolder>60m_WAS.txt

Create one with these lines for 60m DXCC.

delete <ReportsFolder>60m_DXCC*.txt
filter Band = '60m'
Report DXCC <ReportsFolder>60m_DXCC.txt

Then just run the script from DXK.  They run pretty fast.
I have mine delete the previous report but you can skip that if you wish.

73.
Carl - WC4H

I noticed this apparent misbehavior recently thought it would be good to write it up. I love DX Lab Suite so much, thank you Dave!

Summary:
Commander fails to set mode when selected in mode panel following mode change made from radio.

Replication/Explanation:
Change mode from DATA-U1 to RTTY (To tune amplifier)

"Data-U1" looks like a typographical error. What mode is the radio in?

   Observe that Commander mode panel updates to reflect mode change to RTTY
Attempt to set mode to Data-Uw from commander mode panel.

"Data-Uw" looks like a typographical error. What mode are you selecting in Commander's Main window?

   Observe that Commander mode panel updates to indicate mode change to USB-D1
   Mode does not change on radio.

Workaround:
    Change to any other mode from Commander mode panel, then change to USB-D1 is successful.

Note: I was unable to replicate this with other mode combinations.