Date   

Re: DXkeeper "Look-Up" is slowed.....Error Logs attached

Gary Smetana
 

Disabled Windows Defender by:

   - turned OFF Real-Time protection
   - turned OFF Cloud-delivered protection
   - turned OFF Tamper protection

Disabled Windows Defender Firewall

No improvement in DXcapture Lookup response time.





From: DXLab@groups.io <DXLab@groups.io> on behalf of Dave AA6YQ <aa6yq@...>
Sent: Friday, April 10, 2020 10:02 PM
To: DXLab@groups.io <DXLab@groups.io>
Subject: Re: [DXLab] DXkeeper "Look-Up" is slowed.....Error Logs attached
 
+ AA6YQ comments below

I disabled the automatic startup (via Task manager) of all (14) Windows applications, and rebooted Windows (normal);  Lookup
response time has not improved; still takes 4-5 seconds w/hourglass.

I use only Windows Defender.  It shows NO History of quarantine.    No history at all.

What to try next ?

+ Try temporarily disabling Windows defender. Also disable your firewall application.

      73,

                Dave, AA6YQ





Re: DXKeeper Update Failure

Scott
 

Figured it out with trial and error. I've never encountered anything like this before. 

Scott


Re: DXKeeper Update Failure

Scott
 

Dave, thank you for the quick reply. This is where I'm totally lost. I use Windows Defender. I have looked and all DXLabs apps are allowed, and have been that way. I have no idea where to go next 

1. configure your anti-malware application to consider the DXLab application to be "safe"; otherwise, your anti-malware application may delete the re-created file

Can you or someone tell me more specifically how I do this above step? It's Win10. Is Windows Defender the same as the anti-malware application? 


Re: DXkeeper "Look-Up" is slowed.....Error Logs attached

Dave AA6YQ
 

+ AA6YQ comments below

I disabled the automatic startup (via Task manager) of all (14) Windows applications, and rebooted Windows (normal); Lookup
response time has not improved; still takes 4-5 seconds w/hourglass.

I use only Windows Defender. It shows NO History of quarantine. No history at all.

What to try next ?

+ Try temporarily disabling Windows defender. Also disable your firewall application.

73,

Dave, AA6YQ


Re: DXKeeper Update Failure

Dave AA6YQ
 

+ AA6YQ comments below

I attempted to update my DXKeeper and the other programs that needed updated through the Launcher. I was given a warning to close DXKeeper before attempting to upgrade, so I closed it. When I attempted to upgrade I got a message file C:\DXLab\DXKeeper.exe does not exist. Sure enough it was not there. There was the DXKeeper1537 in the folder so I opened it successfully. It included my entire logbook, includingsome QSO's I made this evening in FT4 and FT8, so I immediately did a backup of my logbook. I have no idea where the DXKeeper.exe file went, so I copied the DXKeeper1537 and renamed the copy to DXKeeper.exe, however it still will not launch from the launcher, and I am not able to update to the new version. I'm not sure what to do next besides manually opening the DXKeeper1537 version.

Any assistance would be appreciated.

There have been more than 450 messages posted here over the past week on the topic of DXLab executable files being quarantined or deleted by Microsoft anti-malware applications.

Your anti-malware application is defective, as you can see for yourself:

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

To recover from the damage your anti-malware application caused, see

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

73,

Dave, AA6YQ


Re: DXkeeper "Look-Up" is slowed.....Error Logs attached

Gary Smetana
 

I disabled the automatic startup (via Task manager) of all (14) Windows applications, and rebooted Windows (normal);  Lookup response time has not improved; still takes 4-5 seconds w/hourglass.

I use only Windows Defender.  It shows NO History of quarantine.    No history at all.

What to try next ?
    


From: DXLab@groups.io <DXLab@groups.io> on behalf of Dave AA6YQ <aa6yq@...>
Sent: Friday, April 10, 2020 9:35 PM
To: DXLab@groups.io <DXLab@groups.io>
Subject: Re: [DXLab] DXkeeper "Look-Up" is slowed.....Error Logs attached
 
+ AA6YQ comments below

Results with "Safe Boot w/Networking"......doing call Lookup in DXcapture, or doing DXkeeper Filter:Lookup....very fast response.

Results with Normal Boot.....slow 4-5 second response ...doing the above Lookups.

+ That means an application automatically started by Windows when booted normally is interfering with communication among your
DXKeeper applications. The usual culprit is an anti-malware application, but other culprits have been reported:

<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.dxlabsuite.com%2Fdxlabwiki%2FApplicationInteference&amp;data=02%7C01%7C%7Cbbda76f1bbcc4465451908d7ddb8aa4c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637221657501007788&amp;sdata=1sa1VIy1yrU2%2Bp1XfqGVSU5RIGWn1fAfQS2bQi6ovSc%3D&amp;reserved=0>


NEW ISSUE:  doing a DXcapture call Lookup NO LONGER SHOWS that call in DXkeeper Filter (I know these test calls are in the Log.) I
changed no settings.

It's like we lost a connection between Capture, Keeper, and DXview.

+ After you correct the first issue, let me know whether the second issue is still present.

        73,

                Dave, AA6YQ






DXKeeper Update Failure

Scott
 

I attempted to update my DXKeeper and the other programs that needed updated through the Launcher. I was given a warning to close DXKeeper before attempting to upgrade, so I closed it. When I attempted to upgrade I got a message file C:\DXLab\DXKeeper.exe does not exist. Sure enough it was not there. There was the DXKeeper1537 in the folder so I opened it successfully. It included my entire logbook, includingsome QSO's I made this evening in FT4 and FT8, so I immediately did a backup of my logbook. I have no idea where the DXKeeper.exe file went, so I copied the DXKeeper1537 and renamed the copy to DXKeeper.exe, however it still will not launch from the launcher, and I am not able to update to the new version. I'm not sure what to do next besides manually opening the DXKeeper1537 version. 

Any assistance would be appreciated.

73 Scott
KN3A


Re: Infected file for Commander 14.5.5 update?

Terry Glagowski / W1TR / AFA1DI
 

I’m using Kaspersky Total Security…

No problems with DXLAB stuff.

I DID have a problem with some MARS software doing TCP/IP in the range of port 5000 though.

I had to disable a particular DLL at the direction of Kaspersky Tech Support.

 

Terry G. Glagowski / W1TR
HAM: W1TR / USAF MARS: AFA1DI / GRID: FN31vw / ELEV: 950 MSL / 41.924750 N, 72.190320 W.

25 Hnath Road, Ashford, CT 06278 .
(860) 429-9444 (Home Landline) .
(EMail) W1TR@... .
(Web)  http://www.Glagowski.org/Radio .

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Jacob Derenne
Sent: Friday, April 10, 2020 16:17
To: DXLab@groups.io
Subject: Re: [DXLab] Infected file for Commander 14.5.5 update?

 

I use to use AVG, but always missed something, all my ham software is on separate drive and flagged for defender to accept and once a month I run rogue killer off a usb thumb drive, never a issue here with viruses or such on my system

 

W9BLI Jake

 

Sent from Mail for Windows 10

 

From: neil_zampella
Sent: Friday, April 10, 2020 12:33 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Infected file for Commander 14.5.5 update?

 

I've been using it for over 20 years ... AVG Internet Security.

Neil, KN3ILZ

On 4/10/2020 12:42 PM, w6de wrote:

Neil, what virus detection program do you use.  I like how you describe it works.

 

Dave, w6de

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of neil_zampella
Sent: 10 April, 2020 02:45
To: DXLab@groups.io
Subject: Re: [DXLab] Infected file for Commander 14.5.5 update?

 

There is no trojan or virus in any DXLab executable.    Just as there is no virus or trojan in other ham radio programs like JTAlert, WSJT-X, and many others that get 'triggered' due to some algorithm only known to Microsoft.     I have never had a problem with any DXLab program, nor with the others I mentioned.

Its not so strange that this has occurred to many ham radio programs since this last Windows update.   The really bad design of Defender is that it does not give you any indication of what its doing nor does it give you a chance to say NO.    Another display of how Microsoft wants to 'help' you.

I use a third-party anti-virus that allows me to make the decisions on what happens when it detects 'a virus'.    I can accept the quarantine, continue to install/run the program, or take the option to send it to their 'virus lab' which then returns a result within 15 to 20 minutes (often much earlier). Most often it is a false positive, and they update their definition file at the same time.

Neil, KN3ILZ

On 4/9/2020 8:10 PM, Jack Brabham - KZ5A wrote:

I don't think this is a false positive.  Defender is finding and identifying a specific Trojan. 

 

I'm not reloading Dx Lab unless there is some resolution beyond "ignore it and go on".

 

73 Jack KZ5A

 

 

On 4/9/2020 2:14 PM, Hasan Schiers N0AN wrote:

I should add to my instructions about how to remove a file from quarantine:

 

I'm no computer expert. I found that this procedure works for me. In the interests of avoiding any liability from someone who gets in a jam by not following the instructions precisely, or finds them inaccurate or unhelpful:

 

"While believed to be correct, this advice comes with no guarantees of any kind. You alone remain responsible for the security of information on your computer system".  

 

It's sad, when trying to help people that a statement like this has to be made, but....

 

What is the saying: YMMV? Use Windows 10 at your own risk? Take a file out of quarantine at your own risk?

 

By the time we are done with all this CMA stuff, we might as well turn all this ham radio equipment off and watch TV. 

 

Nevertheless, the advice to put in a disclaimer when trying to help anyone with any software is excellent advice!

 

73, N0AN

 

Hasan

 

 

On Thu, Apr 9, 2020 at 3:03 PM Hasan Schiers N0AN via groups.io <hbasri.schiers6=gmail.com@groups.io> wrote:

Mike:

 

========================================

Finding and Restoring a File from Windows Defender Quarantine:

0. Close all DXLab Programs
1. Bottom Left > Search Box for your Desktop
  (Magnifying Glass just to right of Windows Icon)
2. Type in "Virus & threat protection" (no quotes)
3. The Virus & threat protection app will appear in the search results. Click on it to run it.
4. At the Top 1/4 of the page there is a link: Protection History Click on it.
5. All Recent Items are shown
6. Select the Quarantined File that has been falsely quarantined
7. Chose to Restore it

8. Close the Window

 

Caveat: Once you have restored the file,  you may or may not have to move it to the proper directory. Not being in front of your computer I can't really tell. 

 

9. Restart all your chosen DXLab Programs

=============================================

73, N0AN

Hasan

 

 

On Wed, Apr 8, 2020 at 10:33 PM Michael Schulz <mschulz@...> wrote:

Hi,

 

I just tried to update Commander to the latest version but it was stopped by Windows Defender. Below

screenshot with more info:

 

Error! Filename not specified.

 

73 Mike K5TRI

 

--

What you learn, you must share. What you know, you must teach! - www.creative-chaos.com  -  @mschulz

 

PGP Signature: D300 B646 0D26 2E56 4176  B3C0 141D 9201 3ADF 22CF

 

 

 

Virus-free. www.avg.com

 


Re: DXkeeper "Look-Up" is slowed.....Error Logs attached

Dave AA6YQ
 

+ AA6YQ comments below

Results with "Safe Boot w/Networking"......doing call Lookup in DXcapture, or doing DXkeeper Filter:Lookup....very fast response.

Results with Normal Boot.....slow 4-5 second response ...doing the above Lookups.

+ That means an application automatically started by Windows when booted normally is interfering with communication among your
DXKeeper applications. The usual culprit is an anti-malware application, but other culprits have been reported:

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


NEW ISSUE: doing a DXcapture call Lookup NO LONGER SHOWS that call in DXkeeper Filter (I know these test calls are in the Log.) I
changed no settings.

It's like we lost a connection between Capture, Keeper, and DXview.

+ After you correct the first issue, let me know whether the second issue is still present.

73,

Dave, AA6YQ


Re: To everyone reporting that Commander has stopped working because their Anti-malware has reported it to be infected with a virus

Ed Sutter KC9JBU
 

Dave, wish I had read your comments earlier. Did not think of anti virus software. I took the long road after trying everything else I could think of not realizing that it was effecting others. I saved my log and macros and then did a complete uninstall of DxLab. I then reinstalled DxLab from scratch and it worked. After reading your comments I looked at my Win 10 Defender Anti Virus and found where it had stopped Commander. Could have fixed it right there and then. Will look at anti virus next time I have similar problem first. Thanks for you great support.

Ed 73
KC9JBU


Re: DXkeeper "Look-Up" is slowed.....Error Logs attached

Gary Smetana
 

Dave,

Results with "Safe Boot w/Networking"......doing call Lookup in DXcapture, or doing DXkeeper Filter:Lookup....very fast response.

Results with Normal Boot.....slow 4-5 second response ...doing the above Lookups.

NEW ISSUE:  doing a DXcapture call Lookup NO LONGER SHOWS that call in DXkeeper Filter (I know these test calls are in the Log.)
I changed no settings.

It's like we lost a connection between Capture, Keeper, and DXview.

What to examine ? Try ?

73,
Gary  W1EBM
 


From: DXLab@groups.io <DXLab@groups.io> on behalf of Dave AA6YQ <aa6yq@...>
Sent: Friday, April 10, 2020 6:02 PM
To: DXLab@groups.io <DXLab@groups.io>
Subject: Re: [DXLab] DXkeeper "Look-Up" is slowed.....Error Logs attached
 
+ AA6YQ comments below

I'll Reboot Windows into "Safe Mode with Networking", then start DXKeeper.....and report results.

BTW    With DXview not selected,  DXkeeper Lookups are instantaneous.   (Is that a clue, or that's how it's supposed to be?)

+ That's a clue that "something" on your system is slowing the performance of communication between applications.

        73,

                Dave, AA6YQ





Re: Max Origin DX

Dave AA6YQ
 

+ AA6YQ comments below

You may also need "Lookup missing location info" (and, optionally, "Capture location info from notes").

+ Correct.

+ If a Spot Database Entry's ODX field is empty, that means SpotCollector could not compute the distance to any of the spotting stations because it did not have their locations.

+ This prerequisite was not stated in

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

+ It is now.

73,

Dave, AA6YQ


Re: JTAlert - trying to get it working

D. Scott MacKenzie
 

Thank you Dave - I got it working after I hit the help files and fiddled on
my computer - the issue was picking the right audio source. It was also an
issue with the build. I upgraded to the newest, and problems now solved.

Thank you again

Scott

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Friday, April 10, 2020 7:51 PM
To: DXLab@groups.io
Subject: Re: [DXLab] JTAlert - trying to get it working

+ AA6YQ comments below

Hi all - not sure if this goes here or on the WSJT list. I am trying t get
JTAlert running to no avail. It loads fine, and I get the box where the
calls go, but I am unable to change any setting - I right/Left click and I
can find where to change the setting to interface with DXLabs, and to
capture the data. At least I got WSJT working and decoding properly.
Haven't tried to transmit yet.

+ There are configuration instructions here:

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

+ If they don't help, then I suggest that you seek help here:

<https://hamapps.groups.io/g/Support/messages>

73,

Dave, AA6YQ


Re: Max Origin DX

Scott Stembaugh
 

Yes. My operator location is set to NA-M 40 21' 15"N 86 47 30"W.


On Fri, Apr 10, 2020, 19:46 iain macdonnell - N6ML <ar@...> wrote:
Is your "Operator location" configured, on the General tab of Spot
Collector Configuration?

73,

    ~iain / N6ML


On Fri, Apr 10, 2020 at 4:32 PM Scott Stembaugh <radio.n9ljx@...> wrote:
>
> Sorry for the repeated reply - I need to add that all 6M spots do show an OMDX of 25, while ODX is blank.
> ------
> Scott Stembaugh - N9LJX
> radio.n9ljx@...
> http://sites.google.com/site/radion9ljx
>
>
> On Fri, Apr 10, 2020 at 7:29 PM Scott Stembaugh <radio.n9ljx@...> wrote:
>>
>> OK, I added ODX and OMDX to the view.  ODX is blank for all entries.  OMDX shows stations that are supposedly in the 25m radius.  A recent spot for TI2CDA indicates the only spotting station being XE2JS.  I am pretty certain that Chihuahua, MX is more than 25 miles from EN60.  Others are from K9MK in TX.  Both of these indicate (NA-M)
>>
>> My operator location is set to NA-M 40 21' 15"N 86 47 30"W.
>>
>> How does SC determine the OMDX?
>>
>> Thanks for the help.
>> --scott
>>
>> ------
>> Scott Stembaugh - N9LJX
>> radio.n9ljx@...
>> http://sites.google.com/site/radion9ljx
>>
>>
>> On Fri, Apr 10, 2020 at 7:06 PM Scott Stembaugh <radio.n9ljx@...> wrote:
>>>
>>> That is correct, I am NOT seeing any spotting stations listed that are within the 25 mile radius from my station.
>>>
>>> --scott
>>>
>>> On Fri, Apr 10, 2020, 18:30 g4wjs <bill.8@...> wrote:
>>>>
>>>> Hi Scott,
>>>>
>>>> you did not reply to Iain's implied question (my emphasis):
>>>>
>>>> "... still seeing spot database entries that do not include *any* spots from stations within your specified Max DX Origin ..."
>>>>
>>>> 73
>>>> Bill
>>>> G4WJS.
>>>>
>>>> On 10/04/2020 23:26, Scott Stembaugh wrote:
>>>>
>>>> correct, I do NOT have ignore checked. I have bands 80-6 enabled.
>>>>
>>>> On Fri, Apr 10, 2020, 18:23 iain macdonnell - N6ML <ar@...> wrote:
>>>>>
>>>>> Yeah, the "origin" in "Max DX origin" has no relation to the Origin filter.
>>>>>
>>>>> If you're still seeing spot database entries that do not include any
>>>>> spots from stations within your specified Max DX Origin, your Band
>>>>> filter is somehow broken.
>>>>>
>>>>> You have NOT checked the options in the "Ignore" panel of the Band
>>>>> Filter window, right?
>>>>>
>>>>> You could add a "ODX" column to your spot database display. Side-note
>>>>> to Dave; it'd be nice if the ODX could be displayed somewhere in the
>>>>> "Spots of CCC near FFF in MMM" window - maybe appended to the title?
>>>>>
>>>>> 73,
>>>>>
>>>>>     ~iain / N6ML
>>>>>
>>>>>
>>>>> On Fri, Apr 10, 2020 at 3:16 PM Scott Stembaugh <radio.n9ljx@...> wrote:
>>>>> >
>>>>> > By 'not being restricted' I am referring to the 'Source' (ie call of spotter) and not Origin (NA-M, NA-E, etc).
>>>>> > ------
>>>>> > Scott Stembaugh - N9LJX
>>>>> > radio.n9ljx@...
>>>>> > http://sites.google.com/site/radion9ljx
>>>>> >
>>>>> >
>>>>> > On Fri, Apr 10, 2020 at 5:53 PM Scott Stembaugh <radio.n9ljx@...> wrote:
>>>>> >>
>>>>> >> A whole bunch of 6m spots not being restricted by Max DX Origin.
>>>>> >> ------
>>>>> >> Scott Stembaugh - N9LJX
>>>>> >> radio.n9ljx@...
>>>>> >> http://sites.google.com/site/radion9ljx
>>>>> >>
>>>>> >>
>>>>> >> On Fri, Apr 10, 2020 at 5:41 PM iain macdonnell - N6ML <ar@...> wrote:
>>>>> >>>
>>>>> >>> On Fri, Apr 10, 2020 at 2:26 PM Scott Stembaugh <radio.n9ljx@...> wrote:
>>>>> >>> >
>>>>> >>> > I am attempting to set the Max Origin DX for 6M.
>>>>> >>> >
>>>>> >>> > The document says:
>>>>> >>> > If you type a distance into a band's Max origin DX textbox,  the band's Enable box will be disabled. After completing the entry or modification of this distance, check the band's Enable box; only Spot Database Entries on this band whose distance to the closest spotting station is equal to or less than the specified Max origin DX will be visible in the Spot Database Display. To temporarily disable "maximum distance to closest spotting station" filtering for all bands, check the Ignore panel's Max origin DX box.
>>>>> >>> >
>>>>> >>> > Actually if you attempt to enter a distance you get a popup saying to disable, enter, re-enable.
>>>>> >>> >
>>>>> >>> > When I have distance put in there (currently 25 for testing purposes)I still get spots from  stations beyond that distance.  I do have "Enable Start/End & Max Origin DX Filtering" checked.  I have verified that the spots are only from the station displayed (Display spots of xxx near 50313.0).
>>>>> >>> >
>>>>> >>> > I do have the displayed filtered for Band and Origin and Unconfirmed.  Does that override the Max Origin DX filter?
>>>>> >>>
>>>>> >>> It should be part of the Band Filter. If you type:
>>>>> >>>
>>>>> >>> Band='6m' and <BANDFILTER>
>>>>> >>>
>>>>> >>> In the Filter panel's text box, then Control-S, what do you see?
>>>>> >>>
>>>>> >>> 73,
>>>>> >>>
>>>>> >>>     ~iain / N6ML
>>>>
>>>>
>>>>
>>>> --
>>>> 73
>>>>
>>>> Bill
>>>>
>>>> G4WJS.
>
>




Re: JTAlert - trying to get it working

Dave AA6YQ
 

+ AA6YQ comments below

Hi all - not sure if this goes here or on the WSJT list. I am trying t get JTAlert running to no avail. It loads fine, and I get
the box where the calls go, but I am unable to change any setting - I right/Left click and I can find where to change the setting to
interface with DXLabs, and to capture the data. At least I got WSJT working and decoding properly. Haven't tried to transmit yet.

+ There are configuration instructions here:

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

+ If they don't help, then I suggest that you seek help here:

<https://hamapps.groups.io/g/Support/messages>

73,

Dave, AA6YQ


Re: Max Origin DX

iain macdonnell - N6ML
 

You may also need "Lookup missing location info" (and, optionally,
"Capture location info from notes"). Do the spot database entries in
question have grid squares?

73,

~iain / N6ML

On Fri, Apr 10, 2020 at 4:46 PM iain macdonnell - N6ML <@N6ML> wrote:

Is your "Operator location" configured, on the General tab of Spot
Collector Configuration?

73,

~iain / N6ML


On Fri, Apr 10, 2020 at 4:32 PM Scott Stembaugh <radio.n9ljx@...> wrote:

Sorry for the repeated reply - I need to add that all 6M spots do show an OMDX of 25, while ODX is blank.
------
Scott Stembaugh - N9LJX
radio.n9ljx@...
http://sites.google.com/site/radion9ljx


On Fri, Apr 10, 2020 at 7:29 PM Scott Stembaugh <radio.n9ljx@...> wrote:

OK, I added ODX and OMDX to the view. ODX is blank for all entries. OMDX shows stations that are supposedly in the 25m radius. A recent spot for TI2CDA indicates the only spotting station being XE2JS. I am pretty certain that Chihuahua, MX is more than 25 miles from EN60. Others are from K9MK in TX. Both of these indicate (NA-M)

My operator location is set to NA-M 40 21' 15"N 86 47 30"W.

How does SC determine the OMDX?

Thanks for the help.
--scott

------
Scott Stembaugh - N9LJX
radio.n9ljx@...
http://sites.google.com/site/radion9ljx


On Fri, Apr 10, 2020 at 7:06 PM Scott Stembaugh <radio.n9ljx@...> wrote:

That is correct, I am NOT seeing any spotting stations listed that are within the 25 mile radius from my station.

--scott

On Fri, Apr 10, 2020, 18:30 g4wjs <bill.8@...> wrote:

Hi Scott,

you did not reply to Iain's implied question (my emphasis):

"... still seeing spot database entries that do not include *any* spots from stations within your specified Max DX Origin ..."

73
Bill
G4WJS.

On 10/04/2020 23:26, Scott Stembaugh wrote:

correct, I do NOT have ignore checked. I have bands 80-6 enabled.

On Fri, Apr 10, 2020, 18:23 iain macdonnell - N6ML <@N6ML> wrote:

Yeah, the "origin" in "Max DX origin" has no relation to the Origin filter.

If you're still seeing spot database entries that do not include any
spots from stations within your specified Max DX Origin, your Band
filter is somehow broken.

You have NOT checked the options in the "Ignore" panel of the Band
Filter window, right?

You could add a "ODX" column to your spot database display. Side-note
to Dave; it'd be nice if the ODX could be displayed somewhere in the
"Spots of CCC near FFF in MMM" window - maybe appended to the title?

73,

~iain / N6ML


On Fri, Apr 10, 2020 at 3:16 PM Scott Stembaugh <radio.n9ljx@...> wrote:

By 'not being restricted' I am referring to the 'Source' (ie call of spotter) and not Origin (NA-M, NA-E, etc).
------
Scott Stembaugh - N9LJX
radio.n9ljx@...
http://sites.google.com/site/radion9ljx


On Fri, Apr 10, 2020 at 5:53 PM Scott Stembaugh <radio.n9ljx@...> wrote:

A whole bunch of 6m spots not being restricted by Max DX Origin.
------
Scott Stembaugh - N9LJX
radio.n9ljx@...
http://sites.google.com/site/radion9ljx


On Fri, Apr 10, 2020 at 5:41 PM iain macdonnell - N6ML <@N6ML> wrote:

On Fri, Apr 10, 2020 at 2:26 PM Scott Stembaugh <radio.n9ljx@...> wrote:

I am attempting to set the Max Origin DX for 6M.

The document says:
If you type a distance into a band's Max origin DX textbox, the band's Enable box will be disabled. After completing the entry or modification of this distance, check the band's Enable box; only Spot Database Entries on this band whose distance to the closest spotting station is equal to or less than the specified Max origin DX will be visible in the Spot Database Display. To temporarily disable "maximum distance to closest spotting station" filtering for all bands, check the Ignore panel's Max origin DX box.

Actually if you attempt to enter a distance you get a popup saying to disable, enter, re-enable.

When I have distance put in there (currently 25 for testing purposes)I still get spots from stations beyond that distance. I do have "Enable Start/End & Max Origin DX Filtering" checked. I have verified that the spots are only from the station displayed (Display spots of xxx near 50313.0).

I do have the displayed filtered for Band and Origin and Unconfirmed. Does that override the Max Origin DX filter?
It should be part of the Band Filter. If you type:

Band='6m' and <BANDFILTER>

In the Filter panel's text box, then Control-S, what do you see?

73,

~iain / N6ML


--
73

Bill

G4WJS.


Re: Max Origin DX

iain macdonnell - N6ML
 

Is your "Operator location" configured, on the General tab of Spot
Collector Configuration?

73,

~iain / N6ML

On Fri, Apr 10, 2020 at 4:32 PM Scott Stembaugh <radio.n9ljx@...> wrote:

Sorry for the repeated reply - I need to add that all 6M spots do show an OMDX of 25, while ODX is blank.
------
Scott Stembaugh - N9LJX
radio.n9ljx@...
http://sites.google.com/site/radion9ljx


On Fri, Apr 10, 2020 at 7:29 PM Scott Stembaugh <radio.n9ljx@...> wrote:

OK, I added ODX and OMDX to the view. ODX is blank for all entries. OMDX shows stations that are supposedly in the 25m radius. A recent spot for TI2CDA indicates the only spotting station being XE2JS. I am pretty certain that Chihuahua, MX is more than 25 miles from EN60. Others are from K9MK in TX. Both of these indicate (NA-M)

My operator location is set to NA-M 40 21' 15"N 86 47 30"W.

How does SC determine the OMDX?

Thanks for the help.
--scott

------
Scott Stembaugh - N9LJX
radio.n9ljx@...
http://sites.google.com/site/radion9ljx


On Fri, Apr 10, 2020 at 7:06 PM Scott Stembaugh <radio.n9ljx@...> wrote:

That is correct, I am NOT seeing any spotting stations listed that are within the 25 mile radius from my station.

--scott

On Fri, Apr 10, 2020, 18:30 g4wjs <bill.8@...> wrote:

Hi Scott,

you did not reply to Iain's implied question (my emphasis):

"... still seeing spot database entries that do not include *any* spots from stations within your specified Max DX Origin ..."

73
Bill
G4WJS.

On 10/04/2020 23:26, Scott Stembaugh wrote:

correct, I do NOT have ignore checked. I have bands 80-6 enabled.

On Fri, Apr 10, 2020, 18:23 iain macdonnell - N6ML <@N6ML> wrote:

Yeah, the "origin" in "Max DX origin" has no relation to the Origin filter.

If you're still seeing spot database entries that do not include any
spots from stations within your specified Max DX Origin, your Band
filter is somehow broken.

You have NOT checked the options in the "Ignore" panel of the Band
Filter window, right?

You could add a "ODX" column to your spot database display. Side-note
to Dave; it'd be nice if the ODX could be displayed somewhere in the
"Spots of CCC near FFF in MMM" window - maybe appended to the title?

73,

~iain / N6ML


On Fri, Apr 10, 2020 at 3:16 PM Scott Stembaugh <radio.n9ljx@...> wrote:

By 'not being restricted' I am referring to the 'Source' (ie call of spotter) and not Origin (NA-M, NA-E, etc).
------
Scott Stembaugh - N9LJX
radio.n9ljx@...
http://sites.google.com/site/radion9ljx


On Fri, Apr 10, 2020 at 5:53 PM Scott Stembaugh <radio.n9ljx@...> wrote:

A whole bunch of 6m spots not being restricted by Max DX Origin.
------
Scott Stembaugh - N9LJX
radio.n9ljx@...
http://sites.google.com/site/radion9ljx


On Fri, Apr 10, 2020 at 5:41 PM iain macdonnell - N6ML <@N6ML> wrote:

On Fri, Apr 10, 2020 at 2:26 PM Scott Stembaugh <radio.n9ljx@...> wrote:

I am attempting to set the Max Origin DX for 6M.

The document says:
If you type a distance into a band's Max origin DX textbox, the band's Enable box will be disabled. After completing the entry or modification of this distance, check the band's Enable box; only Spot Database Entries on this band whose distance to the closest spotting station is equal to or less than the specified Max origin DX will be visible in the Spot Database Display. To temporarily disable "maximum distance to closest spotting station" filtering for all bands, check the Ignore panel's Max origin DX box.

Actually if you attempt to enter a distance you get a popup saying to disable, enter, re-enable.

When I have distance put in there (currently 25 for testing purposes)I still get spots from stations beyond that distance. I do have "Enable Start/End & Max Origin DX Filtering" checked. I have verified that the spots are only from the station displayed (Display spots of xxx near 50313.0).

I do have the displayed filtered for Band and Origin and Unconfirmed. Does that override the Max Origin DX filter?
It should be part of the Band Filter. If you type:

Band='6m' and <BANDFILTER>

In the Filter panel's text box, then Control-S, what do you see?

73,

~iain / N6ML


--
73

Bill

G4WJS.


Re: Max Origin DX

Scott Stembaugh
 

Sorry for the repeated reply - I need to add that all 6M spots do show an OMDX of 25, while ODX is blank.


On Fri, Apr 10, 2020 at 7:29 PM Scott Stembaugh <radio.n9ljx@...> wrote:
OK, I added ODX and OMDX to the view.  ODX is blank for all entries.  OMDX shows stations that are supposedly in the 25m radius.  A recent spot for TI2CDA indicates the only spotting station being XE2JS.  I am pretty certain that Chihuahua, MX is more than 25 miles from EN60.  Others are from K9MK in TX.  Both of these indicate (NA-M)

My operator location is set to NA-M 40 21' 15"N 86 47 30"W.

How does SC determine the OMDX?

Thanks for the help.
--scott



On Fri, Apr 10, 2020 at 7:06 PM Scott Stembaugh <radio.n9ljx@...> wrote:
That is correct, I am NOT seeing any spotting stations listed that are within the 25 mile radius from my station. 

--scott

On Fri, Apr 10, 2020, 18:30 g4wjs <bill.8@...> wrote:
Hi Scott,

you did not reply to Iain's implied question (my emphasis):

"... still seeing spot database entries that do not include *any* spots from stations within your specified Max DX Origin ..."

73
Bill
G4WJS.

On 10/04/2020 23:26, Scott Stembaugh wrote:
correct, I do NOT have ignore checked. I have bands 80-6 enabled. 

On Fri, Apr 10, 2020, 18:23 iain macdonnell - N6ML <ar@...> wrote:
Yeah, the "origin" in "Max DX origin" has no relation to the Origin filter.

If you're still seeing spot database entries that do not include any
spots from stations within your specified Max DX Origin, your Band
filter is somehow broken.

You have NOT checked the options in the "Ignore" panel of the Band
Filter window, right?

You could add a "ODX" column to your spot database display. Side-note
to Dave; it'd be nice if the ODX could be displayed somewhere in the
"Spots of CCC near FFF in MMM" window - maybe appended to the title?

73,

    ~iain / N6ML


On Fri, Apr 10, 2020 at 3:16 PM Scott Stembaugh <radio.n9ljx@...> wrote:
>
> By 'not being restricted' I am referring to the 'Source' (ie call of spotter) and not Origin (NA-M, NA-E, etc).
> ------
> Scott Stembaugh - N9LJX
> radio.n9ljx@...
> http://sites.google.com/site/radion9ljx
>
>
> On Fri, Apr 10, 2020 at 5:53 PM Scott Stembaugh <radio.n9ljx@...> wrote:
>>
>> A whole bunch of 6m spots not being restricted by Max DX Origin.
>> ------
>> Scott Stembaugh - N9LJX
>> radio.n9ljx@...
>> http://sites.google.com/site/radion9ljx
>>
>>
>> On Fri, Apr 10, 2020 at 5:41 PM iain macdonnell - N6ML <ar@...> wrote:
>>>
>>> On Fri, Apr 10, 2020 at 2:26 PM Scott Stembaugh <radio.n9ljx@...> wrote:
>>> >
>>> > I am attempting to set the Max Origin DX for 6M.
>>> >
>>> > The document says:
>>> > If you type a distance into a band's Max origin DX textbox,  the band's Enable box will be disabled. After completing the entry or modification of this distance, check the band's Enable box; only Spot Database Entries on this band whose distance to the closest spotting station is equal to or less than the specified Max origin DX will be visible in the Spot Database Display. To temporarily disable "maximum distance to closest spotting station" filtering for all bands, check the Ignore panel's Max origin DX box.
>>> >
>>> > Actually if you attempt to enter a distance you get a popup saying to disable, enter, re-enable.
>>> >
>>> > When I have distance put in there (currently 25 for testing purposes)I still get spots from  stations beyond that distance.  I do have "Enable Start/End & Max Origin DX Filtering" checked.  I have verified that the spots are only from the station displayed (Display spots of xxx near 50313.0).
>>> >
>>> > I do have the displayed filtered for Band and Origin and Unconfirmed.  Does that override the Max Origin DX filter?
>>>
>>> It should be part of the Band Filter. If you type:
>>>
>>> Band='6m' and <BANDFILTER>
>>>
>>> In the Filter panel's text box, then Control-S, what do you see?
>>>
>>> 73,
>>>
>>>     ~iain / N6ML



--
73

Bill

G4WJS.


Re: Max Origin DX

Scott Stembaugh
 

OK, I added ODX and OMDX to the view.  ODX is blank for all entries.  OMDX shows stations that are supposedly in the 25m radius.  A recent spot for TI2CDA indicates the only spotting station being XE2JS.  I am pretty certain that Chihuahua, MX is more than 25 miles from EN60.  Others are from K9MK in TX.  Both of these indicate (NA-M)

My operator location is set to NA-M 40 21' 15"N 86 47 30"W.

How does SC determine the OMDX?

Thanks for the help.
--scott



On Fri, Apr 10, 2020 at 7:06 PM Scott Stembaugh <radio.n9ljx@...> wrote:
That is correct, I am NOT seeing any spotting stations listed that are within the 25 mile radius from my station. 

--scott

On Fri, Apr 10, 2020, 18:30 g4wjs <bill.8@...> wrote:
Hi Scott,

you did not reply to Iain's implied question (my emphasis):

"... still seeing spot database entries that do not include *any* spots from stations within your specified Max DX Origin ..."

73
Bill
G4WJS.

On 10/04/2020 23:26, Scott Stembaugh wrote:
correct, I do NOT have ignore checked. I have bands 80-6 enabled. 

On Fri, Apr 10, 2020, 18:23 iain macdonnell - N6ML <ar@...> wrote:
Yeah, the "origin" in "Max DX origin" has no relation to the Origin filter.

If you're still seeing spot database entries that do not include any
spots from stations within your specified Max DX Origin, your Band
filter is somehow broken.

You have NOT checked the options in the "Ignore" panel of the Band
Filter window, right?

You could add a "ODX" column to your spot database display. Side-note
to Dave; it'd be nice if the ODX could be displayed somewhere in the
"Spots of CCC near FFF in MMM" window - maybe appended to the title?

73,

    ~iain / N6ML


On Fri, Apr 10, 2020 at 3:16 PM Scott Stembaugh <radio.n9ljx@...> wrote:
>
> By 'not being restricted' I am referring to the 'Source' (ie call of spotter) and not Origin (NA-M, NA-E, etc).
> ------
> Scott Stembaugh - N9LJX
> radio.n9ljx@...
> http://sites.google.com/site/radion9ljx
>
>
> On Fri, Apr 10, 2020 at 5:53 PM Scott Stembaugh <radio.n9ljx@...> wrote:
>>
>> A whole bunch of 6m spots not being restricted by Max DX Origin.
>> ------
>> Scott Stembaugh - N9LJX
>> radio.n9ljx@...
>> http://sites.google.com/site/radion9ljx
>>
>>
>> On Fri, Apr 10, 2020 at 5:41 PM iain macdonnell - N6ML <ar@...> wrote:
>>>
>>> On Fri, Apr 10, 2020 at 2:26 PM Scott Stembaugh <radio.n9ljx@...> wrote:
>>> >
>>> > I am attempting to set the Max Origin DX for 6M.
>>> >
>>> > The document says:
>>> > If you type a distance into a band's Max origin DX textbox,  the band's Enable box will be disabled. After completing the entry or modification of this distance, check the band's Enable box; only Spot Database Entries on this band whose distance to the closest spotting station is equal to or less than the specified Max origin DX will be visible in the Spot Database Display. To temporarily disable "maximum distance to closest spotting station" filtering for all bands, check the Ignore panel's Max origin DX box.
>>> >
>>> > Actually if you attempt to enter a distance you get a popup saying to disable, enter, re-enable.
>>> >
>>> > When I have distance put in there (currently 25 for testing purposes)I still get spots from  stations beyond that distance.  I do have "Enable Start/End & Max Origin DX Filtering" checked.  I have verified that the spots are only from the station displayed (Display spots of xxx near 50313.0).
>>> >
>>> > I do have the displayed filtered for Band and Origin and Unconfirmed.  Does that override the Max Origin DX filter?
>>>
>>> It should be part of the Band Filter. If you type:
>>>
>>> Band='6m' and <BANDFILTER>
>>>
>>> In the Filter panel's text box, then Control-S, what do you see?
>>>
>>> 73,
>>>
>>>     ~iain / N6ML



--
73

Bill

G4WJS.


Re: Max Origin DX

Scott Stembaugh
 

That is correct, I am NOT seeing any spotting stations listed that are within the 25 mile radius from my station. 

--scott

On Fri, Apr 10, 2020, 18:30 g4wjs <bill.8@...> wrote:
Hi Scott,

you did not reply to Iain's implied question (my emphasis):

"... still seeing spot database entries that do not include *any* spots from stations within your specified Max DX Origin ..."

73
Bill
G4WJS.

On 10/04/2020 23:26, Scott Stembaugh wrote:
correct, I do NOT have ignore checked. I have bands 80-6 enabled. 

On Fri, Apr 10, 2020, 18:23 iain macdonnell - N6ML <ar@...> wrote:
Yeah, the "origin" in "Max DX origin" has no relation to the Origin filter.

If you're still seeing spot database entries that do not include any
spots from stations within your specified Max DX Origin, your Band
filter is somehow broken.

You have NOT checked the options in the "Ignore" panel of the Band
Filter window, right?

You could add a "ODX" column to your spot database display. Side-note
to Dave; it'd be nice if the ODX could be displayed somewhere in the
"Spots of CCC near FFF in MMM" window - maybe appended to the title?

73,

    ~iain / N6ML


On Fri, Apr 10, 2020 at 3:16 PM Scott Stembaugh <radio.n9ljx@...> wrote:
>
> By 'not being restricted' I am referring to the 'Source' (ie call of spotter) and not Origin (NA-M, NA-E, etc).
> ------
> Scott Stembaugh - N9LJX
> radio.n9ljx@...
> http://sites.google.com/site/radion9ljx
>
>
> On Fri, Apr 10, 2020 at 5:53 PM Scott Stembaugh <radio.n9ljx@...> wrote:
>>
>> A whole bunch of 6m spots not being restricted by Max DX Origin.
>> ------
>> Scott Stembaugh - N9LJX
>> radio.n9ljx@...
>> http://sites.google.com/site/radion9ljx
>>
>>
>> On Fri, Apr 10, 2020 at 5:41 PM iain macdonnell - N6ML <ar@...> wrote:
>>>
>>> On Fri, Apr 10, 2020 at 2:26 PM Scott Stembaugh <radio.n9ljx@...> wrote:
>>> >
>>> > I am attempting to set the Max Origin DX for 6M.
>>> >
>>> > The document says:
>>> > If you type a distance into a band's Max origin DX textbox,  the band's Enable box will be disabled. After completing the entry or modification of this distance, check the band's Enable box; only Spot Database Entries on this band whose distance to the closest spotting station is equal to or less than the specified Max origin DX will be visible in the Spot Database Display. To temporarily disable "maximum distance to closest spotting station" filtering for all bands, check the Ignore panel's Max origin DX box.
>>> >
>>> > Actually if you attempt to enter a distance you get a popup saying to disable, enter, re-enable.
>>> >
>>> > When I have distance put in there (currently 25 for testing purposes)I still get spots from  stations beyond that distance.  I do have "Enable Start/End & Max Origin DX Filtering" checked.  I have verified that the spots are only from the station displayed (Display spots of xxx near 50313.0).
>>> >
>>> > I do have the displayed filtered for Band and Origin and Unconfirmed.  Does that override the Max Origin DX filter?
>>>
>>> It should be part of the Band Filter. If you type:
>>>
>>> Band='6m' and <BANDFILTER>
>>>
>>> In the Filter panel's text box, then Control-S, what do you see?
>>>
>>> 73,
>>>
>>>     ~iain / N6ML



--
73

Bill

G4WJS.