Date   
Re: Cabrillo for SPDX RTTY

John Bednar
 

I will look at the output file generation but any software that reads the Cabrillo file should parse on white space not exact column character number.

 

John, K3CT

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Dany VE2EBK
Sent: Monday, April 29, 2019 7:48 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] Cabrillo for SPDX RTTY

 

Same log format here for a QSO with SP prov..

I realigned manually. with Notepad.

Dany VE2EBK

Re: FLDIGI with N1MM Rig Control

ve3ki
 

You misinterpreted the phrase "Logger's Window > Digital Interface menu item" . It's not "Logger's Window" > "Digital Interface menu item", it's the Logger's "Window > Digital Interface menu item". In other words, in N1MM+ Logger (as distinct from fldigi), go to the Window menu and select the "Digital Interface" menu item. I'll change that to read "N1MM+ Entry window's Window > Digital Interface menu item".

In previous versions of fldigi, there was an XML-RPC tab, and that is what the instructions refer to. This tab has been removed in the latest release of fldigi. The N1MM+ instructions have not yet caught up, but for version 4.1.02 and newer of fldigi, they should simply indicate that NO method of rig control should be selected in fldigi; the xml-rpc method that was formerly selected with its own tab is now silently activated behind the scenes.

73,
Rich VE3KI


On Mon, Apr 29, 2019 at 02:16 AM, WA7SKG wrote:
I'm trying to set up fldigi with N1MM+ for 7QP this weekend. I'm looking
at the manual for digital set up and have run into several problems.
First is terminology. I wish it would be consistent throughout the
documentation.

"2.2. Fldigi Initial Configuration

After fldigi has been downloaded and installed, open the Configurer and
set up the path to fldigi.exe under the Digital Modes tab. After closing
the Configurer, choose a contest in N1MM Logger that supports digital
modes, select the Logger's Window > Digital Interface menu item, and
then in the Digital Interface window, select the Interface > Fldigi menu
item."

I looked all over trying to figure out which window was the "Logger's
Window". This page was the only one I found with a reference to the
"Logger's Window". I finally figured out everywhere else called it the
"Entry Window". Sorry I'm so stupid it took me nearly an hour to figure
out they were the same thing.

Now that I am looking at the "Logger's [ENTRY] Window", I try to find
the "Digital Interface menu item". Once again, no joy in searching the
documentation. Alas, this page seems to be the ONLY place the term
"Digital Interface menu item" appears. After a lot of by guess/by golly,
I think it means to select a digital band on the "Band Panel", an item
frequently identified elsewhere, but never mentioned in this section.
Now, the Digital Interface Window is open. Per the instruction, I click
on the "Interface > Fldigi" menu item. Nothing happens.

This is not the first time I have launched the DI window, so I go to the
fldigi waterfall-only window and select Configure. Continuing to follow
the instructions, I ignore the Operator section and set up the Audio
Devices. Then I come to a standstill.

"Transceiver control - Select the XML-RPC tab, check the Use XML-RPC
Program box, and click the Initialize button. Do NOT select RigCAT,
Hamlib, or MemMap for rig control; none of those will work with N1MM
Logger+ "

Of course I am running the latest fldigi ver 4.1.02 and guess what?
There is NO XML-RPC tab. With no XML-RPC tab, there is naturally no "Use
XML-RPC Program" box or Initialize button. Is this an N1MM problem or an
fldigi problem?

I'll stumble around with this for a while and try to figure out rig
control. Ideas where to go from here are appreciated.

Michael WA7SKG

Re: Cabrillo for SPDX RTTY

ve3ki
 

Since others have reported success, that suggests something wrong in your setup for the contest. The most likely cause is an incorrect or missing entry in the "Sent Exchange" box in the contest setup dialog (File > Open Log in Database...).

73,
Rich VE3KI


On Sun, Apr 28, 2019 at 06:57 PM, <NS2N_PTA@...> wrote:
attempted to upload log to SP website, but it got rejected for Cabrillo errors. Is there a separate template
for Cabrillo for this contest? I haven't ever had a problem before for any contest, so this is new to me.

NS2N

Mode switches from CW to Phone -- huh ?

CW Morse
 

Occasionally during (CW) contests, I press F4 to send my call and a window pops up saying it can't find a WAV file, as if I'm in phone mode.  The K3S still says CW, and the title bar on the submission window says "7039.49 CW Elecraft K3 VFO A", as expected.  If I enter a call and hit tab, the signal report comes up as 59, not the expected 599. 
Restarting the N1MM+ and/or cycling the K3 power doesn't seem to get things back on track.  But something unknown happens and I'm back in CW mode (until later).
Operator error, no doubt.  What might I be doing wrong?
TIA   Don   K2BIO

Re: Mode switches from CW to Phone -- huh ?

ve3ki
 

This indicates that the program is in SSB logging mode, even though the radio is in CW mode. The quick fix is to type CW into the call sign box and press Enter, or click on one of the Band Panel CW buttons.

The most likely cause is in your Mode Control settings in the Configurer. If the default for "Mode recorded in log" ("Use radio mode") is selected, the program's logging mode should follow the radio, but if one of the other choices is selected, that can override the radio's mode. For example, if "Follow band plan" is selected and the frequency the radio is tuned to happens to be in the part of the bandplan designated for SSB, the program will log contacts in SSB even though the radio is in CW mode.

73,
Rich VE3KI


On Mon, Apr 29, 2019 at 08:33 AM, CW Morse wrote:
Occasionally during (CW) contests, I press F4 to send my call and a window pops up saying it can't find a WAV file, as if I'm in phone mode.  The K3S still says CW, and the title bar on the submission window says "7039.49 CW Elecraft K3 VFO A", as expected.  If I enter a call and hit tab, the signal report comes up as 59, not the expected 599. 
Restarting the N1MM+ and/or cycling the K3 power doesn't seem to get things back on track.  But something unknown happens and I'm back in CW mode (until later).
Operator error, no doubt.  What might I be doing wrong?
TIA   Don   K2BIO

Re: Cabrillo for SPDX RTTY

Phil Cooper
 

Hi all,

I submitted my SPDX Cabrillo file without any issues, using the latest version of N1MM+ under Win7 Pro.

As far as I can see, visually, the file looks fine to me:
QSO: 14081 RY 2019-04-27 1201 GU0SUP 599 0001 S53X 599 001
QSO: 14098 RY 2019-04-27 1209 GU0SUP 599 0002 OG8T 599 012
QSO: 14097 RY 2019-04-27 1210 GU0SUP 599 0003 SN5N 599 LW
QSO: 14097 RY 2019-04-27 1211 GU0SUP 599 0004 SP3A 599 ZY
QSO: 14096 RY 2019-04-27 1213 GU0SUP 599 0005 VE2FK 599 012
QSO: 14095 RY 2019-04-27 1214 GU0SUP 599 0006 RG4A 599 013
QSO: 14092 RY 2019-04-27 1217 GU0SUP 599 0007 RA3NC 599 014
QSO: 14092 RY 2019-04-27 1217 GU0SUP 599 0008 SP9KR 599 CN
QSO: 14088 RY 2019-04-27 1219 GU0SUP 599 0009 SP9KDA 599 OY
QSO: 14088 RY 2019-04-27 1220 GU0SUP 599 0010 S51I 599 008

73 de Phil GU0SUP

-----Original Message-----
From: "John Bednar via Groups.Io" <k3ct=verizon.net@groups.io>
Sent: Monday, 29 April, 2019 12:53
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] Cabrillo for SPDX RTTY

I will look at the output file generation but any software that reads the Cabrillo file should parse on white space not exact column character number.



John, K3CT

Re: Unusual Bug found during FLQP

Gerald Boutin (VE1DT)
 

On Sun, Apr 28, 2019 at 08:30 PM, NW0M wrote:
I encountered a very unusual bug this weekend during FLQP.  It is a quirky error but it does create an incorrect log entry and the condition is repeatable.  The bug logs a Q for the wrong band.  I was using version 7598 but can re-create the bug with 7644.

Here are the steps by an example:
  1. On freq 7041 enter K4OJ and WAG county.  Do not log.
  2. Change rig to freq 14041.  Enter K4OJ and WAG county.  Do not log.
  3. Go back to 7041, K4OJ appears above entry box as it should.  Hit Space Bar to populate K4OJ and WAG.  Do not log.
  4. Go back to 14041.  K4OJ and WAG already display IN the call entry box (which is likely the issue).  Log the call.  Call is logged but for freq 7041.

Like I said it's pretty quirky but it did happen to me today.  When you have peanut station such as mine you do a lot of back-and-forth...  :-)

Maybe it's not worth the trouble to look into but I thought I would report it.

73, Mitch
NWØM

 Mitch,

I can also reproduce it here.

In playing around, I can also reproduce it simply by having spots for the same station and exchange on different bands. Once the exchange info is entered on one band, normally a QSY would give a message that the station wasn't logged and logging the station on another band would work properly. For example, changing the band on the radio does not have the issue.

However, by not changing what is in the Entry window, there are a couple methods of getting to the other band that don't trigger the "QSY" in the software. For example, clicking on the Band select icon in the Entry Window or clicking on the station in the Available window both get you to the station on the other band, but the program isn't catching that the band has changed because the Call / Exchange didn't change.

This problem can happen on any contest where you are chasing a station across bands. I have verified that it exists in CQWW. So, I think it is severe enough to warrant fixing.

--
Gerald, VE1DT

Re: Unusual Bug found during FLQP

Steve London
 

SO1R ? SO2V or SO2R with one VFO or radio on 7041, the other on 14041 ?

73,
Steve, N2IC

On 04/28/2019 05:30 PM, NW0M wrote:
I encountered a very unusual bug this weekend during FLQP.  It is a quirky error but it does create an incorrect log entry and the condition is repeatable.  The bug logs a Q for the wrong band.  I was using version 7598 but can re-create the bug with 7644.
Here are the steps by an example:
1. On freq 7041 enter K4OJ and WAG county.  Do not log.
2. Change rig to freq 14041.  Enter K4OJ and WAG county.  Do not log.
3. Go back to 7041, K4OJ appears above entry box as it should.  Hit Space Bar
to populate K4OJ and WAG.  Do not log.
4. Go back to 14041.  K4OJ and WAG already display IN the call entry box (which
is likely the issue).  Log the call.  Call is logged but for freq 7041.
Like I said it's pretty quirky but it did happen to me today.  When you have peanut station such as mine you do a lot of back-and-forth...  :-)
Maybe it's not worth the trouble to look into but I thought I would report it.
73, Mitch
NWØM

Re: Cabrillo for SPDX RTTY

NS2N_PTA@...
 

SPDX Cabrillo problem SOLVED

 

There was no Cabrillo problem. There was an operator problem. Thanks to SP5ELA for pointing out that I was submitting to the wrong website. Post contest, I pulled up the wrong pdf out of my Documents to check the rules/submission info.  The correct place is

 

https:pkrvg.org/

 

Upload – no problem. My apologies for generating unnecessary traffic.

 

What got me thinking ( always a dangerous path) …. For the very first time ever,  N1MM locked up on me. I went to click on a spot in the bandscope. Have done this often. Then nothing worked ,,, keyboard, mouse … totally frozen. Had to ctrl/alt/delete  my way out. Rebooted and everything went ok after that. Thought perhaps some corrupted files occurred but apparently not.

 

Paul NS2N

 

 

 

 

 

Sent from Mail for Windows 10

 

From: Phil Cooper via Groups.Io
Sent: Monday, April 29, 2019 9:29 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] Cabrillo for SPDX RTTY

 

Hi all, 

I submitted my SPDX Cabrillo file without any issues, using the latest version of N1MM+ under Win7 Pro.

As far as I can see, visually, the file looks fine to me:
QSO: 14081 RY 2019-04-27 1201 GU0SUP        599 0001   S53X          599  001    
QSO: 14098 RY 2019-04-27 1209 GU0SUP        599 0002   OG8T          599  012    
QSO: 14097 RY 2019-04-27 1210 GU0SUP        599 0003   SN5N          599    LW   
QSO: 14097 RY 2019-04-27 1211 GU0SUP        599 0004   SP3A          599    ZY   
QSO: 14096 RY 2019-04-27 1213 GU0SUP        599 0005   VE2FK         599  012    
QSO: 14095 RY 2019-04-27 1214 GU0SUP        599 0006   RG4A          599  013    
QSO: 14092 RY 2019-04-27 1217 GU0SUP        599 0007   RA3NC         599  014    
QSO: 14092 RY 2019-04-27 1217 GU0SUP        599 0008   SP9KR         599    CN   
QSO: 14088 RY 2019-04-27 1219 GU0SUP        599 0009   SP9KDA        599    OY   
QSO: 14088 RY 2019-04-27 1220 GU0SUP        599 0010   S51I          599  008

73 de Phil GU0SUP   

-----Original Message-----
From: "John Bednar via Groups.Io" <k3ct@...>
Sent: Monday, 29 April, 2019 12:53
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] Cabrillo for SPDX RTTY

I will look at the output file generation but any software that reads the Cabrillo file should parse on white space not exact column character number.

 

John, K3CT




 

Re: Unusual Bug found during FLQP

VE9AA - Mike
 

Hi Guys,

I didn't notice that, but I did note some stations never showed in the bandmaps as greyed/dupes ( as having been worked before.)
It caught me a few times and I had to apologize, after I called them.

IE: I recall W4B in particular always showed in my bandmap as blue.  However when I entered his callsign into the entry box and hit space, it turned grey
and showed as being a dupe. If I always followed that, I was good.  But if I called a stn w/o hitting spacebar, sometimes I got caught out by seeing it was a dupe.

This happened with a few stations, but W4B was the one I took notice of.

I did not (and never) log stations as "K4OJ/PIN" or "K4KG/MAO"....In every contest always always use just the base call. Not call/county.
The exception is if KU8E/4 is sending the /4 I do log that.

So, to clarify, I am not referring to if K4OJ/PIN was showing as workable(or not) in the bandmap.(but if I  had worked him there before....that's on me)

I wish I had made notes, but as this was only a part time, casual operation , I did not, as I was out of the shack more than in, this w/e

Thanks

Re: Unusual Bug found during FLQP

VE9AA - Mike
 

p.s.-  I was SO2R,primarily 20/40, but some 15m listening, so not sure if that ever played into the scenario or not.

Re: Mode switches from CW to Phone -- huh ?

CW Morse
 

TNX Rich.  Forgot about being able to type mode into Call Box.  Also changed Config choice.  That should do it !

More oddities in FLQP.

Tim Shoppa
 

I'm not sure anything has ever been easy or automatic in a contest with frequent rovers and with spotters using every possible suffix under the sun when spotting rovers. So I was especially careful to listen with my ears and "correct" the call in the bandmap to be the base call without any - stroke-county ornamentation.

But something very odd that occurred frequently to me this past weekend:

1: Find a blue spot on the bandmap. This spot is just the plain call without "/PIN", or "/MAO", or any unnecessary suffix.
2: Click on it, see the call history and the prefill for his previous county, hit space, callsign in entry box turns grey, take a listen, he's still in the same county. So verified by ear, and verified by log inspection, not a new Q, nor a new county.

now the above 2 steps are not all that unusual. Below, is where it gets unusual:

3: Dial away from the frequency, or click on a different spot. Now the call on the bandmap turns Red as if he's a new mult. His call is in bold because I typed him in (not a telnet cluster spot.
4: Click on the red spot and check the prefill. He's a dupe. Same call, same county. Hit space callsign in entry box turns grey.

Also, several rovers sitting on a border, I was able to succesfully type in the exchange using a slash between the two counties, and see it logged as two Q's. But other times (even though I typed in the counties correctly) it didn't log both counties. The first got logged but an obscure error box popped up (sorry, didn't take a screenshot) and the second one wasn't logged.

Tim N3QE

Re: Unusual Bug found during FLQP

Mitch NW0M
 

Steve, I was SO1R.

73, Mitch

Bug in N1MM Logger Plus for Florida QSO Party Expedition Class

Jeff Clarke
 

I noticed when I submitted my FQP log the first time that it listed all my contacts in the Cabrillo file as being from HOL. That's because I had HOL in the Sent Exchange field on the screen that first comes up when you open a log. Usually you can just change that each time you change a county by typing in {ROVERQTH} in the call sign field of the logging window. I changed the exchange to {ROVERQTH} and created another Cabrillo and it just put {ROVERQTH} in the sent field of the Cabrillo file.

The work around seems to be to change your category from Expedition to Rover and put {ROVERQTH} in the Sent Exchange field and then create the Cabrillo file. You then need to open the .log file and change the category from Rover to Expedition.

Jeff KU8E

Re: Unusual Bug found during FLQP

Jeff Clarke
 

A weird intermittent problem I noticed was I would type in a frequency to QSY to another band and it didn't change the frequency in the log but would change the frequency on the radio. I would then restart N1MM Logger Plus and it would change it. I'm using version 1.0.7664.0. Radio is a Kenwood TS590SG.

Maybe it's nothing but RF getting into the computer since my antenna was only about 5 feet way from me.

Jeff KU8E

Re: More oddities in FLQP.

Jeff Clarke
 

Tim,

I did my first two counties from the SAN/OKA county line. If you're a rover you can type in {COUNTYLINE} in the logging window and type in the counties separated by commas.You then put in the {COUNTYLINE} macro in place of the {ROVERQTH} one in the CW memory. (F2 key)  It's a very nice feature because it logs two QSO's for you. One from each county.

Jeff

Re: FLDIGI with N1MM Rig Control

WA7SKG <wa7skg@...>
 

Rich, you are once again my hero. This is what I get trying to work on things very late after a long stressful day. Now it is very clear to me, bringing up the DI Window.

Rig control functions seem to be working as needed. I was wondering about that, since the XML-RPC thing didn't show up. Now I see it is backgrounded so everything works.

My concern right now, then, is power control, AFC, and squelch. When I run fldigi by itself, I get controls at the bottom of the screen that have a power control under the LK button and next to the AFC and SQL buttons. This control allows me to vary the audio drive adjusting the power out. Selecting the digital mode in N1MM+ brings up the fldigi waterfall window and the DI window, but none of these controls seem to be available. I imagine these should be available someplace, I just can't seem to find them.

Michael WA7SKG



ve3ki wrote on 4/29/19 5:17 AM:

You misinterpreted the phrase "Logger's Window > Digital Interface menu item" . It's not "Logger's Window" > "Digital Interface menu item", it's the Logger's "Window > Digital Interface menu item". In other words, in N1MM+ Logger (as distinct from fldigi), go to the Window menu and select the "Digital Interface" menu item. I'll change that to read "N1MM+ Entry window's Window > Digital Interface menu item".
In previous versions of fldigi, there was an XML-RPC tab, and that is what the instructions refer to. This tab has been removed in the latest release of fldigi. The N1MM+ instructions have not yet caught up, but for version 4.1.02 and newer of fldigi, they should simply indicate that NO method of rig control should be selected in fldigi; the xml-rpc method that was formerly selected with its own tab is now silently activated behind the scenes.
73,
Rich VE3KI
On Mon, Apr 29, 2019 at 02:16 AM, WA7SKG wrote:
I'm trying to set up fldigi with N1MM+ for 7QP this weekend. I'm
looking
at the manual for digital set up and have run into several problems.
First is terminology. I wish it would be consistent throughout the
documentation.
"2.2. Fldigi Initial Configuration
After fldigi has been downloaded and installed, open the Configurer and
set up the path to fldigi.exe under the Digital Modes tab. After
closing
the Configurer, choose a contest in N1MM Logger that supports digital
modes, select the Logger's Window > Digital Interface menu item, and
then in the Digital Interface window, select the Interface > Fldigi
menu
item."
I looked all over trying to figure out which window was the "Logger's
Window". This page was the only one I found with a reference to the
"Logger's Window". I finally figured out everywhere else called it the
"Entry Window". Sorry I'm so stupid it took me nearly an hour to figure
out they were the same thing.
Now that I am looking at the "Logger's [ENTRY] Window", I try to find
the "Digital Interface menu item". Once again, no joy in searching the
documentation. Alas, this page seems to be the ONLY place the term
"Digital Interface menu item" appears. After a lot of by guess/by
golly,
I think it means to select a digital band on the "Band Panel", an item
frequently identified elsewhere, but never mentioned in this section.
Now, the Digital Interface Window is open. Per the instruction, I click
on the "Interface > Fldigi" menu item. Nothing happens.
This is not the first time I have launched the DI window, so I go to
the
fldigi waterfall-only window and select Configure. Continuing to follow
the instructions, I ignore the Operator section and set up the Audio
Devices. Then I come to a standstill.
"Transceiver control - Select the XML-RPC tab, check the Use XML-RPC
Program box, and click the Initialize button. Do NOT select RigCAT,
Hamlib, or MemMap for rig control; none of those will work with N1MM
Logger+ "
Of course I am running the latest fldigi ver 4.1.02 and guess what?
There is NO XML-RPC tab. With no XML-RPC tab, there is naturally no
"Use
XML-RPC Program" box or Initialize button. Is this an N1MM problem
or an
fldigi problem?
I'll stumble around with this for a while and try to figure out rig
control. Ideas where to go from here are appreciated.
Michael WA7SKG

IC706MKIIG setup

Doug, K1RDD
 

We're pulling out an IC706MKIIG to use as an auxiliary station. It will be for phone and CW only, no other digital modes. Do I need anything other than a USB to CI-V port cable?
_/--_
Doug

Re: Field Day Class missing from N1MM+ log

Ken Norris
 


OK, If I enter the Call, Class, and Section into the N1MM+ Entry Window, the logger is populated correctly.





But if I manually log it from WSJT-x, It does not populate the Class in the Exch column. 







I have not tried logging from an actual contact yet. 
May have to set up another club member to make a Field Day test contact. 
Let me know if you need additional information.

Ken Norris, KK9N