Many questions can be answered by going to the N1MM+ Web page.
Search has been improved, so give it a try!
ctl t
Richard Zalewski
cw works fine with N1MM. Ctl T toggles SSB to CW but no output or tone indicating that it is transmitting. If mode set to CW same problem CTL T does not produce a tone or output.
|
|
Re: Location for WAV files
Tom Wagner (N1MM)
Find the file in File Explorer.
toggle quoted messageShow quoted text
Press Shift and hold. Right click on the file. Choose "Copy as Path" That is where your file is. Paste it into the SSB message file. Tom - N1MM
On 10/25/2020 9:01 AM, George Harlem wrote:
|
|
Re: Location for WAV files
George Harlem
Rich, this is exactly what I have in the F-key message: VA2EBI
|
|
Mults & Q's updates
I find that the Mults & Q's do not automatically update as new spots come in. Rather, I have to do a SH/DX on the cluster to get the latest spots on Mults & Q's window.
Is there a way to get the spots to continually add to the Mults & Q's list? 73, George K5KG -- G. Wagner K5KG Sarasota, FL
|
|
Wrong score for NH6P in CQ WW SSB
WA5LXS
When I worked NH6P, Big Island Six Meter Club, on 15M, N1MM automatically entered “3” for the CQ zone. He reported his zone as 31 for Hawaii. N1MM still showed 0 points after I entered zone 31. I had to enter his call as NH6P/KH6 to get the expected 3 points and multiplier. My log displayed the zone with a green background. Shouldn’t N1MM use the zone I entered without the /KH6?
Dennis WA5LXS
|
|
locked
Re: SSB band edges - quick question
Please take this discussion to CQ Contest.
Tom - N1MM
|
|
locked
Re: SSB band edges - quick question
PA4JJ
That is not his problem but the problem of
stations who are not allowed to call out of band. They do not
follow the rules.
toggle quoted messageShow quoted text
back in my (contest) hole 73 Jan PA4JJ Op 25-10-2020 om 10:56 schreef Ed K1EP:
|
|
locked
Re: SSB band edges - quick question
Ed K1EP
Correct. But he is running US stations that are out of band.
On Sun, Oct 25, 2020, 01:27 Jennifer-Jenni Eileen Jones <jenni.merfyn.jones@...> wrote:
|
|
Re: staiton stays blue for some time when worked.
Hi all,
toggle quoted messageShow quoted text
When this happened to me in JARTS, I was only clicking on calls in the decode window. 73 de Phil GU0SUP
-----Original Message-----
From: "Pete Smith" <n4zr@comcast.net> Sent: Saturday, 24 October, 2020 22:57 To: N1MMLoggerPlus@groups.io Subject: Re: [N1MM+] staiton stays blue for some time when worked. I think I, at least, need clarification. When this happens, is it when you have pulled a callsign into the Entry window from either the Available window or the Bandmap? What if you work a person who is blue in either window, but where you type the callsign in the Callsign textbox by hand? I have not seen this behavior in weekly CWTs, though there are occasionally other anomalies in getting a clicked call into the Callsign textbox. 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/24/2020 5:32 PM, ve3ki wrote: What happens if you tune away and then tune back (maybe by swapping
|
|
Re: staiton stays blue for some time when worked.
Timon Kruijer
Hi Rich,
When I tune away and I come back it is still there. When I want to work the station again it’s a dupe hi.
I already made a ticket after the sac contest. There must be more with this issue I think.
73 Timon PA1T
Van: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io> Namens Pete Smith
I think I, at least, need clarification. When this happens, is it when you have pulled a callsign into the Entry window from either the Available window or the Bandmap? What if you work a person who is blue in either window, but where you type the callsign in the Callsign textbox by hand? I have not seen this behavior in weekly CWTs, though there are occasionally other anomalies in getting a clicked call into the Callsign textbox. 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/24/2020 5:32 PM, ve3ki wrote:
|
|
locked
Re: SSB band edges - quick question
Just because you in the States, can not operate on 7127, does not mean, that we this side of the world are the same, we all operate under our licence limitations, this is a world wide contest, not just a US one..
toggle quoted messageShow quoted text
I would dearly love to operate on 3912, but I know I can't, so leave the guy alone..
On 25 Oct 2020, at 05:55, Alan K7ACZ <k7acz@...> wrote:
|
|
locked
Re: SSB band edges - quick question
How about all the General Class licenses that sneak into the Extra Class frequencies during a contest. Are they disqualified?
Alan K7ACZ
From: N1MMLoggerPlus@groups.io On Behalf Of Jennifer-Jenni Eileen Jones
Sent: Saturday, October 24, 2020 10:33 PM To: N1MMLoggerPlus@groups.io Subject: Re: [N1MM+] SSB band edges - quick question
I could CQ on 7.127, and I would be within my license limitations, so leave him alone...
_._,_._,_
|
|
locked
Re: SSB band edges - quick question
Don Murray
Calling CQ on 7127, would result in an out of band signal. Your modulation artifacts would extend at least 2+KHz from 7127, falling below 7125, the bottom edge of the American phone band. And in addition... A CW signal centered 250Hz above Be careful around band edges! 73
On Sunday, October 25, 2020 Jennifer-Jenni Eileen Jones <N1MMLoggerPlus@groups.io> wrote: I could CQ on 7.127, and I would be within my license limitations, so leave him alone... On 24 Oct 2020, at 18:43, Tom Osborne <w7why1@...> wrote:
|
|
locked
Re: SSB band edges - quick question
I could CQ on 7.127, and I would be within my license limitations, so leave him alone...
toggle quoted messageShow quoted text
On 24 Oct 2020, at 18:43, Tom Osborne <w7why1@...> wrote:
|
|
locked
Re: SSB band edges - quick question
It's not out of band to him...
toggle quoted messageShow quoted text
On 25 Oct 2020, at 02:47, Ed K1EP <k1ep.list@...> wrote:
|
|
Re: Location for WAV files
ve3ki
What is in the function key message? The correct location depends on the file name in the function key message, i.e. on whether that file name includes any directory information (any \ characters).
toggle quoted messageShow quoted text
If the filename in the function key message has a wav\ in it, then the path to the actual file has to have an extra wav\ in it as well. I think the following is just as likely to be the problem, though: If there is an {OPERATOR}\ macro in the file name in the function key message, then the file the program is looking for has to be inside a subdirectory labelled with the OPERATOR's call sign (*NOT* the STATION call sign, unless they happen to be the same - that depends on what the last OPON command was). On the other hand, if there is no {OPERATOR}\ macro in the file name, the path to the folder from the parent Documents\N1MM Logger+ folder would not include a call sign. 73, Rich VE3KI
On Sat, Oct 24, 2020 at 10:34 PM, Mac wrote:
|
|
locked
Re: SSB band edges - quick question
Ed K1EP
5T5PA is CQing on 7.127 this evening. US stations on LSB are answering out of band.
On Sat, Oct 24, 2020, 13:44 Tom Osborne <w7why1@...> wrote:
|
|
Re: Location for WAV files
Mac
> N1MM Logger+\Wav\wav\va2ebi.wav 73, -Mac NT4D
On 10/24/2020 10:28 PM, George Harlem
wrote:
N1MM Logger+\Wav\wav\va2ebi.wav
|
|
Re: Location for WAV files
George Harlem
Mike, I have this in my F4 function key:
toggle quoted messageShow quoted text
C:\Users\George\My Documents\N1MM Logger+\Wav\wav\va2ebi.wav But I am still not playing the wav file. I was able to play it earlier but I have a suspicion that my pc is the issue—still Windows7 and Windows Media Player might be defunct. George W1EBI From George's iPhone
On Oct 24, 2020, at 9:28 PM, VE9AA - Mike <ve9aa@...> wrote:
|
|
Re: Location for WAV files
Important Change for Those Transitioning from N1MM Classic
N1MM Logger Classic found its wav files assuming the starting directory was the N1MM Logger program directory. Typically users would place their wav files in a sub-directory of the N1MM Logger program directory called wav. To call up a wav file in this sub-directory, you would specify the file name in the form wav\filename.wav (or wav\{OPERATOR}\filename.wav if you were using operator-specific files) in your function key messages. N1MM Logger Plus finds its wav files assuming the starting directory is the wav sub-directory created by the installer inside the N1MM Logger+ user files directory (*not* the program files directory). To call up a wav file in this sub-directory, you specify the file name in your function key messages as filename.wav, i.e. without the leading wav\ (or if you are using the {OPERATOR} macro, as {OPERATOR}\filename.wav, again without the leading wav\). If you edit your message files by removing the leading wav\ on file names in messages, you will be able to access wav files you have placed in the wav sub-directory. Alternatively, if you want to continue to use the same message files you used with Classic without editing them to remove all those leading wav\’s, you can create a new wav sub-sub-directory inside the wav sub-directory in the N1MM Logger+ user files directory (so that these wav files are located at My Documents\N1MM Logger+\wav\wav\filename.wav, or My Documents\N1MM Logger+\wav\wav\{OPERATOR}\filename.wav – note the two levels of wav\ in the path name), and once you have placed your wav files in that new sub-directory (or in operator-specific sub-directories under that wav\wav sub-directory if you are using the {OPERATOR} macro), you can call those wav files up using your old function key message files. C:\Users\George\Documents\N1MM Logger+\Wav\VA2EBI C:\Users\[yourWindowslogonusername]\Documents\N1MM Logger+\wav\{OPERATOR}\cq.wav” -- Mike VE9AA
|
|