+ AA6YQ comments below

If you're going to keep score +1 for being able to run multiples of DXK at any time.

Preface:
My shack is a room built inside the (large) garage and it has two operating positions (each with it's own computer or sharing one).? I also can operate from a kitchen workstation or my 'office' upstairs.? Plus I operate remotely at times (not at home). Not operating from the shack is more comfortable at certain (COLD or HOT) seasons.? [And just for completeness, K4-K4 can happen too.]

Using the LAN, I can connect apps to the shack (either/both rigs) but a simple KVM switch is out of the question (too far away).? I have to remember to not run DXK when not active, so I can use any node.? While my preference is to keep apps (and MOST of the station) running, simply to avoid delay time of bringing them up (at least in the shack).? Even on my fastest computer, bringing up any database app (not just DXK) takes time (nature of the beast apparently).

All nodes are set to read from the same logbook file, living on the NAS (network drive) so all can update it as needed (only one active at any time).? (The NAS allows access when I'm not operating from home too.)

When I get an alert, I can go to the shack or operate from the nearest node (depending on my current activity or expectations of ease of contact, or seasonal comfort).? So being able to operate without concern for what other node/s are running DXK; would be a wanted feature.

+ With a NAS (or cloud storage), you need not terminate the DXKeeper and SpotCollector instances that you aren't using; simply direct DXKeeper to open a dummy log (so that it closes your actual log). Configure SpotCollector to automatically open the same log that DXKeeper has open. Using this approach, switching from one operating position to another should be quick.

?

-=-=-

A thought:
I may misuse or mix terms trying to explain this; please bear with me.

I have WSJT-X sending a broadcasts (254.0.0.1 address, not unicast 127.0.0.1) so it works with both JTAlert and/or GridTracker and/or SC (at the same time).?

+ That's an unsupported configuration. DXLab applications do not currently support broadcast UDP.

?

And/or, other logging apps.? (I'm in a transition state, mix and match, trying to evolve to one station system, else it's too complicated.)

Could it be made possible that one DXK node (the main shack computer) could act as a database server and each other node (running at the same time) are read only clients?? (Ditto the spot database, but we'll focus on logbook.)??

+ With software, pretty much anything is possible.

+ The question is whether implementing a requested enhancement a good use of time. Time spent on task A is time not spent on tasks B, C, and D. Thus the "opportunity cost" of task A is the delayed availability of the benefits that would have been generated if tasks B, C, and D had implemented instead of task A. As you can see in "Enhancement Logs" column of this table

+ there are *many* submitted enhancement requests that have yet to be implemented. I also have several infrastructure improvements in mind.

+ When considering an enhancement request, I consider the likely time required to implement it, the value it would generate, and the fraction of the user community that would benefit from that value. Assuming that all questions posted here have been answered and all reported defects have been repaired, I react immediately to enhancement requests that can be implemented quickly and generate significant value for must users. I decline idiosyncratic requests that would only benefit a small number of users.

+ To your question: years ago, I extended SpotCollector with a web server so that users could remotely monitor and control their Spot Database Display on any device capable of hosting a web browser:

+ DXKeeper could be extended in the same way, enabling remote access to your Log Page Display from any device capable of hosting a web browser. Enabling new QSOs to be logged from this web-based mechanism is also feasible. Given the existing Remote Desktop and File Server (Cloud or NAS) alternatives, however, my impression is that these capabilities would only be exploited by a handful of users, yielding a low ratio of benefit to cost.

? ? ?73,

? ? ? ? ? ? ?Dave, AA6YQ

开云体育

+ 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. 

Dave,

If you're going to keep score +1 for being able to run multiples of DXK at any time.

Preface:
My shack is a room built inside the (large) garage and it has two operating positions (each with it's own computer or sharing one).? I also can operate from a kitchen workstation or my 'office' upstairs.? Plus I operate remotely at times (not at home). Not operating from the shack is more comfortable at certain (COLD or HOT) seasons.? [And just for completeness, K4-K4 can happen too.]

Using the LAN, I can connect apps to the shack (either/both rigs) but a simple KVM switch is out of the question (too far away).? I have to remember to not run DXK when not active, so I can use any node.? While my preference is to keep apps (and MOST of the station) running, simply to avoid delay time of bringing them up (at least in the shack).? Even on my fastest computer, bringing up any database app (not just DXK) takes time (nature of the beast apparently).

All nodes are set to read from the same logbook file, living on the NAS (network drive) so all can update it as needed (only one active at any time).? (The NAS allows access when I'm not operating from home too.)

When I get an alert, I can go to the shack or operate from the nearest node (depending on my current activity or expectations of ease of contact, or seasonal comfort).? So being able to operate without concern for what other node/s are running DXK; would be a wanted feature.

-=-=-

A thought:
I may misuse or mix terms trying to explain this; please bear with me.

I have WSJT-X sending a broadcasts (254.0.0.1 address, not unicast 127.0.0.1) so it works with both JTAlert and/or GridTracker and/or SC (at the same time).? And/or, other logging apps.? (I'm in a transition state, mix and match, trying to evolve to one station system, else it's too complicated.)

Could it be made possible that one DXK node (the main shack computer) could act as a database server and each other node (running at the same time) are read only clients?? (Ditto the spot database, but we'll focus on logbook.)??

Then, any log entry made from any (client) node, any mode, would send a similar (WSJT style) broadcast to the server; which would log it into the one common logbook.? That broadcast would also tell the other (client) node/s "Hey, reload/update the logbook display, it's been updated" so each node displays log and spot (worked/needed) status correctly (everyone synched to the same page).

While I do not contest, if this could be done, it would appeal to that group as well (and the non-contest contest, Field Day).? Plus there is a fair amount of other activity based on HOA or other limitations; remote is popular; station sharing is real.

Comments:
There are also times that I operate both seats in the shack at the same time (different computer, bands and modes, i.e. a 6M opening while chasing HF DX); a server based model would more easily allow that too.??

Since WSJT-X doesn't require a rig control app, I can run it (same computer or not) while operating elsewhere, relying on the broadcast feature to update the log.? But that limits me to WSJT-X plus one (Commander managed) mode.

[And as pointed out, commander can only deal with one rig at any moment, so a second computer for other modes in those times, is the clear answer to that limitation.]

I have NO clue just how much effort that would be to allow mutli-point operations simultaneously, all synched; that's your arena.? Yep, I want it all hi hi and would urge your consideration of this.

Thank you for your help and rapid responses.

73,
Rick nk7i

On Wed, Jun 19, 2024 at 04:51 PM, Dave AA6YQ wrote:

+ 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.

Or log in N1MM and upload to DXK via N1MM-DXK gateway. Works with me on 2 seperate computers with N1MM and a third (small) computer which runs DX-Lab apps.

73

Aart PA3C

# more AA6YQ comments below

+ 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

# Contesting is not DXing or general operating. I have yet to encounter a DXer or general operator who makes simultaneous QSOs in SSB, CW, RTTY, or PSK on two different radios.

?

+ 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).

# The "second station" scenario can be accommodated with a Remote Desktop Application

https://www.dxlabsuite.com/dxlabwiki/RemoteControl

# or with a cloud storage application like OneDrive or GoogleDrive. While cloud storage applications may be problematic when attempting to switch from one PC to another immediately after logging a QSO, they are reliable when the switch is made between operating sessions.?

? ? 73,

? ? ? ? ? ?Dave, AA6YQ

+ 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

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?

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

Bruce - K5WBM

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

+ 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

+ 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

+ 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

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

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?

开云体育

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

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

+ 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

+ 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