Date   
Re: FT8 and RU Practice

John H. Long Jr.
 

Both good questions.
I am looking forward to see the answers.
 
 
 
John H. Long Jr.
KW7A
1370 N 150 E
Nephi, UT 84648
USA
 
(435) 888-LONG
 
 

--------- Original Message ---------
Subject: Re: [N1MMLoggerPlus] FT8 and RU Practice
From: "Barry Bettman" <k6st@...>
Date: 11/17/18 8:16 am
To: "N1MMLoggerPlus@groups.io" <N1MMLoggerPlus@groups.io>

That’s a great question. In addition how do you integrate n1mm logger + with WSJT-x for ft8?

On Saturday, November 17, 2018, David AD4TJ via Groups.Io <ad4tj=yahoo.com@groups.io> wrote:
 
 
Ok, getting ready to set up for Monday night's ARRL RTTY FT8 RU practice session. Do I use the ARRL RTTY RU template in N1MM for the WSJTX FT8 contacts? If I do, then N1MM will show dupes; if I don't, and only upload my log to LOTW and my logging proram later, it won't show dupes. Thoughts? I am not a genius when it comes to N1MM+.
 
73, David AD4TJ

 

 



--
 
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: FT8 and RU Practice

Barry Bettman
 

That’s a great question. In addition how do you integrate n1mm logger + with WSJT-x for ft8?


On Saturday, November 17, 2018, David AD4TJ via Groups.Io <ad4tj=yahoo.com@groups.io> wrote:


Ok, getting ready to set up for Monday night's ARRL RTTY FT8 RU practice session. Do I use the ARRL RTTY RU template in N1MM for the WSJTX FT8 contacts? If I do, then N1MM will show dupes; if I don't, and only upload my log to LOTW and my logging proram later, it won't show dupes. Thoughts? I am not a genius when it comes to N1MM+.

73, David AD4TJ



--

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

FT8 and RU Practice

David AD4TJ
 



Ok, getting ready to set up for Monday night's ARRL RTTY FT8 RU practice session. Do I use the ARRL RTTY RU template in N1MM for the WSJTX FT8 contacts? If I do, then N1MM will show dupes; if I don't, and only upload my log to LOTW and my logging proram later, it won't show dupes. Thoughts? I am not a genius when it comes to N1MM+.

73, David AD4TJ

R: [N1MMLoggerPlus] Spectrum display : visual offset #spectrum

Rick I2BRT
 

I’ll check this with VA2FSQ (father of Win4YAESU).

Thank you so much for pointing me in the right direction.

Best 73

Rick I2BRT

 

 

 

Da: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io> Per conto di ve3ki
Inviato: sabato 17 novembre 2018 15:25
A: N1MMLoggerPlus@groups.io
Oggetto: Re: [N1MMLoggerPlus] Spectrum display : visual offset #spectrum

 

N1MM+, MMTTY, DX clusters and most amateur radios in FSK mode use the Mark frequency; fldigi uses the centre frequency. Perhaps Win4Yaesu is aligning on the centre frequency instead of the Mark frequency. You'd have to check with Tim va2fsq.

73,
Rich VE3KI


On Sat, Nov 17, 2018 at 08:50 AM, Rick I2BRT wrote:

HI RICH !
Many thanks for your fast response.

Yes, display frequency on the rig is 14088.01 (same is reported on N1mm).
Yes, FT5K is in RTTY mode (mean FSK) and so VFO should display Mark (carirer with 2125 Hz offest).
Yoy're right , Mark tone should be at 14.088.01 and space -170 Hz (RTTY-Lsb), 14.087.84
Based on this thoughts , I agee that N1MM is correctly drawing the lines on specturm display (while the peaks are wrong).
In Win4YAESU I see now that there is one "global offset" in Scope control panel.
Tried that.


Worked, it moves up/down the drawing of the spectrum.
Correction appears to be more then 170:2, close more or less to -140 Hz (strange… in not 85 I was think to 170 but maybe there are other variables in the equation).

However … I got two new problems now :-) 
I guess "Global offset" means "for every mode", so maybe now in SSB/AM it could be wrong (no mode offset in Win4Yaesu).
I guess the receiver Width passband on Win4Yaesu scope (the grey area) is now offset by my "Global offset"
Am I wrong ?
However I think I also need the help of the "other" TOM :-) mean va2fsq

Rick I2BRT.


Re: Spectrum display : visual offset #spectrum

ve3ki
 

N1MM+, MMTTY, DX clusters and most amateur radios in FSK mode use the Mark frequency; fldigi uses the centre frequency. Perhaps Win4Yaesu is aligning on the centre frequency instead of the Mark frequency. You'd have to check with Tim va2fsq.

73,
Rich VE3KI


On Sat, Nov 17, 2018 at 08:50 AM, Rick I2BRT wrote:
HI RICH !
Many thanks for your fast response.

Yes, display frequency on the rig is 14088.01 (same is reported on N1mm).
Yes, FT5K is in RTTY mode (mean FSK) and so VFO should display Mark (carirer with 2125 Hz offest).
Yoy're right , Mark tone should be at 14.088.01 and space -170 Hz (RTTY-Lsb), 14.087.84
Based on this thoughts , I agee that N1MM is correctly drawing the lines on specturm display (while the peaks are wrong).
In Win4YAESU I see now that there is one "global offset" in Scope control panel.
Tried that.


Worked, it moves up/down the drawing of the spectrum.
Correction appears to be more then 170:2, close more or less to -140 Hz (strange… in not 85 I was think to 170 but maybe there are other variables in the equation).

However … I got two new problems now :-) 
I guess "Global offset" means "for every mode", so maybe now in SSB/AM it could be wrong (no mode offset in Win4Yaesu).
I guess the receiver Width passband on Win4Yaesu scope (the grey area) is now offset by my "Global offset"
Am I wrong ?
However I think I also need the help of the "other" TOM :-) mean va2fsq

Rick I2BRT.



Re: Spectrum display : visual offset #spectrum

Rick I2BRT
 

HI RICH !
Many thanks for your fast response.

Yes, display frequency on the rig is 14088.01 (same is reported on N1mm).
Yes, FT5K is in RTTY mode (mean FSK) and so VFO should display Mark (carirer with 2125 Hz offest).
Yoy're right , Mark tone should be at 14.088.01 and space -170 Hz (RTTY-Lsb), 14.087.84
Based on this thoughts , I agee that N1MM is correctly drawing the lines on specturm display (while the peaks are wrong).
In Win4YAESU I see now that there is one "global offset" in Scope control panel.
Tried that.


Worked, it moves up/down the drawing of the spectrum.
Correction appears to be more then 170:2, close more or less to -140 Hz (strange… in not 85 I was think to 170 but maybe there are other variables in the equation).

However … I got two new problems now :-) 
I guess "Global offset" means "for every mode", so maybe now in SSB/AM it could be wrong (no mode offset in Win4Yaesu).
I guess the receiver Width passband on Win4Yaesu scope (the grey area) is now offset by my "Global offset"
Am I wrong ?
However I think I also need the help of the "other" TOM :-) mean va2fsq

Rick I2BRT.



Re: rtty fldigi Pseudo FSK issue

Joe Subich, W4TV
 

Fldigi waterfall frequency (center after align): 21083.28 MHz, this is correct according to sweet spot of 2200 Hz
Sweet spot should be 2210 ((2125+2295)/2). You might also need to
specify *-*2210 for LSB.

73,

... Joe, W4TV


On 2018-11-17 3:22 AM, iz1fks wrote:
Hi, this is the behaviour I have detected with latest version in RTTY using FLDIGI. hope this could be a simple fix.
73 de Phil, iz1fks/ai4yn
Radio: IC-756proII
FLDIGI: 4.0.18
N1mm: last release, 1.0.7342.0
Radio mode: RTTY (LSB)
Radio VFO: 21085.48 MHz
Fldigi waterfall frequency (center after align): 21083.28 MHz, this is correct according to sweet spot of 2200 Hz
*Frequency in bandmap and in n1mm main window is not correct with RTTY (lsb mode).*

Re: Spectrum display : visual offset #spectrum

ve3ki
 

Based on the information in your screen shot, I believe that the frequency displayed on your rig's dial is 14088.01 kHz. If so, and if the rig is in FSK mode, then the two peaks in the spectrum/waterfall should be at 14087.84 kHz and 14088.01 kHz (the rig's dial frequency is the Mark frequency, and the Space frequency is 170 Hz lower). The vertical lines in the N1MM+ spectrum display window are placed on these two frequencies (the program uses the radio's dial reading to place the vertical lines).

The two peaks in the Win4Yaesu spectrum/waterfall display are 85 Hz higher than this, i.e. the labels in the Win4Yaesu display appear to be wrong by 85 Hz. The spectrum/waterfall data in the N1MM+ spectrum display comes from Win4Yaesu, and that is why the peaks appear where they do.

Is there a mode-specific IF offset setting in Win4Yaesu? If there is an offset setting in Win4Yaesu, it looks to me as if the setting for RTTY is wrong by 85 Hz. Try adding or subtracting 85 Hz to/from the setting in order to line up the spectrum peaks in the Win4Yaesu display so that the higher-frequency (Mark) peak is labelled with the same frequency in the Win4Yaesu display as the frequency you see on the radio's dial. If you do this, the two peaks in the N1MM+ spectrum display should fall on the vertical lines in the display.

73,
Rich VE3KI



On Sat, Nov 17, 2018 at 07:07 AM, Rick I2BRT wrote:
HI !

My setup :
  • FT-5000 (set for FRSK and to use high tones for RTTY)
  • IF OUT SdrPlay RSP2
  • Win4Yaesu (set to use RSP2 from IF out)
  • Navigator as FSK interface and soundcard
  • MMTTY
  • N1MM
All ok.

Just one thing I can't explain.
While in RTTY and perfectly tuned a station (mean : decode correctly and XY scope centered) the Spectum display seems to be centered just only around one of the tones.
"Visually" I would like to have the signal centered in green are (green verticals lines around mark and space).
Is there any place where I can try to adjust this ?

See image to better clarify what I mean 




Many thanks indeed
Rick I2BRT (formerly iu2fgb)

Re: rtty fldigi Pseudo FSK issue

ve3ki
 

In the DI window's Setup menu, is the option "Turn AutoTRX Offset On" option checked? If your rig displays the actual Mark frequency on its dial (as most rigs do in FSK mode), then this option should not be checked. It should only be checked if your rig is in a mode like LSB or USB where it displays the suppressed carrier (BFO) frequency. There is also a check box in the DI Settings window called "Display Radio Freq and not Exact Freq in DI Caption". If your radio displays the actual Mark frequency on its dial, this check box should be checked; if your radio displays the suppressed carrier frequency, this check box should be unchecked.

73,
Rich VE3KI



On Sat, Nov 17, 2018 at 05:23 AM, iz1fks wrote:

Hi, this is the behaviour I have detected with latest version in RTTY using FLDIGI. hope this could be a simple fix.
73 de Phil, iz1fks/ai4yn

Radio: IC-756proII

FLDIGI: 4.0.18

N1mm: last release, 1.0.7342.0

Radio mode: RTTY  (LSB)

Radio VFO: 21085.48 MHz

Fldigi waterfall frequency (center after align): 21083.28 MHz, this is correct according to  sweet spot of 2200 Hz
F
requency in bandmap and in n1mm main window is not correct with RTTY (lsb mode).


Spectrum display : visual offset #spectrum

Rick I2BRT
 

HI !

My setup :
  • FT-5000 (set for FRSK and to use high tones for RTTY)
  • IF OUT SdrPlay RSP2
  • Win4Yaesu (set to use RSP2 from IF out)
  • Navigator as FSK interface and soundcard
  • MMTTY
  • N1MM
All ok.

Just one thing I can't explain.
While in RTTY and perfectly tuned a station (mean : decode correctly and XY scope centered) the Spectum display seems to be centered just only around one of the tones.
"Visually" I would like to have the signal centered in green are (green verticals lines around mark and space).
Is there any place where I can try to adjust this ?

See image to better clarify what I mean 




Many thanks indeed
Rick I2BRT (formerly iu2fgb)

Re: rtty fldigi Pseudo FSK issue

iz1fks
 

Hi, this is the behaviour I have detected with latest version in RTTY using FLDIGI. hope this could be a simple fix.
73 de Phil, iz1fks/ai4yn

Radio: IC-756proII

FLDIGI: 4.0.18

N1mm: last release, 1.0.7342.0

Radio mode: RTTY  (LSB)

Radio VFO: 21085.48 MHz

Fldigi waterfall frequency (center after align): 21083.28 MHz, this is correct according to  sweet spot of 2200 Hz
F
requency in bandmap and in n1mm main window is not correct with RTTY (lsb mode).


SO2R RX button not shown on 2nd radio window when listening on both radios

Art Suberbielle
 

Hi all,

 

I use a DX-Doubler with the latest version of N1MM+ on my Windows 7 computer. During the last few versions, I've noticed that there is no visual indication of RX on the inactive radio when I use the Tilde key to listen to both radios simultaneously. The green button is not illuminated although the DX-D Green lights do show both RXs are on. 

 

Was this feature eliminated in a version? I'm fairly certain it did indicate on N1MM+ when both RXs are on.


Thanks for  your help.


73,


Art KZ5D

N1MM+ Sweepstakes

Hank Garretson
 

To make Parsed Text above Exchange Textbox easier to read, try

Config, Manage Skins

Colors, and Fonts ...

Fonts

Smaller - buttons, small labels, Bandmap Window callsigns

Left click

Consolas   Bold   12

Save

Contest Exuberantly,

Hank, W6SX

Re: SntNR 001 twice

'Zaba' OH1ZAA
 

Hello Rich!

Thanks for the great clarifications! It is certainly difficult to
write software for a public (mis)using it in many various ways and
with a vast pallet of equipment. My problem listing these issues
earlier, is that I am running many contests SOSB with parallel
call signs on other bands, and for that I am running Win-test
in parallel, as N1MM+ is not keeping track of the own call sign
change with a band change (in this case a log change). Win-test
binds a call sign with a new log upon log init. Due to this
multi-tasking I was many times not sure afterward whether I had
issues with N1MM+ or Win-test. Now with some years of use I am
pretty sure things I write here are related to N1MM+.


Recently I read also here that changing logs is fast in N1MM+
with the Alt + F + number sequence. It helps but I have to
configure the station call sign as well separately.

Please someone check it but I have NEVER seen a change in the
total score summary during the last two years in the lower right
corner of the box during or after a re-score. It only shows the
new score after completely shutting N1MM+ and firing it up again.

OKOMDX CW is now OK, I made some comments about it in today's
other thread. It took multiple steps to get the old log right.

Cheers/73, Zaba OH1ZAA


P.S. Some extra's:

NRAU10M displays the wrong modes: the right ones are
CW / SSB / FM / RTTY for subsequent hours

Also it complains I am logging on the wrong band, even
while having 28 MHz set as band, and it requires a lengthy
confirmation process for doing it (the logging) anyway.


ve3ki kirjoitti 16.11.2018 15:02:

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
Links:
------
[1] https://groups.io/g/N1MMLoggerPlus/message/37889
[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

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