Date   

Re: ARRL RRU: a couple of issues

Dave Hachadorian
 

I also saw #1.  It interrupted normal ESM behavior. My workaround was to hit the delete key to erase the old number before clicking the new number.
 
I did not see #2 here, but my friend W7WW called me to complain about it happening at his place.
 
Dave Hachadorian, K6LL
Yuma, Arizona

 
 
 

From: Jim Miller jtmiller47@... [N1MMLoggerplus]
Sent: Monday, January 9, 2017 7:17 AM
To: N1MMLoggerplus@...
Subject: [N1MMLoggerplus] ARRL RRU: a couple of issues
 
 

1. When logging DX and getting serial numbers from them N1MM+ would complain if the serial number wasn't the same as last time as if it was considering an inconsistency in QTH. It would mark the serial numbers as RED.
 
2. N1MM+ constantly complained that Hawaii wasn't DX but rather a state which is wrong for this contest. It kept wanting a State rather than serial number.
 
I had downloaded the latest N1MM+ version available at the start of the contest.
 
73
 
jim ab3cv
 
 


Re: ARRL not accepting N1MM RU logs

Ron Castro
 

I finally figured it out...it was just the one line in the log that caused the problem.  The QSO with K0IDX did not have the state.  I added that, resubmitted, and the log was accepted.

Ron
N6IE


Re: ARRL not accepting N1MM RU logs

Dave Putman
 

I had a similar error in my log.  One Q was missing both the CALL and the STATE entries. I have no idea why this occurred, except perhaps I fat-fingered the log entry after the Q was completed. Fortunately, the Logger+ transaction log had enough information to edit the log, find and correct the problem in the log itself, then regenerate the Cabrillo for submittal.


Re: ARRL not accepting N1MM RU logs

Dave K2XR
 

You are missing K0IDX's state.
 
  73
 
 
ERROR-->Following QSO errors were found:

  • QSO: 7070 RY 2017-01-08 0055 N6IE 599 CA K0IDX 599
    number of fields in QSO line less than mininum expected(11)
WARNING-->Following QSOs were missing required exchange info. You may want to correct these when you resubmit your log.
  • QSO: 7070 RY 2017-01-08 0055 N6IE 599 CA K0IDX 599
    copied exchange (qthserial) is missing
Any ideas?

Thanks
Ron, N6IE




Re: ARRL RRU: a couple of issues

Rory Sena
 

Mine worked Hawaii and DX numbers just fine, did you update the country file by chance? Did you have the right .mc file loaded?

On Mon, Jan 9, 2017 at 6:17 AM, Jim Miller jtmiller47@... [N1MMLoggerplus] <N1MMLoggerplus@...> wrote:
 

1. When logging DX and getting serial numbers from them N1MM+ would complain if the serial number wasn't the same as last time as if it was considering an inconsistency in QTH. It would mark the serial numbers as RED.

2. N1MM+ constantly complained that Hawaii wasn't DX but rather a state which is wrong for this contest. It kept wanting a State rather than serial number.

I had downloaded the latest N1MM+ version available at the start of the contest.

73

jim ab3cv




Re: ARRL not accepting N1MM RU logs

John Bednar
 


Force logging an incorrect exchange instead of correcting it real time can be the cause.

John, K3CT 

-------- Original message --------
From: "GALE STEWARD k3nd@... [N1MMLoggerplus]" <N1MMLoggerplus@...>
Date: 1/9/17 8:51 AM (GMT-05:00)
To: N1MMLoggerplus@...
Subject: Re: [N1MMLoggerplus] ARRL not accepting N1MM RU logs

 

Hmmm, looks wrong. KoIDX, or should be K0IDX?



From: "Mike KB9BIB kb9bib@... [N1MMLoggerplus]" <N1MMLoggerplus@...>
To: N1MMLoggerplus@...
Sent: Sunday, January 8, 2017 11:34 PM
Subject: Re: [N1MMLoggerplus] ARRL not accepting N1MM RU logs

 
Does that QSO have the state when you edit the Cabrillo file? Or is it in the file and not being seen by the robot for some reason?

On Jan 8, 2017 10:25 PM, "ron@... [N1MMLoggerplus]" <N1MMLoggerplus@...> wrote:
 
I have tried several ways of submitting my log for this year's RTTY RU, but they keep getting bounced. Here are a few lines of my log:

CREATED-BY: N1MM Logger+ 1.0.6016.0
QSO: 14106 RY 2017-01-07 1815 N6IE          599 CA     WT5L          599 FL      
QSO: 14106 RY 2017-01-07 1815 N6IE          599 CA     NX8G          599 OH      
QSO: 14106 RY 2017-01-07 1815 N6IE          599 CA     AA5VU         599 TX      
QSO: 14106 RY 2017-01-07 1815 N6IE          599 CA     K2YG          599 NJ      
QSO: 14106 RY 2017-01-07 1816 N6IE          599 CA     W6EU          599 CA      
QSO: 14106 RY 2017-01-07 1817 N6IE          599 CA     NE8O/4        599 NC  

And here is what I get back from the robot:

ERROR-->Following QSO errors were found:
  • QSO: 7070 RY 2017-01-08 0055 N6IE 599 CA K0IDX 599
    number of fields in QSO line less than mininum expected(11)
WARNING-->Following QSOs were missing required exchange info. You may want to correct these when you resubmit your log.
  • QSO: 7070 RY 2017-01-08 0055 N6IE 599 CA K0IDX 599
    copied exchange (qthserial) is missing
Any ideas?

Thanks
Ron, N6IE




ARRL RRU: a couple of issues

Jim Miller <jtmiller47@...>
 

1. When logging DX and getting serial numbers from them N1MM+ would complain if the serial number wasn't the same as last time as if it was considering an inconsistency in QTH. It would mark the serial numbers as RED.

2. N1MM+ constantly complained that Hawaii wasn't DX but rather a state which is wrong for this contest. It kept wanting a State rather than serial number.

I had downloaded the latest N1MM+ version available at the start of the contest.

73

jim ab3cv



Re: ARRL not accepting N1MM RU logs

GALE STEWARD <k3nd@...>
 

Hmmm, looks wrong. KoIDX, or should be K0IDX?



From: "Mike KB9BIB kb9bib@... [N1MMLoggerplus]"
To: N1MMLoggerplus@...
Sent: Sunday, January 8, 2017 11:34 PM
Subject: Re: [N1MMLoggerplus] ARRL not accepting N1MM RU logs

 
Does that QSO have the state when you edit the Cabrillo file? Or is it in the file and not being seen by the robot for some reason?

On Jan 8, 2017 10:25 PM, "ron@... [N1MMLoggerplus]" <N1MMLoggerplus@...> wrote:
 
I have tried several ways of submitting my log for this year's RTTY RU, but they keep getting bounced. Here are a few lines of my log:

CREATED-BY: N1MM Logger+ 1.0.6016.0
QSO: 14106 RY 2017-01-07 1815 N6IE          599 CA     WT5L          599 FL      
QSO: 14106 RY 2017-01-07 1815 N6IE          599 CA     NX8G          599 OH      
QSO: 14106 RY 2017-01-07 1815 N6IE          599 CA     AA5VU         599 TX      
QSO: 14106 RY 2017-01-07 1815 N6IE          599 CA     K2YG          599 NJ      
QSO: 14106 RY 2017-01-07 1816 N6IE          599 CA     W6EU          599 CA      
QSO: 14106 RY 2017-01-07 1817 N6IE          599 CA     NE8O/4        599 NC  

And here is what I get back from the robot:

ERROR-->Following QSO errors were found:
  • QSO: 7070 RY 2017-01-08 0055 N6IE 599 CA K0IDX 599
    number of fields in QSO line less than mininum expected(11)
WARNING-->Following QSOs were missing required exchange info. You may want to correct these when you resubmit your log.
  • QSO: 7070 RY 2017-01-08 0055 N6IE 599 CA K0IDX 599
    copied exchange (qthserial) is missing
Any ideas?

Thanks
Ron, N6IE




Re: Time Interpolation (Again)

John Bednar
 


Doug,

If you see two panes in the Log window AND you are right clicking on a top pane QSO and the both interpolation munu items are grayed out, exit the program  and direct email me the database. Include which contest to open if there are more than one in the database. 

John,  K3CT 




-------- Original message --------
From: "Doug Smith W9WI dougw9wi@... [N1MMLoggerplus]" <N1MMLoggerplus@...>
Date: 1/9/17 8:12 AM (GMT-05:00)
To: N1MMLoggerplus@...
Subject: Re: [N1MMLoggerplus] Time Interpolation (Again)

 

On 01/09/2017 04:15 AM, 'John Bednar' k3ct@... [N1MMLoggerplus]
wrote:
> Doug,
>
> There are two parts to the Log window, the log and the lower pane of
> temporary data. If you right click on the lower pane, both interpolation
> options are grayed out. Are you right clicking in the log (top) pane?

Yes,

There are other functions that don't work in the lower pane (Add Note,
for example) that do work in the upper, but Set Time Interpolation isn't
one of them.

==
Doug Smith W9WI
Pleasant View, TN EM66


Re: Time Interpolation (Again)

Doug Smith W9WI
 

On 01/09/2017 04:15 AM, 'John Bednar' k3ct@verizon.net [N1MMLoggerplus] wrote:
Doug,

There are two parts to the Log window, the log and the lower pane of
temporary data. If you right click on the lower pane, both interpolation
options are grayed out. Are you right clicking in the log (top) pane?
Yes,

There are other functions that don't work in the lower pane (Add Note, for example) that do work in the upper, but Set Time Interpolation isn't one of them.


==
Doug Smith W9WI
Pleasant View, TN EM66


Re: F2 remains highlighted after receving RTTY exchange

Rick Ellison
 

Open the Digital setup window and on the left side about 4-5 items down place a checkmark in Send Space on Callsign Click.

When you click the call with the first click it will advance the procedure so your F5/F2 will be highlighted next. That should correct what you are seeing.

 

73 Rick n2AMG

 

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Sunday, January 8, 2017 10:49 PM
To: N1MMLoggerplus@...
Subject: [N1MMLoggerplus] F2 remains highlighted after receving RTTY exchange

 

 

First, my apologies if this question has been answered previously. I searched the forum but could not find the situation I’m about to describe.

 

I am using N1MM version 1.0.6024.0. I have “Enter Sends Message” on, “Right Click = Return NOT menu” on and Hover mode off.

 

When using N1MM for RTTY contests, it is not behaving for me as described in the online documentation, which reads:

3.2. The Rate Improver - Right Click = Return NOT Menu

Select from the settings menu in the Digital window "Right Click = Return NOT menu". This setting could improve your rate greatly as your hand never leaves the mouse except for the occasional difficult exchange. Making a qso:

·         While in Run mode with ESM on

o    Right click in the DI's RX window to send CQ

o    When a station replies left click on the call

o    Right click sends your exchange

o    As he sends his exchange, left click on it

o    Right click again to send TU and log the QSO

o    Right click again sends CQ (and you're back at the first bullet)

·         In S&P it does the same thing as hitting Enter to advance thru the ESM mode

 

In S&P mode, I left-click on a call sign and it appears in the Entry window.

 

I right-click and my F4 (S&P Call) macro is sent.

 

I left-click on the signal report and exchange and they appear in appropriate places in the Entry Window, after which, the Entry window cursor moves to the call sign field and the F4 button remains highlighted.

 

If I right-click or hit enter, instead of my “TU” (F3) macro being sent, N1MM sends my F4 macro again, unless I take the additional (undocumented) step of clicking first in the exchange field of the Entry Window. If I do that, the F2 and “Log it” buttons are then highlighted and I can send the TU with a right-click.

 

Everything I see in the documents indicates that the additional step of clicking in the exchange field of the Entry window should not be necessary. And in fact, it wasn’t necessary a couple years ago, with an earlier version of N1MM.

 

What am I doing wrong?


Re: F2 remains highlighted after receving RTTY exchange

Jay Farlow
 

In S&P, it is the TU macro that sends my exchange (in addition to "TU"), so I think I kind of need it. The documented behavior is that after I've left-clicked on the last bit of the running station's exchange, I should be able to send my exchange and log the contact with a single additional action: either pressing the enter key on my keyboard or right-clicking in the digital window. The program is not behaving as documented, which I assume means I have something set up wrong.


Re: Fldigi, mmtty 2 tone or all three?

David G3YYD <g3yyd@...>
 

I would point out that using radio FSK is sub optimum for three reasons.

 

1.     Radio FSK signal is very wide and you are causing QRM to your fellow RTTY operators. (K3 is an exception).

2.     It has timing jitter on the mark/space transitions causing decode errors at the far end.

3.     The wide spectrum occupancy wastes a lot of power as it is beyond the decoder filters.

 

Using AFSK, but preferably either Fldigi AFSK or 2Tone DOOK, has a narrow transmit bandwidth, no timing jitter and makes best use of transmit power as it matches the decoder filtering.

 

If using MMTTY AFSK then it must have the TX bandpass filtering on at 512 taps, the default setting is not good.

 

73 David G3YYD

 

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: 09 January 2017 01:45
To: N1MMLoggerplus@...
Subject: [N1MMLoggerplus] Re: Fldigi, mmtty 2 tone or all three?

 

 

Fldigi doesn't do FSK without additional hardware.

 

The majority of RTTY users, especially those who use FSK, are probably using MMTTY as the main digital engine and adding other programs for receive-only windows. AFSK users might choose to use 2Tone or fldigi as their main (transmit/receive) engine instead.

 

There should not be any port conflicts. The only digital program that should be configured to use any serial port for any purpose is the primary TX/RX engine, whichever one that happens to be, and even then only for FSK keying, not for radio control. The receive-only engines should not be configured to use any serial ports. None of the digital programs should be trying to do any kind of radio control other than FSK and maybe PTT keying from the main engine only; radio control is handled by the main N1MM+ program.

 

It's simpler to set up fldigi inside N1MM+ rather than stand-alone, because you d on't have to worry about rig control or PTT. Remember that fldigi, like MMTTY, must be run from a folder that is outside the protected Program Files path when it is run from N1MM+, as described in the documentation.

 

73,

Rich VE3KI



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

I was trying to get all three to work and ended up creating so odd com
port conflicts that would not release without a computer reboot.

I have a K3 and use FSK keying. Are the majority of RTTY users using
FLdigi for the main tx/rx and then using 2tone and mmtty or similar for
receive windows?

Is FLdigi like mmtty where you want to get it running stand alone first
then work it into N1MM+?

W0MU


Re: Time Interpolation (Again)

John Bednar
 

Doug,

 

There are two parts to the Log window, the log and the lower pane of temporary data. If you right click on the lower pane, both interpolation options are grayed out. Are you right clicking in the log (top) pane?

 

John, K3CT

 

From: N1MMLoggerplus@... [mailto:N1MMLoggerplus@...]
Sent: Sunday, January 08, 2017 9:18 PM
To: N1MMLoggerplus@...
Subject: Re: [N1MMLoggerplus] Time Interpolation (Again)

 

 

On 01/08/2017 04:51 AM, 'John Bednar' k3ct@... [N1MMLoggerplus]
wrote:
> Scott,
>
> I took the time to look at the code and I don’t see any issue.
>
> It is not possible to have two QSO’s in the database (database, not
> contest) with the same timestamp and callsign. Is it possible that your
> interpolation operation violated this condition?
>
> If there is a runtime error in the interpolation operation, none of the
> QSOs should be changed.
>
> I have seen your emails but we do not have any test cases or runtime
> error reports that can be used to duplicate the problem. Can you email
> us a reproducible example, the run time error, and the steps to
> reproduce your report?

I'm afraid my comments below will not be directly relevant to Scott's
issue, but they do involve time interpolation...

Specifically, I'm not able to make it happen at all:

(using version 1.0.6024.0, updated today. New database, also created
today although it does contain my RTTY RU log. I had the same problem
in 2016 with a different database -- I create a new database for each year.

Windows 10 Pro on two different computers. **I think** it did it on
Windows 7 but can't swear to it.

I've had the same problem with previous versions and am not sure it's
ever worked in Plus. It does work in Classic, running on the same
machines & with the same set of QSOs.)

- Create a new contest.

- Select QSOPARTY, TN.
(I get the same results with CQWWCW and would assume, with *any* contest)

- Enter a frequency (say, 3880) and mode (say, LSB) in the call window.
(the radio is turned off as I don't want it sending CW for fake test
QSOs:) )

- Enter some QSOs. (I tried 25 QSOs from a TNQP log and five for CQ WW)
(there are no dupes)

- Right-click on the first QSO.

"Set Start Interpolation Time" is greyed out and cannot be selected.
"Set Stop Interpolation Time" is also greyed out but IIRC that's normal
if you haven't set a start time yet.

==
Doug Smith W9WI
Pleasant View, TN EM66


Re: RSGB VHF B2 Scoring

Les Elliott
 

John
Are you using a version other than the experimental v6014 posted 21st Dec?
 
Les
 

Sent: Sunday, January 08, 2017 2:44 PM
Subject: Re: [N1MMLoggerplus] RSGB VHF B2 Scoring
 
 

Thanks Les

 
Downloading the latest Grids.txt seems to have partially fixed the problem. When I re-exported and rescored it corrected the DF9IC (JN48) contact, but not the DJ5AR (JN49) one. I repeated the export/rescore again, and the version of EDI file produced this time has the correct scores for DF9IC and DJ5AR but now includes bonuses for DL3IAS and DL3IAE at the end of the list, they shouldn't have any bonus as they are not the first QSOs with that square.
170107;1111;DH3NAN;2;599;001;599;000;;JO50NC;1726;;;;
170107;1111;DF9IC;2;599;002;599;000;;JN48IW;1634;;;;
170107;1112;SK7MW;2;599;003;599;000;;JO65MJ;1861;;;;
170107;1112;DJ5AR;2;599;004;599;000;;JN49CV;1546;;;;
170107;1112;GW8ASD;2;599;005;599;000;;IO83LB;809;;;;
170107;1112;G3NNG;2;599;006;599;000;;IO91EP;701;;;;
170107;1112;GI6ATZ;2;599;007;599;000;;IO74AJ;1543;;;;
170107;1112;GM4JTJ;2;599;008;599;000;;IO86RP ;2565;;;;
170107;1113;F6DKW;2;599;009;599;000;;JN18CS;1373;;;;
170107;1113;F6DRO;2;599;010;599;000;;;0;;;;D
170107;1113;F8BRK;2;599;011;599;000;;IN99VF;1331;;;;
170107;1113;F4VRB;2;599;012;599;000;;IN98PT;1387;;;;
170107;1114;DL0VV;2;599;013;599;000;;JO64AD;1759;;;;
170107;1114;DF0MU;2;599;014;599;000;;JO32PC;1416;;;;
170107;1114;DL3IAS;2;599;015;599;000;;JN49EJ;1585;;;;
170107;1114;DL3IAE;2;599;016;599;000;;JN49DG;1588;;;;
 
73
John G3XDY


Re: Reset radio?

Vytenis LY5T
 

Or better yet, use built in dedicated tool "Snipping tool". You will find it under Accessories folder. If you try, you will never come back to any other method. Add to Taskbar if you need this functionality often.

Vytenis LY5T

P.S. sorry for slight off topic.


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

Why use a camera? Just use the PrtSc button on your keyboard to take a screen shot, paste it into Paint, crop it and save it as a png or jpg file.


73,
Rich VE3KI


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

Hey Phil,


Since you used my call, I'll see if I can boot up my camera-phone, computer and radio and fake a "reset radio" blunder on my bandmap and snap a picture for you and try to post it.  I've never attached a photo to a yahoo message before, so we'll see how it goes.


QRX-15


Mike VE9AA



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

Mike VE9AA, and the group,

 

Others have intimated that the button is actually there, but I don’t see it at all. Nor was it visible when the pop-up occurred, although I guess it could have been behind the pop-up box.

 

My bandmap only has the usual buttons at the top, and stretching it out further doesn’t reveal any buttons at the lower edge. There is no scroll bar on the right to show anything lower down.

Is it a setting somewhere that needs to be checked?

 

I’m using the latest version of N1MM+ too.

 

73 all

 

Phil GU0SUP



Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com


 


Re: ARRL not accepting N1MM RU logs

Bill Conkling - NR4C
 

Not sure about upper set but less space between his call and state.  

Bottom call is not US call.  KoIDX needs a serial number or K0IDX needs a State. 

...nr4c. bill


On Jan 8, 2017, at 11:20 PM, ron@... [N1MMLoggerplus] <N1MMLoggerplus@...> wrote:

 

I have tried several ways of submitting my log for this year's RTTY RU, but they keep getting bounced. Here are a few lines of my log:

CREATED-BY: N1MM Logger+ 1.0.6016.0
QSO: 14106 RY 2017-01-07 1815 N6IE          599 CA     WT5L          599 FL      
QSO: 14106 RY 2017-01-07 1815 N6IE          599 CA     NX8G          599 OH      
QSO: 14106 RY 2017-01-07 1815 N6IE          599 CA     AA5VU         599 TX      
QSO: 14106 RY 2017-01-07 1815 N6IE          599 CA     K2YG          599 NJ      
QSO: 14106 RY 2017-01-07 1816 N6IE          599 CA     W6EU          599 CA      
QSO: 14106 RY 2017-01-07 1817 N6IE          599 CA     NE8O/4        599 NC  

And here is what I get back from the robot:

ERROR-->Following QSO errors were found:

  • QSO: 7070 RY 2017-01-08 0055 N6IE 599 CA K0IDX 599
    number of fields in QSO line less than mininum expected(11)

WARNING-->Following QSOs were missing required exchange info. You may want to correct these when you resubmit your log.

  • QSO: 7070 RY 2017-01-08 0055 N6IE 599 CA K0IDX 599
    copied exchange (qthserial) is missing

Any ideas?


Thanks

Ron, N6IE



Re: F2 remains highlighted after receving RTTY exchange

Bill Conkling - NR4C
 

You don't need the TU Macro in S&P. 

Personally I get confused when callers send TU.   I use the Runners TU to time my pounce. 
...nr4c. bill


On Jan 8, 2017, at 10:48 PM, w9lw@... [N1MMLoggerplus] <N1MMLoggerplus@...> wrote:

 

First, my apologies if this question has been answered previously. I searched the forum but could not find the situation I’m about to describe.


I am using N1MM version 1.0.6024.0. I have “Enter Sends Message” on, “Right Click = Return NOT menu” on and Hover mode off.


When using N1MM for RTTY contests, it is not behaving for me as described in the online documentation, which reads:

3.2. The Rate Improver - Right Click = Return NOT Menu

Select from the settings menu in the Digital window "Right Click = Return NOT menu". This setting could improve your rate greatly as your hand never leaves the mouse except for the occasional difficult exchange. Making a qso:

·         While in Run mode with ESM on

o    Right click in the DI's RX window to send CQ

o    When a station replies left click on the call

o    Right click sends your exchange

o    As he sends his exchange, left click on it

o    Right click again to send TU and log the QSO

o    Right click again sends CQ (and you're back at the first bullet)

·         In S&P it does the same thing as hitting Enter to advance thru the ESM mode


In S&P mode, I left-click on a call sign and it appears in the Entry window.


I right-click and my F4 (S&P Call) macro is sent.


I left-click on the signal report and exchange and they appear in appropriate places in the Entry Window, after which, the Entry window cursor moves to the call sign field and the F4 button remains highlighted.


If I right-click or hit enter, instead of my “TU” (F3) macro being sent, N1MM sends my F4 macro again, unless I take the additional (undocumented) step of clicking first in the exchange field of the Entry Window. If I do that, the F2 and “Log it” buttons are then highlighted and I can send the TU with a right-click.


Everything I see in the documents indicates that the additional step of clicking in the exchange field of the Entry window should not be necessary. And in fact, it wasn’t necessary a couple years ago, with an earlier version of N1MM.


What am I doing wrong?


Re: ARRL not accepting N1MM RU logs

Mike KB9BIB <kb9bib@...>
 

Does that QSO have the state when you edit the Cabrillo file? Or is it in the file and not being seen by the robot for some reason?

On Jan 8, 2017 10:25 PM, "ron@... [N1MMLoggerplus]" <N1MMLoggerplus@...> wrote:
 

I have tried several ways of submitting my log for this year's RTTY RU, but they keep getting bounced. Here are a few lines of my log:

CREATED-BY: N1MM Logger+ 1.0.6016.0
QSO: 14106 RY 2017-01-07 1815 N6IE          599 CA     WT5L          599 FL      
QSO: 14106 RY 2017-01-07 1815 N6IE          599 CA     NX8G          599 OH      
QSO: 14106 RY 2017-01-07 1815 N6IE          599 CA     AA5VU         599 TX      
QSO: 14106 RY 2017-01-07 1815 N6IE          599 CA     K2YG          599 NJ      
QSO: 14106 RY 2017-01-07 1816 N6IE          599 CA     W6EU          599 CA      
QSO: 14106 RY 2017-01-07 1817 N6IE          599 CA     NE8O/4        599 NC  

And here is what I get back from the robot:

ERROR-->Following QSO errors were found:

  • QSO: 7070 RY 2017-01-08 0055 N6IE 599 CA K0IDX 599
    number of fields in QSO line less than mininum expected(11)

WARNING-->Following QSOs were missing required exchange info. You may want to correct these when you resubmit your log.

  • QSO: 7070 RY 2017-01-08 0055 N6IE 599 CA K0IDX 599
    copied exchange (qthserial) is missing

Any ideas?


Thanks

Ron, N6IE



Re: ARRL not accepting N1MM RU logs

KØHB
 

The block of QSO’s at the start seem fine.

 

Your Q with K0IDX appears to be missing the “state” info, and you got two flags --- an ERROR for not enough fields, and a WARNING for no QTH.

 

73, de Hans, KØHB
"Just a boy and his radio"™

 

From: ron@... [N1MMLoggerplus]
Sent: Monday, January 9, 2017 4:25 AM
To: N1MMLoggerplus@...
Subject: [N1MMLoggerplus] ARRL not accepting N1MM RU logs

 

 

I have tried several ways of submitting my log for this year's RTTY RU, but they keep getting bounced. Here are a few lines of my log:

CREATED-BY: N1MM Logger+ 1.0.6016.0
QSO: 14106 RY 2017-01-07 1815 N6IE          599 CA     WT5L          599 FL      
QSO: 14106 RY 2017-01-07 1815 N6IE          599 CA     NX8G          599 OH      
QSO: 14106 RY 2017-01-07 1815 N6IE          599 CA     AA5VU         599 TX      
QSO: 14106 RY 2017-01-07 1815 N6IE          599 CA     K2YG          599 NJ      
QSO: 14106 RY 2017-01-07 1816 N6IE          599 CA     W6EU          599 CA      
QSO: 14106 RY 2017-01-07 1817 N6IE          599 CA     NE8O/4        599 NC  

And here is what I get back from the robot:

ERROR-->Following QSO errors were found:

  • QSO: 7070 RY 2017-01-08 0055 N6IE 599 CA K0IDX 599
    number of fields in QSO line less than mininum expected(11)

WARNING-->Following QSOs were missing required exchange info. You may want to correct these when you resubmit your log.

  • QSO: 7070 RY 2017-01-08 0055 N6IE 599 CA K0IDX 599
    copied exchange (qthserial) is missing

Any ideas?

 

Thanks

Ron, N6IE