Date   
Re: DXK log page

Richard Clare
 

You need to put your cursor on the horizontal line in the left hand column and move it a little bit up or down to increase or decrease the height of the line. Richard wb6ewm 


On Apr 7, 2019, at 7:39 AM, Jim Denneny <57JNDenneny@...> wrote:

I mean heigth of rows in log display.  Could not find how to restore original heigth in CONFIG or WIKI.  This never happend B4

Jim K7EG

Re: DXK log page

Jim Denneny
 

I mean heigth of rows in log display.  Could not find how to restore original heigth in CONFIG or WIKI.  This never happend B4

Jim K7EG

DXK log page

Jim Denneny
 

The list of recent qso's at bottom of log page has changed.  The list entries were about 1/4 inch wide showing several recent qso's.  Suddenly, the window qso entries are much wider displaying last two qso's.  How do I restore this window?

Jim K7EG

Re: Commander and Ftdx3000

ART W2NRA
 

Ignore my email. I sent it to the wrong place. That’s what happens when you try to put together a solution to a problem on your phone. Sorry, Guys!

73, Art, W2NRA

On Apr 6, 2019, at 10:20 PM, ART W2NRA via Groups.Io <w2nra@...> wrote:

Go to this link:


Select:


73, Art, W2NRA

On Apr 5, 2019, at 4:19 PM, mitchhunt7 via Groups.Io <mitchhunt7@...> wrote:

Hi I am currently running DXLab suite with my Yeasu ftdx3000. I was wondering if there is a way to configure the commander to power the radio on and off. Thanks! 
Mitch 
KE0UAS 



Sent from my U.S.Cellular© Smartphone

Re: Need a little help correcting a couple of Qs previously submitted to LoTW

Dave AA6YQ
 

* more AA6YQ comments below

Tnx, Dave, for such an elegant -and amazingly simple- solution.

* By default, TQSL rejects QSOs that have already been submitted to LoTW because some users were resubmitting their entire log each
time they worked a few more stations; at one point, more than 50% of the QSOs being submitted were already submitted.

* However, when it's necessary to resubmit a small number of QSOs, TQSL's policy can be overridden; that's what the " Permit
uploading of QSOs already uploaded to LotW" option does.

73,

Dave, AA6YQ

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Saturday, April 6, 2019 5:48 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Need a little help correcting a couple of Qs previously submitted to LoTW

+ AA6YQ comments below

I've 3 or 4 Qs I need to correct and resubmit to LoTW. I've had a look at the LoTW FAQ but these particular Qs seem to deal with
items not mentioned.
Specifically, I need to change the mode and propagation from 'SAT' and '(whatever the sat's name is)' to 'blank field' and 'blank
field'. In another, I need to correct the data in the 'Grid 2' field. For that Q, I did edit the field and attempted to resubmit,
but LoTW rejected it as a duplicate. Could someone point me on the right path to clear this up?

+ On the "QSL Configuration" window's LoTW tab, check the "Permit
+ uploading of QSOs already uploaded to LotW" box, and then resubmit
your corrected QSOs.

73,

Dave, AA6YQ









---
This email has been checked for viruses by AVG.
https://www.avg.com

Re: Need a little help correcting a couple of Qs previously submitted to LoTW

K5ZM
 

Tnx, Dave, for such an elegant -and amazingly simple- solution. You da man.
Again!

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Saturday, April 6, 2019 5:48 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Need a little help correcting a couple of Qs previously
submitted to LoTW

+ AA6YQ comments below

I've 3 or 4 Qs I need to correct and resubmit to LoTW. I've had a look at
the LoTW FAQ but these particular Qs seem to deal with items not mentioned.
Specifically, I need to change the mode and propagation from 'SAT' and
'(whatever the sat's name is)' to 'blank field' and 'blank field'. In
another, I need to correct the data in the 'Grid 2' field. For that Q, I did
edit the field and attempted to resubmit, but LoTW rejected it as a
duplicate. Could someone point me on the right path to clear this up?

+ On the "QSL Configuration" window's LoTW tab, check the "Permit
+ uploading of QSOs already uploaded to LotW" box, and then resubmit
your corrected QSOs.

73,

Dave, AA6YQ

Re: Commander and Ftdx3000

ART W2NRA
 

On Apr 5, 2019, at 4:19 PM, mitchhunt7 via Groups.Io <mitchhunt7@...> wrote:

Hi I am currently running DXLab suite with my Yeasu ftdx3000. I was wondering if there is a way to configure the commander to power the radio on and off. Thanks! 
Mitch 
KE0UAS 



Sent from my U.S.Cellular© Smartphone

Re: Need a little help correcting a couple of Qs previously submitted to LoTW

Dave AA6YQ
 

+ AA6YQ comments below

I've 3 or 4 Qs I need to correct and resubmit to LoTW. I've had a look at the LoTW FAQ but these particular Qs seem to deal with
items not mentioned. Specifically, I need to change the mode and propagation from 'SAT' and '(whatever the sat's name is)' to 'blank
field' and 'blank field'. In another, I need to correct the data in the 'Grid 2' field. For that Q, I did edit the field and
attempted to resubmit, but LoTW rejected it as a duplicate. Could someone point me on the right path to clear this up?

+ On the "QSL Configuration" window's LoTW tab, check the "Permit uploading of QSOs already uploaded to LotW" box, and then resubmit
your corrected QSOs.

73,

Dave, AA6YQ

Need a little help correcting a couple of Qs previously submitted to LoTW

K5ZM
 

Hi all…

 

I’ve 3 or 4 Qs I need to correct and resubmit to LoTW. I’ve had a look at the LoTW FAQ but these particular Qs seem to deal with items not mentioned. Specifically, I need to change the mode and propagation from ‘SAT’ and ‘(whatever the sat’s name is)’ to ‘blank field’ and ‘blank field’. In another, I need to correct the data in the ‘Grid 2’ field. For that Q, I did edit the field and attempted to resubmit, but LoTW rejected it as a duplicate. Could someone point me on the right path to clear this up?

 

Tnx es 73

 

Ian, K5ZM

Re: UDP address on WSJT-X panel on the Configuration window's Spot Sources

g4wjs
 

On 06/04/2019 20:43, Dave AA6YQ wrote:
* As I said the last time this came up here, the current version of SpotCollector supports one local instance of WSJT-X. From my experience extending Commander to interact with FlexRadio's SmartSDR via UDP, I know that lots of bulletproofing is required to deal with more complex network topologies. This thread is the first expression of user need for additional capability. If I can address it without compromising what I'm currently in the middle of, I will do so; otherwise, it will go "on the list".
Dave,

it is a basic setup for a server (SpotCollector) to bind to the wildcard address 0.0.0.0, not doing so will disallow many perfectly simple and valid configurations. Binding to a specific interface like the local loopback interface is normally only done for testing, and even then rarely.

Related to this, what exactly does SpotCollector do with the address specified in the WSJT-X spot source configuration group?



--
73

Bill

G4WJS.

Re: UDP address on WSJT-X panel on the Configuration window's Spot Sources

Dave AA6YQ
 

* AA6YQ comments below

On 06/04/2019 08:27, Dave AA6YQ wrote:
+ I think I know what must be changed, but I'd like to do more testing here before sending you a version to test.
Hi Dave,

it appears that SpotCollector is binding to the local loopback network interface regardless of the address specified in the SpotCollector configuration. TBH I do not understand why an address needs to be specified at all, normally a server binds to the wildcard address
0.0.0.0 which means that it will traffic through any enabled network interface on the local machine. The only reason for binding to a specific network interface would be to restrict traffic from certain subnets.

OTOH optionally specifying a multicast group address to join is a desirable feature that SpotCollector should implement so that the full capabilities of the WSJT-X protocol can be realized.

* As I said the last time this came up here, the current version of SpotCollector supports one local instance of WSJT-X. From my experience extending Commander to interact with FlexRadio's SmartSDR via UDP, I know that lots of bulletproofing is required to deal with more complex network topologies. This thread is the first expression of user need for additional capability. If I can address it without compromising what I'm currently in the middle of, I will do so; otherwise, it will go "on the list".

* While we're discussing UDP, I hope that the next version of WSJT-X will accept a UDP message bearing a "K1JT Mode" to which WSJT-X should switch and a callsign to be placed in the WSJT-X "DX Call" box, after which the "Generate Std Msgs" function would be invoked. This would enabled SpotCollector to respond to the double-clicking of a Spot Database Entry for a station operation in a "K1JT mode" by directing WSJT-X to switch to the correct mode, populate the "DX Call" box with the correct callsign. The user can then confirm reception of the station, choose a transmit frequency, and initiate a call.

73,

Dave, AA6YQ

Re: access to DXCC credits

Dave AA6YQ
 

+ AA6YQ comments below

I think maybe my DXCC Account Number is the problem. Here's what I get:

DXCC Account # 1

Downloaded DXCC Credit information specifies no station callsigns Downloaded DXCC Credit information contains no status table

+ The URL that you posted in

<https://groups.io/g/DXLab/message/185048>

+ shows that your DXCC account number is 1. This doesn't mean that you hold the first ever DXCC account; the DXCC account number for most users is 1 or 2.

+ Please follow steps 1-5 in

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

+ and then click on the "View Award Credit Matrix" hyperlink; does your web browser display your Award Credit Matrix?

73,

Dave, AA6YQ

Re: Download DXCC QSL List

Pete Smith
 

I think maybe my DXCC Account Number is the problem.  Here's what I get:

DXCC Account # 1

Downloaded DXCC Credit information specifies no station callsigns
Downloaded DXCC Credit information contains no status table

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 4/6/2019 12:03 AM, Dave AA6YQ wrote:

* There's a faster way to accomplish your objective than what's described below:

1. follow the procedure given in

<https://groups.io/g/DXLab/message/184862>

2. in the "DXCC, Challenge, & Toplist" panel on the Main window's "Check Progress" tab, click the "Compare" button; this will display a report listing discrepancies between the DXCC Credit shown in your ARRL DXCC Record, and the DXCC Credit shown in DXKeeper.

3. for each QSO that the discrepancy report shows as having been granted DXCC Credit to an LoTW confirmation,

a. locate the QSO in the Log Page Display

b. right-click, and select "Update from LoTW" from the pop-up menu

        73,

             Dave, AA6YQ


+ AA6YQ comments below

Those are the instructions I was working from.

The reason for this exercise is that my LOTW account says I have 4 more DXCC credits than DXK does.  I would like to identify the discrepancies in a relatively efficient manner.

+ That can be accomplished by depressing the CTRL key while clicking the "Sync LoTW QSLs" button. DXKeeper will direct LoTW to report all of your QSOs that are confirmed via LoTW, identifying those to which DXCC Credit has been granted. DXKeeper will then review that report, and update your logged QSOs to reflect LoTW confirmation and DXCC Credit granted to LoTW confirmations.

+ With a large number of QSOs confirmed in LoTW, the above procedure can take a long while. If the words "not responding" appear in the title bar of DXKeeper's Main window, ignore them; that's Windows speak for "waiting for LoTW to assemble and download the requested report".

+ Note that QSL card confirmations to which DXCC Credit has been granted will not be reported by LoTW.

         73,

            Dave, AA6YQ






---
This email has been checked for viruses by AVG.
https://www.avg.com





Re: UDP address on WSJT-X panel on the Configuration window's Spot Sources

g4wjs
 

On 06/04/2019 12:58, g4wjs wrote:
normally a server binds to the wildcard address 0.0.0.0 which means that it will traffic through any enabled network interface on the local machine.
Hi Dave,

oops dropped an important word there:

... normally a server binds to the wildcard address 0.0.0.0 which means that it will *accept* traffic through any enabled network interface on the local machine. ...



--
73

Bill

G4WJS.

Re: UDP address on WSJT-X panel on the Configuration window's Spot Sources

g4wjs
 

On 06/04/2019 08:27, Dave AA6YQ wrote:
+ I think I know what must be changed, but I'd like to do more testing here before sending you a version to test.
Hi Dave,

it appears that SpotCollector is binding to the local loopback network interface regardless of the address specified in the SpotCollector configuration. TBH I do not understand why an address needs to be specified at all, normally a server binds to the wildcard address 0.0.0.0 which means that it will traffic through any enabled network interface on the local machine. The only reason for binding to a specific network interface would be to restrict traffic from certain subnets.

OTOH optionally specifying a multicast group address to join is a desirable feature that SpotCollector should implement so that the full capabilities of the WSJT-X protocol can be realized.



--
73

Bill

G4WJS.

Re: UDP address on WSJT-X panel on the Configuration window's Spot Sources

Carl - WC4H
 

No problem Dave.  Let me know.  

Thanks.
Carl - WC4H

Re: UDP address on WSJT-X panel on the Configuration window's Spot Sources

Dave AA6YQ
 

+ AA6YQ comments below

When I click on the check box to "Enable" the UDP for WSJt-X I get this:
Cannot connect to WSJTX via UDP address 192.168.3.102 port 2237 because address is not available from local machine.

So I can go no further in testing. I have opened port 2237 on the other PC, I can ping from either PC to the other, I even forwarded the port on the router which should not be necessary for the internal network.

So, I guess that ends that unless the Check Box let's me enable it.

+ I think I know what must be changed, but I'd like to do more testing here before sending you a version to test.

73,

Dave, AA6YQ

QRZ's XML service is down <eom>

Dave AA6YQ
 

Re: Download DXCC QSL List

Stan Gammons
 

On 4/5/19 11:15 PM, Dave AA6YQ wrote:
* more AA6YQ comments below

+ Note that QSL card confirmations to which DXCC Credit has been granted will not be reported by LoTW.
Is that because another system/method is used to process cards? I think doing it that way is a bit of a pain. But, it is what it is I suppose.

* The only way to obtain DXCC Credit granted to QSL card confirmations is for DXKeeper to download your Award Credit Matrix from the ARRL, and extract the confirmation and award credit information. See

<https://www.dxlabsuite.com/dxlabwiki/ManageDXCCCredits>
Oh.  I misunderstood what you were saying.   That's the way I manage my DXCC credits, but the way I do it is manual/more difficult method.   Will try to not do that next time...

Thanks Dave!


73

Stan
KM4HQE

Re: Download DXCC QSL List

Dave AA6YQ
 

* more AA6YQ comments below

+ Note that QSL card confirmations to which DXCC Credit has been granted will not be reported by LoTW.
Is that because another system/method is used to process cards? I think doing it that way is a bit of a pain. But, it is what it is I suppose.

* The only way to obtain DXCC Credit granted to QSL card confirmations is for DXKeeper to download your Award Credit Matrix from the ARRL, and extract the confirmation and award credit information. See

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

73,

Dave, AA6YQ