Date   

Re: Spot Collector spot changes radio to wrong Mode?

w2eck
 

Dave
I was not using Direct Operation between DXLab & WSJTX, did have Grid Tracker on line. But I now see the section https://www.dxlabsuite.com/spotcollector/Help/WSJTXInteraction.htm in the online help and will go thru and set that up
thanks for the Hint
73 Paul
w2eck


Re: Security Warning from Pathfinder

Dave AA6YQ
 

+ AA6YQ comments below

And that page contains at least one http link. Are there any Windows configuration changes that I could make that would prevent this warning from occurring?

+ Googling the first line of the Security Warning popup window

do you want to view only the web page content that was delivered securely

+ yields multiple articles explaining how to prevent this popup from appearing. If you find the right Windows setting, please post it here.

73,

Dave, AA6YQ


Re: Security Warning from Pathfinder

Dave AA6YQ
 

+ AA6YQ comments below

I sometimes get a Windows "Security Warning" (see a screenshot of it at https://groups.io/g/DXLab/files/Security%20Warning%20from%20Pathfinder-Screenshot%202022-11-16.jpg) from Pathfinder when clicking on a call sign in SpotCollector. I thought it was random until I saw a request from Dave in an old thread asking for some examples of call signs that caused this to occur. One example that causes this every time is 9H5BZ. If I find any others I will add them to this thread.
--
Jim McPhee
Placitas, NM
W5ABA

That error indicates that the html page that is to be delivered by https contains links to content (eg. images, style sheets, etc) that are plain http.

+ Thanks Jim, and Laurie!

+ QRZ exerts no control over what a QRZ user includes in his or her "QRZ page". Pathfinder is web browser; it will attempt to render the web pages at which you point it when you specify a callsign and invoke one if its Search buttons. If the contents of a web page include security violations, then whatever mechanisms on your system detect and report such violations will do so.

+ Best as I can tell, every QRZ page includes this "plain http" reference:

http://www.arrl.org/lotw/

73,

Dave, AA6YQ


Re: Security Warning from Pathfinder

Jim McPhee
 
Edited

And that page contains at least one http link. Are there any Windows configuration changes that I could make that would prevent this warning from occurring?

And that is one relaxed looking kangaroo on your qrz.com page!
--
Jim McPhee
Placitas, NM
W5ABA


Re: Security Warning from Pathfinder

JTAlert Support (VK3AMA)
 

On 17/11/2022 10:57 am, Jim McPhee wrote:
I sometimes get a Windows "Security Warning" (see a screenshot of it at https://groups.io/g/DXLab/files/Security%20Warning%20from%20Pathfinder-Screenshot%202022-11-16.jpg) from Pathfinder when clicking on a call sign in SpotCollector. I thought it was random until I saw a request from Dave in an old thread asking for some examples of call signs that caused this to occur. One example that causes this every time is 9H5BZ. If I find any others I will add them to this thread.
--
Jim McPhee
Placitas, NM
W5ABA

That error indicates that the html page that is to be delivered by https contains links to content (eg. images, style sheets, etc) that are plain http.


de Laurie VK3AMA


Security Warning from Pathfinder

Jim McPhee
 

I sometimes get a Windows "Security Warning" (see a screenshot of it at https://groups.io/g/DXLab/files/Security%20Warning%20from%20Pathfinder-Screenshot%202022-11-16.jpg) from Pathfinder when clicking on a call sign in SpotCollector. I thought it was random until I saw a request from Dave in an old thread asking for some examples of call signs that caused this to occur. One example that causes this every time is 9H5BZ. If I find any others I will add them to this thread.
--
Jim McPhee
Placitas, NM
W5ABA


Re: Spot Collector spot changes radio to wrong Mode?

Dave AA6YQ
 

+ AA6YQ comments below

I have Spot Collector filtered for just FT8, but when I click on any of those FT8 spots, my Flex 6600 changes to the correct band and freq but changes the radio mode to SSB.

+ Are you using the direct interoperation between DXLab and WSJT-X (SpotCollector considers the latter a spot source), or are you using JT-Alert?

73,

Dave, AA6YQ


Re: Question on Clublog Upload

Dave AA6YQ
 

+ AA6YQ comments below

With regards to "everything you've reported above is correct behavior" I assume DXKeeper believing virtually all QSOs have been uploaded to Clublog is a result of something I have set in DXKeeper.

+ That's false, as I've already explained in

https://groups.io/g/DXLab/message/211020

"Either the ADIF files you imported into DXKeeper included <APP_DXKEEPER_ClubLog:1> fields in each QSO, or you set the APP_DXKEEPER_ClubLog in your logged QSOs after importing them."

+ Are you going to respond to the questions I asked you in

https://groups.io/g/DXLab/message/211042

+ ?

+ Have you contacted Club Log Support to determine why DXKeeper is unable to authenticate and submit QSOs?

73

Dave, AA6YQ


Re: Spot Collector spot changes radio to wrong Mode?

Ed
 

Hi Paul,
I don’t have a FLEX.

FROM Dave’s help files:

Flex Signature (6000) Transceivers

When controlling a Flex Signature transceiver, Commander's Main window's Filters panel provides Width , High-cut, and Low-cut controls. The Main window's Filters panel also provides Group selector that lets you quickly choose pre-set WideNormal, or Narrow width and shift settings that you've defined for the SSB, CW, DIGL, DIGU, RTTY, and AM modes on the Configuration window's Filter Groups tab. Enabling the show each mode's Filter Group setting on this tab causes Commander to parenthetically display each mode's last Filter Group in the Main window's Mode panel.

Have you checked your settings as above?

ED WA6WGS


Spot Collector spot changes radio to wrong Mode?

w2eck
 

I have Spot Collector filtered for just FT8, but when I click on any of those FT8 spots, my Flex 6600 changes to the correct band and  freq but changes the radio mode to SSB. Any ideas on how to correct?
tnx
paul w2eck


Re: Question on Clublog Upload

w0rx - David Willis
 

With regards to "everything you've reported above is correct behavior" I assume DXKeeper believing virtually all QSOs have been uploaded to Clublog is a result of something I have set in DXKeeper.

What might that be?

Tnx and vy 73, Dave. w0rx

On 11/14/2022 1:03 PM, Dave AA6YQ wrote:
My credentials from DXLab are denied by Clublog:

"Upload File to Club Log: Login rejected; check the email address.....etc. specified in the DClub Log Panel on the QSL Configuration........"

This is the message received when trying to upload. So I logged into Clublog, with my browser, changed my password, logged out and logged in again. The new password works. Then I updated the info in the Panel dictated above, but when I tried to upload I still get the same rejection with the new password.

+ Only Club Log personnel can explain why your credentials are accepted from a web browser but not from DXKeeper. I suggest that you contact Club Log support.


None of my QSOs which I have logged with DXKeeper, starting 3/10/2022, have been uploaded to Clublog. Despite DXKeeper claiming so.
In addition to the 1939 QSOs I have made since 3/10/2022, DXKeeper thinks the logs I imported to set up DXKeeper in March were uploaded to Clublog. (Which they have been)

+ You've already described this situation, and I've suggested the steps you should take; see

https://groups.io/g/DXLab/message/211021

So whatever I have done to make DXKeeper think I have uploaded these QSOs to Clublog affects both my log imports and my real time logging in DXKeeper.

+ In what way are your log imports affected?

+ In what way is your real-time logging affected?


I don't even see an option in the import panel for this.

+ To what does "for this" refer?

And as I said before, the box to auto upload Qs to Clublog is not checked, in addition to my credentials being refused by Clublog. If DXKeeper tried to upload to Clublog because of an error I made in settings with DXKeeper I think I would have gotten the same rejection, or at least gotten some kind of error message. As is, I cannot upload to Clublog at all from DXKeeper.

+ Given that Club Log does not accept the username and password you've specified in DXKeeper, everything you've reported above is correct behavior. Until DXKeeper can authenticate with Club Log, it can provide no automation that involves access to Club Log.

73,

Dave, AA6YQ




--
vy 73, Dave, w0rx


Re: Commander Ports issue

Dave AA6YQ
 

+ AA6YQ comments below
finally" meant that I had trouble getting my FTDX3000 connected to my computer. Issue solved.

+ Thanks. I wanted to be sure that I didn't miss something in

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

 
I checked in Configuration to make sure the enable box was checked, it is. Then I noticed the work length was still set to 6. When I changed it to 8 the problem went away. When I now bring up Commander all is well.
+ So you had Commander configured to support multiple primary transceivers, in which case the "Word Length" setting on the Configuration window's "MultiRadio" tab must be set to 8. I'm glad that Commander is controlling your FTDX3000 now.

     73,

            Dave, AA6YQ


Re: Commander Ports issue

edward Deutsch
 

Dave,

"finally" meant that I had trouble getting my FTDX3000 connected to my computer. Issue solved.

I checked in Configuration to make sure the enable box was checked, it is. Then I noticed the work length was still set to 6. When I changed it to 8 the problem went away. When I now bring up Commander all is well.

Thanks Dave all your work.

Ed, KC9GF

On Tuesday, November 15, 2022 at 11:00:17 PM CST, Dave AA6YQ <aa6yq@...> wrote:


+ AA6YQ comments below
I finally got commander setup to work with my FTDX3000 Yaesu.

+ Why do you say "finally"? Was there a problem?

But, when I shut commander down and brought it back up the "word" length changed from 8 to 6. Change it back to 8 works but I have to do it each time I bring commander up. I have tried several thing to fix the problem. Any suggestions?
+ On the MultiRadio tab of Commander's Configuration window, there is a vertical row of four Enable boxes along the right side of the Control panel; are any of these boxes checked?

         73,

                  Dave, AA6YQ


Re: Commander Ports issue

Dave AA6YQ
 

+ AA6YQ comments below
I finally got commander setup to work with my FTDX3000 Yaesu.

+ Why do you say "finally"? Was there a problem?

But, when I shut commander down and brought it back up the "word" length changed from 8 to 6. Change it back to 8 works but I have to do it each time I bring commander up. I have tried several thing to fix the problem. Any suggestions?
+ On the MultiRadio tab of Commander's Configuration window, there is a vertical row of four Enable boxes along the right side of the Control panel; are any of these boxes checked?

         73,

                  Dave, AA6YQ


Commander Ports issue

edward Deutsch
 

I finally got commander setup to work with my FTDX3000 Yaesu. But, when I shut commander down and brought it back up the "word" length changed from 8 to 6. Change it back to 8 works but I have to do it each time I bring commander up. I have tried several thing to fix the problem. Any suggestions?

Ed, KC9GF 


Re: DXkeeper login fail to eQSL.cc

Dave AA6YQ
 

In the message below, I meant to say "contact eQSL support".

73,

Dave, AA6YQ

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Tuesday, November 15, 2022 5:13 PM
To: DXLab@groups.io
Subject: Re: [DXLab] DXkeeper login fail to eQSL.cc

+ AA6YQ comments below


I copied the Username and password from the Update window in the QSL configuration to notepad, confirmed that they were right then copied it to the eqsl.cc login. It logged in to eqsl.cc but I still got the login error message in DXkeeper. I renistalled DXkeeper and got the same result.

What else should I check

+ As I have already suggested, you should contact Club Log Support. Only they can tell you why the username and password you've selected are not enabling your instance of DXKeeper to authenticate with Club Log.

+ Uninstalling and re-installing DXKeeper could not possible solve this problem -- but could have created a much bigger problem. Never attempt to correct a problem with a DXLab application by uninstalling and then re-installing it unless there is hard evidence of a corrupted installation -- like error messages from Windows reporting missing components or libraries.

73,

Dave, AA6YQ


Email id new

Pat McGrath
 

Email


Re: DXkeeper login fail to eQSL.cc

Dave AA6YQ
 

+ AA6YQ comments below
I copied the Username and password from the Update window in the QSL configuration to notepad, confirmed that they were right then copied it to the eqsl.cc login.  It logged in to eqsl.cc but I still got the login error message in DXkeeper.  I renistalled DXkeeper and got the same result.

What else should I check

+ As I have already suggested, you should contact Club Log Support. Only they can tell you why the username and password you've selected are not enabling your instance of DXKeeper to authenticate with Club Log.

+ Uninstalling and re-installing DXKeeper could not possible solve this problem -- but could have created a much bigger problem. Never attempt to correct a problem with a DXLab application by uninstalling and then re-installing it unless there is hard evidence of a corrupted installation -- like error messages from Windows reporting missing components or libraries.

        73,

              Dave, AA6YQ


Re: DXkeeper login fail to eQSL.cc

bwschober@...
 

I copied the Username and password from the Update window in the QSL configuration to notepad, confirmed that they were right then copied it to the eqsl.cc login.  It logged in to eqsl.cc but I still got the login error message in DXkeeper.  I renistalled DXkeeper and got the same result.

What else should I check?


Re: Recent script for DXKeeper?

Dave AA6YQ
 

+ AA6YQ comments below
Thank you Dave. Apparently, I had not previously used the scripts to update and correct my log which contains records of contacts back to 1973.
 
So I ordered the scripts by date oldest to latest and then ran them one at a time. 
 
There were obviously a number of corrections.
 
Thanks again for the great toolbox that is DXLab Suite.
+ See

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

       73,

             Dave, AA6YQ