Date   
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: 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. 

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/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

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: 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

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: WAE changes in Version 1.0.7900 (Aug 13, 2019

VE9AA - Mike
 

p.s.- another thank-you for the "4" in the QTC popup window. ( I already knew about 1, 2, 3)
 Whether I missed it in the documentation, or it's a new feature...it's really great not to have to search for the mouse or paddles to send the QTC header. Sooooo, nice!

This contest is almost too easy ;-) from the DX side.  Those EU's do all the heavy lifting(listening/decoding/typing) in this one and I appreciate their code copying skills (better than mine)

dit dit

Mike VE9AA

Re: WAE changes in Version 1.0.7900 (Aug 13, 2019

VE9AA - Mike
 

OK, I have confirmed I can toggle stereo headphone audio now with the QTC window popped up. (a BIG thank you and sorry for the confusion which was totally my fault.)

I do not however have function key messages passing to the "other" radio in SO2R mode. (so, for example, if I wished to scan the bandmap by doing a CTRL+up arrow on the other radio, or send my call (a little unlikely, but possible on the last QTC), the function key macros only seem pass to the active (transmit) radio.

It's unlikely when sending QTC's that I'd try to make an actual QSO on the 'other' radio early on, but this past weekend I did tune the other radio A LOT....so I appreciate very much that stereo headphone audio is toggleable (is that a word?), but it would be really nice if CTRL+UP Arrow(or subsets thereof) could help me line up a new Q or mult on the other radio when sending QTC's on the active radio.

If it's not possible, I certainly understand and will just do it the way I did it this weekend.....good ol' VFO and ears and watch the bandmap, hi !

Thanks Team !

A very happy VE9AA.....Mike

Re: Dual CQ & Dual Keyboards

Lyubomir Slavov, OR2F
 

Hi Simon,

IMO - any inhibit of the TX-keyboard wouldn't be sensible, at least because the send message couldn't be terminated before its end.
...

I had the same issue (mostly at the end of the contests).
The simplest and fastest solution (but not efficient for me) was to listen in stereo mode, i.e. only with one ear to each radio, all the time when tried dueling-CQ.
It was difficult but worked - left ear towards left hand and the same for the right :)

After several contests, I built a traffic lights - simple low intensity LED-bars controlled by PTT and attached to each keyboard.
(see the attached snapshot please)
... and seem like this my problem is already solved :)

Hope this can help you too !

73,
Leo / OR2F

On Wed, 14 Aug 2019 at 07:19, Simon Ravnič via Groups.Io <s53zo=t-2.net@groups.io> wrote:
Any feedback on this please? 

My biggest fear was that nobody would reply and now we are here :)

73
Simon, S53ZO

Re: Ten Ten Log Problem

Les Elliott
 

Rory, works OK here, send me a copy of your tentenrtty.udc file.
 
QSO:  2855 PH 2019-08-14 1540 G4OGB         LES NM G           K5CKS         RORY         68322    AR
 
Les, G4OGB
 

Sent: Wednesday, August 14, 2019 3:55 PM
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

Ten Ten Log Problem

Rory Bowers
 

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: WAE changes in Version 1.0.7900 (Aug 13, 2019

VE9AA - Mike
 

A kind gentleman in Ontario has set me straight.  We're talking about the same key...doh!

I'll test later and report back. Thanks much.

(what a goof I am )

Sorry all !

MikeAA

Re: WAE changes in Version 1.0.7900 (Aug 13, 2019

VE9AA - Mike
 

By the way, I am 100% sure it's the TILDE ~ key I am talking about,  for toggling stereo mode on/off in my headphones.

  I use it hundreds of times/contest. (I just used it a few minutes ago in the CWT)

..but I haven't checked the new version in a WAE scenario yet....I am thinking no change as you are talking about the ' key, which I have never used.

TIA !

Mike VE9AA

Re: WAE changes in Version 1.0.7900 (Aug 13, 2019

VE9AA - Mike
 


Good morning Rick !

 

You are referring to rx foci, but specifically I am talking about toggling stereo on/off in my headphones.

I’ve yet to test, but I think this may still not work with the QTC window if you’ve programmed the ‘ key to pass through.

From https://n1mmwp.hamdocs.com/setup/keyboard-shortcuts/?hilite=%27%7E%27

 

SO2R Key Assignments

  • <snip>

  • Grave accent, backquote, or unshifted tilde key (~) Toggle STEREO mode on/off, or toggle Auto/PTT modes with modified DXD . Notes: On US keyboards, the key we are talking about is the key just to the left of the number 1 key.

    This is the one I use ! ~

     

    Tnx

     

    Mike VE9AA

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

ve3ki
 

Based on the responses here, the problem appears to be internal to WSJT-X. It is not caused by using N1MM+ (it happens to people who are not using N1MM+), and it will not be fixed by using WSJT-X from N1MM+ (it also happens to people who are using WSJT-X from N1MM+).

73,
Rich VE3KI


On Wed, Aug 14, 2019 at 08:48 AM, va3dx wrote:
I have experienced the same , however no N1MM. Just K3, rigexpert standard and wsjt.
 
Va3dx


On Aug 14, 2019, at 07:59, Chuck Dietz <w5prChuck@...> wrote:

I run both N1MM and WSJT at the same time. Go into the N1MM configuration tab all the way to the right is a tab for WSJT. Fill in the file location if WSJT and you will be able to load WSJT from the last entry on the “windows” tab of N1MM. This will allow you to log WSJT FT8 contacts in to N1MM and, hopefully, solve the problem. 
 
Chuck W5PR 

On Wed, Aug 14, 2019 at 6:09 AM Rich K1DJ via Groups.Io <k1dj93=yahoo.com@groups.io> wrote:
Sorry, a too quick finger mistake.  I have not yet mastered using N1MM+ with WSJT-X.  So when I operate FT-8, N1MM+ is not running, and the rig is controlled directly by the WSJT-X software.  And my K3S occasionally “forgets to transmit” when WSJT goes into transmit mode.  So perhaps N1MM+ is not causing it?
Rich, K1DJ

 

On Aug 14, 2019, at 7:01 AM, Rich K1DJ via Groups.Io <k1dj93@...> wrote:

Same here.  K3S solo op N1MM+ WSJT-X

 

On Aug 13, 2019, at 9:54 PM, Dan Violette - KI6X <danki6x@...> wrote:

  • Every once in a while the radio "forgets" to transmit in FT8 and FT4.  Usually the next cycle it fires off OK.
    Setup: SO2R, N1MM+, MicroHam MR2K+, 2 Elecraft K3s

 

Yes, same problem using K3, WSJT-X, DXLabs (logging) with sound card direct into K3 and serial PTT.  Think our only same items are K3/WSJT-X.  Dan KI6X

 

 

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

va3dx
 

I have experienced the same , however no N1MM. Just K3, rigexpert standard and wsjt.

Va3dx


On Aug 14, 2019, at 07:59, Chuck Dietz <w5prChuck@...> wrote:

I run both N1MM and WSJT at the same time. Go into the N1MM configuration tab all the way to the right is a tab for WSJT. Fill in the file location if WSJT and you will be able to load WSJT from the last entry on the “windows” tab of N1MM. This will allow you to log WSJT FT8 contacts in to N1MM and, hopefully, solve the problem. 

Chuck W5PR 

On Wed, Aug 14, 2019 at 6:09 AM Rich K1DJ via Groups.Io <k1dj93=yahoo.com@groups.io> wrote:
Sorry, a too quick finger mistake.  I have not yet mastered using N1MM+ with WSJT-X.  So when I operate FT-8, N1MM+ is not running, and the rig is controlled directly by the WSJT-X software.  And my K3S occasionally “forgets to transmit” when WSJT goes into transmit mode.  So perhaps N1MM+ is not causing it?
Rich, K1DJ


On Aug 14, 2019, at 7:01 AM, Rich K1DJ via Groups.Io <k1dj93@...> wrote:

Same here.  K3S solo op N1MM+ WSJT-X


On Aug 13, 2019, at 9:54 PM, Dan Violette - KI6X <danki6x@...> wrote:

  • Every once in a while the radio "forgets" to transmit in FT8 and FT4.  Usually the next cycle it fires off OK.
    Setup: SO2R, N1MM+, MicroHam MR2K+, 2 Elecraft K3s

 

Yes, same problem using K3, WSJT-X, DXLabs (logging) with sound card direct into K3 and serial PTT.  Think our only same items are K3/WSJT-X.  Dan KI6X

Re: K3/0 MINI and N1MM+

ve3ki
 

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

Re: WAE changes in Version 1.0.7900 (Aug 13, 2019

Rick Ellison
 

Mike.

N1MM doesn’t use the tilde for any command. It’s the “Grave Accent” (`) key which is the key below the tilde that does the switching for SO2R audio.

 

73 Rick N2AMG

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of VE9AA - Mike
Sent: Tuesday, August 13, 2019 10:31 PM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] WAE changes in Version 1.0.7900 (Aug 13, 2019

 

It's very late here and I am on the road. (so maybe my question is premature, as I have not tested this yet...maybe tmw.)
My one question is for change 9A:
Is that a typo? My understanding is that it was supposed to be the tilde key ~ (left of the #1 on Na KB's) to be passed, not the ' key.
(to control SO2R headphone audio)

That-or I just misunderstood Ricks previous and that (headphone audio) change was not made.

Thanks

Mike VE9AA

Version 1.0.7900 (Aug 13, 2019)

  1. WSJT Decode List: Added SNR to the list display. (Coded by N2AMG)
  2. WSJT Decode List: During the WWDIGI contest shows assumed points for each station in the list. (Coded by N2AMG)
  3. WSJT Decode List and WSJT Radio window were not saving their locations correctly. This is now fixed. (Coded by N2AMG)
  4. Winkey: Fix problem seen by one XP user. (KE2D) (Coded by N2IC)
  5. WSJT Decode List: Clicking in the window anyplace will now shift Radio and keyboard focus to the parent Entry Window of the list. (Coded by N2AMG)
  6. Fix Blacklist Spots and Blacklist Spotters when using Telnet windows to edit their callsigns. (Coded by N2IC)
  7. WWDIGI: Change Cabrillo format to 3.0 (W0YK) (Coded by N1MM)
  8. Cabrillo: Changed V3.0 mode for Digital to "DIGI" (W0YK) (Coded by N1MM)
  9. QTC Window Changes (Coded by N2AMG)
    • Allows ` key to be passed to the Entry Window.
    • Allows F1-F12 passed to the Entry Window Note: Pressing the TU F-key will Send the TU message, Save the current QTC in SQTC or RQTC and close the QTC Window. Pressing the Agn F-Key will send the AGN message associated with the current QTC line in the QTC window.
    • In CW RQTC allows for keypress 1, 2, 3, to be configured to what the user wants to send. See Setup window.
    • in CW SQTC allows te QTC field spacing to be configured. Default is one Space character. See Setup window.


Virus-free. www.avast.com

K3/0 MINI and N1MM+

Jorge Diez - CX6VM
 

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