Date   

Re: DX Keeper- Frequency Field

Dave AA6YQ
 

+ AA6YQ comments below

I realize you are absolutely correct about install and registry. I wonder how many at Microsoft have had nightmares about the registry design, It seems one of the weakest part of Windows. Perhaps there was no better way but many people have had many nightmares over registry problems.

+ Given its architectural heritage (a windowing application built on top of DOS) and Microsoft's policy of maintaining upward compatibility (so that applications like DXLab work correctly from one version of Windows to the next), some aspects of Windows are relatively fragile. This is one of them.

73,

Dave, AA6YQ


SpotCollector can not store spots when closing

3a2mw Franco Lucioni
 

Hi Dave and All,
time to time, when I terminate all DxLab Suite via Launcher, Spot Collector cannot close the program, and I get a label "No Spot Database specified; spots will not be collected". In the Title Bar appears "See Errorlog".
I'm not at all a computer guru, and I do not understand why it happens, so I send the Errorlog and the Error Label to Dave, hoping he can find the origin of the problem.
Thanks in advance
Franco 3A2MW


Re: DX Keeper- Frequency Field

Gilbert Baron W0MN
 

I realize you are absolutely correct about install and registry. I wonder how many at Microsoft have had nightmares about the registry design, It seems one of the weakest part of Windows. Perhaps there was no better way but many people have had many nightmares over registry problems.

Outlook Laptop Gil W0MN
Hierro candente, batir de repente
44.08226N 92.51265W EN34rb

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Friday, June 5, 2020 20:27
To: DXLab@groups.io
Subject: Re: [DXLab] DX Keeper- Frequency Field

+ AA6YQ comments below

I know you recommended against it but I removed DX Keeper and reinstalled it. That actually did fix the problem.

+ Since you don't actually know what the problem was, it's premature to claim that it's been corrected. At best, you can say that the symptoms have not re-appeared since you re-installed DXKeeper.

+ Uninstalling and Re-installing a DXLab application in the absence of error messages of the form "component X not found" is poor practice: doing so can destroy the evidence needed to identify the root cause of the problem at hand, and can corrupt the Windows Registry with respect to installation status in a manner that forces a decision between using a "Registry Cleaner" application or wiping the C: drive and re-installing Windows.

73,

Dave, AA6YQ









--
W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop


Re: DX Keeper- Frequency Field

Dave AA6YQ
 

+ AA6YQ comments below

I know you recommended against it but I removed DX Keeper and reinstalled it. That actually did fix the problem.

+ Since you don't actually know what the problem was, it's premature to claim that it's been corrected. At best, you can say that the symptoms have not re-appeared since you re-installed DXKeeper.

+ Uninstalling and Re-installing a DXLab application in the absence of error messages of the form "component X not found" is poor practice: doing so can destroy the evidence needed to identify the root cause of the problem at hand, and can corrupt the Windows Registry with respect to installation status in a manner that forces a decision between using a "Registry Cleaner" application or wiping the C: drive and re-installing Windows.

73,

Dave, AA6YQ


Re: DX Keeper- Frequency Field

Dave AA6YQ
 

+ AA6YQ comments below

1. what make and model transceiver are you using?
At first I was using an Icom 756 Pro 3. The problem continued even after I switched to an Anon 7000DLE

2. does Commander display your transceiver's frequency and mode when you make changes via the transceiver's front panel?
Yes

3. can you change your transceiver's frequency and mode using Commander's Main window?
Yes

4. what letters appear between the square brackets in the title bar of DXKeeper's Main window?
[QSL queue: 363 QSLs]

5. what version numbers appear in the title bars of Commander's and DXKeeper's Main window?
15.4.9

+ Thanks. What version number appears in the title bar of Commander's Main window?

73,

Dave, AA6YQ


Re: Commander Bandspread Spots

Dave AA6YQ
 

+ AA6YQ comments below

Most all the stations spotted in Bandspread are spotted from foreign countries.

How do I get it to show stations spotted from the USA?

+ On the Bandspread tab of SpotCollector's Configuration window, set the "Spot Filter" panel to "none".

73,

Dave, AA6YQ


Re: WSJTX, JTAlert, and DXKeeper Integration

JT Croteau <jt.tobit@...>
 

Thanks Joe, will give it a try. Not uploading to the sites but could
explain things on my laptop.

N1ESE

On Fri, Jun 5, 2020 at 6:47 PM Joe Subich, W4TV <lists@subich.com> wrote:


In JTAlert ...

Manage Settings -> Logging -> "Check QSO Log Record"

Increase the time delay ... particularly if you have JTAlert set
for DXKeeper to upload to eQSL and LotW. If your system is the
least bit slow, DXKeeper will not perform the look-up quickly
enough for the default "5 secs".

73,

... Joe, W4TV


On 2020-06-05 6:08 PM, JT Croteau wrote:
Not sure where the issue is with this.

WSJTX 2.2.0, JTAlert 2.16.6, all DXLab apps at current versions.

7 times out of 10, all QSOs are reported and logged fine.

However, sometimes, I get a JTAlert pop up, after clicking ok on
WSJT's log window, saying DXKeeper cannot confirm the QSO and it
wasn't logged. However, DXKeeper still logs it fine.

It all seems to work fine but it's a mere annoyance by having me
clicking on another box when this happens.

Thoughts?

Thanks
N1ESE




Re: WSJTX, JTAlert, and DXKeeper Integration

Joe Subich, W4TV
 

In JTAlert ...

Manage Settings -> Logging -> "Check QSO Log Record"

Increase the time delay ... particularly if you have JTAlert set
for DXKeeper to upload to eQSL and LotW. If your system is the
least bit slow, DXKeeper will not perform the look-up quickly
enough for the default "5 secs".

73,

... Joe, W4TV

On 2020-06-05 6:08 PM, JT Croteau wrote:
Not sure where the issue is with this.
WSJTX 2.2.0, JTAlert 2.16.6, all DXLab apps at current versions.
7 times out of 10, all QSOs are reported and logged fine.
However, sometimes, I get a JTAlert pop up, after clicking ok on
WSJT's log window, saying DXKeeper cannot confirm the QSO and it
wasn't logged. However, DXKeeper still logs it fine.
It all seems to work fine but it's a mere annoyance by having me
clicking on another box when this happens.
Thoughts?
Thanks
N1ESE


Re: Commander Bandspread Spots

w6de
 

The stations spotted in Bandspread are from SpotCollector. 

If you don’t see any US calls in SpotCollector, they won’t be in the Bandspread display either.  You’ll need to adjust the filters in SpotCollector to see more US calls in Bandspread.

 

What Bands have you enabled in SpotCollector “BAND”?  What Band are you looking at in Bandspread?  There won’t be very many US calls being spotted on 20 meters.  On the other hand you will see lots of US calls being spotted on 6 meters when the band is open.

 

73,

Dave, w6de

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of tgzuber
Sent: 05 June, 2020 20:01
To: DXLab@groups.io
Subject: [DXLab] Commander Bandspread Spots

 

Most all the stations spotted in Bandspread are spotted from foreign countries.

How do I get it to show stations spotted from the USA?

Tom

WN0DRC


WSJTX, JTAlert, and DXKeeper Integration

JT Croteau <jt.tobit@...>
 

Not sure where the issue is with this.

WSJTX 2.2.0, JTAlert 2.16.6, all DXLab apps at current versions.

7 times out of 10, all QSOs are reported and logged fine.

However, sometimes, I get a JTAlert pop up, after clicking ok on
WSJT's log window, saying DXKeeper cannot confirm the QSO and it
wasn't logged. However, DXKeeper still logs it fine.

It all seems to work fine but it's a mere annoyance by having me
clicking on another box when this happens.

Thoughts?

Thanks
N1ESE


Re: DX Keeper- Frequency Field

Garrett Gonella
 

I know you recommended against it but I removed DX Keeper and reinstalled it.  That actually did fix the problem.  This is the first time it has worked since I have installed it on this computer.  It used to work on the old computer.


Re: DX Keeper- Frequency Field

Garrett Gonella
 

1. what make and model transceiver are you using? 
At first I was using an Icom 756 Pro 3.  The problem continued even after I switched to an Anon 7000DLE

2. does Commander display your transceiver's frequency and mode when you make changes via the transceiver's front panel?
Yes

3. can you change your transceiver's frequency and mode using Commander's Main window?
Yes

4. what letters appear between the square brackets in the title bar of DXKeeper's Main window?
[QSL queue: 363 QSLs]

5. what version numbers appear in the title bars of Commander's and DXKeeper's Main window?
15.4.9


Commander Bandspread Spots

tgzuber
 

Most all the stations spotted in Bandspread are spotted from foreign countries.

How do I get it to show stations spotted from the USA?

Tom

WN0DRC


Re: FW: JT Alert & LOTW

k0is@...
 

Bill, thanks for your suggestion.  It looks like we got it taken care of by removing my LOTW password requirement from my TQSL Certificate as Dave, AA6YQ suggested.  Otherwise, yes, I was ready to just go with bulk downloads to LOTW.  Thanks again, Bill and 73.

 

Larry

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Bill Pence
Sent: Friday, June 5, 2020 6:00 AM
To: DXLab@groups.io
Subject: Re: [DXLab] FW: JT Alert & LOTW

 

If this only occurs for ft8 qso, then JT alerts is likely directing dxkeeper to upload each qso to lotw...

 

This is a dxkeeper setting in jtalerts settings ..

In jtalerts, Open settings -> logging ->dxkeeper and uncheck the upload options.

 

Then you can batch upload from dxkeeper.

 

On Fri, Jun 5, 2020, 12:31 AM <k0is@...> wrote:

 

I’m Larry, K0IS, from LeClaire, IA.  First licensed as WN0ODK, became WA0ODK, and in 1978 passed my extra and became K0IS.  Operate mostly CW, recently applied for my 5BDXCC all CW and have six meter WAS, both with no more than 100 watts in the shack.  So now I’ve decided to jump into the FT8 fray and I’m really enjoying it.  I’ve recently downloaded JT Alert to bring WSJT-X and DX Labs DX Keeper together.  I know my QSO’s are going to LOTW because after every FT8 QSO using WSJT-X when I “Log” the contact I get first of all a pair of script errors which I ignore for now, but a pop up requires me to sign in to LOTW with my password after every QSO.  This while the next station may be calling me already but I can’t see the screen because the pop up telling me to sign in to LOTW is blocking the view.  This has to stop, HI HI.  I imagine I’m not the first to have this issue and I’m pretty sure it’s a setting or configuration that needs changed or corrected but after much looking, still not seeing it. Still on the learning curve here.    73, Larry  K0IS

 

Sent from Mail for Windows 10

 


--

Larry A.


--

Larry A.


Re: DX Keeper- Frequency Field

Dave AA6YQ
 

+ AA6YQ comments below

On Fri, Jun 5, 2020 at 09:10 AM, Garrett Gonella wrote:

I need some help... I have tried uninstalling Commander and reinstalling it. I have cleared the registry and tried again, but my DX Keeper does not fill in the frequency field automatically when logging a contact.  I hope there is a simple fix.

+ Some questions:

1. what make and model transceiver are you using?

2. does Commander display your transceiver's frequency and mode when you make changes via the transceiver's front panel?

3. can you change your transceiver's frequency and mode using Commander's Main window?

4. what letters appear between the square brackets in the title bar of DXKeeper's Main window?

5. what version numbers appear in the title bars of Commander's and DXKeeper's Main window?

 

Note that uninstalling and re-installing a DXLab application is strongly discouraged; doing so rarely solves the problem at hand, but can create much worse problems.

         73,

               Dave, AA6YQ


Re: SOLVED - SpotCollector spot source window will not stay hidden

g4wjs
 

On 05/06/2020 15:57, iain macdonnell - N6ML wrote:
login: G4WJS
Hello Bill, this is GB7MBC in Morecambe, Lancashire
running DXSpider V1.57 build 251
Nodes: 13/418 Clr - Users: 232/4812 Clr Max: 299/6042 Clr - Uptime: 4 06:24
GB7MBC>
For SpotCollector to consider a DX Cluster source valid, the prompt
that it returns must contain your username (as configured in the Spot
Source). See https://www.dxlabsuite.com/spotcollector/Help/DXClusterInteraction.htm

73,

    ~iain / N6ML

Thank you Iain!

Clearly I should have RTFM :(

I guess something changed at that cluster node, maybe switched to DXSpider, I don't recall which flavour of DX Cluster node it was for the last few Years when it has worked FB.

73
Bill
G4WJS.


--
73

Bill

G4WJS.


DX Keeper- Frequency Field

Garrett Gonella
 

I need some help... I have tried uninstalling Commander and reinstalling it. I have cleared the registry and tried again, but my DX Keeper does not fill in the frequency field automatically when logging a contact.  I hope there is a simple fix.


Re: SpotCollector spot source window will not stay hidden

iain macdonnell - N6ML
 

On Fri, Jun 5, 2020 at 6:10 AM g4wjs <bill.8@classdesign.com> wrote:

On 05/06/2020 14:01, g4wjs wrote:

On 05/06/2020 13:59, g4wjs wrote:

It is my outgoing spot source and seems to be otherwise behaving normally.


I'll take that back, looking back at SpotCollector history I don't see any entries with that source as the "Network".

I have just disabled all other sources and can confirm spots are not being taken from this source, here's a session print:

This is the GB7MBC DXCluster system using DXSpider software

If you are getting echo and you don't want it, do: unset/echo

or (if you are a Microsoft telnet user) disable 'local echoing'.

+---------------------------------------------------------------------+

! Warning: Computer Misuse Act (1990) UK applies !

! This system may only be accessed by Radio Amateurs using their real !

! callsigns and in accordance with their jurisdiction's licensing !

! conditions. All connections to this system are recorded. !

+---------------------------------------------------------------------+





login: G4WJS
Hello Bill, this is GB7MBC in Morecambe, Lancashire
running DXSpider V1.57 build 251
Nodes: 13/418 Clr - Users: 232/4812 Clr Max: 299/6042 Clr - Uptime: 4 06:24
GB7MBC>
For SpotCollector to consider a DX Cluster source valid, the prompt
that it returns must contain your username (as configured in the Spot
Source). See https://www.dxlabsuite.com/spotcollector/Help/DXClusterInteraction.htm

73,

~iain / N6ML


Re: Attempt to connect to LoTW fails

Matt Foster
 

It started working again about an hour after I posted this.

--
73, Matt, N0EYE


Re: SpotCollector spot source window will not stay hidden

g4wjs
 

On 05/06/2020 14:01, g4wjs wrote:
On 05/06/2020 13:59, g4wjs wrote:
It is my outgoing spot source and seems to be otherwise behaving normally.

I'll take that back, looking back at SpotCollector history I don't see any entries with that source as the "Network".

I have just disabled all other sources and can confirm spots are not being taken from this source, here's a session print:

This is the GB7MBC DXCluster system using DXSpider software

If you are getting echo and you don't want it, do: unset/echo

or (if you are a Microsoft telnet user) disable 'local echoing'.

+---------------------------------------------------------------------+

!           Warning: Computer Misuse Act (1990) UK applies            !

! This system may only be accessed by Radio Amateurs using their real !

!  callsigns and in accordance with their jurisdiction's licensing    !

!      conditions. All connections to this system are recorded.       !

+---------------------------------------------------------------------+





login: G4WJS
Hello Bill, this is GB7MBC in Morecambe, Lancashire
running DXSpider V1.57 build 251
Nodes: 13/418 Clr - Users: 232/4812 Clr Max: 299/6042 Clr - Uptime: 4 06:24
GB7MBC>
DX de K7CF:       7005.0  JA4XW                                       1304Z
DX de F4HZR:      7144.0  DL3JJ/P      WCA DL-00240                   1304Z
DX de HF0WFF:    14134.0  SP5UUD/P     SPFF-1722 PGA-SU08             1305Z
DX de W6XI:      50060.9  W5EME/B      EM32><>DM42                    1305Z DM42
DX de PA2PKZ:    28015.0  PI75ZUT      CW                             1305Z
DX de K7CF:       7005.0  JR1CEP                                      1306Z
DX de LA7EIA:    28074.0  UA3DLL       JO59CR<ES>KO85                 1306Z
DX de M0KED:      7118.0  GB2DD        D Day SES                      1306Z
DX de YO3GSK:    28074.5  UR9QT        FT8                            1307Z KN34
DX de W6XI:      50061.5  W5EME/B      EM32<>DM42 FREQ CORR.          1307Z DM42

SpotCollector is also reconnecting periodically, I assume because it thinks it's not working.

My initial command is:

set/dxgrid<13>set/wwv<13>sh/dx<13>sh/wwv<13>

which is working on other sources.


--
73

Bill

G4WJS.

13921 - 13940 of 208100