Date   

Re: DXKeeper Capture and WSJT-X

Igor ananyev
 

+ AA6YQ comments below

But in that case is there a way to quickly check the previous QSO”s?

+ Yes. If you're using the direct interoperation between DXLab and WSJT-X, then if you check the Lookup box in the WSJT-X panel on the "Spot Sources" tab of SpotCollector's Configuration window, double-clicking a callsign in WSJT-X will result in DXKeeper displaying previous QSOs with that callsign. See step 4.e in the "Configuring SpotCollector" section of

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

73,

Dave, AA6YQ



Thank you!
I"ll test it at home.
73, Igor


Re: DXKeeper Capture and WSJT-X

Dave AA6YQ
 

+ AA6YQ comments below

But in that case is there a way to quickly check the previous QSO”s?

+ Yes. If you're using the direct interoperation between DXLab and WSJT-X, then if you check the Lookup box in the WSJT-X panel on the "Spot Sources" tab of SpotCollector's Configuration window, double-clicking a callsign in WSJT-X will result in DXKeeper displaying previous QSOs with that callsign. See step 4.e in the "Configuring SpotCollector" section of

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

73,

Dave, AA6YQ


Re: Windows 10 Port (com & LPT) vanished

Bruce N7XGR
 

Mike,  Did you unplug the USB cable and plug it back in with the 991 turned on?
Was there the usual Windoze beeps to indicate this unplug to plug back in?

Bruce  N7XGR


On Wed, Jul 21, 2021 at 12:50 AM Michael E Wilson Sr <ke5wct@...> wrote:
When I checked the update history, the last MS update was last week on the 14th. The problem started after 10pm locat (0300Z) on the 18th . I will be back on the phone to ACER in the morning. not looking forward to talking to support tech's all day! 
But that is easier and less expensive than a replacement.



On Tue, Jul 20, 2021 at 10:19 PM Ed W2LCQ via groups.io <w2lcq=yahoo.com@groups.io> wrote:
In the past two weeks Windows 10 offered me 2 updates which I accepted and downloaded and installed. I’ve had no problems. Is it possible assuming you made or did not make  those updates and afterward your problems occurred? I have a Dell Latitude 7840 machine 3 years old with 16 MB RAM. I use DXL with WSJT-X and N1MM+

73, de Ed Jones W2LCQ

Frankford Radio Club
BUG CWops SKCC FISTS LICWC QCWA


On Jul 20, 2021, at 9:16 PM, Michael E Wilson Sr <ke5wct@...> wrote:

Don's know where to put this issue - In involves Windows to totally removing the Port (com & LPT) setting within Device Manager. No Matter what is done to the PC the Device Manager "Port (COM & LPT)" remains gone.

Chain of events. Sunday Evening I fired up the FT-991A along with wsjt-x and JTAlert. I worked a couple of station, but was tired so shup the radio down, then shut down the PC, same order of events as always, Then went to bed.
Monday, after working at the PC most of the day (working with HRDLog that get qsl's caught up. That evening I fired up the radio and wsjt-x/JTAlert, bam big red flag that the wsjt-x would not connect to the radio. Checked the setting and found that
for the radio port there was on USB listed (no com ports of any kind). No mater what I tried, there was no way to connect to the radio. I check into the PC, and could not find any com ports in device manager. I gave up and went to bed. Today I spent several hours trying to figure out what happened and how to fix it. Found nothing. This after noon, I called ACER (PC is a 6 week on ACER Aspire under 3 year warranty). Tech support had never heard any any events like what I presented. There initial solution after other attempts failed, was to use the PC reset function and reset the PC back to the original factory Windows 10 install as it appeared what I bought it. That only took about 40 minutes. But those 40 mins just to al my total frustration, since the problem remained.

Since this is obviously a Windows problem, thought it would throw it out to the world and see if I could catch me a very big Window 10 SME (Subject Matter Enthusiast). I would think that there has to be at least one other unornate OLD man out there that has run into this problem and has the magic solution!

Any takers?

Very grateful for  any assistance
73 and have a Great DX day.

de KE5WCT 
Mike Wilson
--
Mike
KE5WCT



--
73 de KE5WCT
Mike Wilson

--
Mike
KE5WCT


Re: DXKeeper Capture and WSJT-X

Igor ananyev
 

 

 

+ AA6YQ comments below

I’m newby with FT8 mode.
I use full DXLab and WSJT-X.
When I click callsign on WSJT pane, the one does appear at the DXVieu,
but does not appear at the Capture pane. Is it normal?

+ Yes. When you're using WSJT-X to make QSOs in a K1JT mode like FT8, WSJT-X takes the place of the Capture window. A similar thing happens when you use WInWarbler to make QSOs in PSK, RTTY, CW, or SSB.

        73,

               Dave, AA6YQ

 

 

Thank you, Dave!

But in that case is there a way to quickly check the previous QSO”s?

 

73, Igor, UC6N

_._,_._,_



Re: Windows 10 Port (com & LPT) vanished

Michael E Wilson Sr <ke5wct@...>
 

When I checked the update history, the last MS update was last week on the 14th. The problem started after 10pm locat (0300Z) on the 18th . I will be back on the phone to ACER in the morning. not looking forward to talking to support tech's all day! 
But that is easier and less expensive than a replacement.



On Tue, Jul 20, 2021 at 10:19 PM Ed W2LCQ via groups.io <w2lcq=yahoo.com@groups.io> wrote:
In the past two weeks Windows 10 offered me 2 updates which I accepted and downloaded and installed. I’ve had no problems. Is it possible assuming you made or did not make  those updates and afterward your problems occurred? I have a Dell Latitude 7840 machine 3 years old with 16 MB RAM. I use DXL with WSJT-X and N1MM+

73, de Ed Jones W2LCQ

Frankford Radio Club
BUG CWops SKCC FISTS LICWC QCWA


On Jul 20, 2021, at 9:16 PM, Michael E Wilson Sr <ke5wct@...> wrote:

Don's know where to put this issue - In involves Windows to totally removing the Port (com & LPT) setting within Device Manager. No Matter what is done to the PC the Device Manager "Port (COM & LPT)" remains gone.

Chain of events. Sunday Evening I fired up the FT-991A along with wsjt-x and JTAlert. I worked a couple of station, but was tired so shup the radio down, then shut down the PC, same order of events as always, Then went to bed.
Monday, after working at the PC most of the day (working with HRDLog that get qsl's caught up. That evening I fired up the radio and wsjt-x/JTAlert, bam big red flag that the wsjt-x would not connect to the radio. Checked the setting and found that
for the radio port there was on USB listed (no com ports of any kind). No mater what I tried, there was no way to connect to the radio. I check into the PC, and could not find any com ports in device manager. I gave up and went to bed. Today I spent several hours trying to figure out what happened and how to fix it. Found nothing. This after noon, I called ACER (PC is a 6 week on ACER Aspire under 3 year warranty). Tech support had never heard any any events like what I presented. There initial solution after other attempts failed, was to use the PC reset function and reset the PC back to the original factory Windows 10 install as it appeared what I bought it. That only took about 40 minutes. But those 40 mins just to al my total frustration, since the problem remained.

Since this is obviously a Windows problem, thought it would throw it out to the world and see if I could catch me a very big Window 10 SME (Subject Matter Enthusiast). I would think that there has to be at least one other unornate OLD man out there that has run into this problem and has the magic solution!

Any takers?

Very grateful for  any assistance
73 and have a Great DX day.

de KE5WCT 
Mike Wilson
--
Mike
KE5WCT



--
73 de KE5WCT
Mike Wilson

--
Mike
KE5WCT


Re: spotcollector bandmodes file

Dave AA6YQ
 

+ AA6YQ comments below

I am looking for a SC bandmodes file I can download to my SC folder.

Is there a SC bandmodes file somewhere that defines all band segments for bands from 160 thru 6 meters.

+ The file

BandModes 2021-04-20.txt

+ should be present in your SpotCollector folder. If it is not, you can obtain it here:

www.dxlabsuite.com/spotcollector/BandModes%202021-04-20.txt

73,

Dave, AA6YQ


Re: Windows 10 Port (com & LPT) vanished

Ed W2LCQ
 

In the past two weeks Windows 10 offered me 2 updates which I accepted and downloaded and installed. I’ve had no problems. Is it possible assuming you made or did not make  those updates and afterward your problems occurred? I have a Dell Latitude 7840 machine 3 years old with 16 MB RAM. I use DXL with WSJT-X and N1MM+

73, de Ed Jones W2LCQ

Frankford Radio Club
BUG CWops SKCC FISTS LICWC QCWA


On Jul 20, 2021, at 9:16 PM, Michael E Wilson Sr <ke5wct@...> wrote:

Don's know where to put this issue - In involves Windows to totally removing the Port (com & LPT) setting within Device Manager. No Matter what is done to the PC the Device Manager "Port (COM & LPT)" remains gone.

Chain of events. Sunday Evening I fired up the FT-991A along with wsjt-x and JTAlert. I worked a couple of station, but was tired so shup the radio down, then shut down the PC, same order of events as always, Then went to bed.
Monday, after working at the PC most of the day (working with HRDLog that get qsl's caught up. That evening I fired up the radio and wsjt-x/JTAlert, bam big red flag that the wsjt-x would not connect to the radio. Checked the setting and found that
for the radio port there was on USB listed (no com ports of any kind). No mater what I tried, there was no way to connect to the radio. I check into the PC, and could not find any com ports in device manager. I gave up and went to bed. Today I spent several hours trying to figure out what happened and how to fix it. Found nothing. This after noon, I called ACER (PC is a 6 week on ACER Aspire under 3 year warranty). Tech support had never heard any any events like what I presented. There initial solution after other attempts failed, was to use the PC reset function and reset the PC back to the original factory Windows 10 install as it appeared what I bought it. That only took about 40 minutes. But those 40 mins just to al my total frustration, since the problem remained.

Since this is obviously a Windows problem, thought it would throw it out to the world and see if I could catch me a very big Window 10 SME (Subject Matter Enthusiast). I would think that there has to be at least one other unornate OLD man out there that has run into this problem and has the magic solution!

Any takers?

Very grateful for  any assistance
73 and have a Great DX day.

de KE5WCT 
Mike Wilson
--
Mike
KE5WCT


spotcollector bandmodes file

Joe K2UF
 

I am looking for a SC bandmodes file I can download to my SC  folder.
 
Is there a SC bandmodes file somewhere that defines all band segments for bands from 160 thru 6 meters.  
 
73  Joe K2UF 


Re: USB Relay interface

Hamilton Stewart
 

Thank you all, you have given me a lot of good options to study.  
--
Hamilton K1HMS
Amherst, NH USA


Windows 10 Port (com & LPT) vanished

Michael E Wilson Sr <ke5wct@...>
 

Don's know where to put this issue - In involves Windows to totally removing the Port (com & LPT) setting within Device Manager. No Matter what is done to the PC the Device Manager "Port (COM & LPT)" remains gone.

Chain of events. Sunday Evening I fired up the FT-991A along with wsjt-x and JTAlert. I worked a couple of station, but was tired so shup the radio down, then shut down the PC, same order of events as always, Then went to bed.
Monday, after working at the PC most of the day (working with HRDLog that get qsl's caught up. That evening I fired up the radio and wsjt-x/JTAlert, bam big red flag that the wsjt-x would not connect to the radio. Checked the setting and found that
for the radio port there was on USB listed (no com ports of any kind). No mater what I tried, there was no way to connect to the radio. I check into the PC, and could not find any com ports in device manager. I gave up and went to bed. Today I spent several hours trying to figure out what happened and how to fix it. Found nothing. This after noon, I called ACER (PC is a 6 week on ACER Aspire under 3 year warranty). Tech support had never heard any any events like what I presented. There initial solution after other attempts failed, was to use the PC reset function and reset the PC back to the original factory Windows 10 install as it appeared what I bought it. That only took about 40 minutes. But those 40 mins just to al my total frustration, since the problem remained.

Since this is obviously a Windows problem, thought it would throw it out to the world and see if I could catch me a very big Window 10 SME (Subject Matter Enthusiast). I would think that there has to be at least one other unornate OLD man out there that has run into this problem and has the magic solution!

Any takers?

Very grateful for  any assistance
73 and have a Great DX day.

de KE5WCT 
Mike Wilson
--
Mike
KE5WCT


Re: VUCC report query

Phil Cooper
 

Hi Dave,

Many thanks for your comprehensive answer! I will try that when I am off on Friday, and have some time to do this.
I've copied the instructions to a file, which I will put on the shack PC, which will allow me to copy & paste the SQL expressions, as I am bound to make a mistake if I try and type them in!

I will report back and see what differences there.

73 de Phil GU0SUP

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: 19 July 2021 22:13
To: DXLab@groups.io
Subject: Re: [DXLab] VUCC report query

+ AA6YQ comments below

Simply because my compromise antenna seems to be doing better than expected, mainly because of the improving conditions on 6m, I am starting to chase DXCC, and also keeping an eye on my VUCC total on LoTW.

Currently, LoTW shows that I have 200 grids confirmed on 6m.
However, when I check the VUCC report in DXKeeper, it says 214 worked and 186 confirmed.

Looking at the report, there are quite a few that show MISSING under the LoTW Confirm heading, but are confirmed on LoTW and show up in my VUCC total.

Is it because they were RTTY, rather than FT8, where the grid is usually logged, whist in RTTY, it usually isn't?

+ A QSO can be confirmed via LoTW for DXCC, but if your QSO partner didn't include a grid square in the "Station Location" he or she employed to submit your QSO to LoTW, then the grid square won't be confirmed. If after submitting a QSO with a "Station Location" that doesn't specify a grid square, one of your QSO partners adds the grid square to the "Station Location" and resubmits that QSO, DXKeeper's "Sync LoTW QSLs" function will not update your QSO to reflect the grid square confirmation because LoTW doesn't consider the update a "new confirmation" -- a defect in LOTW, in my opinion.

+ To update those QSOs,

1. filter the Log Page Display with

(Band = '6m') and (Len(gridsquare)>0 ) and (APP_DXKEEPER_LOTW_QSL_RCVD in ('Y','S','V')) and not (APP_DXKEEPER_LOTWCONFIRMATION like '*G*')

and note the number of QSOs in the Log Page Display

2. On the Main window's QSL tab,

2a. set the "QSL Via" panel to LoTW

2b. click the "Update from LoTW" button

3. rerun the SQL expression from step 1 to see how many 6M QSOs with unconfirmed gridsquares remain in your log


+ If you have made 6M QSOs with stations operating on grid square boundaries, then you should repeat the above process for gridsquares 2, 3, and 4. Grid 2, for example, would employ this SQL expression in step 1:

(Band = '6m') and (Len(APP_DXKEEPER_GRID2)>0 ) and (APP_DXKEEPER_LOTW_QSL_RCVD in ('Y','S','V')) and not (APP_DXKEEPER_LOTWCONFIRMATION like '*2*')


I also notice that the VUCC report brings up contacts where there is no card, and no LoTW confirmation, so I would really like to get a VUCC report for just those grids confirmed on LoTW. is that possible?

+ Yes; filter the Log Page Display with the expression

(APP_DXKEEPER_LOTWCONFIRMATION like '*G*') or (APP_DXKEEPER_LOTWCONFIRMATION like '*2*') or (APP_DXKEEPER_LOTWCONFIRMATION like '*3*') or (APP_DXKEEPER_LOTWCONFIRMATION like '*4*')

+ before running the VUCC progress report

73,

Dave, AA6YQ


Re: DXKeeper Capture and WSJT-X

Dave AA6YQ
 

+ AA6YQ comments below
I’m newby with FT8 mode.
I use full DXLab and WSJT-X.
When I click callsign on WSJT pane, the one does appear at the DXVieu,
but does not appear at the Capture pane. Is it normal?
+ Yes. When you're using WSJT-X to make QSOs in a K1JT mode like FT8, WSJT-X takes the place of the Capture window. A similar thing happens when you use WInWarbler to make QSOs in PSK, RTTY, CW, or SSB.

        73,

               Dave, AA6YQ


DXKeeper Capture and WSJT-X

Igor ananyev
 

Hi to all!
I’m newby with FT8 mode.
I use full DXLab and WSJT-X.
When I click callsign on WSJT pane, the one does appear at the DXVieu,
but does not appear at the Capture pane. Is it normal?
Or I’m missing something. HELP did not help me, hi.

73! Igor, UC6N


Re: Transfer a Workspace ...

Peter Laws / N5UWY
 

On Mon, Jul 19, 2021 at 11:44 PM Dave AA6YQ <aa6yq@ambersoft.com> wrote:



In the DXKeeper file (no .reg) within the Workspace directory corresponding to the club's callsign, I find my own callsign in addition to the club call.

"MarathonInformation-0"="N5UWY"
"LotWUser"="n5uwy"
"n5uwy"="[REDACTED]"

I would like to clean that up in a programmatic way since my inclination is to go to Windows Subsystem for Linux, and edit the suckers out of there with vi ... but that's probably not the best way.

* I strongly advise against directly editing the registry files. Instead,
1. Terminate all DXLab applications except the Launcher
2. Direct the Launcher to load the Workspace
3. Start DXKeeper
4. Use DXKeeper to correct the incorrect settings
5. Terminate DXKeeper
6. Direct the Launcher to save Settings to the Workspace
* Now the Workspace has been updated with your corrected settings
But, but, but ... ASCII !! :-D This is exactly what I realized I
could do and should have been more careful about in the past.

Of the examples I left in above, the only one I can't find (so I can
kill) is the second set of LOTW credentials (my call vs the club
call). Club stuff is there, but so is my own stuff. DXKeeper is the
last cleanup I need to do - the rest of my errors were cleaned up
programatically.



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


Re: Transfer a Workspace ...

Dave AA6YQ
 

* AA6YQ comments below

The whole point of moving the workspace from my PC to the new trustee's PC is so he can maintain the log for the club station. Do I not need to bother with the workspace part at all and just Dropbox him the database?

* The database will enable access to the log, but all of DXKeeper's other settings would have to be manually configured.


I had never looked at the files in the workspace folders before, what
with fear of black magic and all, and now I see that they are
basically just the Registry entries in plain text. Including LOTW and
TQSL credentials in plain text. :/

+ They are files with a .reg suffix. Be careful: double-clicking one of them in Windows Explorer, and its contents will be loaded into the Windows Registry.
c:/apps/DXLab/Launcher/Workspaces contains a number of directories, one for each workspace as I guess you'd expect. In each of these directories are files with the name of the various DXL modules. None of them have .reg extensions (yes, I have "hide extensions" turned off because that's weird and I'm looking at them in PowerShell in any case). All appear to *be* Registry entries, e.g.,

REGEDIT4

[HKEY_CURRENT_USER\Software\VB and VBA Program Settings\DXKeeper]

[HKEY_CURRENT_USER\Software\VB and VBA Program Settings\DXKeeper\ADIF]

et cetera so we're talking about the same items regardless of how they may be named.

* My mistake; they contain registry entries, but do not have a .reg file extension.



Looking at the club DXKeeper stuff in the club workspace, I see my own LOTW and TQSL credentials in addition to the club's ... what did I do
wrong for that to happen? How can I gracefully clean that up before the transfer happens?

+ I don't understand the first question. In general, to update a
+ Workspace's contents,
In the DXKeeper file (no .reg) within the Workspace directory corresponding to the club's callsign, I find my own callsign in addition to the club call.

"MarathonInformation-0"="N5UWY"
"LotWUser"="n5uwy"
"n5uwy"="[REDACTED]"

I would like to clean that up in a programmatic way since my inclination is to go to Windows Subsystem for Linux, and edit the suckers out of there with vi ... but that's probably not the best way.

* I strongly advise against directly editing the registry files. Instead,

1. Terminate all DXLab applications except the Launcher

2. Direct the Launcher to load the Workspace

3. Start DXKeeper

4. Use DXKeeper to correct the incorrect settings

5. Terminate DXKeeper

6. Direct the Launcher to save Settings to the Workspace

* Now the Workspace has been updated with your corrected settings

73,

Dave, AA6YQ


Re: PropView: No predicted Sunspot Numbers

Dave AA6YQ
 

+ AA6YQ comments below

Over the last few days, when the DXLab suite starts up, I get an error message for PropView. The error is:

No 'Predicted Sunspot Numbers' URL specified in the Configuration windows 'Prediction URLs' panel.

If I go into the configuration panel within PropView, the Prediction URL's are blank.

What are the suggested URL's to insert in the empty fields?

+ Predicted Sunspot Numbers: https://services.swpc.noaa.gov/json/solar-cycle/predicted-solar-cycle.json

+ Current solar and geomagnetic conditions: https://services.swpc.noaa.gov/text/wwv.txt

+ Predicted SFI and A-index: https://services.swpc.noaa.gov/text/45-day-ap-forecast.txt

73,

Dave, AA6YQ


Re: Broken Link-"Display callsign progress on Lookup"

Dave AA6YQ
 

+ AA6YQ comments below
Those links still don't work for me. Will a newer version of DXKeeper with new Help files/documents need to being installed before the broken links work?

+ I corrected this web page:

https://www.dxlabsuite.com/dxkeeper/Help/ViewEditLog.htm

+ To update your local copy, you can download it into DXKeeper's Help folder, replacing the existing ViewEditLog.htm file. Your local copy will be automatically updated by the next version of DXKeeper.

       73,

             Dave, AA6YQ


 


Re: Broken Link-"Display callsign progress on Lookup"

Jim McPhee
 

Hi Dave,

Those links still don't work for me. Will a newer version of DXKeeper with new Help files/documents need to being installed before the broken links work?
--
Jim McPhee
Placitas, NM
W5ABA


Re: Transfer a Workspace ...

Peter Laws / N5UWY
 

On Mon, Jul 19, 2021 at 5:10 PM Dave AA6YQ <aa6yq@ambersoft.com> wrote:

+ The Launcher's Workspaces window displays the Workspaces present in the current Workspaces folder (which defaults to the Launcher's Workspaces folder). If you move a new folder into the current Workspaces folder while the Launcher is running, terminate and restart the Launcher; the new folder should now be present on the Launcher's Workspaces window.

Cool!


2) Move the DXKeeper MDB with the club log before or after the workspace shenanigans?

+ I don't understand the question. Please elaborate.
The whole point of moving the workspace from my PC to the new
trustee's PC is so he can maintain the log for the club station. Do I
not need to bother with the workspace part at all and just Dropbox him
the database? 'Cause that makes the rest of this moot. :-)




I had never looked at the files in the workspace folders before, what with fear of black magic and all, and now I see that they are basically just the Registry entries in plain text. Including LOTW and TQSL credentials in plain text. :/

+ They are files with a .reg suffix. Be careful: double-clicking one of them in Windows Explorer, and its contents will be loaded into the Windows Registry.
c:/apps/DXLab/Launcher/Workspaces contains a number of directories,
one for each workspace as I guess you'd expect. In each of these
directories are files with the name of the various DXL modules. None
of them have .reg extensions (yes, I have "hide extensions" turned off
because that's weird and I'm looking at them in PowerShell in any
case). All appear to *be* Registry entries, e.g.,

REGEDIT4

[HKEY_CURRENT_USER\Software\VB and VBA Program Settings\DXKeeper]

[HKEY_CURRENT_USER\Software\VB and VBA Program Settings\DXKeeper\ADIF]

et cetera so we're talking about the same items regardless of how they
may be named.



Looking at the club DXKeeper stuff in the club workspace, I see my own LOTW and TQSL credentials in addition to the club's ... what did I do
wrong for that to happen? How can I gracefully clean that up before the transfer happens?

+ I don't understand the first question. In general, to update a Workspace's contents,
In the DXKeeper file (no .reg) within the Workspace directory
corresponding to the club's callsign, I find my own callsign in
addition to the club call.

"MarathonInformation-0"="N5UWY"
"LotWUser"="n5uwy"
"n5uwy"="[REDACTED]"

I would like to clean that up in a programmatic way since my
inclination is to go to Windows Subsystem for Linux, and edit the
suckers out of there with vi ... but that's probably not the best way.

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


PropView: No predicted Sunspot Numbers

RIchard Thorne
 

Over the last few days, when the DXLab suite starts up, I get an error message for PropView. The error is:

No 'Predicted Sunspot Numbers' URL specified in the Configuration windows 'Prediction URLs' panel.

If I go into the configuration panel within PropView, the Prediction URL's are blank.

What are the suggested URL's to insert in the empty fields?

Rich - N5ZC

5641 - 5660 of 208147