Date   

Re: FT-8 lag?

Matt Foster
 

I'm having the same issue with my IC-7300 using Split mode in WSJT-X. Also getting about a 2-3s delay switching to transmit. I'm using the "Fake It" option in WSJT-X for now.

I can provide a debug log from Commander, if that would help.

73, Matt, N0EYE


Re: Updating Distance for existing logs

Dave AA6YQ
 

+ AA6YQ comments below

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of w8be
Sent: Sunday, April 26, 2020 12:55 PM
To: DXLab@groups.io
Subject: [DXLab] Updating Distance for existing logs

Hello,

I am trying to re calculate the distance and update my log records....I am following this procedure:


Updating Already Logged QSOs

If you have been logging QSOs without recording their antenna path, you can use DXKeeper's Advanced Sorts, Filters, and Modifiers window's Modify QSOs <http://www.dxlabsuite.com/dxlabwiki/QSOModifying>; panel to set the the antenna path items of your QSOs to S en masse; just be sure to make a log backup beforehand by clicking the Backup button on the Configuration window's Log tab. After manually correcting the antenna path items of any known long path QSOs to L, you can then use the Modify QSOs <http://www.dxlabsuite.com/dxlabwiki/QSOModifying>; panel to

1. compute the distance item for each QSO by setting the Item ADIF field name selector to DISTANCE and by setting the Item new value to <COMPUTE> before clicking the Mod button

2. compute the antenna azimuth item for each QSO by setting the Item ADIF field name selector to ANT_AZ and by setting the Item new value to <COMPUTE> before clicking the Mod button


I can not get it to update the distance in the logs. I picked one record and tried the options but the distance field is still blank. I can manually set it but when using <compute> all I see is a null value.
I was not sure if I needed DXView and Path finder so I started them but still it does not update. For example I have selected a call in the filter and in the advanced section I am selecting distance under modify QSO in Log Page Display. When I click on the Mod button, I do see the msg 'Compute the value of the DISTANCE item of each qualifying QSO in the Log Page Display'. At that point I still see no distance information

+ Above, you quote from the last section of the article in

<https://www.dxlabsuite.com/dxlabwiki/QSODistance>;

+ The first two section describe additional requirements for computing a QSO's "distance": DXKeeper must be able to determine your location, and the location of your QSO partner.

+ On DXKeeper's Main window's myQTHs tab, do you have one or more "myQTHs" defined? If not, have you specified your QTH latitude and longitude on the Configuration window's Defaults?

+ Pick a QSO for which the distance item has not been populated. Does this QSO specify a grid square?

73,

Dave, AA6YQ


Re: WSJT with SpotCollector

Matt Wilhelm
 

I have no doubt.   For my needs, I do a lot of different types of filtering at the cluster level and I hadn't run into the need to send ascii codes...yet.  Thanks for the history.

73,

Matt W1PY


On Sun, Apr 26, 2020 at 1:59 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

> When you have a chance, could you still look into why the telnet
> macros in spotcollector are not passing <> to the cluster or is that
> by design?

In the "Initial Cluster command", < and > are used to set of a specific ASCII character.  For example, <13><10> sends CRLF (Return, Enter).

See the Spot Collector Help file

+ SpotCollector's use of <> to enclose ascii codes pre-dates clusters employing < and > characters in their filtering by more than a decade.

        73,

             Dave, AA6YQ





Re: WSJT with SpotCollector

Dave AA6YQ
 

+ AA6YQ comments below

When you have a chance, could you still look into why the telnet
macros in spotcollector are not passing <> to the cluster or is that
by design?
In the "Initial Cluster command", < and > are used to set of a specific ASCII character. For example, <13><10> sends CRLF (Return, Enter).

See the Spot Collector Help file

+ SpotCollector's use of <> to enclose ascii codes pre-dates clusters employing < and > characters in their filtering by more than a decade.

73,

Dave, AA6YQ


Re: WSJT with SpotCollector

Matt Wilhelm
 

Thanks for pointing me in the right direction Joe!

'SET DX FILTER SPOTTER <60><62> K2PO/7' does the trick.

73,

Matt W1PY


On Sun, Apr 26, 2020 at 1:35 PM Joe Subich, W4TV <lists@...> wrote:


> When you have a chance, could you still look into why the telnet
> macros in spotcollector are not passing <> to the cluster or is that
> by design?

In the "Initial Cluster command", < and > are used to set of a
specific ASCII character.  For example, <13><10> sends CRLF
(Return, Enter).

See the Spot Collector Help file

73,

    ... Joe, W4TV


On 2020-04-26 12:06 PM, Matt Wilhelm wrote:
> Bah. You're right.  I saw the OP's message in quick scan to see if anyone
> else was seeing the same issue I was.  The syntax was the similar, but the
> question and configuration was not.  Sorry for any confusion there. When
> you have a chance, could you still look into why the telnet macros in
> spotcollector are not passing <> to the cluster or is that by design?
>
> Thanks,
>
> Matt  W1PY
>
> On Sun, Apr 26, 2020 at 11:46 AM Dave AA6YQ <aa6yq@...> wrote:
>
>> + AA6YQ comments below
>>
>> On Sun, Apr 26, 2020 at 04:41 AM, Matt Wilhelm wrote:
>>
>> I'm wondering if Daniel's issue is something that I came across this
>> morning.  I was trying to filter out spots from K2PO/7 on the AR cluster
>> that I'm connected to because my use of SPOTTERZONE=5 does not catch that
>> station.  What I found (examples below) is that spotcollector is not
>> passing <> (not equal) to the cluster when the filter is built in the macro
>> configuration.  However, If you drop the filter right into the telnet
>> filter, it does pass <>.
>>
>> + "SPOTTERZONE=5" is a cluster filter.
>>
>> + SpotCollector's filtering is not accomplished by sending filter
>> directives to a spot source (e.g. a DX cluster). Any filtering implemented
>> by a spot source results in spots being permanently discarded.
>>
>> + SpotCollector uses the information from incoming spots to maintain a
>> database with an entry for each active DX stations operating in a
>> particular mode near a particular frequency. Filtering is accomplished by
>> displaying a subset of the information in that database, not be discarding
>> information.
>>
>> + See <https://www.dxlabsuite.com/dxlabwiki/CollectingSpots>
>> <https://www.dxlabsuite.com/dxlabwiki/CollectingSpots>
>>
>> + and <https://www.dxlabsuite.com/dxlabwiki/SpotDatabaseFilter>
>> <https://www.dxlabsuite.com/dxlabwiki/SpotDatabaseFilter>
>>
>>        73,
>>
>>              Dave, AA6YQ
>>
>>
>>





Re: DxKeeper Freezing with JT Alert

Hasan Schiers N0AN
 

I thought the immediate upload feature of DXK was fantastic when I first used it. After a few weeks I noticed two things:

1. It more often than I found acceptable encountered problems with LoTW site being down. So I had to wait for DXK/TQSL upload to time out before I could resume normal operation, for every qso I made. In real time, this is tedious.

2. Even when LoTW was working correctly, the immediate upload slowed down the finished process to the point that it was annoying. (and I have a 100 Mb/s up/down fiber optic connection).

It just made the whole process a bit clunky and with no real advantage for my use. Now I can wait as along as I like:

1. After a group of qsos
2. After my operating session is finished
3. After my operating for the day is finished
4. Until tomorrow or the day after ...or the day after that.

All one needs do is:

Click on the QSL Tab
Click Add Requested Button
Click on Upload to LotW Button

The delay to do an entire days' operation is barely longer, if at all longer than the delay to upload one qso. 

So, there are other reasons not to use immediate upload other than a slow internet connection. It's all a matter of personal preference.

73, N0AN
Hasan


On Sun, Apr 26, 2020 at 11:37 AM Carl - WC4H via groups.io <wc4h.dx=yahoo.com@groups.io> wrote:
Hi Bob.

The setting instructs DXKeeper to Upload to LoTW.  JTAlerts is not doing the uploading.
Why after each contact?  Well, it's a preference.  Most of us pay exorbitant amounts for high speed internet, why not use it to the max.  I know I do.

73.
Carl - WC4H


Re: WSJT with SpotCollector

Joe Subich, W4TV
 

When you have a chance, could you still look into why the telnet
macros in spotcollector are not passing <> to the cluster or is that
by design?
In the "Initial Cluster command", < and > are used to set of a
specific ASCII character. For example, <13><10> sends CRLF
(Return, Enter).

See the Spot Collector Help file

73,

... Joe, W4TV


On 2020-04-26 12:06 PM, Matt Wilhelm wrote:
Bah. You're right. I saw the OP's message in quick scan to see if anyone
else was seeing the same issue I was. The syntax was the similar, but the
question and configuration was not. Sorry for any confusion there. When
you have a chance, could you still look into why the telnet macros in
spotcollector are not passing <> to the cluster or is that by design?
Thanks,
Matt W1PY
On Sun, Apr 26, 2020 at 11:46 AM Dave AA6YQ <aa6yq@ambersoft.com> wrote:

+ AA6YQ comments below

On Sun, Apr 26, 2020 at 04:41 AM, Matt Wilhelm wrote:

I'm wondering if Daniel's issue is something that I came across this
morning. I was trying to filter out spots from K2PO/7 on the AR cluster
that I'm connected to because my use of SPOTTERZONE=5 does not catch that
station. What I found (examples below) is that spotcollector is not
passing <> (not equal) to the cluster when the filter is built in the macro
configuration. However, If you drop the filter right into the telnet
filter, it does pass <>.

+ "SPOTTERZONE=5" is a cluster filter.

+ SpotCollector's filtering is not accomplished by sending filter
directives to a spot source (e.g. a DX cluster). Any filtering implemented
by a spot source results in spots being permanently discarded.

+ SpotCollector uses the information from incoming spots to maintain a
database with an entry for each active DX stations operating in a
particular mode near a particular frequency. Filtering is accomplished by
displaying a subset of the information in that database, not be discarding
information.

+ See <https://www.dxlabsuite.com/dxlabwiki/CollectingSpots>;
<https://www.dxlabsuite.com/dxlabwiki/CollectingSpots>;

+ and <https://www.dxlabsuite.com/dxlabwiki/SpotDatabaseFilter>;
<https://www.dxlabsuite.com/dxlabwiki/SpotDatabaseFilter>;

73,

Dave, AA6YQ



Updating Distance for existing logs

w8be
 

Hello,

I am trying to re calculate the distance and update my log records....I am following this procedure:

Updating Already Logged QSOs

If you have been logging QSOs without recording their antenna path, you can use DXKeeper's Advanced Sorts, Filters, and Modifiers window's Modify QSOs panel to set the the antenna path items of your QSOs to S en masse; just be sure to make a log backup beforehand by clicking the Backup button on the Configuration window's Log tab. After manually correcting the antenna path items of any known long path QSOs to L, you can then use the Modify QSOs panel to

  1. compute the distance item for each QSO by setting the Item ADIF field name selector to DISTANCE and by setting the Item new value to <COMPUTE> before clicking the Mod button

  2. compute the antenna azimuth item for each QSO by setting the Item ADIF field name selector to ANT_AZ and by setting the Item new value to <COMPUTE> before clicking the Mod button


I can not get it to update the distance in the logs.  I picked one record and tried the options but the distance field is still blank.  I can manually set it but when using <compute> all I see is a null value.  
I was not sure if I needed DXView and Path finder so I started them but still it does not update.  For example I have selected  a call in the filter and in the advanced section I am selecting distance under modify QSO in Log Page Display.  When I click on the Mod button,  I do see the msg 'Compute the value of the DISTANCE item of each qualifying QSO in the Log Page Display'.   At that point I still see no distance information 

Any advice is appreciate.

thanks Mike


Re: DxKeeper Freezing with JT Alert

Carl - WC4H
 

Hi Bob.

The setting instructs DXKeeper to Upload to LoTW.  JTAlerts is not doing the uploading.
Why after each contact?  Well, it's a preference.  Most of us pay exorbitant amounts for high speed internet, why not use it to the max.  I know I do.

73.
Carl - WC4H


Re: DxKeeper Freezing with JT Alert

Gilbert Baron W0MN
 

 

 

Outlook Laptop Gil W0MN

Hierro candente, batir de repente

44.08226N 92.51265W EN34rb

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of KA9JAC
Sent: Sunday, April 26, 2020 11:10
To: DXLab@groups.io
Subject: Re: [DXLab] DxKeeper Freezing with JT Alert

 

First question that comes to my mind is...
Why do you want jtalert uploading to LOTW when you are using DXKeeper?

My thought is that you should be doing your lotw uploads from DXKeeper,
Since this is where you want to have things in sync.

73
Bob

PS I don't understand why folks have a need to upload after every q anyway.

 

BECAUSE WITH DXKEEPER IT IS FAST AND EASY AND YOU DO NOT FORGET TO GET SOMETHING DONE.




On 4/26/2020 11:03 AM, Dave AA6YQ wrote:

+ AA6YQ comments below

On Sun, Apr 26, 2020 at 08:50 AM, Ellam, Timothy St. J. wrote:

I reinstalled AVG (and upgraded it). The issue is still there. Every 7 Qs DXkeeper freezes requiring me to shut it down and restart (it takes several minutes to reappear). I have looked at other start up applications and disabled them on start up, but the problem persists. I have a work around where I disable automatic uploads to LOTW in JTAlert and that seems to prevent DXKeeper from locking up. I suspect I may need to reinstall Win10 as I am having some other issues recently (programs not opening) that suggest there is some form of corruption within Win 10 (we had a power cut causing the computer to shut down. On power up is when these problems started to develop).

+ Previously, you reported that there was no "freezing" after Windows was rebooted into "Safe mode with networking". That's indicative of interference from an anti-malware application; it is not indicative of a problem with Windows.

+ If AVG was the culprit, re-installing and upgrading it would likely not cure the interference. You must properly configure it or, if it doesn't work correctly on your system, replace it.

       73,

            Dave, AA6YQ

 

 

 


AVG logo

This email has been checked for viruses by AVG antivirus software.
www.avg.com




--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop


Re: DxKeeper Freezing with JT Alert

KA9JAC
 

First question that comes to my mind is...
Why do you want jtalert uploading to LOTW when you are using DXKeeper?

My thought is that you should be doing your lotw uploads from DXKeeper,
Since this is where you want to have things in sync.

73
Bob

PS I don't understand why folks have a need to upload after every q anyway.



On 4/26/2020 11:03 AM, Dave AA6YQ wrote:

+ AA6YQ comments below

On Sun, Apr 26, 2020 at 08:50 AM, Ellam, Timothy St. J. wrote:

I reinstalled AVG (and upgraded it). The issue is still there. Every 7 Qs DXkeeper freezes requiring me to shut it down and restart (it takes several minutes to reappear). I have looked at other start up applications and disabled them on start up, but the problem persists. I have a work around where I disable automatic uploads to LOTW in JTAlert and that seems to prevent DXKeeper from locking up. I suspect I may need to reinstall Win10 as I am having some other issues recently (programs not opening) that suggest there is some form of corruption within Win 10 (we had a power cut causing the computer to shut down. On power up is when these problems started to develop).

+ Previously, you reported that there was no "freezing" after Windows was rebooted into "Safe mode with networking". That's indicative of interference from an anti-malware application; it is not indicative of a problem with Windows.

+ If AVG was the culprit, re-installing and upgrading it would likely not cure the interference. You must properly configure it or, if it doesn't work correctly on your system, replace it.

       73,

            Dave, AA6YQ

 





AVG logo

This email has been checked for viruses by AVG antivirus software.
www.avg.com



Re: WSJT with SpotCollector

Matt Wilhelm
 

Bah. You're right.  I saw the OP's message in quick scan to see if anyone else was seeing the same issue I was.  The syntax was the similar, but the question and configuration was not.  Sorry for any confusion there. When you have a chance, could you still look into why the telnet macros in spotcollector are not passing <> to the cluster or is that by design?

Thanks,

Matt  W1PY

On Sun, Apr 26, 2020 at 11:46 AM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

On Sun, Apr 26, 2020 at 04:41 AM, Matt Wilhelm wrote:
I'm wondering if Daniel's issue is something that I came across this morning.  I was trying to filter out spots from K2PO/7 on the AR cluster that I'm connected to because my use of SPOTTERZONE=5 does not catch that station.  What I found (examples below) is that spotcollector is not passing <> (not equal) to the cluster when the filter is built in the macro configuration.  However, If you drop the filter right into the telnet filter, it does pass <>.  

+ "SPOTTERZONE=5" is a cluster filter.

+ SpotCollector's filtering is not accomplished by sending filter directives to a spot source (e.g. a DX cluster). Any filtering implemented by a spot source results in spots being permanently discarded.

+ SpotCollector uses the information from incoming spots to maintain a database with an entry for each active DX stations operating in a particular mode near a particular frequency. Filtering is accomplished by displaying a subset of the information in that database, not be discarding information.

+ See <https://www.dxlabsuite.com/dxlabwiki/CollectingSpots>

+ and <https://www.dxlabsuite.com/dxlabwiki/SpotDatabaseFilter>

      73,

            Dave, AA6YQ


Re: DxKeeper Freezing with JT Alert

Dave AA6YQ
 

+ AA6YQ comments below

On Sun, Apr 26, 2020 at 08:50 AM, Ellam, Timothy St. J. wrote:

I reinstalled AVG (and upgraded it). The issue is still there. Every 7 Qs DXkeeper freezes requiring me to shut it down and restart (it takes several minutes to reappear). I have looked at other start up applications and disabled them on start up, but the problem persists. I have a work around where I disable automatic uploads to LOTW in JTAlert and that seems to prevent DXKeeper from locking up. I suspect I may need to reinstall Win10 as I am having some other issues recently (programs not opening) that suggest there is some form of corruption within Win 10 (we had a power cut causing the computer to shut down. On power up is when these problems started to develop).

+ Previously, you reported that there was no "freezing" after Windows was rebooted into "Safe mode with networking". That's indicative of interference from an anti-malware application; it is not indicative of a problem with Windows.

+ If AVG was the culprit, re-installing and upgrading it would likely not cure the interference. You must properly configure it or, if it doesn't work correctly on your system, replace it.

       73,

            Dave, AA6YQ

 


Re: DxKeeper Freezing with JT Alert

Ellam, Timothy St. J.
 

Dave

I reinstalled AVG (and upgraded it). The issue is still there. Every 7 Qs DXkeeper freezes requiring me to shut it down and restart (it takes several minutes to reappear). I have looked at other start up applications and disabled them on start up, but the problem persists. I have a work around where I disable automatic uploads to LOTW in JTAlert and that seems to prevent DXKeeper from locking up. I suspect I may need to reinstall Win10 as I am having some other issues recently (programs not opening) that suggest there is some form of corruption within Win 10 (we had a power cut causing the computer to shut down. On power up is when these problems started to develop).


73

Tim VE6SH


Re: WSJT with SpotCollector

Dave AA6YQ
 

+ AA6YQ comments below

On Sun, Apr 26, 2020 at 04:41 AM, Matt Wilhelm wrote:
I'm wondering if Daniel's issue is something that I came across this morning.  I was trying to filter out spots from K2PO/7 on the AR cluster that I'm connected to because my use of SPOTTERZONE=5 does not catch that station.  What I found (examples below) is that spotcollector is not passing <> (not equal) to the cluster when the filter is built in the macro configuration.  However, If you drop the filter right into the telnet filter, it does pass <>.  

+ "SPOTTERZONE=5" is a cluster filter.

+ SpotCollector's filtering is not accomplished by sending filter directives to a spot source (e.g. a DX cluster). Any filtering implemented by a spot source results in spots being permanently discarded.

+ SpotCollector uses the information from incoming spots to maintain a database with an entry for each active DX stations operating in a particular mode near a particular frequency. Filtering is accomplished by displaying a subset of the information in that database, not be discarding information.

+ See <https://www.dxlabsuite.com/dxlabwiki/CollectingSpots>

+ and <https://www.dxlabsuite.com/dxlabwiki/SpotDatabaseFilter>

      73,

            Dave, AA6YQ


Re: Com port issue

Steve <KH6CT@...>
 

HI Jim...
This probably has nothing to do with your solved issue.  But if you need virtual serial ports for other applications try com0com.  A google search will find it easily.  Free, easy to use and most of all it works.

73, Steve KH6CT


Re: WSJT with SpotCollector

Matt Wilhelm
 

Just a quick follow up.  I do think I figured out why my filter (when the <> is passed directly in the telnet window) was not working. It needed to be SPOTTER<>K2PO/7-# since that's its actual name as a skimmer.  Still not passing the <> from the macro config, but wanted to post that update in case anyone cared or was following along or it comes up in a search when someone is trying to troubleshoot a similar issue.

Thanks & 73,

Matt W1PY


Re: WSJT with SpotCollector

Matt Wilhelm
 

I'm wondering if Daniel's issue is something that I came across this morning.  I was trying to filter out spots from K2PO/7 on the AR cluster that I'm connected to because my use of SPOTTERZONE=5 does not catch that station.  What I found (examples below) is that spotcollector is not passing <> (not equal) to the cluster when the filter is built in the macro configuration.  However, If you drop the filter right into the telnet filter, it does pass <>.  

Examples:

SET DX FILTER (SPOTTERCQZONE=5 AND SPOTTER<>K2PO/7 AND SKIMVALID) OR CALL={MYCALL}  OR (SPOTTERCQZONE=5 AND NOT SKIMMER)

When configured as a macro-

SET DX FILTER (SPOTTERCQZONE=5 AND SPOTTERK2PO/7 AND SKIMVALID) OR CALL={MYCALL}  OR (SPOTTERCQZONE=5 AND NOT SKIMMER)
ERROR - The requested DX filter did not pass validation and was rejected.  Please re-check.
   Requested filter - (SPOTTERCQZONE=5 AND SPOTTERK2PO/7 AND SKIMVALID) OR CALL={MYCALL}  OR (SPOTTERCQZONE=5 AND NOT SKIMMER)
Error processing Set Dx Filter command: SET DX FILTER (SPOTTERCQZONE=5 AND SPOTTERK2PO/7 AND SKIMVALID) OR CALL={MYCALL}  OR (SPOTTERCQZONE=5 AND NOT SKIMMER)


When dropped right into the telnet window-

SET DX FILTER (SPOTTERCQZONE=5 AND SPOTTER<>K2PO/7 AND SKIMVALID) OR CALL={MYCALL}  OR (SPOTTERCQZONE=5 AND NOT SKIMMER)
DX filter set to: (spottercqzone = 5 and spotter <> k2po/7 and skimvalid) or call = {mycall} or (spottercqzone = 5 and not skimmer)

As you can see in the first example the <> is not being passed to the cluster so it looks like "SPOTTERK2PO/7" .  My filter still isn't filtering out K2PO/7 skimmer spots, but I happened across this issue while trying to set it up this morning.  If this is a bug that has cropped up, I hope this helps to fix it.

Thanks & 73,

Matt W1PY


Re: More Digital Modes?

Dave AA6YQ
 

+ AA6YQ comment below

You have more digital modes than you will ever need , already ! Use Multipsk and it seamlessly integrates with Commander , SpotCollector and DxKeeper .

+ Good point, Andy! I'd forgotten that there's no "bridge" required to use Multipsk with DXLab.

73,

Dave, AA6YQ


Re: More Digital Modes?

Andrew OBrien
 

You have more digital modes than you will ever need , already ! Use Multipsk and it seamlessly integrates with Commander , SpotCollector and DxKeeper .  

Andy


On Apr 25, 2020, at 11:43 PM, n6rsh <stevenpanattoni@...> wrote:

I understand. Thank you, Dave
Steve - N6RSH

5781 - 5800 of 199008