Date   

Re: DXKeeper 16.1.0 is available

Dave AA6YQ
 

+ AA6YQ comments below

Dave I have several contacts logged as Q65 mode in DXkeeper prior to your update. eQSL still does not accept them as is. eQSL say they will accept the QSO's as MFSK with submode Q65. Do these prior contacts need to be modified so they can be uploaded to eQSL? Or should I just wait for eQSL to update their approved mode list?

+ As far as I know, eQSL requires submodes to be submitted as modes; DXKeeper has been successfully submitting FT8 QSOs to eQSL with

<MODE:3>FT8

since the summer of 2017, despite the fact that ADIF represents FT8 as

<MODE:4>MFSK <SUBMODE:3>FT8

If eQSL has changed its policy, please point me at a statement of the new policy.

73,

Dave, AA6YQ


Re: Filtering SC for special callsigns by mode

Dave AA6YQ
 

I have been using the “Identifying Special Callsigns” feature (http://dxlabsuite.com/spotcollector/Help/ConfigurationSpecialCallsigns.htm) of SpotCollector with good success, but I wonder if there is some beneficial additional functionality available that I am missing.

I would like SC to display the callsigns of CWops members that I have yet to work on a given band, but only for the CW mode, in pursuit of CWops awards, along with any spots relevant to my DXCC or Challenge objectives without regard to band or mode.

Using the CWops roster as the Leaderboard special callsign list, I can display spots for all CWops members on unworked bands along with spots needed for DXCC or Challenge objectives, but the spot database display shows this for all modes and not just CW. So, in the case of CWops members, I end up seeing many spots for modes that are not of interest.

If I invoke the Mode filter and set it for CW, then SC displays only the needed entries for CW, which works fine for the CWops awards, but I will miss other desirable entries such as an ATNO on FT8.

The ideal solution would be to allow me to further filter the Leaderboard spot displays by mode so that it contributes only the CWops counters that I need to the display, in conjunction with the display of other spots I need for DXCC and Challenge goals regardless of mode.

Is there a way to do this in the existing program?

+ Yes. Assuming that the tag you've specified for CWops members in the "Special Callsign List" is

cwops

+ use this SQL expression

<NEEDFILTER> or ((TAGS like '*<cwops>*') and (MODE='CW'))

+ The necessary capabilities are described in

https://www.dxlabsuite.com/spotcollector/Help/SpotDatabase.htm#Filtering%20with%20SQL%20expressions

73,

Dave, AA6YQ


Re: WW 9.3.7 PSK output tones seem to be low freq

Joe Subich, W4TV
 

Jon,

sorry if I didn't make it clear that I was referring to the
transmit tones
Transmit and receive tones are the same in PSK##. You transmit
on the same "tone" you are receiving.

Again, where are the "decode lines" in WW (there up to three -
one for each decode window)? Which decode window is "active"
for transmit?

73,

... Joe, W4TV


On 2021-04-23 1:15 PM, Jon Baker wrote:
Thanks for responding Joe.
sorry if I didn't make it clear that I was referring to the
transmit tones


USA-CA award

Carlo - IK2RPE
 

For the USA-CA award that I am pursuing, is there a way/place where to indicate the already submitted, accepted, verified counties as iI do, for example for IOTA, WAS, WAZ. etc.?
Many thanks

Carlo  IK2RPE


Upgrade 16.1.0 failed

kdsipi@...
 



problems w Vs 16.1.0

Dennis, K2SX
 

Seems I have joined the problems with Version 16.1.0 club.  I updated my DXK file to Vs 16.1.0.  After a few minutes, it finally opened but to a blank log page.  The heading was “Vs 16.10 (no log opened) (K2SX).  I tried opening it using an older smaller log file (KM4FOC with only 16K QSOs) and it seemed to open OK.   My K2SX file has 290K QSOs.  Went back to try and open DXK with K2SX.mdb and got the “log contains more fields than expected.  Tis version is incapable of opening it.  Probably can likely be overcome by opening current version of DXK”.  I am also getting a note that “A new version of TQSL is available” which I acknowledged but did nothing with.  It seems like some others are having similar problem but I don’t see a fix for this yet.  Suggestions?

Dennis, K2SX


Re: WW 9.3.7 PSK output tones seem to be low freq

Jon Baker
 

Thanks for responding Joe.
sorry if I didn't make it clear that I was referring to the 
transmit tones


Re: WW 9.3.7 PSK output tones seem to be low freq

Joe Subich, W4TV
 

Is the PSK LF sounding tones normal for WW or am I missing
something ?
What tone have you selected in the WW waterfall? Look for the
"decode lines".

73,

... Joe, W4TV


On 2021-04-23 10:17 AM, Jon Baker wrote:
Started WW and selected PSK31.
noticed the tones coming out seemed low freq,  less than 400Hz,  as though LF hum present.
much different from previous operation as I recall.
Disconnected everything from the PC and the tones from the PC speaker were still Low freq
thought I might have an open ground etc.  checked all connections OK
Tone test  with the PC only sounded normal.
Started Multipsk for comparison and the PSK31  tones sounded clean and
in the  2k+ freq range  as expected.
Is the PSK LF sounding tones  normal for WW  or am I missing something ?
73
Stan  N1ZX


WW 9.3.7 PSK output tones seem to be low freq

Jon Baker
 

Started WW and selected PSK31.
noticed the tones coming out seemed low freq,  less than 400Hz,  as though LF hum present.
much different from previous operation as I recall.

Disconnected everything from the PC and the tones from the PC speaker were still Low freq
thought I might have an open ground etc.  checked all connections OK
Tone test  with the PC only sounded normal.

Started Multipsk for comparison and the PSK31  tones sounded clean and
in the  2k+ freq range  as expected.
Is the PSK LF sounding tones  normal for WW  or am I missing something ?

73
Stan  N1ZX


Re: Q65

Phil Cooper
 

Jim,

 

Have you opened TQSL recently? If you  do, it says there is a new configuration file.

Agree to the download, and all should be OK.

 

73 de Phil GU0SUP

 

 

-----Original Message-----
From: "Jim Miller, AB3CV" <jtmiller47@...>
Sent: Friday, 23 April, 2021 13:12
To: "DXLab@groups.io" <DXLab@groups.io>
Subject: [DXLab] Q65

Anyone know if TQSL and LOTW are now accepting Q65 now that the ADIF committee has acted?

73
Jim ab3cv 


Re: Q65

g4wjs
 

On 23/04/2021 13:12, Jim Miller, AB3CV wrote:
Anyone know if TQSL and LOTW are now accepting Q65 now that the ADIF committee has acted?

73

Jim ab3cv
Hi Jim,

seems fine after the latest tQSL configuration update.



--
73

Bill

G4WJS.


Q65

Jim Miller, AB3CV
 

Anyone know if TQSL and LOTW are now accepting Q65 now that the ADIF committee has acted?

73

Jim ab3cv 


Re: DX LAB 16.1.0 error

Dave Tucker Nu4N <dwtucker19@...>
 

I am also having DXK problems with the new version. Yesterday my computer locked up and had to reboot. Reboot was successful. But when I started DXK the program could not find my log file. I had backed up my log file a day ago. But it would not log. Said that too many lines (16) and would not reload. So I went back and uploaded the day before and it loaded. But I accidently closed DXK keeper. Well it could not my log file again. So I had to resort 2 days a goes restore. I cant shut down DXK without this problem happening ago.
DXK keeper stated to reload a earlier version which I dont have one.
Any help wud be appreciated.

--
73's de NU4N Dave


Re: DXKeeper 16.1.0 is available

Jay KA9CFD
 

Dave I have several contacts logged as Q65 mode in DXkeeper prior to your update. eQSL still does not accept them as is. eQSL say they will accept the QSO's as MFSK with submode Q65. Do these prior contacts need to be modified so they can be uploaded to eQSL? Or should I just wait for eQSL to update their approved mode list?

On another note, I noticed overnight that TQSL has updated their configuration file and now accepts Q65 without having to map it to DATA prior to uploading to LOTW. I probably need to filter my log for Q65 contacts and upload them again with the Q65 mode rather than DATA.

Thanks and 73, 
Jay KA9CFD


Filtering SC for special callsigns by mode

Tim K9WX
 

I have been using the “Identifying Special Callsigns” feature (http://dxlabsuite.com/spotcollector/Help/ConfigurationSpecialCallsigns.htm) of SpotCollector with good success, but I wonder if there is some beneficial additional functionality available that I am missing.

 

I would like SC to display the callsigns of CWops members that I have yet to work on a given band, but only for the CW mode, in pursuit of CWops awards, along with any spots relevant to my DXCC or Challenge objectives without regard to band or mode.

 

Using the CWops roster as the Leaderboard special callsign list, I can display spots for all CWops members on unworked bands along with spots needed for DXCC or Challenge objectives, but the spot database display shows this for all modes and not just CW.  So, in the case of CWops members, I end up seeing many spots for modes that are not of interest.

 

If I invoke the Mode filter and set it for CW, then SC displays only the needed entries for CW, which works fine for the CWops awards, but I will miss other desirable entries such as an ATNO on FT8.

 

The ideal solution would be to allow me to further filter the Leaderboard spot displays by mode so that it contributes only the CWops counters that I need to the display, in conjunction with the display of other spots I need for DXCC and Challenge goals regardless of mode.

 

Is there a way to do this in the existing program?

 

Tim K9WX


Dxcluster ON0DXK-5 cprrect adress

Roland Huysentruyt
 

Hello

Please note correct adress for ON0DXK-5.

on0dxk.dyndns.org  ( port 8000 ) 

Do not use anymore  193.191.136.222 .

ipadress  soon  no more static.

73

Roland ON6HH ,sysop ON0DXK-5


Re: DXKeeper 16.1.0 is available

Dave AA6YQ
 

+ AA6YQ comments below

here is the tail of my DXKeeper ErrorLog.txt:

2021-04-06 19:26:42.417 > program error 3050 in module DXLogModule.OpenLog, state = 15, Pathname = C:\Users\bill\Dropbox\Radio\DXLabs\DXKeeper\Shared databases\G4WJS.mdb: Could not lock file.
2021-04-06 23:06:10.049 > Common.Terminate: DXKeeper shutdown

+ This occurred while you were running the previous version of DXKeeper, 16.0.7.


2021-04-21 10:22:35.877 > program error 3024 in module DXLogModule.OpenLog, state = 14, Pathname = C:\Users\bill\Dropbox\Radio\DXLabs\DXKeeper\Shared databases\G4WJS.mdb: Could not find file 'C:\Users\bill\Dropbox\Radio\DXLabs\DXKeeper\Shared databases\G4WJS.mdb'.

+ State 14 in the "OpenLog" procedure is only reached if after expanding the Mode item capacity DXKeeper's attempt to copy or compact the log file failed. I have added instrumentation to the next version of DXKeeper that will record the exact location of the failure.


2021-04-21 10:31:58.313 > program error 3050 in module DXLogModule.OpenLog, state = 1, Pathname = C:\Users\bill\Dropbox\Radio\DXLabs\DXKeeper\Shared databases\G4WJS.mdb: Could not lock file.

+ That's your "standard" sporadic " Could not lock file" DropBox failure.


Nothing unusual happened between the 6th April and Today other than I started Launcher Today, saw an application update, processed it, then tried to start the Suite as I usually do.

Note the "Could not lock file" messages which seem to correlate with the "whatever problem is causing DropBox to not reliably store your log file" issue you cite. It seems to me, that other than causing the MDB file to be locked periodically, DropBox is doing nothing wrong as files can become locked for a number of reasons unrelated to the application that owns and manages the file, and applications may be able to wait and retry to avoid that becoming a problem. For sure it is not a "chronic" problem with DropBox.

+ DXKeeper does not exclusively open the current log file, as both DXView and SpotCollector require continuous "read only" access. Thus DropBox should only be impeded if it's trying to exclusively open your log file - which it should never do.

I don't see any error messages related to scripts failing

+ There are no scripts involved in this process.


the log file clearly was not recreated during the compaction process. I note again that apart from an error that the log file could not be found, no other error messages were shown. As far as I was concerned the log file simply disappeared.

+ DXKeeper does the following:

1. makes a copy of G4WJS.mdb and name that copy Uncompacted_G4WJS.mdb

2. deletes G4WJS.mdb

3. directs the Jet database engine to compact Uncompacted_G4WJS.mdb and put the compacted result in G4WJS.mdb

+ Thus a failure of step 3 would produce the result you report:

A. Uncompacted_G4WJS.mdb is present

B. G4WJS.mdb is absent.

+ My Google search seeking problematic behavior when the Jet Engine's CompactDatabase function is invoked on files hosted by DropBox yielded no results. The transient "lock errors" you have been encountering could be responsible.

73,

Dave, AA6YQ


Re: LotW Sync not Responding - Solved (I think)

Dave AA6YQ
 

+ AA6YQ comments below

Well, you could knock me over with a feather. I was one of the first 50 customers to own the WN-2. I have a thread here asking about problems with LoTW sync operations in DXK. While it was clearly not a DXL caused issue, it was elusive and I couldn't isolate the behavior. You sir, just hit this nail square on the head.

I can report that over the last couple of days I have been able to independently reproduce this behavior. The WN-2 software is the culprit. Now I can update DXK from LoTW any time I like. This is fantastic.

Now, if it were a *nix system I would isolate the conflict, but being Windows not so much. I owe Alan (WN) a phone call over another question, so I'll update him on this discover.

+ It would be great if this could be tracked down to the root cause and corrected. When downloading information from LoTW, DXKeeper uses a function called

URLDownloadToFile

+ provided by Microsoft's URLMON.dll component. Evidently the WaveNode application is interfering with the operation of this function.

73,

Dave, AA6YQ


Re: LotW Sync not Responding - Solved (I think)

Jon Gefaell
 

Well, you could knock me over with a feather. I was one of the first 50 customers to own the WN-2. I have a thread here asking about problems with LoTW sync operations in DXK. While it was clearly not a DXL caused issue, it was elusive and I couldn't isolate the behavior. You sir, just hit this nail square on the head.

I can report that over the last couple of days I have been able to independently reproduce this behavior. The WN-2 software is the culprit. Now I can update DXK from LoTW any time I like. This is fantastic.

Now, if it were a *nix system I would isolate the conflict, but being Windows not so much. I owe Alan (WN)  a phone call over another question, so I'll update him on this discover.

Thank you Hank, and always Dave as well! 


On Tue, Apr 20, 2021 at 05:16 PM, Dave AA6YQ wrote:

After many process starts and stops, I finally determined that running the WN-2 Ver. 3.62 software for my WaveNode RF meter (USB
comms to computer) directly correlated to the DXKeeper - LotW misbehavior. Software running - errors. Not running no errors.
Doesn't appear to matter whether the WaveNode hardware is powered or not.

+ I'm glad that you found the culprit, Hank! I've added it to "Applications that can Interfere with DXLab Applications" in


Re: DX LAB 16.1.0 error

Dave AA6YQ
 

+ AA6YQ comments below
   Second attempt to upgrade to 16.1.0 also fails after reboot.
1) DXK 16.0.7 was running after I reverted from first attempt.
2) created backup data base
3) shut down DX Lab and rebooted the PC ( I did not start any of the non- DXL things that I normally run )
4) started launcher
5) up graded to 16.1.0
6) started DXK
7) first popup "Existing fields were not successfully updated due to an error noted in the errorlog.txt file; the specified log can not be opened."
8) The errorlog.txt for the contains the seem error message noted but for the present time
9) the database file is present where it has always been ../documents/ham data/DXLAB/DXKeeper/Databases/K0VM.mdb
10) after Ok on the first popup I get a second 'unable to open databse c:\users\al\documents\ham data\dxlab\dxkeeper\databases\k0vm.mdb'
11) after ok on the second popup dxkeeper opens but log  is empty.
12) attempting then to open the log in DXK gives a third popup.. 'the  specified log contains more fields than expected; this version of ...'

+ OK. Please place your K0VM.mdb log file in a zip archive, attache the archive to an email message, and send the message to me via

aa6yq (at) ambersoft.com

        73,

              Dave, AA6YQ

3001 - 3020 of 203945