Date   
Re: Bad cw(uneven spacing)

Jim W7RY
 

Try moving it to a USB 2.0 port?


Thanks
73
Jim W7RY
On 3/19/2019 9:19 AM, Girard Donald via Groups.Io wrote:

Hi John, I am using DTR and RTS and virtual com port so no connections on usb port for cw. Somehow the radio anan 10-e is acting up now. May have to redo set up. Previous messages were perfectly right... as I increase the speed it gets worse... to be continued... 

NB: it used to work fine..... 

Thanks 

Donald
VE2IR

On Tuesday, March 19, 2019, 3:59:44 a.m. GMT, Girard Donald via Groups.Io <girarddonald@...> wrote:


Thanks to all of your ideas there are very appreciated, now it used to  worke fine. As most mentioned about timing and part of the computer being busy, I will definetly looke that way and in fact now that you mentioned it, it all make sense......... to be continued...... 

Donald
VE2IR

On Friday, March 15, 2019, 1:35:39 a.m. GMT, John Bednar via Groups.Io <k3ct@...> wrote:


Girard,

 

Are you using a USB to COM port converter? The converters that use a FTDI chipset work well for sending CW. The Prolific chipset based USB to COM converters have long latency and are not suitable for sending CW.

 

If you are using a FTDI converter with a USB Hub, bypass the hub. Connect the converter directly to the computer.

 

John, K3CT

 

From: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io> On Behalf Of Girard Donald via Groups.Io
Sent: Thursday, March 14, 2019 12:23 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] Bad cw(uneven spacing)

 

First Thanks for your interest, N1MM keyer, and the sdr anan 10-e has its own but the radio's keyer is working fine only the N1MM weird spacing really hard to copy. Any idea !

 

On Wednesday, March 13, 2019, 5:35:32 p.m. GMT, Drew Vonada-Smith K3PA <drew@...> wrote:

 

 

What is the keying method/interface?


Re: Multiple ini files

NS2N_PTA@...
 

Ah , yes. On my system, that line looks like a folder header for the .baks. The ini extension does not show.

Rest of the procedure went OK: had to reconsider what the new .inis were named ( Iincluded N1MM in the name and then promptly forgot).

Thank you 7UT

Paul NS2N

Re: Multiple ini files

Andy (KU7T)
 

Your Windows is likely just not showing the file extensions. The files you are seeing are named *.INI.bak. The INI extension may be hidden. In this case, look for a file called "N1MM Logger" and has a type of INI file. 

73
Andy
KU7T


From: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io> on behalf of NS2N_PTA@... <NS2N_PTA@...>
Sent: Tuesday, March 19, 2019 11:46 AM
To: N1MMLoggerPlus@groups.io
Subject: [N1MMLoggerPlus] Multiple ini files
 
Need to set up for a different radio.  Documentation 2.1.3

Created two shortcuts. Next step is to make a copy of  N1MM Logger.ini from the Documents, I don't see that particular file in there, but a series of files ending with Monday.ini, Teusday.ini. instead.

Windows7 Prof. being used by luddite. Where to go from here?

Paul NS2N

Multiple ini files

NS2N_PTA@...
 

Need to set up for a different radio.  Documentation 2.1.3

Created two shortcuts. Next step is to make a copy of  N1MM Logger.ini from the Documents, I don't see that particular file in there, but a series of files ending with Monday.ini, Teusday.ini. instead.

Windows7 Prof. being used by luddite. Where to go from here?

Paul NS2N

Re: 60m QSO - DDE output string incorrectly shows 80m

zl3ga
 

Thanks Larry, I will check that out. The gateway app may need an update.
73
Geoff ZL3GA

On Wed, 20 Mar 2019, 1:18 AM Larry K8UT, <k8ut@...> wrote:
Geoff,

The RadioInfo packets sent via UDP from N1MM+ to the gateway do not contain a <band> XML tag, only Frequency. Frequency is being sent correctly.

The incorrect band interpretation must be getting inserted by the gateway. 

-larry (K8UT)

------ Original Message ------
From: "zl3ga" <geoff.clark22@...>
Sent: 2019-03-19 03:31:05
Subject: Re: [N1MMLoggerPlus] 60m QSO - DDE output string incorrectly shows 80m

And hopefully a further clue to the developers, ADIF export is working fine with it correctly identifying the <band> field  as 60m. See below.
73
Geoff ZL3GA

<CALL:6>ZL4DVG <QSO_DATE:8>20190318 <TIME_ON:6>041543 <BAND:3>60M <STATION_CALLSIGN:5>ZL3GA <FREQ:7>5.36205 <CONTEST_ID:2>DX <FREQ_RX:7>5.36205 <MODE:2>CW <NAME:3>Dan <RST_RCVD:3>599 <RST_SENT:3>599 <OPERATOR:5>ZL3GA <CQZ:2>32 <STX:3>117 <APP_N1MM_POINTS:1>1 <APP_N1MM_RADIO_NR:1>1 <APP_N1MM_CONTINENT:2>OC <APP_N1MM_RUN1RUN2:1>1 <APP_N1MM_RADIOINTERFACED:1>1 <APP_N1MM_ISORIGINAL:4>True <APP_N1MM_NETBIOSNAME:10>GEOFF-VAIO <APP_N1MM_ISRUNQSO:1>0 <EOR>

Re: Problem with BARTG TIME2 macro

InMiami Ale
 

Thanks for your reply Rich, I know the configuration procedure, on the log there were no errors. At the next contest I just remove tim2 and everything returns as before. 73 Ale

Re: Bad cw(uneven spacing)

Steve London
 

I encourage those of you with CW keying issues to consider how much your time is worth.

For $18 US, your problems could be solved. http://hamprojects.info/mortty/

73,
Steve, N2IC

On 03/19/2019 08:19 AM, Girard Donald via Groups.Io wrote:
Hi John, I am using DTR and RTS and virtual com port so no connections on usb port for cw. Somehow the radio anan 10-e is acting up now. May have to redo set up. Previous messages were perfectly right... as I increase the speed it gets worse... to be continued...
NB: it used to work fine.....
Thanks
Donald
VE2IR
On Tuesday, March 19, 2019, 3:59:44 a.m. GMT, Girard Donald via Groups.Io <girarddonald=yahoo.ca@groups.io> wrote:
Thanks to all of your ideas there are very appreciated, now it used to  worke fine. As most mentioned about timing and part of the computer being busy, I will definetly looke that way and in fact now that you mentioned it, it all make sense......... to be continued......
Donald
VE2IR
On Friday, March 15, 2019, 1:35:39 a.m. GMT, John Bednar via Groups.Io <k3ct=verizon.net@groups.io> wrote:
Girard,
Are you using a USB to COM port converter? The converters that use a FTDI chipset work well for sending CW. The Prolific chipset based USB to COM converters have long latency and are not suitable for sending CW.
If you are using a FTDI converter with a USB Hub, bypass the hub. Connect the converter directly to the computer.
John, K3CT
*From:* N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io> *On Behalf Of *Girard Donald via Groups.Io
*Sent:* Thursday, March 14, 2019 12:23 AM
*To:* N1MMLoggerPlus@groups.io
*Subject:* Re: [N1MMLoggerPlus] Bad cw(uneven spacing)
First Thanks for your interest, N1MM keyer, and the sdr anan 10-e has its own but the radio's keyer is working fine only the N1MM weird spacing really hard to copy. Any idea !
On Wednesday, March 13, 2019, 5:35:32 p.m. GMT, Drew Vonada-Smith K3PA <@K3PA <mailto:@K3PA>> wrote:
What is the keying method/interface?

Re: Bad cw(uneven spacing)

Girard Donald
 

Hi John, I am using DTR and RTS and virtual com port so no connections on usb port for cw. Somehow the radio anan 10-e is acting up now. May have to redo set up. Previous messages were perfectly right... as I increase the speed it gets worse... to be continued... 

NB: it used to work fine..... 

Thanks 

Donald
VE2IR

On Tuesday, March 19, 2019, 3:59:44 a.m. GMT, Girard Donald via Groups.Io <girarddonald@...> wrote:


Thanks to all of your ideas there are very appreciated, now it used to  worke fine. As most mentioned about timing and part of the computer being busy, I will definetly looke that way and in fact now that you mentioned it, it all make sense......... to be continued...... 

Donald
VE2IR

On Friday, March 15, 2019, 1:35:39 a.m. GMT, John Bednar via Groups.Io <k3ct@...> wrote:


Girard,

 

Are you using a USB to COM port converter? The converters that use a FTDI chipset work well for sending CW. The Prolific chipset based USB to COM converters have long latency and are not suitable for sending CW.

 

If you are using a FTDI converter with a USB Hub, bypass the hub. Connect the converter directly to the computer.

 

John, K3CT

 

From: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io> On Behalf Of Girard Donald via Groups.Io
Sent: Thursday, March 14, 2019 12:23 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] Bad cw(uneven spacing)

 

First Thanks for your interest, N1MM keyer, and the sdr anan 10-e has its own but the radio's keyer is working fine only the N1MM weird spacing really hard to copy. Any idea !

 

On Wednesday, March 13, 2019, 5:35:32 p.m. GMT, Drew Vonada-Smith K3PA <drew@...> wrote:

 

 

What is the keying method/interface?

Re: Configure page

Larry K8UT
 

Hi Henry

150% will definitely cause many text fields to overflow their boundaries in N1MM dialog windows. After some experimentation, I settled on 120% as the largest size that still fit everywhere.

-larry (K8UT)

------ Original Message ------
From: k1wcc@...
Sent: 2019-03-18 10:35:29
Subject: Re: [N1MMLoggerPlus] Configure page

The problem was.......my screen scale setting was at 150%. This did not allow the full display of the CONFIGURE page, and it bumped the top of the screen when attempting to drag it.

Setting back to 100% solved the problem. Works great now. Tough getting old.

Tnx for starting me thinking, Tom!

Henry  K1WCC 

Re: 60m QSO - DDE output string incorrectly shows 80m

Larry K8UT
 

Geoff,

The RadioInfo packets sent via UDP from N1MM+ to the gateway do not contain a <band> XML tag, only Frequency. Frequency is being sent correctly.

The incorrect band interpretation must be getting inserted by the gateway. 

-larry (K8UT)

------ Original Message ------
From: "zl3ga" <geoff.clark22@...>
Sent: 2019-03-19 03:31:05
Subject: Re: [N1MMLoggerPlus] 60m QSO - DDE output string incorrectly shows 80m

And hopefully a further clue to the developers, ADIF export is working fine with it correctly identifying the <band> field  as 60m. See below.
73
Geoff ZL3GA

<CALL:6>ZL4DVG <QSO_DATE:8>20190318 <TIME_ON:6>041543 <BAND:3>60M <STATION_CALLSIGN:5>ZL3GA <FREQ:7>5.36205 <CONTEST_ID:2>DX <FREQ_RX:7>5.36205 <MODE:2>CW <NAME:3>Dan <RST_RCVD:3>599 <RST_SENT:3>599 <OPERATOR:5>ZL3GA <CQZ:2>32 <STX:3>117 <APP_N1MM_POINTS:1>1 <APP_N1MM_RADIO_NR:1>1 <APP_N1MM_CONTINENT:2>OC <APP_N1MM_RUN1RUN2:1>1 <APP_N1MM_RADIOINTERFACED:1>1 <APP_N1MM_ISORIGINAL:4>True <APP_N1MM_NETBIOSNAME:10>GEOFF-VAIO <APP_N1MM_ISRUNQSO:1>0 <EOR>

Re: 60m QSO - DDE output string incorrectly shows 80m

zl3ga
 

And hopefully a further clue to the developers, ADIF export is working fine with it correctly identifying the <band> field  as 60m. See below.
73
Geoff ZL3GA

<CALL:6>ZL4DVG <QSO_DATE:8>20190318 <TIME_ON:6>041543 <BAND:3>60M <STATION_CALLSIGN:5>ZL3GA <FREQ:7>5.36205 <CONTEST_ID:2>DX <FREQ_RX:7>5.36205 <MODE:2>CW <NAME:3>Dan <RST_RCVD:3>599 <RST_SENT:3>599 <OPERATOR:5>ZL3GA <CQZ:2>32 <STX:3>117 <APP_N1MM_POINTS:1>1 <APP_N1MM_RADIO_NR:1>1 <APP_N1MM_CONTINENT:2>OC <APP_N1MM_RUN1RUN2:1>1 <APP_N1MM_RADIOINTERFACED:1>1 <APP_N1MM_ISORIGINAL:4>True <APP_N1MM_NETBIOSNAME:10>GEOFF-VAIO <APP_N1MM_ISRUNQSO:1>0 <EOR>

Re: Bad cw(uneven spacing)

Girard Donald
 

Thanks to all of your ideas there are very appreciated, now it used to  worke fine. As most mentioned about timing and part of the computer being busy, I will definetly looke that way and in fact now that you mentioned it, it all make sense......... to be continued...... 

Donald
VE2IR

On Friday, March 15, 2019, 1:35:39 a.m. GMT, John Bednar via Groups.Io <k3ct@...> wrote:


Girard,

 

Are you using a USB to COM port converter? The converters that use a FTDI chipset work well for sending CW. The Prolific chipset based USB to COM converters have long latency and are not suitable for sending CW.

 

If you are using a FTDI converter with a USB Hub, bypass the hub. Connect the converter directly to the computer.

 

John, K3CT

 

From: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io> On Behalf Of Girard Donald via Groups.Io
Sent: Thursday, March 14, 2019 12:23 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] Bad cw(uneven spacing)

 

First Thanks for your interest, N1MM keyer, and the sdr anan 10-e has its own but the radio's keyer is working fine only the N1MM weird spacing really hard to copy. Any idea !

 

On Wednesday, March 13, 2019, 5:35:32 p.m. GMT, Drew Vonada-Smith K3PA <drew@...> wrote:

 

 

What is the keying method/interface?

CTY-2904 Country Files - 19 March 2019

Jim Reisert AD1C
 

The Country (CTY) Files were updated on 19 March 2019:

http://www.country-files.com/cty-2904-19-march-2019/

For installation instructions, start at:

http://www.country-files.com/

Hover your mouse over the word Contest in the menu, then select the
software you are using.

To install the file, follow the link to your software at the top of the page.

If you are interested in a bigger CTY.DAT for everyday logging, you can get
it here:

http://www.country-files.com/big-cty-19-march-2019/

Note that the release notes (and Version Entity) for this larger file are
different than what is shown below. There is a separate link to them.

As a reminder, there is an RSS feed of the latest country file announcements:

http://www.country-files.com/feed/

Here are the release notes:

19 March 2019 (CTY-2904)
VER20190319, Version entity is Tuvalu, T2

Added/changed Entities/Prefixes/Callsigns:

* 4U500M is Vienna Intl Ctr, *4U1V
* 9M4CRP is East Malaysia, 9M6
* VP8CTR is Antarctica, CE9 in ITU zone 73
* KC4USB is Antarctica, CE9 in CQ zone 12
* RI1ANX is Antarctica, CE9 in CQ zone 38, ITU zone 67
* RI1ANZ is Antarctica, CE9 in CQ zone 39, ITU zone 69
* E51AUZ and E51NPQ are both North Cook Islands, E5/n
* EA6LU/P is Balearic Islands, EA6
* EA4URE/9 is Ceuta & Melilla, EA9
* TO19A is Reunion Island, FR
* GB0SPD, GB1SPD, GB2SPD and GB5SPD are all Northern Ireland, GI
* GB5AG is Scotland, GM
* II0IDR/NAVY and II8ICN/NAVY are both Italy, I
* IQ0AH/P and IY0NV are both Sardinia, IS
* K0NW, W2FV and WQ3U are all United States, K in CQ zone 3, ITU zone 6
* AK9D, K4DG, W7II, WA2JQZ and WY6K are all United States, K in CQ zone 4, ITU zone 7
* AC4GW, KN4DUA and WW5M are all United States, K in CQ zone 4, ITU zone 8
* AA0O, N6PAT, NP3K, W7DO, W7IY and W9DC are all United States, K in CQ zone 5, ITU zone 8
* K8KH, K8RN and NU2A are all Mariana Islands, KH0
* AH0FM and KH0UM are both Guam, KH2
* KB6INB, KB7WDC, KE7QML, KH8Z, KI4YOG, WA6IIQ and WB6PIO are all Hawaii, KH6
* K7SGA, KF7GKY, KJ4WIQ, KW1W and N7DBN are all Alaska, KL
* AA0WX, KC2VCR, KC8BFN, KG4GYO, KN4SKZ and N4CIE are all Puerto Rico, KP4
* LU2CRV/D, LU2EE/D, LU3DRP/E, LU5DGG/D, LU5DTF/D, LU8EHV/D and LW7EDH/D
are all Argentina, LU
* LU6WG/W and LU8XW/X are both Argentina, LU in ITU zone 16
* 4U500M is Austria, OE
* R108M, R120MG, R160ASP, R160B, R160IP, R160NN, R160SE, R1961G, R2019LS,
RA2FDX/3, RA9UUY/6, RG61PP, RM0L/1, RU9SO/6, RX3XX/N, UE23DKA, UE23DSA,
UE23DZO and UF0W/6 are all European Russia, UA
* R9XC/1 is European Russia, UA in ITU zone 20
* R160PM is European Russia, UA in CQ zone 17, ITU zone 30
* R777AN is Kaliningrad, UA2
* R160DMP and R160RP are both Asiatic Russia, UA9
* RK4PA/9 is Asiatic Russia, UA9 in ITU zone 20
* R100W is Asiatic Russia, UA9 in CQ zone 16
* RA/OK1DWF is Asiatic Russia, UA9 in CQ zone 19, ITU zone 34
* VE2EW is Canada, VE in CQ zone 2, ITU zone 4
* VK6MB/1 and VK6MB/3 are both Australia, VK
* VK5MAV/6 is Australia, VK in CQ zone 29, ITU zone 58
* VK9JD is Christmas Island, VK9X

Removed Entities/Prefixes/Callsigns:

* 4U1XMAS in Vienna Intl Ctr, *4U1V
* DP0GVN/P and RI63ANT in Antarctica, CE9
* EA2EZ/P and EA9HU/7 in Spain, EA
* GB0KEY and GB2KW in Scotland, GM
* GB0CQD in Wales, GW
* HC8GET/2 in Ecuador, HC
* 4U8F and 4U8FOC in Italy, I
* IR0FOC in Sardinia, IS
* AA4NU, AJ6T, K0MP, K4IQJ, K4TO, K5GDX, K5ROE, K8FC, KE4ETY, KH7AR,
KJ4LTA, KL0S, KL2SX, N1CC, N3BBQ, N4VN, N7HHS, N9BD, NB4M, NJ8M, W0YK,
W3USA, W6IHG, W8WOM, WB4GHZ, WT5L, WX7B, WY7KY and WY7SS in United States, K
* KC5SPG in Mariana Islands, KH0
* KF4UFC in Guam, KH2
* AJ8HT, W2UNS, W6CWJ and W6UNX in Hawaii, KH6
* K8OUA and KD7BGP in Alaska, KL
* K4M and KB2KWB in Puerto Rico, KP4
* LU3CW/W, LU3EFL/D, LU6DO/D and LU9VRC/V in Argentina, LU
* 4U1XMAS in Austria, OE
* R7BA/1, R900BL, R9XAU/6 and RM4P in European Russia, UA
* RA/IK7YTT, RA4RU/9, RM19NY, RT4C/8, RU19NY, RZ19NY and RZ9O/0 in Asiatic Russia, UA9
* VE2/UT3UA in Canada, VE
* VK2CV/6 in Australia, VK
* DT8A in South Shetland Islands, VP8/h

73 - Jim AD1C

--
Jim Reisert AD1C, <jjreisert at alum.mit.edu>, http://www.ad1c.us

Re: Problem with BARTG TIME2 macro

ve3ki
 

Pay attention to the instructions (click on the Show Setup button to see them).

Putting the {TIME2} macro in the Sent Exchange will produce a bad Cabrillo file.

Change that back to just # (or 001). Create a copy of your default message file, replace {EXCH} with {EXCH} {TIME2} in that copy and save the file under a separate file name like BARTGS.mc. Then under the Associated Files tab in the same window you showed the screen shot of (with the BARTGSRTTY contest selected), name that file as the Digital Function Key Filename. From now on that message file will be used in any BARTGSRTTY contest you enter, but not in any other contests.

73,
Rich VE3KI


On Mon, Mar 18, 2019 at 02:38 PM, InMiami Ale wrote:


This and my configuration, I find it faster without touching the macros. 73

Re: Problem with BARTG TIME2 macro

InMiami Ale
 



This and my configuration, I find it faster without touching the macros. 73

Re: Spectrum Display AFSK & IC-7300 Question

Jeff WB9DAR
 

Hey Walt
I’m glad it all worked out for you. I had the same but opposite issue ( I was transmitting in LSB-D Reverse (USB) and receiving in normal LSB-D). So I could copy them, but they couldn’t copy me. 
See how it can get confusing HI HI. 
Anyway Best 73
Jeff WB9DAR

On Mar 18, 2019, at 12:25 PM, Walter Beaton <wrbeaton@...> wrote:


Hello Jeff,
I was able to make many contacts in the USB-D setting, but I think I had the AFSK-R setting in play which would reverse things. Whatever setting I used it worked! Sometimes even a blind squirrel finds an acorrn! Hi Hi  73, Walt

Re: 60m QSO - DDE output string incorrectly shows 80m

zl3ga
 

Thanks Art but 60m is already included in the program. Dxpeditions and General Logging users make use of it. This appears to be a bug as the frequency is parsed correctly, it's just the <band> field that is incorrect in the DDE packet.
73
Geoff ZL3GA 

Re: Spectrum Display AFSK & IC-7300 Question

Walter Beaton
 


Hello Jeff,
I was able to make many contacts in the USB-D setting, but I think I had the AFSK-R setting in play which would reverse things. Whatever setting I used it worked! Sometimes even a blind squirrel finds an acorrn! Hi Hi  73, Walt

Re: 2tone gone wild

David Jaffe
 

I know I restarted N1MM but that was before I realized that the sluggishness was due to the hundred 2tone processes. After I killed them, I may not have restarted N1MM, before it happened for the second time and I had another 100 of them. But at some point I did restart it so maybe that fixed it. Sorry to be vague...it was a contest and I didn’t have time for systematic debugging

If 2tone never launches background processes, then I agree that it sounds like an N1MM issue.

Btw is there a way to make 2tone allow scrolling back to see an earlier decode? When I try that , it always goes back to the end and it’s hard to see something I missed .

Or maybe have a log file that has all the decodes (will get large but disks are big these days and could leave a tail process running in a shell.

K6DAJ

IC-7700 SETTING FOR CW AND DİGİTAL MOD HOW?

Ozkan Ozal <ta7i@...>
 

i was using icom 756pro and it was working with n1mm cw and digital.
got an icom 7700
I used the same cable connections
 
The frequency control of the radio works well with n1mm
but
cw and digital did not work.
no tx
mixw also works without problems.
Do you have an example file for ic-7700
I did not understand what I did missing
tnx 73,
de ta7i