Date   

Re: Error???

Carol Richards
 


John,
 
 
I checked everything by hand. Using the 2 points per cw qso and 1 point per ssb qso, I got 1392 points. When that was multiplied by 67( the actual number of mults), my score came exactly out to 93,364. The 100 bonus points were never included.
 
 
 
Carol


Re: Changing from one contest to another

Steve K8JQ
 

John,

Been playing around with it some. I have six windows open: entry, check, bandmap, log ,multipliers => counties/other, telnet. When I change contests the multipliers window gets the focus instead of the entry window.

If I close the multipliers window and change contests, the focus goes to the entry window's callsign field. Something about the multipliers window?

Steve, K8JQ

On 9/20/2015 8:25 PM, 'John Bednar' k3ct@... [N1MMLoggerplus] wrote:
 

Steve,

 

This version contains all of the updates. When the Entry window returns focus (tuning the radio or clicking on the frame) the cursor should return to the same text box.

 

I placed the cursor in the Callsign box and switched contests a dozen times. The cursor always stayed in the Callsign box. If the Entry window focus changed to another window and back to the Entry window, the cursor always returned to the Callsign box. This is the expected behavior.

 

I saw the behavior you described in older program versions. I am unable to reproduce your report with version 1.0.5176.

 

John, K3CT

 

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Sunday, September 20, 2015 12:16 PM
To: N1MMLoggerplus@...
Subject: Re: [N1MMLoggerplus] Changing from one contest to another

 

 

Using 5176.

Steve, K8JQ

On 9/20/2015 10:40 AM, John Bednar k3ct@... [N1MMLoggerplus] wrote:

 

Steve, 

Are you using the latest program version? 

 

John, K3CT

-------- Original message --------

From: "Steve steve65@... [N1MMLoggerplus]"

Date:09/20/2015 10:18 AM (GMT-05:00)

Subject: [N1MMLoggerplus] Changing from one contest to another

 

 

I've bounced between the SC QSO Party and the NJ QSO Party this weekend.
When I use Alt+F+2 to change to the other contest, the cursor is not in
the call sign field of the Entry Window. It is necessary to use the
mouse to right click in the call sign field to be able to enter data
into it. When changing contests in this fashion, could the cursor be
placed in the call sign field and ready for data entry?

Steve, K8JQ

 



Re: So Carolina QSO party

John Bednar
 

Tom,

 

Are you looking at the Log window or the Score window?

 

I opened a new SC QSO party contest, logged W4CAE and WW4SF on CW in two different Counties. The Score window and Cabrillo output both list the score as 858 points. There are four QSO points, two multipliers, and 850 bonus points. This is correct.

 

John, K3CT

9.4. Final Score

Final Score = [Total QSO Points x Multipliers] + Bonus Station Points

 

 

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Sunday, September 20, 2015 7:48 AM
To: N1MMLoggerplus@...
Subject: [N1MMLoggerplus] So Carolina QSO party

 

 

v.5176 NL+
SC QP

When opening NL+ to the SCQP, a pop-up opens stating that W4CAE and WW4SF
are bonus stations. W4CAE should be a 500 point bonus and WW4SF should be a
350 point bonus, however NL+ gives them 2 points. In the edit QSO pop-up,
points can not be updated, so how can I correct the score or is it left up
to the SC adjudicator to make the changes?

73,
Tom - W4BQF


Re: Changing from one contest to another

John Bednar
 

Steve,

 

This version contains all of the updates. When the Entry window returns focus (tuning the radio or clicking on the frame) the cursor should return to the same text box.

 

I placed the cursor in the Callsign box and switched contests a dozen times. The cursor always stayed in the Callsign box. If the Entry window focus changed to another window and back to the Entry window, the cursor always returned to the Callsign box. This is the expected behavior.

 

I saw the behavior you described in older program versions. I am unable to reproduce your report with version 1.0.5176.

 

John, K3CT

 

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Sunday, September 20, 2015 12:16 PM
To: N1MMLoggerplus@...
Subject: Re: [N1MMLoggerplus] Changing from one contest to another

 

 

Using 5176.

Steve, K8JQ

On 9/20/2015 10:40 AM, John Bednar k3ct@... [N1MMLoggerplus] wrote:

 

Steve, 

Are you using the latest program version? 

 

John, K3CT

-------- Original message --------

From: "Steve steve65@... [N1MMLoggerplus]"

Date:09/20/2015 10:18 AM (GMT-05:00)

Subject: [N1MMLoggerplus] Changing from one contest to another

 

 

I've bounced between the SC QSO Party and the NJ QSO Party this weekend.
When I use Alt+F+2 to change to the other contest, the cursor is not in
the call sign field of the Entry Window. It is necessary to use the
mouse to right click in the call sign field to be able to enter data
into it. When changing contests in this fashion, could the cursor be
placed in the call sign field and ready for data entry?

Steve, K8JQ

 


Re: Error???

John Bednar
 

Carol,

 

I tested with a recent program version and logging K2TD adds 100 points to the score.

 

The score is calculated with this equation (QSO points x  Mults) + Bonus Points.

 

The Log window displays QSO points. Are you looking at the Log window or the Score window?

 

John, K3CT

 

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Sunday, September 20, 2015 4:18 PM
To: N1MMLoggerplus@...
Subject: [N1MMLoggerplus] Re: Error???

 

 



Hello,

 

I just finished the NJQP. K2TD is supposed to be a 100 point bonus qso. N1MM+  only gave me 2 points!

 

 

Carol


Re: Automatic update > everything is now lost, gone!

Pete Smith N4ZR <n4zr@...>
 

Bengt, please be patient.  I have 69 QSOs from your SAC log, in the Do not Use or Erase database you sent me, plus 14 of your transaction logs to recover, each of which must be loaded into a separate database.  This just takes time.

Please remember, this is a direct result of your error in using the Do Not Use or Erase database to log QSOs for some 10 months. and 15 contests.

I am sending you a database containing your SAC log by direct e-mail.  The rest will follow.
73, Pete N4ZR
Download the new N1MM Logger+ at 
. Check 
out the Reverse Beacon Network at 
, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 9/20/2015 3:09 PM, sm6fud@... [N1MMLoggerplus] wrote:

Sent you the zip file, Pete.

Starting up NL+ after comp been turned off and on again some few hours later my complete log of SAC is totally gone. NL+ again told me to fill in my stats and make a new database. Tiresome as it is I went for it. Still no old logs. Hence no SAC result from this weekend big scenario to send in for participating...

I'm out of this for now...

73 - Bengt SM6FUD


Re: Error???

Carol Richards
 


Hello,
 
I just finished the NJQP. K2TD is supposed to be a 100 point bonus qso. N1MM+  only gave me 2 points!
 
 
Carol


Re: Automatic update > everything is now lost, gone!

Bengt Christensen
 

Sent you the zip file, Pete.

Starting up NL+ after comp been turned off and on again some few hours later my complete log of SAC is totally gone. NL+ again told me to fill in my stats and make a new database. Tiresome as it is I went for it. Still no old logs. Hence no SAC result from this weekend big scenario to send in for participating...

I'm out of this for now...

73 - Bengt SM6FUD


Re: WAE QTC

Al - N1API
 

Works with a simple 11 call file sending 10 QTCs to number 11 and then going back to contact number 1 for one QTC and it works.  Should be good on larger logs.

Al


Those of you that were having trouble with not being able to send all of
your QTC.. Please try the latest version and let me know if this corrects
the issue or not. In my testing it was sending all of the available QTC.

73 Rick n2AMG


Re: WAE QTC

Nathan Moreschi
 

Rick,

I just checked, and the QTC problems seem to be fixed.

Nice work.

73,

Nate/N4YDU

On 9/20/2015 1:46 PM, Rick Ellison rellison@... [N1MMLoggerplus] wrote:
�

Those of you that were having trouble with not being able to send all of
your QTC.. Please try the latest version and let me know if this corrects
the issue or not. In my testing it was sending all of the available QTC.

73 Rick n2AMG



Re: In split sending wrong RST

gbyahoo@...
 

Greg,

To check the mode, it would be easier just to rt-click a QSO and "Edit Contact" to see the mode info instead of the gyrations I suggested for looking at it in the Log window.

>> Gerald, VE1DT


WAE QTC

Rick Ellison
 

Those of you that were having trouble with not being able to send all of
your QTC.. Please try the latest version and let me know if this corrects
the issue or not. In my testing it was sending all of the available QTC.

73 Rick n2AMG


Re: In split sending wrong RST

gbyahoo@...
 

Greg,

What radio are you using? Current version of N1MM+ ?

Also, what mode does the QSO with the 59 report get logged as? You say the vfo is in cw mode, but is that getting communicated to N1MM+?

You might have to rt-click the log window and set the show mode option and after that you might also have to auto-set the column widths of remove custom settings, if necessary to be able to see the mode stored in the log.

>> Gerald, VE1DT


---In N1MMLoggerplus@..., <ve3ki@...> wrote :

This sure sounds like a case where the two VFOs are in different modes. I don't know about your radio, but with some, having both VFOs on the same frequency and in the CW portion of the band does *not* guarantee that both VFOs are in CW mode. On the Elecraft K3/K3S, for example, you have to tap the A>B button twice in rapid succession to transfer the mode to the second VFO. A single tap of A>B transfers the frequency but leaves the second VFO in whatever mode it was in previously, i.e. the two VFOs can be in different modes even when they are on the same frequency. The program detects this, and will take its mode from the transmit VFO (VFO B in Split mode).

73,
Rich VE3KI


---In N1MMLoggerplus@..., <gregg.w6izt@...> wrote :

Gerald:

 

Thanks for your reply. Mode control is set to Use Radio. This occurs when the radio is in split, even if both VFOs are in the CW portion of the band and on the same frequency.

 

73

Gregg w6izt

 

From: gbyahoo@... [N1MMLoggerplus] [mailto:N1MMLoggerplus@...]
Sent: Sunday, September 20, 2015 1:47 PM
To: N1MMLoggerplus@...
Subject: RE: [N1MMLoggerplus] In split sending wrong RST

 

 

Greg,


This usually indicates that there is a problem with your Mode control / bandplan settings. The manual explains it in detail, but if you expect the program to use the radio mode, you either want the default setting for Mode Control, or the bandplan needs to match up with your expectations if you are set up to use the mode according to the bandplan.

 

For most contests that I operate, I find the most straight forward setting is the default: "Use radio mode".

 

>> Gerald, VE1DT

 


---In N1MMLoggerplus@..., <gregg.w6izt@...> wrote :

Uusing L+, mode=CW, when in split (both VFOs on CW) L+ auto populates the sent and rec RST as 59. When operating simplex the sent and rec RST is auto populated correctly with 599

 

V1.1.5176. Log type “DX”. Changing the category has no effect. Perhaps I’m missing something? Any assistance is appreciated

 

73

Gregg w6izt


1.0.5210

N1MM <tfwagner@...>
 

Version 1.0.5210 (September 20, 2015)

1. CW Sprint: Could not log a DX prefix (many) (Coded by N1MM)
2. Entry Window highlighting: set the foreground color properly for
darker colors (K3CT) (Coded by N1MM)
3. QTC Window: Corrects counting of remaining QTC should stop not
transmitting all QTC. (Coded by N2AMG)
4. QTC Window: Adds a TU Message Box to the CW Setup tab of the QTC
setup window. This will be sent when exiting QTC window after
exchanging QTC. Supports all N1MM Macro Substitutions. No longer
will use the Entry Window F3 message. (Coded by N2AMG)
5. QTC Window: Adds WAETu.wav to messages that are sent when Use Voice
Messages is checked. This will be sent when exiting QTc Window aftr
exchanging QTC. (Coded by N2AMG)
6. QTC Window: Moves most of the QTC Settings to the Setup window
within the QTC Window. CW, SSB, RTTY. (Coded by N2AMG)
7. QTC Window: Provides a menu on the Entry Window to access the QTC
Setup window. Config/WAE/Open QTC Window Setup (Coded by N2AMG)
8. QTC Window: On SSB Setup tab provides location to where wav files
should be located and a means to Play and Record the wav files.
(This will only work if Use Logger + Audio is selected.) (Coded by
N2AMG)
9. Updates Fldigi Fldg.dll file (Coded by W1TR)
10. Com/LPT Configuration dialog: was not using proper skin colors
(LY5T) (Coded by N1MM)
11. If user was mistakenly using Do_Not_Use_Or_Erase.s3db as their
database, make the user change the name. (Coded by N2IC)


Re: Changing from one contest to another

Steve K8JQ
 

Using 5176.

Steve, K8JQ

On 9/20/2015 10:40 AM, John Bednar k3ct@... [N1MMLoggerplus] wrote:
 
Steve, 
Are you using the latest program version? 

John, K3CT

-------- Original message --------
From: "Steve steve65@... [N1MMLoggerplus]"
Date:09/20/2015 10:18 AM (GMT-05:00)
Subject: [N1MMLoggerplus] Changing from one contest to another

 

I've bounced between the SC QSO Party and the NJ QSO Party this weekend.
When I use Alt+F+2 to change to the other contest, the cursor is not in
the call sign field of the Entry Window. It is necessary to use the
mouse to right click in the call sign field to be able to enter data
into it. When changing contests in this fashion, could the cursor be
placed in the call sign field and ready for data entry?

Steve, K8JQ



Re: In split sending wrong RST

ve3ki@...
 

This sure sounds like a case where the two VFOs are in different modes. I don't know about your radio, but with some, having both VFOs on the same frequency and in the CW portion of the band does *not* guarantee that both VFOs are in CW mode. On the Elecraft K3/K3S, for example, you have to tap the A>B button twice in rapid succession to transfer the mode to the second VFO. A single tap of A>B transfers the frequency but leaves the second VFO in whatever mode it was in previously, i.e. the two VFOs can be in different modes even when they are on the same frequency. The program detects this, and will take its mode from the transmit VFO (VFO B in Split mode).

73,
Rich VE3KI


---In N1MMLoggerplus@..., <gregg.w6izt@...> wrote :

Gerald:

 

Thanks for your reply. Mode control is set to Use Radio. This occurs when the radio is in split, even if both VFOs are in the CW portion of the band and on the same frequency.

 

73

Gregg w6izt

 

From: gbyahoo@... [N1MMLoggerplus] [mailto:N1MMLoggerplus@...]
Sent: Sunday, September 20, 2015 1:47 PM
To: N1MMLoggerplus@...
Subject: RE: [N1MMLoggerplus] In split sending wrong RST

 

 

Greg,


This usually indicates that there is a problem with your Mode control / bandplan settings. The manual explains it in detail, but if you expect the program to use the radio mode, you either want the default setting for Mode Control, or the bandplan needs to match up with your expectations if you are set up to use the mode according to the bandplan.

 

For most contests that I operate, I find the most straight forward setting is the default: "Use radio mode".

 

>> Gerald, VE1DT

 


---In N1MMLoggerplus@..., <gregg.w6izt@...> wrote :

Uusing L+, mode=CW, when in split (both VFOs on CW) L+ auto populates the sent and rec RST as 59. When operating simplex the sent and rec RST is auto populated correctly with 599

 

V1.1.5176. Log type “DX”. Changing the category has no effect. Perhaps I’m missing something? Any assistance is appreciated

 

73

Gregg w6izt


Re: In split sending wrong RST

Gregg Marco W6IZT
 

Gerald:

 

Thanks for your reply. Mode control is set to Use Radio. This occurs when the radio is in split, even if both VFOs are in the CW portion of the band and on the same frequency.

 

73

Gregg w6izt

 

From: gbyahoo@... [N1MMLoggerplus] [mailto:N1MMLoggerplus@...]
Sent: Sunday, September 20, 2015 1:47 PM
To: N1MMLoggerplus@...
Subject: RE: [N1MMLoggerplus] In split sending wrong RST

 

 

Greg,


This usually indicates that there is a problem with your Mode control / bandplan settings. The manual explains it in detail, but if you expect the program to use the radio mode, you either want the default setting for Mode Control, or the bandplan needs to match up with your expectations if you are set up to use the mode according to the bandplan.

 

For most contests that I operate, I find the most straight forward setting is the default: "Use radio mode".

 

>> Gerald, VE1DT

 


---In N1MMLoggerplus@..., <gregg.w6izt@...> wrote :

Uusing L+, mode=CW, when in split (both VFOs on CW) L+ auto populates the sent and rec RST as 59. When operating simplex the sent and rec RST is auto populated correctly with 599

 

V1.1.5176. Log type “DX”. Changing the category has no effect. Perhaps I’m missing something? Any assistance is appreciated

 

73

Gregg w6izt


Re: Changing from one contest to another

John Bednar
 

Steve, 
Are you using the latest program version? 

John, K3CT


-------- Original message --------
From: "Steve steve65@... [N1MMLoggerplus]"
Date:09/20/2015 10:18 AM (GMT-05:00)
To: N1MMLoggerplus@...
Subject: [N1MMLoggerplus] Changing from one contest to another

 

I've bounced between the SC QSO Party and the NJ QSO Party this weekend.
When I use Alt+F+2 to change to the other contest, the cursor is not in
the call sign field of the Entry Window. It is necessary to use the
mouse to right click in the call sign field to be able to enter data
into it. When changing contests in this fashion, could the cursor be
placed in the call sign field and ready for data entry?

Steve, K8JQ


Changing from one contest to another

Steve K8JQ
 

I've bounced between the SC QSO Party and the NJ QSO Party this weekend. When I use Alt+F+2 to change to the other contest, the cursor is not in the call sign field of the Entry Window. It is necessary to use the mouse to right click in the call sign field to be able to enter data into it. When changing contests in this fashion, could the cursor be placed in the call sign field and ready for data entry?

Steve, K8JQ


Re: In split sending wrong RST

gbyahoo@...
 

Greg,

This usually indicates that there is a problem with your Mode control / bandplan settings. The manual explains it in detail, but if you expect the program to use the radio mode, you either want the default setting for Mode Control, or the bandplan needs to match up with your expectations if you are set up to use the mode according to the bandplan.

For most contests that I operate, I find the most straight forward setting is the default: "Use radio mode".

>> Gerald, VE1DT


---In N1MMLoggerplus@..., <gregg.w6izt@...> wrote :

Uusing L+, mode=CW, when in split (both VFOs on CW) L+ auto populates the sent and rec RST as 59. When operating simplex the sent and rec RST is auto populated correctly with 599

 

V1.1.5176. Log type “DX”. Changing the category has no effect. Perhaps I’m missing something? Any assistance is appreciated

 

73

Gregg w6izt