Date   
Re: Spectrum display - Icom 7300 #IC7300 #spectrum

Rob Cichocki
 

Working, many thanks. :)

CTY-2804 Country Files - 01 March 2018

Jim Reisert AD1C
 

The Country (CTY) Files were updated on 01 March 2018:

http://www.country-files.com/cty-2804-01-march-2018/

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-01-march-2018/

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.

Here are the release notes:

1 March 2018 (CTY-2804)
VER20180301, Version entity is Wallis & Futuna Islands, FW

Added/changed Entities/Prefixes/Callsigns:

* VP8ROT is Antarctica, CE9 in ITU zone 73
* TO972A is Martinique, FM
* GB0SPD and GB106TBC are both Northern Ireland, GI
* GB0PGG, GB1LW and GB4UKG are all Wales, GW
* AJ8HT, NH0Z, W6CWJ and W8AYD are all Hawaii, KH6
* K8OUA is Alaska, KL
* N1A is Puerto Rico, KP4
* LU1DBI/D, LU1EPC/D, LU1JAR/J, LU2DT/D, LU3DRP/D, LU3DXG/D, LU4AAO/D,
LU4FM/F, LU5ALS/D, LU5DMP/D, LU5DTF/D, LU5DUC/D, LU5DYT/D, LU5JCL/J, LU6DM/D,
LU7QN/Q, LU8DCH/D, LU9ERA/H, LU9EV/D, LW6DLS/D, LW6EXM/D, LW8DAL/D, LW8EFR/D,
LW9ECR/D and LW9EZX/D are all Argentina, LU
* LU1WL/W, LU1XA/XA, LU2VA/V, LU2VCS/V, LU2WA/W, LU2WC/W, LU3WAM/W,
LU3XEI/XA, LU3YK/W, LU5YF/Y, LU6WG/W, LU7WFM/W, LU7YG/Y and LU8YE/Y are all Argentina, LU in ITU zone 16
* R1943BK, R1989A, R8FF/6, RT9K/6/P, UA0JL/6, UE23DKA, UE23DSA, UE95AE,
UE95E, UE95GA and UE95ME are all European Russia, UA
* R9SAO/1 is European Russia, UA in ITU zone 20
* R3XA/2 and RA3XM/2 are both Kaliningrad, UA2
* RA0QK/8 is Asiatic Russia, UA9
* RA4RU/9/P, RK6YM/8, RQ0C/8 and UA6WIO/9 are all Asiatic Russia, UA9 in ITU zone 20
* R9PS/0, RW3YC/9 and UE23DZO are all Asiatic Russia, UA9 in CQ zone 18, ITU zone 32
* UR5KGG/WAP and UT1KY/WAP are both Ukraine, UR
* VK5MAV/9 is Australia, VK in ITU zone 55

Removed Entities/Prefixes/Callsigns:

* EA1RCI/YOA, EA5URE/P and EA9PD/P in Spain, EA
* ET3AA/YOTA in Ethiopia, ET
* 4U24OCT and 4U7F in Italy, I
* JE1LET/VK3SS and JE1XUZ/YOTA in Japan, JA
* KD0PZ, N0KQ, NH7AA and W4II in United States, K
* N0J in Mariana Islands, KH0
* K3UNS, K8EUT, KB7G, KE7IZS, KF4OOB, KO4RR and N7AMY in Hawaii, KH6
* KB7JA, KE5GEB, KE5NLG, KE7KYU, KH7DA, N0XS and W2KRZ in Alaska, KL
* KN4IGP, KN4ILO and KN4INP in Puerto Rico, KP4
* LU7DZV/D in Argentina, LU
* R300AG, R8MB/1, RK3DWA/3/N, RT9T/1, RW9W/3, RX3XX/N, UB5O/1 and UE80S
in European Russia, UA
* UB5O/2 in Kaliningrad, UA2
* R7LZ/0, R7LZ/9, RAEM, RL5G/9, RN3QOP/9, RU5D/8, RU9SO/4, RZ5D/9,
UB5O/0, UE18M, UE18U and UE18Z in Asiatic Russia, UA9
* CF2RC and CF2VVV in Canada, VE
* VK6AV/4 in Australia, VK

73 - Jim AD1C

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

Is the N1mm+ website down?

Goetz DJ3IW
 

Since several hours it's not possible to get onto the N1mm+ website.

73 de Goetz DJ3IW

Re: Is the N1mm+ website down?

Tom - N1MM
 

Both the web site and the email forwarder are up.  We are moderating all posts so that people don't see 3500 test messages.  I deleted your duplicate post on this topic.

Re: Is the N1mm+ website down?

Goetz DJ3IW
 

Must be a big problem somewhere betwwen NA and EU.
I do NOT get any mails tothe list - had to log in to groups.io (works) to see and read your reply.
73 de Goetz DJ3IW

My K3

Tommy <aldermant@...>
 

Seems to be working gooder??

 

Tom – W4BQF

 

 

 

N1MM+ Flex 6000 question

Chris Tate - N6WM
 

has there been any discussion about adding api support for the flex 6000 series transceivers?  We are able to interface via their cat application, but things like band changes via CAT FA commands have different results in a transceiver that can, say spawn multiple radios in 1 panadapter. etc.  for instance a direct frequency entry sends an FA, will call a qrg, but not necessarily bring all the settings over like an API induced band change.  This is different functionality than on a superhet. other logging platforms have implemented this interface.. but "I likes my N1MM" ;-) and hope something like this can be done here

Chris
N6WM


From: N1MMLoggerPlus@groups.io [N1MMLoggerPlus@groups.io] on behalf of ve3ki [ve3iay@...]
Sent: Wednesday, February 28, 2018 4:14 PM
To: N1MMLoggerPlus@groups.io
Subject: [N1MMLoggerPlus] N1MMLoggerPlus group guidelines

Welcome to the N1MMLoggerPlus user group at groups.io .
 
The purpose of this group is to serve as the main support channel and discussion group for the N1MM Logger+ amateur radio contest logging program.
 
N1MM Logger+ (aka N1MM+) is free contesting software that supports virtually all amateur radio contests. If a contest is not supported now, it can usually be added using the Logger's "user-defined contest" feature. N1MM+ is not a general-purpose logger; there is no support for chasing awards like DXCC and WAS, and there are no QSL management features. For those functions, you should be using a general logging program. You can export contest logs from N1MM+ in ADIF format and import them into almost any general logging program for tracking awards and generating QSLs.
 
You need to join the group in order to post messages. The first posting from a new user must be approved by the moderators. Include your callsign in requests to join. Be proud of your callsign and put it in every post.
 
Don't spam. This is not a list for posting items for sale, for announcing contests or events, for discussing amateur politics or for other off topic posts. It is also not the place for personal attacks. Repeated or egregious violations will result in loss of posting privileges.
 
If the volume of email from the group is too much, you can set your delivery to digests or no email, by signing in to the groups.io web site and selecting "Your Groups > Manage My Subscriptions". You can also change your account preferences by clicking on your account name at the top right. You can change your email address or add an email alias address from the same place.
 
You can view messages on the web site either in chronological order or by topic. Attachments are not conveyed in messages, but the web site also has a Files area to which files and screen shots may be uploaded. 
 
Try to make the subject line of your postings meaningful and descriptive. If you are starting a new topic, don't post it as a follow-up to a different thread; start a new thread with a title appropriate to the new topic. Titles such as "N1MM+" or "Bug report" do not make the grade; they give the reader inadequate indication of the contents, and they result in discussions on different topics being combined into a single thread.
 
When reporting a problem with N1MM+, make sure that you can reproduce it using the current (latest) version of the program. We don't support any but the latest version. Please be specific when describing a problem. Be sure to indicate the mode (CW, SSB, RTTY, etc.), the method you use for interfacing (keying interface, sound card interface, etc.), the contest, the radio type and how it is connected to the computer, and information about your computer and its operating system. If there is an error message, quote its contents; just saying you got an error message without any other identifying information is not likely to get you a helpful response.
 
If you are using port sharing software (LP-Bridge, VSPE, etc.), try to reproduce the problem without it first. We don't support port sharing software, but you are welcome to ask the group for advice about using it with N1MM+.
 
Read all the posts in a topic before posting a response. If a post already says what you were going to say, don't clutter up the list with a "me too" post. When posting a response, it is a good idea to include just enough of the previous discussion to identify the context, and no more. There is no need to quote the entire past history of the thread in every response.
 
After posting a problem, check back for responses. It is rude to post a problem then disappear. Likewise, please do not ask for off-list responses. If your post was important enough to ask 3,500 people to read it, you owe it to them to let them see the responses. If the responses solve your problem, let the group know how your problem was solved; that may help someone else down the road.
 
Please do not think of this group as only a place for you to get answers to your problems, but also as a place where you can help others with their problems. If someone else has a problem hat you know how to fix, feel free to respond and provide the solution. The success of the group  depends on more than just responses from the N1MM development team. However, when you do not know the answer, don't waste everybody's time with meaningless responses like "gee, that's a tough one. I have no idea."
 
Above all, think before posting. You are going before 3,500 people with your posting. If you want help, demonstrate your willingness to do your part of the work. Be polite.
 
73,
The N1MM Logger+ Development Team
 

New Super Check Partial files available VER20180301 (01 MAR 2018)

Stu K6TU
 

A New release of the Super Check Partial database files is available at:

http://www.supercheckpartial.com

Calls in the MASTER.DTA file: 42,070

If you would like to contribute your CABRILLO format logs for the SCP database, please send them at any time.

The easiest thing to do is to bcc the following email address:

logs@...

...when you submit your log to the sponsor’s robot after each contest.

Please DO NOT send ADIF files!

You can send more than one log attachment in a single email BUT PLEASE DON’T SEND THEM IN A ZIP file!

If you want to check the version of the SCP files you are using, look for a call beginning with “VER2". Every SCP file includes the version number in the list of calls in the format VERYYYYMMDD.

The next release of the database will be at the beginning of April 2018. Any requested changes or deletions of callsigns received by NOON PST on April 1st, 2018 will be included in that release. Please send requests to logs@....

PLEASE MAKE SURE TO SEND ADD/CHANGE MESSAGES WITHOUT ATTACHED LOGS OTHERWISE I PROBABLY WON’T SEE YOUR REQUEST due to the email processing robot.

Please let me know if you find any bad calls in the files.
Thanks again to all the contributors!
Stu K6TU

Advanced Voicing Troubles

Dave Malley, W1VEM
 

I thot I had this figured out for ARRL DX SSB but not quite.  The program will voice callsigns but will not voice the F2 report.   My latest attempt for these parts of the message file has F2  My Rpt,{OPERATOR}\#  and F5  (His Call),!.  The Configurer’s Letters Wav path is {OPERATOR}\ .  The path to the regular wave files is Logger+/wav/W1VEM and the letters & number files are in Logger+/wav/LettersFiles\W1VEM.  Any suggestion of what’s wrong would be great!

 

Thx & 73,

Dave, W1VEM

No nbr increase

VE2FK
 

Wanted to test RTTY in NS tonight using nsrttydupe module
and did not had number increase.

73, Claude VE2FK

Re: Advanced Voicing Troubles

ve3ki
 

{OPERATOR}\# is the wrong syntax. The correct syntax is just #. The per-operator part is handled by putting the {OPERATOR} macro in the DVK Letters file path in the Configurer under the Other tab.

For more information on this, see the manual section on the Configurer (<http://n1mm.hamdocs.com/tiki-index.php?page=Configurer&structure=N1MM+Logger+Documentation#Other_Tab_Field_descriptions>), the section on function key messages (<http://n1mm.hamdocs.com/tiki-index.php?page=Stored+Messages+and+the+Function+Key+Message+Editor&structure=N1MM+Logger+Documentation#The_Operator_Macro>), and the section on Macros where the # macro is described (<http://n1mm.hamdocs.com/tiki-index.php?page=Macros&structure=N1MM+Logger+Documentation#General_Macros>).

73,
Rich VE3KI

Re: No nbr increase

Steve London
 

What version ?

73,
Steve, N2IC

On 03/01/2018 06:55 PM, ve2fk wrote:
Wanted to test RTTY in NS tonight using nsrttydupe module
and did not had number increase.
73, Claude VE2FK

Re: No nbr increase

VE2FK
 

Latest version

Le 2018-03-01 à 21:14, Steve London a écrit :
What version ?

73,
Steve, N2IC

On 03/01/2018 06:55 PM, ve2fk wrote:
Wanted to test RTTY in NS tonight using nsrttydupe module
and did not had number increase.

73, Claude VE2FK




-----
Aucun virus trouve dans ce message.
Analyse effectuee par AVG - www.avg.fr
Version: 2016.0.7226 / Base de donnees virale: 4793/15442 - Date: 01/03/2018

Re: No nbr increase

VE2FK
 

And tested UKR RTTY Open all is ok

Le 2018-03-01 à 21:14, Steve London a écrit :
What version ?

73,
Steve, N2IC

On 03/01/2018 06:55 PM, ve2fk wrote:
Wanted to test RTTY in NS tonight using nsrttydupe module
and did not had number increase.

73, Claude VE2FK




-----
Aucun virus trouve dans ce message.
Analyse effectuee par AVG - www.avg.fr
Version: 2016.0.7226 / Base de donnees virale: 4793/15442 - Date: 01/03/2018

Re: No nbr increase

Larry K8UT
 

Claude,

Tried NSRTTYDUPE here. Numbers are advancing properly.

>File >Open Log in Database, Sent Exchange = "001 LARRY MI"
Is that what you're using?

-larry (K8UT)

------ Original Message ------
From: "ve2fk" <duberger.miousse81@...>
Sent: 2018-03-01 20:55:03
Subject: [N1MMLoggerPlus] No nbr increase

Wanted to test RTTY in NS tonight using nsrttydupe module
and did not had number increase.

73, Claude VE2FK

Fixed: Advanced Voicing Troubles

Dave Malley, W1VEM
 

Many thanks to Rich, VE3KI for explaining that I didn’t understand that using # (in F2) was only for voicing serial numbers (and not exchanges as I thot).  That neatly explained why the program was just sending 1. Thx, Rich!

 

I also found that the LettersFiles folder cannot have any extraneous wav files beyond the sixty files that it expects.  Otherwise, callsign voicing doesn’t work.  Per the Manual, a missing wav files will also prevent callsign voicing.

 

Dave, W1VEM

Re: Fixed: Advanced Voicing Troubles

John Bednar
 

Dave,

 

> I also found that the LettersFiles folder cannot have any extraneous wav files beyond the sixty files that it expects. 

 

I have almost 2,200 files in my directory and callsign voicing works correctly. You can record full callsigns, prefix, or suffix wav files. The program looks for them when voicing a callsign.

 

Please test again and confirm.

 

John, K3CT

 

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Dave Malley
Sent: Friday, March 02, 2018 12:09 PM
To: N1MMLoggerPlus@groups.io
Subject: [N1MMLoggerPlus] Fixed: Advanced Voicing Troubles

 

Many thanks to Rich, VE3KI for explaining that I didn’t understand that using # (in F2) was only for voicing serial numbers (and not exchanges as I thot).  That neatly explained why the program was just sending 1. Thx, Rich!

 

I also found that the LettersFiles folder cannot have any extraneous wav files beyond the sixty files that it expects.  Otherwise, callsign voicing doesn’t work.  Per the Manual, a missing wav files will also prevent callsign voicing.

 

Dave, W1VEM

Re: IC-7300 Undocumented Command - Voice TX Memo #IC7300

Scott
 

Tom - this is great info! I did the steps successfully and ready to use the 7300 files in the N1MM+ F- keys in the contest this weekend. I also wanted to confirm that it works with my setup which is using VSPE.

73 Scott
KN3A

Re: Fixed: Advanced Voicing Troubles

Joe WB9SBD
 
Edited

You still have something not right,,,

My Letters folder has just shy of 18 Thousand files in it.. and all works great!

Joe WB9SBD

The Original Rolling Ball Clock
Idle Tyme
Idle-Tyme.com
http://www.idle-tyme.com

On 3/2/2018 11:08 AM, Dave Malley wrote:

Many thanks to Rich, VE3KI for explaining that I didn’t understand that using # (in F2) was only for voicing serial numbers (and not exchanges as I thot).  That neatly explained why the program was just sending 1. Thx, Rich!

 

I also found that the LettersFiles folder cannot have any extraneous wav files beyond the sixty files that it expects.  Otherwise, callsign voicing doesn’t work.  Per the Manual, a missing wav files will also prevent callsign voicing.

 

Dave, W1VEM


Re: No nbr increase

Hank Garretson
 

V1.0.7080.0

NSRTTYDUPE

001 HANK CA

Number is not advancing for RUN contacts. Advances for S&P contacts.



Note that this is a new problem. Two or three versions ago numbers advanced properly.

What am I doing wrong?

Contest Exuberantly,

Hank, W6SX

Note, CC:ing Tom, Steve, and Larry because not sure images will make it through groups.io