Date   

Re: Rotor Control

Julio Peralta
 

Never mind I figured it out. It’s working now.

 

Julio

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Julio Peralta via groups.io
Sent: Saturday, August 29, 2020 5:06 PM
To: DXLab io
Subject: [DXLab] Rotor Control

 

I used to be able to control my rotor using PstRotatorAZ. DXView used to talk to PstRotator. I have lost that ability and I can’t figure out why. I seem to remember that there was a setting in DXView’s rotor control tab that had to be set but I don’t see that now.

 

Was the ability to send heading info to PstRotator lost in the new version of DXView, 4.7.5?

 

Julio, W4HY


Rotor Control

Julio Peralta
 

I used to be able to control my rotor using PstRotatorAZ. DXView used to talk to PstRotator. I have lost that ability and I can’t figure out why. I seem to remember that there was a setting in DXView’s rotor control tab that had to be set but I don’t see that now.

 

Was the ability to send heading info to PstRotator lost in the new version of DXView, 4.7.5?

 

Julio, W4HY


QRZ/PF question

George Steube
 

This started today.  If I try to lookup a call from the capture window I get an error saying "Callbook error: Pathfinder not logged into QRZ.com.  But I am logged into QRZ and PF shows the call with all the call information.  The capture window remains blank except for the call.  I closed DXLabs and restarted the suite and made sure I was logged into QRZ and no change I still get a Callbook error. I have set QRZ to stay logged in for 30 days and call look ups from PF work.  Any suggestions?
73, George
W2GS


Re: Cluster Spot source address

Ron Gibson
 

Hi Franco,

You were showing as locked out. I've unlocked you. Give it a try now.

Ron,
VE3CGR


Re: Cluster Spot source address

Franco IZ4MJP
 

Thank you all for your help.

73,
Franco IZ4MJP


Re: Cluster Spot source address

Franco IZ4MJP
 

Hi Ron,
I used your service (within Spot Collector) until last March without problems.
Now SC "refuse the connection and close the peer" when attempting to connect to:

ve3cgr.dyndns.org:7300

I'm not experiencing problems with other cluster taken from the www.dxcluster.info/telnet/index.php

Sorry

73, Franco IZ4MJP


Re: Computer lockup when I click on Upload to LotW

Steve K8JQ
 

Nothing like Bitcoin mining going on -- at least not that I know of  :-)

Anti-malware is Windows Defender. It is configured to consider the DXLab folder as safe.

I will post results of uploads in safe-mode-with-networking in a week or two.

Thanks.

Steve, K8JQ
 

On 8/26/2020 7:53 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

Reboot at least every morning, usually more than that. RAM 32GB. I will look at Windows Task Manager next time -- if it will let me  :-)

+ Your reboot frequency and available RAM should be more than sufficient, unless you are running multiple protein folding or Bitcoin mining applications in the background.

+ Two other possibilities:

1. interference from a firewall or anti-malware application not configured to consider DXKeeper to be "safe"

2. misconfigured Windows Virtual Memory

+ The typical way to test for anti-malware interference is to reboot Windows into "safe mode with networking", as this  does not start your firewall and anti-malware. I know it'll be a pain, but each time you have QSOs to upload, reboot Windows into "safe mode with networking", start the Launcher, direct the Launcher to start DXKeeper, and then direct DXKeeper to upload your QSOs to LoTW. If you do this 5 times in succession without the "can't run other applications while uploading" symptom appearing, then we'll have gained an important clue.

          73,

                    Dave, AA6YQ







Re: Commander Multi Radio Secondary cat Port

Adrian Fewster <vk4tux@...>
 

Dave, Thankyou again for this great program,

 

Playing with Commander and the secondary CAT connection for the KX3 cat line to SPE, which was com 9,

… I went into advanced comport setting in device manager and changed com9 to com 1 (in use, but applied with a warning), that was already assigned to the real dB9

comport for SPE connection associated with FTDX101MP. > com 1

 

I did not expect anything, but it works great. The two SPE cables share the real comport 1 without issue in individual use as selected.

 

I can switch KX3 to FTDX101MP and vice versa on Commander, and the SPE is following the correct associated TXCR  frequency in each case.

 

This is exactly what I was looking for.  Just a FYI for those using mult radio/amp combinations on what works..  ;

 

 


Re: Printing in Specific Space on QSL

Dave AA6YQ
 

+ AA6YQ comments below

Wondering if anyone has had success in printing in a specific space on their QSL. I have been playing with the label and card settings but my only success so far has been to jam the printer after running my sacrificial QSL thru one too many times.
Yes, I could use stick-on labels but would prefer to laser print the info since the labels have a nasty habit of drying up and falling off after awhile.
My QSL is 3.5x5.5 and the info area is in the top right corner, 2.75 inches from the left edge and extending to the right edge. It is 1.63 inches deep or tall. Standard postcard orientation.

+ The QSL cards directly generated by DXKeeper are intentionally utilitarian, optimized for confirming large numbers of QSOs at low cost. If the QSL cards it generates don't meet your needs, DXKeeper can be configured to drive more sophisticated and flexible QSL card generators, as described here:

<https://www.dxlabsuite.com/dxkeeper/Help/QSL.htm#QSLing%20via%20ADIF>

73,

Dave, AA6YQ


Printing in Specific Space on QSL

Mike / W8DN
 

  Wondering if anyone has had success in printing in a specific space on their QSL. I have been playing with the label and card settings but my only success so far has been to jam the printer after running my sacrificial QSL thru one too many times.
  Yes, I could use stick-on labels but would prefer to laser print the info since the labels have a nasty habit of drying up and falling off after awhile.
  My QSL is 3.5x5.5 and the info area is in the top right corner, 2.75 inches from the left edge and extending to the right edge. It is 1.63 inches deep or tall. Standard postcard orientation.

Thanks,
Mike / W8DN


Re: Log question

Ed W2LCQ <w2lcq@...>
 

That solves my problem. Thanks for all that info Dave!

Best, Ed

73 de W2LCQ, Ed Jones

Frankford Radio Club
BUG 204 - CWops 701 (Life) - SKCC 5474T 
FISTS 12294 - QCWA 33438 - LICWC 51 - ARRL (NLI) - DXCC

“The present is theirs; the future, for which I really worked, is mine.” —- Nicola Tesla


On Aug 28, 2020, at 9:26 PM, Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

I’m fairly new to DXL. I’ve been working so far with CMD, DXK and SC. I notice that the QSO line on my log only  displays info from left to right from Call up until RST. From that point all the following info is obscured with a gray mask.

+ Nothing is being "obscured"; DXKeeper is displaying all of the columns you've configured the Log Page Display to include.

How can I display and get visibility to all the info on the log QSO line?

+ There are 119 items of information recorded with each logged QSO, so you likely don't want visibility to all of them in each Log Page Display entry, but you can add the ones you consider important using the procedure described here:

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

+ A description of each of those 119 items is available here:

<https://www.dxlabsuite.com/dxkeeper/Help/Items.htm>

   73,

           Dave, AA6YQ





Re: Log question

Dave AA6YQ
 

+ AA6YQ comments below

I’m fairly new to DXL. I’ve been working so far with CMD, DXK and SC. I notice that the QSO line on my log only displays info from left to right from Call up until RST. From that point all the following info is obscured with a gray mask.

+ Nothing is being "obscured"; DXKeeper is displaying all of the columns you've configured the Log Page Display to include.

How can I display and get visibility to all the info on the log QSO line?

+ There are 119 items of information recorded with each logged QSO, so you likely don't want visibility to all of them in each Log Page Display entry, but you can add the ones you consider important using the procedure described here:

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

+ A description of each of those 119 items is available here:

<https://www.dxlabsuite.com/dxkeeper/Help/Items.htm>

73,

Dave, AA6YQ


Log question

Ed W2LCQ <w2lcq@...>
 

I’m fairly new to DXL. I’ve been working so far with CMD, DXK and SC. I notice that the QSO line on my log only  displays info from left to right from Call up until RST. From that point all the following info is obscured with a gray mask. How can I display and get visibility to all the info on the log QSO line?  Thanks a lot!

Best Ed

73 de W2LCQ, Ed Jones

Frankford Radio Club
BUG 204 - CWops 701 (Life) - SKCC 5474T 
FISTS 12294 - QCWA 33438 - LICWC 51 - ARRL (NLI) - DXCC

“The present is theirs; the future, for which I really worked, is mine.” —- Nicola Tesla


Re: Importing QSOs.

Dave AA6YQ
 

+ AA6YQ comments below

I am a new member of the group, my first posting.

+ Welcome to DXLab!

Using wsjt-x and DXKeeper.

How do I import just new QSOs?

At the moment, I am importing the entire log every time which takes longer and longer.

+ You can enable the Import function's "duplicate checking" function, which is described here:

<https://www.dxlabsuite.com/dxkeeper/Help/Import.htm#Duplicate_Checking>

+ However, this is very inefficient, as DXKeeper has to check each QSO in the file being imported to see if it's already present in your log.

+ The better approach is to have WSJT-X log QSOs directly to DXKeeper, eliminating the need to manually import them. There are two ways that WSJT-X can interoperate with DXLab, on both ways give you direct logging to DXKeeper. They are described here:

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

+ with step-by-step configuration instructions available for both. Choose the one that best meets your needs.

73,

Dave, AA6YQ


Re: Importing QSOs.

W9MR Mike
 

Welcome to the group.

You should take a look at this article which describes how to connect WSJT-X with the DXLab Suite and perform direct logging operations.


73,
Mike ND9G


On Fri, Aug 28, 2020 at 1:29 PM Jim Peden via groups.io <g3zqq=yahoo.co.uk@groups.io> wrote:
Hi, 

I am a new member of the group, my first posting.

Using wsjt-x and DXKeeper.

How do I import just new QSOs?
At the moment, I am importing the entire log every time which takes longer and longer.

Jim, G3ZQQ


Importing QSOs.

Jim Peden
 

Hi, 

I am a new member of the group, my first posting.

Using wsjt-x and DXKeeper.

How do I import just new QSOs?
At the moment, I am importing the entire log every time which takes longer and longer.

Jim, G3ZQQ


Re: Cluster Spot source address

Ron Gibson
 

My cluster is alive and well. What makes you think it's no longer active?

Ron
VE3CGR


Re: Cluster Spot source address

Larry K8UT
 

If you're an N1MM user, the program uses a new crowd-sourced Cluster Rating system that collects cluster usage statistics from hams as they connect (or try to connect) to sites. The listing sorts by continent and lists each site with the number of connections (popularity) and percent of successful connections (failure rates). Only sites with > 75% success rates are displayed, and the data is continuously purged to exclude data older than about 30 days.

In the program, go to >Window >Telnet >Clusters

To read more about the feature, see this page:

-larry (K8UT)

------ Original Message ------
From: "Ed W2LCQ via groups.io" <w2lcq@...>
Sent: 2020-08-27 5:12:30 PM
Subject: Re: [DXLab] Cluster Spot source address

I have had great luck using NC7J DX cluster  Recommend it highly. 

73 de W2LCQ, Ed Jones

Frankford Radio Club
BUG 204 - CWops 701 - SKCC 5474T 
FISTS 12294 - QCWA 33438 - LICWC 51 - ARRL (NLI) - DXCC

“The present is theirs; the future, for which I really worked, is mine.” —- Nicola Tesla


On Aug 27, 2020, at 5:00 PM, Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

After some months of absence from HAM activities i found that some cluster spot sources are no longer active (VE3CGR and ZL2AQY for example).
I'm looking for some NA - JA - ZL valid DX Clusters sources for Spot Collector.

Could someone kindly suggest me some address?

+ A directory of active DX Clusters is available here:

<http://www.dxcluster.info/telnet/index.php>

+ Reviewing this information may be helpful:

<https://www.dxlabsuite.com/spotcollector/Help/SourceConnection.htm#Connecting%20to%20DXClusters>

       73,

            Dave, AA6YQ






Re: Cluster Spot source address

Ed W2LCQ <w2lcq@...>
 

I have had great luck using NC7J DX cluster  Recommend it highly. 

73 de W2LCQ, Ed Jones

Frankford Radio Club
BUG 204 - CWops 701 - SKCC 5474T 
FISTS 12294 - QCWA 33438 - LICWC 51 - ARRL (NLI) - DXCC

“The present is theirs; the future, for which I really worked, is mine.” —- Nicola Tesla


On Aug 27, 2020, at 5:00 PM, Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

After some months of absence from HAM activities i found that some cluster spot sources are no longer active (VE3CGR and ZL2AQY for example).
I'm looking for some NA - JA - ZL valid DX Clusters sources for Spot Collector.

Could someone kindly suggest me some address?

+ A directory of active DX Clusters is available here:

<http://www.dxcluster.info/telnet/index.php>

+ Reviewing this information may be helpful:

<https://www.dxlabsuite.com/spotcollector/Help/SourceConnection.htm#Connecting%20to%20DXClusters>

       73,

            Dave, AA6YQ






Re: Question on Check Progress

Dave AA6YQ
 

+ AA6YQ comments below

I noticed on the IOTA Realtime Awards tracking tab that the "RSGB" column contains letter codes that are not explained in the "Key" that appears to the right. Namely the letters "H", "D" and "P" appear next to certain IOTA references. Can someone explain to mean the meaning of these codes?

+ As documented in

<https://www.dxlabsuite.com/dxkeeper/Help/Progress.htm#Realtime%20Award%20Tracking%20for%20RSGB%20IOTA%20Awards>

D - deleted

P - provisional

H - on hold pending additional information

+ Since IOTA is now independent of RSGB, the "RSGB" column has been renamed "Status" in the next version of DXKeeper.

73,

Dave, AA6YQ

14281 - 14300 of 210228