Date   

Re: ROUNDUP WITH WSJT FT8 AND FLDIGI RTTY

Rick Ellison
 

Select Digital..

73 Rick N2AMG

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Murf via Groups.Io
Sent: Thursday, January 2, 2020 3:18 AM
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] ROUNDUP WITH WSJT FT8 AND FLDIGI RTTY

 

in Roundup.. do you choose RTTY or  Digital   for the mode in N1mm.  Planning on running ft8 and rtty.
tnx
Murf
n7uvh


Re: Mode SetUp for ARRL RTTY

Rick Ellison
 

Just use Digital . This will get the correct modes in the log..

 

73 Rick N2AMG

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Bill - AK6A
Sent: Thursday, January 2, 2020 1:35 PM
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] Mode SetUp for ARRL RTTY

 

When setting up the new log Mode for the upcoming ARRL RTTY contest N1MM only gives me the option of either RTTY -OR- Digital, not both. Do I just select RTTY and do a mode switch during the contest? I have the ability to do multimodes for other modes like CW and SSB but I don't see an option for RTTY -AND- Digital. Am I missing something?

Thanks!

Bill - AK6A


Re: Mode SetUp for ARRL RTTY

Les Elliott
 

Is RTTY, DIGITAL??
 
Les, G4OGB
 

Sent: Thursday, January 02, 2020 6:35 PM
Subject: [N1MM+] Mode SetUp for ARRL RTTY
 
When setting up the new log Mode for the upcoming ARRL RTTY contest N1MM only gives me the option of either RTTY -OR- Digital, not both. Do I just select RTTY and do a mode switch during the contest? I have the ability to do multimodes for other modes like CW and SSB but I don't see an option for RTTY -AND- Digital. Am I missing something?

Thanks!

Bill - AK6A


Re: K3s, N1MM+ & MMTTY Settings

ckjones76@...
 

GE,

Rich, Max:  Thanks for the help, I could not get good without using the FSK-microHam and a matching COM port in N1MM.  Using just EXTFSK or EXTFSK64 I could get some keying but at the same time it sound like there was a carrier being TX'd also.

Danny:  Thanks for the hint on restoring the RTTY EMG window.  Weird, I have been using N1MM/MMTTY combo for almost 20yrs and have never seen this occur.

=============
HNY, 73, Chuck N7BV


Trying to open Radio 1 3rd receiver window

Jim W7RY
 

Trying to open an 3rd receiver window on radio 1 with 2-tone and get this error… It used to work…

 

Any ideas?

Thanks 73

Jim W7RY

 

 

N1MMLogger.net - Version 1.0.8052.0

Built: 12/31/2019 6:39:16 AM

Microsoft Windows NT 10.0.18362.0,64:1,en-US,en-US

Error occurred at: 1/2/2020 8:09:08 PM in Thread:

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

System.UnauthorizedAccessException: Access to the port 'COM1' is denied.

   at System.IO.Ports.InternalResources.WinIOError(Int32 errorCode, String str)

   at System.IO.Ports.SerialStream..ctor(String portName, Int32 baudRate, Parity parity, Int32 dataBits, StopBits stopBits, Int32 readTimeout, Int32 writeTimeout, Handshake handshake, Boolean dtrEnable, Boolean rtsEnable, Boolean discardNull, Byte parityReplace)

   at System.IO.Ports.SerialPort.Open()

   at N1MMLogger.Net.DigitalMultiRXWindow.InitRTTYInterface() in C:\N1MM+Source\N1MM Logger on .NET\main\N1MM Logger.Net\Forms\DigitalMultiRXWindow.vb:line 1256

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

 

 

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

   at System.Environment.get_StackTrace()

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

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

   at N1MMLogger.Net.DigitalMultiRXWindow.InitRTTYInterface() in C:\N1MM+Source\N1MM Logger on .NET\main\N1MM Logger.Net\Forms\DigitalMultiRXWindow.vb:line 1347

   at N1MMLogger.Net.DigitalMultiRXWindow.DigitalMultiRXWindow_Load(Object sender, EventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\main\N1MM Logger.Net\Forms\DigitalMultiRXWindow.vb:line 907

   at System.Windows.Forms.Form.OnLoad(EventArgs e)

   at System.Windows.Forms.Form.SetVisibleCore(Boolean value)

   at System.Windows.Forms.Control.Show()

   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)

   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)

   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

   at Microsoft.VisualBasic.CompilerServices.Symbols.Container.InvokeMethod(Method TargetProcedure, Object[] Arguments, Boolean[] CopyBack, BindingFlags Flags)

  at Microsoft.VisualBasic.CompilerServices.NewLateBinding.CallMethod(Container BaseReference, String MethodName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack, BindingFlags InvocationFlags, Boolean ReportErrors, ResolutionFailure& Failure)

   at Microsoft.VisualBasic.CompilerServices.NewLateBinding.ObjectLateCall(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack, Boolean IgnoreReturn)

   at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateCall(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack, Boolean IgnoreReturn)

   at N1MMLogger.Net.DigitalInterface.mnuOpenRXWindows_Click(Object sender, EventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\main\N1MM Logger.Net\Forms\DigitalInterface.vb:line 5868

   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)

   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)

   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)

   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)

   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)

   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)

   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)

   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)

   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

   at System.Windows.Forms.Control.WndProc(Message& m)

   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

   at System.Windows.Forms.ToolStrip.WndProc(Message& m)

   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)

   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)

   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)

   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)

   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()

   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()

   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)

   at N1MMLogger.Net.My.MyApplication.Main(String[] Args) in :line 82

 

Thanks and 73

Jim W7RY

 


Re: TQSL does not recognize my Cabrillo CWT file

Rich K1DJ
 

Thanks for the suggestions everybody!   After attempting to track down some HML info that Rich VE3KI suggested might indicate that TQSL had omitted CW Op contests, but not finding the file, I tried a second or third time to load the ADIF version of the problem CWT log into LOTW and it went through.  I had no problem loading the Cabrillo version of the next CWT, so it appears to have been some sort of mistake by me or my computer or the software (I always suspect I am the most likely of these with computer issues) on the one log.
I have been loading Cabrillo files into LOTW for several years with only rare rejections, and on those occasions, LOTW until now had always accepted the ADIF versions of the logs.  This was the first time LOTW had rejected both formats of a log.
73 -
Rich, K1DJ


On Jan 2, 2020, at 6:29 PM, Michael Keane K1MK <k1mk@...> wrote:


On 01/01/2020 3:20 PM, Rich K1DJ via Groups.Io wrote:
K3S, Windows 7 PC, N1MM+ latest version

After today's 1900Z CWT, I generated a cabrillo file as always and tried to upload it to LOTW via TQSL.  This worked fine with the same versions of N1MM+ and TQSL earlier today after the 1300Z CWT.

This time, TQSL refused to accept the log.  I got the following from TQSL:
"
Signing using Callsign K1DJ, DXCC Entity UNITED STATES OF AMERICA

Error: C:\Users\Owner\Documents\N1MM Logger+\ExportFiles\K1DJ CWT 1.1.20 1900.log: Cabrillo unknown CONTEST: CW-Ops
Unable to find a valid call-worked field.
Please define a custom Cabrillo entry for this contest.
 on line 14
"

I tried saving the log as an ADIF file and got essentially the same message rejecting the log from TQSL.

Help please?

Rich, K1DJ


What does line 14 of your Cabrillo file look like?

TQSL is complaining that it can't find  what it recognizes as a callsign on that line

73,
Mike K1MK


Green light when listening to both RX in SO2R

Art Suberbielle
 

When running SO2R using a DX-Doubler, I often listen to both audio streams simultaneously. Would it be possible to get N1MM to show the green light in both entry windows when doing so?

I usually have my eyes fixed on the entry windows and not looking at the DX-Doubler that does show two green lights.

Thanks and HNY to all the N1MM gang.

73,
Art KZ5D


Re: N1MM CW Question

AB2ZY
 

I'm partial to the Microham products. For a single radio, the Digikeyer II will provide CAT, PTT, FSK, Winkey and a sound card separate from the computer for digital modes. The only limitation is that voice playback does not mute the radio microphone, so you either need to use your computer soundcard for that or find a way to mute the radio mike while transmitting. If you don't use prerecorded messages, then it is no concern whatsoever.

Way better than the Signallink for serious work.

Al
AB2ZY

On 1/2/2020 4:50 PM, Cable Television wrote:
Tom,
What interfaces work well with N1MM?

I heard the Rigblaster Advantage my integrate well with N1NN.

TNX

WA3TD


On Thu, Jan 2, 2020, 11:27 AM Tom Wagner (N1MM)
<n1mmtomwagner@... <mailto:n1mmtomwagner@...>> wrote:

I looked at the manual. It appears that cw sending via dtr is NOT
supported.

You will probably need to generate cw via audio.   This is not
supported by n1mm.

Further, the product has a 25 wpm limit for cw  via keying cable.
This is inadequate for contest use.

Buy a Morty or a winkeyer.

Tom - N1MM

On Thu, Jan 2, 2020, 11:08 AM Vytenis LY5T
<vytenis.sciucka@... <mailto:vytenis.sciucka@...>> wrote:

CTRL-K ?

ly5t
Vytenis


Re: TQSL does not recognize my Cabrillo CWT file

Michael Keane K1MK
 

On 01/01/2020 3:20 PM, Rich K1DJ via Groups.Io wrote:
K3S, Windows 7 PC, N1MM+ latest version

After today's 1900Z CWT, I generated a cabrillo file as always and tried to upload it to LOTW via TQSL.  This worked fine with the same versions of N1MM+ and TQSL earlier today after the 1300Z CWT.

This time, TQSL refused to accept the log.  I got the following from TQSL:
"
Signing using Callsign K1DJ, DXCC Entity UNITED STATES OF AMERICA

Error: C:\Users\Owner\Documents\N1MM Logger+\ExportFiles\K1DJ CWT 1.1.20 1900.log: Cabrillo unknown CONTEST: CW-Ops
Unable to find a valid call-worked field.
Please define a custom Cabrillo entry for this contest.
 on line 14
"

I tried saving the log as an ADIF file and got essentially the same message rejecting the log from TQSL.

Help please?

Rich, K1DJ


What does line 14 of your Cabrillo file look like?

TQSL is complaining that it can't find  what it recognizes as a callsign on that line

73,
Mike K1MK


Re: N1MM CW Question

Tom Wagner (N1MM)
 

https://n1mmwp.hamdocs.com/manual-supported/supported-radios/#ts-590-ts-590d

For CW: Mortty or Winkey

For RTTY: Internal TS-590 codec or Mortty

For SSB: Internal TS-590 codec.

Sell the SignalLink and buy a Mortty or Winkey.

Tom

On 1/2/2020 4:50 PM, Cable Television wrote:
Tom,
What interfaces work well with N1MM?

I heard the Rigblaster Advantage my integrate well with N1NN.

TNX

WA3TD


On Thu, Jan 2, 2020, 11:27 AM Tom Wagner (N1MM) <n1mmtomwagner@... <mailto:n1mmtomwagner@...>> wrote:

I looked at the manual. It appears that cw sending via dtr is NOT
supported.

You will probably need to generate cw via audio.   This is not
supported by n1mm.

Further, the product has a 25 wpm limit for cw  via keying cable.
This is inadequate for contest use.

Buy a Morty or a winkeyer.

Tom - N1MM

On Thu, Jan 2, 2020, 11:08 AM Vytenis LY5T
<vytenis.sciucka@... <mailto:vytenis.sciucka@...>> wrote:

CTRL-K ?

ly5t
Vytenis


Re: TQSL does not recognize my Cabrillo CWT file

Mikel EA2CW
 

You are right, but I have always sent my logs as ADIF and never have any problem. Try this way, please


Re: TQSL does not recognize my Cabrillo CWT file

Jack Brindle
 

Not true. It accepts both formats. I use the Cabrillo format almost exclusively for LOTW uploads after each contest.

73!
Jack, W6FB


On Jan 2, 2020, at 2:17 PM, Mikel EA2CW <ea2cw@...> wrote:

As far as I know, TQSL only accepts ADIF files, not Cabrillo. Export your log from N1MM to adif, and upload the generated .adi file. You will not find any trouble
73, Mikel


Re: TQSL does not recognize my Cabrillo CWT file

Mikel EA2CW
 

As far as I know, TQSL only accepts ADIF files, not Cabrillo. Export your log from N1MM to adif, and upload the generated .adi file. You will not find any trouble
73, Mikel


Re: N1MM CW Question

Drew Vonada-Smith K3PA
 

For CW, anything with a Winkey.  For low cost, look at MORTTY.

73,
Drew K3PA


Re: N1MM+ will not install

Madison R. Jones
 

Thank, Larry. That worked!


Re: N1MM CW Question

Carol Richards
 

Hello,

I have a rig blaster advantage and it does work on CW, but I have found that a usb cable with the FTDI chip is a better alternative. I use the rig blaster advantage for RTTY, FT8, FT4 and as a DVK.


Carol

On 1/2/2020 5:02 PM, Gilbert Baron W0MN wrote:

 

 

Outlook Laptop Gil W0MN

Hierro candente, batir de repente

44.08226N 92.51265W EN34rb

 

From: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io> On Behalf Of Cable Television
Sent: Thursday, January 2, 2020 15:50
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] N1MM CW Question

 

Tom, 

What interfaces work well with N1MM?

 

I heard the Rigblaster Advantage my integrate well with N1NN.

 

TNX

 

WA3TD

 

 

On Thu, Jan 2, 2020, 11:27 AM Tom Wagner (N1MM) <n1mmtomwagner@...> wrote:

I looked at the manual. It appears that cw sending via dtr is NOT supported.  

 

You will probably need to generate cw via audio.   This is not supported by n1mm. 

 

Further, the product has a 25 wpm limit for cw  via keying cable. This is inadequate for contest use.

 

NO BUT BETTER THAN THE 49 WPM I HAVE MEASURED FROM SOME.

 

 

Buy a Morty or a winkeyer.

 

Tom - N1MM

 

On Thu, Jan 2, 2020, 11:08 AM Vytenis LY5T <vytenis.sciucka@...> wrote:

CTRL-K ?

ly5t
Vytenis


--
W0MN Rochester, MN


Re: N1MM CW Question

Gilbert Baron W0MN
 

 

 

Outlook Laptop Gil W0MN

Hierro candente, batir de repente

44.08226N 92.51265W EN34rb

 

From: N1MMLoggerPlus@groups.io <N1MMLoggerPlus@groups.io> On Behalf Of Cable Television
Sent: Thursday, January 2, 2020 15:50
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MM+] N1MM CW Question

 

Tom, 

What interfaces work well with N1MM?

 

I heard the Rigblaster Advantage my integrate well with N1NN.

 

TNX

 

WA3TD

 

 

On Thu, Jan 2, 2020, 11:27 AM Tom Wagner (N1MM) <n1mmtomwagner@...> wrote:

I looked at the manual. It appears that cw sending via dtr is NOT supported.  

 

You will probably need to generate cw via audio.   This is not supported by n1mm. 

 

Further, the product has a 25 wpm limit for cw  via keying cable. This is inadequate for contest use.

 

NO BUT BETTER THAN THE 49 WPM I HAVE MEASURED FROM SOME.

 

 

Buy a Morty or a winkeyer.

 

Tom - N1MM

 

On Thu, Jan 2, 2020, 11:08 AM Vytenis LY5T <vytenis.sciucka@...> wrote:

CTRL-K ?

ly5t
Vytenis


--
W0MN Rochester, MN


Re: N1MM CW Question

Cable Television
 

Tom, 
What interfaces work well with N1MM?

I heard the Rigblaster Advantage my integrate well with N1NN.

TNX

WA3TD


On Thu, Jan 2, 2020, 11:27 AM Tom Wagner (N1MM) <n1mmtomwagner@...> wrote:
I looked at the manual. It appears that cw sending via dtr is NOT supported.  

You will probably need to generate cw via audio.   This is not supported by n1mm. 

Further, the product has a 25 wpm limit for cw  via keying cable. This is inadequate for contest use.

Buy a Morty or a winkeyer.

Tom - N1MM

On Thu, Jan 2, 2020, 11:08 AM Vytenis LY5T <vytenis.sciucka@...> wrote:
CTRL-K ?

ly5t
Vytenis


Re: N1MM+ will not install

Larry K8UT
 

Did you follow the instructions in the error message: "Rename the file before restarting N1MM Logger"?

There is something wrong with your N1MM Admin database (not your logging database). Renaming it will force N1MM to create a new database and give you a fresh start.

-larry K8UT

------ Original Message ------
From: "Madison R. Jones" <w5mikejuliet@...>
Sent: 2020-01-02 15:34:39
Subject: Re: [N1MM+] N1MM+ will not install

I updated to the latest version, but other than the splash screen, there was no further activity. After  waiting for 5 minutes while the computer did nothing, I received a message that the image was “malformed.” What next?


Re: N1MM+ will not install

Madison R. Jones
 

I updated to the latest version, but other than the splash screen, there was no further activity. After  waiting for 5 minutes while the computer did nothing, I received a message that the image was “malformed.” What next?