Date   
Re: SORRY OFF TOPIC: need SWL software for contest

Giuseppe Giunta
 

wow! Les,

this is exactly what an SWL needs! Thanks again ...

I did some QSO tests for the next SSB WPX later this month; I created the Cabrillo and I hope everything is fine for sending the log via the CQWW WPX web page; I have a question: I created the Adif file to import the QSOs on Logger32, but by performing the import, only the main callsign field is populated, not the corresponding one (second callsign heard); opening the Adif I see that the second callsign is put in the <SECTION: x> field; how can I make Logger32 read this field correctly and import the other callsign?

Grazie, Giù

Il 23/03/2020 17:26, Giuseppe Giunta ha scritto:

Grazie Les, I Will take a look.
Giù, IT9VDQ

Il lun 23 mar 2020, 17:22 Les Elliott via Groups.Io <g4ogb=tiscali.co.uk@groups.io> ha scritto:
Take a look at
written by NA3M, it may suffice your needs.
Les, G4OGB
 
Sent: Monday, March 23, 2020 12:40 PM
Subject: [N1MM+] SORRY OFF TOPIC: need SWL software for contest
 

sorry for the off topic! :-)

Good morning everyone,

I'm looking for a software to manage contests as SWL, and able to generate the cabrillo and adif files, to send them to the committee via web page and to import them into the general log; In the Russian DX I used SP7DQR's  DQR_Log, but I can't upload it to their web page, always getting a "fatal error"; waiting for the WPX, what do you recommend me to use? Any idea?

Grazie mille de Giù -  IT9-60339

(op: IT9VDQ one of IB9T crew)

Re: Using GRITTY as a Second Decoder Causes N1MM to Terminate after a few Hours

B. Smith
 

There is a pretty good chance that there is a problem with GRITTY, although it may be how GRITTY interacts when running it along with MMTTY. I experienced sudden vanishing N1MM a few times in past RTTY contests but never reported it. In those contests, MMTTY was my main decoder, as I remember it. This past weekend, I wasn't running GRITTY for most of the contest and never had a vanishing N1MM problem. Also this past weekend I was using FLDGI as my main decoder. I'm not sure if vanishing N1MM is caused by GRITTY or the interaction of various decoding programs. I can say for sure that it isn't related to sending, as I am sure it happens when just receiving. I use Win 10 - 64bit and giving this some thought, I would suspect an issue like an overflow in receive memory buffers. Personally, I don't understand how these sorts of things work nowadays, but this would be a suspect based on the passive nature of the issue, i.e. it can occur when in receive only operations.

Morserunner

Joe WB9SBD
 

I just tried the new morserunner and it's awesome except for one thing.
it has the checkbox to mute my sidetone.

But the program behaves like full breakin. I hear the stations while I'm transmitting

I would like it to be semi breakin, can this be done? In otherwords while I am transmitting is do NOT hear the band

Joe WB9SBD

Re: General (net) logging

denf.acm
 

Thanks guys.

I wasn't really looking for a full general logger (I have DXLab) but just a quickie checklist for local 'keep in touch' nets.

However many thanks to all responders for their thoughts and advice.

73

Den M0ACM  

============================
stay safe;  stay well;  stay busy !

Re: SORRY OFF TOPIC: need SWL software for contest

Giuseppe Giunta
 

Grazie Les, I Will take a look.
Giù, IT9VDQ

Il lun 23 mar 2020, 17:22 Les Elliott via Groups.Io <g4ogb=tiscali.co.uk@groups.io> ha scritto:
Take a look at
written by NA3M, it may suffice your needs.
Les, G4OGB
 
Sent: Monday, March 23, 2020 12:40 PM
Subject: [N1MM+] SORRY OFF TOPIC: need SWL software for contest
 

sorry for the off topic! :-)

Good morning everyone,

I'm looking for a software to manage contests as SWL, and able to generate the cabrillo and adif files, to send them to the committee via web page and to import them into the general log; In the Russian DX I used SP7DQR's  DQR_Log, but I can't upload it to their web page, always getting a "fatal error"; waiting for the WPX, what do you recommend me to use? Any idea?

Grazie mille de Giù -  IT9-60339

(op: IT9VDQ one of IB9T crew)

Re: Pg Up/Pg Down keys intermittently not working?

Bob Evans
 

Perfect answer Rich!  You’re on top of it and I might see a fix in the future but I realize two keyboard stuff is WAY down the list of things to do.

 

Stay healthy and thanks for the reply.

 

Bob K5WA

Re: General (net) logging

Anthony Luscre
 

There are a number of free general logging programs that may serve you better.

On Mon, Mar 23, 2020 at 4:41 AM denf.acm <denf.acm@...> wrote:
I have seen youtubes of N1MM+ being used for general net logging purposes.

Searches suggest that a 'DX' udc will provide this function.

I thought I had found one but it doesn't provide the fields I had seen: Call, report in, report out, name, notes....

What am I missing / failing to do ?

Thanks guys.

Den M0ACM



--
Anthony Luscre

K8ZT
Ohio Section Section Youth Coordinator & Education Outreach
ARRL - The National Association For Amateur Radio™
 
k8zt@... (best for Amateur Radio)

The Web Resource Hoarder- www.ZTLearn.com

K8ZT Radio Website- www.k8zt.com

Amateur Radio Resources for Students/Youth - www.k8zt.com/hry

Re: SORRY OFF TOPIC: need SWL software for contest

Les Elliott
 

Take a look at
written by NA3M, it may suffice your needs.
Les, G4OGB
 

Sent: Monday, March 23, 2020 12:40 PM
Subject: [N1MM+] SORRY OFF TOPIC: need SWL software for contest
 

sorry for the off topic! :-)

Good morning everyone,

I'm looking for a software to manage contests as SWL, and able to generate the cabrillo and adif files, to send them to the committee via web page and to import them into the general log; In the Russian DX I used SP7DQR's  DQR_Log, but I can't upload it to their web page, always getting a "fatal error"; waiting for the WPX, what do you recommend me to use? Any idea?

Grazie mille de Giù -  IT9-60339

(op: IT9VDQ one of IB9T crew)

Re: Carl down arrow changes filter setting on 7610

John MM0JOM
 

There are three filter settings on the 7610
Fil 1  currently set to 1.2k
Fil 2 set to 500
Fil 3 set to 150.
For cw I like 150
At the top of the band map if I set the filter to wide it changes the radio to fil 1 - 1.2k
If i then click on a spot it changes the filter setting to nar and the radio changes to Fil 2 - 500.
At the top of the bandmap if I set the filter to Nar it set the radio to Fil 2 - 500
If I subsequently cclick on a spot the radio stays on Fil 2 - 500.
How can I get it to go to and to stay on Fil 3 - 150
John
MM0JOM

On Sun, Mar 22, 2020 at 01:57 PM, John Bednar wrote:
John,
I expect that you have our software set to use the filter selection that is being set. It is set at the top of the Bandmap.
 
John, K3CT 
 
 
 
-------- Original message --------
From: John MM0JOM <j@...>
Date: 3/22/20 9:24 AM (GMT-05:00)
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] Carl down arrow changes filter setting on 7610
 
I am using N1MM with an Icom 7610. Everything works perfectly except when using ctrl down arrow to work down the band map it changes the filter setting. I have it set up as SO2V and run on vfoA and s&p on VFO B. If I set filter on VFO B to filter 1 when I next use ctrl down arrow move to the next call sign on the band map it changes the filter to filter 2.
John
MM0JOM

Re: N1MM Serial Numbering

David G3YYD
 

Tim

 

Yes I was working between 2 bands 20 and 40m so it could well be linked to something I did on EW2. The 3rd QSO with the sent SN3 and logged as 2 was EW1

 

73 David

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Tim Shoppa
Sent: 23 March 2020 13:49
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] N1MM Serial Numbering

 

David and Dave,

 

I had this mismatch between number on screen/number logged/number sent consistently happen to me for the Thursday night NS Sprints (both RTTY and CW). It only happened on the first few Q's then somehow straighted itself out.

 

I was SO1R, but it seemed to particularly happen when I was hopping between bands (which is what a SO2R guy would want to do). In particular David your pattern where QSO #3 was the one that first showed the goof-up, is what sticks in my head.

 

I even submitted a bug ticket with a link, to a video of it happening.

 

But I haven't observed it in several months now so it's possible it's been fixed but I don't know how to find my bug ticket number or trace its resolution.

 

Is it possible you guys are running a version from several months ago?

 

Tim N3QE

 

On Mon, Mar 23, 2020 at 9:34 AM Dave Sumner <sumner@...> wrote:

The same thing happened to me in the Russian DX Contest (CW).

 

I corrected it via paddle with my 3rd QSO partner and edited the QSO in the log before going on to QSO number 4. After that everything was fine.

 

But I just tested for CQWPX SSB next weekend and it seems to be OK.

 

Dave K1ZZ

 

On Monday, March 23, 2020, 05:43:51 AM EDT, David G3YYD via Groups.Io <g3yyd2=btinternet.com@groups.io> wrote:

 

 

During the BARTG RTTY contest, I had a strange event that I have never seen before.

 

My first QSO I sent SN 1 and logged SN 1.

 

My second QSO sent SN 2 and logged SN 2

 

My Third QSO sent SN 3 and Logged SN 2

 

My fourth QSO sent SN 3 and Logged SN 3

 

All following QSOs were correct.

 

I was working SO2R. I will email the adjudicator so the guy I worked does not have a QSO with busted SN.

 

73 David G3YYD

Re: N1MM Serial Numbering

David G3YYD
 

I am up to date too. 73 David G3YYD

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Dave Sumner
Sent: 23 March 2020 14:22
To: n1mmloggerplus@groups.io; N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] N1MM Serial Numbering

 

Hi Tim,

 

No, I am up to date.

 

Dave K1ZZ

 

 

On Monday, March 23, 2020, 09:48:54 AM EDT, Tim Shoppa <tshoppa@...> wrote:

 

 

David and Dave,

 

I had this mismatch between number on screen/number logged/number sent consistently happen to me for the Thursday night NS Sprints (both RTTY and CW). It only happened on the first few Q's then somehow straighted itself out.

 

I was SO1R, but it seemed to particularly happen when I was hopping between bands (which is what a SO2R guy would want to do). In particular David your pattern where QSO #3 was the one that first showed the goof-up, is what sticks in my head.

 

I even submitted a bug ticket with a link, to a video of it happening.

 

But I haven't observed it in several months now so it's possible it's been fixed but I don't know how to find my bug ticket number or trace its resolution.

 

Is it possible you guys are running a version from several months ago?

 

Tim N3QE

 

On Mon, Mar 23, 2020 at 9:34 AM Dave Sumner <sumner@...> wrote:

The same thing happened to me in the Russian DX Contest (CW).

 

I corrected it via paddle with my 3rd QSO partner and edited the QSO in the log before going on to QSO number 4. After that everything was fine.

 

But I just tested for CQWPX SSB next weekend and it seems to be OK.

 

Dave K1ZZ

 

On Monday, March 23, 2020, 05:43:51 AM EDT, David G3YYD via Groups.Io <g3yyd2=btinternet.com@groups.io> wrote:

 

 

During the BARTG RTTY contest, I had a strange event that I have never seen before.

 

My first QSO I sent SN 1 and logged SN 1.

 

My second QSO sent SN 2 and logged SN 2

 

My Third QSO sent SN 3 and Logged SN 2

 

My fourth QSO sent SN 3 and Logged SN 3

 

All following QSOs were correct

 

I was working SO2R. I will email the adjudicator so the guy I worked does not have a QSO with busted SN.

 

73 David G3YYD

Re: N1MM Serial Numbering

Dave Sumner
 

Hi Tim,

No, I am up to date.

Dave K1ZZ


On Monday, March 23, 2020, 09:48:54 AM EDT, Tim Shoppa <tshoppa@...> wrote:


David and Dave,

I had this mismatch between number on screen/number logged/number sent consistently happen to me for the Thursday night NS Sprints (both RTTY and CW). It only happened on the first few Q's then somehow straighted itself out.

I was SO1R, but it seemed to particularly happen when I was hopping between bands (which is what a SO2R guy would want to do). In particular David your pattern where QSO #3 was the one that first showed the goof-up, is what sticks in my head.

I even submitted a bug ticket with a link, to a video of it happening.

But I haven't observed it in several months now so it's possible it's been fixed but I don't know how to find my bug ticket number or trace its resolution.

Is it possible you guys are running a version from several months ago?

Tim N3QE

On Mon, Mar 23, 2020 at 9:34 AM Dave Sumner <sumner@...> wrote:
The same thing happened to me in the Russian DX Contest (CW).

I corrected it via paddle with my 3rd QSO partner and edited the QSO in the log before going on to QSO number 4. After that everything was fine.

But I just tested for CQWPX SSB next weekend and it seems to be OK.

Dave K1ZZ

On Monday, March 23, 2020, 05:43:51 AM EDT, David G3YYD via Groups.Io <g3yyd2=btinternet.com@groups.io> wrote:


During the BARTG RTTY contest, I had a strange event that I have never seen before.

 

My first QSO I sent SN 1 and logged SN 1.

 

My second QSO sent SN 2 and logged SN 2

 

My Third QSO sent SN 3 and Logged SN 2

 

My fourth QSO sent SN 3 and Logged SN 3

 

All following QSOs were correct.

 

I was working SO2R. I will email the adjudicator so the guy I worked does not have a QSO with busted SN.

 

73 David G3YYD

Re: Unable to reconfigure radio nr.2 as radio nr.1

Ira Lipton
 

Thanks for the suggestion Les. I resolved the problem by switching the PTT and key cables at the Winkey box.
 
73,
 
Ira  WA2OAX
 
 
 


From: "Les Elliott via Groups.Io" <g4ogb@...>
Sent: Monday, March 23, 2020 5:40 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] Unable to reconfigure radio nr.2 as radio nr.1
 
Unless someone has a better suggestion....
 
Close Logger.
Browse to your User area Documents\N1MM Logger+
find the third oldest n1mm logger.ini.day.bak
look at the date it was created to ensure it was made
while your ft9k was OK, and rename it by removing
the day.  You now have a good backup ini file for when
the ft9k is returned to working condition.
 
Rename n1mm logger.ini to n1mm loggerOLD.ini
Start logger and re-configure.
Les, G4OGB
 
Sent: Sunday, March 22, 2020 9:22 PM
Subject: [N1MM+] Unable to reconfigure radio nr.2 as radio nr.1
 
My primary radio-an FT9000D-failed just in time for a self imposed isolation for Covid19. I have a second radio (an FT1000D) which is set as radio nr2. The 1000 is controlled via a Microham USB ll. I am attempting to reset the FT1000 as radio nr 1 (and delete the FT9000 until I can have it repaired). Even though I'm using the same configuration parameters, I am unable to have the FT1000 keyed by Winkey unless I revert to having it set as radio nr2 in SO2R. I would greatly appreciate any suggestions.

73,

Ira  WA2OAX

Re: Unable to reconfigure radio nr.2 as radio nr.1

Ira Lipton
 

Many thanks John. Problem solved by switching the PTT and key cables at the Winkey box.
 
73,
 
Ira   WA2OAX
 
 
 


From: "John Bednar via Groups.Io" <k3ct@...>
Sent: Monday, March 23, 2020 6:35 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] Unable to reconfigure radio nr.2 as radio nr.1
 

Ira,

 

The baud rate window for each radio contains a radio Nr box. Make sure you have those set correctly.

If your WinKey has a Radio1 and Radio2 CW cables, make sure that the correct cable is plugged into radio 1.

 

John, K3CT

 

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Ira Lipton
Sent: Sunday, March 22, 2020 5:22 PM
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] Unable to reconfigure radio nr.2 as radio nr.1

 

My primary radio-an FT9000D-failed just in time for a self imposed isolation for Covid19. I have a second radio (an FT1000D) which is set as radio nr2 The 1000 is controlled via a Microham USB ll. I am attempting to reset the FT1000 as radio nr 1 (and delete the FT9000 until I can have it repaired) Even though I'm using the same configuration parameters, I am unable to have the FT1000 keyed by Winkey unless I revert to having it set as radio nr2 in SO2R. I would greatly appreciate any suggestions.

73,

Ira  WA2OAX

 

Re: N1MM Serial Numbering

Tim Shoppa
 

David and Dave,

I had this mismatch between number on screen/number logged/number sent consistently happen to me for the Thursday night NS Sprints (both RTTY and CW). It only happened on the first few Q's then somehow straighted itself out.

I was SO1R, but it seemed to particularly happen when I was hopping between bands (which is what a SO2R guy would want to do). In particular David your pattern where QSO #3 was the one that first showed the goof-up, is what sticks in my head.

I even submitted a bug ticket with a link, to a video of it happening.

But I haven't observed it in several months now so it's possible it's been fixed but I don't know how to find my bug ticket number or trace its resolution.

Is it possible you guys are running a version from several months ago?

Tim N3QE


On Mon, Mar 23, 2020 at 9:34 AM Dave Sumner <sumner@...> wrote:
The same thing happened to me in the Russian DX Contest (CW).

I corrected it via paddle with my 3rd QSO partner and edited the QSO in the log before going on to QSO number 4. After that everything was fine.

But I just tested for CQWPX SSB next weekend and it seems to be OK.

Dave K1ZZ

On Monday, March 23, 2020, 05:43:51 AM EDT, David G3YYD via Groups.Io <g3yyd2=btinternet.com@groups.io> wrote:


During the BARTG RTTY contest, I had a strange event that I have never seen before.

 

My first QSO I sent SN 1 and logged SN 1.

 

My second QSO sent SN 2 and logged SN 2

 

My Third QSO sent SN 3 and Logged SN 2

 

My fourth QSO sent SN 3 and Logged SN 3

 

All following QSOs were correct.

 

I was working SO2R. I will email the adjudicator so the guy I worked does not have a QSO with busted SN.

 

73 David G3YYD

Re: N1MM Serial Numbering

Dave Sumner
 

The same thing happened to me in the Russian DX Contest (CW).

I corrected it via paddle with my 3rd QSO partner and edited the QSO in the log before going on to QSO number 4. After that everything was fine.

But I just tested for CQWPX SSB next weekend and it seems to be OK.

Dave K1ZZ

On Monday, March 23, 2020, 05:43:51 AM EDT, David G3YYD via Groups.Io <g3yyd2@...> wrote:


During the BARTG RTTY contest, I had a strange event that I have never seen before.

 

My first QSO I sent SN 1 and logged SN 1.

 

My second QSO sent SN 2 and logged SN 2

 

My Third QSO sent SN 3 and Logged SN 2

 

My fourth QSO sent SN 3 and Logged SN 3

 

All following QSOs were correct.

 

I was working SO2R. I will email the adjudicator so the guy I worked does not have a QSO with busted SN.

 

73 David G3YYD

SORRY OFF TOPIC: need SWL software for contest

Giuseppe Giunta
 

sorry for the off topic! :-)

Good morning everyone,

I'm looking for a software to manage contests as SWL, and able to generate the cabrillo and adif files, to send them to the committee via web page and to import them into the general log; In the Russian DX I used SP7DQR's  DQR_Log, but I can't upload it to their web page, always getting a "fatal error"; waiting for the WPX, what do you recommend me to use? Any idea?

Grazie mille de Giù -  IT9-60339

(op: IT9VDQ one of IB9T crew)

Re: New user with two keyboards (changed title)

ve3ki
 

On Mon, Mar 23, 2020 at 07:09 AM, KOSTAS STAMATIS wrote:

I tried to use 2 computers in SO2V with a ft1000 field. As I am new in n1mm, I don't know if this is an operator error but I was expected if I type anything in keyboard 1,it will be written in 1st entry window and if I type in 2nd keyboard it will be written in 2nd entry window. Instead of this I was needed to hit \ to change entry windows. Is anything in setup I need to change or to change the way it works? It is more normal it works as my description.

This post has nothing to do with the original discussion thread. Please create a new topic instead of taking over an existing topic.

"I tired to use 2 computers in SO2V..."   -  this is not possible. SO2V means one radio with dual receivers, and only one computer can connect to a single radio. Perhaps this was a typing mistake, and what you really meant was "I tried to use 2 computers in SO2R...", or perhaps you meant "I tried to use 2 keyboards in SO2V...".

If you are really talking about two-computer SO2R, each computer would be connected to its own radio, N1MM+ in each computer would be in SO1V mode and have only one Entry window, and the rest of the networked computer setup would be similar to a Multi-Single operation. This is described in the manual at <https://n1mmwp.hamdocs.com/manual-operating/single-operator-contesting/#two-computer-so2r>.

Assuming instead that you really meant single-computer two-keyboard operation in SO2V, it has been a long time since I tried this (and I do not even remember for sure whether two keyboards work in SO2V), but I believe that in order to use two keyboards, you need to select the "Config > SO2R > Two Keyboards" menu item in the main (VFO A or Radio 1) Entry window. You may then need to shut down the N1MM+ program and restart it. The first keyboard you type in after restarting the program will be used for the VFO A/Radio 1 Entry window, and the second keyboard will be used for the VFO B/Radio 2 Entry window. See <https://n1mmwp.hamdocs.com/manual-windows/entry-window/#config-menu-selections> and scroll down to the description of the "Two Keyboards" menu item.

73,
Rich VE3KI

Re: Pg Up/Pg Down keys intermittently not working?

ve3ki
 

One potential contributor to this is the following: In existing versions of the program, the PgUp/PgDn keys always affect only the radio with TX focus, regardless of which Entry window has keyboard focus (or, at least with the current version, regardless of which keyboard is used). The same is true of the mouse-clickable buttons for changing CW speed - regardless of which Entry window you use, with the current program they affect only the radio with TX focus.

This is not what users would expect for the mouse or when using two keyboards, and may be part (or perhaps even all) of the explanation for what you observed. That is, when you thought you were changing the speed of the radio with keyboard focus, it was actually the speed of the other radio that was being changed. That might go unnoticed if it happened when the TX radio was not actually transmitting.

Note that I am not saying that this is how the program ought to behave or how it will behave in the future - just that this is how it behaves now and in the past, and perhaps this is the explanation for some of the observed problems.

73,
Rich VE3KI


On Sun, Mar 22, 2020 at 06:17 PM, Bob Evans wrote:
In the Russian DX contest this weekend, I saw something I've never seen before.  I had downloaded the latest version prior to the contest and have not tried a previous version to see if the behavior goes back to normal...this is a "just askin'" question to see if anybody else saw it since I use Pg Up/Dwn a lot. 

The keyboard Page Up/Page Down keys didn't adjust the CW speed about half the time.  I could use my mouse and adjust speed with the screen carrots (or whatever they are called) but the keyboard buttons wouldn't work intermittently.  Sometimes they worked perfectly.  I am using two keyboard (very badly) which might be part of the problem.  I had not noticed this in previous contests.  One factor may be that I was mixed mode so one keyboard might be SSB and the other was CW?

No biggie, just curious. 

73,
Bob K5WA 

Re: General (net) logging

ve3ki
 

Adding to what Larry said:

N1MM+ is designed to be a contest logger. It has many features that are useful only in the contest logging context. Conversely, features are not included that might be useful for other purposes but that might interfere with or affect performance in contest logging. Some other related uses are directly supported, such as use by DXpeditions (*not* by DX chasers - many of the features DX chasers want and need are missing by design, because they would slow down contesting performance). Another related use is for familiarization outside of contests, which is what the DX log type was designed for (it was not designed for use as a general-purpose logger).

When a new log database is created, the first log created in that database is a DX log. There is nothing to stop users from creating multiple DX logs within the same database, but the only way to tell them apart is to use the "Start Date" field. The default DX log starts out with a start date & time of 0000Z on January 1, 1900. If you create additional DX logs, you should edit this field (by selecting the contest and mouse-clicking in the start date field to open an edit window where you can change the date and/or time). If you do not do this, you will not be able to tell which DX log is which. There is no field where you can name DX logs to tell them apart, other than by using start dates, perhaps as an arbitrary designation.

Instead of creating multiple DX logs in a single database file, you might find it easier to create multiple database files, using descriptive file names. Each database file would contain its own separate DX log, along with any other contest logs you created in that database,

The DX log type has fields for sent and received signal reports, for a name, and for comments. Unlike most other exchange fields in N1MM+ (including the Name field in the DX log), the Comment field in the DX log can contain spaces. If you type a space anywhere in the Comment field, the space bar's normal function as a smart Tab key will be temporarily unavailable, and you will have to use the Tab key to move the keyboard insertion point (cursor) out of the Comment field into another field.

73,
Rich VE3KI



On Mon, Mar 23, 2020 at 04:54 AM, Larry K8UT wrote:
Den,
 
1. Don't believe everything that you see on the Internet ;-)
 
2. The "DX" contest that hams are using for general purpose logging is not a UDC, it's a standard contest.
 
3. Despite DX's popularity as a general purpose logging app, we still recommend using a real GP logger that does stuff like: real-time QRZ, ClubLog and LoTW interfacing, awards tracking (DXCC, IOTA, WAZ), QSL management...
 
-larry (K8UT)
 
------ Original Message ------
From: "denf.acm" <denf.acm@...>
Sent: 2020-03-23 04:40:47
Subject: [N1MM+] General (net) logging
 
I have seen youtubes of N1MM+ being used for general net logging purposes.

Searches suggest that a 'DX' udc will provide this function.

I thought I had found one but it doesn't provide the fields I had seen: Call, report in, report out, name, notes....

What am I missing / failing to do ?

Thanks guys.

Den M0ACM