Date   
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

Re: How to record frequency in manual mode

John Bednar
 


For cqww with a non interfaced radio only the band is important.  Don't fuss with entering the exact frequency. 

Interfacing the ic7300 is easy. Install the icom driver, connect a usb cable, follow the icom setup instructions in the Additional Files section of the web page. You can use the ic7300 radio codec for on the fly voice record & playback messages. 

John, K3CT 




-------- Original message --------
From: ve3ki <ve3iay@...>
Date: 10/25/19 9:00 AM (GMT-05:00)
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] How to record frequency in manual mode

Type the frequency (in kHz) into the call sign box in the Entry window and press the Enter key. The frequency in the title bar will change to the frequency you typed in, and that is the frequency that will be logged. You can do the same with the mode, e.g. type SSB or CW into the call sign box and press the Enter key to change the program's logging mode.

73,
Rich VE3KI

On Fri, Oct 25, 2019 at 08:56 AM, <hp1stb@...> wrote:
I'm a new N1MM user (and fairly new ham) and am having issues with connecting my Icom 7300.  While I'm sorting this out, I still want to participate in the CQ WW SSB contest this weekend, so my fallback position will be to manually log QSOs.  However, the entry page does not seem to allow for input of FREQUENCY.  How can I enter this?
Thx

Call History File for CQ WW SSB

David AD4TJ
 

I don't see a CHF for this weekend's contest. Not needed?

73, David AD4TJ

Re: How to record frequency in manual mode

NS2N_PTA@...
 

One other point ... the frequency need only show the band the operation is taking place .... eg., 14200 for all 20m SSB contacts. The exact frequency is only necessary if you are competing for World or Continental awards.

Paul NS2N


From: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io> on behalf of ve3ki <ve3iay@...>
Sent: Friday, October 25, 2019 9:00:05 AM
To: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io>
Subject: Re: [N1MM+] How to record frequency in manual mode
 
Type the frequency (in kHz) into the call sign box in the Entry window and press the Enter key. The frequency in the title bar will change to the frequency you typed in, and that is the frequency that will be logged. You can do the same with the mode, e.g. type SSB or CW into the call sign box and press the Enter key to change the program's logging mode.

73,
Rich VE3KI

On Fri, Oct 25, 2019 at 08:56 AM, <hp1stb@...> wrote:
I'm a new N1MM user (and fairly new ham) and am having issues with connecting my Icom 7300.  While I'm sorting this out, I still want to participate in the CQ WW SSB contest this weekend, so my fallback position will be to manually log QSOs.  However, the entry page does not seem to allow for input of FREQUENCY.  How can I enter this?
Thx

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

Pete Smith
 

Also be sure you are using a current wl_cty.dat file.  Just taking Antarctica as an example, the file says:

Antarctica:               13:  74:  SA:  -90.00:     0.00:     0.0:  CE9:
    3Y[73],AX0(39)[69],AY1Z[73],AY2Z[73],AY3Z[73],AY4Z[73],AY5Z[73],AY6Z[73],
    AY7Z[73],AY8Z[73],AY9Z[73],FT0Y(30)[70],FT1Y(30)[70],FT2Y(30)[70],
    FT3Y(30)[70],FT4Y(30)[70],FT5Y(30)[70],FT6Y(30)[70],FT7Y(30)[70],
    FT8Y(30)[70],LU1Z[73],LU2Z[73],LU3Z[73],LU4Z[73],LU5Z[73],LU6Z[73],
    LU7Z[73],LU8Z[73],LU9Z[73],RI1AN(29)[69],VI0(39)[69],VK0(39)[69],
    ZL5(30)[71],ZM5(30)[71],ZS7(38)[67],=8J1RL(39)[67],=DP0GVN(38)[67],
    =DP1POL(38)[67],=EM1U[73],=EM1UA[73],=IA0/IZ1KHY/P(29)[70],=KC4AAA(39),
    =KC4AAC[73],=KC4USB(12),=KC4USV(30)[71],=RI1ANC(29)[70],=RI1ANZ(39)[69],
    =VP8AL[73],=VP8CTR[73];

The first line is the default for the "country." Exceptions  with "=" are full callsigns, CQ zones are in "()" and IARU zones in "[]".  As you can see, AD1C tries hard to keep up with the exceptions.  and of course you can always change the prefilled zone depending on what you copy.  Pity the poor non-US competitors, who have to contend with our many, many exceptions!

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 3:39 AM, Tom Owens via Groups.Io wrote:

N1MM – Potential Issue Logging Certain Calls In CQWW Contents (Other as Well)

 

Testing some stuff before the CQ WW DX SSB Contest tomorrow.  I believe there are some problems.

 

ONE.

CE9 can be in Zone 12, 13, 29, 30, 32 and 39

In each case the country is Antarctica

Logging CE9ABC should go in as CE9 Antarctica

Logging that call does populate the correct zone, depending on what is entered in the zone field.

However, it does NOT show up as CE9 in the Countries window, or anything as far as I can tell.

 

TWO

VK9 call signs.  No way I can find to correct the error if calls are logged as the wrong country.

For example, zone 29 can be:  Cocos-Keeling or Christmas Island.  If other that C or X are the first letter in the suffice all bets are off for what county is going to be identified in the countries window.  And the Edit Contact window does not allow changing an incorrect country to the correct country.

 

Same issue applies to zone 30, which can also have different countries:  Lord Howe Island, Mellish Reef, and Willis Island.

 

THREE

VP8 callsigns.  All are in zone 13 but can be:  Falkland Islands, South Georgia, South Orkney, South Sandwich or South Shetland.  Again, there does not appear to me to be a way to correct an incorrect entry.  When we work a VP8 we always ask what country there are in so that it can be logged correctly.

 

Same comment about asking the operator what country he is in applies to zones 29 and 30 as well.

 

FOUR

JW can be: JW-S Svalbard or JW/b Bear Island.  Again, when working a JW station we ask which country they are in so we can log it correctly.  N1MM does not appear to have a way to append the /b for Bear Island.

 

I have suggestions on how to address these issues if the program team is interested.

Re: How to record frequency in manual mode

ve3ki
 

Type the frequency (in kHz) into the call sign box in the Entry window and press the Enter key. The frequency in the title bar will change to the frequency you typed in, and that is the frequency that will be logged. You can do the same with the mode, e.g. type SSB or CW into the call sign box and press the Enter key to change the program's logging mode.

73,
Rich VE3KI


On Fri, Oct 25, 2019 at 08:56 AM, <hp1stb@...> wrote:
I'm a new N1MM user (and fairly new ham) and am having issues with connecting my Icom 7300.  While I'm sorting this out, I still want to participate in the CQ WW SSB contest this weekend, so my fallback position will be to manually log QSOs.  However, the entry page does not seem to allow for input of FREQUENCY.  How can I enter this?
Thx

How to record frequency in manual mode

Steve Barnett
 

I'm a new N1MM user (and fairly new ham) and am having issues with connecting my Icom 7300.  While I'm sorting this out, I still want to participate in the CQ WW SSB contest this weekend, so my fallback position will be to manually log QSOs.  However, the entry page does not seem to allow for input of FREQUENCY.  How can I enter this?
Thx

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

John Bednar
 

Tom,

If needed, users change the zone that come from the country file before logging the qso.

The logged qso zone can be changed after logging an entry mistake occurs. 

John, K3CT 

-------- Original message --------
From: "Tom Owens via Groups.Io" <exk7rsc@...>
Date: 10/25/19 3:39 AM (GMT-05:00)
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] Potential Logging Issues For 2019 CW WW DX SSB Contest

N1MM – Potential Issue Logging Certain Calls In CQWW Contents (Other as Well)

 

Testing some stuff before the CQ WW DX SSB Contest tomorrow.  I believe there are some problems.

 

ONE.

CE9 can be in Zone 12, 13, 29, 30, 32 and 39

In each case the country is Antarctica

Logging CE9ABC should go in as CE9 Antarctica

Logging that call does populate the correct zone, depending on what is entered in the zone field

However, it does NOT show up as CE9 in the Countries window, or anything as far as I can tell.

 

TWO

VK9 call signs.  No way I can find to correct the error if calls are logged as the wrong country.

For example, zone 29 can be:  Cocos-Keeling or Christmas Island.  If other that C or X are the first letter in the suffice all bets are off for what county is going to be identified in the countries window.  And the Edit Contact window does not allow changing an incorrect country to the correct country.

 

Same issue applies to zone 30, which can also have different countries:  Lord Howe Island, Mellish Reef, and Willis Island.

 

THREE

VP8 callsigns.  All are in zone 13 but can be:  Falkland Islands, South Georgia, South Orkney, South Sandwich or South Shetland.  Again, there does not appear to me to be a way to correct an incorrect entry.  When we work a VP8 we always ask what country there are in so that it can be logged correctly.

 

Same comment about asking the operator what country he is in applies to zones 29 and 30 as well.

 

FOUR

JW can be: JW-S Svalbard or JW/b Bear Island.  Again, when working a JW station we ask which country they are in so we can log it correctly.  N1MM does not appear to have a way to append the /b for Bear Island.

 

I have suggestions on how to address these issues if the program team is interested.

Re: Telenet setup

Jim W7RY
 

So is:

ws7i.ewarg.org:7300

Always on the air and reliable. A CC Cluster.


Thanks
73
Jim W7RY





On 10/25/2019 6:14 AM, Michael Walker wrote:

Mine is up 100% of the time. 

Va3mw-7

Va3mw.dxcluster.org
Port 41112

Mike

On Oct 25, 2019, at 3:13 AM, Clay N9IO <n9io@...> wrote:


VE7CC is the go to cluster you can always rely on.
Clay N9IO

Sent from my Verizon, Samsung Galaxy smartphone


From: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io> on behalf of Jim W7RY <jimw7ry@...>
Sent: Tuesday, October 22, 2019 8:31:15 PM
To: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io>
Subject: Re: [N1MM+] Telenet setup
 
WS7I works well. Its a CC cluster.



Thanks
73
Jim W7RY
On 10/22/2019 2:24 PM, Dave Sublette wrote:
Just tried wb4qoj--NO LUCK.  So far only VE7CC works

K4TO


On Tue, Oct 22, 2019 at 3:15 PM Ed W2LCQ via Groups.Io <w2lcq=yahoo.com@groups.io> wrote:
I use NC7J with N1MM+

 http://dxc.nc7j.com:7373/

73, Ed Jones W2LCQ

CWops 701 - SKCC 5474C - FISTS 12294
             —-Frankford Radio Club—-






On Oct 22, 2019, at 11:07 AM, Dave Sublette <k4to.dave@...> wrote:


I was able to connect to VE7CC.  I guess all the ones on the list are pretty much duds.  Thanks for the help.

73,

Dave, K4TO

On Tue, Oct 22, 2019 at 4:01 AM ShelbyK4WW <shelbyk4ww@...> wrote:
Dave, I use W9PA.....dxc.w9pa.net

On Tue, Oct 22, 2019 at 1:47 AM Dave Sublette <k4to.dave@...> wrote:

Dave Sublette <k4to.dave@...>

10:12 PM (55 minutes ago)

to N1MMLoggerPlus
I have used N1MM for several years, but have never tried to connect to a cluster.  Tonight I tried, without success, to connect to several on the list of clusters.  I am in Kentucky.  Is there a cluster that I can connect to that will give me useful spots? I've been trying to read the manual and see if there is something about the setup that I need to do, but no luck so far.

 thanks,

Dave, K4TO


--
73, Shelby - K4WW
As I don't have an iPad nor iPhone, sent from my PC


Re: Telenet setup

Michael Walker
 

Mine is up 100% of the time. 

Va3mw-7

Va3mw.dxcluster.org
Port 41112

Mike

On Oct 25, 2019, at 3:13 AM, Clay N9IO <n9io@...> wrote:


VE7CC is the go to cluster you can always rely on.
Clay N9IO

Sent from my Verizon, Samsung Galaxy smartphone


From: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io> on behalf of Jim W7RY <jimw7ry@...>
Sent: Tuesday, October 22, 2019 8:31:15 PM
To: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io>
Subject: Re: [N1MM+] Telenet setup
 
WS7I works well. Its a CC cluster.



Thanks
73
Jim W7RY
On 10/22/2019 2:24 PM, Dave Sublette wrote:
Just tried wb4qoj--NO LUCK.  So far only VE7CC works

K4TO


On Tue, Oct 22, 2019 at 3:15 PM Ed W2LCQ via Groups.Io <w2lcq=yahoo.com@groups.io> wrote:
I use NC7J with N1MM+

 http://dxc.nc7j.com:7373/

73, Ed Jones W2LCQ

CWops 701 - SKCC 5474C - FISTS 12294
             —-Frankford Radio Club—-






On Oct 22, 2019, at 11:07 AM, Dave Sublette <k4to.dave@...> wrote:


I was able to connect to VE7CC.  I guess all the ones on the list are pretty much duds.  Thanks for the help.

73,

Dave, K4TO

On Tue, Oct 22, 2019 at 4:01 AM ShelbyK4WW <shelbyk4ww@...> wrote:
Dave, I use W9PA.....dxc.w9pa.net

On Tue, Oct 22, 2019 at 1:47 AM Dave Sublette <k4to.dave@...> wrote:

Dave Sublette <k4to.dave@...>

10:12 PM (55 minutes ago)

to N1MMLoggerPlus
I have used N1MM for several years, but have never tried to connect to a cluster.  Tonight I tried, without success, to connect to several on the list of clusters.  I am in Kentucky.  Is there a cluster that I can connect to that will give me useful spots? I've been trying to read the manual and see if there is something about the setup that I need to do, but no luck so far.

 thanks,

Dave, K4TO


--
73, Shelby - K4WW
As I don't have an iPad nor iPhone, sent from my PC

Re: Telnet question

Dave Sublette <k4to.dave@...>
 

Thanks Larry,

This hound isn't chasing that Fox.  I prefer CW. I have no axe to grind with the digital modes.  They will probably be the salvation of ham radio in whatever form it survives.  

73,

Dave, K4TO

On Fri, Oct 25, 2019 at 5:27 AM Larry K8UT <K8UT@...> wrote:
Those are spots for the new - and very popular - FT8 digital mode. In that mode, there is a sophisticated split method for rare stations and DXpeditions to operate using Fox & Hounds mode, typically abbreviated as F/H.

You have lots of catching up to do!

-larry K8UT

------ Original Message ------
From: "Dave Sublette" <k4to.dave@...>
Sent: 2019-10-25 05:20:27
Subject: [N1MM+] Telnet question

I have been away from the Telnet scene for several years and have just started watching  it again.  I keep seeing F/H in the comments.  What does this mean?

Thanks,

Dave, K4TO

Re: Telnet question

John H. Long Jr.
 

F/H stands for Fox Hound.
When a dxpedition is using FT8 digital mode they are the Fox and we are the Hounds seaking them.

The software package WSJT-X gives them the ability to have multiple digital qso's at the same time improving their qso rate.

John
KW7A 




Sent from my Verizon, Samsung Galaxy smartphone

-------- Original message --------
From: Dave Sublette <k4to.dave@...>
Date: 10/25/19 3:20 AM (GMT-07:00)
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] Telnet question

I have been away from the Telnet scene for several years and have just started watching  it again.  I keep seeing F/H in the comments.  What does this mean?

Thanks,

Dave, K4TO

Re: Telnet question

Larry K8UT
 

Those are spots for the new - and very popular - FT8 digital mode. In that mode, there is a sophisticated split method for rare stations and DXpeditions to operate using Fox & Hounds mode, typically abbreviated as F/H.

You have lots of catching up to do!

-larry K8UT

------ Original Message ------
From: "Dave Sublette" <k4to.dave@...>
Sent: 2019-10-25 05:20:27
Subject: [N1MM+] Telnet question

I have been away from the Telnet scene for several years and have just started watching  it again.  I keep seeing F/H in the comments.  What does this mean?

Thanks,

Dave, K4TO