Win 10 and N1MM contesting -fustration!

  • 1
  • Question
  • Updated 3 years ago

N1MM contesting software loosing connection to the radio. I had N1MM all setup for 20m CQ WPX RTTY contest started on 20m ran for 6 hours no issues, then I wanted to change bands due to losing signals on 20 I QSY to 40m and all hell broke loose the N1mm software lost connection to the radio I could get it back by selecting retry and the radio would reconnect but garbage on the screen. For the next hour is kept loosing connection. Anyone has seen this?

Jim

WU5E


Photo of James Kennedy-WU5E

James Kennedy-WU5E

  • 338 Posts
  • 35 Reply Likes

Posted 3 years ago

  • 1
Photo of K3DCW

K3DCW

  • 95 Posts
  • 36 Reply Likes
Sounds to me like RF is getting into your system on 40m.
Photo of James Kennedy-WU5E

James Kennedy-WU5E

  • 338 Posts
  • 35 Reply Likes

nope that is not it. - I never able to transmit after change from 20m 40m after selection of 40m about 30 second later the radio lost connection  to the com port. I would try several different comports to no avail. SO you suggestion of RF is silly. rethink that.

I would reboot N1MM and reboot the computer. To No avail. This is a issue of the Digital interface connection to the radio.  The alert I see is N1MM logger has lost communication Radio 1  ( Radio 1 Flex 6000 Series on Com 5 is nor responding.

I don't know why the 20m lasted for 6 hours before I change bands. This is a problem.


Jim

WU5E


Photo of K3DCW

K3DCW

  • 95 Posts
  • 36 Reply Likes
Well, if you had provided all of that information in your initial post; especially the part about not transmitting on 40 and the drops starting immediately, my response might have been different. 

However, thanks for calling the suggestion from someone who's trying to help "silly."  The only thing I'll "rethink" is trying to help you in the future.  In the meantime, you may want to take some time away from the contest and spend a bit of time reading this:

Photo of James Kennedy-WU5E

James Kennedy-WU5E

  • 338 Posts
  • 35 Reply Likes
nope that's not it
Photo of Kevin

Kevin

  • 931 Posts
  • 271 Reply Likes
Been running N1MM on 20, 40 and 80 with RTTY at 100 watts. Only problem I'm having is hitting the wrong buttons (I need a lot of practice). So far, no connectivity problems.
Photo of Paul Mandel

Paul Mandel

  • 83 Posts
  • 21 Reply Likes
I had a similar issue with my 6500 but with W7.   My setup that worked in the past would not connect to the radio. The display on N1MM said Manual.   I tried everything including clearing the ini file but I could never get ti to connect.  Other programs work fine but not N1MM+ 
Photo of James Kennedy-WU5E

James Kennedy-WU5E

  • 338 Posts
  • 35 Reply Likes
here more info.
N1MMLogger.net - Version 1.0.6059.0



   at N1MMLogger.Net.My.MyApplication.Main(String[] Args) in 17d14f5c-a337-4978-8281-53493378c1071.vb:line 82   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)   at RawInput_dll.RawInput.WndProc(Message& message)   at System.Windows.Forms.NativeWindow.WndProc(Message& m)   at System.Windows.Forms.NativeWindow.DefWndProc(Message& m)   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)   at System.Windows.Forms.Form.WndProc(Message& m)   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)   at System.Windows.Forms.Control.WndProc(Message& m)   at System.Windows.Forms.Control.InvokeMarshaledCallbacks()   at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)   at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)   at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)   at System.Delegate.DynamicInvokeImpl(Object[] args)   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)   at N1MMLogger.Net.EntryWindow.HandleSerialMessage(Byte[] arr) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\EntryWindow.vb:line 17705   at N1MMLogger.Net.CWIFInterfaceClass.HandleMessage(Object& data) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\CWIFInterface.vb:line 540   at N1MMLogger.Net.CWIFInterfaceClass.HandleNonXMLMessage(Object& data, String& aStr) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\CWIFInterface.vb:line 574   at N1MMLogger.Net.EntryWindow.CWIFInt_ReceivedCommData(Int32 PortNum) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\EntryWindow.vb:line 17773   at N1MMLogger.Net.DigitalInterface.OnComm(Int16 Intnr) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\DigitalInterface.vb:line 6016   at N1MMLogger.Net.DigitalProcessing.RxComData(String sMsg, Int32 Index) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\DigitalProcessing.vb:line 740   at N1MMLogger.Net.DigitalProcessing.PrintToRxWindow(String sMsg, Int32 Index) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\DigitalProcessing.vb:line 601   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 211   at N1MMLibrary.SharedLib.CallStackString() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Library\Classes\SharedCode.vb:line 58   at System.Environment.get_StackTrace()Call Stack before the runtime error:   at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)---------------------------------------------------------------------------------------   at N1MMLogger.Net.DigitalProcessing.PrintToRxWindow(String sMsg, Int32 Index) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\DigitalProcessing.vb:line 507   at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateGet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack)   at Microsoft.VisualBasic.CompilerServices.Symbols.Container..ctor(Object Instance)System.NullReferenceException: Object variable or With block variable not set.---------------------------------------------------------------------------------------Error occurred at: 2/12/2017 4:51:52 PM in Thread: Microsoft Windows NT 10.0.10586.0,64:1,en-US,en-USBuilt: 2/8/2017 5:49:42 AMN1MMLogger.net - Version 1.0.6059.0



This the error I got.

Jim
wu5e
Photo of Michael Coslo

Michael Coslo

  • 947 Posts
  • 259 Reply Likes
Why do people get upset and call people names who are just trying to help? This whole issue here has become complicated all out of need. Please take this in the spirit in which it is offered, hopefully I am not being stupid or silly. This is what I do:

Toroids on all entrances and exits on the radio and computer. High quality Cat 5 cable is used as well.  This, even if it does not cure your present problem, will probably stop problems down the road.  That router almost certainly has some oscillators that can be affected by RF. As well, the occasional issue crops up in the system or Program software with RF. 

At this time, I would also save my profiles, revo uninstall N1MM and SSDR, and start over.