Date   

Re: Can't log with Winwarbler

Dave AA6YQ
 

+ AA6YQ comments below

I need some setup hints. I am using Winwarbler for PSK but when I 'log' a contact, it does not appear in DxKeeper. I have followed the Winwarbler setup guidelines in the Wiki.

+ So that I can see what's going on, please do the following with DXKeeper running:

1. on the General tab of WinWarbler's Configuration window, check the "log debugging info" box

2. terminate WinWarbler

3. start WinWarbler

4. log a QSO via WinWarbler

5. on the General tab of WinWarbler's Configuration window, uncheck the "log debugging info" box

6. attach the errorlog.txt file from your WinWarbler folder to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ


Re: Feature Request - OQRS QSL Reminder

Dave AA6YQ
 

+ AA6YQ comments below

I just sent a QSL request using OQRS, and I think it would be helpful if I could set a calendar reminder to check on the status of my request in 30 - 45 days.

Would that be a function that could be incorporated into DXKeeper?

I know I can do a search (I just don't know the SQL function!) for OQRS QSL Requested and not received, but an automatic reminder, with the ability to snooze the reminder for an adjustable number of days, would be nice to have.

+ Whenever you like, you can review all requested but not-yet-received confirmations by clicking the "Card Aging" button in the lower-left corner of the Main window's "Check Progress" tab to generate a "QSL Aging" report

https://www.dxlabsuite.com/dxkeeper/Help/Progress.htm#Card%20Aging

73,

Dave, AA6YQ


Can't log with Winwarbler

Chip Swett
 

I need some setup hints.  I am using Winwarbler for PSK but when I 'log' a contact, it does not appear in DxKeeper.  I have followed the Winwarbler setup guidelines in the Wiki.  Thanks.


Re: Feature Request - OQRS QSL Reminder

Joe Subich, W4TV
 

I know I can do a search (I just don't know the SQL function!) for OQRS QSL Requested and not received,
Start with ...

QSLSDATE < DateAdd("d",-60,Now()) and QSL_Sent='Y' and
QSL_SENT_VIA = 'E' and not (QSL_RCVD in ('Y','S','V')
or APP_DXKEEPER_LotW_QSL_RCVD in ('Y','S','V')

This is a modification of my "needed QSLs" search ...

The "-60" sets a 60 day window, change it to -30 or -45
as you wish. QSL_Sent='Y' is probably redundant (given
QSLSDATE) but I include it anyway.

73,

... Joe, W4TV


On 2022-08-07 10:11 AM, Bob WB2NVR wrote:
Hi Dave -
I just sent a QSL request using OQRS, and I think it would be helpful if I could set a calendar reminder to check on the status of my request in 30 - 45 days.
Would that be a function that could be incorporated into DXKeeper?
I know I can do a search (I just don't know the SQL function!) for OQRS QSL Requested and not received, but an automatic reminder, with the ability to snooze the reminder for an adjustable number of days, would be nice to have.
Obviously not a high priority.
I haven't said it recently, so thanks for the best logging suite and support available at any price!
73,
Bob WB2NVR


Feature Request - OQRS QSL Reminder

Bob WB2NVR
 

Hi Dave - 

I just sent a QSL request using OQRS, and I think it would be helpful if I could set a calendar reminder to check on the status of my request in 30 - 45 days.

Would that be a function that could be incorporated into DXKeeper?

I know I can do a search (I just don't know the SQL function!) for OQRS QSL Requested and not received, but an automatic reminder, with the ability to snooze the reminder for an adjustable number of days, would be nice to have.

Obviously not a high priority.

I haven't said it recently, so thanks for the best logging suite and support available at any price!

73,
Bob WB2NVR


Re: WSJT-X Time Sync - Updated NTP Setup Instructional Guide (August 2022), by David Taylor.

Marshall, AA0FO
 

Thanks Peter.  The instruction manual does appear easier than previous version or maybe it appears clearer to me after the 2nd read.  I don't understand why "W32Time, by default, only contacts servers once a week"!  It sure would be nice if Microsoft would just incorporate NTP into Windows so we don't have to screw around with it.


Re: Lotw failure to update status of LotW QSOs when DXKeeper claims one QSO is "Already Uploaded"

ART W2NRA
 

Hi Joe,

I forgot to thank you. Thank you Dupe info.

73, Art W2NRA
CWOPS #1955

On Aug 5, 2022, at 4:12 PM, Joe Subich, W4TV <lists@...> wrote:


See: <www.dxlabsuite.com/dxlabwiki/RemovingDuplicates>

73,

... Joe, W4TV

On 2022-08-05 3:52 PM, ART W2NRA via groups.io wrote:
Hi Dave,
Your wrote:
+ The most common cause of this situation? You have one or more duplicate QSOs in your log, possibly from importing a file of QSOs that you had already imported. But let's not jump to conclusions; please filter the Log Page Display to show all QSOs with AA2IL. Is there more than one copy of your QSO on 20m CW on 2022-06-14 at 03:23:24Z ?
YOU ARE RIGHT! And it is probably multiple duplicate QSOs.
How do I fix that?
Which dups do I delete? Some have been uploaded. Or does it matter if I delete a QSO that has been uploaded and then upload the other QSO again?
Thank you!
73, Art W2NRA CWOPS #1955





Re: DXK/N1MM Gateway

Dave AA6YQ
 

+ AA6YQ comments below

The 12060 UDP port being used in DXKGW is hardcoded to that base address and cannot be changed to the best of my knowledge.

+ That's correct.

73,

Dave, AA6YQ


Re: Spotcollector Layout and Connect

Dave AA6YQ
 

+ AA6YQ comments below
While looking for the ERRORLOG.TXT file I got sidetracked and compared my files in the Spotcollector Databases folder to a recent backup. The backup had several more files so I overwrote the files in the Databases folder with the 'known good' files from the backup. I restarted Spotcollector and everything works.

+ Sounds like your spot database (spots.mdb) was corrupted, but I'd need to see your errorlog.txt file to be sure. This can be caused by SpotCollector not completing its shutdown procedure, or by a hardware failure; you might check the Windows event logs for signs of the latter.

The most notable omission from the folder was SPOTS.LDB and I assume that is where the layout resided.

+ Spots.ldb is used by the Microsoft Jet database engine to indicate the level of locking against access by other applications.

73,

Dave, AA6YQ


Re: New MYQTHID

k6xt
 

Problem solved after a fashion. Using a TQSL tbk restored the deleted Station Locations, then was able to LoTW upload.

Midnight Thursday got FCC email that I'd been successful despite all odds (<5%) getting our club station a 1x2. Better start buying lotto tickets.

W7NTA is history. I get to start this process all over. I'll try to do better this time. Tnx info Dave.
--
73 Art K6XT/K7OX


Re: DXK/N1MM Gateway

dxradio33
 

Jim, you can change the UDP base port in PstRotatorAz to something like 10000 then in N1MM+ you can change the UDP Rotor port to 10060 that should solve the issue.

 

The 12060 UDP port being used in DXKGW is hardcoded to that base address and cannot be changed to the best of my knowledge.

 

Joe K8FC

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Jim N7US
Sent: Saturday, August 06, 2022 13:01
To: DXLab Reflector (DXLab@groups.io) <dxlab@groups.io>
Subject: [DXLab] DXK/N1MM Gateway

 

I recently resumed using rotor control program PstRotatorAz including its SteppIR Controller window.

 

I just tried N1MM-DXKeeper Gateway, after not using it for a long time, and found it couldn’t connect to N1MM because PstRotatorAz is already using Radio Port 12060 to communicate with N1MM.

 

Is there a work-around?

 

73,  Jim N7US

 


DXK/N1MM Gateway

Jim N7US
 

I recently resumed using rotor control program PstRotatorAz including its SteppIR Controller window.

 

I just tried N1MM-DXKeeper Gateway, after not using it for a long time, and found it couldn’t connect to N1MM because PstRotatorAz is already using Radio Port 12060 to communicate with N1MM.

 

Is there a work-around?

 

73,  Jim N7US

 


Re: Spotcollector Layout and Connect

John Huffman
 

Dave -

While looking for the ERRORLOG.TXT file I got sidetracked and compared my files in the Spotcollector Databases folder to a recent backup.  The backup had several more files so I overwrote the files in the Databases folder with the 'known good' files from the backup.  I restarted Spotcollector and everything works.

The most notable omission from the folder was SPOTS.LDB and I assume that is where the layout resided.

73, John K1ESE

On Sat, Aug 6, 2022 at 10:54 AM Dave AA6YQ <aa6yq@...> wrote:
Is there an errrorlog.txt file in your SpotCollector folder?

If so, please attach it to an email message, and send the message to me via

aa6yq@... 

    73,

             Dave, AA6YQ 


Re: WSJT-X Time Sync - Updated NTP Setup Instructional Guide (August 2022), by David Taylor.

Peter Laws / N5UWY
 

On Sat, Aug 6, 2022 at 10:22 AM Mark Murray via groups.io
<markmu.Boeing747@...> wrote:

The often used NTP Setup Instructional Guide has just recently been updated by Mr. David Taylor.
Found at the below SatSignal website.

https://www.satsignal.eu/ntp/setup.html
Yes, yes, yes. GM8ARV's guide is the best. For goodness' sake, don't
pay for a time sync program when NTP (W3HCF's DARPA project) is free.
Windows' built-in time client got better from XP -> Vista -> 7 -> 10
but it's not as good as NTP - just follow the directions and never
worry about your time again.


--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!


Re: Farthest contact made

Dave AA6YQ
 

* more AA6YQ comments below

Yes, please, Dave

+ If some or all of your logged QSOs do not specify a DISTANCE item, DXKeeper can compute them for you en masse; if you'd like to do this, let me know and I'll show you how.

* See

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

* Be sure to backup your log before using the "Modify QSOs" panel.

73,

Dave, AA6YQ


WSJT-X Time Sync - Updated NTP Setup Instructional Guide (August 2022), by David Taylor.

Mark MM
 

The often used NTP Setup Instructional Guide has just recently been updated by Mr. David Taylor. 
Found at the below SatSignal website.  

https://www.satsignal.eu/ntp/setup.html
--

73 de Mark ..w2or..


Re: Farthest contact made

Dave AA6YQ
 

+ AA6YQ comments below
Ok…I checked the Details box to make the Details panel visible and looks like DIST is blank even though logs have grid squares and lat/long info.

+ Does the QSO in question specify an "Antenna Path" item?

+ Does the QSO specify a "my QTHID" that in turn specifies that latitude and longitude from which you made the QSO?

73,

Dave, AA6YQ


Re: Spotcollector Layout and Connect

Dave AA6YQ
 

Is there an errrorlog.txt file in your SpotCollector folder?

If so, please attach it to an email message, and send the message to me via

aa6yq@... 

    73,

             Dave, AA6YQ 


Re: Lotw failure to update status of LotW QSOs when DXKeeper claims one QSO is "Already Uploaded"

ART W2NRA
 

Thank you, Joe, it sounds good.  I found where the Gateway can be downloaded.  I’ll look into it. 

73, Art W2NRA
CWOPS OPS #1955

On Aug 6, 2022, at 9:39 AM, dxradio33 <k8fc@...> wrote:



Art, as a side note, if you are using N1MM+ to log the CWT you can also use N1MM DXKeeper Gateway to automatically log each CWT QSO as you work them.  I use this feature all the time and it eliminates me having to export the CWT file to ADIF and the subsequent import of said file into DXKeeper.

 

73’s

 

Joe, K8FC

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of ART W2NRA via groups.io
Sent: Friday, August 05, 2022 22:09
To: DXLab@groups.io
Subject: Re: [DXLab] Lotw failure to update status of LotW QSOs when DXKeeper claims one QSO is "Already Uploaded"

 

Hi Dave,

 

I had 157 dupes.  I take the CWOPS CWT contest QSOs, convert them to ADIF files, add the data in the right field to import to the DXKeeper adif file.  From there it’s easy to add data from the contest program and upload that data to DXKeeper.  I must have created one contest twice by mistake.  That’s a first in 5 years.  I also verify the total QSOs every week or two.  And since DXKeeper QSOs matched the number CWOPS QSOs I though everything was fine.

 

I’m curious, why doesn’t DXKeeper stop the duplicate QSOs when imported? 

 

There’s nothing difficult about the DXKeeper wiki.  It’s just so much to look thru, so I wind up reading sections over and over, loosing my place, going back, forgetting what I read and where I read it.  It’s me, not you.

73, Art W2NRA

CWOPS #1955



On Aug 5, 2022, at 7:33 PM, Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

That worked great! All 74,492 QSOs since 1979 are still there and so are my 36,916 CWOPS QSOs.

+ Good! How many duplicates were removed?

FTR I get lost in the DXLab wiki. I have to keep reading it over and over. 

+ If you come across a section that you find difficult to understand, please point it out so that I can improve it.

     73,

            Dave, AA6YQ

 


Re: Lotw failure to update status of LotW QSOs when DXKeeper claims one QSO is "Already Uploaded"

dxradio33
 

Art, as a side note, if you are using N1MM+ to log the CWT you can also use N1MM DXKeeper Gateway to automatically log each CWT QSO as you work them.  I use this feature all the time and it eliminates me having to export the CWT file to ADIF and the subsequent import of said file into DXKeeper.

 

73’s

 

Joe, K8FC

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of ART W2NRA via groups.io
Sent: Friday, August 05, 2022 22:09
To: DXLab@groups.io
Subject: Re: [DXLab] Lotw failure to update status of LotW QSOs when DXKeeper claims one QSO is "Already Uploaded"

 

Hi Dave,

 

I had 157 dupes.  I take the CWOPS CWT contest QSOs, convert them to ADIF files, add the data in the right field to import to the DXKeeper adif file.  From there it’s easy to add data from the contest program and upload that data to DXKeeper.  I must have created one contest twice by mistake.  That’s a first in 5 years.  I also verify the total QSOs every week or two.  And since DXKeeper QSOs matched the number CWOPS QSOs I though everything was fine.

 

I’m curious, why doesn’t DXKeeper stop the duplicate QSOs when imported? 

 

There’s nothing difficult about the DXKeeper wiki.  It’s just so much to look thru, so I wind up reading sections over and over, loosing my place, going back, forgetting what I read and where I read it.  It’s me, not you.

73, Art W2NRA

CWOPS #1955



On Aug 5, 2022, at 7:33 PM, Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

That worked great! All 74,492 QSOs since 1979 are still there and so are my 36,916 CWOPS QSOs.

+ Good! How many duplicates were removed?

FTR I get lost in the DXLab wiki. I have to keep reading it over and over. 

+ If you come across a section that you find difficult to understand, please point it out so that I can improve it.

     73,

            Dave, AA6YQ

 

1561 - 1580 of 211088