开云体育

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. DXLab
  2. Messages
Expanded Topics Messages Polls
Date
Re: Can't log FR1GV

Danny Douglas
 

The sweater I have on right now says: " Yeah, Im old, but at least I got here".?? I have that same problem, of not remembering exactly how to phrase the question I am trying to ask.? But, thats not because I am old.? I started that really early, and it was really dumb of me
to major in Math and minor in Physics - when I cant remember ...... what do they call those things?? Ah, yeah, formulas.

From: "'Bob Main' bobmain1@... [dxlab]"
To: dxlab@...
Sent: Friday, March 4, 2016 11:12:08 AM
Subject: RE: [dxlab] Can't log FR1GV

?

OK, I am not fussing at Joe or anybody, he has fussed at me a few times, even when somebody suggested that I ask him directly. I read his post and thought “Go get ‘em Joe.” I also agree with Rich, if the instructions say to recompute, then we should abide by that, especially if you want things to work correctly later in life. Tends to bite you in the ….. if you don’t, always.

Bill, I also envy Joe and others and how they can tell you where to find stuff. I have discovered over the years that when a search routine is written for manuals that you need to learn the terminology they were thinking when they wrote it. Because if you don’t know that you may never find what you are looking for. Rich has given me a couple links that I have bookmarked and I use them quite often, but sometimes I can’t figure out the terminology to ask when I am searching and have to come here to ask, or to Dave.

I have also discovered that despite what some younger folks think getting older is good, in fact VERY good. Because the fix to that is real permanent. Good to see you over here on the reflector too, after DXBase.

73, Bob KB4CL

From: dxlab@... [mailto:dxlab@...]
Sent: Friday, March 04, 2016 10:35 AM
To: dxlab@...
Subject: Re: [dxlab] Can't log FR1GV

Bob, the older I get, the harder it is to remember all the myriad of
options in DXLabs.
I envy Joe and the others who help out. I have no idea how they can
remember all of the various DXL settings.

So what I do... when I read a post asking how to fix, or modify, or can
I (insert ? asked), I do a quick check of the settings I have enabled in
that DXLabs module.
Most of the time I find that it's is set properly, but occasionally I
find that I hadn't understood what that option would do correctly and
make the appropriate change. This also offers me the opportunity to
relearn some of the features available but use less frequently than others.

My thanks to both the questioners and those providing the answers. I
learn; (but mostly relearn) some feature I had forgotten.

On 3/4/2016 09:07, 'Bob Main' bobmain1@... [dxlab] wrote:
> I think the problem is, for many of us, is we see someone is having a problem. Since we aren’t having it at the time it goes over our heads and we pay little attention to it. Later when we do have the problem it is “OK I vaguely remember somebody had that problem recently, but what did they do to solve it?” Now instead of going back and searching the hundreds (or thousands) of messages it is simply easier, what did they do again? Just my take on this.
>
>
>
> 73, Bob KB4CL
>
>
>
> From: dxlab@... [mailto:dxlab@...]
> Sent: Friday, March 04, 2016 9:30 AM
> To: dxlab@...
> Subject: Re: [dxlab] Can't log FR1GV
>
>
>
>
>
>
> Please review the dozen or more times this question has been asked
> in the last few weeks.
>
> You apparently failed to follow the instructions when you last updated
> the DXCC database which called for performing a "recompute" to update
> the log in DXKeeper in order to reflect the updated DXCC Prefixes.
>
> In DXKeeper, select the "Check Progress" tab then click "Recompute"
> in the center of the bottom row. Once that has been completed, you
> may also want to perform a recompute in SpotCollector to update any
> "old" spots in the Spots database. In SpotCollector, select Config ->
> Spot Database and click the Recompute button in the middle of the
> right column.
>
> 73,
>
> ... Joe, W4TV
>
> On 3/4/2016 8:35 AM, Daniel Brown daniel.h.brown@... [dxlab] wrote:
>> Greetings -
>>
>> I worked FR1GV the other day on JT65 (yay) but am having trouble
>> getting it logged with DXKeeper. I keep getting a message that says it
>> cannot be logged because the QSO contains invalid items. The "DXCC"
>> field is flashing red when "FR" is selected. FR was automatically
>> filled by DXKeeper, upon entering the call sign. I changed it to FR-G
>> (which obviously isn't correct) and of course got an error back from
>> LOTW when the contact was confirmed.
>>
>> Any thoughts here?
>>
>> 73, N8YSZ.
>>
>
>
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
> Posted by: "Bob Main"
> ------------------------------------
>
>
> ------------------------------------
>
> Yahoo Groups Links
>
>
>

--
In beautiful downtown Harwood Hts. IL
Re: Can't log FR1GV

 

OK, I am not fussing at Joe or anybody, he has fussed at me a few times, even when somebody suggested that I ask him directly. I read his post and thought “Go get ‘em Joe.” I also agree with Rich, if the instructions say to recompute, then we should abide by that, especially if you want things to work correctly later in life. Tends to bite you in the ….. if you don’t, always.



Bill, I also envy Joe and others and how they can tell you where to find stuff. I have discovered over the years that when a search routine is written for manuals that you need to learn the terminology they were thinking when they wrote it. Because if you don’t know that you may never find what you are looking for. Rich has given me a couple links that I have bookmarked and I use them quite often, but sometimes I can’t figure out the terminology to ask when I am searching and have to come here to ask, or to Dave.



I have also discovered that despite what some younger folks think getting older is good, in fact VERY good. Because the fix to that is real permanent. Good to see you over here on the reflector too, after DXBase.



73, Bob KB4CL



From: dxlab@... [mailto:dxlab@...]
Sent: Friday, March 04, 2016 10:35 AM
To: dxlab@...
Subject: Re: [dxlab] Can't log FR1GV





Bob, the older I get, the harder it is to remember all the myriad of
options in DXLabs.
I envy Joe and the others who help out. I have no idea how they can
remember all of the various DXL settings.

So what I do... when I read a post asking how to fix, or modify, or can
I (insert ? asked), I do a quick check of the settings I have enabled in
that DXLabs module.
Most of the time I find that it's is set properly, but occasionally I
find that I hadn't understood what that option would do correctly and
make the appropriate change. This also offers me the opportunity to
relearn some of the features available but use less frequently than others.

My thanks to both the questioners and those providing the answers. I
learn; (but mostly relearn) some feature I had forgotten.

On 3/4/2016 09:07, 'Bob Main' bobmain1@... [dxlab] wrote:
I think the problem is, for many of us, is we see someone is having a problem. Since we aren’t having it at the time it goes over our heads and we pay little attention to it. Later when we do have the problem it is “OK I vaguely remember somebody had that problem recently, but what did they do to solve it?” Now instead of going back and searching the hundreds (or thousands) of messages it is simply easier, what did they do again? Just my take on this.



73, Bob KB4CL



From: dxlab@... [mailto:dxlab@...]
Sent: Friday, March 04, 2016 9:30 AM
To: dxlab@...
Subject: Re: [dxlab] Can't log FR1GV






Please review the dozen or more times this question has been asked
in the last few weeks.

You apparently failed to follow the instructions when you last updated
the DXCC database which called for performing a "recompute" to update
the log in DXKeeper in order to reflect the updated DXCC Prefixes.

In DXKeeper, select the "Check Progress" tab then click "Recompute"
in the center of the bottom row. Once that has been completed, you
may also want to perform a recompute in SpotCollector to update any
"old" spots in the Spots database. In SpotCollector, select Config ->
Spot Database and click the Recompute button in the middle of the
right column.

73,

... Joe, W4TV

On 3/4/2016 8:35 AM, Daniel Brown daniel.h.brown@... [dxlab] wrote:
Greetings -

I worked FR1GV the other day on JT65 (yay) but am having trouble
getting it logged with DXKeeper. I keep getting a message that says it
cannot be logged because the QSO contains invalid items. The "DXCC"
field is flashing red when "FR" is selected. FR was automatically
filled by DXKeeper, upon entering the call sign. I changed it to FR-G
(which obviously isn't correct) and of course got an error back from
LOTW when the contact was confirmed.

Any thoughts here?

73, N8YSZ.



[Non-text portions of this message have been removed]



------------------------------------
Posted by: "Bob Main" <bobmain1@...>
------------------------------------


------------------------------------

Yahoo Groups Links


--
In beautiful downtown Harwood Hts. IL





[Non-text portions of this message have been removed]
Re: Can't log FR1GV

 


Joe -

Thanks for the response. It does appear to have fixed the issue.

That said, I'm not sure how I could have guessed that would be the solution for a brand new contact - when DXKeeper has seemed to be working fine. I haven't been actively monitoring the group, recently and didn't get anything when I searched for a few terms around "Reunion" "FR" and Dxkeeper. Guess I should have dug a bit deeper before assuming I'd get a friendly and helpful answer back from fellow hams. Perhaps for future such things, having DXkeeper do something like open up a window and ask "Recompute the database now?" if it is needed after an upgrade might safe a few of us poor lids from having to re-ask FAQ's.?


73 - Best regards.?

N8YSZ.?


On Fri, Mar 4, 2016 at 9:30 AM, 'Joe Subich, W4TV' lists@... [dxlab] <dxlab@...> wrote:
?


Please review the dozen or more times this question has been asked
in the last few weeks.

You apparently failed to follow the instructions when you last updated
the DXCC database which called for performing a "recompute" to update
the log in DXKeeper in order to reflect the updated DXCC Prefixes.

In DXKeeper, select the "Check Progress" tab then click "Recompute"
in the center of the bottom row. Once that has been completed, you
may also want to perform a recompute in SpotCollector to update any
"old" spots in the Spots database. In SpotCollector, select Config ->
Spot Database and click the Recompute button in the middle of the
right column.

73,

... Joe, W4TV

On 3/4/2016 8:35 AM, Daniel Brown daniel.h.brown@... [dxlab] wrote:
> Greetings -
>
> I worked FR1GV the other day on JT65 (yay) but am having trouble
> getting it logged with DXKeeper. I keep getting a message that says it
> cannot be logged because the QSO contains invalid items. The "DXCC"
> field is flashing red when "FR" is selected. FR was automatically
> filled by DXKeeper, upon entering the call sign. I changed it to FR-G
> (which obviously isn't correct) and of course got an error back from
> LOTW when the contact was confirmed.
>
> Any thoughts here?
>
> 73, N8YSZ.
>




--
Dan Brown
brown@...
Re: Can't log FR1GV

 

I know and understand that. In fact I will admit that since I know that is sometimes a requirement when an update comes out that affects the databases the first thing I tend to do is look for the work “recompute”. If I see that then I look more closely to see what and where. Maybe as a user and not a member of the support crew I might be a bit different because I look for just that first.



73, Bob KB4CL



From: dxlab@... [mailto:dxlab@...]
Sent: Friday, March 04, 2016 10:45 AM
To: dxlab@...
Subject: Re: [dxlab] Can't log FR1GV





Bob,
The problem is not that people didn't read or remember the solutions to posts on this reflector. The problem is that they didn't read and follow the instructions that were delivered with the database release. If they did, they would never have had the problem in the first place. Some, not all, releases of the DXCC database require one to do a recompute in both DXKeeper and SpotCollector to update the existing databases. That is clearly spelled out in the update instructions. Dave does not do it automatically because it can be time consuming so why waste the time it takes to do it when it is not necessary?

73, Rich - W3ZJ


On 3/4/2016 10:07 AM, 'Bob Main' bobmain1@... [dxlab] wrote:

I think the problem is, for many of us, is we see someone is having a problem. Since we aren’t having it at the time it goes over our heads and we pay little attention to it. Later when we do have the problem it is “OK I vaguely remember somebody had that problem recently, but what did they do to solve it?” Now instead of going back and searching the hundreds (or thousands) of messages it is simply easier, what did they do again? Just my take on this.



73, Bob KB4CL







[Non-text portions of this message have been removed]
Re: Can't log FR1GV

 

开云体育

Bob,
The problem is not that people didn't read or remember the solutions to posts on this reflector. The problem is that they didn't read and follow the instructions that were delivered with the database release. If they did, they would never have had the problem in the first place. Some, not all, releases of the DXCC database require one to do a recompute in both DXKeeper and SpotCollector to update the existing databases. That is clearly spelled out in the update instructions. Dave does not do it automatically because it can be time consuming so why waste the time it takes to do it when it is not necessary?

73, Rich - W3ZJ


On 3/4/2016 10:07 AM, 'Bob Main' bobmain1@... [dxlab] wrote:

I think the problem is, for many of us, is we see someone is having a problem.  Since we aren’t having it at the time it goes over our heads and we pay little attention to it.  Later when we do have the problem it is “OK I vaguely remember somebody had that problem recently, but what did they do to solve it?”  Now instead of going back and searching the hundreds (or thousands) of messages it is simply easier, what did they do again?  Just my take on this.



73, Bob KB4CL
Re: Can't log FR1GV

FireBrick
 

Bob, the older I get, the harder it is to remember all the myriad of options in DXLabs.
I envy Joe and the others who help out. I have no idea how they can remember all of the various DXL settings.

So what I do... when I read a post asking how to fix, or modify, or can I (insert ? asked), I do a quick check of the settings I have enabled in that DXLabs module.
Most of the time I find that it's is set properly, but occasionally I find that I hadn't understood what that option would do correctly and make the appropriate change. This also offers me the opportunity to relearn some of the features available but use less frequently than others.

My thanks to both the questioners and those providing the answers. I learn; (but mostly relearn) some feature I had forgotten.

On 3/4/2016 09:07, 'Bob Main' bobmain1@... [dxlab] wrote:
I think the problem is, for many of us, is we see someone is having a problem. Since we aren’t having it at the time it goes over our heads and we pay little attention to it. Later when we do have the problem it is “OK I vaguely remember somebody had that problem recently, but what did they do to solve it?” Now instead of going back and searching the hundreds (or thousands) of messages it is simply easier, what did they do again? Just my take on this.


73, Bob KB4CL


From: dxlab@... [mailto:dxlab@...]
Sent: Friday, March 04, 2016 9:30 AM
To: dxlab@...
Subject: Re: [dxlab] Can't log FR1GV




Please review the dozen or more times this question has been asked
in the last few weeks.

You apparently failed to follow the instructions when you last updated
the DXCC database which called for performing a "recompute" to update
the log in DXKeeper in order to reflect the updated DXCC Prefixes.

In DXKeeper, select the "Check Progress" tab then click "Recompute"
in the center of the bottom row. Once that has been completed, you
may also want to perform a recompute in SpotCollector to update any
"old" spots in the Spots database. In SpotCollector, select Config ->
Spot Database and click the Recompute button in the middle of the
right column.

73,

... Joe, W4TV

On 3/4/2016 8:35 AM, Daniel Brown daniel.h.brown@... [dxlab] wrote:
Greetings -

I worked FR1GV the other day on JT65 (yay) but am having trouble
getting it logged with DXKeeper. I keep getting a message that says it
cannot be logged because the QSO contains invalid items. The "DXCC"
field is flashing red when "FR" is selected. FR was automatically
filled by DXKeeper, upon entering the call sign. I changed it to FR-G
(which obviously isn't correct) and of course got an error back from
LOTW when the contact was confirmed.

Any thoughts here?

73, N8YSZ.






------------------------------------
Posted by: "Bob Main" <bobmain1@...>
------------------------------------


------------------------------------

Yahoo Groups Links


--
In beautiful downtown Harwood Hts. IL
Re: Can't log FR1GV

 

I think the problem is, for many of us, is we see someone is having a problem. Since we aren’t having it at the time it goes over our heads and we pay little attention to it. Later when we do have the problem it is “OK I vaguely remember somebody had that problem recently, but what did they do to solve it?” Now instead of going back and searching the hundreds (or thousands) of messages it is simply easier, what did they do again? Just my take on this.



73, Bob KB4CL



From: dxlab@... [mailto:dxlab@...]
Sent: Friday, March 04, 2016 9:30 AM
To: dxlab@...
Subject: Re: [dxlab] Can't log FR1GV






Please review the dozen or more times this question has been asked
in the last few weeks.

You apparently failed to follow the instructions when you last updated
the DXCC database which called for performing a "recompute" to update
the log in DXKeeper in order to reflect the updated DXCC Prefixes.

In DXKeeper, select the "Check Progress" tab then click "Recompute"
in the center of the bottom row. Once that has been completed, you
may also want to perform a recompute in SpotCollector to update any
"old" spots in the Spots database. In SpotCollector, select Config ->
Spot Database and click the Recompute button in the middle of the
right column.

73,

... Joe, W4TV

On 3/4/2016 8:35 AM, Daniel Brown daniel.h.brown@... [dxlab] wrote:
Greetings -

I worked FR1GV the other day on JT65 (yay) but am having trouble
getting it logged with DXKeeper. I keep getting a message that says it
cannot be logged because the QSO contains invalid items. The "DXCC"
field is flashing red when "FR" is selected. FR was automatically
filled by DXKeeper, upon entering the call sign. I changed it to FR-G
(which obviously isn't correct) and of course got an error back from
LOTW when the contact was confirmed.

Any thoughts here?

73, N8YSZ.




[Non-text portions of this message have been removed]
Re: Can't log FR1GV

 

Please review the dozen or more times this question has been asked
in the last few weeks.

You apparently failed to follow the instructions when you last updated
the DXCC database which called for performing a "recompute" to update
the log in DXKeeper in order to reflect the updated DXCC Prefixes.

In DXKeeper, select the "Check Progress" tab then click "Recompute"
in the center of the bottom row. Once that has been completed, you
may also want to perform a recompute in SpotCollector to update any
"old" spots in the Spots database. In SpotCollector, select Config ->
Spot Database and click the Recompute button in the middle of the
right column.

73,

... Joe, W4TV

On 3/4/2016 8:35 AM, Daniel Brown daniel.h.brown@... [dxlab] wrote:
Greetings -

I worked FR1GV the other day on JT65 (yay) but am having trouble
getting it logged with DXKeeper. I keep getting a message that says it
cannot be logged because the QSO contains invalid items. The "DXCC"
field is flashing red when "FR" is selected. FR was automatically
filled by DXKeeper, upon entering the call sign. I changed it to FR-G
(which obviously isn't correct) and of course got an error back from
LOTW when the contact was confirmed.

Any thoughts here?

73, N8YSZ.
Can't log FR1GV

 

Greetings -

I worked FR1GV the other day on JT65 (yay) but am having trouble
getting it logged with DXKeeper. I keep getting a message that says it
cannot be logged because the QSO contains invalid items. The "DXCC"
field is flashing red when "FR" is selected. FR was automatically
filled by DXKeeper, upon entering the call sign. I changed it to FR-G
(which obviously isn't correct) and of course got an error back from
LOTW when the contact was confirmed.

Any thoughts here?

73, N8YSZ.

--
Dan Brown
brown@...
Thanks Dave

[email protected]
 

开云体育

Hi Dave,
?
Thanks for fulfilling my "senior moment".? I do not remember removing WinWarbler?from the Digital Mode Application in SC?General Config. But it was blank.? I retyped it in.??DXLab?Suite is working flawless.
?
Again, thanks.
?
73? de Rick W4UEF
?
PS:?I shud have said left click instead of right click.?
?

>>>AA6YQ comments below


I have been using Dxlab Suite for a long time. For about a week, I have been researching for an answer to a (maybe of not) slight
problem. But did not find and answer.

When right click on a call line in Spotcollector, that call populates (goes to) call field of DxKeeper, DxView, Pathfinder and
Commander's Bandspread. Also there is an indication on that band in PropView Prediction.

I thought that right clicking on a call line in Spotcollector also send that call to Winwarbler. If so then it is no longer doing
it.

Is this a "senior moment" or I may have clicked a wrong buttons in any DxLab Config?

Question: When right clicking on a call in Spotcollector, is that call sent to WW?

>>>Right-clicking an Entry in the Spot Database Display causes a menu of several commands to appear. If you then select the "Lookup"
command, SpotCollector will direct DXView and Pathfinder to perform "lookup" operations for the entry's callsign.

>>>Double-clicking a Spot Database Display Entry will convey that Entry's callsign to the other DXLab applications, including
WinWarbler. Note that if you double-click the Entry for a station operating in SSB or CW, the Entry's callsign will only be conveyed
to WinWarbler if SpotCollector is configured appropriately, as described in



73,

Dave, AA6YQ
Re: Commander CW Speed

 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Friday, March 04, 2016 2:26 AM
To: dxlab@...
Subject: [dxlab] Commander CW Speed

Commander cw speed is not functioning. CW box is checked but shows the cw speed as 20wpm and is non responsive.

Are you referring to a user-defined slider that you configured to control your TS-480's CW speed? Did this slider previously work correctly?
What do you mean by "is non responsive" ?
73,

Dave, AA6YQ
Commander CW Speed

[email protected]
 

Commander cw speed is not functioning. CW box is checked but shows the cw
speed as 20wpm and is non responsive. Could not find anything in he Config pertaining to this.
Running Kenwood TS-480sat.


john/n4dsp
DXView 4.2.0 is available

 

This release

- responds correctly if PropView stops running

- with the "Generate propagation forecast" option enabled and Commander and PropView running, responds to a mouse click of the words
Short or Long in the Main window's Heading panel by directing PropView to generate a short-path or long-path forecast from the
currently-selected location using the transceiver's current band (tnx to Paul N1BUG)

- in the Rotator Control tab's Model panel, replaces "Idiom Press" with Rotor-EZ (tnx to Barry VE6TN)

- updates the Configuration.htm and Operation.htm documentation files


Notes:

1. Update your firewall and anti-malware applications to consider this new version of DXView to be "safe"

2. If this upgrade doesn't work correctly, see the "After an Upgrade" section of
<>

3. After upgrading, to revert to the previous version of DXView, see <>


DXView 4.2.0 is available via the DXLab Launcher or via

<>


73,

Dave, AA6YQ
Re: DXKeeper pathing to network

 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Thursday, March 03, 2016 5:54 PM
To: dxlab@...
Subject: RE: [dxlab] DXKeeper pathing to network

Does the function that restricts saving eQSL images to a local PC tolerate drive letters created via NET USE?

I don't know, Michael, I haven't tested it.
73,

Dave, AA6YQ
Re: DXKeeper pathing to network

 

开云体育

Dave - -

Does the function that restricts saving eQSL images to a local PC tolerate drive letters created via NET USE?

--
Michael Adams | mda@...
Re: Spotcollector sends calls to other DxLab Suite

 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Thursday, March 03, 2016 3:56 PM
To: dxlab@...
Subject: [dxlab] Spotcollector sends calls to other DxLab Suite

I have been using Dxlab Suite for a long time. For about a week, I have been researching for an answer to a (maybe of not) slight
problem. But did not find and answer.

When right click on a call line in Spotcollector, that call populates (goes to) call field of DxKeeper, DxView, Pathfinder and
Commander's Bandspread. Also there is an indication on that band in PropView Prediction.

I thought that right clicking on a call line in Spotcollector also send that call to Winwarbler. If so then it is no longer doing
it.

Is this a "senior moment" or I may have clicked a wrong buttons in any DxLab Config?

Question: When right clicking on a call in Spotcollector, is that call sent to WW?

Right-clicking an Entry in the Spot Database Display causes a menu of several commands to appear. If you then select the "Lookup"
command, SpotCollector will direct DXView and Pathfinder to perform "lookup" operations for the entry's callsign.

Double-clicking a Spot Database Display Entry will convey that Entry's callsign to the other DXLab applications, including
WinWarbler. Note that if you double-click the Entry for a station operating in SSB or CW, the Entry's callsign will only be conveyed
to WinWarbler if SpotCollector is configured appropriately, as described in

<>

73,

Dave, AA6YQ
Spotcollector sends calls to other DxLab Suite

[email protected]
 

开云体育

Hi,
?
I have been using Dxlab Suite for a long time.? For about a week,? I have been researching for an answer to a (maybe of not) slight problem.? But did not find and answer.
?
When right click on a call line in Spotcollector,? that call populates (goes to) call field of DxKeeper, DxView, Pathfinder and Commander's Bandspread.? Also there is an indication on that band in PropView Prediction.
?
I thought that right clicking on a call line in Spotcollector also send that call to Winwarbler.? If so then it is no longer doing it.
?
Is this a "senior moment" or I may have clicked a wrong buttons in any DxLab Config?
?
Question: When right clicking on a call in Spotcollector, is that call sent to WW?
?
Thanking you in advance for information.
?
73 de Rick W4UEF
?
Re: SQL filter for specific spotters?

 

开云体育

Works great. Even the audio announcements work correctly (announcing only when spot comes in from me for the first time and not on consecutive spots from others).

?

Thanks and 73

Andy

KU7T

?

From: dxlab@... [mailto:dxlab@...]
Sent: Thursday, March 3, 2016 11:36 AM
To: dxlab <dxlab@...>
Subject: Re: [dxlab] SQL filter for specific spotters?

?

?

On Thu, Mar 3, 2016 at 10:48 AM, ku7t@... [dxlab]
<dxlab@...> wrote:
>
> I want to fine tune a query so it will only include spots from my own skimmer (fed to RBN). It sort of works. When a spot spotted by me comes in, it shows up in the grid, but then quickly disappears. I believe this is because it has been re-spotted by someone else.
>
> Is there any setting or trick I could use to make this work? Basically I would like to filter out all my spots that are needed for better visibility and also audio announcements.

Try:

Cumulative like '*de KU7T *'

(assuming that's the 'Source' of your skimmer spots - don't include
the '-#' suffix, since SpotCollector appears to chop that off before
adding to 'Cumulative')

73,

~iain / N6ML
Re: SQL filter for specific spotters?

 

On Thu, Mar 3, 2016 at 10:48 AM, ku7t@... [dxlab]
<dxlab@...> wrote:

I want to fine tune a query so it will only include spots from my own skimmer (fed to RBN). It sort of works. When a spot spotted by me comes in, it shows up in the grid, but then quickly disappears. I believe this is because it has been re-spotted by someone else.

Is there any setting or trick I could use to make this work? Basically I would like to filter out all my spots that are needed for better visibility and also audio announcements.
Try:

Cumulative like '*de KU7T *'

(assuming that's the 'Source' of your skimmer spots - don't include
the '-#' suffix, since SpotCollector appears to chop that off before
adding to 'Cumulative')

73,

~iain / N6ML
SQL filter for specific spotters?

 

Hi,

I want to fine tune a query so it will only include spots from my own skimmer (fed to RBN).? It sort of works. When a spot spotted by me comes in, it shows up in the grid, but then quickly disappears. I believe this is because it has been re-spotted by someone else.

Is there any setting or trick I could use to make this work?? Basically I would like to filter out all my spots that are needed for better visibility and also audio announcements.

Thanks and 73
Andy
KU7T
73281 - 73300 of 229142