Date   

Re: DX Keeper - LOTW QSL sync problem

Fred Roberts
 

Dave,
     I only have 1 MyQTHID set. It is set to my call, WB4QOC.
Fred
PS....thank you for your very quick response!





Sent from my phone.....Fred


On Sat, Mar 13, 2021, 6:26 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Addendum.....the only other clue that i have is that on the Log QSOs page, in the QSL section, I have a flashing blue "my QTH" message in front if the drop down box. If I press the down arrow, I can choose my call sign, but the drop down box reverts to a nil entry....it will not permit me to populate that field....sorry for not including that in the first post.

+ On the Main window's "my QTHs" tab, how many QTHs have you defined?

       73,

              Dave, AA6YQ









Re: DX Keeper - LOTW QSL sync problem

Dave AA6YQ
 

+ AA6YQ comments below

Addendum.....the only other clue that i have is that on the Log QSOs page, in the QSL section, I have a flashing blue "my QTH" message in front if the drop down box. If I press the down arrow, I can choose my call sign, but the drop down box reverts to a nil entry....it will not permit me to populate that field....sorry for not including that in the first post.

+ On the Main window's "my QTHs" tab, how many QTHs have you defined?

73,

Dave, AA6YQ


Re: DX Keeper - LOTW QSL sync problem

Dave AA6YQ
 

+ AA6YQ comments below

I am very new to the DX labs suite of programs....actually still setting it up with the help of a long time user of the programs, and one of my Elmers. Unfortunately, he didn't convince me to start using DXkeeper until I had 10,000+ QSOs in the log. I imported my log in ADIF format with no problems, and then I tried the Sync LoTW QSLs button; the program waited 2 or 3 seconds and then I received the Program not responding error message, as the previous poster did.

The Sync LoTW QSOs button works, as does the Update from LoTW button - (which by the way for 10,000+ records took about 8 hours). Can you help a newbie to the group with an idea as to what I've done wrong in setting things up?

+ First, the appearance of "Not responding" in DXKeeper's Title bar means "waiting for input or output" - in this case, waiting for LoTW to supply an ADIF file specifying all of your QSLs. When this "Micosoft-speak message" appears, ignore it and let the operation run to completion.

+ The "Update from LoTW" function directs LoTW to report the status of each QSO in the Log Page Display - one at a time (and is thus much slower). If you've already done this for all 10,000 of your logged QSOs, there is no need to invoked "Sync LoTW QSLs" with the date beneath it set to the beginning of time. On the Main window's QSL tab,

1. set the "QSO Via" panel to LoTW

2. double-click the date under the "Sync LotW QSLs" button

3. In the small "LoTW QSL Synchronization" window that appears, change the date to

2021-01-01

and click the OK button

4. click the "Sync LotW QSLs" button

+ This will direct LotW to report any QSLs that have arrived since the beginning of the year, providing some overlap in case new QSLs have arrived since you completed the "Update from LoTW" operation above.

+ From now on, just click "Sync LoTW QSLs", and your Log will be updated to reflect new LoTW confirmatins.

73,

Dave, AA6YQ


Re: DX Keeper - LOTW QSL sync problem

Fred Roberts
 

Addendum.....the only other clue that i have is that on the Log QSOs page, in the QSL section, I have a flashing blue "my QTH" message in front if the drop down box. If I press the down arrow, I can choose my call sign, but the drop down box reverts to a nil entry....it will not permit me to populate that field....sorry for not including that in the first post.
73,
Fred
WB4QOC


Re: DX Keeper - LOTW QSL sync problem

Fred Roberts
 

Dave,
       I am very new to the DX labs suite of programs....actually still setting it up with the help of a long time user of the programs, and one of my Elmers. Unfortunately, he didn't convince me to start using DXkeeper until I had 10,000+ QSOs in the log. I imported my log in ADIF format with no problems, and then I tried the Sync LoTW QSLs button; the program waited 2 or 3 seconds and then I received the Program not responding error  message, as the previous poster did. The Sync LoTW QSOs button works, as does the Update from LoTW button - (which by the way for 10,000+ records took about 8 hours). Can you help a newbie to the group with an idea as to what I've done wrong in setting things up?
Thanks,
Fred
WB4QOC


Re: Spotcollector Message

Dave AA6YQ
 

+ AA6YQ comments below

Sorry This is the Message that I get after 10 minutes after started Spotcolletor.

The Spot Database cannot be accessed for compaction:
Permissin denied.

Anyone a idea what i doing wrong?

+ Windows is preventing SpotCollector from compacting the Spot Database, probably because Windows erroneously considers one of the files involved to be still "in use". As a first step, try rebooting Windows.

73,

Dave, AA6YQ


Re: DXK Popup Window

Dave AA6YQ
 

+ AA6YQ comments below

I use DXKeeper for my main log.
I'm doing incoming QSLs from Buro today and every so often I get a pop up window when I hit to check a QSL card was received. Anybody know what that window is for or what it does? The window says, "Send this QSL card to the CQ WPX desk (LZ6-80M, LZ6-CW)! THe window has the small X in the upper right corner, and an OK button.
The message isn't always the same depending on the call.
That pop-up tells you the particular card qualifies for an award (or advances your progress toward an award). The example you cite indicates this is your first LZ6 prefix on 80M and CW.

+ The award is one that you've configured DXKeeper to pursue (via its Configuration window's Awards tab). If you don't want these "submission reminders" to appear when you mark a QSO as confirmed via QSL card, uncheck the "Submission reminder" box in the "Log Settings" panel on the Configuration window's Log tab.

73,

Dave, AA6YQ


Re: DXLab support for remotely controlling a FlexRadio Signature transceiver via SmartLink

dxradio33
 

I consistently Commander with a remote Flex 6600 from my home station.  There is no way to set it up using the Flex interface that I am aware of, instead I use a Flex virtual serial port (CAT) setup on the remote Flex of course and I configure my local Commander as follows:  Radio = KENWOOD , Interrogation is checked ,  100 milliseconds Command Interval , 1 Scan Dwell check mark in “Accept ‘Dual Rcv On’ directives, a check mark in Accept ‘Dual Rcv Off’ Directives and finally a checkmark in Use Multiple Monitors which you may or may not have…..

 

Good luck

 

Joe

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Friday, March 12, 2021 17:59
To: DXLab@groups.io
Subject: Re: [DXLab] DXLab support for remotely controlling a FlexRadio Signature transceiver via SmartLink

 

+ AA6YQ comments below

A little late to the party but...

Has anyone successfully created a remote connection between DX Commander and a remote 6xxx?

+ I requested a technical description of SmartLink from Flex more than a year ago. Still waiting.

     73,

            Dave, AA6YQ

 


Re: DXK Popup Window

Joe Subich, W4TV
 

No, it's simply an advisory message telling you to put the card
aside for generating your next submission. You could potentially
set the "WPX vfy" box to "S" to indicate that card/LotW confirmation
should be submitted if you don't have a separate place to put cards
"to be submitted".

73,

... Joe, W4TV

On 2021-03-13 9:21 AM, Robert T wrote:
So rather than closing out this box with the X, I'd hit the OK button to allow this to be counted.
RET
<pre>1</pre>

On 03/13/2021 9:08 AM Joe Subich, W4TV <lists@subich.com> wrote:

That pop-up tells you the particular card qualifies for an award
(or advances your progress toward an award). The example you cite
indicates this is your first LZ6 prefix on 80M and CW.

73,

... Joe, W4TV


On 2021-03-13 8:18 AM, Robert T wrote:
I use DXKeeper for my main log.
I'm doing incoming QSLs from Buro today and every so often I get a pop up window when I hit to check a QSL card was received. Anybody know what that window is for or what it does? The window says, "Send this QSL card to the CQ WPX desk (LZ6-80M, LZ6-CW)! THe window has the small X in the upper right corner, and an OK button.
The message isn't always the same depending on the call.

Thanks,
Bob, K2RET



Re: DXK Popup Window

Robert T
 

So rather than closing out this box with the X, I'd hit the OK button to allow this to be counted.

RET

<pre>1</pre>

On 03/13/2021 9:08 AM Joe Subich, W4TV <lists@subich.com> wrote:


That pop-up tells you the particular card qualifies for an award
(or advances your progress toward an award). The example you cite
indicates this is your first LZ6 prefix on 80M and CW.

73,

... Joe, W4TV


On 2021-03-13 8:18 AM, Robert T wrote:
I use DXKeeper for my main log.
I'm doing incoming QSLs from Buro today and every so often I get a pop up window when I hit to check a QSL card was received. Anybody know what that window is for or what it does? The window says, "Send this QSL card to the CQ WPX desk (LZ6-80M, LZ6-CW)! THe window has the small X in the upper right corner, and an OK button.
The message isn't always the same depending on the call.

Thanks,
Bob, K2RET



Re: Spotcollector Message

Rien Aarden
 

Sorry This is the Message that I get after 10 minutes after started Spotcolletor.

The Spot Database cannot be accessed for compaction:
Permissin denied.

Anyone a idea what i doing wrong?

Tnx Rien, PA7RA 


Spotcollector Message

Rien Aarden
 



After a 10 minutes when I start Spotcollector I get this message.
What  is wrong ? someone any idea?

Tnx Rien, PA7RA 


Re: DXK Popup Window

Joe Subich, W4TV
 

That pop-up tells you the particular card qualifies for an award
(or advances your progress toward an award). The example you cite
indicates this is your first LZ6 prefix on 80M and CW.

73,

... Joe, W4TV

On 2021-03-13 8:18 AM, Robert T wrote:
I use DXKeeper for my main log.
I'm doing incoming QSLs from Buro today and every so often I get a pop up window when I hit to check a QSL card was received. Anybody know what that window is for or what it does? The window says, "Send this QSL card to the CQ WPX desk (LZ6-80M, LZ6-CW)! THe window has the small X in the upper right corner, and an OK button.
The message isn't always the same depending on the call.
Thanks,
Bob, K2RET


DXK Popup Window

Robert T
 

I use DXKeeper for my main log.
I'm doing incoming QSLs from Buro today and every so often I get a pop up window when I hit to check a QSL card was received. Anybody know what that window is for or what it does? The window says, "Send this QSL card to the CQ WPX desk (LZ6-80M, LZ6-CW)! THe window has the small X in the upper right corner, and an OK button.
The message isn't always the same depending on the call.

Thanks,
Bob, K2RET


Re: DXLab support for remotely controlling a FlexRadio Signature transceiver via SmartLink

Björn (SM0SBL)
 
Edited

It is not only your own radio you are putting at risk when you expose a doubtfully protected port to internet.
I doubt Flex is using anything proprietary as TCP stack, and if they did it would be even more dangerous.
My guess is if is linux is running inside the box.
I also guess you don't receive security updates to the equipment connected to internet on a regular basis? By regular I mean once a month or so.
An enormous amount of security holes are patched each month on all systems normally used, linux as well as windows.

What you risk when exposing a potentially unsafe port is for autonomous bots getting a foothold on your connected system which might lead to ether that you will get all your files on all locally connected internal computer encrypted by ransomware secretly, and often autonomously, spread internally on your local network, or your equipment might become part of a botnet used to attack and hack other systems in the world such as government organizations or the vaccine supply chain or using your equipment for other criminal activity. Or your equipment may be part of spreading child pornograpy or worse...

Unfortunately, IMHO, it is no longer sufficient to think that you personally are not interesting for cyber criminals or that you don't have anything valuable to safeguard.
I realize It is, or should be, the responsibility of the supplier of the equipment to make sure patches are available at a regular basis and the individuals owning the equipment to actually apply the patches.

OpenVPN is not to hard to set up nowadays, and are often available in routers. If it is to difficult for an individual maybe he/she could get help from a fellow ham or someone else around.

I would really not recommend leave an interface open, unencrypted and unauthorized using a well accepted system.

This post is NOT meant as a personal attack on anyone not using a secure connection. Please to read it as such!
The idea that security is not so important for different reasons are unfortunately well spread in the public domain.
This post is intended as, hopefully, an eyeopener for whom it may concern.

 EDIT: I incorrectly remembered it was Larry who wrote about exposing the port insecurely. Removed names and made the post more generic...

Regards
SM0SBL, Björn
--
Björn, SM0SBL


Re: Satellite Modes

Dave AA6YQ
 

+ AA6YQ comments below

Something got stuck in my head a while back and I made a list:
https://docs.google.com/spreadsheets/d/1oJV0Bv24mHhq_eICUp3L6g4pTy-wItUWfkyT-Uf5z0g/edit#gid=0

S band is a problem because, by IEEE's naming, amateurs have two bands
- 13 and 9 cm.

My research shows that 6 mm was designated "R" (not Q) by AMSAT-DL in the run-up to the ill-fated OSCAR 40 while IEEE calls it V ... but of course AMSAT used V for 2 m. It's all good.

I do have the citation for AMSAT's band designators on the page above but if I have a copy of the document ... I've misplaced it! The title is listed, though.

The reason for this was because the original modes, A (2 up, 10 down), B (70 up, 2 down), J (2 up, 70 down) clearly wouldn't scale with the number of bands that OSCAR 40 (Phase 3D prior to launch) was to have and follow on spacecraft were expected to have. So, wisely, they went with a letter for each band and, as Suitbert notes, the first letter is the uplink, the second is the downlink.

Sadly, as is often the case, old timers couldn't let go and insisted on using the old single-letter modes leading to mixed messages in AMSAT publications.

I would suggest mapping the uplink and downlink bands entered by the operator to those bands' appropriate letter but allow the operator to override the default should they wish to use the obsolete designator.

+ If on startup the next version of DXKeeper finds a file named SatelliteModes.txt in its Databases folder, the Satellite Mode selectors are initialized from the satellite modes specified in this file, one line per mode; otherwise, the Satellite Mode selectors are loaded with a default set of Satellite Modes as provided in previous versions of DXKeeper, augmented by SX.

73,

Dave, AA6YQ


Re: Satellite Modes

Peter Laws / N5UWY
 

On Thu, Mar 11, 2021 at 12:54 AM <suitbert@monz-online.de> wrote:

Newer satellite mode-names do use a combination of two letters, representing the up- and down-link band.
As there are: H 15m, T 10m, V 2m, U 70cm, L 23cm, S 13cm, C 6cm, X 3cm, K 1,2cm, Q 6mm
Something got stuck in my head a while back and I made a list:
https://docs.google.com/spreadsheets/d/1oJV0Bv24mHhq_eICUp3L6g4pTy-wItUWfkyT-Uf5z0g/edit#gid=0

S band is a problem because, by IEEE's naming, amateurs have two bands
- 13 and 9 cm.

My research shows that 6 mm was designated "R" (not Q) by AMSAT-DL in
the run-up to the ill-fated OSCAR 40 while IEEE calls it V ... but of
course AMSAT used V for 2 m. It's all good.

I do have the citation for AMSAT's band designators on the page above
but if I have a copy of the document ... I've misplaced it! The title
is listed, though.

The reason for this was because the original modes, A (2 up, 10 down),
B (70 up, 2 down), J (2 up, 70 down) clearly wouldn't scale with the
number of bands that OSCAR 40 (Phase 3D prior to launch) was to have
and follow on spacecraft were expected to have. So, wisely, they
went with a letter for each band and, as Suitbert notes, the first
letter is the uplink, the second is the downlink.

Sadly, as is often the case, old timers couldn't let go and insisted
on using the old single-letter modes leading to mixed messages in
AMSAT publications.

I would suggest mapping the uplink and downlink bands entered by the
operator to those bands' appropriate letter but allow the operator to
override the default should they wish to use the obsolete designator.

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


Re: DXKeeper Questions

Dave AA6YQ
 

I have identified and corrected the defect responsible for QSOs with start or end times of 00:00:00Z erroneously triggering the "you're changing a QSO already submitted to eQSL or LoTW" warning. The defect was a regression in a defect repair included with the current public release (15.9.9).

Thanks to all who reported this behavior, going back to Mike K6MKF, who initiated this thread! I've sent all of you a version of DXKeeper with the defect corrected; please let me know how it goes.

73,

Dave, AA6YQ


Re: DXKeeper - Copy to Clipboard - Frequency

Dave AA6YQ
 

+ AA6YQ comments below

If there is an option to control this, and I've missed it, I apologize.

Is there any way to set DXKeeper to not round the frequency up up when using "copy to clipboard" from the main log view?

+ Yes: In the "Log Page Display" panel on the Configuration window's Log tab, increase the specified "Frequency precision".


Even better would be a way to copy the dial frequency

+ Right click in Commander's Main VFO display, and select Copy from the pop-up menu.


Out of curiosity, into what are you pasting this information?

73,

Dave, AA6YQ


Re: DXLab support for remotely controlling a FlexRadio Signature transceiver via SmartLink

Dave AA6YQ
 

 + AA6YQ comments below
I'm controlling the Flex via SmartCAT works.  I'm not using the network API.  My interest is driving the radio based on SC.

+ SmartCAT is a primitive, Kenwood-like CAT protocol. The Flex API provides more functionality, and is faster. Being able to see active stations reported by SpotCollector  displayed on SmartSDR with color-coding for need and LoTW/eQSL participation is a boon for DXers.

     73,

              Dave, AA6YQ

3141 - 3160 of 203460