Date   

Re: SntNR 001 twice

ve3ki
 

>>> I have put some suggestions in line below

73,
Rich VE3KI

On Fri, Nov 16, 2018 at 04:15 AM, 'Zaba' OH1ZAA wrote:
Hello Jaan, Steve and Barry!

MWC nor Minitest has a multi-op sub-class. What I may have done is to
log the first QSO with the wrong mode or band, then correct the issue,
and subsequently go for QSO No. 2, however it was displaying 001 for the
serial as well...
>>> Did you do a Tools > Rescore Current Contest after editing the first QSO? I can't say for certain, but I believe this might have fixed it.

Other issues with N1MM+:

It still does not re-score in a way immediately visible to the operator.
One has to close the program first, and then the score has been updated.
>>> You do not have to close and reopen the program. Just go to the Tools menu and select "Rescore Current Contest".
>>> You should do this any time after making changes (importing from ADIF, or editing contacts in the log).

Recently upon initiating a new log N1MM+ suggests an initial date 3 - 5
days off. Formerly e.g. the CWops CWT date and time were coming up
exactly
right, but now it is not the case.
>>> The CWT dates/times are a problem, because there are three CWTs a week, two of them on the same UTC date.
>>> What it does depends on when you set up the CWT log - before the first session or in between CWT sessions on a single day.
>>> Often I find that it initializes the start date/time to the following week, as if this week's CWTs were all completed after the first one.
>>> Checking and if necessary editing the start date/time is a routine part of my CWT preparation.

OKOMDX-CW was still rated at 10 points per QSO, but the rules say 1
point.
>>> I believe Les responded to this.

Maybe a cache flush for several parameters would be good when initiating
a new log. Mostly a call sign logged in a previous contest is shown
above
the field where the new call sign is to be logged (when starting a new
log).
>>> That call sign in the frame comes from the Bandmap window.
>>> If you switch logs when there are two contests at the same time, you might not want the bandmap to be
>>>  cleared just because you were logging the next contact in a different contest log.
>>> You might want to just log that one contact and then switch back to the first contest with the bandmap intact.
>>> The choice is left to the user.
>>> If you do want to start a fresh bandmap, right-click in the Bandmap window and use one of the "Remove Spots" menu items.

After running the VHFNAC on 432 MHz last Tuesday, the band in the
CWT-test
was marked as 420000... my fault, I did not choose the band... but it is
a
HF-contest, so maybe a reminder could be displayed to choose the right
band?
>>> If you are using a radio that is interfaced to the program for rig control, this happens automatically.
>>> If your radio is not interfaced, it is up to you to tell the program what frequency and mode you want it to log.


Otherwise I have been running N1MM+ as a stand alone logger (not wired
to radio).

Thanks for all your efforts, N1MM+ is a great tool!

Cheers/73, Zaba OH1ZAA




Jaan, SM9X kirjoitti 16.11.2018 09:56:
Hello Barry and Zaba

I'm running single op, and the issue with double SntNR 001, has been
notices in at least two Revisions.
My plan is to write down all steps and see if I can capture the fault.
This week I did run MINITEST and the day before I prepared the two
databases one for 80 meter and the second for 40 meter.
I started to load the 40 meter test and got the issue. When the next
contest started, 1 hour later on 80 meter, the issue didn't occure.

Hope to come back with some detailed analysis on how to reproduce the
fault.

regards, Jaan
SM9X



Links:
------
[1] https://groups.io/g/N1MMLoggerPlus/message/37885
[2] https://groups.io/mt/28143946/763388
[3] https://groups.io/g/N1MMLoggerPlus/post
[4] https://groups.io/g/N1MMLoggerPlus/editsub/763388
[5] https://groups.io/g/N1MMLoggerPlus/leave/defanged


OKOMDX- points

'Zaba' OH1ZAA
 

GA Les,

Funny... I ran OKOMDX with 3 different calls... and I ran all of them
for rescore after the correction update was issued. There was no change
in the output log... so I sent Cabrillo's as per N1MM+ output...

Now I opened the OH5ZA log and it came up with 10 points/QSO and the former
50k claimed result. THEN I did rescore and points were set to 1 per QSO, but
the total score did not change (old issue for the last 2 years on all rescores).
Subsequently, when I restarted N1MM+ the score was correct at about 5k....

When I opened the OKOMDX-log first time, it showed 70 MHz as the operating
frequency (from yesterday's VHFNAC)... a minor issue .. it disappeared after
checking the final rescore...

I guess everything is right, now for OKOMDX.... Cheers/73, Zaba OH1ZAA


Les Elliott via Groups.Io kirjoitti 16.11.2018 11:53:

-----Original Message----- From: 'Zaba' OH1ZAA Sent: Friday, November
16, 2018 9:15 AM To: N1MMLoggerPlus@groups.io Cc: Jaan, SM9X Subject:
Re: [N1MMLoggerPlus] SntNR 001 twice
OKOMDX-CW was still rated at 10 points per QSO, but the rules say 1 point.
Cheers/73, Zaba OH1ZAA
If you have the latest update and you are sill getting 10 points/qso
are you loading for the SSB contest?
Les, G4OGB


Re: SntNR 001 twice

Les Elliott
 

-----Original Message-----
From: 'Zaba' OH1ZAA Sent: Friday, November 16, 2018 9:15 AM To: N1MMLoggerPlus@groups.io Cc: Jaan, SM9X Subject: Re: [N1MMLoggerPlus] SntNR 001 twice


OKOMDX-CW was still rated at 10 points per QSO, but the rules say 1 point.

Cheers/73, Zaba OH1ZAA

If you have the latest update and you are sill getting 10 points/qso
are you loading for the SSB contest?

Les, G4OGB


Re: SntNR 001 twice

'Zaba' OH1ZAA
 

Hello Jaan, Steve and Barry!

MWC nor Minitest has a multi-op sub-class. What I may have done is to
log the first QSO with the wrong mode or band, then correct the issue,
and subsequently go for QSO No. 2, however it was displaying 001 for the
serial as well...

Other issues with N1MM+:

It still does not re-score in a way immediately visible to the operator.
One has to close the program first, and then the score has been updated.

Recently upon initiating a new log N1MM+ suggests an initial date 3 - 5
days off. Formerly e.g. the CWops CWT date and time were coming up exactly
right, but now it is not the case.

OKOMDX-CW was still rated at 10 points per QSO, but the rules say 1 point.

Maybe a cache flush for several parameters would be good when initiating
a new log. Mostly a call sign logged in a previous contest is shown above
the field where the new call sign is to be logged (when starting a new log).

After running the VHFNAC on 432 MHz last Tuesday, the band in the CWT-test
was marked as 420000... my fault, I did not choose the band... but it is a
HF-contest, so maybe a reminder could be displayed to choose the right band?

Otherwise I have been running N1MM+ as a stand alone logger (not wired to radio).

Thanks for all your efforts, N1MM+ is a great tool!

Cheers/73, Zaba OH1ZAA




Jaan, SM9X kirjoitti 16.11.2018 09:56:

Hello Barry and Zaba
I'm running single op, and the issue with double SntNR 001, has been
notices in at least two Revisions.
My plan is to write down all steps and see if I can capture the fault.
This week I did run MINITEST and the day before I prepared the two
databases one for 80 meter and the second for 40 meter.
I started to load the 40 meter test and got the issue. When the next
contest started, 1 hour later on 80 meter, the issue didn't occure.
Hope to come back with some detailed analysis on how to reproduce the
fault.
regards, Jaan
SM9X
Links:
------
[1] https://groups.io/g/N1MMLoggerPlus/message/37885
[2] https://groups.io/mt/28143946/763388
[3] https://groups.io/g/N1MMLoggerPlus/post
[4] https://groups.io/g/N1MMLoggerPlus/editsub/763388
[5] https://groups.io/g/N1MMLoggerPlus/leave/defanged


Re: SntNR 001 twice

Jaan, SM9X
 

Hello Barry and Zaba

I'm running single op, and the issue with double SntNR 001, has been notices in at least two Revisions.
My plan is to write down all steps and see if I can capture the fault. This week I did run MINITEST and the day before I prepared the two databases one for 80 meter and the second for 40 meter.
I started to load the 40 meter test and got the issue. When the next contest started, 1 hour later on 80 meter, the issue didn't occure.

Hope to come back with some detailed analysis on how to reproduce the fault.

regards, Jaan
SM9X


Re: Update today - No Permission - Aborting ??

Richard Stein
 

I did and bingo! 73, Dick, K2ZR

-----Original Message-----
From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Steve London
Sent: Thursday, November 15, 2018 5:54 PM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] Update today - No Permission - Aborting ??

Go to the N1MM web site, and manually download and install the update.

http://n1mmplus.hamdocs.com/tiki-list_file_gallery.php?galleryId=15

73,
Steve, N2IC

On 11/15/2018 03:06 PM, Richard Stein wrote:
Hi Gil & Gerald,

All good but certainly an unusual day. 1^st I have 2 stations that run N1MM+

1._Station A:_Where I got the error message. Pardon the fact that I did not copy
the screen nor do a better job of noting exactly what was said when I got to
abort message. The Fix: I took the step to simply download the latest Update {
Nov 13^th } 1.0.7342.exe from the N1MM site and the Update worked just fine. So
all is good!

2._Station B_opened N1MM+ just fine, no error message! _But_, never got the
usual *_Do You Want To Update Screen_* { 1^st time for that }. So I went to the
N1MM+ site downloaded and “finished” the Nov 13^th Update. All is good except no
clue why I did not get the usual message asking me if I wanted to update. The
ambiguities of the computer ether-world.

Let’s see what happens next Update.

73 and thanks for the interest,

Dick, K2ZR

*From:*N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] *On Behalf Of
*Gerald Boutin (VE1DT)
*Sent:* Thursday, November 15, 2018 4:03 PM
*To:* N1MMLoggerPlus@groups.io
*Subject:* Re: [N1MMLoggerPlus] Update today - No Permission - Aborting ??

On Thu, Nov 15, 2018 at 02:41 PM, Richard Stein wrote:

Not sure what this is about but when I went to update my laptop today I got a
message that said something like this: *No Permission – Aborting *

Never seen this before & I generally update each week when an N1MM update is
available.

Anyone know what’s happening

73,

Dick, K2ZR

Dick,

Does the error stil happen or was it a one time event?

The exact wording and where the error came from would help in diagnosing the
issue. If it is an N1MM error, the error message should be in the LogError.txt
file, which is typically stored in: C:\Users\username\Documents\N1MM Logger+

N1MM+ error messages are time stamped and saved in that file.

It could be that your antivirus program was being overly suspicious and caused
this error to show up. To test, you ccn either add an exception to the antivirus
software or just temporarily disable it while doing the update.

--
Gerald, VE1DT


Re: Update today - No Permission - Aborting ??

Steve London
 

Go to the N1MM web site, and manually download and install the update.

http://n1mmplus.hamdocs.com/tiki-list_file_gallery.php?galleryId=15

73,
Steve, N2IC

On 11/15/2018 03:06 PM, Richard Stein wrote:
Hi Gil & Gerald,
All good but certainly an unusual day. 1^st  I have 2 stations that run N1MM+
1._Station A:_Where I got the error message. Pardon the fact that I did not copy the screen nor do a better job of noting exactly what was said when I got to abort message. The Fix: I took the step to simply download the latest Update { Nov 13^th } 1.0.7342.exe from the N1MM site and the Update worked just fine. So all is good!
2._Station B_opened N1MM+ just fine, no error message! _But_, never got the usual *_Do You Want To Update Screen_* { 1^st time for that }. So I went to the N1MM+ site downloaded and “finished” the Nov 13^th Update. All is good except no clue why I did not get the usual message asking me if I wanted to update. The ambiguities of the computer ether-world.
Let’s see what happens next Update.
73 and thanks for the interest,
Dick, K2ZR
*From:*N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] *On Behalf Of *Gerald Boutin (VE1DT)
*Sent:* Thursday, November 15, 2018 4:03 PM
*To:* N1MMLoggerPlus@groups.io
*Subject:* Re: [N1MMLoggerPlus] Update today - No Permission - Aborting ??
On Thu, Nov 15, 2018 at 02:41 PM, Richard Stein wrote:
Not sure what this is about but when I went to update my laptop today I got a message that said something like this: *No Permission – Aborting *
Never seen this before & I generally update each week when an N1MM update is available.
Anyone know what’s happening
73,
Dick, K2ZR
Dick,
Does the error stil happen or was it a one time event?
The exact wording and where the error came from would help in diagnosing the issue. If it is an N1MM error, the error message should be in the LogError.txt file, which is typically stored in: C:\Users\username\Documents\N1MM Logger+
N1MM+ error messages are time stamped and saved in that file.
It could be that your antivirus program was being overly suspicious and caused this error to show up. To test, you ccn either add an exception to the antivirus software or just temporarily disable it while doing the update.
--
Gerald, VE1DT


Re: Update today - No Permission - Aborting ??

Richard Stein
 

Hi Gil & Gerald,

All good but certainly an unusual day. 1st  I have 2 stations that run N1MM+

1.       Station A: Where I got the error message. Pardon the fact that I did not copy the screen nor do a better job of noting exactly what was said when I got to abort message. The Fix: I took the step to simply download the latest Update { Nov 13th } 1.0.7342.exe from the N1MM site and the Update worked just fine. So all is good!

2.       Station B opened N1MM+ just fine, no error message! But, never got the usual Do You Want To Update Screen { 1st time for that }. So I went to the N1MM+ site downloaded and “finished” the Nov 13th Update. All is good except no clue why I did not get the usual message asking me if I wanted to update. The ambiguities of the computer ether-world.

Let’s see what happens next Update.

73 and thanks for the interest,

Dick, K2ZR

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Gerald Boutin (VE1DT)
Sent: Thursday, November 15, 2018 4:03 PM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] Update today - No Permission - Aborting ??

 

On Thu, Nov 15, 2018 at 02:41 PM, Richard Stein wrote:

Not sure what this is about but when I went to update my laptop today I got a message that said something like this: No Permission – Aborting

Never seen this before & I generally update each week when an N1MM update is available.

Anyone know what’s happening

73,

Dick, K2ZR

 

Dick,

Does the error stil happen or was it a one time event?

The exact wording and where the error came from would help in diagnosing the issue. If it is an N1MM error, the error message should be in the LogError.txt file, which is typically stored in: C:\Users\username\Documents\N1MM Logger+

N1MM+ error messages are time stamped and saved in that file.

It could be that your antivirus program was being overly suspicious and caused this error to show up. To test, you ccn either add an exception to the antivirus software or just temporarily disable it while doing the update.
 
--
Gerald, VE1DT


Re: Log window frequency precision

Todd Shiffer
 

I changed those settings from 2 to 9 both is numbers & currency, n1mm still rounds up! column is wide enough. change say 14074.38 to 14074.388 log window displays 14074.39 but leave it as 14.074.38 log window displays 14074.38


Re: Update today - No Permission - Aborting ??

Gerald Boutin (VE1DT)
 

On Thu, Nov 15, 2018 at 02:41 PM, Richard Stein wrote:

Not sure what this is about but when I went to update my laptop today I got a message that said something like this: No Permission – Aborting

Never seen this before & I generally update each week when an N1MM update is available.

Anyone know what’s happening

73,

Dick, K2ZR

 

Dick,

Does the error stil happen or was it a one time event?

The exact wording and where the error came from would help in diagnosing the issue. If it is an N1MM error, the error message should be in the LogError.txt file, which is typically stored in: C:\Users\username\Documents\N1MM Logger+

N1MM+ error messages are time stamped and saved in that file.

It could be that your antivirus program was being overly suspicious and caused this error to show up. To test, you ccn either add an exception to the antivirus software or just temporarily disable it while doing the update.
 
--
Gerald, VE1DT


Re: Update today - No Permission - Aborting ??

Gilbert Baron W0MN
 

There should be more information than that. Show the entire message. It could mean a million things.

Did you get any messages when you tried to start the update? Are you running any Malware programs?

 

Outlook Laptop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

 

From: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io> On Behalf Of Richard Stein
Sent: Thursday, November 15, 2018 12:41
To: N1MMLoggerPlus@groups.io
Subject: [N1MMLoggerPlus] Update today - No Permission - Aborting ??

 

Not sure what this is about but when I went to update my laptop today I got a message that said something like this: No Permission – Aborting

Never seen this before & I generally update each week when an N1MM update is available.

Anyone know what’s happening

73,

Dick, K2ZR

 


Update today - No Permission - Aborting ??

Richard Stein
 

Not sure what this is about but when I went to update my laptop today I got a message that said something like this: No Permission – Aborting

Never seen this before & I generally update each week when an N1MM update is available.

Anyone know what’s happening

73,

Dick, K2ZR

 


Re: SntNR 001 twice

Barry Bettman
 

In some contest, being a multi will have a separate set of serial number for each band. Could this be the case in your situation? Barry K6ST


On Thursday, November 15, 2018, 'Zaba' OH1ZAA <elefa@...> wrote:

Hello Steve,

It was during OK1WC Memorial (MWC) that I was running OH3BCX and
the log started with a double 001 given sequence at the start...
It did the same with another contest, but then ever since it has
not occurred again. I guess I was also running v.1.0.7300 at the time.

Cheers/73, Zaba OH1ZAA



Steve London kirjoitti 15.11.2018 16:23:
Can you reproduce this outside of the contest ?

Can you go back to an earlier version and show that it doesn't happen ?

73,
Steve, N2IC

On 11/15/2018 01:25 AM, Jaan, SM9X wrote:
I have seen a issue when running contests every week for at least two latest versions of the Logger +

I have configured the contest that I plan to run some time before. And when time comes to start I load the contest from File -> Open Log in Database:
The two first QSO gets the same SntNR

QSO:  7024 CW 2018-11-14 1700 SM9X          599  001  DL4ME         599  002
QSO:  7024 CW 2018-11-14 1701 SM9X          599  001  MW0EDX        599  005

This has happen for the two contests I run weekly for a long time, MINITESTCW and OK1WC

I noticed the same from another ham in a SOAPBOX comment:

*OH3BCX:*       N1MM made a double on the 1st QSO, and I thought I have to correct them all... "


I'm using Windows 10 and Swedish Keyboard. Version of logger V1.0.7300.0 and V1.0.7336.0 wher issue has been noticed.

Regards, Jaan
SM9X










--

Barry

Barry Bettman, ATL, PCC
"Approved Tribal Leader" consultant for workplace culture
"Professional Certified Coach" with leaders and executives
775-622-3801

LEADERSHIP FOR EVERYONE TO BE GREAT TOGETHER
Executive Producer, Stage 5 Leadership Productions - Real Time High Engagement Teleseminars


Re: SntNR 001 twice

'Zaba' OH1ZAA
 

Hello Steve,

It was during OK1WC Memorial (MWC) that I was running OH3BCX and
the log started with a double 001 given sequence at the start...
It did the same with another contest, but then ever since it has
not occurred again. I guess I was also running v.1.0.7300 at the time.

Cheers/73, Zaba OH1ZAA



Steve London kirjoitti 15.11.2018 16:23:

Can you reproduce this outside of the contest ?
Can you go back to an earlier version and show that it doesn't happen ?
73,
Steve, N2IC
On 11/15/2018 01:25 AM, Jaan, SM9X wrote:
I have seen a issue when running contests every week for at least two latest versions of the Logger +
I have configured the contest that I plan to run some time before. And when time comes to start I load the contest from File -> Open Log in Database:
The two first QSO gets the same SntNR
QSO:  7024 CW 2018-11-14 1700 SM9X          599  001  DL4ME         599  002
QSO:  7024 CW 2018-11-14 1701 SM9X          599  001  MW0EDX        599  005
This has happen for the two contests I run weekly for a long time, MINITESTCW and OK1WC
I noticed the same from another ham in a SOAPBOX comment:
*OH3BCX:* N1MM made a double on the 1st QSO, and I thought I have to correct them all... "
I'm using Windows 10 and Swedish Keyboard. Version of logger V1.0.7300.0 and V1.0.7336.0 wher issue has been noticed.
Regards, Jaan
SM9X


Re: SntNR 001 twice

Steve London
 

Can you reproduce this outside of the contest ?

Can you go back to an earlier version and show that it doesn't happen ?

73,
Steve, N2IC

On 11/15/2018 01:25 AM, Jaan, SM9X wrote:
I have seen a issue when running contests every week for at least two latest versions of the Logger +
I have configured the contest that I plan to run some time before. And when time comes to start I load the contest from File -> Open Log in Database:
The two first QSO gets the same SntNR
QSO:  7024 CW 2018-11-14 1700 SM9X          599  001  DL4ME         599  002
QSO:  7024 CW 2018-11-14 1701 SM9X          599  001  MW0EDX        599  005
This has happen for the two contests I run weekly for a long time, MINITESTCW and OK1WC
I noticed the same from another ham in a SOAPBOX comment:
*OH3BCX:* N1MM made a double on the 1st QSO, and I thought I have to correct them all... "
I'm using Windows 10 and Swedish Keyboard. Version of logger V1.0.7300.0 and V1.0.7336.0 wher issue has been noticed.
Regards, Jaan
SM9X


SntNR 001 twice

Jaan, SM9X
 

I have seen a issue when running contests every week for at least two latest versions of the Logger +

I have configured the contest that I plan to run some time before. And when time comes to start I load the contest from File -> Open Log in Database:
The two first QSO gets the same SntNR

QSO:  7024 CW 2018-11-14 1700 SM9X          599  001  DL4ME         599  002
QSO:  7024 CW 2018-11-14 1701 SM9X          599  001  MW0EDX        599  005

This has happen for the two contests I run weekly for a long time, MINITESTCW and OK1WC

I noticed the same from another ham in a SOAPBOX comment: 

OH3BCX: N1MM made a double on the 1st QSO, and I thought I have to correct them all... "


I'm using Windows 10 and Swedish Keyboard. Version of logger V1.0.7300.0 and V1.0.7336.0 wher issue has been noticed.

Regards, Jaan
SM9X


Re: New version of MM issue (no SS mults)

wk4r
 

Tom

Followed your recommendations.  All is good.  You're the man!

73  Bill  K4XS/KH7XS


Re: New version of MM issue (no SS mults)

Tom Wagner (N1MM)
 

That was not affected by the changes.

Try opening it again. -or-

Try opening it again while holding the ctl key down. Look at the bottom edge of all monitors for the window. The title bar should be just visible. -or-

Change this section in your ini file:

[SectionMults]
Height=367
IsOpen=False
Left=133
Top=288
Width=944
WindowState=0

Change the Left & Top values to zero.

73,

Tom - n1MM

On 11/14/2018 12:06 AM, wk4r via Groups.Io wrote:
Downloaded new version and have a problem which I did not have before the download.  I am unable to pull up the window for the section/states for SS.  I did not have this issue with the old version for SSCW.  Went back to the SSCW I did two weeks ago and the mults will not appear there anymore either.

Bill KH7XS/K4XS


New version of MM issue (no SS mults)

wk4r
 

Downloaded new version and have a problem which I did not have before the download.  I am unable to pull up the window for the section/states for SS.  I did not have this issue with the old version for SSCW.  Went back to the SSCW I did two weeks ago and the mults will not appear there anymore either.

Bill KH7XS/K4XS


3 bugs in the DI under RTTY So2r operation

Jeff AC0C
 

#1 - Callstack - in the WAE contest not too many opportunities to use the callstack function but it seems the "blank" callsign problem remains meaning a couple of times the program thought I had a callsign in the stack when there was none and it sent the NOW message with a blank callsign.  Fortunately it was easy to clear this time which is a big improvement over the CQ DX RTTY. This comment is based only on perhaps 15 uses of the callstack function this weekend.

#2 - Callstack - the FIFO/mults first function does not work. It's LIFO only.

#3 - CLEAR ON QSY - The clear grab and receive window on QSY has a bug that I think has been around for a long time in some variation.  The way I saw it this weekend was:

QSY on rig 1 --> clears DI window for rig 2 (problem with this one)
QSY on rig 2 --> clears DI window for rig 2 (correct function)

73/jeff/ac0c
alpha-charlie-zero-charlie
www.ac0c.com