开云体育

As evidenced by yesterday's discussion of the SPAR Winter Field Day contest, there are contests in our Supported Contests List that are obsolete/inactive and should be de-listed from the Entry Window's >File >New Log in Database - contest choices. By coincidence, in recent weeks the N1MM DevTeam has been working with Bruce WA7BNM regarding a direct interface between his Contest Calendar website and N1MM. As part of that effort we have identified 51 contests that appear to be obsolete/inactive. In this week's Latest Update release we will begin trimming the menu selection list by removing contests that are tagged as obsolete/inactive. The list of those 51 proposed obsolete contests can be found in the website's >Downloads >Program Files >Experimental Versions gallery. If your contest is listed but is still an active contest, please contact the Dev Team to get your contest reinstated on the list. https://n1mmwp.hamdocs.com/mmfiles/categories/programexperimental/ NOTE: This list does not includes User Defined Contests (UDCs) and QSO Parties. We'll be looking at those in the future, also. -larry K8UT

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

A new poll has been created: Do you use LOTW (Log of the World)? Do not reply to this post. Just click on the poll and answer it. I am interested in the penetration of LOTW within contest logger users and the possibility of leveraging the certificate that LOTW provides as a way of authenticating Telnet users. This is in response to the increasing level of malicious spots during contest weekends. I am just as interested in those who answer the last four categories as I am those who answer "Yes". Tom - N1MM 1. Yes 2. No, but I have the capability. I installed it and my certficate is up-to-date. 3. No. I didn't install it, 4. I installed it, but stopped using it. 5. Huh? Click Here To Vote Do not reply to this message to vote in the poll. You can vote in polls only through the group's website.

Is there a way for N1MM to alert us when we accidentally operate out of band? It appears I was not paying close attention and moved into the CW band while working Phone in CQ WW. 73 Chuck K9LC

K4 usb control. EA RTTY Contest, mode FSK, everything working nomally. Switch to MO QP which is configured for CW and SSB. Rig stays in FSK. Type CW in entry window, K4 switches to CW. But! QSK is not ON. How do I make QSK sticky for CW? Config, Mode Control: Use contest or radio mode selected. Radio 1 and Radio 2 RTTY > RTTY, DIGI > PSK Help please. What am I doing wrong. Contest Exuberantly, Hank, W6SX

Hey folks, is there a file for the IG-RY RTTY bash this coming weekend? I can’t see one when I search here. 73 Keith

Folks, During the EA-RTTY contest, while S&P I found stations calling very close or on top of the International Beacon Project IBP frequency on 20 meters. A similar issue happened during the CQWPX Phone contest on 21.150 MHz. Would it be possible to include an option so the VFO on CAT jumps or warns over these frequencies, i.e. 14.098 to 14.102 MHz? Thanks! jon, ea2sn / ee2a

I wonder, is it possible to have N1MM+ echo the CAT data from a connected radio to another port? I have searched the user manual, but can't see anything. That's not to say it isn't there, of course... The use case I have in mind is: Radio (FTdx101) connected to N1MM+ via USB Amplifier (Acom 2000) connected to radio via coax and PTT cable At present, the amplifier automatically tunes to whatever segment it detects when I send it some RF. It is possible, however, to connect the amplifier to a serial port and have it select the appropriate band segment as the data on the serial port changes. This means the amplifier is already tuned correctly prior to RF being applied, which is probably slightly better for the amplifier. My question is whether the N1MM+ software can send the CAT data it has received from the radio out through another serial port to control the amplifier? In a perfect world, I could connect the amplifier CAT port to the serial connector on the rear panel of the radio, but, apparently, the Acom doesn't speak FTdx101 language. Thus, I thought a work-around could be to send the data out from the logging software - It would need to be translated into something more vanilla, I suppose- Kenwood TS2000 or Yaesu FT1000, maybe. Is there already a way to do this? If not, is it something that would constitute a worthwhile enhancement? Cheers, John G4DRS

I was running N1MM through the paces this morning getting ready for the MOQP, and N1MM states that self-spotting is not allowed. It clearly is in the rules. How do I fix this before tomorrow? Thanks! 73, Jim KK0U

I posted experimental code that will be released in the near future with enhancements to Logger+ Audio. I’d like users to try the code and let me know if issues are found. https://n1mmwp.hamdocs.com/mmfiles/categories/programexperimental/ I am aware that some users are changing the “Operator” setting to switch wav files for language or phonetic variations. This also changes the Operator field that is stored in the QSO record. I am making a change that will allow everyone to deprecate the use of {OPERATOR} in function key messages and allow users to swap voice message directories on the fly. To accomplish this, two new macros have been introduced. {WAVDIR} takes the place of {OPERATOR} in function key messages and the Letters Wav File Path. {SETWAVDIR} allows the user to change the setting of {WAVDIR} using a function key, key mapper, or a stream deck. The format of the macro is explained in the release notes. These macros are not case sensitive but the examples will use the standard used in the documentation of all upper case. Existing function key files will continue to work but the default function key file has been changed to use the new macro name {WAVDIR}. When the operator setting is changed, the value of {WAVDIR} is set to the same callsign string. For the group of users that want to use more than one wav file, they can change the wav directories by changing {WAVDIR} on the fly with the {SETWAVDIR} macro. Additional details can be found in the release notes. The WAV file directory structures have not changed and the use of {OPERATOR} can continue with the known QSO record byproduct. Below are examples that show the existing directory hierarchy (indent indicates a sub directory). John, K3CT Example1: {WAVDIR} = “K3CT” and Config, Other tab, Letters Wav File Path = “\” Used by a single op, single set of LettersFiles files. WAV K3CT (CQ, TU, QRZ, etc wav files) LettersFiles (letter, number, callsign wav files) Example2: {WAVDIR} = “K3CT” and Config, Other tab, Letters Wav File Path = “{WAVDIR}\” Used by a multi or single ops, each operator has a set of WAV files and a set of LettersFiles files. WAV K3CT (CQ, TU, QRZ, etc wav files) LettersFiles K3CT (letter, number, callsign wav files) Single ops that want to switch between multiple sets of wav files would use the {SETWAVDIR} macro to change the {WAVDIR}. {SETWAVDIR K3CT_2} would switch to using the alternate wav files and LettersFiles as shown here. WAV K3CT_2 (CQ, TU, QRZ, etc wav files) LettersFiles K3CT_2 (letter, number, callsign wav files)

The Country (CTY) Files were updated on 06 April 2025: https://www.country-files.com/cty-3510-06-april-2025/ For installation instructions, start at: https://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: https://www.country-files.com/big-cty-06-april-2025/ 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: https://www.country-files.com/feed/ Here are the release notes: 6 April 2025 (CTY-3510) VER20250406, Version entity is Morocco, CN Added/changed Entities/Prefixes/Callsigns: * EF0F/8 is Canary Islands, EA8 * M0KXR is Northern Ireland, GI * GB5WAA and GB9WAA are both Scotland, GM * KB2DJE, KG5DVX and NV2T are all Hawaii, KH6 * KD7CYC and NN7C are both Alaska, KL * LU1DHL/W, LU6DO/V and LU8YE/Y are all Argentina, LU in ITU zone 16 * R9FCS/4, UE80MA and UE80SZ are all European Russia, UA * RA/EU1FY is Kaliningrad, UA2 * RK4PA/9 is Asiatic Russia, UA9 in ITU zone 20 Removed Entities/Prefixes/Callsigns: * IT9ECY/CH in Sicily, *IT9 * EM1U, KC4/KB1EHE, KC4/KB1IFZ and VK0/FT4YM/P in Antarctica, CE9 * EA5IKT/P in Spain, EA * FO/F4LYI and FO/F6BCW in Marquesas Islands, FO/m * G6ICR in Isle of Man, GD * G0HCQ, G0JCE, G4WZG, G5RDX, GB4CDG and M0TFU in Scotland, GM * M0KWG and M0TDZ in Wales, GW * IZ3QBN/CRT in Italy, I * K3JWI, KG7SPL, NE9U and W5SGL in United States, K * AA7LE, KJ6NCW and W2DK in Hawaii, KH6 * KD6UDQ and WH6IQ in Alaska, KL * LU1VNH/V, LU1YY/V, LU3WFJ/XA, LU5DTF/D, LU6DJ/D, LU6DM/D, LU6UVI/D, LU8DBB/D, LU8DCH/D, LU8EMD/D, LU8XW/XP, LW2EDL/D, LW5EVI/D and LW9EVV/D in Argentina, LU * R102AE, R102ME, R9YDX/6, UB0IBA/7 and UE82AWD in European Russia, UA * UB9MCW/P in Asiatic Russia, UA9 * VK9/W5EIT in Cocos (Keeling) Islands, VK9C Though I am subscribed to this reflector so that I can make these announcements, I do not see most messages posted to it. If you have any comments or corrections to the country file, please contact me directly. 73 - Jim AD1C -- Jim Reisert AD1C, <jjreisert at alum.mit.edu>, https://ad1c.us

Hi Does it possible to add TRUETTY ( from UA9OV) in N1MM as it is possible with CW GET in CW mode? See you on EA RTTY this week-end ! 73 Jean-Phi

Want to change my Radio 2 (TS590) SDR unit from my RSP to an Airspy HF+. Am already using an HF+ on Radio 1. Will SDR Server work using two HF+ units? Manual seems to say not directly. Manual: "Airspy server can be used as a way to run a second Airspy on the same computer." K1TTT apparently does that. But if I'm reading correctly that method is not recommended and hasn't been supported since Jan 2024. Even if it works today I'd rather not count on an unsupported feature working long term. There is some talk in the manual indicating I might need to set up the second HF+ on a different computer and point SDR Server to its IP address? - N1MM SDR Server supports multiple SDRs, but only with ExtIO dlls that recognize different SDRs. You cannot rename a dll to accomplish this. It is the internals of the dll that recognizes a particular SDR. A workaround to this problem is to run SDR Server on mulitple computers. You’ll need to put the ip address of the 2nd computer in the Connect tab of the associated spectrum display window. ~and~ - N1MM SDR Server supports multiple SDRs, but only with ExtIO dlls that recognize different SDRs. You cannot rename a dll to accomplish this. It is the internals of the dll that recognizes a particular SDR. A workaround to this problem is to run SDR Server on mulitple computers. You’ll need to put the ip address of the 2nd computer in the Connect tab of the associated spectrum display window What are people doing? Kevan N4XL