Date   

Re: Commander Flex IP Error

ab4sf@...
 

I have been having the same issue here: Flex 6600M, Win 11 Home 64-bit Dell tower, i7-8700 3.2 Ghz proc, 16GB RAM.  The Flex reports that its DHCP IP is 192.168.0.159.

Problem began with Commander 15.4.4.  Reverting back to 15.4.3 clears the problem but then, of course, I do not have access to the cool new features of 15.4.4.

- 14.4.4 issue: Commander could not find my radio. Commander Config Tab kept coming up on an old IP address.  Thanks to this thread found the old IP adr also in the MultiRadio Tab but changing that to the current IP did not fix the issue.  The General tab does not remember the Port number (4992).  When I put that port number in the field manually and Reset, Commander immediately finds my radio and all is good until I shut down and later start the Suite back up again. At that point the Port Number box is again empty.

- I tried re-saving the one Workspace I use.  That did not fix the problem (Port Number does not return when Commander starts the next time) so I Deleted the Workspace and then saved a new one with a different name.  Still no joy.  The Port number is not remembered when Commander starts the next time, thus no radio found.

- Yes, I have upgraded the Flex from 2.7.6 to 2.8 but this Commander behavior is the same with both Flex versions.  

- The Flex is sitting on the same network as the DXLabs pc.

- I do have 3 other radios in the MultiRadio tab.  One I do use, an IC-7100 on COM 3.  That one is enabled.  There are two other Icoms configured from past experiments where I was helping friends check out radios but those two are not enabled (box not checked) or set to Interrogate, nor are the radios present.

- My knowledge of IP networking is probably just enough to be dangerous :)

That's all I can think of to report.  Any ideas??

73
Wray AB4SF


Re: DXKeeper take 5 minutes to start?

f6gcp
 

Hi
Why not... I am using only MS Antivirus, and I removed unnecessary SW from boot. Any other software is capable to start in a reasonable time after boot, as I know that MS desktop is shown rapidly even the boot sequence is not fully performed, but no application needs 5mn to start (even 1mn, even 30s).
Question : 

2022-06-27 22:11:29     > DXLab Apps        : 

this line is related to a check if any DXlab Apps are already running ? 

  • Advanced Threat Defense causes the delays in logging, delays in callsign lookups, and slows both application startup and shutdow
    so it means that there is no solution? or can we declare to Defender "safe area / datas / area" not to check" (may be no recommended...)

    In fact, I already declared (long time ago) Defender not to scan DXLab folders (because of Winwarbler is getting too slow in RTTY)

    I will perform another test later today
    73 P@t




Re: Entering QSL card data

Dave AA6YQ
 

On Mon, Jun 27, 2022 at 10:54 PM, Earl Needham wrote:
Aaaaand -- all fixed.

Great!

       Dave


Re: Entering QSL card data

Earl Needham
 

Aaaaand -- all fixed.  Thanks again, Dave.

Earl
KD5XB


On Mon, Jun 27, 2022 at 10:06 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below
I did a hybrid app for DXCC about 15 years ago -- some were LoTW and some on cards.
 
Somewhere I have a counting error or maybe I'm not reading this right, but ARRL shows my DXCC total at 102, while DXKeeper shows the below information.  Can I get some proofreading on this?  After so long, I'm not sure I remember how to do this correctly

+ DXKeeper shows on 23 DXCC credits, compared to 102 in your DXCC record. Step 1 is to identify the discrepancies by following these instructions:

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

+ Step 2 is to resolve the inconsistencies, by updating your logged QSOs to reflect DXCC award credit granted. The instructions for doing that are here:

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

       73,

              Dave, AA6YQ

 


Re: Entering QSL card data

Earl Needham
 

Thanks, Dave -- workin' on it!

Vy 7 3
Earl


On Mon, Jun 27, 2022 at 10:06 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below
I did a hybrid app for DXCC about 15 years ago -- some were LoTW and some on cards.
 
Somewhere I have a counting error or maybe I'm not reading this right, but ARRL shows my DXCC total at 102, while DXKeeper shows the below information.  Can I get some proofreading on this?  After so long, I'm not sure I remember how to do this correctly

+ DXKeeper shows on 23 DXCC credits, compared to 102 in your DXCC record. Step 1 is to identify the discrepancies by following these instructions:

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

+ Step 2 is to resolve the inconsistencies, by updating your logged QSOs to reflect DXCC award credit granted. The instructions for doing that are here:

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

       73,

              Dave, AA6YQ

 


Re: Entering QSL card data

Dave AA6YQ
 

+ AA6YQ comments below
I did a hybrid app for DXCC about 15 years ago -- some were LoTW and some on cards.
 
Somewhere I have a counting error or maybe I'm not reading this right, but ARRL shows my DXCC total at 102, while DXKeeper shows the below information.  Can I get some proofreading on this?  After so long, I'm not sure I remember how to do this correctly

+ DXKeeper shows on 23 DXCC credits, compared to 102 in your DXCC record. Step 1 is to identify the discrepancies by following these instructions:

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

+ Step 2 is to resolve the inconsistencies, by updating your logged QSOs to reflect DXCC award credit granted. The instructions for doing that are here:

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

       73,

              Dave, AA6YQ

 


Entering QSL card data

Earl Needham
 

I did a hybrid app for DXCC about 15 years ago -- some were LoTW and some on cards.

Somewhere I have a counting error or maybe I'm not reading this right, but ARRL shows my DXCC total at 102, while DXKeeper shows the below information.  Can I get some proofreading on this?  After so long, I'm not sure I remember how to do this correctly.

Thanks,
Earl
KD5XB
______________________________________________

KD5XB DXCC Progress Report 27-Jun-2022

Filter: None

Counts confirmations via QSL cards and LotW


ARRL-verified Honor Roll Countries (excludes deleted countries)
    mixed     023
    phone     013
    cw        008
    digi      002
    160m      000
    80m       000
    40m       001
    30m       001
    20m       011
    17m       001
    15m       008
    12m       001
    10m       000
    6m        000
    2m        000
    Sat       000

Confirmed DXCC Countries (includes deleted countries)
    mixed     063
    phone     038
    cw        036
    digi      004
    PSK       001
    160m      002
    80m       004
    40m       015
    30m       005
    20m       032
    17m       010
    15m       019
    12m       002
    10m       007
    6m        003
    2m        000
    Sat       000

Confirmed HF band and mode totals (Phone, CW, Digital, includes deleted countries)
    modes     0077
    bands     0096
    total     0173

Confirmed DXCC Challenge total (Phone, CW, Digital, excludes deleted countries)
    bands     0096

Confirmed DXCC Countries (excludes deleted countries)
    mixed     061
    phone     036
    cw        035
    digi      004
    PSK       001
    160m      002
    80m       004
    40m       014
    30m       005
    20m       030
    17m       010
    15m       019
    12m       002
    10m       007
    6m        003
    2m        000
    Sat       000

Top (9 HF Bands, Phone, CW, Digital, excludes deleted countries)
    topmode   0074
    topband   0093
    toplist   0167


(long country grid deleted)


Includes deleted entities  

                Mixed  Phone     CW   DIGI    PSK 160M  80M  40M  30M  20M  17M  15M  12M  10M   6M   2M Card LotW  Sat

        worked     64     39     36      4      1    2    4   15    5   32   10   19    2    8    3    0              0
     confirmed     63     38     36      4      1    2    4   15    5   32   10   19    2    7    3    0   62   63    0
      verified     23     13      8      2      1    0    0    1    1   11    1    8    1    0    0    0   23   23    0


Non-deleted entities only  

                Mixed  Phone     CW   DIGI    PSK 160M  80M  40M  30M  20M  17M  15M  12M  10M   6M   2M Card LotW Challenge  Sat

        worked     62     37     35      4      1    2    4   14    5   30   10   19    2    8    3    0                  97    0
     confirmed     61     36     35      4      1    2    4   14    5   30   10   19    2    7    3    0   60   61        96    0
      verified     23     13      8      2      1    0    0    1    1   11    1    8    1    0    0    0   23   23        23    0


SpotCollector 9.2.1 is available

Dave AA6YQ
 

If you are using Windows Defender anti-malware, direct it to update its definitions from

https://www.microsoft.com/en-us/wdsi/definitions

before you install SpotCollector 9.2.1


This release

- retains the "Discard spots from spotting station callsigns ending in -@" setting between operating sessions (tnx to Parker W5ADD)

- provides an "Include Pri & Sec Subs in message" option on the Configuration window's "Email Alarm" tab (tnx to Jose N4BAA)

- reduces the performance impact of sending an email message

- in the "SQL Filters" window, displays the pathname of the file to which SQL filters were last saved or from which they were last
restored title bar (tnx to Norm W4QN)

- recognizes VARA in spot notes to mean that the Mode is "VARA HF"

- updates the DefaultModes.txt file

- updates the ConfigurationNotifications.htm and SpotDatabase.htm documentation files



Notes:

1. Update your firewall and anti-malware applications to consider the new versions of SpotCollector.exe and SC_WSJTX.exe to be
"safe"

a. 0/15 Jotti scanners detected malware in SpotCollector.exe

b. 0/66 VirusTotal scanners detected malware in SpotCollector.exe

c. 0/15 Jotti scanners detected malware in SC_WSJTX.exe

d. 1/68 VirusTotal scanners detected malware in SC_WSJTX.exe

e. SpotCollector.exe and SC_WSJTX.exe have been submitted to "Microsoft Security Intelligence" and found free of malware.

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 SpotCollector, see

http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion



SpotCollector 9.2.1 is available via the DXLab Launcher, and via

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


73,

Dave, AA6YQ


Re: DXKeeper take 5 minutes to start?

Dave AA6YQ
 

+ AA6YQ comments below
Safe mode, so it means only one Monitor available
- immediate start (click on Launcher just few seconde after the desktop is displayed)

+ That means one of the applications that Windows is configured to start automatically when booted normally is interfering with the Launcher's startup. The culprit is typically your anti-malware, but other applications can also produce an adverse result. See

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

     73,

            Dave, AA6YQ


Re: DXKeeper take 5 minutes to start?

f6gcp
 

Hi

Safe mode, so it means only one Monitor available
- immediate start (click on Launcher just few seconde after the desktop is displayed)
- from log : 
2022-06-27 22:07:38     > DXLab Apps        : 
2022-06-27 22:07:38     > Monitors          : 1

A restart in "normal" mode (here 4 minutes)
2022-06-27 22:11:29     > DXLab Apps        : 
2022-06-27 22:15:11     > Monitors          : 3

Thanks - 73 P@t



Re: LOTW down?

Joe Subich, W4TV
 

Not down here ... was able to log in and check most recent QSOs/QSLs
as well as Awards status and the home page. The number of QSO records
in the system is incrementing in fits and starts.

73,

... Joe, W4TV

On 2022-06-27 4:05 PM, Dave AA6YQ wrote:
LoTW is currently down.
My erroneous claim below was the result of checking the LoTW Queue, rather than attempting to log in or submit QSOs or Sync.
      73,
             Dave, AA6YQ
+ AA6YQ comments below
I get the following error when trying to upload to LOTW:
Attempting to upload one QSO
C:\HamPrograms\DXLab\DXKeeper\LotWUpload.ADI: Couldn't upload
the file: CURL returned "Timeout was reached" (Failed to connect
to lotw.arrl.org port 443 after 21013 ms: Timed out)
Final Status: TQSL Error(4)
+ Either LoTW was down (it's running at 1958Z), your internet
connection was down, or TQSL is being prevented from accessing the
internet, most likely by your anti-malware.


Re: [ARRL-LoTW] LOTW down?

Gordon LaPoint
 

Back up, just uploaded the 4 QSO's that I got the error on.
Thanks,
Gordon - N1MGO

On 6/27/2022 16:13 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

I just uploaded a log with TQSL and had no problem.

Are you connected to the internet? Can you open https://lotw.arrl.org/ in a browser?

+ Here, this URL times out:

https://lotw.arrl.org/lotwuser/default

+ A line of thunderstorms just passed over Newington...

73,

Dave, AA6YQ






Re: LOTW down?

Dave AA6YQ
 

LoTW is currently down. 

My erroneous claim below was the result of checking the LoTW Queue, rather than attempting to log in or submit QSOs or Sync.

      73,

             Dave, AA6YQ

 

+ AA6YQ comments below
I get the following error when trying to upload to LOTW:

Attempting to upload one QSO
C:\HamPrograms\DXLab\DXKeeper\LotWUpload.ADI: Couldn't upload the file: CURL returned "Timeout was reached" (Failed to connect to lotw.arrl.org port 443 after 21013 ms: Timed out)
Final Status: TQSL Error(4)

+ Either LoTW was down (it's running at 1958Z), your internet connection was down, or TQSL is being prevented from accessing the internet, most likely by your anti-malware.


Re: LOTW down?

Dave AA6YQ
 

+ AA6YQ comments below
I get the following error when trying to upload to LOTW:

Attempting to upload one QSO
C:\HamPrograms\DXLab\DXKeeper\LotWUpload.ADI: Couldn't upload the file: CURL returned "Timeout was reached" (Failed to connect to lotw.arrl.org port 443 after 21013 ms: Timed out)
Final Status: TQSL Error(4)

+ Either LoTW was down (it's running at 1958Z), your internet connection was down, or TQSL is being prevented from accessing the internet, most likely by your anti-malware.

          73,

              Dave, AA6YQ


Re: DX Commander and Icom IC-375A

Joe Subich, W4TV
 

//It's worth noting that the ancient IC-375A does not have a CAT
command to control PTT, so that function must be performed separately
from the CAT link (via RTS on the COM port).
In Commander -> Config-> Ports -> Primary CAT Serial Port
Set RTS to TX

If you are using the multi-rig capability of Commander in
Commander -> Config -> MultiRadio -> CAT Serial Port
Set the correct radio # RTS to "X"

These are the same settings for all Icom transceivers of that era
that did not support PTT via CAT command (and works with any interface
that supports PTT on the CAT port RTS line).

73,

... Joe, W4TV


On 2022-06-27 2:51 PM, Walter Miller, AJ6T wrote:
I sent the message below to the WSJT-X group looking for help with control of my old IC-375A.  Since I hope to run that rig via DX Commander I am sending the message to the DXLab group as well to look for help here.
/I recently obtained a old 1980s-era Icom IC-375A monoband 222 MHz transceiver, and I cannot get it to work with WSJT-X.  The first problem is that there is no IC-375A Radio option in the WSJT-X settings menu, so there is no direct way to control this transceiver from WSJT-X.  I had partial success by selecting "DX Lab Suite Commander" as the radio and using DX Commander to control the CAT portion of the interface since DX Commander does have an IC-375A option.  With that setup I can control the IC-375A frequency and mode from DX Commander, and both DX Commander and WSJT-X properly display the chosen mode and frequency.  FT8 reception works, but PTT and audio TX do not work.  I'm using the default IC-375A CI-V parameters Hex12 and 1200 baud. //
/ /
//My interface is a G8XGG "USB-DIGIMODE-4" box with three cables: USB to computer, ACC DIN connector to rig, and CI-V cable to the rig's  3.5mm mini "REMOTE" connector.  This interface presents both an audio CODEC and a COM port to the computer. //
/ /
//It's worth noting that the ancient IC-375A does not have a CAT command to control PTT, so that function must be performed separately from the CAT link (via RTS on the COM port).  The rig will be operated in USB mode since there is no dedicated digital mode on the IC-375A. //
/ /
//The IC-375A is very similar to other monoband VHF rigs of that era, the IC-275 (2m) and IC-475 (70cm), so I imagine that the hamlib programs used for all three rigs must be very similar. Another complication is that it appears that all of the WSJT-X options for Icom radios use the default settings for CI-V ports and baud rates. //
/ /
//I would like to run the IC-375A directly from WSJT-X in one configuration, and to control the rig from DX Commander in a separate configuration (obviously not at the same time) since that brings in the very nice DX Lab environment. //
/ /
//Any suggestions on how I might breathe life into my IC-375A would be most appreciated. //
/ /
//73, Walt, AJ6T /


Re: TCP import sends LotW card against option.

Dave AA6YQ
 

+ AA6YQ comments below
When I send DXKeeper an externallog entry via TCP, it uploads the QSO  to LotW  whether or not I have specified <UploadLoTW:1>N
I went through the config screens and tried to make sure that there were no "LotW upload" options enabled, perhaps I missed something.
The other options included in the command are  <DeduceMissing:1>Y and <QueryCallbook:1>Y
In looking at the errorlog, I note these lines:
2022-06-27 19:07:50.723 > DXLogModule.QSLsViaLotW, theCallsign = X1XX
2022-06-27 19:07:50.727 > DXLogModule.QSLsViaLotW, result = Y
(the call is substituted for a real call from my log).
Is this DXKeeper querying either the local log or some online resource and pulling the LotW status from it, and using the trigger to upload the QSO?
If so, how can I keep DXKeeper from using that field as upload request while still having it fill in other missing info from the local log / web?

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

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

2. terminate DXKeeper

3. start DXKeeper, and wait for it to fully initialized

4.send DXKeeper an externallog directive with <UploadLoTW:1>N

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

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

aa6yq (at) ambersoft.com

      73,

             Dave, AA6YQ


LOTW down?

Gordon LaPoint
 

I get the following error when trying to upload to LOTW:


Attempting to upload one QSO
C:\HamPrograms\DXLab\DXKeeper\LotWUpload.ADI: Couldn't upload the file: CURL returned "Timeout was reached" (Failed to connect to lotw.arrl.org port 443 after 21013 ms: Timed out)
Final Status: TQSL Error(4)



Thanks,

Gordon - N1MGO


Re: Can not locate exported file to be sent to LOTW

Dave AA6YQ
 

+ AA6YQ comments below
On Mon, Jun 27, 2022 at 12:31 PM Dick Bingham <dick.bingham@...> wrote:
Hello Rick

Where you say ===> "What I would try is to run a Command prompt "As Adminstrator" - press the "Windows" key, type the letters "cmd" then you should see a "Run as Administrator" option. Select that. (Or, right click the icon and choose "Run as Administrator") "
 
That depends on what Windows version you're running.
 
Look for an article explaining how to do that for your version of Windows.  (I don't know if Windows 11 has a similar way to get admin credentials.)
 
I get the following response ===>

 and nowhere find the run as administrator after right-clicking the 'mouse' on everything in or on the popup screen.
The remainder of your suggestions I have not tried because I can't get past the first step described above !

I am also puzzled by the "header" in the above screen capture where in says "C:\Windows\System32\cmd.exe"
System info says ===>

I have a 64-bit OS
 
That's fine. 64-bit windows does run things that are 32-bit applications. And some programs are in System32 because that's where they first appeared.
 
Dave, should we take this off list?

+ Not necessary, Rick. While not everyone here may be anxiously awaiting the next episode, what you're describing is certainly of interest to some members, perhaps reinforcing what they already understood. Also, the thread will be accessible her to future queries.

  
         73,

               Dave, AA6YQ


Re: DX Commander and Icom IC-375A

Dave AA6YQ
 

+ AA6YQ comments below

 

I sent the message below to the WSJT-X group looking for help with control of my old IC-375A.  Since I hope to run that rig via DX Commander I am sending the message to the DXLab group as well to look for help here.

 

I recently obtained a old 1980s-era Icom IC-375A monoband 222 MHz transceiver, and I cannot get it to work with WSJT-X.  The first problem is that there is no IC-375A Radio option in the WSJT-X settings menu, so there is no direct way to control this transceiver from WSJT-X.  I had partial success by selecting "DX Lab Suite Commander" as the radio and using DX Commander to control the CAT portion of the interface since DX Commander does have an IC-375A option.  With that setup I can control the IC-375A frequency and mode from DX Commander, and both DX Commander and WSJT-X properly display the chosen mode and frequency.  FT8 reception works, but PTT and audio TX do not work.  I'm using the default IC-375A CI-V parameters Hex12 and 1200 baud.

My interface is a G8XGG "USB-DIGIMODE-4" box with three cables: USB to computer, ACC DIN connector to rig, and CI-V cable to the rig's  3.5mm mini "REMOTE" connector.  This interface presents both an audio CODEC and a COM port to the computer.

It's worth noting that the ancient IC-375A does not have a CAT command to control PTT, so that function must be performed separately from the CAT link (via RTS on the COM port).  The rig will be operated in USB mode since there is no dedicated digital mode on the IC-375A.

+ Have you arranged for the COM port RTS signal to switch your IC-375 from RX to TX and back? Does this work correctly?

+ Have you configured the Audio tab of the WSJT-X Settings window's Audio tab to use the virtual soundcard sections presumably created by your "USB-DIGIMODE-4" box for Input and Output?

+ Have you configured the Windows multimedia mixer to provide a sufficient level on the virtual soundcard's Playback section?

    73,

          Dave, AA6YQ


TCP import sends LotW card against option.

Tim Sweeney
 

When I send DXKeeper an externallog entry via TCP, it uploads the QSO  to LotW  whether or not I have specified <UploadLoTW:1>N
I went through the config screens and tried to make sure that there were no "LotW upload" options enabled, perhaps I missed something.
The other options included in the command are  <DeduceMissing:1>Y and <QueryCallbook:1>Y
In looking at the errorlog, I note these lines:
2022-06-27 19:07:50.723 > DXLogModule.QSLsViaLotW, theCallsign = X1XX
2022-06-27 19:07:50.727 > DXLogModule.QSLsViaLotW, result = Y
(the call is substituted for a real call from my log).
Is this DXKeeper querying either the local log or some online resource and pulling the LotW status from it, and using the trigger to upload the QSO?
If so, how can I keep DXKeeper from using that field as upload request while still having it fill in other missing info from the local log / web?

Thanks, Tim K1BR

2341 - 2360 of 211086