Date   
Re: Airspy & Spectrum Scope

John H. Long Jr.
 

I am also having problems with getting Airspy HF+ Discovery working in the N1MM spectrum display.
 
This is my first attempt at trying to run it.
Do I need to change anything as a way of setting up spyserver and N1MM?
 
I noticed Airsoy server screen says it is listening on 0.0.0.0:5555
  N1mm seems to be looking for 127.0.0.0:5555
 
Is that an issue?
 
 
 
 
 
 
John H. Long Jr.
KW7A
1370 N 150 E
Nephi, UT 84648
USA
 
(435) 888-LONG
 
 

--------- Original Message ---------
Subject: [N1MM+] Airspy & Spectrum Scope
From: 'William Liporace WC2L' <wc2l@...>
Date: 11/20/19 7:03 pm
To: N1MMLoggerPlus@groups.io

I'm hoping someone can help me!!
I have the latest version of N1MM & SDRPlay!

When I start N1MM+, Spyserver does not auto start.
Manually start Spyserver
Start N1MM+
Window - Spectrum Display
Right Click Spectrum Display - Airspy HF+
Then I get the following error:

N1MMLogger.net - Version 1.0.8014.0
Built: 11/13/2019 8:53:10 AM
Microsoft Windows NT 10.0.18363.0,64:1,en-US,en-US
Error occurred at: 11/20/2019 8:48:31 PM in Thread: Spectrum UI Thread - a12dd15d-87ac-49f8-9cc7-0c774e031876
---------------------------------------------------------------------------------------
System.ApplicationException: Device got disconnected
   at N1MMLogger.Net.SDRSharp.FrontEnds.SpyServer.SpyClient.Connect(String host, Int32 port) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\AirspyInterface.vb:line 166
   at N1MMLogger.Net.SpectrumWindow.SpyConnect() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 4161
   at N1MMLogger.Net.SpectrumWindow.ConnectSpy() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 4138
   at N1MMLogger.Net.SpectrumWindow.SetUpSpectrumProcessingClass() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 1309
---------------------------------------------------------------------------------------

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\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\N1MM Logger.Net\Modules\SharedCode.vb:line 186
   at N1MMLogger.Net.SpectrumWindow.SetUpSpectrumProcessingClass() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 1355
   at N1MMLogger.Net.SpectrumWindow.AirspySourceMenuItem_Click(Object sender, EventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 2241
   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 System.Windows.Forms.Application.Run(Form mainForm)
   at N1MMLogger.Net.N1MMLoggerCommon.StartSpectrumWindow(Object aGuid) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Modules\N1MMLoggerCommon.vb:line 11600
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart(Object obj)

The Spyserver says Device is sleeping, Wake up!
Could not acquire the device

If I try to connect anyway, I get the following:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ApplicationException: Device got disconnected
   at N1MMLogger.Net.SDRSharp.
FrontEnds.SpyServer.SpyClient.Connect(String host, Int32 port) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\AirspyInterface.vb:line 166
   at N1MMLogger.Net.SpectrumWindow.
SpyConnect() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 4161
   at N1MMLogger.Net.SpectrumWindow.
ConnectSpy() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 4138
   at N1MMLogger.Net.SpectrumWindow.
AirspyConnect_Click(Object sender, EventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 4346
   at System.Windows.Forms.Control.
OnClick(EventArgs e)
   at System.Windows.Forms.Button.
OnClick(EventArgs e)
   at System.Windows.Forms.Button.
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)

************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4042.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.
NET/Framework/v4.0.30319/mscorlib.dll
------------------------------
----------
N1MMLogger.net
    Assembly Version: 1.0.8014.0
    Win32 Version: 1.0.8014
    CodeBase: file:///C:/Program%20Files%20(
x86)/N1MM%20Logger+/N1MMLogger.net.exe
------------------------------
----------
Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 14.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.
Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
------------------------------
----------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.
Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
------------------------------
----------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4042.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.
Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
------------------------------
----------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4042.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.
Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
------------------------------
----------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.
Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
------------------------------
----------
N1MMLibrary
    Assembly Version: 1.0.8014.0
    Win32 Version: 1.0.8014
    CodeBase: file:///C:/Program%20Files%20(
x86)/N1MM%20Logger+/N1MMLibrary.DLL
------------------------------
----------
IQ
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files%20(
x86)/N1MM%20Logger+/IQ.DLL
------------------------------
----------
System.Windows.Forms.
DataVisualization
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3815.0
    CodeBase: file:///C:/WINDOWS/Microsoft.
Net/assembly/GAC_MSIL/System.Windows.Forms.DataVisualization/v4.0_4.0.0.0__31bf3856ad364e35/System.Windows.Forms.DataVisualization.dll
------------------------------
----------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.
Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
------------------------------
----------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.
Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
------------------------------
----------
System.Web
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4042.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.
Net/assembly/GAC_32/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll
------------------------------
----------
System.Runtime.Remoting
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.
Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
------------------------------
----------
System.Data.SQLite
    Assembly Version: 1.0.92.0
    Win32 Version: 1.0.92.0
    CodeBase: file:///C:/Program%20Files%20(
x86)/N1MM%20Logger+/System.Data.SQLite.DLL
------------------------------
----------
System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.
Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
------------------------------
----------
AxInterop.N1MMV12WaveLib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.0.0
    CodeBase: file:///C:/Program%20Files%20(
x86)/N1MM%20Logger+/AxInterop.N1MMV12WaveLib.DLL
------------------------------
----------
N1MMV12WaveLib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.0.0
    CodeBase: file:///C:/Program%20Files%20(
x86)/N1MM%20Logger+/N1MMV12WaveLib.DLL
------------------------------
----------
Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.
Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
------------------------------
----------
System.Transactions
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.
Net/assembly/GAC_32/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll
------------------------------
----------
ObjectListView
    Assembly Version: 2.7.0.42249
    Win32 Version: 2.7.0.0
    CodeBase: file:///C:/Program%20Files%20(
x86)/N1MM%20Logger+/ObjectListView.DLL
------------------------------
----------
System.EnterpriseServices
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.
Net/assembly/GAC_32/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
------------------------------
----------
System.Runtime.Caching
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0
    CodeBase: file:///C:/WINDOWS/Microsoft.
Net/assembly/GAC_MSIL/System.Runtime.Caching/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Runtime.Caching.dll
------------------------------
----------
RawInput
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files%20(
x86)/N1MM%20Logger+/RawInput.DLL
------------------------------
----------
Microsoft.VisualBasic.
PowerPacks.Vs
    Assembly Version: 10.0.0.0
    Win32 Version: 11.0.50727.1
    CodeBase: file:///C:/Program%20Files%20(
x86)/N1MM%20Logger+/Microsoft.VisualBasic.PowerPacks.Vs.DLL
------------------------------
----------
NAudio
    Assembly Version: 1.8.5.0
    Win32 Version: 1.8.5.0
    CodeBase: file:///C:/Program%20Files%20(
x86)/N1MM%20Logger+/NAudio.DLL
------------------------------
----------
System.Numerics
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.
Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
------------------------------
----------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


What is going on?? Can someone help??
TNX Will WC2L

-- 
William Liporace WC2L
http://www.wc2l.com or http://dxc.wc2l.com
AR-Cluster Node  telnet dxc.wc2l.com or 144.93 MHz
wc2l@...

Re: Icom voice memories?

Dany VE2EBK
 

Airspy & Spectrum Scope

William Liporace WC2L
 

I'm hoping someone can help me!!
I have the latest version of N1MM & SDRPlay!

When I start N1MM+, Spyserver does not auto start.
Manually start Spyserver
Start N1MM+
Window - Spectrum Display
Right Click Spectrum Display - Airspy HF+
Then I get the following error:

N1MMLogger.net - Version 1.0.8014.0
Built: 11/13/2019 8:53:10 AM
Microsoft Windows NT 10.0.18363.0,64:1,en-US,en-US
Error occurred at: 11/20/2019 8:48:31 PM in Thread: Spectrum UI Thread - a12dd15d-87ac-49f8-9cc7-0c774e031876
---------------------------------------------------------------------------------------
System.ApplicationException: Device got disconnected
   at N1MMLogger.Net.SDRSharp.FrontEnds.SpyServer.SpyClient.Connect(String host, Int32 port) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\AirspyInterface.vb:line 166
   at N1MMLogger.Net.SpectrumWindow.SpyConnect() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 4161
   at N1MMLogger.Net.SpectrumWindow.ConnectSpy() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 4138
   at N1MMLogger.Net.SpectrumWindow.SetUpSpectrumProcessingClass() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 1309
---------------------------------------------------------------------------------------

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\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\N1MM Logger.Net\Modules\SharedCode.vb:line 186
   at N1MMLogger.Net.SpectrumWindow.SetUpSpectrumProcessingClass() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 1355
   at N1MMLogger.Net.SpectrumWindow.AirspySourceMenuItem_Click(Object sender, EventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 2241
   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 System.Windows.Forms.Application.Run(Form mainForm)
   at N1MMLogger.Net.N1MMLoggerCommon.StartSpectrumWindow(Object aGuid) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Modules\N1MMLoggerCommon.vb:line 11600
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart(Object obj)

The Spyserver says Device is sleeping, Wake up!
Could not acquire the device

If I try to connect anyway, I get the following:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ApplicationException: Device got disconnected
   at N1MMLogger.Net.SDRSharp.FrontEnds.SpyServer.SpyClient.Connect(String host, Int32 port) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\AirspyInterface.vb:line 166
   at N1MMLogger.Net.SpectrumWindow.SpyConnect() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 4161
   at N1MMLogger.Net.SpectrumWindow.ConnectSpy() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 4138
   at N1MMLogger.Net.SpectrumWindow.AirspyConnect_Click(Object sender, EventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 4346
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.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)

************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4042.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
N1MMLogger.net
    Assembly Version: 1.0.8014.0
    Win32 Version: 1.0.8014
    CodeBase: file:///C:/Program%20Files%20(x86)/N1MM%20Logger+/N1MMLogger.net.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 14.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4042.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4042.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
N1MMLibrary
    Assembly Version: 1.0.8014.0
    Win32 Version: 1.0.8014
    CodeBase: file:///C:/Program%20Files%20(x86)/N1MM%20Logger+/N1MMLibrary.DLL
----------------------------------------
IQ
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files%20(x86)/N1MM%20Logger+/IQ.DLL
----------------------------------------
System.Windows.Forms.DataVisualization
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3815.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.DataVisualization/v4.0_4.0.0.0__31bf3856ad364e35/System.Windows.Forms.DataVisualization.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Web
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4042.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll
----------------------------------------
System.Runtime.Remoting
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Data.SQLite
    Assembly Version: 1.0.92.0
    Win32 Version: 1.0.92.0
    CodeBase: file:///C:/Program%20Files%20(x86)/N1MM%20Logger+/System.Data.SQLite.DLL
----------------------------------------
System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
AxInterop.N1MMV12WaveLib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.0.0
    CodeBase: file:///C:/Program%20Files%20(x86)/N1MM%20Logger+/AxInterop.N1MMV12WaveLib.DLL
----------------------------------------
N1MMV12WaveLib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.0.0
    CodeBase: file:///C:/Program%20Files%20(x86)/N1MM%20Logger+/N1MMV12WaveLib.DLL
----------------------------------------
Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Transactions
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll
----------------------------------------
ObjectListView
    Assembly Version: 2.7.0.42249
    Win32 Version: 2.7.0.0
    CodeBase: file:///C:/Program%20Files%20(x86)/N1MM%20Logger+/ObjectListView.DLL
----------------------------------------
System.EnterpriseServices
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
----------------------------------------
System.Runtime.Caching
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Caching/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Runtime.Caching.dll
----------------------------------------
RawInput
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files%20(x86)/N1MM%20Logger+/RawInput.DLL
----------------------------------------
Microsoft.VisualBasic.PowerPacks.Vs
    Assembly Version: 10.0.0.0
    Win32 Version: 11.0.50727.1
    CodeBase: file:///C:/Program%20Files%20(x86)/N1MM%20Logger+/Microsoft.VisualBasic.PowerPacks.Vs.DLL
----------------------------------------
NAudio
    Assembly Version: 1.8.5.0
    Win32 Version: 1.8.5.0
    CodeBase: file:///C:/Program%20Files%20(x86)/N1MM%20Logger+/NAudio.DLL
----------------------------------------
System.Numerics
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


What is going on?? Can someone help??
TNX Will WC2L

-- 
William Liporace WC2L
http://www.wc2l.com or http://dxc.wc2l.com
AR-Cluster Node  telnet dxc.wc2l.com or 144.93 MHz
wc2l@...

Icom voice memories?

Jamie WW3S
 

Is there a way for the software to trigger the internal Icom voice memories?

Re: Initial Startup of N1MM+

Tom Wagner (N1MM)
 

On 11/20/2019 4:03 PM, Jimmy Moser wrote:
Equipment: ICOM 7300
                  Windows 10 PC
                  USB cable connecting radio and PC

Have installed the N1MM+ software and have done the update. When I startup the program
I configure the ports, radio, etc. The radio then immediately goes into xmit mode. Is there a
setting that I have mis-configured that is causing this? Anyone else have this problem?

Jimmy
KN4LXH

Re: Multiplier-search/Third computer on M/2 network?

Rick Tavan
 

OK, thanks Chris. No, won’t be working stations from the third listen-only position. Now I understand that I can have two “RunN” computers.

/Rick

--
Rick Tavan

On Nov 20, 2019, at 4:01 PM, Chris Plumblee <chris.plumblee@...> wrote:


The third computer can be either Run1 or Run2. The associated transmitter (if you intend to transmit with it) should be interlocked to prevent two signals from Run1 or Run2 being on the air at once. 

If it's just a hot standby it's not critical which you choose as that computer will not be adding QSOs to the log. 

You can switch Run1/Run2 for a given computer with a keyboard command that eludes me at the moment.

73,
Chris W4WF

On Wed, Nov 20, 2019 at 1:52 PM Rick Tavan <rtavan@...> wrote:
Is there a way to have a third computer online when operating M/2, both for multiplier searching and as a hot standby? Trying this, MM insists that the third computer be either Run1 or Run2. There are already Run1 and Run2 computers on the network. What do I tell the third computer?

thanks,

/Rick N6XI

--
--

Rick Tavan
Truckee and Saratoga, CA

--
Chris Plumblee
407.494.5155

Re: Multiplier-search/Third computer on M/2 network?

Rick Tavan
 

Thanks, Tom. No interest in working found mults, just band mapping them. But need to get thru specifying Run1 or Run2 which are the actual transmit positions.

Rick N6XI

--
Rick Tavan

On Nov 20, 2019, at 3:57 PM, Tom Wagner (N1MM) <n1mmtomwagner@...> wrote:

There is no multiplier station in M2. You would need to specify Run1 or Run2 at any given time for that station and make sure it doesn't run the band change limit over 8. Assuming each QSO is in the middle of a big run for the corresponding Run1/Run2 station, each QSO will create two band changes for that station. Note that you are responsible to electrically prevent two signals by the same Run1/Run2 station from transmitting at the same time.

*2. Two Transmitters (MULTI-TWO):*A maximum of two transmitted signals on two different bands may be used at any time. The log must indicate which station/signal made each QSO. Each station/signal may make a maximum of 8 band changes in any clock hour (00 through 59 minutes). Total output power must not exceed 1500 watts on any band at any time.

Tom - N1MM

On 11/20/2019 1:51 PM, Rick Tavan wrote:
Is there a way to have a third computer online when operating M/2, both for multiplier searching and as a hot standby? Trying this, MM insists that the third computer be either Run1 or Run2. There are already Run1 and Run2 computers on the network. What do I tell the third computer?

thanks,

/Rick N6XI

--
--

Rick Tavan
Truckee and Saratoga, CA

Re: Initial Startup of N1MM+

Rick Tavan
 

Check DTR/Rts settings on the Config Hardware line for your radio? If it treats either as PTT, that’s what you’d see.

Rick N6XI

--
Rick Tavan

On Nov 20, 2019, at 6:04 PM, Jimmy Moser <wxgeek@...> wrote:

Equipment: ICOM 7300
                  Windows 10 PC
                  USB cable connecting radio and PC

Have installed the N1MM+ software and have done the update. When I startup the program
I configure the ports, radio, etc. The radio then immediately goes into xmit mode. Is there a
setting that I have mis-configured that is causing this? Anyone else have this problem?

Jimmy
KN4LXH

Initial Startup of N1MM+

Jimmy Moser <wxgeek@...>
 

Equipment: ICOM 7300
                  Windows 10 PC
                  USB cable connecting radio and PC

Have installed the N1MM+ software and have done the update. When I startup the program
I configure the ports, radio, etc. The radio then immediately goes into xmit mode. Is there a
setting that I have mis-configured that is causing this? Anyone else have this problem?

Jimmy
KN4LXH

Re: Multiplier-search/Third computer on M/2 network?

Chris Plumblee
 

The third computer can be either Run1 or Run2. The associated transmitter (if you intend to transmit with it) should be interlocked to prevent two signals from Run1 or Run2 being on the air at once. 

If it's just a hot standby it's not critical which you choose as that computer will not be adding QSOs to the log. 

You can switch Run1/Run2 for a given computer with a keyboard command that eludes me at the moment.

73,
Chris W4WF

On Wed, Nov 20, 2019 at 1:52 PM Rick Tavan <rtavan@...> wrote:
Is there a way to have a third computer online when operating M/2, both for multiplier searching and as a hot standby? Trying this, MM insists that the third computer be either Run1 or Run2. There are already Run1 and Run2 computers on the network. What do I tell the third computer?

thanks,

/Rick N6XI

--
--

Rick Tavan
Truckee and Saratoga, CA

--
Chris Plumblee
407.494.5155

Re: Multiplier-search/Third computer on M/2 network?

Tom Wagner (N1MM)
 

There is no multiplier station in M2.  You would need to specify Run1 or Run2 at any given time for that station and make sure it doesn't run the band change limit over 8.  Assuming each QSO is in the middle of a big run for the corresponding Run1/Run2 station, each QSO will create two band changes for that station. Note that you are responsible to electrically prevent two signals by the same Run1/Run2 station from transmitting at the same time.

*2. Two Transmitters (MULTI-TWO):*A maximum of two transmitted signals on two different bands may be used at any time. The log must indicate which station/signal made each QSO. Each station/signal may make a maximum of 8 band changes in any clock hour (00 through 59 minutes). Total output power must not exceed 1500 watts on any band at any time.

Tom - N1MM

On 11/20/2019 1:51 PM, Rick Tavan wrote:
Is there a way to have a third computer online when operating M/2, both for multiplier searching and as a hot standby? Trying this, MM insists that the third computer be either Run1 or Run2. There are already Run1 and Run2 computers on the network. What do I tell the third computer?

thanks,

/Rick N6XI

--
--

Rick Tavan
Truckee and Saratoga, CA

Multiplier-search/Third computer on M/2 network?

Rick Tavan
 

Is there a way to have a third computer online when operating M/2, both for multiplier searching and as a hot standby? Trying this, MM insists that the third computer be either Run1 or Run2. There are already Run1 and Run2 computers on the network. What do I tell the third computer?

thanks,

/Rick N6XI

--
--

Rick Tavan
Truckee and Saratoga, CA

Re: Kudos

ckjones76@...
 

GM,

I also would  like to thank all those who make N1MM+ and my enjoyment of ham radio better. 

Members of this group who contribute personally to solving problems for others such as Rich VE3KI and Joe WB9SBD who step up to help others are greatly appreciated.

Tks.  73, Chuck N7BV

CTY-2916 Country Files - 20 November 2019

Jim Reisert AD1C
 

The Country (CTY) Files were updated on 20 November 2019:

http://www.country-files.com/cty-2916-20-november-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-20-november-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:

20 November 2019 (CTY-2916)
VER20191120, Version entity is Austral Islands, FO/a

Added/changed Entities/Prefixes/Callsigns:

* 3D2AG/P is Rotuma Island, 3D2/r
* 3DA0BP/J is Kingdom of eSwatini, 3DA
* A41HA/ND, A41KJ/ND and A41NN/ND are all Oman, A4
* A61Q/FD is United Arab Emirates, A6
* CE9/SQ1SGB and VP8HAL are both Antarctica, CE9 in ITU zone 73
* EA5EZ/P is Spain, EA
* EA8BFH/P is Canary Islands, EA8
* EA1DFP/9 is Ceuta & Melilla, EA9
* FO/F6BCW is Marquesas Islands, FO/m
* TO9W is St. Martin, FS
* GB0SBG is Northern Ireland, GI
* GB0GDS, GB2CWR and GB2SAS are all Scotland, GM
* 4U25B, II5BP/J and IK6FAW/J are all Italy, I
* N2JNR is United States, K in CQ zone 3, ITU zone 6
* W2IY and W9DKB are both United States, K in CQ zone 4, ITU zone 7
* AE4ED, K4UU, N3RA, NJ4P and NN4NT are all United States, K in CQ zone 4, ITU zone 8
* K9GWS is United States, K in CQ zone 5, ITU zone 8
* AE7CA is Guam, KH2
* K6HNL, KL3JC, KM6UVP and N7ODC are all Hawaii, KH6
* K7VRK, KB4DX, KF4JET, KF7FLL, KF7FLM, KF7KTH and KM4AGL are all Alaska, KL
* LU1DI/D, LU1ELY/D, LU1IG/I, LU1SF/S, LU1UG/U, LU2CDE/D, LU2EE/D,
LU2EGA/D, LU2ENH/D, LU2EPL/D, LU2EPP/D, LU2FGD/J, LU3AYE/D, LU3DAR/D, LU3DEY/D,
LU3DJA/D, LU3DJT/D, LU3ELR/D, LU3FCA/F, LU3FV/F, LU4DGC/D, LU4DLN/D, LU4KC/K,
LU5DA/D, LU5DGR/D, LU5DQ/D, LU5HA/H, LU5HPM/H, LU5QR/Q, LU6EQV/D, LU6EVD/D,
LU7DHE/D, LU7DLN/D, LU7DW/D, LU7EXX/D, LU7KGB/O, LU7YG/F, LU8DY/D, LU8GCJ/GA,
LU8VCC/U, LU9AOS/D, LU9DPI/D, LU9DPI/I, LU9FBA/F, LU9LOP/L, LW1DXH/D, LW1ECE/D,
LW2DKF/D, LW2EQS/D, LW3DAB/D, LW3DED/D, LW3DGC/D, LW3DJC/D, LW3DTD/D, LW3EK/D,
LW5DTD/D, LW5DUS/D, LW6DYZ/D, LW8EGA/D, LW9DTP/D, LW9DTQ/D and LW9EDX/D
are all Argentina, LU
* LU1VDF/V, LU1VYL/V, LU1XAB/V, LU1YJG/V, LU1YY/V, LU2WA/W, LU3YLF/V,
LU5YEC/V, LU6VEK/W, LU8VCC/V and LU8XW/XP are all Argentina, LU in ITU zone 16
* OV4JAM/J is Denmark, OZ
* PA0TLM/J, PA1AW/J, PA1EDL/J, PA1ET/J, PA2RO/J, PA3AFG/J, PA4AGO/J,
PA4WK/J, PA6JAM/J, PA6SHB/J, PA6SJB/J, PA9JAS/J, PC5D/J, PC6RH/J, PE18KA/J,
PE1ORG/J, PE1PEX/J, PE7M/J, PH9GFB/J and PI4VHW/J are all Netherlands, PA
* SV2AEL/J, SV2CLJ/J, SV2JAO/J and SZ4SRM/J are all Greece, SV
* R105DA, R200SB, R9JBF/1, RD0L/3, UA9MA/1 and UA9MA/3 are all European Russia, UA
* R100MTK is European Russia, UA in ITU zone 30
* R1II/P is European Russia, UA in CQ zone 17, ITU zone 20
* RF1A/9 is Asiatic Russia, UA9
* R4YA/8 and RV7B/9 are both Asiatic Russia, UA9 in ITU zone 20
* R100KM and UA0ZDY/9 are both Asiatic Russia, UA9 in CQ zone 18, ITU zone 31
* VE2KK is in ITU zone 9, not ITU zone 4
* VE2KK is in CQ zone 5, not CQ zone 2
* VY2NA/VE2 is Canada, VE in CQ zone 2, ITU zone 4
* VK60LZ is Australia, VK
* HF0ANT is South Shetland Islands, VP8/h

Removed Entities/Prefixes/Callsigns:

* 4U500M in Vienna Intl Ctr, *4U1V
* GB2WAM in Shetland Islands, *GM/s
* 9M4CKT/6 and 9M4CRP/6 in East Malaysia, 9M6
* EA8BFH/4 and EA8BFH/P in Spain, EA
* EA5EZ and EA5EZ/P in Balearic Islands, EA6
* TO019IEEE and TO0MPB in Reunion Island, FR
* GB0WRH, GB2GVC, GB2KDR, GB2OWM, GB2RDR and GB2WAM in Scotland, GM
* GB0SRK in Guernsey, GU
* GB0CTK, GB0VK, GB0WHH, GB2SCC, GB4BIT, GB4OST and GB60ATG in Wales, GW
* 7Z1AL/ND in Saudi Arabia, HZ
* JD1BNA/JD1 in Minami Torishima, JD/m
* AH6AX and WD5F in United States, K
* AA7LE, AK2J, K6KKW, K6MIO, KB7AKQ, N1VOP and W4PRO in Hawaii, KH6
* KD0JJB, KF6RMG, KG7JVJ, N1NDA, N7HRO and N8SUG in Alaska, KL
* K2U, K7V and KB0JRR in Puerto Rico, KP4
* LU2FGD/F, LU3YA/V and LU9FNI/F in Argentina, LU
* 4U500M in Austria, OE
* R0CAF/3, R70MRK, R75YBO, R8MB/1, R9GM/P, R9OM/6, R9YU/3, RA9DF/4/P,
RA9DF/6/P, RA9KD/6, RA9SB/3, RA9WU/6, RN9N/6, RO75RK, RT9K/6, RU9CK/6/P,
RV9CX/6/P, RW9JZ/6, RW9WJ/P, UA9XK/1, UB5O/1 and UE90AGN in European Russia, UA
* UB5O/2 in Kaliningrad, UA2
* R1FW/0, RA4RU/9, RK4PA/9, RV3DSA/0, UB5O/0, UB5O/4, UB5O/8 and UB5O/9
in Asiatic Russia, UA9
* VK3ZK/6, VK3ZK/8, VK5FLEA/6 and VK6MB/3 in Australia, VK
* RI1ANF in South Shetland Islands, VP8/h

73 - Jim AD1C

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

Re: Faulty Mult recognition in SSB SS

VE9AA - Mike
 

I saw this for 1 mult in SS CW, I had worked VY1AAA , and another VY1 kept popping up red...I think it was VY1CO?

Unlike the USA, we all operate up here where our prefixes indicate our province or territory.

Easy, peasy

cu this w/e guys

Mike VE9AA NB

Re: Faulty Mult recognition in SSB SS

Drew Vonada-Smith K3PA
 

I saw the same thing re Canadian mults.  Worked them all, still saw red.

73,

Drew K3PA

Re: Faulty Mult recognition in SSB SS

Joe WB9SBD
 

Did anyone else have spots that ended up having freqs like in the FT-8 area down in the CW bands?
The box would turn RED in the mult window and if you clicked on it, you would go way down there?
Joe WB9SBD

On 11/19/2019 10:32 PM, Victor Paul wrote:
I noted two issues with multiplier identification.
First, after I had  worked every single Canadian multiplier, N1MM+ flagged VA3WSG in red in my Available Mults and Qs window.  After I cleared it out, I believe another VE3 also came up red in the AMQ window, but that phenomenon eventually stopped.  This isn't the first time I've seen an issue like this with Canadian mults (I seem to recall seeing something similar in one the RAC contests?) and have just lived with it. 

Second, and more concerning is the inverse of the problem above.  On Sunday AM the only mult I lacked was Puerto Rico.  As things had settled down I had the AMQ window set to show mults AND Qs, (not just Mults).  Good thing too, because I saw KP3MM come up, but only in blue.  N1MM+ hadn't recognized it as a needed Puerto Rican multiplier and if I'd left the AMQ window in Mults only mode I would have missed it.   I noticed that N1LN noting the same thing in his 3830 blurb at:

https://www.3830scores.com/showrumor.php?arg=RnaNzpmfcmsvp

Fortunately, I recognized it, swung the beam SE and bagged him.  Maybe the N1MM+ logic isn't set up to recognize KP3 as KP4?

Not a huge deal, but thought the developers would like to know.  Kudos to the N1MM+ team for their outstanding contribution to 21st century contesting.

73,
Victor WB0TEV

Faulty Mult recognition in SSB SS

Victor Paul
 

I noted two issues with multiplier identification.
First, after I had  worked every single Canadian multiplier, N1MM+ flagged VA3WSG in red in my Available Mults and Qs window.  After I cleared it out, I believe another VE3 also came up red in the AMQ window, but that phenomenon eventually stopped.  This isn't the first time I've seen an issue like this with Canadian mults (I seem to recall seeing something similar in one the RAC contests?) and have just lived with it. 

Second, and more concerning is the inverse of the problem above.  On Sunday AM the only mult I lacked was Puerto Rico.  As things had settled down I had the AMQ window set to show mults AND Qs, (not just Mults).  Good thing too, because I saw KP3MM come up, but only in blue.  N1MM+ hadn't recognized it as a needed Puerto Rican multiplier and if I'd left the AMQ window in Mults only mode I would have missed it.   I noticed that N1LN noting the same thing in his 3830 blurb at:

https://www.3830scores.com/showrumor.php?arg=RnaNzpmfcmsvp

Fortunately, I recognized it, swung the beam SE and bagged him.  Maybe the N1MM+ logic isn't set up to recognize KP3 as KP4?

Not a huge deal, but thought the developers would like to know.  Kudos to the N1MM+ team for their outstanding contribution to 21st century contesting.

73,
Victor WB0TEV

Re: N1MM Logger Plus and FT8

ve3ki
 

This is indeed a limitation in the FT8 (or FT4 or JT65 or JT9 or ...) protocol, and not in N1MM+, but it is not as simple as a character count.

FT8 messages are not encoded in ASCII. The data payload in an FT8 message is only 77 bits, and yet it can accommodate a message like KA1ABC DL1ABC JN68, although that message looks to us like 18 characters. In fact, that same message can also be sent in JT65, which has only a 72 bit payload.

The bottom line is that only standard call signs can be sent in the standard message formats. Compound call signs fit into a much more restricted set of message formats, and those don't include grid squares. Consult the WSJT-X documentation (chapters 7 and 17) for more information.

73,
Rich VE3KI

Re: N1MM Logger Plus and FT8

AB2ZY
 

Wasn’t this discussed recently?

 

Not an N1MM issue.  FT8 messages are limited to 13 characters. CQ PJ4/KU8E FK52 is 16 characters.

 

Al

AB2ZY

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Jeff Clarke
Sent: Tuesday, November 19, 2019 9:07 AM
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] N1MM Logger Plus and FT8

 

I've been doing some FT8 from PJ4 since activity is so low on CW during the weekday.

Does anyone know how I get my grid square to send when I call CQ or answer someone? When I call CQ it just sends CQ PJ4/KU8E in the standard messages.

I changed my station data in N1MM Logger Plus and in the WSJT-X window File>Settings> General I have PJ4/KU8E and FK52 for my grid square.

Thanks, Jeff  PJ4/KU8E