Date   

Re: DX Keeper and upload to LotW

Serge Bertuzzo
 

Thank you very much for your prompt response Dave.
While I made sure all of the software I was using was the latest version, I confess that I did not check for a recent version of the N1MM+ DXKeeper Gateway software. 
My apologies. I have downloaded the latest version and will try it out. 

Keep up the great work. 

73
Serge
VA3SB


Re: DxCommander and inadvertent Xmt

Dave AA6YQ
 

+ AA6YQ comments below

Hi - I was operating FT8 (new to it) for a bit. QSOs were logged with DxKeeper and everything seemed very streamlined. I left the computer configuration the same and simply turned off my radio and came back to it a day or so later. FT8 operation was fantastic...QSOs were being logged. It was very strange...I was actually getting involved in the FT8 as I had many contacting me and had to manage that by direct intervention. Anyway, after several QSOs I looked at the log and none had been logged even though the prompt to log came up for each (and there were several) and I clicked OK.
This is where the fun starts. It seemed as though I was getting inadvertent transmissions commanded by the WSJTX app. I would have to hit the power button on the radio as I could not figure out from the various screens why this was happening. I then shut down all the apps (WSJTX, Dxlab, etc) and did not power down the computer. When I restarted DxLab and commander only, as soon as commander connected with the radio, it would start to transmit. Again, I used the power button to stop the inadvertent transmission. I then turned the radio back on and the radio (Yaesu FT991A) showed a blinking transmission light (it was not transmitting, but maybe being commanded to transmit??). I then restarted everything...computer...radio. Now, I think SSB voice operation is ok - I have not checked FT8 operation again yet.
Any hints here? I would like to consistently record FT8 contacts (I think I missed a few) and switch to other modes easily. There are a lot of moving parts with all these apps so I am not sure I have a grasp on this.
Any help would be appreciated.

+ Hint 1: read the WSJT-X user manual in

https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.3.0-rc1_en.html

+ If you have questions, feel free to post them here, or on the WSJT-X support forum in

https://wsjtx.groups.io/g/main/messages


+ For QSOs logged in WSJT-X to be conveyed to DXKeeper, you must appropriately configure DXLab. Step-by-step instructions are here:

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


+ For the QSOs you logged before configuring DXLab to receive them, you can direct DXKeeper to import them from the ADIF file that WSJT-X maintains. In the WSJT-X File menu, run the "Open Log Directory" command. That will produce a Windows Explorer window containing the file

wsjt_log.adi

+ This file contains all QSOs logged with WSJT-X. If none of these QSOs have previously been recorded in DXKeeper, you can simply direct DXKeeper to import this file. Otherwise, you must enable "Duplicate checking" on the "Import QSOs" tab of DXKeeper's Main window before importing the above file; importing with duplicate checking enabled is a slow operation.

73,

Dave, AA6YQ


Re: DX Keeper and upload to LotW

Dave AA6YQ
 

+ AA6YQ comments below

I have looked around the documentation/archives and have not been able to find a solution to uploading QSOs to LotW using N1MM+ DXKeeper Gateway software. I am using all of the latest version of the software mentioned below.

I log all my qso's to DXKeeper. When using WSJT-X and JTAlert, I have the software set up so that it automatically logs the contacts to DX Keeper.
I also have DXKeeper set up so that any contact that is logged via the capture window is uploaded to LotW. I can see when this is happening as I see a window indicating that the QSO is being uploaded to LotW.
If I make a contact and then go to the LotW site I can verify that the qso has indeed been uploaded.
My issue is when I use DXKeeper and N1MM DXKeeper Gateway. When making qsos with N1MM (say in a CW contest) even though I do see that QSO's are being logged in DXKeeper, if I go to LotW I do not see the latest contact(s) with the stations that I just worked.

I thought I had everything set up properly in DXKeeper as it seems to work when using WSJT and JTAlert software. Perhaps uploading automatically to LotW does not work when using the N1MM+ DXKeeper Gateway program for some reason? Please let me know if you require any additional information on my setup.

Any guidance or assistance would be greatly appreciate. Thank you very much in advance.

+ Did you check the "Upload to LoTW" box on the N1MM-DXKeeper Gateway window's Main window?

+ If this box is not present, upgrade to version 1.2.1 of the Gateway, which is available here:

https://www.dxlabsuite.com/N1MM-DXKeeper/index.htm

73,

Dave, AA6YQ


DxCommander and inadvertent Xmt

Lance HP
 

Hi - I was operating FT8 (new to it) for a bit. QSOs were logged with DxKeeper and everything seemed very streamlined. I left the computer configuration the same and simply turned off my radio and came back to it a day or so later. FT8 operation was fantastic...QSOs were being logged. It was very strange...I was actually getting involved in the FT8 as I had many contacting me and had to manage that by direct intervention. Anyway, after several QSOs I looked at the log and none had been logged even though the prompt to log came up for each (and there were several) and I clicked OK.
This is where the fun starts. It seemed as though I was getting inadvertent transmissions commanded by the WSJTX app. I would have to hit the power button on the radio as I could not figure out from the various screens why this was happening. I then shut down all the apps (WSJTX, Dxlab, etc) and did not power down the computer. When I restarted DxLab and commander only, as soon as commander connected with the radio, it would start to transmit. Again, I used the power button to stop the inadvertent transmission. I then turned the radio back on and the radio (Yaesu FT991A) showed a blinking transmission light (it was not transmitting, but maybe being commanded to transmit??). I then restarted everything...computer...radio. Now, I think SSB voice operation is ok - I have not checked FT8 operation again yet.
Any hints here? I would like to consistently record FT8 contacts (I think I missed a few) and switch to other modes easily. There are a lot of moving parts with all these apps so I am not sure I have a grasp on this.
Any help would be appreciated.

Lance


DX Keeper and upload to LotW

Serge Bertuzzo
 

Hello to the group. 

I have looked around the documentation/archives and have not been able to find a solution to  uploading QSOs to LotW using N1MM+ DXKeeper Gateway software. I am using all of the latest version of the software mentioned below. 

I log all my qso's to DXKeeper. When using WSJT-X and JTAlert, I have the software set up so that it automatically logs the contacts to DX Keeper. 
I also have DXKeeper set up so that any contact that is logged via the capture window is uploaded to LotW. I can see when this is happening as I see a window indicating that the QSO is being uploaded to LotW. 
If I make a contact and then go to the LotW site I can verify that the qso has indeed been uploaded. 
My issue is when I use DXKeeper and N1MM DXKeeper Gateway. When making qsos with N1MM (say in a CW contest) even though I do see that QSO's are being logged in DXKeeper, if I go to LotW I do not see the latest contact(s) with the stations that I just worked. 

I thought I had everything set up properly in DXKeeper as it seems to work when using WSJT and JTAlert software. Perhaps uploading automatically to LotW does not work when using the N1MM+ DXKeeper Gateway program for some reason? Please let me know if you require any additional information on my setup. 

 Any guidance or assistance would be greatly appreciate. Thank you very much in advance.


73

Serge
VA3SB


Re: How Do I Designate a POTA QSO in DXK

Dave AA6YQ
 

+ AA6QY comments below

Dave - thanks for the tip, and yes the Generate Progress Report box is no longer greyed out. But now I get a popup msg saying "Unable to open the file C:\Dxlab\DXKeeper|Reports\W2ECK WWFF/POTA Progress Report 2021-03019.txt for output; a log report cannot be generated"

+ Is there a Reports folder in your DXKeeper folder?

73,

Dave, AA6YQ


Re: Sorting Log for POTA in Comments Field

Mark Robinson
 

Thanks Joe,

That worked

73 Mark N1UK

On 19-Mar-21 3:33 PM, Joe Subich, W4TV wrote:

I think the syntax would be

COMMENT = "*POTA*"

but it didn't find anything. So I must have something wrong. Can you
point me in the right direction
COMMENT LIKE '*POTA*'

Note: Like instead of = for "wild card" searches
      single not double quotes for alpha searches

73,

   ... Joe, W4TV


On 2021-03-19 3:25 PM, Mark Robinson wrote:
I am trying to sort my log to find log entries that contain POTA in the comments field

I think I add an SQL filter in Log >Adv  > SQL Filters

I think the syntax would be

COMMENT = "*POTA*"

but it didn't find anything. So I must have something wrong. Can you point me in the right direction

73 Mark N1UK







On 18-Mar-21 11:23 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

Is there a recommended way to designate POTA QSO's in DXKeeper ?
Currently I am just making a note of the Park number in the Comments field along with the abbreviation POTA.

+ See "Tracking Progress Towards an Award with a User-defined Item: POTA" in

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

      73,

             Dave, AA6YQ




Re: Sorting Log for POTA in Comments Field

Joe Subich, W4TV
 

I think the syntax would be

COMMENT = "*POTA*"

but it didn't find anything. So I must have something wrong. Can you
point me in the right direction
COMMENT LIKE '*POTA*'

Note: Like instead of = for "wild card" searches
single not double quotes for alpha searches

73,

... Joe, W4TV


On 2021-03-19 3:25 PM, Mark Robinson wrote:
I am trying to sort my log to find log entries that contain POTA in the comments field
I think I add an SQL filter in Log >Adv  > SQL Filters
I think the syntax would be
COMMENT = "*POTA*"
but it didn't find anything. So I must have something wrong.  Can you point me in the right direction
73 Mark N1UK
On 18-Mar-21 11:23 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

Is there a recommended way to designate POTA QSO's in DXKeeper ?
Currently I am just making a note of the Park number in the Comments field along with the abbreviation POTA.

+ See "Tracking Progress Towards an Award with a User-defined Item: POTA" in

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

      73,

             Dave, AA6YQ


Re: How Do I Designate a POTA QSO in DXK

w2eck
 

Dave - thanks for the tip, and yes the Generate Progress Report box is no longer greyed out. But now I get a popup msg saying "Unable to open the file C:\Dxlab\DXKeeper|Reports\W2ECK WWFF/POTA Progress Report 2021-03019.txt for output; a log report cannot be generated"

tnx & 73
Paul
w2eck


Sorting Log for POTA in Comments Field

Mark Robinson
 

I am trying to sort my log to find log entries that contain POTA in the comments field

I think I add an SQL filter in Log >Adv  > SQL Filters

I think the syntax would be

COMMENT = "*POTA*"

but it didn't find anything. So I must have something wrong.  Can you point me in the right direction

73 Mark N1UK

On 18-Mar-21 11:23 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

Is there a recommended way to designate POTA QSO's in DXKeeper ?
Currently I am just making a note of the Park number in the Comments field along with the abbreviation POTA.

+ See "Tracking Progress Towards an Award with a User-defined Item: POTA" in

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

73,

Dave, AA6YQ






Re: How Do I Designate a POTA QSO in DXK

Dave AA6YQ
 

Hello Paul. I am a avid POTA chaser myself. I dont see in awards progress POTA. Do I need to define one for POTA? Or am i missing something.

+ See " Tracking Progress Towards an Award with a User-defined Item: POTA" in

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

+ The same technique can be used for WWFF, Lighthouses, and Modern Art Museums.

73,

Dave, AA6YQ


Re: Error Logging from JTAlert to DXKeeper

Dave AA6YQ
 

+ AA6YQ comments below

I'm not sure the "solution" mentioned in this thread is really the right one. If double logging was happening then either two servers were receiving logged QSO datagrams, or one server was receiving them twice.
The former is quite possible when using multicast and the solution would be to configure one of the servers not to convey logged QSOs to DXKeeper. The latter could be due to a combination of the server listening on all local interfaces and WSJT-X being configured to send datagrams to more than one local interface (e.g. the loopback interface and a local subnet interface).

Reducing the outgoing network interfaces to just one could fix either of those issues but for the former it is not the right solution, and for the latter I would expect a multicast UDP server to have some control over which local network interfaces it listens on. For sure with the latter, and no such listening control, such a server is going to be prone to duplicate actions.

+ The configuration instructions in

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

+ will remain limited to the most common case: WSJT-X and JT-Alert hosted on the same computer.

+ If someone writes an article describing the effective use of multicast UDP in more complex topologies, I will be happy to add it to "Getting Started with DXLab".

73,

Dave, AA6YQ


Re: N1MM, DXKeeper, ????.

Dave AA6YQ
 

+ AA6YQ comments below

Yes, I am using Primary Callbook - QRZ.COM, Secondary Callbook - HamQTH.

+ That considerably increases the time required to log a QSO via the Gateway. Try unchecking the Gateway's "Query Callbook" box. Then after the contest,

1. Filter the Log Page Display to contain your QSOs from that contest

2. depress the ALT key while clicking the CBA button; this will perform a callbook lookup on each of your contest QSOs

73,

Dave, AA6YQ


Re: How Do I Designate a POTA QSO in DXK

Dave AA6YQ
 

+ AA6YQ comments below

So when I go to User Item Progress Report Selector tab and check POTA, the "Generate Progress Report" button is greyed out, what step have I left out?

+ For the "Generate Progress Report" button on the "User Item Progress Report Selector" window to be enabled,

1. select a user-defined item on the left side of the "User Item Progress Report Selector" window

2. In the "Progress report Generation" panel on the Configuration window's "User Items" tab, check the Enable box for the user-defined item in question; while you're there, check or uncheck the eQSL and LoTW boxes for that user-defined item to indicate whether or not eQSL and LoTW confirmations "count" for award progress.

+ See the "Configuring a user-defined item" section in "Tracking Progress Towards an Award with a User-defined Item: POTA":

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

73,

Dave, AA6YQ


Re: Error Logging from JTAlert to DXKeeper

g4wjs
 

On 19/03/2021 17:44, Dave AA6YQ wrote:
Summary:

1. Russ is using JTAlert with WSJT-X and DXLab.

2. Russ reported that each QSO logged from JTAlert to DXKeeper was creating two QSOs in DXKeeper

3. An analysis of DXKeeper's errorlog showed that DXKeeper was receiving two "log QSOs" directives

4. Russ found an "Outgoing Interfaces" setting in WSJT-X that evidently caused the double-logging

5. I wanted to be sure that setting was properly documented in "Getting Started with K1JT modes using WSJT-X, JTAlert, and DXLab"

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

but could not find the "Outgoing Interfaces" setting in my instance of WSJT-X

6. Now that I understand that the "Outgoing Interfaces" setting only appears if the "UDP Server" address is set to a multicast address, I have updated the instructions cited above to suggest setting the "UDP Server" address to 127.0.0.1, which will prevent the double-logging.

Note: Configuration instructions in "Getting Started with DXLab" suggest a basic configuration suitable for most users. They do not cover all usage scenarios, for example hosting WSJT-X and JTAlert on different computers.

73,

Dave, AA6YQ
Hi Dave and Russ,

I'm not sure the "solution" mentioned in this thread is really the right one. If double logging was happening then either two servers were receiving logged QSO datagrams, or one server was receiving them twice. The former is quite possible when using multicast and the solution would be to configure one of the servers not to convey logged QSOs to DXKeeper. The latter could be due to a combination of the server listening on all local interfaces and WSJT-X being configured to send datagrams to more than one local interface (e.g. the loopback interface and a local subnet interface).

Reducing the outgoing network interfaces to just one could fix either of those issues but for the former it is not the right solution, and for the latter I would expect a multicast UDP server to have some control over which local network interfaces it listens on. For sure with the latter, and no such listening control, such a server is going to be prone to duplicate actions.



--
73

Bill

G4WJS.


Re: How Do I Designate a POTA QSO in DXK

Dave Tucker Nu4N <dwtucker19@...>
 

Hello Paul. I am a avid POTA chaser myself. I dont see in awards progress POTA. Do I need to define one for POTA? Or am i missing something.
Thanks
--
73's de NU4N Dave


Re: Error Logging from JTAlert to DXKeeper

Joe Subich, W4TV
 

Hi Joe,

yes it does but I though we were discussing SpotCollector as the
server for WSJT-X clients.
The original poster indicated the use of WSJTX, JTAlert and SC:

Windows 10 20H2, current as of today
WSJT-X v2.3.0
JTAlert v2.16.17
DXLab Suite's DXKeeper v16.0.7
Flex 6700
SmartSDR v3.1.12
(connected together by physical Ethernet switch but port forwarded
through my router to enable DXLab's Commander to work remotely)
As a note, I have "Post decoded Callsigns to SpotCollector as local spots" enabled (under JTAlert -> Settings -> Manage Settings -> Applications -> DXLab Suite -> SpotCollector) with no problems. I depend on those spots in my set-up.
73,

... Joe, W4TV


On 2021-03-19 10:50 AM, g4wjs wrote:
On 19/03/2021 13:53, Joe Subich, W4TV wrote:
but I have to ask why you are using multicast and also why you are
having WSJT-X send traffic on two separate network interfaces.
Seems to me I saw that from *you* on the WSJTX list in regard to
JTAlert when 2.3.0(?) added multicast support.

73,

   ... Joe, W4TV


On 2021-03-19 9:26 AM, g4wjs wrote:
On 19/03/2021 13:23, Joe Subich, W4TV wrote:

On 2021-03-19 6:45 AM, g4wjs wrote:
no one using SpotCollector as a UDP server for WSJT-X should be using
a multicast group address as a UDP destination in WSJT-X.
Bill,

Really?  Works just fine for me with WSJTX 2.4.0-rc3, JT Alert
2.16.17 and SpotCollector with UDP Server 239.255.01, Port 2237,
and outgoing interfaces: wireless_0, loopback_6


73,

   ... Joe, W4TV


On 2021-03-19 6:45 AM, g4wjs wrote:

Hi Dave,

specifying the network interface(s) datagrams are sent on is only required for multicast group addresses, for unicast addresses the routing is determined by the networking infrastructure. Since SpotCollector does not support multicast no one using SpotCollector as a UDP server for WSJT-X should be using a multicast group address as a UDP destination in WSJT-X.

73
Bill
G4WJS.
Hi Joe,

OK, I can see how that might work, but I have to ask why you are using multicast and also why you are having WSJT-X send traffic on two separate network interfaces. That seems a recipe for duplicate traffic to any server listening on all interfaces on the local machine.

73
Bill
G4WJS.
Hi Joe,
yes it does but I though we were discussing SpotCollector as the server for WSJT-X clients.


Re: WinWarbler

Dave AA6YQ
 

+ AA6YQ comments below

I need your help in determining my error when setting up the program.
When I click on a callsign in the Bandspread window, a command to search for data for that callsign is received, processed and displayed in Commander, DXKeeper, Pathfinder, PropView, DXVeiw, Capture but in WinWarbler the callsign is not entered and there is no information related to the entered callsign.
I searched the documentation, but I couldn't find the answer. Help me please.

+ In the "DX Spots" panel on the Bandspread tab of Commander's Configuration window, set the "Digital Mode Application" sub-panel's Name to

winwarbler

+ If WinWarbler is running, click the Connect button to the right of the name. It should not be necessary to click the Connect button again.

73,

Dave, AA6YQ


Re: Error Logging from JTAlert to DXKeeper

Dave AA6YQ
 

Summary:

1. Russ is using JTAlert with WSJT-X and DXLab.

2. Russ reported that each QSO logged from JTAlert to DXKeeper was creating two QSOs in DXKeeper

3. An analysis of DXKeeper's errorlog showed that DXKeeper was receiving two "log QSOs" directives

4. Russ found an "Outgoing Interfaces" setting in WSJT-X that evidently caused the double-logging

5. I wanted to be sure that setting was properly documented in "Getting Started with K1JT modes using WSJT-X, JTAlert, and DXLab"

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

but could not find the "Outgoing Interfaces" setting in my instance of WSJT-X

6. Now that I understand that the "Outgoing Interfaces" setting only appears if the "UDP Server" address is set to a multicast address, I have updated the instructions cited above to suggest setting the "UDP Server" address to 127.0.0.1, which will prevent the double-logging.

Note: Configuration instructions in "Getting Started with DXLab" suggest a basic configuration suitable for most users. They do not cover all usage scenarios, for example hosting WSJT-X and JTAlert on different computers.

73,

Dave, AA6YQ


Re: Error Logging from JTAlert to DXKeeper

Dave AA6YQ
 

+ AA6YQ comments below

specifying the network interface(s) datagrams are sent on is only required for multicast group addresses, for unicast addresses the routing is determined by the networking infrastructure. Since SpotCollector does not support multicast no one using SpotCollector as a UDP server for WSJT-X should be using a multicast group address as a UDP destination in WSJT-X.

+ Russ is using JT-Alert to interoperate with WSJT-X (see subject), not SpotCollector. SpotCollector's capabilities are no more relevant in this configuration than its ability to automatically land aircraft in dense fog.

73,

Dave, AA6YQ

3561 - 3580 of 204054