Topics

Numbering of QSO, SntNR, resets after each period.

Jaan, SM9X
 

Hi, my first public post here.
I have been running same test a long time now without any problems. Now something has gone wrong.
The test I'm running is MINITESTCW The rules are each CallSign is a multiplier and can be worked once every 10 minutes period under 60 minutes. The exchange is RST + Serial No.
After exactly 10 minutes my Serial No. (SntNr) starts from from 001 again instead of increasing as in my case with 017. See example from my log:

 

QSO:  7027 CW 2018-04-11 1708 SM9X          599  015  UA4CBJ        599  013
QSO:  7027 CW 2018-04-11 1709 SM9X          599  016  UA4AQL        599  021
QSO:  7018 CW 2018-04-11 1711 SM9X          599  001  UA4AQL        599  022
QSO:  7019 CW 2018-04-11 1711 SM9X          599  002  RT3A          599  029

I'm running on N1MM+ V1.0.7147.0

73 de Jaan, SM9X

Steve London
 

Are you sure that you don't accidentally have a User Defined Contest loaded, rather than MINITESTCW ?

73,
Steve, N2IC

On 04/12/2018 12:35 AM, swejaan@... wrote:
Hi, my first public post here.
I have been running same test a long time now without any problems. Now something has gone wrong.
The test I'm running is MINITESTCW The rules are each CallSign is a multiplier and can be worked once every 10 minutes period under 60 minutes. The exchange is RST + Serial No.
After exactly 10 minutes my Serial No. (SntNr) starts from from 001 again instead of increasing as in my case with 017. See example from my log:
QSO:  7027 CW 2018-04-11 1708 SM9X          599  015  UA4CBJ        599  013
QSO:  7027 CW 2018-04-11 1709 SM9X          599  016  UA4AQL        599  021
QSO:  7018 CW 2018-04-11 1711 SM9X          599 001  UA4AQL        599  022
QSO:  7019 CW 2018-04-11 1711 SM9X          599  002  RT3A          599  029
I'm running on N1MM+ V1.0.7147.0
73 de Jaan, SM9X

Jaan, SM9X
 

I have checked that in my userDefinontest folder. No such file there.

regards, Jaan

SM9X

Steve London
 

Do you ever use User Defined Contests ?

Is it possible that a User Defined Contest was loaded or used before MINITESTCW ?

73,
Steve, N2IC

On 04/12/2018 10:27 AM, Jaan, SM9X wrote:
I have checked that in my userDefinontest folder. No such file there.
regards, Jaan
SM9X
_._,_._,_

Gerald Boutin (VE1DT)
 
Edited

Jaan,

I checked here setting up the contest for today at 1700z and the QSO numbering works as it should. At each ten minute mark, the stations in the bandmap that I entered as working in the previous 10 minute section change color to workable again. The next sent number does NOT get set back to 1. I am using v.1.0.7149.0, but I doubt that would make any difference.

I cannot explain why it did not work for you. Did it reset the SntNr every 10 minutes, or was this just a single instance?

Perhaps you could try it again now and make some fake QSOs by entering callsigns and serial numbers and using the log button to log the qso. That way the radio does not have to transmit. Does it still reset the sent number every 10 minutes?
--
Gerald, VE1DT

Jaan, SM9X
 

Good morning.
I have been running this test four times on two different updates, v.1.0.7147.0  and the previous. The problem occured all the time. The MINITESTCW sets my SntNr to 001 after exactly 10 minutes through out the whole test. That is five times in 1h.

I had another question from Steve N2IC asking if I'm using one of my User Defind Contest? No, I have no user defind contest with that name. However I have a few that I have been playing around with but twith completely different naming.

I will try this weekend and do a simulation and run the above test on latest upgrade like you suggested Gerald.

Is there any chance or possibility to remove any file that could cause this problem, .ini or other file that could cause some confusion when running this or any other test?
73 de Jaan
SM9X

Jaan, SM9X
 

Sorry Steve, I was in a hurry.
Before MINITESTCW I was using a User Defind Contest that I downloaded, OK1WC.udc Could that affect settings you mean?

Cheers!

Jaan

NA3M Nick
 

Jaan,

 

    I looked at OK1WC.udc and there is nothing that could cause the problem you described. I suspect something else is setting CIsSNPerSession parameter to True in the logger when you run it.

I prepared experimental version located here:

 

http://n1mm.hamdocs.com/tiki-list_file_gallery.php?galleryId=20

 

Let us know if this will fix the problem.

 

Nick NA3M

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Jaan, SM9X
Sent: Friday, April 13, 2018 2:26 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] Numbering of QSO, SntNR, resets after each period.

 

Sorry Steve, I was in a hurry.
Before MINITESTCW I was using a User Defind Contest that I downloaded, OK1WC.udc Could that affect settings you mean?

Cheers!

Jaan

_._,_._,_


 

Jaan, SM9X
 

Hi, just did some testing on experimental version, same issue as Before, after 10 minutes I got serial 001

 

QSO:  3537 CW 2018-04-14 1309 SM9X          599  010  YO8TTT        599  011 
QSO:  3537 CW 2018-04-14 1310 SM9X          599  001  SE5L          599  012

Regards, Jaan

SM9X

NA3M Nick
 

Jaan,

 

Are you sure you were using this experimental version: N1MM Logger+ Update 1.0.7149 UDC
For testing 10 minute SN reset problem (SM9X)?

 

I can see that it was not downloaded it yet (0 downloads).

 

Nick NA3M

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Jaan, SM9X
Sent: Saturday, April 14, 2018 9:14 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] Numbering of QSO, SntNR, resets after each period.

 

Hi, just did some testing on experimental version, same issue as Before, after 10 minutes I got serial 001

 

QSO:  3537 CW 2018-04-14 1309 SM9X          599  010  YO8TTT        599  011 
QSO:  3537 CW 2018-04-14 1310 SM9X          599  001  SE5L          599  012

Regards, Jaan

SM9X

Jaan, SM9X
 

Good morning Nick
I just downloaded your V1.0.7149 and tested it for 11 minutes and I got the serial back to 001 after ten minutes. Before that I accidentally took the 7199....

Regards, Jaan

2018-04-14 17:41 GMT+02:00 NA3M Nick <na3m@...>:

Jaan,

 

Are you sure you were using this experimental version: N1MM Logger+ Update 1.0.7149 UDC
For testing 10 minute SN reset problem (SM9X)?

 

I can see that it was not downloaded it yet (0 downloads).

 

Nick NA3M

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Jaan, SM9X
Sent: Saturday, April 14, 2018 9:14 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] Numbering of QSO, SntNR, resets after each period.

 

Hi, just did some testing on experimental version, same issue as Before, after 10 minutes I got serial 001

 

QSO:  3537 CW 2018-04-14 1309 SM9X          599  010  YO8TTT        599  011 
QSO:  3537 CW 2018-04-14 1310 SM9X          599  001  SE5L          599  012

Regards, Jaan

SM9X


Jaan, SM9X
 

Good afternoon.
I tried the V1.0.7149.0 on another PC and it works fine, no problems with numbering. Difference is on the one where I see the numbering, SntNR, issue restarting from 001 after ten minutes is on a Windows 10 and the one I just tested OK on is Windows 7. Don't know if that makes any sense, anyway, just to let you know.

Regards, Jaan
SM9X

Jaan, SM9X
 

Hi
I just now tried a earlier version V1.0.6963 and it works perfectly well, SntNR increments as expected. On latest version V1.0.7157 the issue still remains with reset of SntNR. Hope this helps you to find where the issue occured later in your releases.

Regards, Jaan
SM9X

NA3M Nick
 

Hi Jaan,

 

  This appears to be isolated to your computer. Let’s take it off the list. I will send you a few questions in direct email.

 

Nick NA3M

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Jaan, SM9X
Sent: Tuesday, April 17, 2018 12:54 PM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] Numbering of QSO, SntNR, resets after each period.

 

Hi
I just now tried a earlier version V1.0.6963 and it works perfectly well, SntNR increments as expected. On latest version V1.0.7157 the issue still remains with reset of SntNR. Hope this helps you to find where the issue occured later in your releases.

Regards, Jaan
SM9X