Date   

DXK Sync LOTW

Jim Denneny
 

DXK 16.0.7 will not sync LOTW QSL or QSO today.  Error: "Unable to download from LOTW".  I tried loading an earlier version to registry but DXK still displayed 16.0.7. There are 46009 QSO's in my log.

I logged onto LOTW online and found no issues from the ARRL end. Records are correct. Is anyone else experiencing this issue?

73, Jim K7EG


Re: Error Logging from JTAlert to DXKeeper

Joe Subich, W4TV
 

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.
--
73
Bill
G4WJS.


Re: Error Logging from JTAlert to DXKeeper

g4wjs
 

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.


--
73

Bill

G4WJS.


Re: Error Logging from JTAlert to DXKeeper

Joe Subich, W4TV
 

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.


Re: How Do I Designate a POTA QSO in DXK

w2eck
 

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?
&3 Paul w2eck


WinWarbler

Yuriy Veselov
 

Hello Dave.

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.

73. Yuri R2ZX


Re: Error Logging from JTAlert to DXKeeper

g4wjs
 

On 19/03/2021 06:14, Dave AA6YQ wrote:
+ AA6YQ comments below

I wanted to follow up on this. After posting this, I was called away out of town and took my Flex Maestro and computer to operate remotely. Amazingly, the problem stopped happening while I was gone. I returned home today and tried again and the double logging started happening again. That got me thinking that while I don't remember changing this setting after I got it working, the "loopback thing" in WSJT-X was new to me so I checked it's setting in WSJT-X -> Reporting -> Outgoing interfaces: . It was set to "Loopback 0" but I could have sworn I set it to "Ethernet 2" originally. The whole idea of "looping back" relative to "double logging" got me thinking ... So I set it to "Ethernet 2" and nothing logged at all ! Actually pretty good news since I was at least touching something apparently related. So I added "Ethernet 2" to "Loopback 0" and that did it! No more double logging. When I checked the setting again, what had originally shown in the WSJT-X drop-down as "Ethernet 2" now shows as "Ethernet_32774". Apparently WSJT-X reset it ?

I wanted to mention this here in case it's of value to anyone else. I followed up on Laurie's reflector as well. Of course I ended up bugging both Laurie and Dave about this while the problem was actually a setting in WSJT-X all along. Makes me appreciate Laurie and Dave's help all the more.

Thank You again !
Russ

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.


+ Russ, I don't see "Outgoing Interfaces" on the Reporting tab of the Settings window in WSJT-X 2.3.0.

73,

Dave, AA6YQ
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.




--
73

Bill

G4WJS.


Re: Error Logging from JTAlert to DXKeeper

neil_zampella
 

Dave,

you have to have a multicast IP address such as 239.255.0.1 entered into the UDP Server box, and the Outgoing Interfaces drop down appears.

Neil, KN3ILZ

On 3/19/2021 1:22 AM, Russ Ravella via groups.io wrote:
Screen shot emailed …


On Mar 18, 2021, at 11:14 PM, Dave AA6YQ <aa6yq@ambersoft.com> wrote:

+ AA6YQ comments below

I wanted to follow up on this. After posting this, I was called away out of town and took my Flex Maestro and computer to operate remotely. Amazingly, the problem stopped happening while I was gone. I returned home today and tried again and the double logging started happening again. That got me thinking that while I don't remember changing this setting after I got it working, the "loopback thing" in WSJT-X was new to me so I checked it's setting in WSJT-X -> Reporting -> Outgoing interfaces: . It was set to "Loopback 0" but I could have sworn I set it to "Ethernet 2" originally. The whole idea of "looping back" relative to "double logging" got me thinking ... So I set it to "Ethernet 2" and nothing logged at all ! Actually pretty good news since I was at least touching something apparently related. So I added "Ethernet 2" to "Loopback 0" and that did it! No more double logging. When I checked the setting again, what had originally shown in the WSJT-X drop-down as "Ethernet 2" now shows as "Ethernet_32774". Apparently WSJT-X reset it ?

I wanted to mention this here in case it's of value to anyone else. I followed up on Laurie's reflector as well. Of course I ended up bugging both Laurie and Dave about this while the problem was actually a setting in WSJT-X all along. Makes me appreciate Laurie and Dave's help all the more.

Thank You again !
Russ

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.


+ Russ, I don't see "Outgoing Interfaces" on the Reporting tab of the Settings window in WSJT-X 2.3.0.

73,

Dave, AA6YQ









Re: Send 5 Volts on off signal for ant switch relays

Larry K8UT
 

Dave - thanks for those nice words about the FreqEZ Band Decoder.

Simon - my FreqEZ Band Decoder software is free. The Console runs on Windows, and the Controller runs on a Raspberry Pi. You can build your own Controller hardware (instructions provided) or purchase a companion HAT board from me. FreqEZ v1.x (now) supports 16 outputs; v2 (soon) will support 64. More details and a video link on the website www.freqez.info.

FreqEZ was written with Dave AA6YQ's help and is specifically intended for DXLab users (like me). It can be used as a simple manual switch using mouse clicks. But if you use Commander's >Config >NetSvc settings to send <RadioInfo> packets to FreqEZ's Console - it's automagic. Connect via ethernet or WiFi. No messy serial or parallel ports required.

-larry (K8UT)

------ Original Message ------
From: "Simon" <simonhk7@...>
Sent: 2021-03-18 22:37:56
Subject: Re: [DXLab] Send 5 Volts on off signal for ant switch relays

Hi Dave w6de

Thanks for pointer. Yes, the radio info message has every basic thing needed and solve the laptop issue



On Friday, March 19, 2021, w6de <w6de@...> wrote:

There is a Hardware & Software solution for your problem. FreqEz is a raspberry Pi hat and software set that reads the UDP data from DXLab Commander or N1MM contesting software and sends the frequency data FreqEx on the Windows computer and according to a matrix you set up sends antenna selection data to the raspberry pi and a switching board for antenna selection.  Do a WEB search for FreqEZ.  FreqEz was developed by Larry K8UT who also frequents this forum.

 

73,

Dave, w6de

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Simon via groups.io
Sent: Thursday, March 18, 2021 18:09
To: DXLab@groups.io
Subject: [DXLab] Send 5 Volts on off signal for ant switch relays

 

Planning for a home brew relay box to route the rig to diffetent ant depends on band.

 

Can the software send 5 Volts on off signal via a hardware box? Of course, it can be manual control if above not possible.


Re: N1MM, DXKeeper, Gateway.

Dave AA6YQ
 

+ AA6YQ comments below:
Yes, a bunch of N1MM - DXKeeper, Gateway - everything works as described in the documentation.
+ Good!
Note that QSO registration in DXKeeper is not quite as fast as we would like.

+ Do you have DXKeeper configured to perform a callbook lookup?

     73,

           Dave, AA6YQ


N1MM, DXKeeper, Gateway.

Yuriy Veselov
 

Hi Dave.

Yes, a bunch of N1MM - DXKeeper, Gateway - everything works as described in the documentation.
Note that QSO registration in DXKeeper is not quite as fast as we would like.
My opinion: it is better to use each N1MM and DXLab program for its intended purpose.
Thank you for your help and attention to my question.

73. Yuri R2ZX


Re: Error Logging from JTAlert to DXKeeper

Russ Ravella
 

Screen shot emailed …

On Mar 18, 2021, at 11:14 PM, Dave AA6YQ <aa6yq@ambersoft.com> wrote:

+ AA6YQ comments below

I wanted to follow up on this. After posting this, I was called away out of town and took my Flex Maestro and computer to operate remotely. Amazingly, the problem stopped happening while I was gone. I returned home today and tried again and the double logging started happening again. That got me thinking that while I don't remember changing this setting after I got it working, the "loopback thing" in WSJT-X was new to me so I checked it's setting in WSJT-X -> Reporting -> Outgoing interfaces: . It was set to "Loopback 0" but I could have sworn I set it to "Ethernet 2" originally. The whole idea of "looping back" relative to "double logging" got me thinking ... So I set it to "Ethernet 2" and nothing logged at all ! Actually pretty good news since I was at least touching something apparently related. So I added "Ethernet 2" to "Loopback 0" and that did it! No more double logging. When I checked the setting again, what had originally shown in the WSJT-X drop-down as "Ethernet 2" now shows as "Ethernet_32774". Apparently WSJT-X reset it ?

I wanted to mention this here in case it's of value to anyone else. I followed up on Laurie's reflector as well. Of course I ended up bugging both Laurie and Dave about this while the problem was actually a setting in WSJT-X all along. Makes me appreciate Laurie and Dave's help all the more.

Thank You again !
Russ

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.


+ Russ, I don't see "Outgoing Interfaces" on the Reporting tab of the Settings window in WSJT-X 2.3.0.

73,

Dave, AA6YQ







Re: Error Logging from JTAlert to DXKeeper

Dave AA6YQ
 

+ AA6YQ comments below

I wanted to follow up on this. After posting this, I was called away out of town and took my Flex Maestro and computer to operate remotely. Amazingly, the problem stopped happening while I was gone. I returned home today and tried again and the double logging started happening again. That got me thinking that while I don't remember changing this setting after I got it working, the "loopback thing" in WSJT-X was new to me so I checked it's setting in WSJT-X -> Reporting -> Outgoing interfaces: . It was set to "Loopback 0" but I could have sworn I set it to "Ethernet 2" originally. The whole idea of "looping back" relative to "double logging" got me thinking ... So I set it to "Ethernet 2" and nothing logged at all ! Actually pretty good news since I was at least touching something apparently related. So I added "Ethernet 2" to "Loopback 0" and that did it! No more double logging. When I checked the setting again, what had originally shown in the WSJT-X drop-down as "Ethernet 2" now shows as "Ethernet_32774". Apparently WSJT-X reset it ?

I wanted to mention this here in case it's of value to anyone else. I followed up on Laurie's reflector as well. Of course I ended up bugging both Laurie and Dave about this while the problem was actually a setting in WSJT-X all along. Makes me appreciate Laurie and Dave's help all the more.

Thank You again !
Russ

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.


+ Russ, I don't see "Outgoing Interfaces" on the Reporting tab of the Settings window in WSJT-X 2.3.0.

73,

Dave, AA6YQ


Re: Error Logging from JTAlert to DXKeeper

Russ Ravella
 

Hello,

I wanted to follow up on this.  After posting this, I was called away out of town and took my Flex Maestro and computer to operate remotely.  Amazingly, the problem stopped happening while I was gone.  I returned home today and tried again and the double logging started happening again.  That got me thinking that while I don't remember changing this setting after I got it working, the "loopback thing" in WSJT-X was new to me so I checked it's setting in WSJT-X -> Reporting -> Outgoing interfaces: .  It was set to "Loopback 0" but I could have sworn I set it to "Ethernet 2" originally.  The whole idea of "looping back" relative to "double logging" got me thinking ...  So I set it to "Ethernet 2" and nothing logged at all !  Actually pretty good news since I was at least touching something apparently related. So I added "Ethernet 2" to "Loopback 0" and that did it!  No more double logging.  When I checked the setting again, what had originally shown in the WSJT-X drop-down as "Ethernet 2" now shows as "Ethernet_32774". Apparently WSJT-X reset it ?

I wanted to mention this here in case it's of value to anyone else.  I followed up on Laurie's reflector as well.  Of course I ended up bugging both Laurie and Dave about this while the problem was actually a setting in WSJT-X all along.  Makes me appreciate Laurie and Dave's help all the more.

Thank You again !
Russ

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.


Re: ft857

Joe K2UF
 

Greg,
 
That was set correct.  I think that option is CAT by default and I never used the radio with a linear as it was/is used in my truck.
 
Thanks for the reply.
 
73  Joe K2UF



From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Greg
Sent: Friday, March 19, 2021 1:27 AM
To: DXLab@groups.io
Subject: Re: [DXLab] ft857

Joe

I was trapped once on my radio club's radio as menu item 20 was set to "Linear".  This means there is no CAT operation available on the DIN socket.

Greg VK3VT


On 19/03/2021 08:27, Joe K2UF wrote:
Hi Bill,
 
com port is ok.  I have several USB > Serial adapter cables, have used them for several years on different projects with no problems.  I suspect the ct62 (din to db9 cable).  I have a new one on order.
 
73  Joe K2UF. 


From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Bill Pence
Sent: Thursday, March 18, 2021 5:18 PM
To: DXLab@groups.io
Subject: Re: [DXLab] ft857

What does the device manager show?

Could you be suffering the effects if the dreaded cloned prolific usb device driver impact?



On Thu, Mar 18, 2021, 4:03 PM Joe K2UF <joe@...> wrote:
Thanks Dave,

All the settings are correct.  I suspect the ct62 cable.  I got it cheap on
ebay from an off shore vendor.  I am going to get one from HRO and try
again.  I want to use this radio mobile using  home brew software to control
from a laptop.  Connected it to commander to see if it was my software or a
hardware problem.

Thanks for the info.

73  Joe K2UF 

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Thursday, March 18, 2021 3:19 PM
To: DXLab@groups.io
Subject: Re: [DXLab] ft857

+ AA6YQ comments below

Any one using commander control for a Yeasu ft857  xcvr.  I have tried using
straight thru and cross over adapter just in case.  I am using a CT62 cable
I got on EBay(ugh!).

+ I've used Commander to control my FT817 via a Yaesu CT62 cable. The FT817,
FT857, and FT897 all use the same CAT instruction set.

+ Step-by-step instructions are here:

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

     73,

                 Dave, AA6YQ













Re: ft857

Greg
 

Joe

I was trapped once on my radio club's radio as menu item 20 was set to "Linear".  This means there is no CAT operation available on the DIN socket.

Greg VK3VT


On 19/03/2021 08:27, Joe K2UF wrote:
Hi Bill,
 
com port is ok.  I have several USB > Serial adapter cables, have used them for several years on different projects with no problems.  I suspect the ct62 (din to db9 cable).  I have a new one on order.
 
73  Joe K2UF. 


From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Bill Pence
Sent: Thursday, March 18, 2021 5:18 PM
To: DXLab@groups.io
Subject: Re: [DXLab] ft857

What does the device manager show?

Could you be suffering the effects if the dreaded cloned prolific usb device driver impact?



On Thu, Mar 18, 2021, 4:03 PM Joe K2UF <joe@...> wrote:
Thanks Dave,

All the settings are correct.  I suspect the ct62 cable.  I got it cheap on
ebay from an off shore vendor.  I am going to get one from HRO and try
again.  I want to use this radio mobile using  home brew software to control
from a laptop.  Connected it to commander to see if it was my software or a
hardware problem.

Thanks for the info.

73  Joe K2UF 

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Thursday, March 18, 2021 3:19 PM
To: DXLab@groups.io
Subject: Re: [DXLab] ft857

+ AA6YQ comments below

Any one using commander control for a Yeasu ft857  xcvr.  I have tried using
straight thru and cross over adapter just in case.  I am using a CT62 cable
I got on EBay(ugh!).

+ I've used Commander to control my FT817 via a Yaesu CT62 cable. The FT817,
FT857, and FT897 all use the same CAT instruction set.

+ Step-by-step instructions are here:

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

     73,

                 Dave, AA6YQ













Re: How Do I Designate a POTA QSO in DXK

Dave AA6YQ
 

+ 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: Send 5 Volts on off signal for ant switch relays

Simon <simonhk7@...>
 

Hi Dave w6de

Thanks for pointer. Yes, the radio info message has every basic thing needed and solve the laptop issue



On Friday, March 19, 2021, w6de <w6de@...> wrote:

There is a Hardware & Software solution for your problem. FreqEz is a raspberry Pi hat and software set that reads the UDP data from DXLab Commander or N1MM contesting software and sends the frequency data FreqEx on the Windows computer and according to a matrix you set up sends antenna selection data to the raspberry pi and a switching board for antenna selection.  Do a WEB search for FreqEZ.  FreqEz was developed by Larry K8UT who also frequents this forum.

 

73,

Dave, w6de

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Simon via groups.io
Sent: Thursday, March 18, 2021 18:09
To: DXLab@groups.io
Subject: [DXLab] Send 5 Volts on off signal for ant switch relays

 

Planning for a home brew relay box to route the rig to diffetent ant depends on band.

 

Can the software send 5 Volts on off signal via a hardware box? Of course, it can be manual control if above not possible.


Re: Send 5 Volts on off signal for ant switch relays

Simon <simonhk7@...>
 

Hi Dale,

Would you mind telling me what are the devices function 


On Friday, March 19, 2021, Dale Drake <daleaa1qd@...> wrote:
Simon,

Last summer I designed and built a unit to do automatic antenna switching to take advantage of the external device that Dave pointed out.  It works FB.  I can send you the schematic and photo.

Dale, AA1QD


How Do I Designate a POTA QSO in DXK

Mark Robinson
 

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.

73 Mark N1UK

3521 - 3540 of 203988