Date   
Re: Working DX Cluster List -- USA and Canada ** Confirmed

Pete Smith
 

There were two problems I became painfully aware of when I manually updated the list last year:

You have no way of knowing about new clusters that have joined the community since the last list

Not all clusters are 24/7, so a lot depends on when you test.

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 10/25/2019 1:22 PM, Michael Walker wrote:

Hi Brian

Yes, you are correct.  It just needs an owner to make it happen.   Are you volunteering?

Pete, the same is true for the list of valid clusters to be in update in N1MM.  It also needs someone and I don't think it can be the N1MM crew.  I'd rather have them writing code.  For the moment, I will see if I can merge all the data points in the coming weeks and the publish on GitHub. 

73, Mike 

On Fri, Oct 25, 2019 at 1:14 PM <brian.moran@...> wrote:
Computers are pretty good at contacting one another -- "Uptime monitoring" services can connect to a website and do something to verify that it's up at whatever interval you like, and keep stats over a long time -- much longer than a human can pay attention.  Sure, it might cost $20 a month to have the list always updated, but conceivably that data could be used to have the list in N1MM Logger (or a page on the N1MM Logger website) be shown with a 'quality bar' next to each of the choices with the status... just a thought.


On Fri, Oct 25, 2019 at 7:41 AM Steve London <n2ic@...> wrote:
W0MU,w0mu.net:7373

has always worked well.

73,
Steve, N2IC

On 10/25/2019 08:33 AM, Larry K8UT wrote:
> Mike,
>
> THANK YOU for testing the North American clusters on the list. If you can supply
> a complete list = Tested_North_American and Untested_Everywhere_Else = I will
> replace the list on the website with your updated list. (send to me as an email
> attach)
>
> And if anyone else wants to volunteer and test those untested from Mike's list
> we can integrate your results into a complete "all tested as of 2019-10-25"
> download file.
>
> While you were testing those we were modifying the documentation for importing a
> list into N1MM+. You will find a new section under >Docs >Windows >Telnet
> Window, "Importing a Downloaded Cluster List"
> https://n1mmwp.hamdocs.com/manual-windows/telnet-window/#importing-a-downloaded-cluster-list
>
> Thanks again,
>
> -larry K8UT
> ------ Original Message ------
> From: "Michael Walker" <va3mw@... <mailto:va3mw@...>>
> To: N1MMLoggerPlus@groups.io <mailto:N1MMLoggerPlus@groups.io>
> Sent: 2019-10-25 10:15:23
> Subject: [N1MM+] Working DX Cluster List -- USA and Canada ** Confirmed
>
>> Hi All
>>
>> I took an hour this morning and tested ALL the USA and Canada dx clusters.  I
>> did not test any cluster outside of NA.  Maybe someone else can do that.
>>
>> This is what works:
>>
>> K1EU,K1EU.DYNIP.COM <http://K1EU.DYNIP.COM>
>> K2LS,DXC.K2LS.COM <http://DXC.K2LS.COM>
>> K7AR,K7AR.NET:7300 <http://K7AR.NET:7300>
>> KN4F,DXC.KN4F.NET <http://DXC.KN4F.NET>
>> N7OD,N7OD.PENTUX.NET <http://N7OD.PENTUX.NET>
>> VA3MW,va3mw.dxcluster.org:41112 <http://va3mw.dxcluster.org:41112>
>> VE3EY-7,DX.FIREROUTE.COM <http://DX.FIREROUTE.COM>
>> VE6TN,DX.MIDDLEBROOK.CA <http://DX.MIDDLEBROOK.CA>
>> VE7CC,VE7CC.NET <http://VE7CC.NET>
>> W1AAA,DXUSA.NET:7300 <http://DXUSA.NET:7300>
>> WF5E,WF5E.NO-IP.COM <http://WF5E.NO-IP.COM>
>> RBN,telnet.reversebeacon.net:7000 <http://telnet.reversebeacon.net:7000>
>> NC7J,dxc.nc7j.com:23 <http://dxc.nc7j.com:23>
>>
>> If you want to fix this.
>>
>>  1. Copy the above  list and place it in a text file somewhere you can find
>>  2. Open up N1MM and go into the Telnet screen.
>>  3. Edit Telnet List
>>  4. Highlight all the entries by holding the left button on the mouse and
>>     dragging down to the bottom so they are all in blue.
>>  5. Hit the delete key and that will delete all your cluster entries.  This
>>     will clean out the entire list.  You can keep the ones you like if you
>>     know the work
>>  6. Now, File/Import and select the file you saved in step 1
>>
>> You now have a very clean and workable list.
>>
>> Mike va3mw
>



Re: Working DX Cluster List -- USA and Canada ** Confirmed

Michael Walker
 

Hi Brian

Yes, you are correct.  It just needs an owner to make it happen.   Are you volunteering?

Pete, the same is true for the list of valid clusters to be in update in N1MM.  It also needs someone and I don't think it can be the N1MM crew.  I'd rather have them writing code.  For the moment, I will see if I can merge all the data points in the coming weeks and the publish on GitHub. 

73, Mike 

On Fri, Oct 25, 2019 at 1:14 PM <brian.moran@...> wrote:
Computers are pretty good at contacting one another -- "Uptime monitoring" services can connect to a website and do something to verify that it's up at whatever interval you like, and keep stats over a long time -- much longer than a human can pay attention.  Sure, it might cost $20 a month to have the list always updated, but conceivably that data could be used to have the list in N1MM Logger (or a page on the N1MM Logger website) be shown with a 'quality bar' next to each of the choices with the status... just a thought.


On Fri, Oct 25, 2019 at 7:41 AM Steve London <n2ic@...> wrote:
W0MU,w0mu.net:7373

has always worked well.

73,
Steve, N2IC

On 10/25/2019 08:33 AM, Larry K8UT wrote:
> Mike,
>
> THANK YOU for testing the North American clusters on the list. If you can supply
> a complete list = Tested_North_American and Untested_Everywhere_Else = I will
> replace the list on the website with your updated list. (send to me as an email
> attach)
>
> And if anyone else wants to volunteer and test those untested from Mike's list
> we can integrate your results into a complete "all tested as of 2019-10-25"
> download file.
>
> While you were testing those we were modifying the documentation for importing a
> list into N1MM+. You will find a new section under >Docs >Windows >Telnet
> Window, "Importing a Downloaded Cluster List"
> https://n1mmwp.hamdocs.com/manual-windows/telnet-window/#importing-a-downloaded-cluster-list
>
> Thanks again,
>
> -larry K8UT
> ------ Original Message ------
> From: "Michael Walker" <va3mw@... <mailto:va3mw@...>>
> To: N1MMLoggerPlus@groups.io <mailto:N1MMLoggerPlus@groups.io>
> Sent: 2019-10-25 10:15:23
> Subject: [N1MM+] Working DX Cluster List -- USA and Canada ** Confirmed
>
>> Hi All
>>
>> I took an hour this morning and tested ALL the USA and Canada dx clusters.  I
>> did not test any cluster outside of NA.  Maybe someone else can do that.
>>
>> This is what works:
>>
>> K1EU,K1EU.DYNIP.COM <http://K1EU.DYNIP.COM>
>> K2LS,DXC.K2LS.COM <http://DXC.K2LS.COM>
>> K7AR,K7AR.NET:7300 <http://K7AR.NET:7300>
>> KN4F,DXC.KN4F.NET <http://DXC.KN4F.NET>
>> N7OD,N7OD.PENTUX.NET <http://N7OD.PENTUX.NET>
>> VA3MW,va3mw.dxcluster.org:41112 <http://va3mw.dxcluster.org:41112>
>> VE3EY-7,DX.FIREROUTE.COM <http://DX.FIREROUTE.COM>
>> VE6TN,DX.MIDDLEBROOK.CA <http://DX.MIDDLEBROOK.CA>
>> VE7CC,VE7CC.NET <http://VE7CC.NET>
>> W1AAA,DXUSA.NET:7300 <http://DXUSA.NET:7300>
>> WF5E,WF5E.NO-IP.COM <http://WF5E.NO-IP.COM>
>> RBN,telnet.reversebeacon.net:7000 <http://telnet.reversebeacon.net:7000>
>> NC7J,dxc.nc7j.com:23 <http://dxc.nc7j.com:23>
>>
>> If you want to fix this.
>>
>>  1. Copy the above  list and place it in a text file somewhere you can find
>>  2. Open up N1MM and go into the Telnet screen.
>>  3. Edit Telnet List
>>  4. Highlight all the entries by holding the left button on the mouse and
>>     dragging down to the bottom so they are all in blue.
>>  5. Hit the delete key and that will delete all your cluster entries.  This
>>     will clean out the entire list.  You can keep the ones you like if you
>>     know the work
>>  6. Now, File/Import and select the file you saved in step 1
>>
>> You now have a very clean and workable list.
>>
>> Mike va3mw
>



Re: Working DX Cluster List -- USA and Canada ** Confirmed

brian.moran@...
 

Computers are pretty good at contacting one another -- "Uptime monitoring" services can connect to a website and do something to verify that it's up at whatever interval you like, and keep stats over a long time -- much longer than a human can pay attention.  Sure, it might cost $20 a month to have the list always updated, but conceivably that data could be used to have the list in N1MM Logger (or a page on the N1MM Logger website) be shown with a 'quality bar' next to each of the choices with the status... just a thought.


On Fri, Oct 25, 2019 at 7:41 AM Steve London <n2ic@...> wrote:
W0MU,w0mu.net:7373

has always worked well.

73,
Steve, N2IC

On 10/25/2019 08:33 AM, Larry K8UT wrote:
> Mike,
>
> THANK YOU for testing the North American clusters on the list. If you can supply
> a complete list = Tested_North_American and Untested_Everywhere_Else = I will
> replace the list on the website with your updated list. (send to me as an email
> attach)
>
> And if anyone else wants to volunteer and test those untested from Mike's list
> we can integrate your results into a complete "all tested as of 2019-10-25"
> download file.
>
> While you were testing those we were modifying the documentation for importing a
> list into N1MM+. You will find a new section under >Docs >Windows >Telnet
> Window, "Importing a Downloaded Cluster List"
> https://n1mmwp.hamdocs.com/manual-windows/telnet-window/#importing-a-downloaded-cluster-list
>
> Thanks again,
>
> -larry K8UT
> ------ Original Message ------
> From: "Michael Walker" <va3mw@... <mailto:va3mw@...>>
> To: N1MMLoggerPlus@groups.io <mailto:N1MMLoggerPlus@groups.io>
> Sent: 2019-10-25 10:15:23
> Subject: [N1MM+] Working DX Cluster List -- USA and Canada ** Confirmed
>
>> Hi All
>>
>> I took an hour this morning and tested ALL the USA and Canada dx clusters.  I
>> did not test any cluster outside of NA.  Maybe someone else can do that.
>>
>> This is what works:
>>
>> K1EU,K1EU.DYNIP.COM <http://K1EU.DYNIP.COM>
>> K2LS,DXC.K2LS.COM <http://DXC.K2LS.COM>
>> K7AR,K7AR.NET:7300 <http://K7AR.NET:7300>
>> KN4F,DXC.KN4F.NET <http://DXC.KN4F.NET>
>> N7OD,N7OD.PENTUX.NET <http://N7OD.PENTUX.NET>
>> VA3MW,va3mw.dxcluster.org:41112 <http://va3mw.dxcluster.org:41112>
>> VE3EY-7,DX.FIREROUTE.COM <http://DX.FIREROUTE.COM>
>> VE6TN,DX.MIDDLEBROOK.CA <http://DX.MIDDLEBROOK.CA>
>> VE7CC,VE7CC.NET <http://VE7CC.NET>
>> W1AAA,DXUSA.NET:7300 <http://DXUSA.NET:7300>
>> WF5E,WF5E.NO-IP.COM <http://WF5E.NO-IP.COM>
>> RBN,telnet.reversebeacon.net:7000 <http://telnet.reversebeacon.net:7000>
>> NC7J,dxc.nc7j.com:23 <http://dxc.nc7j.com:23>
>>
>> If you want to fix this.
>>
>>  1. Copy the above  list and place it in a text file somewhere you can find
>>  2. Open up N1MM and go into the Telnet screen.
>>  3. Edit Telnet List
>>  4. Highlight all the entries by holding the left button on the mouse and
>>     dragging down to the bottom so they are all in blue.
>>  5. Hit the delete key and that will delete all your cluster entries.  This
>>     will clean out the entire list.  You can keep the ones you like if you
>>     know the work
>>  6. Now, File/Import and select the file you saved in step 1
>>
>> You now have a very clean and workable list.
>>
>> Mike va3mw
>



Re: Working DX Cluster List -- USA and Canada ** Confirmed

Gary E. Kohtala
 


Please add:

W7JD-1,   w7jd.ddns.net, PORT 9000. It is up 24/7, works, and is in Radcliff, KY.
I am sysop. Runs VE7CC's CC Cluster software.

I have full time feed from VE7CC-1 and others, plus RBN. Users can optionally turn
RBN spots off or on with a single command.
Thanks!

Best regards,

Gary, K7EK

Re: Potential Logging Issues For 2019 CW WW DX SSB Contest

Pete Smith
 

Hi Ted.  I had forgotten all about that feature, which seems like it would be fine during the QSO.  Do you know any way to fix it once the QSO has been logged?

I just tried to run that tool (Add Call to Country) with a hypothetical VP8 callsign and got the following error:

What to do???

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 10/25/2019 12:12 PM, Ted Bryant wrote:

Tom,

 

Have you tried using the “Add Call to Country” feature under the Tools menu in the Entry window?

https://n1mmwp.hamdocs.com/manual-windows/entry-window/#tools-menu-selections

 

Add call to country – Specify a country for the call-sign in the call-sign textbox in the Entry window. If no call-sign is entered this menu item will be grayed out. This is a quick way during the heat of a contest to add a country temporarily, until the next time you import wl_cty.dat. Making changes permanent requires editing the country file (wl_cty.dat) to be imported.

 

73, Ted W4NZ

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Tom Owens via Groups.Io
Sent: Friday, October 25, 2019 11:18 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] Potential Logging Issues For 2019 CW WW DX SSB Contest

 

Pete and John,

Thanks for the input.

Pete, I am using the current  WL-Cty.dat file.  It was installed today.  And the issues still persist.

John, we too change the zone to what we copy BEFORE logging the contact.  Yes, I can change the zone in the Edit Contact window but that does not change the country.  For example, I just logged VK9OOO.  That call could be in zone 29, 30 or 32.  The program logged it as zone 32, Norfolk --- which is correct BUT that call could have been in zone 29 or 30.  For kicks, I went into the Edit Contact window (it is not possible to change the country prefix there as it is grayed out).  I changed the zone there to zone  but the Countries window still show the contact VK9N.  If the zone change took, which it did, the country should have changes to KL7.

The problems occurs in two different ways.  One, there are more than one country in the same zone.  Two, the country can be in one or more zone - HK0 can be ether zone 7 or 9.  The program defaults to zone 7 - HK0A.  Changing the zone to 9 does NOT change the country to HK0M in either the Edit Contact window of the Countries worked window.

If either of you would like to call me I can be reached by phone at 206 935-0457.  I can walk you through the procedure to correctly identify the correct zones and countries.

Tom, K7RI
206 935-0457

Re: Airspy HF+/Spectrum Display/Receive Antenna

Rick Tavan
 

You can drive the HF+ from the IF Out port of the K3, leaving the RX IN connection available for an actual RX antenna. I tried this successfully but eventually reverted to the RX Ant loop. You don't suffer the 3 dB sharing loss but I think you have to specify different IF offsets when you change modes. I'm not using an actual RX antenna. I suppose you could use both an HF+ connected to RX Ant OUT and an actual RX antenna connected to RX Ant IN but I haven't tried it.

73,

/Rick N6XI


On Fri, Oct 25, 2019 at 8:00 AM Pete Smith <n4zr@...> wrote:

I would like to be able to use a receiving antenna on my K3 while also using the spectrum display of N1MM+.  I assume from the manual's discussion of using the HF+ that it *must* be used on the Ant Out/Ant In loop of my K3.  That suggests that I either have to choose one or the other or cascade splitters and accept the 6+ dB of loss.  Am I missing something?

-- 

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.



--
--

Rick Tavan
Truckee and Saratoga, CA

Re: Working DX Cluster List -- USA and Canada ** Confirmed

Pete Smith
 

Mike, I don't know which, if any cluster file is included in updates of MM+, but you can find the latest cluster list at <https://n1mmwp.hamdocs.com/mmfiles/clusters-2019-10-11-txt/>

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 10/25/2019 11:22 AM, Michael Walker wrote:

Hi Pete

I agree.  the RBN should be removed.

As well, the other 2 were never in the 'shipped' version of N1MM that I can tell, so if they got into a list, they had to be manually added.

What are their addresses?  

Mike va3mw


On Fri, Oct 25, 2019 at 11:12 AM Pete Smith <n4zr@...> wrote:

A couple of caveats - this list lacks a couple of longtime stalwarts, W9PA and W3LPL.  There are probably a number of others. 

Also, the list includes the RBN's Telnet feed, which is intended only to provide spots to DX clusters that wish to connect.  To keep up with the volume, the servers behind this address have been stripped of all filtering, so you will miss out on some very useful capabilities if you connect directly to the RBN.  Please don't!  You don't want to be the straw that breaks the camel's back during CQWWCW.

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 10/25/2019 10:50 AM, John Webster wrote:
Many, many thanks. 

John
NN1SS

On Fri, Oct 25, 2019 at 10:15 AM Michael Walker <va3mw@...> wrote:
Hi All

I took an hour this morning and tested ALL the USA and Canada dx clusters.  I did not test any cluster outside of NA.  Maybe someone else can do that.

This is what works:


If you want to fix this.

  1. Copy the above  list and place it in a text file somewhere you can find 
  2. Open up N1MM and go into the Telnet screen.
  3. Edit Telnet List
  4. Highlight all the entries by holding the left button on the mouse and dragging down to the bottom so they are all in blue.
  5. Hit the delete key and that will delete all your cluster entries.  This will clean out the entire list.  You can keep the ones you like if you know the work
  6. Now, File/Import and select the file you saved in step 1
You now have a very clean and workable list.

Mike va3mw

Re: Potential Logging Issues For 2019 CW WW DX SSB Contest

Ted Bryant
 

Tom,

 

Have you tried using the “Add Call to Country” feature under the Tools menu in the Entry window?

https://n1mmwp.hamdocs.com/manual-windows/entry-window/#tools-menu-selections

 

Add call to country – Specify a country for the call-sign in the call-sign textbox in the Entry window. If no call-sign is entered this menu item will be grayed out. This is a quick way during the heat of a contest to add a country temporarily, until the next time you import wl_cty.dat. Making changes permanent requires editing the country file (wl_cty.dat) to be imported.

 

73, Ted W4NZ

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Tom Owens via Groups.Io
Sent: Friday, October 25, 2019 11:18 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] Potential Logging Issues For 2019 CW WW DX SSB Contest

 

Pete and John,

Thanks for the input.

Pete, I am using the current  WL-Cty.dat file.  It was installed today.  And the issues still persist.

John, we too change the zone to what we copy BEFORE logging the contact.  Yes, I can change the zone in the Edit Contact window but that does not change the country.  For example, I just logged VK9OOO.  That call could be in zone 29, 30 or 32.  The program logged it as zone 32, Norfolk --- which is correct BUT that call could have been in zone 29 or 30.  For kicks, I went into the Edit Contact window (it is not possible to change the country prefix there as it is grayed out).  I changed the zone there to zone  but the Countries window still show the contact VK9N.  If the zone change took, which it did, the country should have changes to KL7.

The problems occurs in two different ways.  One, there are more than one country in the same zone.  Two, the country can be in one or more zone - HK0 can be ether zone 7 or 9.  The program defaults to zone 7 - HK0A.  Changing the zone to 9 does NOT change the country to HK0M in either the Edit Contact window of the Countries worked window.

If either of you would like to call me I can be reached by phone at 206 935-0457.  I can walk you through the procedure to correctly identify the correct zones and countries.

Tom, K7RI
206 935-0457

Re: Working DX Cluster List -- USA and Canada ** Confirmed

Michael Walker
 

Hi Pete

I agree.  the RBN should be removed.

As well, the other 2 were never in the 'shipped' version of N1MM that I can tell, so if they got into a list, they had to be manually added.

What are their addresses?  

Mike va3mw


On Fri, Oct 25, 2019 at 11:12 AM Pete Smith <n4zr@...> wrote:

A couple of caveats - this list lacks a couple of longtime stalwarts, W9PA and W3LPL.  There are probably a number of others. 

Also, the list includes the RBN's Telnet feed, which is intended only to provide spots to DX clusters that wish to connect.  To keep up with the volume, the servers behind this address have been stripped of all filtering, so you will miss out on some very useful capabilities if you connect directly to the RBN.  Please don't!  You don't want to be the straw that breaks the camel's back during CQWWCW.

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 10/25/2019 10:50 AM, John Webster wrote:
Many, many thanks. 

John
NN1SS

On Fri, Oct 25, 2019 at 10:15 AM Michael Walker <va3mw@...> wrote:
Hi All

I took an hour this morning and tested ALL the USA and Canada dx clusters.  I did not test any cluster outside of NA.  Maybe someone else can do that.

This is what works:


If you want to fix this.

  1. Copy the above  list and place it in a text file somewhere you can find 
  2. Open up N1MM and go into the Telnet screen.
  3. Edit Telnet List
  4. Highlight all the entries by holding the left button on the mouse and dragging down to the bottom so they are all in blue.
  5. Hit the delete key and that will delete all your cluster entries.  This will clean out the entire list.  You can keep the ones you like if you know the work
  6. Now, File/Import and select the file you saved in step 1
You now have a very clean and workable list.

Mike va3mw

Re: Potential Logging Issues For 2019 CW WW DX SSB Contest

Tom Owens
 

Pete and John,

Thanks for the input.

Pete, I am using the current  WL-Cty.dat file.  It was installed today.  And the issues still persist.

John, we too change the zone to what we copy BEFORE logging the contact.  Yes, I can change the zone in the Edit Contact window but that does not change the country.  For example, I just logged VK9OOO.  That call could be in zone 29, 30 or 32.  The program logged it as zone 32, Norfolk --- which is correct BUT that call could have been in zone 29 or 30.  For kicks, I went into the Edit Contact window (it is not possible to change the country prefix there as it is grayed out).  I changed the zone there to zone  but the Countries window still show the contact VK9N.  If the zone change took, which it did, the country should have changes to KL7.

The problems occurs in two different ways.  One, there are more than one country in the same zone.  Two, the country can be in one or more zone - HK0 can be ether zone 7 or 9.  The program defaults to zone 7 - HK0A.  Changing the zone to 9 does NOT change the country to HK0M in either the Edit Contact window of the Countries worked window.

If either of you would like to call me I can be reached by phone at 206 935-0457.  I can walk you through the procedure to correctly identify the correct zones and countries.

Tom, K7RI
206 935-0457

Re: Working DX Cluster List -- USA and Canada ** Confirmed

Pete Smith
 

A couple of caveats - this list lacks a couple of longtime stalwarts, W9PA and W3LPL.  There are probably a number of others. 

Also, the list includes the RBN's Telnet feed, which is intended only to provide spots to DX clusters that wish to connect.  To keep up with the volume, the servers behind this address have been stripped of all filtering, so you will miss out on some very useful capabilities if you connect directly to the RBN.  Please don't!  You don't want to be the straw that breaks the camel's back during CQWWCW.

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 10/25/2019 10:50 AM, John Webster wrote:

Many, many thanks. 

John
NN1SS

On Fri, Oct 25, 2019 at 10:15 AM Michael Walker <va3mw@...> wrote:
Hi All

I took an hour this morning and tested ALL the USA and Canada dx clusters.  I did not test any cluster outside of NA.  Maybe someone else can do that.

This is what works:


If you want to fix this.

  1. Copy the above  list and place it in a text file somewhere you can find 
  2. Open up N1MM and go into the Telnet screen.
  3. Edit Telnet List
  4. Highlight all the entries by holding the left button on the mouse and dragging down to the bottom so they are all in blue.
  5. Hit the delete key and that will delete all your cluster entries.  This will clean out the entire list.  You can keep the ones you like if you know the work
  6. Now, File/Import and select the file you saved in step 1
You now have a very clean and workable list.

Mike va3mw

Airspy HF+/Spectrum Display/Receive Antenna

Pete Smith
 

I would like to be able to use a receiving antenna on my K3 while also using the spectrum display of N1MM+.  I assume from the manual's discussion of using the HF+ that it *must* be used on the Ant Out/Ant In loop of my K3.  That suggests that I either have to choose one or the other or cascade splitters and accept the 6+ dB of loss.  Am I missing something?

-- 

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.

Re: Call History File for CQ WW SSB

David AD4TJ
 

Thanks, Tim!

David

On Friday, October 25, 2019, 10:26:23 AM EDT, Tim Shoppa <tshoppa@...> wrote:


Super Check Partial and the Country Files, are for all purposes, the call history file for CQWW.

Between them they contain callsigns of known active contesters, and the rules and exceptions to map callsigns to zones and countries.

The maintainers of these files not only base these on past history, but also include announced special calls and DXpeditions active during CQWW.

You can update them by going to Tools->Download and Install Latest Check Partial File, and Tools->Download and install latest country file.

Tim N3QE


On Fri, Oct 25, 2019 at 9:37 AM David AD4TJ via Groups.Io <ad4tj=yahoo.com@groups.io> wrote:
I don't see a CHF for this weekend's contest. Not needed?

73, David AD4TJ

Re: Working DX Cluster List -- USA and Canada ** Confirmed

John Webster
 

Many, many thanks. 

John
NN1SS

On Fri, Oct 25, 2019 at 10:15 AM Michael Walker <va3mw@...> wrote:
Hi All

I took an hour this morning and tested ALL the USA and Canada dx clusters.  I did not test any cluster outside of NA.  Maybe someone else can do that.

This is what works:


If you want to fix this.

  1. Copy the above  list and place it in a text file somewhere you can find 
  2. Open up N1MM and go into the Telnet screen.
  3. Edit Telnet List
  4. Highlight all the entries by holding the left button on the mouse and dragging down to the bottom so they are all in blue.
  5. Hit the delete key and that will delete all your cluster entries.  This will clean out the entire list.  You can keep the ones you like if you know the work
  6. Now, File/Import and select the file you saved in step 1
You now have a very clean and workable list.

Mike va3mw

Re: Working DX Cluster List -- USA and Canada ** Confirmed

Michael Walker
 

Hi Steve

w0mu failed my tests as the Port number was not specified in the list.


You'll see it is missing the 7373

73, Mike va3mw


On Fri, Oct 25, 2019 at 10:41 AM Steve London <n2ic@...> wrote:
W0MU,w0mu.net:7373

has always worked well.

73,
Steve, N2IC

On 10/25/2019 08:33 AM, Larry K8UT wrote:
> Mike,
>
> THANK YOU for testing the North American clusters on the list. If you can supply
> a complete list = Tested_North_American and Untested_Everywhere_Else = I will
> replace the list on the website with your updated list. (send to me as an email
> attach)
>
> And if anyone else wants to volunteer and test those untested from Mike's list
> we can integrate your results into a complete "all tested as of 2019-10-25"
> download file.
>
> While you were testing those we were modifying the documentation for importing a
> list into N1MM+. You will find a new section under >Docs >Windows >Telnet
> Window, "Importing a Downloaded Cluster List"
> https://n1mmwp.hamdocs.com/manual-windows/telnet-window/#importing-a-downloaded-cluster-list
>
> Thanks again,
>
> -larry K8UT
> ------ Original Message ------
> From: "Michael Walker" <va3mw@... <mailto:va3mw@...>>
> To: N1MMLoggerPlus@groups.io <mailto:N1MMLoggerPlus@groups.io>
> Sent: 2019-10-25 10:15:23
> Subject: [N1MM+] Working DX Cluster List -- USA and Canada ** Confirmed
>
>> Hi All
>>
>> I took an hour this morning and tested ALL the USA and Canada dx clusters.  I
>> did not test any cluster outside of NA.  Maybe someone else can do that.
>>
>> This is what works:
>>
>> K1EU,K1EU.DYNIP.COM <http://K1EU.DYNIP.COM>
>> K2LS,DXC.K2LS.COM <http://DXC.K2LS.COM>
>> K7AR,K7AR.NET:7300 <http://K7AR.NET:7300>
>> KN4F,DXC.KN4F.NET <http://DXC.KN4F.NET>
>> N7OD,N7OD.PENTUX.NET <http://N7OD.PENTUX.NET>
>> VA3MW,va3mw.dxcluster.org:41112 <http://va3mw.dxcluster.org:41112>
>> VE3EY-7,DX.FIREROUTE.COM <http://DX.FIREROUTE.COM>
>> VE6TN,DX.MIDDLEBROOK.CA <http://DX.MIDDLEBROOK.CA>
>> VE7CC,VE7CC.NET <http://VE7CC.NET>
>> W1AAA,DXUSA.NET:7300 <http://DXUSA.NET:7300>
>> WF5E,WF5E.NO-IP.COM <http://WF5E.NO-IP.COM>
>> RBN,telnet.reversebeacon.net:7000 <http://telnet.reversebeacon.net:7000>
>> NC7J,dxc.nc7j.com:23 <http://dxc.nc7j.com:23>
>>
>> If you want to fix this.
>>
>>  1. Copy the above  list and place it in a text file somewhere you can find
>>  2. Open up N1MM and go into the Telnet screen.
>>  3. Edit Telnet List
>>  4. Highlight all the entries by holding the left button on the mouse and
>>     dragging down to the bottom so they are all in blue.
>>  5. Hit the delete key and that will delete all your cluster entries.  This
>>     will clean out the entire list.  You can keep the ones you like if you
>>     know the work
>>  6. Now, File/Import and select the file you saved in step 1
>>
>> You now have a very clean and workable list.
>>
>> Mike va3mw
>



Re: Working DX Cluster List -- USA and Canada ** Confirmed

Michael Walker
 

Thanks Larry

It is just a lot of typing for anyone else to try.  You don't have to do it in N1MM. 

 I found it faster to use Windows command prompt.  

Open a command prompt, type in Telnet and then use the 'open' command.  

Example:

open va3mw.dxcluster.org 41112       <--- (you can't use the Colon : that is in the N1MM format)

If it times out, it is dead Jim!

Someone who is quick with Python could script it to check as well, which would be ideal.

I also did NOT test anything that had a hard coded IP address,  I did test 10 of them and none worked, so I deleted the rest.  :)  Sorry if that was you.  If you need a DNS hosting, I can help you out.

73, Mike va3mw

p.s. It is nice to know what works.  I think last year ve7cc had a failure for a bit.




On Fri, Oct 25, 2019 at 10:34 AM Larry K8UT <K8UT@...> wrote:
Mike,

THANK YOU for testing the North American clusters on the list. If you can supply a complete list = Tested_North_American and Untested_Everywhere_Else = I will replace the list on the website with your updated list. (send to me as an email attach)

And if anyone else wants to volunteer and test those untested from Mike's list we can integrate your results into a complete "all tested as of 2019-10-25" download file.

While you were testing those we were modifying the documentation for importing a list into N1MM+. You will find a new section under >Docs >Windows >Telnet Window, "Importing a Downloaded Cluster List"

Thanks again,

-larry K8UT
------ Original Message ------
From: "Michael Walker" <va3mw@...>
Sent: 2019-10-25 10:15:23
Subject: [N1MM+] Working DX Cluster List -- USA and Canada ** Confirmed

Hi All

I took an hour this morning and tested ALL the USA and Canada dx clusters.  I did not test any cluster outside of NA.  Maybe someone else can do that.

This is what works:


If you want to fix this.

  1. Copy the above  list and place it in a text file somewhere you can find 
  2. Open up N1MM and go into the Telnet screen.
  3. Edit Telnet List
  4. Highlight all the entries by holding the left button on the mouse and dragging down to the bottom so they are all in blue.
  5. Hit the delete key and that will delete all your cluster entries.  This will clean out the entire list.  You can keep the ones you like if you know the work
  6. Now, File/Import and select the file you saved in step 1
You now have a very clean and workable list.

Mike va3mw

Re: Working DX Cluster List -- USA and Canada ** Confirmed

Steve London
 

W0MU,w0mu.net:7373

has always worked well.

73,
Steve, N2IC

On 10/25/2019 08:33 AM, Larry K8UT wrote:
Mike,
THANK YOU for testing the North American clusters on the list. If you can supply a complete list = Tested_North_American and Untested_Everywhere_Else = I will replace the list on the website with your updated list. (send to me as an email attach)
And if anyone else wants to volunteer and test those untested from Mike's list we can integrate your results into a complete "all tested as of 2019-10-25" download file.
While you were testing those we were modifying the documentation for importing a list into N1MM+. You will find a new section under >Docs >Windows >Telnet Window, "Importing a Downloaded Cluster List"
https://n1mmwp.hamdocs.com/manual-windows/telnet-window/#importing-a-downloaded-cluster-list
Thanks again,
-larry K8UT
------ Original Message ------
From: "Michael Walker" <va3mw@... <mailto:va3mw@...>>
To: N1MMLoggerPlus@groups.io <mailto:N1MMLoggerPlus@groups.io>
Sent: 2019-10-25 10:15:23
Subject: [N1MM+] Working DX Cluster List -- USA and Canada ** Confirmed

Hi All

I took an hour this morning and tested ALL the USA and Canada dx clusters.  I did not test any cluster outside of NA.  Maybe someone else can do that.

This is what works:

K1EU,K1EU.DYNIP.COM <http://K1EU.DYNIP.COM>
K2LS,DXC.K2LS.COM <http://DXC.K2LS.COM>
K7AR,K7AR.NET:7300 <http://K7AR.NET:7300>
KN4F,DXC.KN4F.NET <http://DXC.KN4F.NET>
N7OD,N7OD.PENTUX.NET <http://N7OD.PENTUX.NET>
VA3MW,va3mw.dxcluster.org:41112 <http://va3mw.dxcluster.org:41112>
VE3EY-7,DX.FIREROUTE.COM <http://DX.FIREROUTE.COM>
VE6TN,DX.MIDDLEBROOK.CA <http://DX.MIDDLEBROOK.CA>
VE7CC,VE7CC.NET <http://VE7CC.NET>
W1AAA,DXUSA.NET:7300 <http://DXUSA.NET:7300>
WF5E,WF5E.NO-IP.COM <http://WF5E.NO-IP.COM>
RBN,telnet.reversebeacon.net:7000 <http://telnet.reversebeacon.net:7000>
NC7J,dxc.nc7j.com:23 <http://dxc.nc7j.com:23>

If you want to fix this.

1. Copy the above  list and place it in a text file somewhere you can find
2. Open up N1MM and go into the Telnet screen.
3. Edit Telnet List
4. Highlight all the entries by holding the left button on the mouse and
dragging down to the bottom so they are all in blue.
5. Hit the delete key and that will delete all your cluster entries.  This
will clean out the entire list.  You can keep the ones you like if you
know the work
6. Now, File/Import and select the file you saved in step 1

You now have a very clean and workable list.

Mike va3mw

Re: Working DX Cluster List -- USA and Canada ** Confirmed

Larry K8UT
 

Mike,

THANK YOU for testing the North American clusters on the list. If you can supply a complete list = Tested_North_American and Untested_Everywhere_Else = I will replace the list on the website with your updated list. (send to me as an email attach)

And if anyone else wants to volunteer and test those untested from Mike's list we can integrate your results into a complete "all tested as of 2019-10-25" download file.

While you were testing those we were modifying the documentation for importing a list into N1MM+. You will find a new section under >Docs >Windows >Telnet Window, "Importing a Downloaded Cluster List"

Thanks again,

-larry K8UT

------ Original Message ------
From: "Michael Walker" <va3mw@...>
Sent: 2019-10-25 10:15:23
Subject: [N1MM+] Working DX Cluster List -- USA and Canada ** Confirmed

Hi All

I took an hour this morning and tested ALL the USA and Canada dx clusters.  I did not test any cluster outside of NA.  Maybe someone else can do that.

This is what works:


If you want to fix this.

  1. Copy the above  list and place it in a text file somewhere you can find 
  2. Open up N1MM and go into the Telnet screen.
  3. Edit Telnet List
  4. Highlight all the entries by holding the left button on the mouse and dragging down to the bottom so they are all in blue.
  5. Hit the delete key and that will delete all your cluster entries.  This will clean out the entire list.  You can keep the ones you like if you know the work
  6. Now, File/Import and select the file you saved in step 1
You now have a very clean and workable list.

Mike va3mw

Re: Call History File for CQ WW SSB

Tim Shoppa
 

Super Check Partial and the Country Files, are for all purposes, the call history file for CQWW.

Between them they contain callsigns of known active contesters, and the rules and exceptions to map callsigns to zones and countries.

The maintainers of these files not only base these on past history, but also include announced special calls and DXpeditions active during CQWW.

You can update them by going to Tools->Download and Install Latest Check Partial File, and Tools->Download and install latest country file.

Tim N3QE


On Fri, Oct 25, 2019 at 9:37 AM David AD4TJ via Groups.Io <ad4tj=yahoo.com@groups.io> wrote:
I don't see a CHF for this weekend's contest. Not needed?

73, David AD4TJ

Working DX Cluster List -- USA and Canada ** Confirmed

Michael Walker
 

Hi All

I took an hour this morning and tested ALL the USA and Canada dx clusters.  I did not test any cluster outside of NA.  Maybe someone else can do that.

This is what works:


If you want to fix this.

  1. Copy the above  list and place it in a text file somewhere you can find 
  2. Open up N1MM and go into the Telnet screen.
  3. Edit Telnet List
  4. Highlight all the entries by holding the left button on the mouse and dragging down to the bottom so they are all in blue.
  5. Hit the delete key and that will delete all your cluster entries.  This will clean out the entire list.  You can keep the ones you like if you know the work
  6. Now, File/Import and select the file you saved in step 1
You now have a very clean and workable list.

Mike va3mw