Date   
Re: Spot Collector stopped working

K4PX K4PX
 

Hi Dave,
Well the spots are coming in as when I look at the Config/Sources the spots are all rolling in, but none show in the Spotcollector display.  I have made sure all filters are cleared.  It has worked just fine for 3 years now but suddenly stopped a few days ago without me changing anything.  Any ideas?
Thanks Dave.
Joe
K4PX

SWL report via Buro

d_ziolkowski
 

Hi Dave-

I have an SWL report received via BURO.

I want to sent reply via BURO. 

I was able to set up as a card, but when I set to ADIF to sent to Global QSL, it appears the SWL info in not in the ADIF file.

Is this possible to send as AdIF or limited to a printed Card?

Dan KC2STA

Re: Commander 14.5.3 is available

CSM\(r\) Gary Huber - AB9M
 

did you try config, general, reset ?


From: DXLab@groups.io <DXLab@groups.io> on behalf of f4gwg <jlbzh@...>
Sent: Saturday, March 28, 2020 3:28 AM
To: DXLab@groups.io <DXLab@groups.io>
Subject: Re: [DXLab] Commander 14.5.3 is available
 
a precision :
commander can see the mode change from the trx but won't update correctly the sdr uno
if i am on usb and switch to lsb it works  . if i am on lsb and switch to usb : no change.

bests 73 Jean-Luc

Re: Commander 14.5.3 is available

f4gwg
 

a precision :
commander can see the mode change from the trx but won't update correctly the sdr uno
if i am on usb and switch to lsb it works  . if i am on lsb and switch to usb : no change.

bests 73 Jean-Luc

Re: Commander 14.5.3 is available

f4gwg
 

Hello to all
a bug appeard with the new version
i use commander to send frequency and mode to sdr uno software via vitual com ports
  since new version this morning  the mode won't change correctly anymore on the sdruno  frequency still ok
i went back to 14.4 and works again now.

73 stay safe

Commander 14.5.3 is available

Dave AA6YQ
 

This release

- correctly specifies callsign text and background colors for display on Flex SmartSDR panadaptor (tnx to Rick WR0H)

- prevents an errorlog.txt entry from being generated by SpectrumModule.DisplaySpectrumData state 36

- after a band change with the Spectrum Display in Centered mode, updates the Spectrum Display's  Reference Level with reference to
the correct frequency (tnx to Mike K4PRO and Björn SM7IUN)

- when switching the primary transceiver from a Yaesu FT-736 to another radio, doesn't terminate Commander (tnx to Jim N8SIM)

- when switching the primary transceiver from a Yaesu FT-736 to another radio, waits 50 ms after sending the "stop CAT" command to
the FT-736 before closing the primary CAT port (tnx to Jim N8SIM)

- when controlling an Icom transceiver with Spectrum capabilities, doesn't expect an ACK/NAK response from the "set reference level"
or "set tracking mode" commands, because they may not be sent if "CI-V transceive" is enabled (tnx to Mike K4PRO and Björn SM7IUN)

- when controlling a Flex Signature radio, ensures that the S-meter is displayed above the Main window's VFO (tnx to Keith - AC9S)

- enables the Secondary CAT port to follow the uplink or downlink frequency when connected to SatPC32 (tnx to Joe W4WT)

- enables the Secondary CAT port to follow the uplink or downlink mode when connected to SatPC32 (tnx to Joe W4WT)

- updates the Configuration.htm documentation file


Notes

1. Update your firewall and anti-malware applications to consider this new version of Commander to be "safe"


2. If this upgrade doesn't work correctly, see the "After an Upgrade" section of
<http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>


3. After upgrading, to revert to the previous version of Commander, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>



Commander 14.5.3 is available via the DXLab Launcher and via

<http://www.dxlabsuite.com/download.htm>

73,

Dave, AA6YQ

Re: Warnings and Lock Up

wb6bee
 

Dave, 

I went to DX Keeper configuration , Callbook.      I unchecked "warn when callbook fails, etc.

Don

Re: K3 and Commander

Dave AA6YQ
 

+ AA6YQ comments below

The box is checked.

+ OK, so let's determine why your K3 doesn't work correctly with Interrogation enabled. Exactly what is it that doesn't work correctly?

73,

Dave, AA6YQ

Re: Spot Collector stopped working

Dave AA6YQ
 

+ AA6YQ comments below

Spot Collector has stopped working.

+ What is it that leads you to conclude that SpotCollector has stopped working?

+ Please review

<https://www.dxlabsuite.com/dxlabwiki/EmptyDatabase>

73,

Dave, AA6YQ

Re: Spot Collector stopped working

g4wjs
 

On 27/03/2020 20:15, K4PX K4PX wrote:
Clock is OK
Hi OM,

unless you are set to UTC, is your PC set to the correct time zone?



--
73

Bill

G4WJS.

QSOs submitted to LoTW but not accepted

Dave AA6YQ
 

On your behalf, DXKeeper uses the TQSL application to encrypt and submit your QSOs to LoTW. This is normally transparent, as DXKeeper won't attempt to submit a QSO that it knows TQSL would reject, e.g. because it doesn't specify a valid callsign or specifies an invalid propagation mode. However, as described in

<https://www.dxlabsuite.com/dxlabwiki/UploadLoTWDuplicates>

TQSL won't allow you to submit a QSO that it has already submitted. Earlier versions of TQSL referred to such QSOs as "duplicates", but to avoid confusion, the most recent version refers to them as "already submitted". During normal operation, DXKeeper's LoTW automation should not attempt to submit QSOs that have already been submitted, but two things can cause this to happen:

1. You have actual duplicate QSOs in your log (solution: remove the duplicate QSOs, as described in <https://www.dxlabsuite.com/dxlabwiki/RemovingDuplicates>)

2. An error occurred when you originally submitted the QSO to LoTW, so TQSL considers the QSO to have been submitted, but the QSO does not appear in your LoTW account, so you wish to re-submit it

For the second case, DXKeeper provides a means of overriding TQSL's "already submitted" detection, as described in the first article cited above. Several of you have employed this option over the years.

As described here by Greg K0GW, chair of the ARRL's LoTW Committee, LoTW was not operating correctly on March 23 and March 24:

<https://groups.arrl.org/g/ARRL-LoTW/message/32478>

Greg's post alludes to a different mechanism used by LoTW to reject submissions from TQSL in which the set of QSOs submitted is identical to a previous set of QSOs submitted. ARRL IT Manager Mike K1MK confirmed the existence of this mechanism in his response to Iain N6ML:

<https://groups.arrl.org/g/ARRL-LoTW/message/32490>

Mike acknowledges that LoTW's handling of this situation was itself defective: if an exception occurs during the processing of a set of QSOs received from TQSL, LoTW should not consider this set of QSOs to have been processed, and thus should not reject the same set of QSOs when they are subsequently submitted. A correction of this LoTW defect is underway.

To determine whether you have QSOs that you submitted to LoTW but were not accepted, do the following:

1. on the Main window's QSL tab,

1a. set the "QSL Via" panel to LotW

1b. click the "Sync LoTW QSOs" button

2. in the Filter panel at the bottom of the Main window's LoTW tab, click the LoTW button; this will filter the Log Page Display to contain all QSOs submitted to LoTW, but not accepted by LoTW

3. if the Log Page Display is empty, all of your submitted QSOs have been accepted, and no further action is required

4. If the Log Page Display is not empty, then

4a. on the "QSL Configuration" window's LoTW tab, check the "permit uploading of QSOs already uploaded to LoTW" box

4b. on the Main window's QSL tab, click the "Add All" button; this will populate the QSL Queue with the QSOs present in the Log Page Display (QSOs that were submitted, but not accepted)

4c. on the Main window's QSL tab, click the "Upload to LoTW" button; this will resubmit the QSOs that have not been accepted by LoTW

4d. check the LoTW Queue Status via < http://www.arrl.org/logbook-queue-status> to determine how long it will likely take for LoTW to process your submitted QSOs

4e. after an appropriate amount of time has passed, on the Main window's QSL tab, click the "Sync LoTW QSOs" button

4f. in the Filter panel at the bottom of the Main window's LoTW tab, click the LoTW button; if the Log Page Display contains QSOs, then please send me email via

aa6yq (at) ambersoft.com

so I can help you determine the appropriate corrective action.

73,

Dave, AA6YQ

Re: Spot Collector stopped working

K4PX K4PX
 

Clock is OK

Re: Recurring issue: awards recompute slows down to a crawl

Dave AA6YQ
 

+ AA6YQ comments below

Dave, I rebooted into safe mode and tested DXKeeper as a standalone (as I cannot get my normal configuration running as virtual serial ports are also disabled in safe mode). On logging a QSO, the recomputation is instantaneous. On deleting a QSO, the recomputation is very fast - less than a second. After rebooting back into the normal mode, I tested DXKeeper as a standalone - to compare apples with apples - and I got the same results as above. However, once I hook everything up together, the speed issue is is back.

+ That's hard evidence that an application automatically started when Windows is booted "normally" is responsible for the slowdown. The culprit is almost always an incompetent or incorrectly configured firewall or anti-malware application. You must configure these applications to consider your DXLab applications to be "safe". If you've already done that, then the applications in question are defective, and should be replaced with something that provides protection without preventing your DXLab applications from interoperating.

73,

Dave, AA6YQ

Re: Warnings and Lock Up

Dave AA6YQ
 

+ AA6YQ comments below

I spent about an hour putting all my programs back together on five monitors after a "Call Book Look Up error" appeared. The call was valid and QRZ brought it up, but the look up error notice locked up the five monitors and I could not find it. It was buried behind some other window on a different monitor than I had entered the call sign. By the time I found it, all the programs had minimized or moved off screen into space someplace.

I have now attempted to disable every "write over" or "call book Look up" error. I hope I found them all. It's Not because I don't like the notice or think its valuable, but because the error message locks up everything until the error is cleared and it appears where it wants to.

It would be nice if the error message appeared dead center of the window you were entering the data, not someplace else on the surface of five monitors.

+ DXKeeper does not display an error message whose text is "Call Book Look Up error"

+ The next time this message appears, please make a screen shot of that shows it, attach the screen shot to an email message, and send the message to me via

aa6yq (at) ambersoft.com

+ so that I can determine which application is displaying it.

73,

Dave, AA6YQ

Re: K3 and Commander

NK6A
 

The box is  checked.

Re: Recurring issue: awards recompute slows down to a crawl

Jan AE7U
 

Dave, I rebooted into safe mode and tested DXKeeper as a standalone (as I cannot get my normal configuration running as virtual serial ports are also disabled in safe mode). On logging a QSO, the recomputation is instantaneous.  On deleting a QSO, the recomputation is very fast - less than a second.   After rebooting back into the normal mode, I tested DXKeeper as a standalone - to compare apples with apples - and I got the same results as above.  However, once I hook everything up together, the speed issue is is back.

My basic setup is: TS590s -> COM3 (virtual port) -> COM1 (VSPE splitter) -> Commander (via DXLabsuite interface) -> WSJT-X <- JTAlert.

P.S. I also tried running without any ancillary programs e.g. SDRUno with additional instances of WSJT-X,  but it makes no difference to the speed issue.

73's, Jan, AE7U

Re: "Leading! " Filter

ND9G Mike
 

I wouldn't do that, which may cause doubling of everything in Club Log. I don't know the capabilities of Club Log for preventing duplicates. I think it would be fine and it would likely match, but that could also be a long process. I personally wouldn't chance it and would clean it up locally to get things the way I want them.

Here is the way I would handle it, assuming that the 19 you identified initially are the only ones that you've changed since the upload..

1. Start by making a backup of your log. (Don't skip this step)
2. Clear any filtering you have in place to have all 160k QSOs displayed on your log page display
3a. Using the Advanced Sorts, Filters, & Modifers window (Click Adv button on the Log Page Display)
3b. At the bottom in the Modify QSOs in Log Page Display set
  • Item Name to APP_DXKeeper_ClubLog
  • Item new value to Y
  • Click the Mod button to set this value to Y for all 160k QSO
4. On the log page display, check the box to display the Auxiliary panel
5a. Locate each of the 19 QSOs that you modified based on your feedback from Club Log's email.
5b. In the Auxiliary panel, set the Club field value to M and save the record

If you then run the query that I sent previously, you should only display the ones you have modified (19)

Now go into QSL config and make sure your Club Log configuration is setup (see: https://www.dxlabsuite.com/dxkeeper/Help/QSLConfiguration.htm#Club%20Log%20Tab)

Once that is done, go to the Check Progress tab of DXKeeper, and you can click the Upload button in the Club Log panel, it will upload only those 19 records to Club Log.

Now in the future, you can periodically click this button to upload a batch of records that will be any you've changed since the last time, or any new ones. There is no need for you to set the Club field manually, DXK will keep track of any that you've changed since it was uploaded before, including if you change the QSl status or sync with LotW.

Please take a look at this section of the manual related to Club Log uploads.



73,
Mike ND9G


On Fri, Mar 27, 2020 at 9:42 AM Pete Smith <n4zr@...> wrote:

Thank you for the fuller explanation, Mike.  As you may have guessed, I wrote an ADIF file from the Export tab, and uploaded it using ClubLog's process.  So I guess that fundamentally I need to do it all again from the Check Progress tab.

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 3/27/2020 9:48 AM, ND9G Mike wrote:
Pete,

As I mentioned previously, you don't need to do anything special. DX Keeper is built to handle these cases. If you upload to Club Log from the Check Progress tab of DX Keeper, it will mark every QSO uploaded to Club Log with a Y. Then if at any point you make a change to that QSO in DX Keeper, it will change it to an M. Any new QSOs will have no value in that field. When uploading using the Check Progress tab of DX Keeper, it will upload any QSO that is marked with something other than a Y or N (the N is a value that you can set manually if you don't want that QSO uploaded to Club Log at all. The field I'm referring to is the Club field in the Auxiliary panel of the Log QSOs tab.

This situation covers your initial upload and then any subsequent upload will only upload the batch that has never been uploaded or modified.

If you want to see how many QSOs would be uploaded by a subsequent upload from DX Keeper, run the following SQL query.
APP_DXKeeper_ClubLog NOT IN ('Y','N')

If you run that now, and get the entire 164,000 QSOs (check the title bar of DX Keeper to see how many records are with the filter), then DX Keeper has no indicator that you uploaded anything to Club Log. I would think this would be from you exporting an ADIF File and uploading it to Club Log independently. If you did this and none are marked as Y, then we'll want to address that first, then go back and set the 19 that you needed to edit to modified, so they can be uploaded in your next upload.


73,
Mike ND9G


On Fri, Mar 27, 2020 at 8:02 AM Pete Smith <n4zr@...> wrote:

First of all, "they" is Clublog support.  Sorry for not making that clearer. 

Dave, I'm not asking about QSO by QSO synchronizing, but about a one-time *export* of a few QSOs from my DXKeeper to Clublog.

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 3/27/2020 2:09 AM, Dave AA6YQ wrote:
+ AA6YQ comments below

But what about ones where the problem was nothing more than a portable suffix?  For example, I logged AH3C/KH5, when it should have been  AH3C/KH5K according to Clublog.

+ With respect to AH3C/KH5 vs  AH3C/KH5K, I'd be more inclined to see what the station's operator submitted as his or her "Station Callsign" when they submitted their QSOs to LoTW.

They told me just to change it in DXLog, but what if I want to upload a tiny ADIF with only the amended QSOs, rather than re-sending the whole 164,000?

+ Who is "they"?

Is there a way to do that in DXKeeper?

DXKeeper is intended to server as your primary logging application. It provides facilities for importing batches of QSOs  made with specialized logging applications (like N1MM for contest QSOs, or one optimized for county hunting). It does not provide the ability to synchronize QSO-by-QSO with other logging applications.

       73,

              Dave, AA6YQ




Re: "Leading! " Filter

Pete Smith
 

Thank you for the fuller explanation, Mike.  As you may have guessed, I wrote an ADIF file from the Export tab, and uploaded it using ClubLog's process.  So I guess that fundamentally I need to do it all again from the Check Progress tab.

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 3/27/2020 9:48 AM, ND9G Mike wrote:

Pete,

As I mentioned previously, you don't need to do anything special. DX Keeper is built to handle these cases. If you upload to Club Log from the Check Progress tab of DX Keeper, it will mark every QSO uploaded to Club Log with a Y. Then if at any point you make a change to that QSO in DX Keeper, it will change it to an M. Any new QSOs will have no value in that field. When uploading using the Check Progress tab of DX Keeper, it will upload any QSO that is marked with something other than a Y or N (the N is a value that you can set manually if you don't want that QSO uploaded to Club Log at all. The field I'm referring to is the Club field in the Auxiliary panel of the Log QSOs tab.

This situation covers your initial upload and then any subsequent upload will only upload the batch that has never been uploaded or modified.

If you want to see how many QSOs would be uploaded by a subsequent upload from DX Keeper, run the following SQL query.
APP_DXKeeper_ClubLog NOT IN ('Y','N')

If you run that now, and get the entire 164,000 QSOs (check the title bar of DX Keeper to see how many records are with the filter), then DX Keeper has no indicator that you uploaded anything to Club Log. I would think this would be from you exporting an ADIF File and uploading it to Club Log independently. If you did this and none are marked as Y, then we'll want to address that first, then go back and set the 19 that you needed to edit to modified, so they can be uploaded in your next upload.


73,
Mike ND9G


On Fri, Mar 27, 2020 at 8:02 AM Pete Smith <n4zr@...> wrote:

First of all, "they" is Clublog support.  Sorry for not making that clearer. 

Dave, I'm not asking about QSO by QSO synchronizing, but about a one-time *export* of a few QSOs from my DXKeeper to Clublog.

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 3/27/2020 2:09 AM, Dave AA6YQ wrote:
+ AA6YQ comments below

But what about ones where the problem was nothing more than a portable suffix?  For example, I logged AH3C/KH5, when it should have been  AH3C/KH5K according to Clublog.

+ With respect to AH3C/KH5 vs  AH3C/KH5K, I'd be more inclined to see what the station's operator submitted as his or her "Station Callsign" when they submitted their QSOs to LoTW.

They told me just to change it in DXLog, but what if I want to upload a tiny ADIF with only the amended QSOs, rather than re-sending the whole 164,000?

+ Who is "they"?

Is there a way to do that in DXKeeper?

DXKeeper is intended to server as your primary logging application. It provides facilities for importing batches of QSOs  made with specialized logging applications (like N1MM for contest QSOs, or one optimized for county hunting). It does not provide the ability to synchronize QSO-by-QSO with other logging applications.

       73,

              Dave, AA6YQ




Re: "Leading! " Filter

ND9G Mike
 

Pete,

As I mentioned previously, you don't need to do anything special. DX Keeper is built to handle these cases. If you upload to Club Log from the Check Progress tab of DX Keeper, it will mark every QSO uploaded to Club Log with a Y. Then if at any point you make a change to that QSO in DX Keeper, it will change it to an M. Any new QSOs will have no value in that field. When uploading using the Check Progress tab of DX Keeper, it will upload any QSO that is marked with something other than a Y or N (the N is a value that you can set manually if you don't want that QSO uploaded to Club Log at all. The field I'm referring to is the Club field in the Auxiliary panel of the Log QSOs tab.

This situation covers your initial upload and then any subsequent upload will only upload the batch that has never been uploaded or modified.

If you want to see how many QSOs would be uploaded by a subsequent upload from DX Keeper, run the following SQL query.
APP_DXKeeper_ClubLog NOT IN ('Y','N')

If you run that now, and get the entire 164,000 QSOs (check the title bar of DX Keeper to see how many records are with the filter), then DX Keeper has no indicator that you uploaded anything to Club Log. I would think this would be from you exporting an ADIF File and uploading it to Club Log independently. If you did this and none are marked as Y, then we'll want to address that first, then go back and set the 19 that you needed to edit to modified, so they can be uploaded in your next upload.


73,
Mike ND9G


On Fri, Mar 27, 2020 at 8:02 AM Pete Smith <n4zr@...> wrote:

First of all, "they" is Clublog support.  Sorry for not making that clearer. 

Dave, I'm not asking about QSO by QSO synchronizing, but about a one-time *export* of a few QSOs from my DXKeeper to Clublog.

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 3/27/2020 2:09 AM, Dave AA6YQ wrote:
+ AA6YQ comments below

But what about ones where the problem was nothing more than a portable suffix?  For example, I logged AH3C/KH5, when it should have been  AH3C/KH5K according to Clublog.

+ With respect to AH3C/KH5 vs  AH3C/KH5K, I'd be more inclined to see what the station's operator submitted as his or her "Station Callsign" when they submitted their QSOs to LoTW.

They told me just to change it in DXLog, but what if I want to upload a tiny ADIF with only the amended QSOs, rather than re-sending the whole 164,000?

+ Who is "they"?

Is there a way to do that in DXKeeper?

DXKeeper is intended to server as your primary logging application. It provides facilities for importing batches of QSOs  made with specialized logging applications (like N1MM for contest QSOs, or one optimized for county hunting). It does not provide the ability to synchronize QSO-by-QSO with other logging applications.

       73,

              Dave, AA6YQ




Re: Spot Collector stopped working

g4wjs
 

On 27/03/2020 13:01, K4PX K4PX wrote:
Spot Collector has stopped working.  Uninstalled and reinstalled but still not working.
Hi OM,

first thing to check is you PCs clock, did a DST adjustment get missed perhaps.



--
73

Bill

G4WJS.