Date   
Re: Ten Ten Log Problem

John Bednar
 


Rory,

You listed the output of the adif export.

John, K3CT 




-------- Original message --------
From: Rory Bowers <k6cks01@...>
Date: 8/14/19 10:55 AM (GMT-05:00)
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] Ten Ten Log Problem

I worked the Ten Ten Summer SSB Contest a couple of weeks ago and discovered a problem with my log when N1MM+ created the Cabrillo file.  It cut off most of the Exchange text for each contact.
 
Logfile Data:
<CALL:5>N5EMS <QSO_DATE:8>20190803 <TIME_ON:6>160700 <TIME_OFF:6>160700 <SECTION:2>N5 <BAND:3>10M <STATION_CALLSIGN:5>K5CKS <FREQ:8>28.40200 <CONTEST_ID:7>TENTEN- <FREQ_RX:8>28.40200 <MODE:3>SSB <NAME:4>GARY <RST_RCVD:2>59 <RST_SENT:2>59 <OPERATOR:1>  <APP_N1MM_EXCHANGE1:2>AR <APP_N1MM_POINTS:1>1 <APP_N1MM_RADIO_NR:1>0 <APP_N1MM_RUN1RUN2:1>0 <APP_N1MM_RADIOINTERFACED:1>0 <APP_N1MM_ISORIGINAL:4>True <APP_N1MM_NETBIOSNAME:15>ADMINRG-EER99FA <APP_N1MM_ISRUNQSO:1>0 <EOR>
 <CALL:6>KD5ILA <QSO_DATE:8>20190803 <TIME_ON:6>164200 <TIME_OFF:6>164200 <SECTION:3>KD5 <BAND:3>10M <STATION_CALLSIGN:5>K5CKS <FREQ:8>28.41700 <CONTEST_ID:7>TENTEN- <FREQ_RX:8>28.41700 <MODE:3>SSB <NAME:4>JACK <RST_RCVD:2>59 <RST_SENT:2>59 <OPERATOR:1>  <APP_N1MM_EXCHANGE1:8>77652 AR <APP_N1MM_POINTS:1>1 <APP_N1MM_RADIO_NR:1>0 <APP_N1MM_RUN1RUN2:1>0 <APP_N1MM_RADIOINTERFACED:1>0 <APP_N1MM_ISORIGINAL:4>True <APP_N1MM_NETBIOSNAME:15>ADMINRG-EER99FA <APP_N1MM_ISRUNQSO:1>0 <EOR>
 <CALL:5>W5TMC <QSO_DATE:8>20190803 <TIME_ON:6>192400 <TIME_OFF:6>192400 <SECTION:2>W5 <BAND:3>10M <STATION_CALLSIGN:5>K5CKS <FREQ:8>28.40200 <CONTEST_ID:7>TENTEN- <FREQ_RX:8>28.40200 <MODE:3>SSB <NAME:4>MIKE <RST_RCVD:2>59 <RST_SENT:2>59 <OPERATOR:1>  <APP_N1MM_EXCHANGE1:8>74810 OK <APP_N1MM_POINTS:1>1 <APP_N1MM_RADIO_NR:1>0 <APP_N1MM_RUN1RUN2:1>0 <APP_N1MM_RADIOINTERFACED:1>0 <APP_N1MM_ISORIGINAL:4>True <APP_N1MM_NETBIOSNAME:15>ADMINRG-EER99FA <APP_N1MM_ISRUNQSO:1>0 <EOR>
 <CALL:5>K5MGM <QSO_DATE:8>20190803 <TIME_ON:6>210600 <TIME_OFF:6>210600 <SECTION:2>K5 <BAND:3>10M <STATION_CALLSIGN:5>K5CKS <FREQ:8>28.40200 <CONTEST_ID:7>TENTEN- <FREQ_RX:8>28.40200 <MODE:3>SSB <NAME:4>BILL <RST_RCVD:2>59 <RST_SENT:2>59 <OPERATOR:1>  <APP_N1MM_EXCHANGE1:8>69555 AR <APP_N1MM_POINTS:1>1 <APP_N1MM_RADIO_NR:1>0 <APP_N1MM_RUN1RUN2:1>0 <APP_N1MM_RADIOINTERFACED:1>0 <APP_N1MM_ISORIGINAL:4>True <APP_N1MM_NETBIOSNAME:15>ADMINRG-EER99FA <APP_N1MM_ISRUNQSO:1>0 <EOR>

Cabrillo Export:
QSO: 28402 PH 2019-08-03 1607 K5CKS         RORY 68322 AR      N5EMS         GARY         AR            
QSO: 28417 PH 2019-08-03 1642 K5CKS         RORY 68322 AR      KD5ILA        JACK         7765          
QSO: 28402 PH 2019-08-03 1924 K5CKS         RORY 68322 AR      W5TMC         MIKE         7481          
QSO: 28402 PH 2019-08-03 2106 K5CKS         RORY 68322 AR      K5MGM         BILL         6955  
Any ideas how I can keep this from happening again?
73,
Rory, K5CKS

Re: Ten Ten Log Problem

Rory Bowers
 

Yes and under that I have listed the output of the log portion of the Cabrillo file.  Did you miss it?
Thanks for the reply!
73,
Rory, K5CKS

On Wed, Aug 14, 2019 at 11:17 AM John Bednar via Groups.Io <k3ct=verizon.net@groups.io> wrote:

Rory,

You listed the output of the adif export.

John, K3CT 




-------- Original message --------
From: Rory Bowers <k6cks01@...>
Date: 8/14/19 10:55 AM (GMT-05:00)
Subject: [N1MM+] Ten Ten Log Problem

I worked the Ten Ten Summer SSB Contest a couple of weeks ago and discovered a problem with my log when N1MM+ created the Cabrillo file.  It cut off most of the Exchange text for each contact.
 
Logfile Data:
<CALL:5>N5EMS <QSO_DATE:8>20190803 <TIME_ON:6>160700 <TIME_OFF:6>160700 <SECTION:2>N5 <BAND:3>10M <STATION_CALLSIGN:5>K5CKS <FREQ:8>28.40200 <CONTEST_ID:7>TENTEN- <FREQ_RX:8>28.40200 <MODE:3>SSB <NAME:4>GARY <RST_RCVD:2>59 <RST_SENT:2>59 <OPERATOR:1>  <APP_N1MM_EXCHANGE1:2>AR <APP_N1MM_POINTS:1>1 <APP_N1MM_RADIO_NR:1>0 <APP_N1MM_RUN1RUN2:1>0 <APP_N1MM_RADIOINTERFACED:1>0 <APP_N1MM_ISORIGINAL:4>True <APP_N1MM_NETBIOSNAME:15>ADMINRG-EER99FA <APP_N1MM_ISRUNQSO:1>0 <EOR>
 <CALL:6>KD5ILA <QSO_DATE:8>20190803 <TIME_ON:6>164200 <TIME_OFF:6>164200 <SECTION:3>KD5 <BAND:3>10M <STATION_CALLSIGN:5>K5CKS <FREQ:8>28.41700 <CONTEST_ID:7>TENTEN- <FREQ_RX:8>28.41700 <MODE:3>SSB <NAME:4>JACK <RST_RCVD:2>59 <RST_SENT:2>59 <OPERATOR:1>  <APP_N1MM_EXCHANGE1:8>77652 AR <APP_N1MM_POINTS:1>1 <APP_N1MM_RADIO_NR:1>0 <APP_N1MM_RUN1RUN2:1>0 <APP_N1MM_RADIOINTERFACED:1>0 <APP_N1MM_ISORIGINAL:4>True <APP_N1MM_NETBIOSNAME:15>ADMINRG-EER99FA <APP_N1MM_ISRUNQSO:1>0 <EOR>
 <CALL:5>W5TMC <QSO_DATE:8>20190803 <TIME_ON:6>192400 <TIME_OFF:6>192400 <SECTION:2>W5 <BAND:3>10M <STATION_CALLSIGN:5>K5CKS <FREQ:8>28.40200 <CONTEST_ID:7>TENTEN- <FREQ_RX:8>28.40200 <MODE:3>SSB <NAME:4>MIKE <RST_RCVD:2>59 <RST_SENT:2>59 <OPERATOR:1>  <APP_N1MM_EXCHANGE1:8>74810 OK <APP_N1MM_POINTS:1>1 <APP_N1MM_RADIO_NR:1>0 <APP_N1MM_RUN1RUN2:1>0 <APP_N1MM_RADIOINTERFACED:1>0 <APP_N1MM_ISORIGINAL:4>True <APP_N1MM_NETBIOSNAME:15>ADMINRG-EER99FA <APP_N1MM_ISRUNQSO:1>0 <EOR>
 <CALL:5>K5MGM <QSO_DATE:8>20190803 <TIME_ON:6>210600 <TIME_OFF:6>210600 <SECTION:2>K5 <BAND:3>10M <STATION_CALLSIGN:5>K5CKS <FREQ:8>28.40200 <CONTEST_ID:7>TENTEN- <FREQ_RX:8>28.40200 <MODE:3>SSB <NAME:4>BILL <RST_RCVD:2>59 <RST_SENT:2>59 <OPERATOR:1>  <APP_N1MM_EXCHANGE1:8>69555 AR <APP_N1MM_POINTS:1>1 <APP_N1MM_RADIO_NR:1>0 <APP_N1MM_RUN1RUN2:1>0 <APP_N1MM_RADIOINTERFACED:1>0 <APP_N1MM_ISORIGINAL:4>True <APP_N1MM_NETBIOSNAME:15>ADMINRG-EER99FA <APP_N1MM_ISRUNQSO:1>0 <EOR>

Cabrillo Export:
QSO: 28402 PH 2019-08-03 1607 K5CKS         RORY 68322 AR      N5EMS         GARY         AR            
QSO: 28417 PH 2019-08-03 1642 K5CKS         RORY 68322 AR      KD5ILA        JACK         7765          
QSO: 28402 PH 2019-08-03 1924 K5CKS         RORY 68322 AR      W5TMC         MIKE         7481          
QSO: 28402 PH 2019-08-03 2106 K5CKS         RORY 68322 AR      K5MGM         BILL         6955  
Any ideas how I can keep this from happening again?
73,
Rory, K5CKS

Re: Ten Ten Log Problem

Rory Bowers
 

Here is the complete output of the Cabrillo file...

START-OF-LOG: 3.0
LOCATION: AR
CALLSIGN: K5CKS
CLUB:  
CONTEST: TENTEN-
CATEGORY-OPERATOR: SINGLE-OP
CATEGORY-ASSISTED: ASSISTED
CATEGORY-BAND: 10M
CATEGORY-MODE: SSB
CATEGORY-POWER: HIGH
CATEGORY-STATION: FIXED
CATEGORY-TRANSMITTER: ONE
CLAIMED-SCORE: 4
OPERATORS: K5CKS
NAME: Rory
ADDRESS: 4722 N. M Street
ADDRESS-CITY: Fort Smith
ADDRESS-STATE-PROVINCE: AR
ADDRESS-POSTALCODE: 72904
ADDRESS-COUNTRY: UNITED STATES
EMAIL: k5cks@...
CREATED-BY: N1MM Logger+ 1.0.7883.0
QSO: 28402 PH 2019-08-03 1607 K5CKS         RORY 68322 AR      N5EMS         GARY         AR            
QSO: 28417 PH 2019-08-03 1642 K5CKS         RORY 68322 AR      KD5ILA        JACK         7765          
QSO: 28402 PH 2019-08-03 1924 K5CKS         RORY 68322 AR      W5TMC         MIKE         7481          
QSO: 28402 PH 2019-08-03 2106 K5CKS         RORY 68322 AR      K5MGM         BILL         6955          
END-OF-LOG:


On Wed, Aug 14, 2019 at 11:17 AM John Bednar via Groups.Io <k3ct=verizon.net@groups.io> wrote:

Rory,

You listed the output of the adif export.

John, K3CT 




-------- Original message --------
From: Rory Bowers <k6cks01@...>
Date: 8/14/19 10:55 AM (GMT-05:00)
Subject: [N1MM+] Ten Ten Log Problem

I worked the Ten Ten Summer SSB Contest a couple of weeks ago and discovered a problem with my log when N1MM+ created the Cabrillo file.  It cut off most of the Exchange text for each contact.
 
Logfile Data:
<CALL:5>N5EMS <QSO_DATE:8>20190803 <TIME_ON:6>160700 <TIME_OFF:6>160700 <SECTION:2>N5 <BAND:3>10M <STATION_CALLSIGN:5>K5CKS <FREQ:8>28.40200 <CONTEST_ID:7>TENTEN- <FREQ_RX:8>28.40200 <MODE:3>SSB <NAME:4>GARY <RST_RCVD:2>59 <RST_SENT:2>59 <OPERATOR:1>  <APP_N1MM_EXCHANGE1:2>AR <APP_N1MM_POINTS:1>1 <APP_N1MM_RADIO_NR:1>0 <APP_N1MM_RUN1RUN2:1>0 <APP_N1MM_RADIOINTERFACED:1>0 <APP_N1MM_ISORIGINAL:4>True <APP_N1MM_NETBIOSNAME:15>ADMINRG-EER99FA <APP_N1MM_ISRUNQSO:1>0 <EOR>
 <CALL:6>KD5ILA <QSO_DATE:8>20190803 <TIME_ON:6>164200 <TIME_OFF:6>164200 <SECTION:3>KD5 <BAND:3>10M <STATION_CALLSIGN:5>K5CKS <FREQ:8>28.41700 <CONTEST_ID:7>TENTEN- <FREQ_RX:8>28.41700 <MODE:3>SSB <NAME:4>JACK <RST_RCVD:2>59 <RST_SENT:2>59 <OPERATOR:1>  <APP_N1MM_EXCHANGE1:8>77652 AR <APP_N1MM_POINTS:1>1 <APP_N1MM_RADIO_NR:1>0 <APP_N1MM_RUN1RUN2:1>0 <APP_N1MM_RADIOINTERFACED:1>0 <APP_N1MM_ISORIGINAL:4>True <APP_N1MM_NETBIOSNAME:15>ADMINRG-EER99FA <APP_N1MM_ISRUNQSO:1>0 <EOR>
 <CALL:5>W5TMC <QSO_DATE:8>20190803 <TIME_ON:6>192400 <TIME_OFF:6>192400 <SECTION:2>W5 <BAND:3>10M <STATION_CALLSIGN:5>K5CKS <FREQ:8>28.40200 <CONTEST_ID:7>TENTEN- <FREQ_RX:8>28.40200 <MODE:3>SSB <NAME:4>MIKE <RST_RCVD:2>59 <RST_SENT:2>59 <OPERATOR:1>  <APP_N1MM_EXCHANGE1:8>74810 OK <APP_N1MM_POINTS:1>1 <APP_N1MM_RADIO_NR:1>0 <APP_N1MM_RUN1RUN2:1>0 <APP_N1MM_RADIOINTERFACED:1>0 <APP_N1MM_ISORIGINAL:4>True <APP_N1MM_NETBIOSNAME:15>ADMINRG-EER99FA <APP_N1MM_ISRUNQSO:1>0 <EOR>
 <CALL:5>K5MGM <QSO_DATE:8>20190803 <TIME_ON:6>210600 <TIME_OFF:6>210600 <SECTION:2>K5 <BAND:3>10M <STATION_CALLSIGN:5>K5CKS <FREQ:8>28.40200 <CONTEST_ID:7>TENTEN- <FREQ_RX:8>28.40200 <MODE:3>SSB <NAME:4>BILL <RST_RCVD:2>59 <RST_SENT:2>59 <OPERATOR:1>  <APP_N1MM_EXCHANGE1:8>69555 AR <APP_N1MM_POINTS:1>1 <APP_N1MM_RADIO_NR:1>0 <APP_N1MM_RUN1RUN2:1>0 <APP_N1MM_RADIOINTERFACED:1>0 <APP_N1MM_ISORIGINAL:4>True <APP_N1MM_NETBIOSNAME:15>ADMINRG-EER99FA <APP_N1MM_ISRUNQSO:1>0 <EOR>

Cabrillo Export:
QSO: 28402 PH 2019-08-03 1607 K5CKS         RORY 68322 AR      N5EMS         GARY         AR            
QSO: 28417 PH 2019-08-03 1642 K5CKS         RORY 68322 AR      KD5ILA        JACK         7765          
QSO: 28402 PH 2019-08-03 1924 K5CKS         RORY 68322 AR      W5TMC         MIKE         7481          
QSO: 28402 PH 2019-08-03 2106 K5CKS         RORY 68322 AR      K5MGM         BILL         6955  
Any ideas how I can keep this from happening again?
73,
Rory, K5CKS

Re: K3/0 MINI and N1MM+

Jorge Diez - CX6VM
 

hello Rich

yes, that´s mine

RRC1258 COM0 (COM3)
RRC1258 COM1 (COM4)
RRC1258 COM2 (COM20)
RRC1258 COMExtra (COM15)  

I also have 

USB Serial Port (COM8) that is my FTDI RS232 interfase, connected to RR control COM1 adn to a USB port on my laptop

On N1MM+ I have COM8 for  rig control (Radio = K3, etc.)

and now I use COM15 for a Winkeyer and is working OK

Thanks!

Before i was using a pair of K3/100 and i was using COM3 for the Winkeyer

thanks!
Jorge



Libre de virus. www.avast.com


El mié., 14 ago. 2019 a las 9:48, ve3ki (<ve3iay@...>) escribió:
You need to configure N1MM+ to use the RemoteRig's Winkeyer.

Your RemoteRig box creates four new COM ports. In the Windows Device Manager on my computer they look like this:

RRC1258 COM0 (COM13)
RRC1258 COM1 (COM12)
RRC1258 COM2 (COM14)
RRC1258 COMExtra (COM11)

The numbers inside the parentheses will be different on your system - you need to use the numbers from your system, not mine. In my copy of N1MM+, I have COM12 (the RRC1258 COM1 port) configured for rig control (Radio = K3, etc.), and I have COM11 (the RRC1258 COMExtra port) configured for a Winkeyer (Radio = None, CW/Other box checked, and the WinKey check box checked in the setup for the port). N1MM+ uses the Winkey port (COM11 on my computer) to send function key messages.

73,
Rich VE3KI
 


On Wed, Aug 14, 2019 at 08:15 AM, Jorge Diez - CX6VM wrote:
hello
 
i am trying to setup a remote K3 and K3/0 Mini
 
I connected the cable set RRMINICBL 
 
I connect a paddle to remoterig box. Sending CW with the paddles is OK, but I couldnt send CW with N1MM+ messages
 
Any help for that?
 
--
73,
Jorge
CX6VM/CW5W

Libre de virus. www.avast.com



--
73,
Jorge
CX6VM/CW5W

RDAC Call Histoy file

VE2FK
 

RDAC call history file have been deleted, too old.
A new file will be available tomorrow. Valery UR7QM is working on it.

73, Claude VE2FK

Re: K3 intermittently forgets to transmit even though FT8 has gone into TX mode, PS

Paul wyse
 

I use JTDX by it's self and with N1MM+ and the problem exists in both implementations. Using WSJT-x acts the same. It seems to be much more noticeable in the last month or so for me. 

Loss of radio 2 control with ver 1.0.7900

Lewis Sayre
 

Upgraded to ver 1.0.7900 from Ver 1.0.7883 and got an error when loading WSJT-X from inside N1MM+ on radio 2 only.  No frequency communication between radio 2 and N1MM+.  I did not get the run time error documented as I thought the problem was 2 new security updates that had just been run through Windows 10. I deleted the Windows updates and went back to Ver 1.0.7883 and things are back to normal.
Anybody else have radio 2 problems between N1MM+ and WSJT-X with Ver 1.0.7900?   Should I go back and recreate the run time error so that the coder gurus know what happened?
    73 and I remain,
    Lew     w7ew

Re: Loss of radio 2 control with ver 1.0.7900

Gary Hembree
 

Lew,
I upgraded my K3 SO2R N1MM+ setup to 1.0.7900 this morning and got a RTE when I tried to run WSJT-X from Radio 1.  Closed that instance and was then unable to open WSJT-X again until I closed and reloaded N1MM+.  However, I got the same RTE every time so I reverted back to 1.0.7883 and my setup is working normally.  When I have a chance I’ll document the RTE and file a bug report.  Too many other more pressing matters at the moment.
 
Something got changed with the K3 code in January around Ver 1.0.7467.  N1MM+ now has trouble following band and mode changes with multi-mode, multi-band logs with my SO2R K3 setup.  I haven’t take the time to do extensive documentation of this bug but just work around it.
 
73
Gary, N7IR
 

Sent: Wednesday, August 14, 2019 3:45 PM
Subject: [N1MM+] Loss of radio 2 control with ver 1.0.7900
 
Upgraded to ver 1.0.7900 from Ver 1.0.7883 and got an error when loading WSJT-X from inside N1MM+ on radio 2 only.  No frequency communication between radio 2 and N1MM+.  I did not get the run time error documented as I thought the problem was 2 new security updates that had just been run through Windows 10. I deleted the Windows updates and went back to Ver 1.0.7883 and things are back to normal.
Anybody else have radio 2 problems between N1MM+ and WSJT-X with Ver 1.0.7900?   Should I go back and recreate the run time error so that the coder gurus know what happened?
    73 and I remain,
    Lew     w7ew
 

Re: Loss of radio 2 control with ver 1.0.7900

John Bednar
 

Gary,

 

This is the only report.

 

> Something got changed with the K3 code in January around Ver 1.0.7467.

The radio control class changed Dec 12, January 13, and April 9. I look at every change and there were no changes to the K3 radio control. I also checked the radio commands and there were no K3 changes to the commands.

 

Install an old version and see if you notice a change.

 

John, K3CT

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Gary Hembree
Sent: Wednesday, August 14, 2019 8:07 PM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] Loss of radio 2 control with ver 1.0.7900

 

Lew,

I upgraded my K3 SO2R N1MM+ setup to 1.0.7900 this morning and got a RTE when I tried to run WSJT-X from Radio 1.  Closed that instance and was then unable to open WSJT-X again until I closed and reloaded N1MM+.  However, I got the same RTE every time so I reverted back to 1.0.7883 and my setup is working normally.  When I have a chance I’ll document the RTE and file a bug report.  Too many other more pressing matters at the moment.

 

Something got changed with the K3 code in January around Ver 1.0.7467.  N1MM+ now has trouble following band and mode changes with multi-mode, multi-band logs with my SO2R K3 setup.  I haven’t take the time to do extensive documentation of this bug but just work around it.

 

73

Gary, N7IR

 

Sent: Wednesday, August 14, 2019 3:45 PM

Subject: [N1MM+] Loss of radio 2 control with ver 1.0.7900

 

Upgraded to ver 1.0.7900 from Ver 1.0.7883 and got an error when loading WSJT-X from inside N1MM+ on radio 2 only.  No frequency communication between radio 2 and N1MM+.  I did not get the run time error documented as I thought the problem was 2 new security updates that had just been run through Windows 10. I deleted the Windows updates and went back to Ver 1.0.7883 and things are back to normal.
Anybody else have radio 2 problems between N1MM+ and WSJT-X with Ver 1.0.7900?   Should I go back and recreate the run time error so that the coder gurus know what happened?
    73 and I remain,
    Lew     w7ew

 

Re: N1MM+ & WSJT-X integration: A Moving Target

Victor Paul
 

The write-up by Don, AA5AU at the link below is excellent!  Best set of instructions I've seen on the latest on integration of N1MM+ with WSJT-X. Very detailed, with lots of screen shots and explanations of not just how, but why.  Not sure who would need to do what, but I think it would be great if a .pdf version of it could be loaded into the Additional Support Files folder in the Downloads section of the main N2MM+ website.

https://www.rttycontesting.com/tutorials/n1mm/operating-ww-digi-with-n1mm/

Thanks Don, for the time you took to make this tutorial. 

73,
Victor WB0TEV / V31VP

Re: N1MM+ & WSJT-X integration: A Moving Target

Jim Cooper
 

On 14 Aug 2019 at 18:38, Victor Paul wrote:

Not sure who would need to do what,
but I think it would be great if a
.pdf version of it could be loaded
into the Additional Support Files
folder in the Downloads section of
the main N2MM+ website.
Today I made myself a PDF of that document,
with most all of the links in it appended to
the PDF ...

If anyone wants it, to upload or for themselves,
let me know.

Jim W2JC

Re: Suggested improvement for serial number contest F2 macros

Jim W7RY
 

Agreed Pete!

Thanks
73
Jim W7RY
On 8/13/2019 10:09 AM, Pete Smith wrote:

I think there's another way to look at this.  Having the 5NN sent before the serial number, in my opinion, provides a useful pacing function that is helpful in times of deep and quick QSB.  What do I mean?  I'm talking about knowing when to expect the first code element of the serial number, as well as the speed at which it will be sent.  Taken together with the internal redundancy of full Morse code numbers, I find this gives me a significant advantage in quickly copying a serial number under difficult conditions.

73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.
On 8/13/2019 9:04 AM, Tim Shoppa wrote:
I should add.... I have observed when asking for serial number fills over the past decade, that the fraction of folks who send the "5NN then the serial" for every fill has gone from a few percent to circa 80%.

I think this percentage is ENTIRELY a measure of the N1MM market penetration and usage it's default macros. If you look at the logs submitted by various logger software, more than 50% of the logs are now made by N1MM. Now factor in that most of the N1MM logs are much larger than the onesy-twosy loggers, and probably 80% of QSO's are made with N1MM worldwide today.

In other words, it's because N1MM is so popular today, and the default F2 key macro sends 5NN before the exchange, that I observe 5NN being sent unnecessarily on almost every fill repeat. And I make a lot of fill repeat requests in every serial number contest!!! Yes I am a stickler for getting the serial number right.

Yes education can also be part of the solution too. But everybody could've optimized their macros for a serial number repeat, and hardly any did. 
 
It's because of N1MM's large market penetration, and the way everyone is using its default macros, that I feel N1MM's default F2 behavior and default macros can be part of the solution.

Tim N3QE

On Mon, Aug 12, 2019 at 11:01 AM Tim Shoppa <tshoppa@...> wrote:
Most serial number contests - for example WAE, WPX, etc - require a signal report and a serial number. So on CW, everyone has their F2 key setup to send 5NN and the serial number. Or maybe my call then TU then 5NN then the serial number (yes, a lot of guys have that on their S&P F2 macro!)

80%+ of the time I ask for a fill in a CW serial number contest, the guy hits F2 once or twice, and I get 5NN 1234 or maybe 5NN 1234 5NN 1234 or maybe N3QE TU 5NN 1234. Of course I don't need anything but the serial number but the guy only knows the F2 key so I get the full F2 message each time. Although there is some "synchronization value" in the 5NN, really all I want is the serial number and I just asked for the number to be repeated so I don't think there's any actual value in repeating 5NN each time. He sent 5NN the first time as required by the rules, I'm not asking for a fill of the RST, I'm asking for a fill of the serial number.

Now I do it a little different. I programmed a different function key just to repeat only the serial number. So I hit F6 and send the serial number only, or hit it twice and send it twice.

My suggested improvement, is that given these guys will never hit anything but F2, that after the first F2 send, that hitting the F2 button only send the serial number without the RST and without any callsigns or pleasantries.

I know this is programmatically a little weird and breaks some of the consistency of the F2 button. Maybe a N1MM macro expert can recommend a way to use existing macro functions to achieve the same end result, and we can make sure this way goes into all future "default macro setups" from now. For example, maybe {SENTRST} could be the default macro, and we could have a special rule that {SENTRST} is only ever sent once per contact.

Obviously some education could work instead. Since forever, they other op could configure a different function key just for a fill or a super-fill on the serial number. But after getting a record number of 5NN repeats this past weekend I'm dubious that education could reach every corner of the world.

A similar improvement would actually be even better in RTTY. Invariably if I ask for a repeat of a serial number in RTTY they send ".... N3QE N3QE TU 599 1234 N3QE" when all I really wanted was the 1234. When it doesn't come through I ask again and they resend ".... N3QE N3QE TU 599 1234 N3QE" several more times. This could be so much more efficient!

Tim N3QE

Re: Suggested improvement for serial number contest F2 macros

Jim W7RY
 

I don't like the fact that your promoting the use of B4 in your (N1MM) CW macros.

Always work dupes! Always!

Thanks
73
Jim W7RY
On 8/14/2019 3:25 AM, Les Elliott via Groups.Io wrote:

 
Les, G4OGB
 
Sent: Wednesday, August 14, 2019 4:05 AM
Subject: Re: [N1MM+] Suggested improvement for serial number contest F2 macros
 
In N1MM+ how does one vary the speed of the contents associated with an F key?

73, Ed W2LCQ

Frankford Radio Club
CWops 701 - SKCC 5474 - FISTS 12294
 


 
 

On Aug 13, 2019, at 9:26 AM, Al - N1API <n1api@...> wrote:

A good operator will know what the called or calling stations wants and respond accordingly.

For S&P in CW my working keys are F4 My call, and F2 exchange.  But I also programed F5 My call slowed down about 4 WPM, (which works great also when answering CQ's for operators not running 35 WPM or so), and also F6 which is my exchange slowed down twice also about 4 WPM slower there is also a longer space between the {EXCH}  {EXCH} to either distinguish between the reports or time to hit ESC to only sent the reply once.

Works great for me.

Al

Re: N1MM+ & WSJT-X integration: A Moving Target

Don Hill AA5AU <aa5au@...>
 

Thanks Jim.

Distribute the PDF as you like. If the N1MM+ team wants to post it on their
site. That's fine with me.

Don AA5AU

-----Original Message-----
From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf
Of Jim Cooper
Sent: Wednesday, August 14, 2019 8:47 PM
To: Victor Paul
Cc: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] N1MM+ & WSJT-X integration: A Moving Target

On 14 Aug 2019 at 18:38, Victor Paul wrote:

Not sure who would need to do what,
but I think it would be great if a
.pdf version of it could be loaded
into the Additional Support Files
folder in the Downloads section of
the main N2MM+ website.
Today I made myself a PDF of that document,
with most all of the links in it appended to
the PDF ...

If anyone wants it, to upload or for themselves,
let me know.

Jim W2JC

N1MM+/WSJT-X feature requests (Decode List Font, FT4/FT8 mode switch)

Victor Paul
 

A couple ideas for possible enhancements to the N1MM+/WSJT-X integration:

1) Add font sizer buttons to the WSJT-X Decode List window to increase/decrease font size as on other N1MM+ windows.
2) Make it so that when operating FT8 and you type FT4<enter> into the N1MM+ entry window, that it tasks WSJT-X For EW1 to actually switch to FT4 mode (and vice versa).  At present in order to switch modes you have to do it from the Mode pull-down on the WSJT-X- ForEW1 panel.  (I'd rate this a low priority, unless it turns out to be a pretty straightforward code tweak).

Victor WB0TEV / V31VP

Runtime error on 2nd launch of WSJT-X from N1MM+

Victor Paul
 

This happened to me several times tonight so I closed everything down and took notes on how I elicited a runtime error message.  Recipe is as follows:
Many of these steps are likely not necessary to cause the problem but they do seem to be sufficient.  Windows 7 64-bit. N1MM+ V1.0.7900.0 (13 Aug 2019). WSJT-X 2.1.0.

Launch N1MM+ (double click desktop icon).
EW, Log, Telnet and Network Status Windows come up.
Close network status window (X).
Minimize Telnet window (_)
Type FT8<enter> into EW.
WSJT-X ForEW1, associated WSJT-X Wide Graph, WSJT-X Decode List 1 and N1MM-WSJT Connection -1 windows come up, with the latter showing green and Decode list populating nicely.  WSJT-X is actually in FT4 mode, the way it was when last used.
Minimize Log window, it flies down to just above the task bar next to the Telnet window icon.
Minimize decode list window which flies down to the task bar.
Minimize the EW, it flies down to the task bar.
Raise the log window.
Raise the decode list.
Switch to FT8 mode using the mode pull-down in WSJT-X.
Clear decode list window (max lines = 10 FWIW)
I note that the N1MM-WSJT Connection -1 panel is no where to be found, I don't see it in the task bar, and it's  not hiding under any of the other panels.
Close the Decode List panel (X)
Close WSJT-X ForEW1 panel (X). It goes away and takes the Wide graph with it as expected.
Raise the N1MM+ EW panel by clicking on the only N1MM+ icon in the task bar (hoving over it shows there are no more beneath it).
Telnet window and EW window fly up to the desktop.
Minimize the Telnet Window (_)
Type FT8<enter> into EW.

and up comes this:

N1MMLogger.net - Version 1.0.7900.0
Built: 8/13/2019 1:13:14 PM
Microsoft Windows NT 6.1.7601 Service Pack 1,64:1,en-US,en-US
Error occurred at: 8/14/2019 9:59:21 PM in Thread:
---------------------------------------------------------------------------------------
System.NullReferenceException: Object reference not set to an instance of an object.
   at N1MMLogger.Net.WSJTRadio.RadioTCPListening() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\WSJTRadio.vb:line 115
---------------------------------------------------------------------------------------


Call Stack before the runtime error:   at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
   at System.Environment.get_StackTrace()
   at N1MMLibrary.SharedLib.CallStackString() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Library\Classes\SharedCode.vb:line 89
   at N1MMLogger.Net.SharedCode.HandleError(Exception e, String PortName, String Info) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Modules\SharedCode.vb:line 186
   at N1MMLogger.Net.WSJTRadio.RadioTCPListening() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\WSJTRadio.vb:line 150
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

Victor WB0TEV / V31VP

Unable to Obtain a Functioning Second WSJT-X in SO2R

Tony Gasperino
 

Using V1.0.7900, I am unable to obtain a second instance of WSJT-X FT4 operating correctly in SO2R. When I open the first instance of FT4 in either Radio 1 or Radio 2, the CAT connection, Tune and Enable TX all work as expected, as long as the target radio has TX focus. If the radio has only RX focus, then the Radio receives OK, but when FT4 TX is enabled, TX occurs on the other Radio (with no RF), which has the red TX dot. If the N1MM TX dot is at the first FT4 radio, all works as expected.

 

Now if FT4 is working correctly on Radio 1 entering FT4 on Radio 2 brings up the Error Message below along with the FT4 Main Panel, Waterfall, Decode List, and Radio Connection window. However, there is no CAT connection or Tune/Enable TX operation, only active Receive.

 

So I end up with one Radio with an active FT4 and the other Radio with an inactive FT4. Either Radio can end up with the working FT4, as long as it is the Radio on which FT4 is first opened. Opening the second instance of FT4 results in the Error Message.

 

I’m using 2 TS590s, a YCCC SO2R+ Box, WSJT-X V2.1.0, and a Windows 7 (Z400 Quadcore) machine.

 

Last week, using N1MM V1.0.7870, I had FT4 working on both radios, although to shift FT4 TX from one radio to the other, the N1MM Entry Window TX focus had to be shifted to the other radio also.

 

I’m not versed in Windows NT to understand what the Error Message means and thus troubleshoot the problem. I’m wondering if the SO2R box has some role in this issue. I would appreciate any suggestions on how to remedy this problem.

 

73, Tony, WS7V

 

 

N1MMLogger.net - Version 1.0.7900.0

Built: 8/13/2019 11:13:14 AM

Microsoft Windows NT 6.1.7601 Service Pack 1,64:1,en-US,en-US

Error occurred at: 8/14/2019 4:34:32 PM in Thread:

---------------------------------------------------------------------------------------

System.NullReferenceException: Object reference not set to an instance of an object.

at N1MMLogger.Net.WSJTRadio.RadioTCPListening() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\WSJTRadio.vb:line 115

---------------------------------------------------------------------------------------

 

 

Call Stack before the runtime error: at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)

at System.Environment.get_StackTrace()

at N1MMLibrary.SharedLib.CallStackString() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Library\Classes\SharedCode.vb:line 89

at N1MMLogger.Net.SharedCode.HandleError(Exception e, String PortName, String Info) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Modules\SharedCode.vb:line 186

at N1MMLogger.Net.WSJTRadio.RadioTCPListening() in C:\N1MM+Source\N1MM Logger on. .NET\N1MM Logger.Net\Forms\WSJTRadio.vb:line 150

at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

at System.Threading.ThreadHelper.ThreadStart()

Re: Loss of radio 2 control with ver 1.0.7900

Rick Ellison
 

I have posted an Experimental version that will correct the RTE that users are seeing.. I made a change and it was working fine on my system so I released it.. I still have not had it crash on my system but this version corrects the problem..

 

https://n1mmwp.hamdocs.com/n1mmwpfiles/Download/Program%20Files/Experimental%20Versions/N1MM%20Logger%2B%20Update%201.0.7900%20For%20K1TTT-2.exe

 

73 Rick N2AMG

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Gary Hembree
Sent: Wednesday, August 14, 2019 8:07 PM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] Loss of radio 2 control with ver 1.0.7900

 

Lew,

I upgraded my K3 SO2R N1MM+ setup to 1.0.7900 this morning and got a RTE when I tried to run WSJT-X from Radio 1.  Closed that instance and was then unable to open WSJT-X again until I closed and reloaded N1MM+.  However, I got the same RTE every time so I reverted back to 1.0.7883 and my setup is working normally.  When I have a chance I’ll document the RTE and file a bug report.  Too many other more pressing matters at the moment.

 

Something got changed with the K3 code in January around Ver 1.0.7467.  N1MM+ now has trouble following band and mode changes with multi-mode, multi-band logs with my SO2R K3 setup.  I haven’t take the time to do extensive documentation of this bug but just work around it.

 

73

Gary, N7IR

 

Sent: Wednesday, August 14, 2019 3:45 PM

Subject: [N1MM+] Loss of radio 2 control with ver 1.0.7900

 

Upgraded to ver 1.0.7900 from Ver 1.0.7883 and got an error when loading WSJT-X from inside N1MM+ on radio 2 only.  No frequency communication between radio 2 and N1MM+.  I did not get the run time error documented as I thought the problem was 2 new security updates that had just been run through Windows 10. I deleted the Windows updates and went back to Ver 1.0.7883 and things are back to normal.
Anybody else have radio 2 problems between N1MM+ and WSJT-X with Ver 1.0.7900?   Should I go back and recreate the run time error so that the coder gurus know what happened?
    73 and I remain,
    Lew     w7ew

 


Virus-free. www.avast.com

Re: SO2R and X-keys will it work?

Kari Gustafsson SM0HRP
 

Hi Andy, not what I know. I have tested one x-keys panel programmed with keystrokes from different keyboards but x-keys wont recognises these as from the same keyboard :( 
But for a programmer it should be easy perhaps to add some script before the keyboard entry in x-keys? 

Re: Loss of radio 2 control with ver 1.0.7900

Tim K9WX
 

Thanks, Rick.  The experimental version appears to have eliminated the RTE I was seeing when running the second instance of WSJT-X.

Tim K9WX