Date   
CTY-2916 Country Files - 20 November 2019

Jim Reisert AD1C
 

The Country (CTY) Files were updated on 20 November 2019:

http://www.country-files.com/cty-2916-20-november-2019/

For installation instructions, start at:

http://www.country-files.com/

Hover your mouse over the word Contest in the menu, then select the
software you are using.

To install the file, follow the link to your software at the top of the page.

If you are interested in a bigger CTY.DAT for everyday logging, you can get
it here:

http://www.country-files.com/big-cty-20-november-2019/

Note that the release notes (and Version Entity) for this larger file are
different than what is shown below. There is a separate link to them.

As a reminder, there is an RSS feed of the latest country file announcements:

http://www.country-files.com/feed/

Here are the release notes:

20 November 2019 (CTY-2916)
VER20191120, Version entity is Austral Islands, FO/a

Added/changed Entities/Prefixes/Callsigns:

* 3D2AG/P is Rotuma Island, 3D2/r
* 3DA0BP/J is Kingdom of eSwatini, 3DA
* A41HA/ND, A41KJ/ND and A41NN/ND are all Oman, A4
* A61Q/FD is United Arab Emirates, A6
* CE9/SQ1SGB and VP8HAL are both Antarctica, CE9 in ITU zone 73
* EA5EZ/P is Spain, EA
* EA8BFH/P is Canary Islands, EA8
* EA1DFP/9 is Ceuta & Melilla, EA9
* FO/F6BCW is Marquesas Islands, FO/m
* TO9W is St. Martin, FS
* GB0SBG is Northern Ireland, GI
* GB0GDS, GB2CWR and GB2SAS are all Scotland, GM
* 4U25B, II5BP/J and IK6FAW/J are all Italy, I
* N2JNR is United States, K in CQ zone 3, ITU zone 6
* W2IY and W9DKB are both United States, K in CQ zone 4, ITU zone 7
* AE4ED, K4UU, N3RA, NJ4P and NN4NT are all United States, K in CQ zone 4, ITU zone 8
* K9GWS is United States, K in CQ zone 5, ITU zone 8
* AE7CA is Guam, KH2
* K6HNL, KL3JC, KM6UVP and N7ODC are all Hawaii, KH6
* K7VRK, KB4DX, KF4JET, KF7FLL, KF7FLM, KF7KTH and KM4AGL are all Alaska, KL
* LU1DI/D, LU1ELY/D, LU1IG/I, LU1SF/S, LU1UG/U, LU2CDE/D, LU2EE/D,
LU2EGA/D, LU2ENH/D, LU2EPL/D, LU2EPP/D, LU2FGD/J, LU3AYE/D, LU3DAR/D, LU3DEY/D,
LU3DJA/D, LU3DJT/D, LU3ELR/D, LU3FCA/F, LU3FV/F, LU4DGC/D, LU4DLN/D, LU4KC/K,
LU5DA/D, LU5DGR/D, LU5DQ/D, LU5HA/H, LU5HPM/H, LU5QR/Q, LU6EQV/D, LU6EVD/D,
LU7DHE/D, LU7DLN/D, LU7DW/D, LU7EXX/D, LU7KGB/O, LU7YG/F, LU8DY/D, LU8GCJ/GA,
LU8VCC/U, LU9AOS/D, LU9DPI/D, LU9DPI/I, LU9FBA/F, LU9LOP/L, LW1DXH/D, LW1ECE/D,
LW2DKF/D, LW2EQS/D, LW3DAB/D, LW3DED/D, LW3DGC/D, LW3DJC/D, LW3DTD/D, LW3EK/D,
LW5DTD/D, LW5DUS/D, LW6DYZ/D, LW8EGA/D, LW9DTP/D, LW9DTQ/D and LW9EDX/D
are all Argentina, LU
* LU1VDF/V, LU1VYL/V, LU1XAB/V, LU1YJG/V, LU1YY/V, LU2WA/W, LU3YLF/V,
LU5YEC/V, LU6VEK/W, LU8VCC/V and LU8XW/XP are all Argentina, LU in ITU zone 16
* OV4JAM/J is Denmark, OZ
* PA0TLM/J, PA1AW/J, PA1EDL/J, PA1ET/J, PA2RO/J, PA3AFG/J, PA4AGO/J,
PA4WK/J, PA6JAM/J, PA6SHB/J, PA6SJB/J, PA9JAS/J, PC5D/J, PC6RH/J, PE18KA/J,
PE1ORG/J, PE1PEX/J, PE7M/J, PH9GFB/J and PI4VHW/J are all Netherlands, PA
* SV2AEL/J, SV2CLJ/J, SV2JAO/J and SZ4SRM/J are all Greece, SV
* R105DA, R200SB, R9JBF/1, RD0L/3, UA9MA/1 and UA9MA/3 are all European Russia, UA
* R100MTK is European Russia, UA in ITU zone 30
* R1II/P is European Russia, UA in CQ zone 17, ITU zone 20
* RF1A/9 is Asiatic Russia, UA9
* R4YA/8 and RV7B/9 are both Asiatic Russia, UA9 in ITU zone 20
* R100KM and UA0ZDY/9 are both Asiatic Russia, UA9 in CQ zone 18, ITU zone 31
* VE2KK is in ITU zone 9, not ITU zone 4
* VE2KK is in CQ zone 5, not CQ zone 2
* VY2NA/VE2 is Canada, VE in CQ zone 2, ITU zone 4
* VK60LZ is Australia, VK
* HF0ANT is South Shetland Islands, VP8/h

Removed Entities/Prefixes/Callsigns:

* 4U500M in Vienna Intl Ctr, *4U1V
* GB2WAM in Shetland Islands, *GM/s
* 9M4CKT/6 and 9M4CRP/6 in East Malaysia, 9M6
* EA8BFH/4 and EA8BFH/P in Spain, EA
* EA5EZ and EA5EZ/P in Balearic Islands, EA6
* TO019IEEE and TO0MPB in Reunion Island, FR
* GB0WRH, GB2GVC, GB2KDR, GB2OWM, GB2RDR and GB2WAM in Scotland, GM
* GB0SRK in Guernsey, GU
* GB0CTK, GB0VK, GB0WHH, GB2SCC, GB4BIT, GB4OST and GB60ATG in Wales, GW
* 7Z1AL/ND in Saudi Arabia, HZ
* JD1BNA/JD1 in Minami Torishima, JD/m
* AH6AX and WD5F in United States, K
* AA7LE, AK2J, K6KKW, K6MIO, KB7AKQ, N1VOP and W4PRO in Hawaii, KH6
* KD0JJB, KF6RMG, KG7JVJ, N1NDA, N7HRO and N8SUG in Alaska, KL
* K2U, K7V and KB0JRR in Puerto Rico, KP4
* LU2FGD/F, LU3YA/V and LU9FNI/F in Argentina, LU
* 4U500M in Austria, OE
* R0CAF/3, R70MRK, R75YBO, R8MB/1, R9GM/P, R9OM/6, R9YU/3, RA9DF/4/P,
RA9DF/6/P, RA9KD/6, RA9SB/3, RA9WU/6, RN9N/6, RO75RK, RT9K/6, RU9CK/6/P,
RV9CX/6/P, RW9JZ/6, RW9WJ/P, UA9XK/1, UB5O/1 and UE90AGN in European Russia, UA
* UB5O/2 in Kaliningrad, UA2
* R1FW/0, RA4RU/9, RK4PA/9, RV3DSA/0, UB5O/0, UB5O/4, UB5O/8 and UB5O/9
in Asiatic Russia, UA9
* VK3ZK/6, VK3ZK/8, VK5FLEA/6 and VK6MB/3 in Australia, VK
* RI1ANF in South Shetland Islands, VP8/h

73 - Jim AD1C

--
Jim Reisert AD1C, <jjreisert at alum.mit.edu>, http://www.ad1c.us

Re: Faulty Mult recognition in SSB SS

VE9AA - Mike
 

I saw this for 1 mult in SS CW, I had worked VY1AAA , and another VY1 kept popping up red...I think it was VY1CO?

Unlike the USA, we all operate up here where our prefixes indicate our province or territory.

Easy, peasy

cu this w/e guys

Mike VE9AA NB

Re: Faulty Mult recognition in SSB SS

Drew Vonada-Smith K3PA
 

I saw the same thing re Canadian mults.  Worked them all, still saw red.

73,

Drew K3PA

Re: Faulty Mult recognition in SSB SS

Joe WB9SBD
 

Did anyone else have spots that ended up having freqs like in the FT-8 area down in the CW bands?
The box would turn RED in the mult window and if you clicked on it, you would go way down there?
Joe WB9SBD

On 11/19/2019 10:32 PM, Victor Paul wrote:
I noted two issues with multiplier identification.
First, after I had  worked every single Canadian multiplier, N1MM+ flagged VA3WSG in red in my Available Mults and Qs window.  After I cleared it out, I believe another VE3 also came up red in the AMQ window, but that phenomenon eventually stopped.  This isn't the first time I've seen an issue like this with Canadian mults (I seem to recall seeing something similar in one the RAC contests?) and have just lived with it. 

Second, and more concerning is the inverse of the problem above.  On Sunday AM the only mult I lacked was Puerto Rico.  As things had settled down I had the AMQ window set to show mults AND Qs, (not just Mults).  Good thing too, because I saw KP3MM come up, but only in blue.  N1MM+ hadn't recognized it as a needed Puerto Rican multiplier and if I'd left the AMQ window in Mults only mode I would have missed it.   I noticed that N1LN noting the same thing in his 3830 blurb at:

https://www.3830scores.com/showrumor.php?arg=RnaNzpmfcmsvp

Fortunately, I recognized it, swung the beam SE and bagged him.  Maybe the N1MM+ logic isn't set up to recognize KP3 as KP4?

Not a huge deal, but thought the developers would like to know.  Kudos to the N1MM+ team for their outstanding contribution to 21st century contesting.

73,
Victor WB0TEV

Faulty Mult recognition in SSB SS

Victor Paul
 

I noted two issues with multiplier identification.
First, after I had  worked every single Canadian multiplier, N1MM+ flagged VA3WSG in red in my Available Mults and Qs window.  After I cleared it out, I believe another VE3 also came up red in the AMQ window, but that phenomenon eventually stopped.  This isn't the first time I've seen an issue like this with Canadian mults (I seem to recall seeing something similar in one the RAC contests?) and have just lived with it. 

Second, and more concerning is the inverse of the problem above.  On Sunday AM the only mult I lacked was Puerto Rico.  As things had settled down I had the AMQ window set to show mults AND Qs, (not just Mults).  Good thing too, because I saw KP3MM come up, but only in blue.  N1MM+ hadn't recognized it as a needed Puerto Rican multiplier and if I'd left the AMQ window in Mults only mode I would have missed it.   I noticed that N1LN noting the same thing in his 3830 blurb at:

https://www.3830scores.com/showrumor.php?arg=RnaNzpmfcmsvp

Fortunately, I recognized it, swung the beam SE and bagged him.  Maybe the N1MM+ logic isn't set up to recognize KP3 as KP4?

Not a huge deal, but thought the developers would like to know.  Kudos to the N1MM+ team for their outstanding contribution to 21st century contesting.

73,
Victor WB0TEV

Re: N1MM Logger Plus and FT8

ve3ki
 

This is indeed a limitation in the FT8 (or FT4 or JT65 or JT9 or ...) protocol, and not in N1MM+, but it is not as simple as a character count.

FT8 messages are not encoded in ASCII. The data payload in an FT8 message is only 77 bits, and yet it can accommodate a message like KA1ABC DL1ABC JN68, although that message looks to us like 18 characters. In fact, that same message can also be sent in JT65, which has only a 72 bit payload.

The bottom line is that only standard call signs can be sent in the standard message formats. Compound call signs fit into a much more restricted set of message formats, and those don't include grid squares. Consult the WSJT-X documentation (chapters 7 and 17) for more information.

73,
Rich VE3KI

Re: N1MM Logger Plus and FT8

AB2ZY
 

Wasn’t this discussed recently?

 

Not an N1MM issue.  FT8 messages are limited to 13 characters. CQ PJ4/KU8E FK52 is 16 characters.

 

Al

AB2ZY

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Jeff Clarke
Sent: Tuesday, November 19, 2019 9:07 AM
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] N1MM Logger Plus and FT8

 

I've been doing some FT8 from PJ4 since activity is so low on CW during the weekday.

Does anyone know how I get my grid square to send when I call CQ or answer someone? When I call CQ it just sends CQ PJ4/KU8E in the standard messages.

I changed my station data in N1MM Logger Plus and in the WSJT-X window File>Settings> General I have PJ4/KU8E and FK52 for my grid square.

Thanks, Jeff  PJ4/KU8E

N1mm won’t load .....but it has many times before

W6PNG
 

Not sure what I have done but N1mm has worked fine for ages and now throws up an error message when I try to load it.

I’m using windows 10, latest patches on an old MS Surface Pro.

Uninstalling and then reinstalling makes no difference

 

Re: N1MM+ Flex 6000 question

Roland Guidry
 

That is an interesting question. I run Win 7 in Virtualbox on Linux. All works great with programs that use the Flex API or TCP. But N1MM will not recognize the com ports. So can't use N1MM.

Roland

Re: Sweepstakes! Jump to Issue

Joe WB9SBD
 

Morning,

    

Gerald , VE1DT has been working with me off list on this so I don't post so much. After many tries at things, he thought of that last night.  I tried it here at my house this morning and YUP it fixed it! I was waiting to hear from where we actually did SS at to see if it made it work there also before I told everyone here of Geralds suggestion to try.

Thanks Again Gerald!

Joe WB9SBD
W9ET DRIFTLESS ZONE CONTESTERS

On 11/19/2019 5:41 AM, Tim K9WX wrote:
Make sure your graphics card hot key options are disabled before you try to use the N1MM Ctrl+Alt+Up/Down arrow hot keys.  On some PCs, Ctrl+Alt+Down arrow will flip your monitor upside down and you don't want this to happen mid contest.  Don't ask me how I know this.

See this web page for one description of Windows feature: https://www.thewindowsclub.com/screen-upside-down-windows

Beyond that, I find that the N1MM Ctrl+Alt+Up/Down arrow hot keys work as expected in SS SSB.

Tim K9WX

Re: N1MM Logger Plus and FT8

Tim Shoppa
 

Jeff, with “compound callsigns” like PJ4/KU8E in FT8 it is not possible to send grid squares in your CQ.

This is not a M1MM issue, this is an FT8 issue. So further discussion should probably go to a FT8 list.

Tim N3QE

On Nov 19, 2019, at 9:06 AM, Jeff Clarke <ku8e@...> wrote:

I've been doing some FT8 from PJ4 since activity is so low on CW during the weekday.

Does anyone know how I get my grid square to send when I call CQ or answer someone? When I call CQ it just sends CQ PJ4/KU8E in the standard messages.

I changed my station data in N1MM Logger Plus and in the WSJT-X window File>Settings> General I have PJ4/KU8E and FK52 for my grid square.

Thanks, Jeff  PJ4/KU8E

Re: N1MM Logger Plus and FT8

ShelbyK4WW
 

Jeff, I believe that adding the grid square exceeds the number of characters allowed. Try just using PJ2T, along with grid square to test my belief?


On Tue, Nov 19, 2019 at 9:07 AM Jeff Clarke <ku8e@...> wrote:
I've been doing some FT8 from PJ4 since activity is so low on CW during the weekday.

Does anyone know how I get my grid square to send when I call CQ or answer someone? When I call CQ it just sends CQ PJ4/KU8E in the standard messages.

I changed my station data in N1MM Logger Plus and in the WSJT-X window File>Settings> General I have PJ4/KU8E and FK52 for my grid square.

Thanks, Jeff  PJ4/KU8E



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

N1MM Logger Plus and FT8

Jeff Clarke
 

I've been doing some FT8 from PJ4 since activity is so low on CW during the weekday.

Does anyone know how I get my grid square to send when I call CQ or answer someone? When I call CQ it just sends CQ PJ4/KU8E in the standard messages.

I changed my station data in N1MM Logger Plus and in the WSJT-X window File>Settings> General I have PJ4/KU8E and FK52 for my grid square.

Thanks, Jeff  PJ4/KU8E

Kudos

wo4o RiC
 

Just a quick note to thank the development team for making my participation in radiosport much more enjoyable because of the availability of the best (IMO) logging program. Also adding my kudos to all the users who participate in offering ideas for improvement and answers and assistance to help those of us who endeavor to become proficient with operating MM+. Recently had a question about utilizing the W1VE synthesized messages for phone contesting and Joe WB9SBD stepped up to resolve my issue in a matter of minutes. I'd list all the other helpful hams by name and call sign but as initially stated, this was intended to be a 'quick note'.  THANK YOU!
--------------------
73 de RiC wo4o
Grand Island FL

Re: Sweepstakes! Jump to Issue

Tim K9WX
 

Make sure your graphics card hot key options are disabled before you try to use the N1MM Ctrl+Alt+Up/Down arrow hot keys.  On some PCs, Ctrl+Alt+Down arrow will flip your monitor upside down and you don't want this to happen mid contest.  Don't ask me how I know this.

See this web page for one description of Windows feature: https://www.thewindowsclub.com/screen-upside-down-windows

Beyond that, I find that the N1MM Ctrl+Alt+Up/Down arrow hot keys work as expected in SS SSB.

Tim K9WX

Re: TX focus switching problems with Flex 6600M

Larry K8UT
 

>Has anyone ever experimented?
As KU7T suggested, you can run some ping tests to the radio but in a local LAN situation the turnaround time will be very short - less than a millisecond.

To answer your question - Yes, The Dev Team has experimented when comparing the delivery speeds of serial cat comms versus tcp/udp packet transmissions. Delivery times were measured from a program mouse click to arrival at the destination device. IIRC the packets were delivered in 10 - 20 milliseconds. If you're experiencing problems with Lead/Tail times set at 200ms, network latency is not likely to be the villain.

-larry K8UT

------ Original Message ------
From: "Grant Kesselring" <kesselg75@...>
Sent: 2019-11-19 01:27:51
Subject: Re: [N1MM+] TX focus switching problems with Flex 6600M

After operating for the entire Sweepstakes SSB contest this weekend, I only saw the "attempt to change TX antenna while transmitting" maybe one or two times.  However, I did have Radio Swap Transmit Lead/Tail times set at 200ms.  I purposefully set these delay time longer to prevent any problems.  However, there were times during operation where I noticed this radio swap delay, and would have preferred it to be shorter.

In my setup, I have the Flex6600M cabled to the PC running N1MM+ through a Netgear Nighthawk X6 router.  My question is: would it be better from a radio swapping latency perspective if the FlexRadio was connected directly to the PC running the software (ie, remove the router)?  The router itself is just a few months old so I have no reason to suspect problems with it.  However, it seems like a piece of hardware that could potentially be causing latency in the system.  Has anyone ever experimented?

Re: TX focus switching problems with Flex 6600M

Jamie WW3S
 

FWIW, I had a 6600, separate Maestro...bought it mainly because it’s marketed as SO2R in the box.....I never could solve the TX switching problem.....mainly used on RTTY and cqing on two bands was difficult.....when it worked, it worked well, but when it didn’t, well you know that story.....sometimes I could go for a few hours, no hiccups, sometimes three times in ten minutes....I guess my point is, it’s not the network....


On Nov 19, 2019, at 1:27 AM, Grant Kesselring <kesselg75@...> wrote:

After operating for the entire Sweepstakes SSB contest this weekend, I only saw the "attempt to change TX antenna while transmitting" maybe one or two times.  However, I did have Radio Swap Transmit Lead/Tail times set at 200ms.  I purposefully set these delay time longer to prevent any problems.  However, there were times during operation where I noticed this radio swap delay, and would have preferred it to be shorter.

In my setup, I have the Flex6600M cabled to the PC running N1MM+ through a Netgear Nighthawk X6 router.  My question is: would it be better from a radio swapping latency perspective if the FlexRadio was connected directly to the PC running the software (ie, remove the router)?  The router itself is just a few months old so I have no reason to suspect problems with it.  However, it seems like a piece of hardware that could potentially be causing latency in the system.  Has anyone ever experimented?

Re: TX focus switching problems with Flex 6600M

Andy (KU7T)
 

Unlikely. You can run a ping to your radio and it's likely 1ms or less. If its much longer your network is having issues.

You could try to reduce the 200ms a little but still keep it stable.

Remember, N1MM+ treats the 6600M like two generic CAT radios.  It seems to need more time to switch...

Andy
KU7T

Sent from my T-Mobile 4G LTE Device


From: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io> on behalf of Grant Kesselring <kesselg75@...>
Sent: Monday, November 18, 2019 10:27:51 PM
To: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io>
Subject: Re: [N1MM+] TX focus switching problems with Flex 6600M
 
After operating for the entire Sweepstakes SSB contest this weekend, I only saw the "attempt to change TX antenna while transmitting" maybe one or two times.  However, I did have Radio Swap Transmit Lead/Tail times set at 200ms.  I purposefully set these delay time longer to prevent any problems.  However, there were times during operation where I noticed this radio swap delay, and would have preferred it to be shorter.

In my setup, I have the Flex6600M cabled to the PC running N1MM+ through a Netgear Nighthawk X6 router.  My question is: would it be better from a radio swapping latency perspective if the FlexRadio was connected directly to the PC running the software (ie, remove the router)?  The router itself is just a few months old so I have no reason to suspect problems with it.  However, it seems like a piece of hardware that could potentially be causing latency in the system.  Has anyone ever experimented?

Re: TX focus switching problems with Flex 6600M

Grant Kesselring
 

After operating for the entire Sweepstakes SSB contest this weekend, I only saw the "attempt to change TX antenna while transmitting" maybe one or two times.  However, I did have Radio Swap Transmit Lead/Tail times set at 200ms.  I purposefully set these delay time longer to prevent any problems.  However, there were times during operation where I noticed this radio swap delay, and would have preferred it to be shorter.

In my setup, I have the Flex6600M cabled to the PC running N1MM+ through a Netgear Nighthawk X6 router.  My question is: would it be better from a radio swapping latency perspective if the FlexRadio was connected directly to the PC running the software (ie, remove the router)?  The router itself is just a few months old so I have no reason to suspect problems with it.  However, it seems like a piece of hardware that could potentially be causing latency in the system.  Has anyone ever experimented?

Re: Sweepstakes! Jump to Issue

danzee
 

Tim, i found that issuing a telent data refresh fixed the taht problem. 



Sent from my Verizon, Samsung Galaxy smartphone

-------- Original message --------
From: Tim Shoppa <tshoppa@...>
Date: 11/18/19 2:43 PM (GMT-05:00)
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] Sweepstakes! Jump to Issue

Mike, historically N1MM has never worked for me in SS or NAQP in showing what are trivially new Canadian mults.

Like you point out it does the wrong the other way too. Like you, even after I had worked VY1AAA, it kept on showing VY1CO as a new mult. There were other Canadian calls that were trivially new mults that don't get lit up.

After I get the callsign into the entry window and space or tab over to the exchange, it lights up as a mult accurately.

I think this is some bad interaction between history file and the trivial callsign to mult mapping but I never have figured it out. Just lived with it for many many years now.

Tim N3QE

Tim N3QE

On Mon, Nov 18, 2019 at 1:23 PM VE9AA - Mike <ve9aa@...> wrote:
I didn't work the SS SSB this past weekend, but did work the SS CW and did unlimited, the "83Q/83Mults" thing.

Pretty much all I did was CTRL-ALT-UP/DN arrows and barely tuned around at all and it worked perfectly at that time.

The only issue I found in SS CW was that , even though I had already worked VY1AAA early on, it kept reporting another VY1 as a mult.
Since it was only one stn, it was easy to ignore.

The jump to the next mult thing worked fine how (in SS CW)...