Date   

Re: DX Lab glasses ?

Pete Smith
 

My situation (two monitors and trifocals) is the same as yours, but so far, at least, I have not been troubled.  I have taken care to place my two 27"monitors close together side-by-side at a height that avoids neck pain, for me anyhow.  I have also experimented with a pair of 2.5 diopter drugstore glasses, and find they work fine, but since the middle range of my trifocals also works well, I have opted to avoid the inconvenience of swapping glasses.

73, Pete N4ZR
Check out the new Reverse Beacon Network
web server at <https://reversebeacon.net>.
For spots, please use your favorite 
"retail" DX cluster.
On 7/17/2022 9:36 PM, Andrew OBrien wrote:


With many DX Lab users using two large screen monitors for all the DXL features , I wonder if users have advice on eye glasses ? I use two monitors and wear prescription tri-focals. Increasingly , I find myself having neck pain as I shift my head/eyes to the various Windows . With an upcoming annual eye exam , I thought I would see if users here have advice . I have read that professional optometry organizations feel there is “no need  for computer glasses “

Andy K3UK


DX Lab glasses ?

Andrew OBrien
 


With many DX Lab users using two large screen monitors for all the DXL features , I wonder if users have advice on eye glasses ? I use two monitors and wear prescription tri-focals. Increasingly , I find myself having neck pain as I shift my head/eyes to the various Windows . With an upcoming annual eye exam , I thought I would see if users here have advice . I have read that professional optometry organizations feel there is “no need  for computer glasses “

Andy K3UK


Re: Commander Connection to Kenwood TS-590S

Dave AA6YQ
 

+ AA6YQ comments below
via a USB A-B cable

+ Then I suggest that you switch to a USB-to-Serial-Port converter connected to the RS232 port on the back of your TS-590S, following these instructions:

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

+ If you don't have a USB-to-Serial-Port converter at hand, I recommend this one:

https://www.amazon.com/Tripp-Lite-Keyspan-High-Speed-USA-19HS/dp/B0000VYJRY/ref=sr_1_11

   73,

        Dave, aa6yq

 

 

 

 


Re: Commander Connection to Kenwood TS-590S

John-WA7ZXD
 

via a USB A-B cable


Re: IP Address for Flex6000

Paul W5PF
 

Yes it was checked and unchecking it fixed the problem. Since I only have one radio I don't know why it was checked.

Thanks for your quick response.

73, Paul W5PF


On 7/17/2022 6:12 PM, Dave AA6YQ wrote:

+ AA6YQ comments below
Recently, within about the last month, Commander does not retain the correct IP address for my Flex6600. When it starts up it has the incorrect address. I have to input the proper address and hit the reset button for it to work properly. The incorrect address is always the same (169.254.27.78). The address for my radio does not change, it is 192.168.1.17.

I have tried saving my Commander configuration into my workspace after changing the address, but that makes no difference.

I am running Win7 with  Commander 15.4.4, Launcher 2.1.7,DXkeeper 16.7.1, DXview 4.8.9 and Spotcollector 9.2.1.

I looked for help concerning the IP address on the Commander configuration help page, but that says the IP address is only for the K4 and Thetis radios.

How do I make Commander remember the proper IP address?

+ Do you have MultiRadio support enabled for your 6600 on the Configuration window's MultiRadio tab?

      73,

             Dave, AA6YQ


Re: IP Address for Flex6000

Dave AA6YQ
 

+ AA6YQ comments below
Recently, within about the last month, Commander does not retain the correct IP address for my Flex6600. When it starts up it has the incorrect address. I have to input the proper address and hit the reset button for it to work properly. The incorrect address is always the same (169.254.27.78). The address for my radio does not change, it is 192.168.1.17.

I have tried saving my Commander configuration into my workspace after changing the address, but that makes no difference.

I am running Win7 with  Commander 15.4.4, Launcher 2.1.7,DXkeeper 16.7.1, DXview 4.8.9 and Spotcollector 9.2.1.

I looked for help concerning the IP address on the Commander configuration help page, but that says the IP address is only for the K4 and Thetis radios.

How do I make Commander remember the proper IP address?

+ Do you have MultiRadio support enabled for your 6600 on the Configuration window's MultiRadio tab?

      73,

             Dave, AA6YQ


IP Address for Flex6000

Paul W5PF
 

Recently, within about the last month, Commander does not retain the correct IP address for my Flex6600. When it starts up it has the incorrect address. I have to input the proper address and hit the reset button for it to work properly. The incorrect address is always the same (169.254.27.78). The address for my radio does not change, it is 192.168.1.17.

I have tried saving my Commander configuration into my workspace after changing the address, but that makes no difference.

I am running Win7 with  Commander 15.4.4, Launcher 2.1.7,DXkeeper 16.7.1, DXview 4.8.9 and Spotcollector 9.2.1.

I looked for help concerning the IP address on the Commander configuration help page, but that says the IP address is only for the K4 and Thetis radios.

How do I make Commander remember the proper IP address?

Thanks, Paul W5PF


DXKeeper 16.7.1 is available

Dave AA6YQ
 

Before installing or upgrading to DXKeeper 16.7.1,

if you are using Window Defender Antivirus on Windows 10 or Windows 11, update it to its latest malware definition in

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


This version

- in the QRZ panel on the Configuration window's Callbook tab, expands the name of the "Ignore geocoded grid squares" option to
"Ignore geocoded grid squares, latitudes, and longitudes"

- provides a "Preferred Location Source" panel on the Configuration window's Callbook tab that operates as described in
https://groups.io/g/DXLab/message/209060 (tnx to Stewart G0LGS and Joe W4TV)

- corrects a regression introduced in DXKeeper 16.3.7 that gives Callbook data preference over data from previous QSOs when logging
via the Main window's "Log QSOs" tab (tnx to Stewart G0LGS)

- corrects a regression introduced in DXKeeper 16.5.7 that fails to initialize a new QSO's Propagation Mode item if "Default
Propagation Mode by Band" is not enabled on the Configuration window's Defaults tab (tnx to Julio W4HY)

- eliminates unnecessary DXView and Pathfinder lookups during invocations of the "Sync LoTW QSOs", "Sync LoTW QSLs", and "Sync eQSL
QSLs" functions (tnx to Jon KM8V)

- updates the Configuration.htm, Import.htm, and QSL.htm documentation files


Notes:

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

a. JOTTI virus scan: 0 of 15 scanners detected malware in this version's executable

b. VirusTotal: 0 of 69 scanners detected malware in this version's executable

c. submitted to Microsoft for analysis by Windows Defender: no malware detected in this version's executable


2. To view QSOs with missing Propagation Mode items as a result of the regression in DXKeeper 16.5.7, filter the Log Page Display
with the SQL expression

(QSO_BEGIN>#2022-05-21#) and (LEN(PROP_MODE)=0)


2A. If all the Propagation Mode items of all of these QSOs should be set to the same value -- e.g. F2 -- then

2A1. backup your log (Configuration window, Log tab, Backup button)

2A2. in the "Modify QSOs" panel at the bottom of the "Advanced Sorts, Filters, and Modifiers" window,

2A2a. set the "Item name" selector to PROP_MODE

2A2b. set the "Item new value" selector to the correct propagation mode (e.g. F2)

2A2c. click the Mod button


2B. If all the Propagation Mode items of all of these QSOs should be set to different values as a function of Band or Date Range,
then make the corrections in segments. For example, to set PROP_MODE as a function of Band:

2B1. backup your log (Configuration window, Log tab, Backup button)

2B2. filter the Log Page Display with (QSO_BEGIN>#2022-05-21#) and (LEN(PROP_MODE)=0) and (Band = '6M')

2B3. use the "Modify QSOs" panel to set the PROP_MOD in all QSOs in the Log Page Display to ES

2B4. filter the Log Page Display with (QSO_BEGIN>#2022-05-21#) and (LEN(PROP_MODE)=0) and (Band <> '6M')

2B5. use the "Modify QSOs" panel to set the PROP_MOD in all QSOs in the Log Page Display to F2


3. If this upgrade doesn't work correctly, see the "After an Upgrade" section of

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


4. After upgrading, to revert to the previous version of DXKeeper, see

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


DXKeeper 16.7.1 is available via the DXLab Launcher and via

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

73,

Dave, AA6YQ


updated eQSL AG, LoTW, and RDA databases are available...

Dave AA6YQ
 

...via the Databases tab of DXView's Configuration window.

Please terminate DXKeeper and SpotCollector before upgrading these Databases.

DXKeeper 16.7.1 is also now available; if you intend to upgrade DXKeeper, wait to restart DXKeeper until after it's been updated.

73,

Dave, AA6YQ


Re: Commander Connection to Kenwood TS-590S

Dave AA6YQ
 

+ AA6YQ comments below

I have used Commander for several years until I upgraded to Windows 11 on my PC. I have not been able to connect senses December 2021. I tried the updated Silicon Labs driver and have had several back and forth emails with them. I have tried to use a PC specialist to come to my house to fix it. Spent $350 but no fix. I have currently had a retired friend who spent 40 years in Silicon valley working on MS programs, no fix. I am 80 years old and would dearly like to get it running again. Also I can no longer connect to the Kenwood radio control program on my PC.

+ The TS-590S can be connected to a computer in one of two ways:

1. via a USB A-B cable

2. via an RS-232 connection

+ Which one are you using?

+ If you are using an RS-232 connection, to what in your computer is the RS-232 cable connected?

73,

Dave, AA6YQ


Re: VARA AC contacts

Dave AA6YQ
 

+ AA6YQ comments below
LotW does not currently accept "Dynamic" - you will need to
create a mode map in tQSL to map Dynamic to DATA in order to
upload those QSOs to LotW.

+ Step-by-step instructions are here:

https://lotw.arrl.org/lotw-help/pref-adi/

      73,

           Dave, AA6YQ


Re: VARA AC contacts

Joe Subich, W4TV
 

LotW does not currently accept "Dynamic" - you will need to
create a mode map in tQSL to map Dynamic to DATA in order to
upload those QSOs to LotW.

73,

... Joe, W4TV

On 2022-07-17 11:18 AM, Bob WB2NVR wrote:
Hi Dave -
I changed the Mode for my VarAC contacts from DATA to VARA HF.
When I try to upload these Qs to LoTW, I get the following error:
TQSL Version 2.6.4 [v2.6.4]
Signing using Callsign WB2NVR, DXCC Entity UNITED STATES OF AMERICA
Invalid MODE (DYNAMIC) on line 5
CALL: 4Z1AC
TIME_ON: 023036
QSO_DATE: 20220625
MODE: DYNAMIC
SUBMODE: VARA HF
BAND: 40M
FREQ: 7.105
PROP_MODE: F2
Invalid MODE (DYNAMIC) on line 6
CALL: 9A4BL
TIME_ON: 185900
QSO_DATE: 20220416
MODE: DYNAMIC
SUBMODE: VARA HF
BAND: 15M
FREQ: 21.141
BAND_RX: 15M
FREQ_RX: 21.141
PROP_MODE: F2
Invalid MODE (DYNAMIC) on line 38
CALL: W9TD
TIME_ON: 003204
QSO_DATE: 20220505
MODE: DYNAMIC
SUBMODE: VARA HF
BAND: 20M
FREQ: 14.10425
PROP_MODE: F2
Invalid MODE (DYNAMIC) on line 39
CALL: WD6BNY
TIME_ON: 011100
QSO_DATE: 20220427
MODE: DYNAMIC
SUBMODE: VARA HF
BAND: 40M
FREQ: 7.10425
BAND_RX: 40M
FREQ_RX: 7.10425
PROP_MODE: F2
No records to upload
Final Status: No QSOs written(8)
I checked, and I have TQSL Version 2.6.4, and Configuration Data Version
11.20, which are reported to be the latest available.
Will TQSL have to be updated so that Vara HF will be able to be uploaded to
LoTW?
TNX ES 73,
Bob WB2NVR
Bob Schaps, WB2NVR
10 Club Pointe Drive
White Plains, NY 10605-4463
914-347-7331 (H/O)
914-262-3535 (C)


Re: VARA AC contacts

Bob WB2NVR
 

Hi Dave –

 

I changed the Mode for my VarAC contacts from DATA to VARA HF.

 

When I try to upload these Qs to LoTW, I get the following error:

 

TQSL Version 2.6.4 [v2.6.4]

Signing using Callsign WB2NVR, DXCC Entity UNITED STATES OF AMERICA

 

Invalid MODE (DYNAMIC) on line 5

CALL: 4Z1AC

TIME_ON: 023036

QSO_DATE: 20220625

MODE: DYNAMIC

SUBMODE: VARA HF

BAND: 40M

FREQ: 7.105

PROP_MODE: F2

 

Invalid MODE (DYNAMIC) on line 6

CALL: 9A4BL

TIME_ON: 185900

QSO_DATE: 20220416

MODE: DYNAMIC

SUBMODE: VARA HF

BAND: 15M

FREQ: 21.141

BAND_RX: 15M

FREQ_RX: 21.141

PROP_MODE: F2

 

 

 

Invalid MODE (DYNAMIC) on line 38

CALL: W9TD

TIME_ON: 003204

QSO_DATE: 20220505

MODE: DYNAMIC

SUBMODE: VARA HF

BAND: 20M

FREQ: 14.10425

PROP_MODE: F2

 

Invalid MODE (DYNAMIC) on line 39

CALL: WD6BNY

TIME_ON: 011100

QSO_DATE: 20220427

MODE: DYNAMIC

SUBMODE: VARA HF

BAND: 40M

FREQ: 7.10425

BAND_RX: 40M

FREQ_RX: 7.10425

PROP_MODE: F2

 

No records to upload

Final Status: No QSOs written(8)

 

 

I checked, and I have TQSL Version 2.6.4, and Configuration Data Version 11.20, which are reported to be the latest available.

 

Will TQSL have to be updated so that Vara HF will be able to be uploaded to LoTW?

 

TNX ES 73,

 

Bob WB2NVR

 

Bob Schaps, WB2NVR

10 Club Pointe Drive

White Plains, NY  10605-4463

 

914-347-7331 (H/O) 

914-262-3535  (C)  

 


Commander Connection to Kenwood TS-590S

John-WA7ZXD
 

I have used Commander for several years until I upgraded to Windows 11 on my PC.  I have not been able to connect senses December 2021.  I tried the updated Silicon Labs driver and have had several back and forth emails with them. I have tried to use a PC specialist to come to my house to fix it.  Spent $350 but no fix.  I have currently had a retired friend who spent 40 years in Silicon valley working on MS programs, no fix. I am 80 years old and would dearly like to get it running again.  Also I can no longer connect to the Kenwood radio control program on my PC. 

Any suggestions would be appreciated.  


LogPublisher 1.2.4 is available

Volker Rose
 

This release

  • corrects a defect that prevented logbook upload to QRZ.com for users without paid QRZ.com subscription (adaption to QRZ.com's changes). Tnx to George AB4KN

Update instructions:

Update your firewall and anti-malware applications to consider LogPublisher.exe, LogPublisherUpdater.exe and OnAir.exe to be safe.

LogPublisher 1.2.4 is available via LogPublishers's update feature (New ? - button).

For more information about LogPublisher visit http://www.dl9ho.de/LogPublisher/LogPublisher.htm

Full release is available at: http://www.dl9ho.de/adidl.html

73,
Volker, DL9HO

Other Add on for DXLAB (interoperation with SpotCollector / DXKeeper / WinWarbler / Commander):
SpotSpy - extends SpotCollector to support visible and audible alarms

For more information about SpotSpy visit http://www.dl9ho.de/SpotSpy/SpotSpy.htm


Re: VARA AC contacts

Rick Murphy
 

Just to make it clear, if you're talking about VarAC  - that's an application, not a mode.

Having an ADIF mode for VarAC would be equivalent to having an ADIF mode for WSJT-X. 
73,
    -Rick

On Sat, Jul 16, 2022 at 1:26 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

I wonder what mode is being used to log VaraAC contacts?  Is an ADIF mode for it in the future?

+ ADIF 3.1.3 added a new DYNAMIC mode, with 4 submodes:

VARA HF

VARA SATELLITE

VARA FM 1200

VARA FM 9600


+ DXKeeper version 16.6.5 added each of these to the Mode selectors in the Capture window and the Main window's "Log QSOs" tab:

VARA HF

VARA SATELLITE

VARA FM 1200

VARA FM 9600

+ See

https://www.dxlabsuite.com/dxkeeper/ReleaseNotes/1665.txt

+ These new modes are imported from and exported to ADIF and tab-delimited files as specified in ADIF 3.1.3.

+ Note that you have control over which modes appear in DXKeeper's Mode selectors:

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

        73,

               Dave, AA6YQ








--
Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA


Re: Incorrect myQTH submitted to LOTW

w2eck
 

Dave & Joe
Thanks for help, problem solved and all Q's uploaded with correct QTH

73 Paul
w2eck


Re: Importing a Large DX4Win Log

Rick Heinrich
 

Dave,

I LOVE homework assignments... ;)

Thanks for your help, guidance, and patience.  I think both our hopes are that this dialog will help someone else.

Rick N0YY


Re: Importing a Large DX4Win Log

Dave AA6YQ
 

+ AA6YQ comments below

Unreal especially when you think about the hoops we have to jump through to use LOTW. Glad the user side is under control but the league side is..........lacking.

+ When downloading credits from the ARRL's DXCC system,

- DXCC credits generated from LoTW confirmations are 100% accurate; this is an unsung benefit of LoTW

- DXCC credits generated from QSL Card submissions are about 75% accurate, with inaccuracies caused by data entry errors and shortcuts.


+ DXKeeper's automation will automatically link downloaded DXCC credits to QSOs that exactly match

+ DXKeeper's automation provides assistance for manually linking downloaded DXCC credits to QSOs that don't exactly match.

+ While the process can take time if you have many DXCC credits, to my knowledge, no one who tried has ever failed to link all of their downloaded DXCC credits to their logged QSOs:

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

73,

Dave, AA6YQ


Re: Importing a Large DX4Win Log

W0MU
 

Unreal especially when you think about the hoops we have to jump through to use LOTW.  Glad the user side is under control but the league side is..........lacking.

W0MU

On 7/15/2022 3:14 PM, Joe Subich, W4TV wrote:

On 2022-07-15 2:15 PM, Rick Heinrich wrote:

Somewhere it appears that the paper cards may not have found their home in LoTW for credit.  Only now with the transition from DX4Win
to DXK this has come to light.
LotW linking for card credits is very sloppy due to "shortcuts" taken
by ARRL staff when they (manually) enter card data into the DXCC records
and those records are then merged with LotW status.

1) times are often not entered and dates may not even be accurate.
2) very old credits (pre "computerization" in the 1990s) may not
   even include the entire callsign.  Those "QSOs" will also only
   be good for mode unless they were for a single band DXCC - in
   which case they will only be good for the band.

One can go to the "Awards" tab in LotW, select DXCC, then select
Challenge, and "View All Credits" to see each of the Challenge
(entity-band) credits.  Similarly, one can select Mixed, Phone,
CW or Digital to see each of the entity-mode credits.  If the
credit has a *number* (the "country number") instead of a callsign,
it is not possible to automatically link that credit to a QSO in
DXKeeper ... there will be no callsign in the LotW record, there
will be no band or mode (depending on the award), and the date
will be totally fictitious (e.g., my Mixed credit for Abu Ail
shows: Worked:002, Date 1975-01-01 ... even though I was still
in school and not working DX in those days).

Many of my "early" card confirmations are similar.  The LotW records
are completely garbage ... remarkable for their lack of accurate data!

73,

   ... Joe, W4TV



On 2022-07-15 2:15 PM, Rick Heinrich wrote:
Dave,

Thanks for the assessment.  I am doing some additional research on the DX4Win and LoTW QSL confirmations.  I submitted several hundred QSLs to a card checker and submitted the subsequent application.  Somewhere it appears that the paper cards may not have found their home in LoTW for credit.  Only now with the transition from DX4Win to DXK this has come to light.

More research required...  This will manifest itself more in band countries than honor roll totals.

Thanks again,
Rick N0YY