Keyboard Shortcuts
Likes
- DXLab
- Messages
Search
Re: DXKeeper and LOTW
开云体育Not until the ARRL puts it back online.On 6/21/2024 6:22 PM, Chris--AJ8Q
wrote:
Now that things have (hopefully) settled down, does LOTW accept submissions from DXKeeper? I tried yesterday (6/20/2024) and it gave me back a failure. Is there somsthing new? |
Re: E-Mail Alert Notification Issue
+ AA6YQ comments below
I am trying to send e-mail alerts to myself using the setup in SpotCollector. The outgoing gmail server requires OAuth authentication. This is not available as an option in the setup window. Is there any way to get around this, or am I out of luck? + SpotCollector does not support OAuth authentication. ? ? ?73, ? ? ? ? ? ? Dave, AA6YQ |
Re: DXKeeper - abbreviated times
+ AA6YQ comments below
In the DXKeeeper pdf manual it says on page 10: + That's an inadvertent regression. I'll send you a corrected version later this evening ? ? ? ? 73, ? ? ? ? ? ? ?Dave, AA6YQ |
DXKeeper - abbreviated times
In the DXKeeeper pdf manual it says on page 10:
"In fields containing dates, the year must be 1930 or later, if you do not include time separators in the begin or end fields, DXKeeper will insert them appropriately" and says that if while manually entering a QSO with realtime optimised disabled I enter eg 1239 it will automatically change this to 12:39. It does not seem to, I have to manually type in the semi colon. Is this a bug or am I misreading. Thanks 73 Dave G3YMC |
Re: Sync DXLab files with Google Drive
Thanks Dave.? I will contact Google support.
toggle quoted message
Show quoted text
On 6/19/2024 5:25 PM, Dave AA6YQ via groups.io wrote:
# more AA6YQ comments below |
Re: FFMA report
# more AA6YQ comments below
+ With VUCC realtime award tracking for 6m enabled, this SQL filter will highlight active stations in grid squares in the contiguous 48 US States that are un-worked or worked-but-not-confirmed: >This filter will also "miss" VE1,VE2,VE3,VE7 and XE stations in # Thanks, Joe! #The corrected FFMA filter is ((dxccprefix='K') or (DXGRID in ('CN78', 'CN88', 'DM12', 'DM22', 'DM31', 'DM32', 'DM41', 'DM51', 'DM61', 'DM70', 'DM71', 'DL79', 'DL88', 'DL89', 'DL98', 'DL99', 'EL06', 'EL07', 'DL15', 'EN29', 'EN38', 'EN48', 'EN57', 'EN76', 'EN85', 'EN86', 'EN81', 'EN82', 'EN92', 'FN02', 'FN03', 'FN13', 'FN24', 'FN25', 'FN34', 'FN35', 'FN45', 'FN46', 'FN56', 'FN57', 'FN65', 'FN66', 'FN67'))) and (Band='6m') and (GridBandProg in ('U','W')) ? ? ? 73, ? ? ? ? ? ? Dave, AA6YQ |
Re: FFMA report
+ With VUCC realtime award tracking for 6m enabled, this SQL filter will highlight active stations in grid squares in the contiguous 48 US States that are un-worked or worked-but-not-confirmed: >This filter will also "miss" VE1,VE2,VE3,VE7 and XE stations in border grids that "count" for FFMA because the grid is, in part, located in the continental US. The "shared" border grids are: CN78, CN88, DM12, DM22, DM31, DM32, DM41, DM51, DM61, DM70, DM71, DL79, DL88, DL89, DL98, DL99, EL06, EL07, DL15, EN29, EN38, EN48, EN57, EN76, EN85, EN86, EN81, EN82, EN92, FN02, FN03, FN13, FN24, FN25, FN34, FN35, FN45, FN46, FN56, FN57, FN65, FN66, FN67 73, ... Joe, W4TV On 6/19/2024 5:35 PM, Dave AA6YQ wrote: + AA6YQ comments below+ FFMA is a "6m contiguous US grid squares only" subset of VUCC. Thus if you enable DXLab's VUCC realtime award tracking for 6m, SpotCollector will highlight active stations in needed 6m grid squares. |
Re: FFMA report
+ AA6YQ comments below
Come to think of it, it might be helpful if I had the option of showing the grids I haven't worked in the FFMA report, too + FFMA is a "6m contiguous US grid squares only" subset of VUCC. Thus if you enable DXLab's VUCC realtime award tracking for 6m, SpotCollector will highlight active stations in needed 6m grid squares. (dxccprefix='K') and (Band='6m') and (GridBandProg in ('U','W')) + See ? ? 73, ? ? ? ? ? ? ?Dave, AA6YQ |
Re: Sync DXLab files with Google Drive
# more AA6YQ comments below
Dave, I understand that you may not be familiar with Google Drive. Perhaps I should try to locate a group that is dedicated to Google Drive much the same way that this group is dedicated to DXLab. I think I have taken up too much bandwidth on this subject here. # I'm not, but others here may have relevant experience. # My advice is to contact Google support. If they need more information about the applications you're running, don't hesitate to provide them with my contact information. 73, Dave, AA6YQ |
Re: Sync DXLab files with Google Drive
开云体育
On 6/19/2024 3:45 PM, Dave AA6YQ via
groups.io wrote:
+ AA6YQ comments below I am having trouble creating a DXLab file Sync with Google Drive. I am getting a Google Drive error list for 3 files that I have been unable to correct. The troublesome files are: Translation.mdb and Overrides.mdb in DXView and Spots.mdb in SpotCollector. Looking in the DXLab files I see that there are duplicate files in DXView with the dupes having the same file name but with a (1) after the file name ie. Overrides.mdb with 528 KB and Overrides (1).mdb with 0 KB. Translation.mdb is similar. In SpotCollector, Spots.mdb is not duplicated with a (1) copy but will also not sync with Google Drive. I tried deleting one of the files that had a 0 size but it made no difference. I also reviewed the permissions for the files in Google Drive but again no joy. Hopefully someone on the reflector is also using Google Drive and has an idea how to correct this issue. Any help would be appreciated. + The only way those duplicate files - with a (1) appended to the file name - could come into existence is if you created them. ??? ??? **I am not aware that I created them.? I seldom dive into
the DXLab files.? As stated above, Spots.mdb never had a (1)
appended to its file name but it was flagged as an error along
with the other two with (1) appended.? ??? ??? **When Google Drive finishes syncing, if there are problems a window opens containing an Error list.? The error for all three items is "can't locate some files in the cloud" Google provides three choices to investigate the issue. "Open file", "Retry" and "learn more".? I used "Retry" after deleting the zero-length duplicate files with no effect. " Learn more" choice brings me to a help window entitled "Fix problems in Drive for desktop".? Under the heading "Fix error messages"? one of the errors listed is "can't locate some files in the cloud".? The advice is: ??? ? Changes can’t be synced because the file has been deleted or unshared with you in Drive. ??? *To sync changes, ask the owner to reshare the item with you. ??? *If the item has been deleted, remove it from the syncing folder and add it back.
None of the remedies seem to apply to my situation.?
+ I suggest that you terminate you DXLab applications, and then delete the zero-length duplicate files. + What is a "Google Drive error list"? If it's a list of error messages, please post those messages here; you'll have to type them in, as screenshots are not supported. ??? **See above. Dave, I understand that you may not be familiar with Google
Drive. Perhaps I should try to locate a group that is dedicated to
Google Drive much the same way that this group is dedicated to
DXLab.? I think I have taken up too much bandwidth on this subject
here.? 73, Dave, AA6YQ |
Re: LOTW - unable to contact server
+ AA6YQ comments below
The slow startup could be waiting for TQSL to contact the mothership if he didn't stop that as you recommended previously. + On startup, DXKeeper directs Windows to start TQSL with a command line argument that directs it to place "LoTW News" in the file LoTWNews.txt + in your DXKeeper folder, and then continues with its initialization. + Four times per second, an event fires that causes DXKeeper to check for the creation of the LoTWNews.txt file. If the file exists, DXKeeper displays its contents; otherwise, DXKeeper increments a counter. If that counter reaches 120 (after 30 seconds), DXKeeper informs you that TQSL is unable to contact LoTW, and stops checking for the creation of the LotWNews.txt file. + I don't know why those 120 checks for the existence of a file over the course of 30 seconds would prevent Windows from conveying a message from Pathfinder to DXKeeper, not do I understand why it would cause an observable slowdown in DXKeeper's startup. I see neither of those effects here, so it must be specific to particular versions of Windows and/or differences in operating environment. 73, Dave, AA6YQ |
Re: Sync DXLab files with Google Drive
+ AA6YQ comments below
I am having trouble creating a DXLab file Sync with Google Drive. I am getting a Google Drive error list for 3 files that I have been unable to correct. The troublesome files are: Translation.mdb and Overrides.mdb in DXView and Spots.mdb in SpotCollector. Looking in the DXLab files I see that there are duplicate files in DXView with the dupes having the same file name but with a (1) after the file name ie. Overrides.mdb with 528 KB and Overrides (1).mdb with 0 KB. Translation.mdb is similar. In SpotCollector, Spots.mdb is not duplicated with a (1) copy but will also not sync with Google Drive. I tried deleting one of the files that had a 0 size but it made no difference. I also reviewed the permissions for the files in Google Drive but again no joy. Hopefully someone on the reflector is also using Google Drive and has an idea how to correct this issue. Any help would be appreciated. + The only way those duplicate files - with a (1) appended to the file name - could come into existence is if you created them. + I suggest that you terminate you DXLab applications, and then delete the zero-length duplicate files. + What is a "Google Drive error list"? If it's a list of error messages, please post those messages here; you'll have to type them in, as screenshots are not supported. 73, Dave, AA6YQ |
Sync DXLab files with Google Drive
开云体育
I am having trouble creating a DXLab
file Sync with Google Drive. I am getting a Google Drive error
list
for 3 files that I have been unable to correct. The troublesome
files
are: Translation.mdb and Overrides.mdb in DXView and Spots.mdb in
SpotCollector. Looking in the DXLab files I see that there are
duplicate files in DXView with the dupes having the same file name
but with a (1) after the file name ie. Overrides.mdb with 528 KB
and
Overrides (1).mdb with 0 KB. Translation.mdb is similar. In
SpotCollector, Spots.mdb is not duplicated with a (1) copy but
will
also not sync with Google Drive. I tried deleting one of the files
that had a 0 size but it made no difference. I also reviewed the
permissions for the files in Google Drive but again no joy.
Hopefully someone on the reflector is also using Google Drive and
has
an idea how to correct this issue. Any help would be appreciated.
73...Bill...W1GY |
Re: Accessing Log on two computers - unexpected behavior
开云体育On 20/06/2024 1:51 am, Dave AA6YQ via
groups.io wrote:
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.? Agreed! These cloud services are file-share services designed for file sharing across multiple devices not for multi-client concurrent database sharing which is what some are trying to achieve using cloud-based sharing of an open DXKeeper log across devices. For the non-DBA users of the group this is part of an article I penned recently about file-replication cloud services. Sharing a database with multiple clients via a file-share service (like Dropbox and OneDrive) is a very bad idea. With a file-share service and say 2 clients (PCs) you can have potentially 3 versions of the database file in different states. Local PC copies and the remote (Cloud) copy. de Laurie VK3AMA (JTAlert author) |
Re: Accessing Log on two computers - unexpected behavior
+ AA6YQ comments below
+ 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. ?
+ That's an unsupported configuration. DXLab applications do not currently support broadcast UDP. ?
+ 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. + 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 |
Re: Accessing Log on two computers - unexpected behavior
开云体育On 6/19/2024 7:51 AM, Dave AA6YQ via
groups.io 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. Dave, If you're going to keep score +1 for being able to run multiples
of DXK at any time. Preface: 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 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: 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,
|
Re: Accessing Log on two computers - unexpected behavior
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 |
Re: Accessing Log on two computers - unexpected behavior
# 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 # 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 # 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 |