Date   
Re: FT8 and DXLabs

Norman Heyen
 

Thanks Bill,
Sorry for being slow and missing that. I'll take a look and see how to get everyone to play together. I'm assuming I need to use JTAlert with DXLab and WSJT-X? Is anything else needed? DXLabs works well for my SSB needs. I've got WSJT-X to work and it logs to the file in WSJT-X.  But I've never really dipped my toe into the digital water so it is all pretty new to me.


On Mon, Apr 15, 2019 at 6:33 PM g4wjs <bill.8@...> wrote:
On 16/04/2019 00:25, Norman Heyen wrote:

Is there a simple set of instructions that I can use to for FT8? I have the ‘raw’ WSJT-X package working fine but obviously it doesn’t auto-fill contacts into DXKeeper.

What other packages are needed? And what needs to be configured to integrate everything so I can use SpotCollector and DXKeeper at least.

Norman,

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

which is the top of the results for a search for "WSJT-X with DX Lab Suite" and recommended here many times.



--
73

Bill

G4WJS.

Re: Smart SDR 3.0.1.9 loaded but WSJT-X stopped receiving

Jamie WW3S
 

perhaps I'm just lucky, I upgraded to 3.0 and Commander still works for me....

------ Original Message ------
From: "Dave AA6YQ" <@AA6YQ>
To: DXLab@groups.io
Sent: 4/15/2019 6:42:19 PM
Subject: Re: [DXLab] Smart SDR 3.0.1.9 loaded but WSJT-X stopped receiving

+ AA6YQ comments below

I simply offered up a suggestion, as he didn't specifically mention that he was having a problem with Commander, just that he was having a problem with WSJT-X and FT8, after updating to 3.0. The DX Labs reference seemed as more an after thought that anything.

+ The only way to control a Flex Signature radio via CAT is to set Commander's Radio Model selector to Kenwood. This is an unsupported configuration.

I had a similar problem, when my Maestro prompted the update to 3.0. It updated itself and the radio, but I had to manually download and install SmartSDR to update CAT and DAX, of which DAX is used for FT8 operation.

Having said that, I thought your message regarding problems with SmartSDR, was about using it via SmartLink, not that it didn't work at all. I am running v3.0 on my 6600+Maestro with Commander (13.9.0), but I also don't use Commander to the extent that some on this group do. So perhaps the problems with it are further in on some of the deeper features of Commander.

+ I have not installed SmartSDR v3. From what I see on the Flex v3 Alpha test email reflector and the Flex Forums, it does not yet appear stable. However, Eric KE5DTO of Flex states that until Commander is extended to support v3, it will be unable to switch the transceiver between RX and TX, and unable to mute a slice.

73,

Dave, AA6YQ




Re: Smart SDR 3.0.1.9 loaded but WSJT-X stopped receiving

Dave AA6YQ
 

+ AA6YQ comments below

On Mon, Apr 15, 2019 at 06:41 PM, Jamie WW3S wrote:

perhaps I'm just lucky, I upgraded to 3.0 and Commander still works for me....

Try directing Commander to switch your Flex transceiver between RX and TX.

       73,

            Dave, AA6YQ

 

LOTW-NO RESPONSE

 

I AM GETTING A ERROR CODE WHEN TRYING TO DOWNLOAD LOTW.
ALL IN IS CORRECT  , CALL AND PASSWORD,LOCATION
I GET THIS BACK FROM LOTW
ATTEMPT TO CONNECT TO LOTW FAILED: RESPONSEINFO 12157
ANY HELP WOULD BE APPRECIATED.
THANKS IN ADAVANCE
--
 Dave NU4N

Re: LOTW-NO RESPONSE

John Bastin
 

On 16Apr 2019, at 05:08, Dave Tucker <@DWT> wrote:

I AM GETTING A ERROR CODE WHEN TRYING TO DOWNLOAD LOTW.
ALL IN IS CORRECT , CALL AND PASSWORD,LOCATION
I GET THIS BACK FROM LOTW
ATTEMPT TO CONNECT TO LOTW FAILED: RESPONSEINFO 12157
ANY HELP WOULD BE APPRECIATED.
THANKS IN ADAVANCE
From the DXLab wiki:

"if uploading or synchronizing produces an error message containing the error code 12029 or 12157, verify that all of Internet Explorer's Use TLS options are enabled: (note that you must do this whether or not you use Internet Explorer as your web browser)”

More information at

http://www.dxlabsuite.com/dxlabwiki/LotWConnectivityErrors

Hope this helps.

73.

John K8AJS
bastinj@...

Re: Smart SDR 3.0.1.9 loaded but WSJT-X stopped receiving

Jamie WW3S
 

goes into TX , but not switching to RX, it stays in TX.....but then again, I never use this function.....I'm more of a control the radio and let the software follow kinda guy.....mainly cw here, using semi breakin, so I've never had the need to use that in commander.....


------ Original Message ------
From: "Dave AA6YQ" <aa6yq@...>
Sent: 4/15/2019 9:45:42 PM
Subject: Re: [DXLab] Smart SDR 3.0.1.9 loaded but WSJT-X stopped receiving

+ AA6YQ comments below

On Mon, Apr 15, 2019 at 06:41 PM, Jamie WW3S wrote:

perhaps I'm just lucky, I upgraded to 3.0 and Commander still works for me....

Try directing Commander to switch your Flex transceiver between RX and TX.

       73,

            Dave, AA6YQ

 

Re: FT8 and DXLabs

Robert T
 

Norm,

Let me try and tell you my settings for DXLab, WSJT-X, and JTAlert.

First I always run DXLab Commander as my rig control.

Under WSJT-X, File, Settings, Radio Tab, For rig select DX Lab Suite Commander

In JTAlert, Select Settings, Manage Settings, Logging, DXLab DXKeeper

Check the box for Enable DXLab DXKeeper Logging



You will need to enter the path of your log from DXLab. It should be similar to my Log File

You can also instuct DXKeeper to upload each new QSO to EQsl if so desired.


I hope this helps.

If it works great, if still having an issue, let me know.  I could have overlooked a setting.


Your WSJT-X will need to work via DXLab Commander as mentioned above.

In this order:    Open Commander,  Open DXKeeper,  Open WSJT-X, lastly Open JTAlert


You can open as many of the DXLab windows you want at this point. ie: spot collector, path finder, etc.


Bob - K2RET


On April 15, 2019 at 7:40 PM Norman Heyen <norman.heyen@...> wrote:

Thanks Bill,
Sorry for being slow and missing that. I'll take a look and see how to get everyone to play together. I'm assuming I need to use JTAlert with DXLab and WSJT-X? Is anything else needed? DXLabs works well for my SSB needs. I've got WSJT-X to work and it logs to the file in WSJT-X.  But I've never really dipped my toe into the digital water so it is all pretty new to me.

On Mon, Apr 15, 2019 at 6:33 PM g4wjs < bill.8@...> wrote:
On 16/04/2019 00:25, Norman Heyen wrote:

Is there a simple set of instructions that I can use to for FT8? I have the ‘raw’ WSJT-X package working fine but obviously it doesn’t auto-fill contacts into DXKeeper.

What other packages are needed? And what needs to be configured to integrate everything so I can use SpotCollector and DXKeeper at least.

Norman,

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

which is the top of the results for a search for "WSJT-X with DX Lab Suite" and recommended here many times.



--
73

Bill

G4WJS.

 

 

Re: FT8 and DXLabs

g4wjs
 

On 16/04/2019 00:40, Norman Heyen wrote:
I'm assuming I need to use JTAlert with DXLab and WSJT-X?
Norman,

that is one of two options that the document I linked suggests. *I recommend that you read it*, then decide which of the two configurations best suits your needs.

73
Bill
G4WJS.



--
73

Bill

G4WJS.

Re: LOTW-NO RESPONSE

 

Thanks much John. There in lies the problem. Its a XP machine with Explorer 7. No way to upgrade so I will just use my WIN 7 and WIN 10 machines
Thanks for taking the time to answer my query.
73
--
 Dave NU4N

"which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:"

Jim McPhee
 

 

In the file:///C:/DXLab/DXKeeper/Help/Progress.htm page, there is a line that states”


For seven of these award families, DXKeeper provides Realtime Award Tracking (RAT) service, which enables SpotCollector to immediately identify active DX stations with whom a QSO would advance your award progress, and which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:

This function is working perfectly, and has been for years,  with Spot Collector based on my settings for ARRL DX Century Club (DXCC). But I’ll be darned if I can figure out how to get DXKeeper to “to immediately identify QSOs whose confirmation would advance your award progress:”, and I’ve being looking very carefully through the settings and the Help Files.

Any help would be greatly appreciated.


Jim McPhee
Placitas, NM
W5ABA

Re: Smart SDR 3.0.1.9 loaded but WSJT-X stopped receiving

Dave AA6YQ
 

+ AA6YQ comments below

goes into TX , but not switching to RX, it stays in TX.....but then again, I never use this function.....I'm more of a control the radio and let the software follow kinda guy.....mainly cw here, using semi breakin, so I've never had the need to use that in commander.....

+ So you happen to not employ a function that doesn't work when Commander is controlling a Flex Signature running SmartSDR v3.

+ Anyone using Commander for transceiver control with FLDigi, MixW, MMTTY, MultiPSK, WinWarbler, or WSJT-X would not say that "DXLab works fine with SmartSDR v3".

73,

Dave, AA6YQ

Re: "which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:"

Dave AA6YQ
 

+ AA6YQ comments below

In the file:///C:/DXLab/DXKeeper/Help/Progress.htm page, there is a line that states”

For seven of these award families, DXKeeper provides Realtime Award Tracking (RAT) service, which enables SpotCollector <https://www.dxlabsuite.com/spotcollector> to immediately identify active DX stations with whom a QSO would advance your award progress, and which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:

This function is working perfectly, and has been for years, with Spot Collector based on my settings for ARRL DX Century Club (DXCC) <http://www.arrl.org/awards/dxcc/> . But I’ll be darned if I can figure out how to get DXKeeper to “to immediately identify QSOs whose confirmation would advance your award progress:”, and I’ve being looking very carefully through the settings and the Help Files.

+ On the Main window's QSL tab, set the "QSL Via" panel to cards or labels, and then click the "Add Needed" button; DXKeeper will populate the QSL Queue with each QSO whose confirmation would advance your award progress, as based on the objectives you've specified on the Configuration window's Awards tab. Load your printer with the appropriate media, and DXKeeper can then be directed to generate QSL cards or QSL labels requesting the needed confirmations, and envelopes or address labels to convey or route your outgoing QSL cards. For more information, see

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

73,

Dave, AA6YQ

Re: "which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:"

Jim McPhee
 

Dave,

Thank you for that explanation.

I was anticipating that if I had the "QSL Via" pane set to LoTW, that the main DXKeeper display would show active LoTW participants (based on the LoTW tab setting of "Maximum age of most recent LoTW upload to be considered "active" (months)", who had so far failed to QSL for a QSO that I had uploaded to LoTW. That would suggest to me that I should "ping" that LoTW participant via email, if they had uploaded to LoTW since our QSO took place.

Isn't that what SpotCollector is advising when a spot shows in the default blue font, with the yellow or light blue background? That I have a QSO logged with that station, but it has not been confirmed via LoTW?

73,

Jim McPhee
Placitas, NM
W5ABA

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Tuesday, April 16, 2019 3:48 PM
To: DXLab@groups.io
Subject: Re: [DXLab] "which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:"

+ AA6YQ comments below

In the file:///C:/DXLab/DXKeeper/Help/Progress.htm page, there is a line that states”

For seven of these award families, DXKeeper provides Realtime Award Tracking (RAT) service, which enables SpotCollector <https://www.dxlabsuite.com/spotcollector> to immediately identify active DX stations with whom a QSO would advance your award progress, and which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:

This function is working perfectly, and has been for years, with Spot Collector based on my settings for ARRL DX Century Club (DXCC) <http://www.arrl.org/awards/dxcc/> . But I’ll be darned if I can figure out how to get DXKeeper to “to immediately identify QSOs whose confirmation would advance your award progress:”, and I’ve being looking very carefully through the settings and the Help Files.

+ On the Main window's QSL tab, set the "QSL Via" panel to cards or labels, and then click the "Add Needed" button; DXKeeper will populate the QSL Queue with each QSO whose confirmation would advance your award progress, as based on the objectives you've specified on the Configuration window's Awards tab. Load your printer with the appropriate media, and DXKeeper can then be directed to generate QSL cards or QSL labels requesting the needed confirmations, and envelopes or address labels to convey or route your outgoing QSL cards. For more information, see

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

73,

Dave, AA6YQ
--
Jim McPhee
Placitas, NM
W5ABA

Re: "which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:"

Dave AA6YQ
 

+ AA6YQ comments below

Thank you for that explanation.

I was anticipating that if I had the "QSL Via" pane set to LoTW, that the main DXKeeper display would show active LoTW participants (based on the LoTW tab setting of "Maximum age of most recent LoTW upload to be considered "active" (months)", who had so far failed to QSL for a QSO that I had uploaded to LoTW.

+ That's not correct. On the Main window's QSL tab, setting the "QSL Via" panel to LoTW simply configures the controls on that tab for submitting QSOs to LoTW, and syncing with LoTW. See

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


That would suggest to me that I should "ping" that LoTW participant via email, if they had uploaded to LoTW since our QSO took place.

+ In the Filter panel at the bottom of the Main window's "Log QSOs" tab, depressing the CTRL key while clicking the LoTW button will filter the Log Page Display to contain all QSOs not yet confirmed via LoTW, even though your QSO partner has submitted QSOs to LoTW after the date of your QSO. These are QSOs partners that merit an email message, as they may have incorrectly submitted your QSO details to LoTW. See

<https://www.dxlabsuite.com/dxkeeper/Help/FilterLog.htm#LotW>


Isn't that what SpotCollector is advising when a spot shows in the default blue font, with the yellow or light blue background? That I have a QSO logged with that station, but it has not been confirmed via LoTW?

+ That's not correct. Background colors in SpotCollector only indicate a station's participation in LoTW by having submitted QSOs within a timeframe you've specified; they do not indicate the presence of unconfirmed QSOs in your log. See

<https://www.dxlabsuite.com/spotcollector/Help/SpotDatabase.htm#Highlighting%20Spot%20Database%20Entries%20of%20stations%20known%20to%20participate%20in%20ARRL's%20Logbook%20of%20the%20World%20(LotW)>

73,

Dave, AA6YQ

FW: [ARRL-LoTW] TQSL 2.4.5 Defect

Dave AA6YQ
 

A DXKeeper user reported a defect in TQSL 2.4.5 that could affect users of any logging program that runs on Windows and uses TQSL on behalf of the user.

If a QSO has an error, such as a bad callsign, then the message sent to command line applications is jumbled gibberish. It might have enough text to make out the message, and may not.

This doesn't affect TQSL used "directly", only when it's used by loggers to upload QSOs, but it makes it pretty difficult to understand why a QSO is being rejected.

If you're running into this, there's an updated version with the fix which the reporting user has confirmed corrects the defect.

The release candidate is available here:
https://www.rickmurphy.net/lotw/tqsl-2.4.6.msi


I'll be releasing this as production this weekend there's no other issues reported.

Apologies for yet another quick release, but this is a pretty serious defect.


73,
-Rick

Remove R from QSL sent box

Julio Peralta
 

Is there a way to remove the R from the QSL sent box for several QSO records at one time? I have a need to send just a couple of QSL’s to the buro and when I do an add requested about 10 QSO’s fill the window. I’m not sure how the R got placed in the sent box as I didn’t do it.

 

I only want to print one label and want to permanently remove the R from the QSL sent box of these others.

 

Julio, W4HY

Re: Remove R from QSL sent box

Salvatore Besso
 

Julio,

make a log backup before doing any en masse update.

Filter the log for the QSOs you need to modify.

Then open the (ADV)anced dialog.

At bottom select the field to be "bulk" modified in the "Item name"
combo box, in this case QSL_Sent.

Select the new value in the "Item new value" combo box, in this case
nothing (NULL), leave the combo empty.

Click the Mod button to update.

Did I alredy mention to BACKUP THE LOG before doing this operation? :-)

Did I alredy mention to FILTER THE LOG before doing this operation? :-)

I guess that the (R)equested value is a default, but I don't remember if
there is a setting modifiable by the user.

73 de
Salvatore (I4FYV)

for white stick operators

Frank Pletinck <frank.pletinck@...>
 

Hello,

 

Is there any white stick operator who uses dxlabsuite with jaws ?

 

73 Frank ON4AAC

Re: for white stick operators

eddy on5jk
 

Wat is Jaws? (Is ook een haaienfilm natuurlijk)

Eddy ON5JK

Op 17/04/2019 om 11:08 schreef Frank Pletinck:

Hello,

 

Is there any white stick operator who uses dxlabsuite with jaws ?

 

73 Frank ON4AAC


Virusvrij. www.avg.com

Re: "which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:"

Jim McPhee
 

Dave,

Thanks again for taking the time to provide that explanation.

If I may go back to the original question, because it appears I did not explain myself very well:

For seven of these award families, DXKeeper provides Realtime Award Tracking (RAT) service, which enables SpotCollector <https://www.dxlabsuite.com/spotcollector>  to immediately identify active DX stations with whom a QSO would advance your award progress, and which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:"

SpotCollector does do that "Realtime", without having to run a filtered report, by displaying "Unworked DX Band or Mode" in one colored font, and "Unconfirmed DX" in another colored font.

Is there a way to configure DXKeeper to, in Realtime,  "immediately identify QSOs whose confirmation would advance your award progress", similar to the way that SpotCollector does?

73,

 Jim McPhee

Placitas, NM

W5ABA

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Tuesday, April 16, 2019 7:37 PM
To: DXLab@groups.io
Subject: Re: [DXLab] "which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:"

+ AA6YQ comments below

Thank you for that explanation.

I was anticipating that if I had the "QSL Via" pane set to LoTW, that the main DXKeeper display would show active LoTW participants (based on the LoTW tab setting of "Maximum age of most recent LoTW upload to be considered "active" (months)", who had so far failed to QSL for a QSO that I had uploaded to LoTW.

+ That's not correct. On the Main window's QSL tab, setting the "QSL Via" panel to LoTW simply configures the controls on that tab for submitting QSOs to LoTW, and syncing with LoTW. See

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


That would suggest to me that I should "ping" that LoTW participant via email, if they had uploaded to LoTW since our QSO took place.

+ In the Filter panel at the bottom of the Main window's "Log QSOs" tab, depressing the CTRL key while clicking the LoTW button will filter the Log Page Display to contain all QSOs not yet confirmed via LoTW, even though your QSO partner has submitted QSOs to LoTW after the date of your QSO. These are QSOs partners that merit an email message, as they may have incorrectly submitted your QSO details to LoTW. See

<https://www.dxlabsuite.com/dxkeeper/Help/FilterLog.htm#LotW>


Isn't that what SpotCollector is advising when a spot shows in the default blue font, with the yellow or light blue background? That I have a QSO logged with that station, but it has not been confirmed via LoTW?

+ That's not correct. Background colors in SpotCollector only indicate a station's participation in LoTW by having submitted QSOs within a timeframe you've specified; they do not indicate the presence of unconfirmed QSOs in your log. See

<https://www.dxlabsuite.com/spotcollector/Help/SpotDatabase.htm#Highlighting%20Spot%20Database%20Entries%20of%20stations%20known%20to%20participate%20in%20ARRL's%20Logbook%20of%20the%20World%20(LotW)>

        73,

              Dave, AA6YQ



--
Jim McPhee
Placitas, NM
W5ABA