Date   

Re: Spot Collector : BandModeWorked problem

iain macdonnell - N6ML
 

On Wed, Sep 9, 2020 at 6:52 PM Dave AA6YQ <aa6yq@ambersoft.com> wrote:

+ AA6YQ comments below

I thought I stated it above - all-FT8 DXCC Challenge and per-band DXCC
on FT8 (i.e. 10m FT8, 12m FT8, etc.).

+ Thanks. So you want to confirm every DXCC entity in FT8 on every band between 160m and 6m (excluding 60m). If there were an option to always populate the BandModeWorked field in every Spot Database Entry, then filtering with

(BandModeWorked <> 'Y') and (Mode = 'FT8') and (Band in ('160m','80m','40m','30m','20m','17m','15m','12m','10m','6m'))

+ would identify the active stations you should seek to work, correct?
Something along those lines, yes.

73,

~iain / N6ML


Re: Error message when starting DXKeeper or SpotCollector.

Carl - WC4H
 

HI Dave.

So I tried port 52010 and got the same error & it told me that port 52012 was in use.
I then tried 52100 and it worked.  So I set it for that in Commander & DXKeeper.

It's stil kind of strange.

Thanks.
Carl - WC4H


Re: Spot Collector : BandModeWorked problem

Dave AA6YQ
 

+ AA6YQ comments below
I thought I stated it above - all-FT8 DXCC Challenge and per-band DXCC
on FT8 (i.e. 10m FT8, 12m FT8, etc.).

+ Thanks. So you want to confirm every DXCC entity in FT8 on every band between 160m and 6m (excluding 60m). If there were an option to always populate the BandModeWorked field in every Spot Database Entry, then filtering with 

(BandModeWorked <> 'Y') and (Mode = 'FT8') and (Band in ('160m','80m','40m','30m','20m','17m','15m','12m','10m','6m'))

+ would identify the active stations you should seek to work, correct?

      73,

         Dave, AA6YQ

 


Re: Error message when starting DXKeeper or SpotCollector.

Dave AA6YQ
 

* More AA6YQ comments below
I rebooted and launched only DXKeeper and still get the same error.

* Then you either need to identify the application that is using the port in question and configure it to use a different port, or configure each of your DXLab applications to use a different range of ports"

Commander: click the NetServ button the Configuration window's General tab

DXKeeper: use the "Network Service" panel on the Configuration window's Defaults tab

* Specify the same "base port" in both of the above applications.

      73,

               Dave, AA6YQ

 


Re: Spot Collector : BandModeWorked problem

iain macdonnell - N6ML
 

On Wed, Sep 9, 2020 at 5:28 PM Dave AA6YQ <aa6yq@ambersoft.com> wrote:

+ AA6YQ comments below

That may solve Phil's problem, but that's just one case where having
those fields populated for all spot database entries could be useful.

My current personal pursuit (only semi-serious) is pseudo-awards using
only FT8 and only LoTW. I've finished WAS on 6-160m (incl 60m). The
next milestone is DXCC Challenge (1073 worked, 942 confirmed). DXCC on
individual bands next, probably - pretty close to finishing 15 thru
80m. The rest are waiting for prop. SpotCollector is not very helpful
in this pursuit, even with FT8 as my user-specified digital mode
family) since it only identifies cases where the entity has not been
worked on any band as "needed". JTAlert helps quite a bit, but only on
the band I'm monitoring at the time.

+ Specifying FT8 as your user-specified digital mode means that you wish to confirm all DXCC entities in FT8.

+ I can't tell from your post above what other objectives you are pursuing. Please elaborate.
I thought I stated it above - all-FT8 DXCC Challenge and per-band DXCC
on FT8 (i.e. 10m FT8, 12m FT8, etc.).

73,

~iain / N6ML


Re: Error message when starting DXKeeper or SpotCollector.

Carl - WC4H
 

I rebooted and launched only DXKeeper and still get the same error.

Thanks.
Carl - WC4H


Re: Error message when starting DXKeeper or SpotCollector.

Carl - WC4H
 

The apps are the same ones that were running before the message:

DXKeeper, WSJT-X, GridTracker, FLrig (as radio for WSJT-X).
GridTracker has been logging the WSJT-X to DXKeeper for many weeks now.  
It uses Port 52000 but that is the normal setup.

I'll still try the reboot and let you know if it cures it.

Thanks.
Carl - WC4H


Re: Spot Collector : BandModeWorked problem

Dave AA6YQ
 

+ AA6YQ comments below
That may solve Phil's problem, but that's just one case where having
those fields populated for all spot database entries could be useful.

My current personal pursuit (only semi-serious) is pseudo-awards using
only FT8 and only LoTW. I've finished WAS on 6-160m (incl 60m). The
next milestone is DXCC Challenge (1073 worked, 942 confirmed). DXCC on
individual bands next, probably - pretty close to finishing 15 thru
80m. The rest are waiting for prop. SpotCollector is not very helpful
in this pursuit, even with FT8 as my user-specified digital mode
family) since it only identifies cases where the entity has not been
worked on any band as "needed". JTAlert helps quite a bit, but only on
the band I'm monitoring at the time.

+ Specifying FT8 as your user-specified digital mode means that you wish to confirm all DXCC entities in FT8.

+ I can't tell from your post above what other objectives you are pursuing. Please elaborate.

         73,

              Dave, AA6YQ

 


Re: Error message when starting DXKeeper or SpotCollector.

Dave AA6YQ
 

+ AA6YQ comments below

Since yesterday, when I launch DXKeeper I get the popup error: "TCP/IP port 52001 is already in use; choose another port and restart the Network Server.

Similarly for SpotCollector but with port 52003.

Then I click OK and they work.

I did update those two yesterday and I had a windows 10 update (not major) yesterday.

There are no other apps running using these ports.

+ If some other application on your system is using the 52000 - 52007 port range that DXLab applications employ by default, you can configure you DXLab applications to use another range. But before you do that, I suggest that you try rebooting Windows.

73,

Dave, AA6YQ


Error message when starting DXKeeper or SpotCollector.

Carl - WC4H
 

Hi Dave.

Since yesterday, when I launch DXKeeper I get the popup error: "TCP/IP port 52001 is already in use;  choose another port and restart the Network Server.

Similarly for SpotCollector but with port 52003.

Then I click OK and they work.

I did update those two yesterday and I had a windows 10 update (not major) yesterday.

There are no other apps running using these ports.

Thanks.
Carl - WC4H


Re: eqsl login /m suffix errorr

Joel Christiansen
 

Thanks for the reply Dave !

73 Joel w9ii


Re: Problem with Gateway

Bill Pence
 

And your image does not get sent to the list...


On Wed, Sep 9, 2020, 6:29 PM Richard Lawn <rjlawn@...> wrote:
I confess to not being a real contester but in retirement I'm now beginning to devote more time to contesting. I'm also trying to settle in on 1 logger for everything and am liking DXLabs Suite and Keeper. But I want to use N1MM+ for contesting. I've tried to set up the Gateway app so that anything logged in N1MM+ goes into DXKeeper. I think that WSJT-X couple be the culprit but it's not working and I've received the attached error message. I could use some help configuring this as I don't want to use more applications than are necessary. For radios I use either a Flex 6400 or IC-7610.

Rick, W2JAZ

--
Rick, W2JAZ 


Re: Problem with Gateway

Bill Pence
 

Email me direct. I use n1mm wsjt and dxkeeper gateway....


On Wed, Sep 9, 2020, 6:29 PM Richard Lawn <rjlawn@...> wrote:
I confess to not being a real contester but in retirement I'm now beginning to devote more time to contesting. I'm also trying to settle in on 1 logger for everything and am liking DXLabs Suite and Keeper. But I want to use N1MM+ for contesting. I've tried to set up the Gateway app so that anything logged in N1MM+ goes into DXKeeper. I think that WSJT-X couple be the culprit but it's not working and I've received the attached error message. I could use some help configuring this as I don't want to use more applications than are necessary. For radios I use either a Flex 6400 or IC-7610.

Rick, W2JAZ

--
Rick, W2JAZ 


Problem with Gateway

Richard Lawn <rjlawn@...>
 

I confess to not being a real contester but in retirement I'm now beginning to devote more time to contesting. I'm also trying to settle in on 1 logger for everything and am liking DXLabs Suite and Keeper. But I want to use N1MM+ for contesting. I've tried to set up the Gateway app so that anything logged in N1MM+ goes into DXKeeper. I think that WSJT-X couple be the culprit but it's not working and I've received the attached error message. I could use some help configuring this as I don't want to use more applications than are necessary. For radios I use either a Flex 6400 or IC-7610.

Rick, W2JAZ

--
Rick, W2JAZ 


Re: Spot Collector : BandModeWorked problem

iain macdonnell - N6ML
 

On Wed, Sep 9, 2020 at 11:46 AM Dave AA6YQ <aa6yq@ambersoft.com> wrote:

+ AA6YQ comments below

Tnx for quick reply.

Well, I understand that it will be too expensive (in term of perormance).

I love DxLabs software. Dave you are making a great job.
But, this function for all call-signs should be great.

I am on the air every day and I try to make as much interesting QSO as I can.
For me, an interesting QSO is not located in EU, and if it is a DX call-sign, it's better.

Very often I see a Dx-call-sign on spotcollector. Then I click on it, and I have wait that DxKeeper tells me I have already worked him on this bandmode.
I have 90000 QSO in log, about 2700 slots, so many DX seen on spotcollector had already been worked. But here are some DX I did not work yet.

I just saw the Dave's answer. (tnx DAve)

+ states that they are not populated in all cases. SpotCollector only refers to a Spot Database Entry's Bandworked field, for example, if the Entry's BandProgress field is set to 'W' (meaning "worked"). For all other values of BandProgress, there is no need to take the time to query your log to determine a value for Bandworked.

There is a big difference for me :
If I have already worked and confirmed ZL4TT on 80m CW, spotcollector will not show ZL4TT as needed.
So I have ZL worked and confirmed. But from EU, a QSO with ZL is always a pleasure because it's very far from EU.

So, if SpotCollector shows ZL2AGY on 80m CW, it should be great to work him if it's an unworked.
There is no value for award, but there is a good value for a good QSO.

This is my point of view. May be I am alone ... or not.

+ There is a DXing objective known as the "Quixote Quest" which is to confirm every DXCC entity on every combination of band and mode. There is a SpotCollector add-in called SpotSpy that supports this objective. See

<http://www.dl9ho.de/SpotSpy/SpotSpy.htm>

+ As for the objective of confirming a QSO with every callsign on every combination of band and mode, I'm sure that you aren't the only ham pursuing this objective, but your numbers are small. I prioritize DXLab development work by considered the magnitude of the effort, the magnitude of the benefit to a user, and the number of users likely to enjoy that benefit.

+ As was writing this response, it occurred to me that the effort to extend SpotCollector to support your "every callsign on every combination of band and mode" object is simply that of providing a "consider all callsigns to have a <leaderboard> tag" option. So while the number of users likely to enjoy the benefit is small, so is the magnitude of the effort. I've added this to SpotCollector's enhancement list.
That may solve Phil's problem, but that's just one case where having
those fields populated for all spot database entries could be useful.

My current personal pursuit (only semi-serious) is pseudo-awards using
only FT8 and only LoTW. I've finished WAS on 6-160m (incl 60m). The
next milestone is DXCC Challenge (1073 worked, 942 confirmed). DXCC on
individual bands next, probably - pretty close to finishing 15 thru
80m. The rest are waiting for prop. SpotCollector is not very helpful
in this pursuit, even with FT8 as my user-specified digital mode
family) since it only identifies cases where the entity has not been
worked on any band as "needed". JTAlert helps quite a bit, but only on
the band I'm monitoring at the time.

Not complaining ... just sharing another perspective....

73,

~iain / N6ML


Re: Port 7300 conflict?

Dave AA6YQ
 

+ AA6YQ comments below

I have been using Spot Collector without incident until today. When I booted up my PC (Win 10) and started the program, I received an error message that I could not log into the N6WS cluster.

+ Please make a screen shot showing the error message, attach the screen shot to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ


Re: Spot Collector : BandModeWorked problem

F5PHW Phil BERGER
 

Dave

Tnx for quick answer as usual.

And also for this sentence :

"I've added this to SpotCollector's enhancement list."

If another operator need this function, please, send an email to Dave !!!

Tnx to all

Best 73

F5PHW Phil

Web page on http://f5phw.free.fr
F5PHW on FACEBOOK : https://www.facebook.com/phil.berger.75
WX in Nostang :
http://www.nostang.meteoamikuze.com/index.html
https://www.wunderground.com/personal-weather-station/dashboard?ID=IBRETAGN147

----- Mail original -----
De: "aa6yq" <aa6yq@ambersoft.com>
À: "DXLab" <DXLab@groups.io>
Envoyé: Mercredi 9 Septembre 2020 20:46:46
Objet: Re: [DXLab] Spot Collector : BandModeWorked problem

+ AA6YQ comments below

Tnx for quick reply.

Well, I understand that it will be too expensive (in term of perormance).

I love DxLabs software. Dave you are making a great job.
But, this function for all call-signs should be great.

I am on the air every day and I try to make as much interesting QSO as I can.
For me, an interesting QSO is not located in EU, and if it is a DX call-sign, it's better.

Very often I see a Dx-call-sign on spotcollector. Then I click on it, and I have wait that DxKeeper tells me I have already worked him on this bandmode.
I have 90000 QSO in log, about 2700 slots, so many DX seen on spotcollector had already been worked. But here are some DX I did not work yet.

I just saw the Dave's answer. (tnx DAve)

+ states that they are not populated in all cases. SpotCollector only refers to a Spot Database Entry's Bandworked field, for example, if the Entry's BandProgress field is set to 'W' (meaning "worked"). For all other values of BandProgress, there is no need to take the time to query your log to determine a value for Bandworked.

There is a big difference for me :
If I have already worked and confirmed ZL4TT on 80m CW, spotcollector will not show ZL4TT as needed.
So I have ZL worked and confirmed. But from EU, a QSO with ZL is always a pleasure because it's very far from EU.

So, if SpotCollector shows ZL2AGY on 80m CW, it should be great to work him if it's an unworked.
There is no value for award, but there is a good value for a good QSO.

This is my point of view. May be I am alone ... or not.

+ There is a DXing objective known as the "Quixote Quest" which is to confirm every DXCC entity on every combination of band and mode. There is a SpotCollector add-in called SpotSpy that supports this objective. See

<http://www.dl9ho.de/SpotSpy/SpotSpy.htm>

+ As for the objective of confirming a QSO with every callsign on every combination of band and mode, I'm sure that you aren't the only ham pursuing this objective, but your numbers are small. I prioritize DXLab development work by considered the magnitude of the effort, the magnitude of the benefit to a user, and the number of users likely to enjoy that benefit.

+ As was writing this response, it occurred to me that the effort to extend SpotCollector to support your "every callsign on every combination of band and mode" object is simply that of providing a "consider all callsigns to have a <leaderboard> tag" option. So while the number of users likely to enjoy the benefit is small, so is the magnitude of the effort. I've added this to SpotCollector's enhancement list.

73,

Dave, AA6YQ


Re: DXLab error update and SpotCollector question/feature request.

Dave AA6YQ
 

+ AA6YQ comments below
This is what I do, when I want the WWV data updated in SpotCollector. The telnet cluster is used just so I can issue the SH/WWV command at the start of a session

+ You can configure SpotCollector to issue the SH/WWV command immediately after connecting to the telnet cluster.

, or let it auto update if the session extends long enough.

Granted that I'm not familiar with the 'behind the scenes' activities and perhaps the cost involved, my preference is not to use DX Cluster resources just for WWV data. It does not seem fair and/or an efficient use of the resource.

+ There's no cause for concern. DX Clusters are designed to handle large numbers of connections, and your usage is "in bounds". If you wanted, you could configure DXKeeper with 3 "WWV only" spot sources but only enable one, rotating among them from time to time.

       73,

             Dave, AA6YQ

 


Port 7300 conflict?

Lou Laderman W0FK
 

I have been using Spot Collector without incident until today. When I booted up my PC (Win 10) and started the program, I received an error message that I could not log into the N6WS cluster.



I didn't change anything in the configuration settings, and logged into the other clusters (one of which also specifies port 7300. I am puzzled why I am getting this error message and what to do about it. There are my config settings under spot sources:



I am also running Commander, DXKeeper and DXView. Radio selected is a Flex 6600 (radio was not active when I ran into this issue).

I'd appreciate some guidance.

73, Lou W0FK


Re: Spot Collector : BandModeWorked problem

Dave AA6YQ
 

+ AA6YQ comments below

Tnx for quick reply.

Well, I understand that it will be too expensive (in term of perormance).

I love DxLabs software. Dave you are making a great job.
But, this function for all call-signs should be great.

I am on the air every day and I try to make as much interesting QSO as I can.
For me, an interesting QSO is not located in EU, and if it is a DX call-sign, it's better.

Very often I see a Dx-call-sign on spotcollector. Then I click on it, and I have wait that DxKeeper tells me I have already worked him on this bandmode.
I have 90000 QSO in log, about 2700 slots, so many DX seen on spotcollector had already been worked. But here are some DX I did not work yet.

I just saw the Dave's answer. (tnx DAve)

+ states that they are not populated in all cases. SpotCollector only refers to a Spot Database Entry's Bandworked field, for example, if the Entry's BandProgress field is set to 'W' (meaning "worked"). For all other values of BandProgress, there is no need to take the time to query your log to determine a value for Bandworked.

There is a big difference for me :
If I have already worked and confirmed ZL4TT on 80m CW, spotcollector will not show ZL4TT as needed.
So I have ZL worked and confirmed. But from EU, a QSO with ZL is always a pleasure because it's very far from EU.

So, if SpotCollector shows ZL2AGY on 80m CW, it should be great to work him if it's an unworked.
There is no value for award, but there is a good value for a good QSO.

This is my point of view. May be I am alone ... or not.

+ There is a DXing objective known as the "Quixote Quest" which is to confirm every DXCC entity on every combination of band and mode. There is a SpotCollector add-in called SpotSpy that supports this objective. See

<http://www.dl9ho.de/SpotSpy/SpotSpy.htm>

+ As for the objective of confirming a QSO with every callsign on every combination of band and mode, I'm sure that you aren't the only ham pursuing this objective, but your numbers are small. I prioritize DXLab development work by considered the magnitude of the effort, the magnitude of the benefit to a user, and the number of users likely to enjoy that benefit.

+ As was writing this response, it occurred to me that the effort to extend SpotCollector to support your "every callsign on every combination of band and mode" object is simply that of providing a "consider all callsigns to have a <leaderboard> tag" option. So while the number of users likely to enjoy the benefit is small, so is the magnitude of the effort. I've added this to SpotCollector's enhancement list.

73,

Dave, AA6YQ

9761 - 9780 of 205912