Date   

Re: Help document for SpotCollector/WSJT-X

Scott Stembaugh
 

Thanks Dave.

Something else I noticed.  While you can change the UDP port in SC, upon restart it resets to 2237.  I don't know if that is by design or not.  I thought it would retain the setting between sessions.  I noticed this when I shutdown SC to update the databases this morning.  The only reason I had changed the UDP port was because there appeared to be a conflict on 2237 that was not allowing connection to WSJT-X.  By changing to 2238 in both apps it worked fine. 

 I don't anticipate keeping the connection up constantly and only using it to try and stalk a DX station while I am away from the radio by using a text message alert based on call, spot source, and network.

73,
--scott N9LJX


On Mon, Jun 8, 2020 at 1:16 AM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

No, I didn't misread.
"To connect to an instance of WSJT-X running on your computer, do the following in the WSJT-X panel on the Configuration window's Spot Sources tab:

1.      Set the UDP address <http://dxlabsuite.com/spotcollector/Help/ConfigurationSources.htm#WSJTX_UDP_address>  to UDP address specified on the Reporting tab of the WSJT-X Settings window"

There is no UDP address setting in the Spot Sources tab of Spot Collectors WSJT-X panel.

+ The documentation error has been corrected; direct your web browser to refresh. Thanks!

        73,

               Dave, AA6YQ






Re: JS8CALL to LoTW from DXKEEPER

Komkit Listisard
 

Dave, thanks.  DXKEEPER is my main master log.  Log publisher seem like the way to go.

I didn't need the log publisher with WSJT-X / JTDX because JTALERT support both. And sending out log to QRZ,  so the add on like log publisher was not needed. It was not about spending money buy the license for different programs. Just don't want to open 5 programs to do 1 task.

If DXKEEPER have the abilities to send the QSO up to QRZ from within, I would be all set.

Otherwise, I will send the author of the log publisher some beer money and use it for JS8CALL.

73, W3KIT


Re: Help document for SpotCollector/WSJT-X

Dave AA6YQ
 

+ AA6YQ comments below

No, I didn't misread.
"To connect to an instance of WSJT-X running on your computer, do the following in the WSJT-X panel on the Configuration window's Spot Sources tab:

1. Set the UDP address <http://dxlabsuite.com/spotcollector/Help/ConfigurationSources.htm#WSJTX_UDP_address> to UDP address specified on the Reporting tab of the WSJT-X Settings window"

There is no UDP address setting in the Spot Sources tab of Spot Collectors WSJT-X panel.

+ The documentation error has been corrected; direct your web browser to refresh. Thanks!

73,

Dave, AA6YQ


Re: Help document for SpotCollector/WSJT-X

Scott Stembaugh
 

No, I didn't misread.
"To connect to an instance of WSJT-X running on your computer, do the following in the WSJT-X panel on the Configuration window's Spot Sources tab:
  1. Set the UDP address to UDP address specified on the Reporting tab of the WSJT-X Settings window"

There is no UDP address setting in the Spot Sources tab of Spot Collectors WSJT-X panel.

I did have to change the UDP port in both applications from what I assume is the default 2237 to 2238 to get them to see each other.  Something else must have grabbed 2237,



On Mon, Jun 8, 2020 at 12:28 AM Scott Stembaugh <radio.n9ljx@...> wrote:
I apologize.  I misread.  I was looking for the UDP server address in SpotCollector, not where the doc clearly says it is in WSJT-X.

73,
--scott


On Sun, Jun 7, 2020 at 9:58 PM g4wjs <bill.8@...> wrote:
On 08/06/2020 02:54, Scott Stembaugh wrote:
In trying to get WSJT-X talking to Spotcollector again I noticed in  http://dxlabsuite.com/spotcollector/Help/SourceConnection.htm#Connecting_to_WSJT-X that it refers to setting the UDP address of the UDP server in WSJT-X, but in SpotCollector there is only the option of setting the port.



73,
--scott

Hi Scott,

that's correct. The client (WSJT-X) needs the server IP address and the service port to send traffic to, the server (SpotCollector) only needs to know the service port it is supposed to listen for clients on. The server communicates back to clients on ip address and service port that the client messages, it is replying to, arrived from.


--
73

Bill

G4WJS.


Re: updated eQSL AG and LoTW databases are available...

Björn SM7IUN
 

Thanks Dave,

It is great to have such frequent updates. 
Can we hope for an updated USAP database also? 
It is such a great help for WAS hunting.

Björn SM7IUN

Den mån 8 juni 2020 kl 05:42 skrev Dave AA6YQ <aa6yq@...>:

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

       73,

             Dave, AA6YQ





Re: updated eQSL AG and LoTW databases are available...

Dave AA6YQ
 

+ AA6YQ comments below

On Sun, Jun 7, 2020 at 09:02 PM, Ed Ireland wrote:

In my Databases tab in DXView Configuration, everything is greyed out.  What do I need to do?

+ What happens if you click the New? button on that tab?

       73,

               Dave, AA6YQ


Re: Help document for SpotCollector/WSJT-X

Scott Stembaugh
 

I apologize.  I misread.  I was looking for the UDP server address in SpotCollector, not where the doc clearly says it is in WSJT-X.

73,
--scott


On Sun, Jun 7, 2020 at 9:58 PM g4wjs <bill.8@...> wrote:
On 08/06/2020 02:54, Scott Stembaugh wrote:
In trying to get WSJT-X talking to Spotcollector again I noticed in  http://dxlabsuite.com/spotcollector/Help/SourceConnection.htm#Connecting_to_WSJT-X that it refers to setting the UDP address of the UDP server in WSJT-X, but in SpotCollector there is only the option of setting the port.



73,
--scott

Hi Scott,

that's correct. The client (WSJT-X) needs the server IP address and the service port to send traffic to, the server (SpotCollector) only needs to know the service port it is supposed to listen for clients on. The server communicates back to clients on ip address and service port that the client messages, it is replying to, arrived from.


--
73

Bill

G4WJS.


Re: updated eQSL AG and LoTW databases are available...

Ed Ireland
 

Dave,

In my Databases tab in DXView Configuration, everything is greyed out.  What do I need to do?

Ed K5YZW

On Sun, Jun 7, 2020 at 10:42 PM Dave AA6YQ <aa6yq@...> wrote:
...via the Databases tab on DXView's Configuration window.

       73,

             Dave, AA6YQ





updated eQSL AG and LoTW databases are available...

Dave AA6YQ
 

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

73,

Dave, AA6YQ


Re: JS8CALL to LoTW from DXKEEPER

Dave AA6YQ
 

+ AA6YQ comments below

On Sun, Jun 7, 2020 at 05:35 PM, Komkit Listisard wrote:

OKay, I guess.  Just upload ADIF to QRZ.   I was more concern about user that do not use LoTW.   I uploads to LoTW from DXKEEPER, LoTW just changed JS8 to DATA.

For FT8 I normally upload the log to QRZ using JTALERT and and then JTALERT log QSO to DXKEEPER and at the same time JTALERT tell DXKEEPER to upload the log to LoTW.  No issue there.

Since JTALERT does not work with JS8CALL, I have no way to send the log to QRZ automatically.  I depends on DXKEEPER (manually) sending the JS8 log to LoTW and often I just got on QRZ and import logs / confirmations from LoTW back to QRZ.

In this case I got DATA back from LoTW instead of JS8 in mode field.  However if the JS8 contacts I made and the party does not use LoTW but just QRZ, if he/she upload to just QRZ the mode will be mismatch between JS8 vs DATA.

Other than that, I think I can live with manually upload separate JS8 logs to QRZ just not through LoTW.

+ My advice is to pick one application to serve as your "master log". Route all logged QSOs to this "master Log", and convey QSOs to other applications from this "master log".

+ Many ops use DXKeeper as their "master log", as it can accept QSOs directly via DDE or TCP, or by importing an ADIF or tab-delimited file. DXKeeper can submit QSOs to Club Log, eQSL, and LoTW. The LogPublisher add-in can convey QSOs from DXKeeper to HRDLog.net and QRZ.com:

<http://www.dl9ho.de/LogPublisher/LogPublisher.htm>

      73,
                
             Dave, AA6YQ

 


Re: Help document for SpotCollector/WSJT-X

g4wjs
 

On 08/06/2020 02:54, Scott Stembaugh wrote:
In trying to get WSJT-X talking to Spotcollector again I noticed in  http://dxlabsuite.com/spotcollector/Help/SourceConnection.htm#Connecting_to_WSJT-X that it refers to setting the UDP address of the UDP server in WSJT-X, but in SpotCollector there is only the option of setting the port.



73,
--scott

Hi Scott,

that's correct. The client (WSJT-X) needs the server IP address and the service port to send traffic to, the server (SpotCollector) only needs to know the service port it is supposed to listen for clients on. The server communicates back to clients on ip address and service port that the client messages, it is replying to, arrived from.


--
73

Bill

G4WJS.


Help document for SpotCollector/WSJT-X

Scott Stembaugh
 

In trying to get WSJT-X talking to Spotcollector again I noticed in  http://dxlabsuite.com/spotcollector/Help/SourceConnection.htm#Connecting_to_WSJT-X that it refers to setting the UDP address of the UDP server in WSJT-X, but in SpotCollector there is only the option of setting the port.



73,
--scott


Re: JS8CALL to LoTW from DXKEEPER

Komkit Listisard
 

OKay, I guess.  Just upload ADIF to QRZ.   I was more concern about user that do not use LoTW.   I uploads to LoTW from DXKEEPER, LoTW just changed JS8 to DATA.

For FT8 I normally upload the log to QRZ using JTALERT and and then JTALERT log QSO to DXKEEPER and at the same time JTALERT tell DXKEEPER to upload the log to LoTW.  No issue there.

Since JTALERT does not work with JS8CALL, I have no way to send the log to QRZ automatically.  I depends on DXKEEPER (manually) sending the JS8 log to LoTW and often I just got on QRZ and import logs / confirmations from LoTW back to QRZ.

In this case I got DATA back from LoTW instead of JS8 in mode field.  However if the JS8 contacts I made and the party does not use LoTW but just QRZ, if he/she upload to just QRZ the mode will be mismatch between JS8 vs DATA.

Other than that, I think I can live with manually upload separate JS8 logs to QRZ just not through LoTW.

Thank you for your time.

73, W3KIT


Re: JS8CALL to LoTW from DXKEEPER

Dave AA6YQ
 

+ AA6YQ comments below

 

On 2020-06-07 6:46 PM, Komkit Listisard via groups.io wrote:

 

> I read more into it, seems like LoTW does not directly support JS8 as

> it own mode.  I think have to upload it as MFSK and then JS8 as

> sub-mode.  I do not how to accomplish that.

 

DXKeeper exports JS8 properly.  LotW does not accept JS8 as anything other that DATA.  There are no ARRL (or CQ) awards for JS8.  For DXCC JS8, like every other digital mode is simply "Data".  For WAS there are no endorsements for JS8 so they are simply treated as a generic "DATA" mode.

 

In both cases that is the same as all of the other fringe data modes

- all are recorded in LotW simply as "Data".

 

For Dave's benefit, tQSL's config.xml version 11.11 maps JS8 to Data.

 

+ Thanks, Joe; you are correct. Here's how LoTW reports a confirmed JS8 QSO submitted with <MODE:4>MFSK<SUBMODE:3>JS8

<APP_LoTW_OWNCALL:5>AA6YQ

<STATION_CALLSIGN:5>AA6YQ

<CALL:5>N6XVZ

<BAND:3>40M

<FREQ:7>7.07800

<MODE:4>DATA

<APP_LoTW_MODE:4>DATA

<APP_LoTW_MODEGROUP:4>DATA

<QSO_DATE:8>20181206

<APP_LoTW_RXQSO:19>2018-12-06 02:44:02 // QSO record inserted/modified at LoTW

<TIME_ON:6>022153

<APP_LoTW_QSO_TIMESTAMP:20>2018-12-06T02:21:53Z // QSO Date & Time; ISO-8601

<PROP_MODE:2>F2

<QSL_RCVD:1>Y

<QSLRDATE:8>20181206

<APP_LoTW_RXQSL:19>2018-12-06 03:56:46 // QSL record matched/modified at LoTW

<DXCC:3>291

<COUNTRY:24>UNITED STATES OF AMERICA

<APP_LoTW_DXCC_ENTITY_STATUS:7>Current

<PFX:2>N6

<APP_LoTW_2xQSL:1>Y

<GRIDSQUARE:6>EM13PC

<STATE:2>TX // Texas

<CNTY:9>TX,COLLIN // Collin

<CQZ:2>04

<ITUZ:2>07

<eor>

 

     73,

 

            Dave, AA6YQ


Re: JS8CALL to LoTW from DXKEEPER

Joe Subich, W4TV
 

On 2020-06-07 6:46 PM, Komkit Listisard via groups.io wrote:

I read more into it, seems like LoTW does not directly support JS8 as
it own mode. I think have to upload it as MFSK and then JS8 as
sub-mode. I do not how to accomplish that.
DXKeeper exports JS8 properly. LotW does not accept JS8 as anything
other that DATA. There are no ARRL (or CQ) awards for JS8. For
DXCC JS8, like every other digital mode is simply "Data". For WAS
there are no endorsements for JS8 so they are simply treated as a
generic "DATA" mode.

In both cases that is the same as all of the other fringe data modes
- all are recorded in LotW simply as "Data".

For Dave's benefit, tQSL's config.xml version 11.11 maps JS8 to Data.

73,

... Joe, W4TV


On 2020-06-07 6:46 PM, Komkit Listisard via groups.io wrote:
Dave,  I do not have anything the the mapping configuration tab, all blank.
For now I just won't upload the JS8 contacts to LoTW from DXKEEPER.   I read more into it, seems like LoTW does not directly support JS8 as it own mode.  I think have to upload it as MFSK and then JS8 as sub-mode.  I do not how to accomplish that.
I will just manually upload the ADIF JS8CALL log file directly to QRZ.     Logs from JS8CALL to DXKEEPER as JS8 is fine with the help of N1MM logger and N1MM Gateway.
Thank you kindly.
73, W3KIT


Re: JS8CALL to LoTW from DXKEEPER

Dave AA6YQ
 

+ AA6YQ comments below

Dave, I do not have anything the the mapping configuration tab, all blank.

For now I just won't upload the JS8 contacts to LoTW from DXKEEPER. I read more into it, seems like LoTW does not directly support JS8 as it own mode. I think have to upload it as MFSK and then JS8 as sub-mode.

+ The ADIF representation of JS8 is

<MODE:4>MFSK <SUBMODE:3>JS8

I do not how to accomplish that.

+ DXKeeper automatically does that when you direct it to submit a JS8 QSO to LoTW. I have successful submitted JS8 QSOs to LoTW from DXKeeper.

+ What version of DXKeeper are you running? This information appears in the Main window's title bar.

73,

Dave, AA6YQ


Re: JS8CALL to LoTW from DXKEEPER

Komkit Listisard
 

Dave,  I do not have anything the the mapping configuration tab, all blank.

For now I just won't upload the JS8 contacts to LoTW from DXKEEPER.   I read more into it, seems like LoTW does not directly support JS8 as it own mode.  I think have to upload it as MFSK and then JS8 as sub-mode.  I do not how to accomplish that. 

I will just manually upload the ADIF JS8CALL log file directly to QRZ.     Logs from JS8CALL to DXKEEPER as JS8 is fine with the help of N1MM logger and N1MM Gateway.

Thank you kindly.
73, W3KIT


Re: Use Of Commander

Dave AA6YQ
 

* AA6YQ comments below

On Sun, Jun 7, 2020 at 01:38 PM, Joe Subich, W4TV wrote:

Can complete radio control be accomplish with Commander as is with
FLRig? >
+ No.
The same capabilities as WSJT-X/FLrig and FLDIGI/FLRig can generally be
obtained with WSJT-X/Commander/SpotCollector and FLdig plus the FLdigi-
DxLab Gateway <http://www.n2amg.com/software/fldigi-dxlabs-gateway/>.

In those two configurations Commander replaces FLrig as the rig control
portion of the system.

* The author of the FLDdigi-DXLab Gateway reports that it does not work correctly with Windows 10, and that repairing it is not imminent. Replacing the FLDdigi-DXLab Gateway will become my top priority (behind answer questions here and correcting defects) after I finish re-architecting and re-implementing SpotCollector's interoperation with WSJT-X.

         73,

               Dave, AA6YQ


Re: Use Of Commander

Joe Subich, W4TV
 

Can complete radio control be accomplish with Commander as is with
FLRig? >
+ No.
The same capabilities as WSJT-X/FLrig and FLDIGI/FLRig can generally be
obtained with WSJT-X/Commander/SpotCollector and FLdig plus the FLdigi-
DxLab Gateway <http://www.n2amg.com/software/fldigi-dxlabs-gateway/>.

In those two configurations Commander replaces FLrig as the rig control
portion of the system.

73,

... Joe, W4TV


On 2020-06-07 3:33 PM, Dave AA6YQ wrote:
+ AA6YQ comments below
I use DXKeeper as my one and only logging program. I use it with WSJT-X and Fldigi. I also use Flrig to control my radio when using both program.
Within WSJT-X → Setting → Radio → I choose FLRig FLRig as my Rig control. I am able to have complete control over radio functions including auto-tuning without touching the radio. I can also monitor the S meter, radio SWRs and Power output with FLRig.
By not having Commander running, does this impact performance of the DXLab Suite?
+ DXLab applications rely on Commander for access to your transceiver's frequency, mode, split, RX/TX status, etc.
+ If you're not using SpotCollector, you're missing much of the functionality that DXLab uniquely provides for DXers; see
<https://www.dxlabsuite.com/dxlabwiki/DXingWithDXLab>
Can complete radio control be accomplish with Commander as is with FLRig?
+ No.
73,
Dave, AA6YQ


Re: How to color code stations I have not worked in WSJT-X using Spot Collector

Dave AA6YQ
 

+ AA6YQ comments below

<blob:applewebdata://3e2026cf-d89d-4363-8309-e4d2953e9fe1/254cf701-0bdc-4c56-899d-df06d5f53435>

+ Not accessible.

73,

Dave, AA6YQ

5841 - 5860 of 200078