¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date

Re: Accessing Log on two computers - unexpected behavior

 

+ For what fraction of the current and prospective user community?
I don't know but given the increasing number of questions concerning
the matter I would suggest it is no longer a trivial fraction. In
addition, given the number of users that are known to use multiple
radios for contesting the percentage that would use the capability
if it was available is probably even higher.

+ Note that the DXLab's direct interoperation with WSJT-X supports multiple instances of WSJT-X running on multiple computers controlling multiple transceivers.
But that is limited to WSJTX direct and does not even support JT Alert
(which I find superior to "bare" WSJTX) not to mention other modes or
simple phone/CW operation from a second station (e.g., in a home
office or family room).

73,

... Joe, W4TV


On 6/18/2024 7:54 PM, Dave AA6YQ wrote:
+ AA6YQ comments below


This assumes that each of the transceivers are physically adjacent to
the computer (can be reached by the operator from the computer) and
that only one transceiver is in use at a time. Both assumptions are
seriously out of date.
+ For what fraction of the current and prospective user community?
+ Note that the DXLab's direct interoperation with WSJT-X supports multiple instances of WSJT-X running on multiple computers controlling multiple transceivers.
73,
Dave, AA6YQ


Re: How to change Fiji Islands to Conway Reef

 

Fiji Islands has not changed to Conway Reef.

Apparently you have a recent QSO with a 3D2 station ClubLog lists
as being on Conway (perhaps 3D2CCC).

How do I change designation in DX Keeper to Conway Reef?
Find the QSO in question and edit the DXCC box to 3D2-C (from 3D2-F).

73,

... Joe, W4TV

On 6/19/2024 9:10 AM, bcowan wrote:
I was trying to upload my ADIF file to Clublog and I received an error message that Fiji Islands is now Conway Reef.? How do I change designation in DX Keeper to Conway Reef?


Re: LOTW - unable to contact server

 

The slow startup could be waiting for TQSL to contact the mothership if he didn¡¯t stop that as you recommended previously.

Bruce - K5WBM

On Jun 19, 2024, at 9:23?AM, Dave AA6YQ via groups.io <aa6yq@...> wrote:

?With the Launcher configured to automatically start your DXLab applications, the recommended diagnostic test for "slow startup" is

1. reboot Windows into "Safe mode with networking"

2. note the time

3. start the Launcher

4. subtract the time noted at step 2 from the current time to determine "safe mode startup time"

Note that Commander and DXView may complain about non-existing serial ports, as Windows does not boot serial port device drivers when started in Safe mode

5. Reboot Windows normally

6. note the time

7. start the Launcher

8. subtract the time noted at step 6 from the current time to determine "normal startup time"

If "normal startup time" is significantly longer than "normal startup time", then one or more of the applications that Windows is configured to automatically start when booted normally is likely responsible; anti-malware applications are typically - but not always - the culprit. See



73,

Dave, AA6YQ






Re: Spotcollector Webserver Problem

 

Thanks Dave!!

I was being an idiot ... not adding the /spots to the URL!!

Working perfectly now!!!

Thanks for pointing me in the right direction!!!

73 de BARRY MURRELL ZS2EZ
KF26ta - Port Elizabeth, South Africa
EPC#0558?DMC#1690? 30MDG#4081
DXCC HONOR ROLL (334/340)
website : www.zs2ez.co.za

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Dave AA6YQ
Sent: Wednesday, June 19, 2024 4:38 PM
To: [email protected]
Subject: Re: [DXLab] Spotcollector Webserver Problem

+ AA6YQ comments below

I have just got my DX Cluster (ZS2EZ-3) back up and running after a couple
of weeks down - now have a Fixed IP on my Fibre Line (was using No-IP
service) and have a parked domain pointing to the IP address. Working well
with the cluster.

I am trying to set up an old laptop running Windows 10 to connect to the
cluster and provide a Web Interface via SpotCollector.. I used to have a
similar setup running once before , but now every time I try to connect to
the SpotCollector Webserver I get "GET is not supported"

I have the SpotCollector Web Server Port set to 8001, 25 spots per page and
a Refresh interval of 1 minute. I have port 8001 on my router forwarded to
the laptop running SpotCollector which is picking up spots from the Cluster
perfectly. I even tried connecting via 127.0.0.1:8001 on the laptop and got
the same "GET is not supported"

+ The message "GET is not supported" is not generated by SpotCollector.

+ Here, the IP address of the PC that hosts SpotCollector is
+ 192.168.88.238

+ From any other device connected to our home network, this URL accesses
SpotCollector's Web server:

192.168.88.238/spots

+ From a device with a small screen - like a smartphone - use

192.168.88.238/smallspots

I am at a loss - what am I doing wrong??

+ My guess is that you're not connecting to SpotCollector's web server.

73,

Dave, AA6YQ


Re: Accessing Log on two computers - unexpected behavior

 

+ AA6YQ comments below

I have no data on the fraction of the current and prospective user community that has or will have a physical layout that makes such capability useful.

So, in the absence of data, I'll tell a story....even though I am aware that the plural of "anecdote" is not "data."

My "shack" is a corner of the living room, so it's not as spread out as those with an entire room to themselves. At first the gear was close enough that using multiple computers wasn't needed. However, having everything crammed together was uncomfortable to operate. The ergonomics were terrible. So after more than 3 years of enduring it, I upgraded my operating desks and spread things out more. Now there are three places I can operate. At each I can move my chair under the desk, reach the keys and controls, have enough light, power plugs, etc. I can comfortably operate any of the three.

One of the three has the shack PC monitor directly in front. I can swivel the monitor to sort of face the second station, where I keep a second keyboard and mouse. Ergonomically it's not ideal - I have to twist my neck to see the monitor and it's a bit further away than in the primary position, so there's eye strain as well. Still, it's workable. The third position is at right angles, and puts the monitor to my 5 o'clock position. That is where I have started to use a laptop for logging.

+ An alternative would be to replace the laptop with a third keyboard, monitor, and mouse all connected to your shack PC via a "KVM" switch.

73,

Dave, AA6YQ


Re: Spotcollector Webserver Problem

 

+ AA6YQ comments below

I have just got my DX Cluster (ZS2EZ-3) back up and running after a couple of weeks down - now have a Fixed IP on my Fibre Line (was
using No-IP service) and have a parked domain pointing to the IP address. Working well with the cluster.

I am trying to set up an old laptop running Windows 10 to connect to the cluster and provide a Web Interface via SpotCollector.. I
used to have a similar setup running once before , but now every time I try to connect to the SpotCollector Webserver I get "GET is
not supported"

I have the SpotCollector Web Server Port set to 8001, 25 spots per page and a Refresh interval of 1 minute. I have port 8001 on my
router forwarded to the laptop running SpotCollector which is picking up spots from the Cluster perfectly. I even tried connecting
via 127.0.0.1:8001 on the laptop and got the same "GET is not supported"

+ The message "GET is not supported" is not generated by SpotCollector.

+ Here, the IP address of the PC that hosts SpotCollector is 192.168.88.238

+ From any other device connected to our home network, this URL accesses SpotCollector's Web server:

192.168.88.238/spots

+ From a device with a small screen - like a smartphone - use

192.168.88.238/smallspots

I am at a loss - what am I doing wrong??

+ My guess is that you're not connecting to SpotCollector's web server.

73,

Dave, AA6YQ


Re: How to change Fiji Islands to Conway Reef

 

+ AA6YQ comments below

I was trying to upload my ADIF file to Clublog and I received an error message that Fiji Islands is now Conway Reef. How do I change designation in DX Keeper to Conway Reef?

+ On the "Log QSOs" tab of DXKeeper's Main window

1. in the Log Page Display at the bottom of the tab, select the QSO whose DXCC entity is erroneously set to "Fiji Islands"

2. In the lower-right corner of the QSO panel at the top of the tab, change the entity selector from "Fiji Islands"

3. If the Edit button is visible just above the left top corner of the Log Page Display, click it

4. change the entity selector to "Conway Reef"

5. Click the Save button just above the left top corner of the Log Page Display

73,

Dave, AA6YQ


Re: LOTW - unable to contact server

 

With the Launcher configured to automatically start your DXLab applications, the recommended diagnostic test for "slow startup" is

1. reboot Windows into "Safe mode with networking"

2. note the time

3. start the Launcher

4. subtract the time noted at step 2 from the current time to determine "safe mode startup time"

Note that Commander and DXView may complain about non-existing serial ports, as Windows does not boot serial port device drivers when started in Safe mode

5. Reboot Windows normally

6. note the time

7. start the Launcher

8. subtract the time noted at step 6 from the current time to determine "normal startup time"

If "normal startup time" is significantly longer than "normal startup time", then one or more of the applications that Windows is configured to automatically start when booted normally is likely responsible; anti-malware applications are typically - but not always - the culprit. See



73,

Dave, AA6YQ


How to change Fiji Islands to Conway Reef

 

I was trying to upload my ADIF file to Clublog and I received an error message that Fiji Islands is now Conway Reef.? How do I change designation in DX Keeper to Conway Reef?


Spotcollector Webserver Problem

 

¿ªÔÆÌåÓý

Hi Dave

?

I have just got my DX Cluster (ZS2EZ-3) back up and running after a couple of weeks down ¨C now have a Fixed IP on my Fibre Line (was using No-IP service) and have a parked domain pointing to the IP address. Working well with the cluster.

?

I am trying to set up an old laptop running Windows 10 to connect to the cluster and provide a Web Interface via SpotCollector¡­. I used to have a similar setup running once before , but now every time I try to connect to the SpotCollector Webserver I get ¡°GET is not supported¡±

?

I have the SpotCollector Web Server Port set to 8001, 25 spots per page and a Refresh interval of 1 minute. I have port 8001 on my router forwarded to the laptop running SpotCollector which is picking up spots from the Cluster perfectly. I even tried connecting via 127.0.0.1:8001 on the laptop and got the same ¡°GET is not supported¡±

?

I am at a loss ¨C what am I doing wrong??

?

Thanks!

?

73 de BARRY MURRELL ZS2EZ

KF26ta - Port Elizabeth, South Africa

EPC#0558?DMC#1690? 30MDG#4081

DXCC HONOR ROLL (334/340)

website :

?


Re: LOTW - unable to contact server

 

No worries, Curt - I just wanted to understand because mine doesn't take nearly as long to start.

I'm also not starting everything at once. My auto-start list when Launcher kicks off is SpotCollector and DXView. That takes about 30 seconds. Then I start commander and DXKeeper from the buttons when I need them. Maybe another 20-30 seconds each, and they overlap so it's not 40-60.

My suggestion: Uncheck everything and start Launcher. How long does it take? Then check each app one at a time to see which one takes the longest. That might give you a clue as to what's going on - is it network? something else?

Another slightly-related tip, set SpotCollector's?max-DB size and age maximums to keep the database smaller. SpotCollector does slow down when its DB gets very large.

GL es 73!

-Brian n8wrl

On Wed, Jun 19, 2024 at 7:48?AM Curt Bowles via <curt.bowles=[email protected]> wrote:
Brian N8wrl...

My words but by bootup .. I mean launching DXLab complete suite of apps, including all the "Apps started After DXLab Apps" using? DX LA launcher. I'll try to be more careful with my word smithing !!! :-)

--
Curt Bowles
VE3ZN


Re: LOTW - unable to contact server

 

Yes... I noticed LoTW was down ... I said "I notice right away"..... again I will be more careful with my word smithing on this site! I guess I should have said;? I noticed LOTW was down right away!!! :-)?
--
Curt Bowles
VE3ZN


Re: LOTW - unable to contact server

 

Brian N8wrl...

My words but by bootup .. I mean launching DXLab complete suite of apps, including all the "Apps started After DXLab Apps" using? DX LA launcher. I'll try to be more careful with my word smithing !!! :-)

--
Curt Bowles
VE3ZN


Re: Accessing Log on two computers - unexpected behavior

 

I have no data on the fraction of the current and prospective user community that has or will have a physical layout that makes such capability useful.??

So, in the absence of data, I'll tell a story....even though I am aware that the plural of "anecdote" is not "data."

My "shack" is a corner of the living room, so it's not as spread out as those with an entire room to themselves.? At first the gear was close enough that using multiple computers wasn't needed.? However, having everything crammed together was uncomfortable to operate.? The ergonomics were terrible.? So after more than 3 years of enduring it, I upgraded my operating desks and spread things out more.? Now there are three places I can operate.? At each I can move my chair under the desk, reach the keys and controls, have enough light, power plugs, etc.? I can comfortably operate any of the three.??

One of the three has the shack PC monitor directly in front.? I can swivel the monitor to sort of face the second station, where I keep a second keyboard and mouse.? Ergonomically it's not ideal - I have to twist my neck to see the monitor and it's a bit further away than in the primary position, so there's eye strain as well.? Still, it's workable.? The third position is at right angles, and puts the monitor to my 5 o'clock position.? That is where I have started to use a laptop for logging.

Of course, the capability I'm using does have additional implications for remote use.? A rig control app coupled with DXKeeper and SpotCollector would make for a decent minimalist setup that would allow DXing from your hotel room.? That's not my principal motive, although I can see myself trying it out in the future and I am aware that more and more remote operations are becoming almost the norm.??

As a side note, last night I replicated the same steps as the prior evening, except I stopped SpotCollector and DXKeeper on the shack desktop and waited until OneDrive had completed syncing before starting them on the laptop.? I worked and logged a couple of QSOs on the laptop, shut down, waited for OneDrive to sync, then started SC and DXK on the desktop and the laptop QSOs were present as expected.? My failure to stop SC on the desktop appears to have been the cause of my unexpected behavior.??


73 de Chuck, WS1L



On Tue, Jun 18, 2024 at 7:54?PM Dave AA6YQ via <aa6yq=[email protected]> wrote:
+ AA6YQ comments below
This assumes that each of the transceivers are physically adjacent to
the computer (can be reached by the operator from the computer) and
that only one transceiver is in use at a time. Both assumptions are
seriously out of date.

+ For what fraction of the current and prospective user community?

+ Note that the DXLab's direct interoperation with WSJT-X supports multiple instances of WSJT-X running on multiple computers controlling multiple transceivers.

? ? ?73,

? ? ? ? Dave, AA6YQ


Re: Accessing Log on two computers - unexpected behavior

 

+ AA6YQ comments below
This assumes that each of the transceivers are physically adjacent to
the computer (can be reached by the operator from the computer) and
that only one transceiver is in use at a time. Both assumptions are
seriously out of date.

+ For what fraction of the current and prospective user community?

+ Note that the DXLab's direct interoperation with WSJT-X supports multiple instances of WSJT-X running on multiple computers controlling multiple transceivers.

? ? ?73,

? ? ? ? Dave, AA6YQ


Re: Accessing Log on two computers - unexpected behavior

 

+ Commander can be connected to up to 4 primary transceivers, and can
switch from one to another with a single mouse click. Thus logging
with multiple transceivers can be supported by one instance of DXLab
running on one computer.
This assumes that each of the transceivers are physically adjacent to
the computer (can be reached by the operator from the computer) and
that only one transceiver is in use at a time. Both assumptions are
seriously out of date.

73,

... Joe, W4TV

On 6/18/2024 7:17 PM, Dave AA6YQ wrote:
+ AA6YQ comments below




Then I also could not use my station position two at the same time as the
primary seat (same physical room, different radio/computer) with both
logging at the same time, each computer being current with the other.



Got it.? It's not something I do a lot (the DX must be heard on two bands,
not uncommon), just seeking the limits a little.

+ Commander can be connected to up to 4 primary transceivers, and can switch from one to another with a single mouse click. Thus logging with multiple transceivers can be supported by one instance of DXLab running on one computer.
73,
Dave, AA6YQ


Re: Spot Collector Issue

 

That did it Dave.? Thanks!

73,
Dick - W6TK

On Tue, Jun 18, 2024 at 4:19?PM Dave AA6YQ via <aa6yq=[email protected]> wrote:
+ AA6YQ comments below
?I have encountered an issue with Spot Collector in the last two days - it doesn't open or connect to the network and allow spots to come through.
?
? ?I have a note on the Spot Collector title bar indicating I need to check the Error Log.? In checking the Error File under Spot Collector --> Errorlog I? get the following message:

+ The errorlog indicates that your Spot Database has been corrupted. To recover from this,

1. terminate SpotCollector

2. delete the file C:\DXLab\SpotCollector\Databases\Spots.mdb

3. start SpotCollector

? ? ? 73,

? ? ? ? ? ? Dave, AA6YQ


Re: Spot Collector Issue

 

+ AA6YQ comments below
?I have encountered an issue with Spot Collector in the last two days - it doesn't open or connect to the network and allow spots to come through.
?
? ?I have a note on the Spot Collector title bar indicating I need to check the Error Log.? In checking the Error File under Spot Collector --> Errorlog I? get the following message:

+ The errorlog indicates that your Spot Database has been corrupted. To recover from this,

1. terminate SpotCollector

2. delete the file C:\DXLab\SpotCollector\Databases\Spots.mdb

3. start SpotCollector

? ? ? 73,

? ? ? ? ? ? Dave, AA6YQ


Re: Accessing Log on two computers - unexpected behavior

 

+ AA6YQ comments below

Then I also could not use my station position two at the same time as the primary seat (same physical room, different radio/computer) with both logging at the same time, each computer being current with the other.

Got it.? It's not something I do a lot (the DX must be heard on two bands, not uncommon), just seeking the limits a little.

+ Commander can be connected to up to 4 primary transceivers, and can switch from one to another with a single mouse click. Thus logging with multiple transceivers can be supported by one instance of DXLab running on one computer.

? ? ?73,

? ? ? ? ? Dave, AA6YQ


Spot Collector Issue

 

Hello Dave and all,
? ?I have encountered an issue with Spot Collector in the last two days - it doesn't open or connect to the network and allow spots to come through.

? ?I have a note on the Spot Collector title bar indicating I need to check the Error Log.? In checking the Error File under Spot Collector --> Errorlog I? get the following message:
? ? ? ?2024-06-18 13:21:16 ? ? > SpotCollector version 9.6.9
2024-06-18 13:21:16 ? ? > App.Path ? ? ? ? ?: C:\DXLab\SpotCollector
2024-06-18 13:21:16 ? ? > App.exe ? ? ? ? ? : SpotCollector
2024-06-18 13:21:16 ? ? > Module ? ? ? ? ? ?: C:\DXLab\SpotCollector\SpotCollector.exe
2024-06-18 13:21:16 ? ? > Operating System ?: Windows 10 Home (64-bit) build 22631
2024-06-18 13:21:16 ? ? > Locale ID ? ? ? ? : 1033 (0x409)
2024-06-18 13:21:16 ? ? > ANSI CodePage ? ? : 1252
2024-06-18 13:21:16 ? ? > OEM CodePage ? ? ?: 437
2024-06-18 13:21:16 ? ? > Country ? ? ? ? ? : United States
2024-06-18 13:21:16 ? ? > Language ? ? ? ? ?: English
2024-06-18 13:21:16 ? ? > DecimalSeparator ?: . <46><0>
2024-06-18 13:21:16 ? ? > ThousandSeparator : , <44><0>
2024-06-18 13:21:16 ? ? > DXLab Apps ? ? ? ?:
2024-06-18 13:21:16 ? ? > Monitors ? ? ? ? ?: 1
2024-06-18 13:21:16 ? ? > Monitor 1
2024-06-18 13:21:16 ? ? > ? ?width ? ? ? ? ?: 1920
2024-06-18 13:21:16 ? ? > ? ?height ? ? ? ? : 1080
2024-06-18 13:21:16 ? ? > ? ?dimensions ? ? : (0, 0)-(1920, 1080)
2024-06-18 13:21:16.429 > program error 3343 in module SpotDatabaseModule.OpenSpotDatabase: Unrecognized database format 'C:\DXLab\SpotCollector\Databases\Spots.mdb'.
2024-06-18 13:21:16.522 > program error 91 in module Config.DoPrune: Object variable or With block variable not set
2024-06-18 13:21:16.663 > program error 91 in module SpotDatabaseModule.UpdateSNRPredictions, theState = 1: Object variable or With block variable not set

? ?I don't know what to do to correct the Program errors 3343 and 91 as identified in the Error Log.? ?Any help to resolve the issue will be appreciated.? Thanks

? ?Been using DXLAb for quite a while and all its features - a great asset in operating and keeping track of awards, etc.? Thanks to Dave and the Team - your work and efforts are much appreciated!

73,
Dick - W6TK