Date   
FT Roundup, A Learning Experience

Mike K2MK
 
Edited

I think this contest has been a learning experience for many of us. At the start of the contest, calling CQ resulted in many dupes calling me. I reviewed the WSJT online guide examples and realized that many people probably did not understand that only one person sends 73. After 73 is sent the contact is over. I too found it strange, especially on FT4 that the full contact was completed so quickly followed by a loss of the Enable TX red indication. A few hours later the problem seemed to resolve itself. Hardly any dupes. I can only assume that everybody began to understand the 73 concept.

It's also very nice to be able to switch back and forth between FT4 and FT8. It almost feels like switching bands as you find a new batch of potential contacts.

I'm looking forward to the January VHF contest. FT8 on 6 meters has, in the past, resulted in many dupes and some QSOs that never seemed to end. It was a good idea to have different frequencies for contest QSOs in the FT Roundup. I hope this idea is utilized for 6 meters in the VHF contest. I think many of the dupes, and the endless back-and-forth, may have been the result of mixing contest and non-contest operators.

73,
Mike K2MK

Re: FT Roundup?N1MM+ Problem

Rick Ellison
 

Paul..

You’re the second one to mention this. I need look and see what has changed. When the tcp port makes the connection to WSJT it should turn green and when the tcp closes it should turn red. But since everything is working for something has gotten confused.. I will look and see what that is..

 

73 Rick N2AMG

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of w2eck
Sent: Saturday, December 7, 2019 6:19 PM
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] FT Roundup?N1MM+ Problem

 

I seem to have N1MM+/WSJT-X working properly for the FT Roundup going on now. Receiving and Tx'ing fine, DeCode List populating etc. One issue remaining is that when I  open N1MM+ I am still getting the small N1MM Box with the Red Square in it and the DeBug box you can check. I am not seeing a DeBug Log on my desktop anywhere. So need some help in figuring out how to turn the Red Box -- Green. Any ideas on how to fix this ?

73 Paul w2eck

Re: VE mults

Jamie WW3S
 

And I have the available window set to display only mults, and the counter says one, yet there are several in the window....


On Dec 7, 2019, at 3:26 PM, Pete Smith <n4zr@...> wrote:



I  just noticed that the title bar of the Multiplier window says 58 of 83, while my actual count is 66 so far

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 12/7/2019 1:37 PM, Tim Shoppa wrote:
Similar - if not identical - things happened in Sweepstakes. And in years past I’ve seen it at the others extreme - never flagging any VEs as mults in NAQP.

This particularly affects VE3 and Maritimes where mapping from province to ARRL section is not one to one.

I myself did not see a problem with VE2 or VE6s.

But it might have some interaction with history file and even a province decoding done by some clusters so maybe different history files or different cluster decode options could vary the symptoms between users.

Tim N3QE

On Dec 7, 2019, at 12:41 PM, Carol Richards <n2mm@...> wrote:

Hello all....


I noticed in the available band multiplier window all VE stations show up as multipliers; even after I have worked a VE. I am not referring to them as a section multiplier, but rather all! Every VE3 that gets spotted appears in the multiplier window, shaded as a multiplier. ( in my case RED) When I work them they count normally. If I set up the multiplier/band window to only show multipliers, no VE show up; even the VE mults that I need. The band map seems to be ok.


Is this a bug? Does anyone else have this problem?



Carol






Re: VE mults

Jamie WW3S
 

Ditto.....unless they were in call history, then they were not coded as a mult....it’s almost backwards from other contests, when VE doesn’t show as a mult, yet it should,....


On Dec 7, 2019, at 3:49 PM, Drew Vonada-Smith K3PA <drew@...> wrote:



I also had VE3s flagged as mults even though I had worked all the VE3 sections.  

73,

Drew K3PA

FT Roundup?N1MM+ Problem

w2eck
 

I seem to have N1MM+/WSJT-X working properly for the FT Roundup going on now. Receiving and Tx'ing fine, DeCode List populating etc. One issue remaining is that when I  open N1MM+ I am still getting the small N1MM Box with the Red Square in it and the DeBug box you can check. I am not seeing a DeBug Log on my desktop anywhere. So need some help in figuring out how to turn the Red Box -- Green. Any ideas on how to fix this ?

73 Paul w2eck

Re: VE mults

Drew Vonada-Smith K3PA
 

I also had VE3s flagged as mults even though I had worked all the VE3 sections.  

73,

Drew K3PA

Re: install folder error #solved

Pete Smith
 

Did you also delete the N1MM+ Documents folder?

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 12/7/2019 3:23 PM, Eliot Mayer, W1MJ via Groups.Io wrote:

I get an error message, "N1MMLogger.net - The program detected that your N1MM+ user folder ... is stored in the cloud ... Re-Install and move the files to a local location on your disk".  It was true that my original user folder was a OneDrive folder, so I uninstalled and re-installed N1MM, choosing a local folder.  But I still get the message, and it still thinks my user folder is the original OneDrive folder.  In other words, it seems to have ignored my choice of local folder during re-installation.  How can I get N1MM to forget the original folder and use my local folder?  Thanks dE W1MJ

Re: VE mults

Pete Smith
 

I  just noticed that the title bar of the Multiplier window says 58 of 83, while my actual count is 66 so far

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 12/7/2019 1:37 PM, Tim Shoppa wrote:

Similar - if not identical - things happened in Sweepstakes. And in years past I’ve seen it at the others extreme - never flagging any VEs as mults in NAQP.

This particularly affects VE3 and Maritimes where mapping from province to ARRL section is not one to one.

I myself did not see a problem with VE2 or VE6s.

But it might have some interaction with history file and even a province decoding done by some clusters so maybe different history files or different cluster decode options could vary the symptoms between users.

Tim N3QE

On Dec 7, 2019, at 12:41 PM, Carol Richards <n2mm@...> wrote:

Hello all....


I noticed in the available band multiplier window all VE stations show up as multipliers; even after I have worked a VE. I am not referring to them as a section multiplier, but rather all! Every VE3 that gets spotted appears in the multiplier window, shaded as a multiplier. ( in my case RED) When I work them they count normally. If I set up the multiplier/band window to only show multipliers, no VE show up; even the VE mults that I need. The band map seems to be ok.


Is this a bug? Does anyone else have this problem?



Carol







Re: install folder error #solved

Eliot Mayer, W1MJ
 

I get an error message, "N1MMLogger.net - The program detected that your N1MM+ user folder ... is stored in the cloud ... Re-Install and move the files to a local location on your disk".  It was true that my original user folder was a OneDrive folder, so I uninstalled and re-installed N1MM, choosing a local folder.  But I still get the message, and it still thinks my user folder is the original OneDrive folder.  In other words, it seems to have ignored my choice of local folder during re-installation.  How can I get N1MM to forget the original folder and use my local folder?  Thanks dE W1MJ

Re: VE mults

Tim Shoppa
 

Similar - if not identical - things happened in Sweepstakes. And in years past I’ve seen it at the others extreme - never flagging any VEs as mults in NAQP.

This particularly affects VE3 and Maritimes where mapping from province to ARRL section is not one to one.

I myself did not see a problem with VE2 or VE6s.

But it might have some interaction with history file and even a province decoding done by some clusters so maybe different history files or different cluster decode options could vary the symptoms between users.

Tim N3QE

On Dec 7, 2019, at 12:41 PM, Carol Richards <n2mm@...> wrote:

Hello all....


I noticed in the available band multiplier window all VE stations show up as multipliers; even after I have worked a VE. I am not referring to them as a section multiplier, but rather all! Every VE3 that gets spotted appears in the multiplier window, shaded as a multiplier. ( in my case RED) When I work them they count normally. If I set up the multiplier/band window to only show multipliers, no VE show up; even the VE mults that I need. The band map seems to be ok.


Is this a bug? Does anyone else have this problem?



Carol



Re: VE mults

Carol Richards
 

Hi Pete,


I heard a ve7 but he was puny weak and I have a zero noise floor. I know W2GD worked him, but it must have taken all of the beverage strength,,,lol


Carol

On 12/7/2019 12:52 PM, Pete Smith wrote:

I noticed the same thing (red VEs), and wondered if I'd been hibernating and missed the explanation.  Seems like it should be easy to fix.  My multiplier window is working properly, though - once again, VE7 is among the missing...

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 12/7/2019 12:41 PM, Carol Richards wrote:
Hello all....


I noticed in the available band multiplier window all VE stations show up as multipliers; even after I have worked a VE. I am not referring to them as a section multiplier, but rather all! Every VE3 that gets spotted appears in the multiplier window, shaded as a multiplier. ( in my case RED) When I work them they count normally. If I set up the multiplier/band window to only show multipliers, no VE show up; even the VE mults that I need. The band map seems to be ok.


Is this a bug? Does anyone else have this problem?



Carol





Re: VE mults

Pete Smith
 

I noticed the same thing (red VEs), and wondered if I'd been hibernating and missed the explanation.  Seems like it should be easy to fix.  My multiplier window is working properly, though - once again, VE7 is among the missing...

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 12/7/2019 12:41 PM, Carol Richards wrote:

Hello all....


I noticed in the available band multiplier window all VE stations show up as multipliers; even after I have worked a VE. I am not referring to them as a section multiplier, but rather all! Every VE3 that gets spotted appears in the multiplier window, shaded as a multiplier. ( in my case RED) When I work them they count normally. If I set up the multiplier/band window to only show multipliers, no VE show up; even the VE mults that I need. The band map seems to be ok.


Is this a bug? Does anyone else have this problem?



Carol





VE mults

Carol Richards
 

Hello all....


I noticed in the available band multiplier window all VE stations show up as multipliers; even after I have worked a VE. I am not referring to them as a section multiplier, but rather all! Every VE3 that gets spotted appears in the multiplier window, shaded as a multiplier. ( in my case RED) When I work them they count normally. If I set up the multiplier/band window to only show multipliers, no VE show up; even the VE mults that I need. The band map seems to be ok.


Is this a bug? Does anyone else have this problem?



Carol

Objet : [N1MM+] Problem with Update 1.0.8029 (Dec 3, 2019)

Serge Lavoie
 

Hello Gerald

 

Perhaps you changed the settings for the Directory storage for N1MM+?

I have just intalled the update like every new one???

 

I assume it should be looking for a directory with your call: ve2hls in it.

The printscreen error refers to not being able to access a file in this directory: C:\Users\ve2hl\Documents\...

Yes, I know my computer name is ve2hl...

 

I did try to install the new update around 5 or 6 times with the same notification...

I will wait for the next update, since the ARRL contest is on the way and I dont want to loose any qso already log in.

 

Thank you for your answer...

 

73’ de Serge VE2HLS

 

De : Gerald Boutin (VE1DT)
Envoyé le :6 décembre 2019 19:27
À : N1MMLoggerPlus@groups.io
Objet :Re: [N1MM+] Problem with Update 1.0.8029 (Dec 3, 2019)

 

Serge,

Perhaps you changed the settings for the Directory storage for N1MM+?

The printscreen error refers to not being able to access a file in this directory: C:\Users\ve2hl\Documents\...

I assume it should be looking for a directory with your call: ve2hls in it.


--
Gerald, VE1DT

 

Re: TS-590 not keyed by WSJT-X

Andrew O'Brien
 

With WSJT, you need a second PTT config in N1MM. I checked the PTT Via Radio Command option. 

Andy


On Dec 6, 2019, at 7:44 PM, Andy k3wyc <a.durbin@...> wrote:

The last time I was tempted to try a contest with N1MM and WSJT-X I got it working and made a few QSO.  Now, with later versions of N1MM and WSJT-X, I can't find any settings that will give CAT keying.

WSJT-X is configured for Rig Commander; PTT CAT, Mode None, Split Rig. (Commander is not running)
WSJT-X test CAT goes green but test CAT does not key the TS-590
N1MM is configured for TS-590; PTT via Radio Command Digital Mode.
Use Logger+ audio is enabled and before that was set Audio was set to "radio 1 output device is an internal radio codec"

These settings should cause N1MM to issue a TX1; command when WSJT is set to transmit.  However WSJT-X is producing audio  but the TS-590 is not keyed.

If I issue a TX1; command using a band map macro button then the rig is keyed and, if WSJT-X is set to transmit, then TS-590 transmits.

It's clear  that setting WSJT-X to transmit does not cause N1MM to issue a TX1; command over the "commander" interface but this did work before N1MM and WSJT-X updates.

Does anyone else see this problem or have any suggestions as to my configuration  error?

(WSJT-X 2.1.1, N1MM 1.0.8029.0)

Thanks and 73,
Andy, k3wyc

Re: TS-590 not keyed by WSJT-X

Andy k3wyc
 

On Fri, Dec 6, 2019 at 05:44 PM, Andy k3wyc wrote:
Now, with later versions of N1MM and WSJT-X, I can't find any settings that will give CAT keying.
Selected contest is CW only.  I had initially thought it was mixed mode.

Andy, k3wyc

Re: Operating time

Fred - NA2U
 

I’ve been looking for that for a long time. Thanks, Rich!

73 from the desert,

Fred/NA2U

On Dec 6, 2019, at 4:43 PM, danzee via Groups.Io <k2ywe=yahoo.com@groups.io> wrote:

In other words, if there are no off-time rules for that particular contest, it assumes a 30-minute period for calculating off times. If you take a break of less than 30 minutes between logged contacts, it counts that as operating time, but a gap of more than 30 minutes with no contacts logged will be counted as off time.

73,
Rich VE3KI

TS-590 not keyed by WSJT-X

Andy k3wyc
 

The last time I was tempted to try a contest with N1MM and WSJT-X I got it working and made a few QSO.  Now, with later versions of N1MM and WSJT-X, I can't find any settings that will give CAT keying.

WSJT-X is configured for Rig Commander; PTT CAT, Mode None, Split Rig. (Commander is not running)
WSJT-X test CAT goes green but test CAT does not key the TS-590
N1MM is configured for TS-590; PTT via Radio Command Digital Mode.
Use Logger+ audio is enabled and before that was set Audio was set to "radio 1 output device is an internal radio codec"

These settings should cause N1MM to issue a TX1; command when WSJT is set to transmit.  However WSJT-X is producing audio  but the TS-590 is not keyed.

If I issue a TX1; command using a band map macro button then the rig is keyed and, if WSJT-X is set to transmit, then TS-590 transmits.

It's clear  that setting WSJT-X to transmit does not cause N1MM to issue a TX1; command over the "commander" interface but this did work before N1MM and WSJT-X updates.

Does anyone else see this problem or have any suggestions as to my configuration  error?

(WSJT-X 2.1.1, N1MM 1.0.8029.0)

Thanks and 73,
Andy, k3wyc

Re: Problem with Update 1.0.8029 (Dec 3, 2019)

Gerald Boutin (VE1DT)
 

Serge,

Perhaps you changed the settings for the Directory storage for N1MM+?

The printscreen error refers to not being able to access a file in this directory: C:\Users\ve2hl\Documents\...

I assume it should be looking for a directory with your call: ve2hls in it.


--
Gerald, VE1DT

Re: Operating time

danzee
 

Log a specific bogus call when you want to start or stop the clock. Later examine the Cabtillo log and figure the times by hand or Excel. Then remove the bogus callsigns.



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: ve3ki <ve3iay@...>
Date: 12/6/19 6:33 PM (GMT-05:00)
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] Operating time

It does not count the time the program is open. After all, you might leave the program open for days on end without ever being at the radio. It has no way to know whether you are listening or not.

It counts time based on when QSOs are actually logged. If you spend the entire contest SWLing and never make a contact, it will credit you with zero operating time. 

From the manual description of the View menu items at
<https://n1mmwp.hamdocs.com/manual-windows/entry-window/#view-menu-selections>:

Off Times – Shows off times. Lists each off period that complies with the contest rules, or each off-time of 30 minutes or more if the contest rules do not specify.

In other words, if there are no off-time rules for that particular contest, it assumes a 30-minute period for calculating off times. If you take a break of less than 30 minutes between logged contacts, it counts that as operating time, but a gap of more than 30 minutes with no contacts logged will be counted as off time.

73,
Rich VE3KI


On Fri, Dec 6, 2019 at 03:03 PM, Gilbert Baron W0MN wrote:

A good explanation for a contest with a time off minimum. How about one like 160CW where there is no off requirement. If I want to track how many hours I actually was on and searching or CQing or actually participating must I simply close the N1MM window? If I do that is operating time only the amount of time the window was open or what? Seems no easy way other than closing down N1MM because no way for it to tell if I am at the radio or just listening or what I am doing especially if I am not turning any radio knobs. Not a big deal as I could keep track of my own time but wonder what happens in the no off time required case.

 

Outlook Laptop Gil W0MN

Hierro candente, batir de repente

44.08226N 92.51265W EN34rb

 

From: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io> On Behalf Of ve3ki
Sent: Friday, December 6, 2019 07:12
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] Operating time

 

N1MM+ calculates on and off times the same way the contest scorers do. Operating time includes any clock minute during which a contact is logged, as well as idle clock minutes that do not qualify as off time. Off time during the contest requires 30 (or 60, depending on the contest rules) consecutive full clock minutes during which no contacts are logged. In effect, the off time clock starts at the beginning of the clock minute after the last logged QSO and continues until the beginning of the clock minute before the next logged QSO, and if there are not enough such consecutive minutes to meet the contest rules for off times, that time interval counts as operating time. Full clock minutes at the beginning and end of the contest during which no contact is logged qualify as off time and do not count towards the operating time.

73,
Rich VE3KI


On Fri, Dec 6, 2019 at 07:57 AM, Gilbert Baron W0MN wrote:

How does N1MM calculate operating time

 

Outlook Laptop Gil W0MN

Hierro candente, batir de repente

44.08226N 92.51265W EN34rb

 


--
W0MN Rochester, MN

 


--
W0MN Rochester, MN