Date   

Re: WSJT-X / N1MM+ with FT-857D

Don R
 

Thanks Rich, the settings look right but they just don't want to work together.

Don


On 11/22/2020 7:59 AM, ve3ki wrote:
One of your settings is wrong.

Go to <https://n1mmwp.hamdocs.com/manual-windows/wsjt-x-decode-list-window/>. Look at the first screen shot image on that page, and in particular at the uppermost of the three red boxes. In N1MM+, with everything in either CW or SSB mode (WSJT-X not running), open the Configurer and select the WSJT/JTDX Setup tab. Make sure that in your configuration your IP Address and UDP Port are the same as shown there, and that the Enable check box is checked.

After closing the Configurer, if you made any changes to the settings above, close down N1MM+ and restart it. Now make sure that rig control works from N1MM+. When you type a frequency in kHz (like 14070) into the Entry window's call sign box, the rig's frequency should change to match.

Once that is all working, open WSJT-X from N1MM+ by typing FT8 into the call sign box and pressing Enter. Open the WSJT-X Settings window and select the Reporting tab. Just over halfway down the window, in the area called "UDP Server", make sure the "Accept UDP requests" check box is checked. The UDP Server IP address and port number should match the ones shown in the third screen shot image on the web page I referred to above.

After closing the Settings window, the communications between the two programs should now be working. If not, go back to the web page I referred to above and go through all of your settings step by step.

73,
Rich VE3KI




On Sun, Nov 22, 2020 at 08:37 AM, <donmar1234@...> wrote:
I had this setup working for FT-8 several months ago but it won't work, now.  Today, I uninstalled both programs and downloaded the latest versions of both.  Independently, both programs are working, i.e., rig control and signal decoding.  However, I can not get WSJT-X to startup properly or control the rig from within N1MM+.

1) Open N1MM+, type FT8 in the callsign field.
2) After about 15 seconds WSJT-X opens, no spectrum display or signal decoding.
3) If I click on the Band dropdown and select a frequency, the spectrum display begins working and signals are decoded.
The Circle for CAT control next to the Band is Orange at first and later turns Red.  The frequency display is 0.000 000.  After several minutes, the WSJT-X Rig Control Error pops up.
WSJT-X is set to: DX Lab Suite Commander, N1MM+ is set to Yaesu FT-857 Com3.

I've ran out of ideas, is this an N1MM+ or WSJT-X issue (or both)?

73,
Don / KW7R


Re: N1MM+ changes IC-7300 filter bandwidth when using the band buttons in the Entry window

Gerd DK8NT
 

Correction:

 

Again (@N1MM+ coding team…), for my part, I’d prefer that N1MM+ won’t change my radio’s filter unless I explicitly wish it (by clicking the Wide or Narrow buttons in the bandmap’s context menu).

 

should read:

 

Again (@N1MM+ coding team…), for my part, I’d prefer that N1MM+ won’t change my radio’s filter unless I explicitly wish it (by clicking the Wide or Narrow buttons in the bandmap).

 

Sorry!

 

 

Von: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] Im Auftrag von Gerd DK8NT
Gesendet: Sonntag, 22. November 2020 21:09
An: N1MMLoggerPlus@groups.io
Cc: 'Rick Ellison'
Betreff: Re: [N1MM+] N1MM+ changes IC-7300 filter bandwidth when using the band buttons in the Entry window

 

Nooo worries, Rick! And I‘m bringing the thread back into the group now.

 

In the full radio manual I now found the (many) CAT command tables. Thanks!

What a jungle … but I managed to gain some insight and tried to resolve the issues I raised in my previous message (further down):

 

·         In the bandmap command set “Set transceiver Filter Codes”, the “Wide” commands all point to FIL1, the “Narrow” ones point to FIL2. This more or less matches ICOM’s default settings (FIL1 = wide, FIL2 = medium, FIL3 = narrow), but the really narrow FIL3 isn’t selectable. (I guess older ICOMs had only two widths?)

·         However, when I click the bandmap button “Wide”, my radio goes to FIL2 (and displays the “Nar” button).
And clicking “Nar” switches to FIL1 (and displays the “Wide” button).
This means that the N1MM documentation is WRONG here (on https://n1mmwp.hamdocs.com/manual-windows/bandmap-window/) saying “The second [button] toggles between wide and narrow filter settings, always displaying the one that will be selected next if it is clicked.”
Instead, it should read something like: “The second [button] toggles between wide and narrow filter settings, always displaying the one that is currently selected.”

·         Again (@N1MM+ coding team…), for my part, I’d prefer that N1MM+ won’t change my radio’s filter unless I explicitly wish it (by clicking the Wide or Narrow buttons in the bandmap’s context menu).
As mentioned, changing bands via a click on a call in the Available window, or via Ctrl+Up/Dn, both do NOT change the filter in the radio (this is as I like it) – only a click on a band button in the Entry window does (and always switches to FIL2)!
(This is also the wish of Goetz DJ3IW’s post “[N1MM+] N1MM+ band change button changes ICOM filter selection” today.)

 

Hope that together we’ve almost reached the bottom of this thread – and that the documentation and the Entry window’s band button behavior will be corrected ;-)).

 

73, Gerd DK8NT

 

 

Von: Rick Ellison [mailto:rellison@...]
Gesendet: Sonntag, 22. November 2020 19:49
An: 'Gerd Ballenberger'
Betreff: RE: [N1MM+] N1MM+ changes IC-7300 filter bandwidth when using the band buttons in the Entry window

 

Hi Gerd..

Sorry for not getting back to you.

You should be able to look in the7300 manual where it lists all of the CAT commands and find the code that is needed. Mine are the default ones that N1MM selected when it loads the radio. I though mine went to the #3 filter but looking it only has 1 and 2 setup.

 

73 Rick N2AMG

 

From: Gerd Ballenberger [mailto:gerd.ballenberger@...]
Sent: Saturday, November 21, 2020 10:29 AM
To: 'Rick Ellison' <rellison@...>
Subject: AW: [N1MM+] N1MM+ changes IC-7300 filter bandwidth when using the band buttons in the Entry window

 

Hi Rick,

 

you complicate my world view ;-))

 

I’ve never noticed the Wide/Nar button in the Bandmap, nor the “Set Transceiver Filter Codes” command in the Bandmap’s context menu! But OK, some users may like it.

 

For my part, I’d prefer that N1MM+ won’t change my radio’s filter if I don’t explicitly wish it.

As mentioned, changing bands via a click on a call in the Available window, or via Ctrl+Up/Dn, both do NOT change the filter in the radio (this is as I like it) – only a click on a band button in the Entry window does!

 

If “The second [button] toggles between wide and narrow filter settings, always displaying the one that will be selected next if it is clicked.” (on https://n1mmwp.hamdocs.com/manual-windows/bandmap-window/) is true, then on my radio Wide à FIL2, and Nar à FIL1 – which contradicts the default sequence as described in the IC-7300 manual (FIL1 = broad, FIL2 medium, FIL3 narrow) …

 

Should you finally convince me to use the Wide/Nar button, how would I find out (or confirm) the hex radio commands for the IC-7300 and its three filters FIL1/2/3?

 

Sorry that this initially small issue is now escalating ;-))

 

73, Gerd DK8NT

 

 

Hi Gerd..

When I posted that I had not looked at the sourcecode to see the workings. N1MM always defaults to the Wide filter selection and clicking on the button switches to the narrow. If you right click on the button about halfway down the menu there is a place to set the CAT codes for the filter you want to use for all 3 modes wide and narrow selections. On mine right now everything is set to use Filter1 for Wide and Filter2 for narrow. Except in RTTY I have the narrow filter change to Filter #3.

 

73 Rick N2AMG

_

 

Das Bild wurde vom Absender entfernt.

Virus-free. www.avast.com

 


Re: N1MM+ changes IC-7300 filter bandwidth when using the band buttons in the Entry window

Gerd DK8NT
 

Nooo worries, Rick! And I‘m bringing the thread back into the group now.

 

In the full radio manual I now found the (many) CAT command tables. Thanks!

What a jungle … but I managed to gain some insight and tried to resolve the issues I raised in my previous message (further down):

 

·         In the bandmap command set “Set transceiver Filter Codes”, the “Wide” commands all point to FIL1, the “Narrow” ones point to FIL2. This more or less matches ICOM’s default settings (FIL1 = wide, FIL2 = medium, FIL3 = narrow), but the really narrow FIL3 isn’t selectable. (I guess older ICOMs had only two widths?)

·         However, when I click the bandmap button “Wide”, my radio goes to FIL2 (and displays the “Nar” button).
And clicking “Nar” switches to FIL1 (and displays the “Wide” button).
This means that the N1MM documentation is WRONG here (
on https://n1mmwp.hamdocs.com/manual-windows/bandmap-window/) saying “The second [button] toggles between wide and narrow filter settings, always displaying the one that will be selected next if it is clicked.”
Instead, it should read something like: “The second [button] toggles between wide and narrow filter settings, always displaying the one that is currently selected.”

·         Again (@N1MM+ coding team…), for my part, I’d prefer that N1MM+ won’t change my radio’s filter unless I explicitly wish it (by clicking the Wide or Narrow buttons in the bandmap’s context menu).
As mentioned, changing bands via a click on a call in the Available window, or via Ctrl+Up/Dn, both do NOT change the filter in the radio (this is as I like it) – only a click on a band button in the Entry window does (and always switches to FIL2)!
(This is also the wish of Goetz DJ3IW’s post “[N1MM+] N1MM+ band change button changes ICOM filter selection” today.)

 

Hope that together we’ve almost reached the bottom of this thread – and that the documentation and the Entry window’s band button behavior will be corrected ;-)).

 

73, Gerd DK8NT

 

 

Von: Rick Ellison [mailto:rellison@...]
Gesendet: Sonntag, 22. November 2020 19:49
An: 'Gerd Ballenberger'
Betreff: RE: [N1MM+] N1MM+ changes IC-7300 filter bandwidth when using the band buttons in the Entry window

 

Hi Gerd..

Sorry for not getting back to you.

You should be able to look in the7300 manual where it lists all of the CAT commands and find the code that is needed. Mine are the default ones that N1MM selected when it loads the radio. I though mine went to the #3 filter but looking it only has 1 and 2 setup.

 

73 Rick N2AMG

 

From: Gerd Ballenberger [mailto:gerd.ballenberger@...]
Sent: Saturday, November 21, 2020 10:29 AM
To: 'Rick Ellison' <rellison@...>
Subject: AW: [N1MM+] N1MM+ changes IC-7300 filter bandwidth when using the band buttons in the Entry window

 

Hi Rick,

 

you complicate my world view ;-))

 

I’ve never noticed the Wide/Nar button in the Bandmap, nor the “Set Transceiver Filter Codes” command in the Bandmap’s context menu! But OK, some users may like it.

 

For my part, I’d prefer that N1MM+ won’t change my radio’s filter if I don’t explicitly wish it.

As mentioned, changing bands via a click on a call in the Available window, or via Ctrl+Up/Dn, both do NOT change the filter in the radio (this is as I like it) – only a click on a band button in the Entry window does!

 

If “The second [button] toggles between wide and narrow filter settings, always displaying the one that will be selected next if it is clicked.” (on https://n1mmwp.hamdocs.com/manual-windows/bandmap-window/) is true, then on my radio Wide à FIL2, and Nar à FIL1 – which contradicts the default sequence as described in the IC-7300 manual (FIL1 = broad, FIL2 medium, FIL3 narrow) …

 

Should you finally convince me to use the Wide/Nar button, how would I find out (or confirm) the hex radio commands for the IC-7300 and its three filters FIL1/2/3?

 

Sorry that this initially small issue is now escalating ;-))

 

73, Gerd DK8NT

 

 

Hi Gerd..

When I posted that I had not looked at the sourcecode to see the workings. N1MM always defaults to the Wide filter selection and clicking on the button switches to the narrow. If you right click on the button about halfway down the menu there is a place to set the CAT codes for the filter you want to use for all 3 modes wide and narrow selections. On mine right now everything is set to use Filter1 for Wide and Filter2 for narrow. Except in RTTY I have the narrow filter change to Filter #3.

 

73 Rick N2AMG

_

 

Das Bild wurde vom Absender entfernt.

Virus-free. www.avast.com

 


Re: F2 Msg Exch #n1mm

Gilles DESANSAC F6IRA
 

Off course Dr Watson !!! I was imagine that  #  label was for all predefine contest model depending zones or progressives numbers. Thanks so much Mike and other for lights and kind assistance. My fake resolved. Sorry for bandwith. Gilles F6IRA


Re: F2 Msg Exch #n1mm

VE9AA - Mike
 

# = serial number.( As Rich has said)
I believe in your contest setup dialog you should put in your ITU zone. THATS why you are seeing a serial number I think.

I am not near a computer to test, sorry.
--
CU (all of a sudden) in the next one.
Mike VE9AA


Re: Updated - Now N1MMLogger+ will not start

Joseph Giasi
 

Tom,

 

Thanks for the reply. I just took the following steps:

 

  1. Uninstalled Logger and deleted the program folder (only file in data folder is LogError.txt, so I left that as is)
  2. Disabled virus protection (Webroot SecureAnywhere)
  3. Ran full installer (1.0.8501) as administrator
  4. Rebooted computer
  5. Disabled virus protection again
  6. Ran update .8730 as administrator

 

When install finished, the readme file and then the same error popped up.

 

Nothing is being written to the folder in Documents except LogError.txt. Should there be files in that folder from the full install?

 

Is it possible to manually start the .ocx before running installing the update?

 

Should I try to install an older version? The program ran without any problem back in August.

 

Joe, W2QQ

 


Re: F2 Msg Exch #n1mm

Gilles DESANSAC F6IRA
 

Ooops sorry Mike and all. Yes it is an  # into Set Exchange field into contest log in database. From long time i have this strange behavior into my contest computer and perhaps alone because others French's friends reports by PM there not have this thing on their configuration . Strange but however as I know this point wiil check manualy Zone into macros fields when I need. Thanks for your help sorry for my sad english.


Re: F2 Msg Exch #n1mm

VE9AA - Mike
 

Gilles

I don't think you answered Richs first question.

CONTEST SETUP DIALOG...( NOT function keys)


On Sun, Nov 22, 2020 at 10:39 AM, ve3ki wrote:
Is there a # character in the Sent Exchange box in your contest setup dialog? That will cause the {EXCH} macro to send a serial number. Also, if there is a # character in your F2 message, that will send a serial number regardless of what is in the Sent Exchange box.

 
--
CU (all of a sudden) in the next one.
Mike VE9AA


Re: F2 Msg Exch #n1mm

Gilles DESANSAC F6IRA
 

Hi Rich it is my macro text (before change  {EXCH} by 27). Thanks for your help Gilles F6IRA
#
# CW Function Key File
#
# This file can be used in most CW contests that have a simple exchange
# The {EXCH} macro uses the contents of the Sent Exchange box in the contest setup
# The {SENTRSTCUT} defaults to 5NN. If you want to send another signal report,
#  change the Sent RST in the Entry Window before transmitting your exchange.
#
# F5 uses "!" macro for his callsign
# Do not use the {CALL} macro in place of the ! macro
#
# S&P F1 calls QRL? before placing the program in RUN mode for calling CQ
# To respond to caller, send F5 then F2, or ; (default exchange key) or
#   Insert, or Enter in ESM
#
###################
#   RUN Messages
# msg F2 original Exch, {SENTRSTCUT} {EXCH}
###################
F1 Cq,Cq {MYCALL} lz<<<<<<test>>>>>>
F2 Exch,{SENTRSTCUT} {EXCH}
F3 Tu,Tu {MYCALL}
F4 my,{MYCALL}
F5 His Call,!
F6 TNX,TNX
F7 ?,?
F8 AGN,AGN
F9 QSOB4,QSO B4
F10 Call?,Cl?
F11 Wipe,{WIPE}
F12 Efface,{WIPE}
#
###################
#   S&P Messages
###################
F1 CQ,Cq {MYCALL}  lz<<<<<<test>>>>>>
F2 Exch,{SENTRSTCUT} {EXCH}
F3 Tu,Tu
F4 {MYCALL},{MYCALL}
F5 His Call,!
F6 TNX,TNX
F7 ?,?
F8 ?,?
F9 Nr?,Nr?
F10 Call?,Cl?
F11 Wipe,{WIPE}
F12 Efface,{WIPE}


Re: Updated - Now N1MMLogger+ will not start

Tom Wagner (N1MM)
 

Your install is failing trying to initialize an .OCX file.  Please try running the full installer as administrator and also run the update as administrator.

It would be worthwhile to turn off virus protection while doing this. If you could the reinstall with virus protection on and then off, that would be useful information to us.

Tom - N1MM

On 11/22/2020 10:26 AM, jpgw2qq@... wrote:
Yikes!

I've been running N1MMLogger for years (ran classic before +), without any problems, but have now encountered an issue that prevents the program from even opening.

I am running Windows 10 64 bit, updated to most recent release. 32GB RAM and a 1TB SSD.

Last ran the program in August. Program and data files are installed locally in their default locations (data folder is in Documents) and no prior issues writing or reading to the data files. When I went to open N1MM yesterday, I received a message that the program was more than 30 days old and should be updated. Unusually, the program would not open (ie, I couldn't update from within the program) so I downloaded the most recent version (.8730) and installed it. After the readme appeared, the following error message came up:

Thread # 1 @ 2020-11-22 14:48:20.415 PM
  N1MMLogger.net - Version 1.0.8730.0
Built: 11/17/2020 5:00:10 AM
Microsoft Windows NT 10.0.19042.0,64:1,en-US,en-US
Error occurred at: 11/22/2020 9:48:20 AM in Thread:
---------------------------------------------------------------------------------------
System.InvalidOperationException: An error occurred creating the form. See Exception.InnerException for details.  The error is: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. ---> System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at System.Windows.Forms.UnsafeNativeMethods.CoCreateInstance(Guid& clsid, Object punkOuter, Int32 context, Guid& iid)
   at System.Windows.Forms.AxHost.CreateWithLicense(String license, Guid clsid)
   at System.Windows.Forms.AxHost.CreateInstanceCore(Guid clsid)
   at System.Windows.Forms.AxHost.CreateInstance()
   at System.Windows.Forms.AxHost.GetOcxCreate()
   at System.Windows.Forms.AxHost.TransitionUpTo(Int32 state)
   at System.Windows.Forms.AxHost.CreateHandle()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.AxHost.EndInit()
   at N1MMLogger.Net.EntryWindow.InitializeComponent() in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\Forms\EntryWindow.Designer.vb:line 3485
   at N1MMLogger.Net.EntryWindow..ctor() in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\Forms\EntryWindow.vb:line 639
   --- End of inner exception stack trace ---
   at N1MMLogger.Net.My.MyProject.MyForms.Create__Instance__[T](T Instance) in :line 190
   at N1MMLogger.Net.My.MyApplication.OnCreateMainForm() in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\My Project\Application.Designer.vb:line 183
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
---------------------------------------------------------------------------------------
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at System.Windows.Forms.UnsafeNativeMethods.CoCreateInstance(Guid& clsid, Object punkOuter, Int32 context, Guid& iid)
   at System.Windows.Forms.AxHost.CreateWithLicense(String license, Guid clsid)
   at System.Windows.Forms.AxHost.CreateInstanceCore(Guid clsid)
   at System.Windows.Forms.AxHost.CreateInstance()
   at System.Windows.Forms.AxHost.GetOcxCreate()
   at System.Windows.Forms.AxHost.TransitionUpTo(Int32 state)
   at System.Windows.Forms.AxHost.CreateHandle()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.AxHost.EndInit()
   at N1MMLogger.Net.EntryWindow.InitializeComponent() in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\Forms\EntryWindow.Designer.vb:line 3485
   at N1MMLogger.Net.EntryWindow..ctor() in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\Forms\EntryWindow.vb:line 639
---------------------------------------------------------------------------------------
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:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Library\Classes\SharedCode.vb:line 91
   at N1MMLogger.Net.SharedCode.HandleError(Exception e, String PortName, String Info, String additionalInfoForLogFile) in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\Modules\SharedCode.vb:line 213
   at N1MMLogger.Net.My.MyApplication.MyApplication_UnhandledException(Object sender, UnhandledExceptionEventArgs e) in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\ApplicationEvents.vb:line 14
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.raise_UnhandledException(Object sender, UnhandledExceptionEventArgs e)
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnUnhandledException(UnhandledExceptionEventArgs e)
   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

The error message suggests possible corrupt memory, so I ran a Windows diagnostic memory test, but it reported that there are no issues with any of the installed memory.

I tried uninstalling and reinstalling the program (moved all the data files to a backup folder and removed the N1MM data folder). After running the full installer and the most recent update (ran both as administrator), I receive the same error message and the only file written to the data folder is LogError.txt.

I'm guessing that a recent Windows update may have added some unwanted protection to the Documents folder, but I don't see anyone else experiencing the same problem. Otherwise, I have no idea as to how to get the program up and running again.

Does anyone have any ideas that may get me running the logger again?

Joe, W2QQ


Re: New Morserunner mode fully integrated in latest N1MM+ versions

DD5XX
 

anyone?


Updated - Now N1MMLogger+ will not start

Joseph Giasi
 

Yikes!

I've been running N1MMLogger for years (ran classic before +), without any problems, but have now encountered an issue that prevents the program from even opening.

I am running Windows 10 64 bit, updated to most recent release. 32GB RAM and a 1TB SSD.

Last ran the program in August. Program and data files are installed locally in their default locations (data folder is in Documents) and no prior issues writing or reading to the data files. When I went to open N1MM yesterday, I received a message that the program was more than 30 days old and should be updated. Unusually, the program would not open (ie, I couldn't update from within the program) so I downloaded the most recent version (.8730) and installed it. After the readme appeared, the following error message came up:

Thread # 1 @ 2020-11-22 14:48:20.415 PM
  N1MMLogger.net - Version 1.0.8730.0
Built: 11/17/2020 5:00:10 AM
Microsoft Windows NT 10.0.19042.0,64:1,en-US,en-US
Error occurred at: 11/22/2020 9:48:20 AM in Thread: 
---------------------------------------------------------------------------------------
System.InvalidOperationException: An error occurred creating the form. See Exception.InnerException for details.  The error is: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. ---> System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at System.Windows.Forms.UnsafeNativeMethods.CoCreateInstance(Guid& clsid, Object punkOuter, Int32 context, Guid& iid)
   at System.Windows.Forms.AxHost.CreateWithLicense(String license, Guid clsid)
   at System.Windows.Forms.AxHost.CreateInstanceCore(Guid clsid)
   at System.Windows.Forms.AxHost.CreateInstance()
   at System.Windows.Forms.AxHost.GetOcxCreate()
   at System.Windows.Forms.AxHost.TransitionUpTo(Int32 state)
   at System.Windows.Forms.AxHost.CreateHandle()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.AxHost.EndInit()
   at N1MMLogger.Net.EntryWindow.InitializeComponent() in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\Forms\EntryWindow.Designer.vb:line 3485
   at N1MMLogger.Net.EntryWindow..ctor() in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\Forms\EntryWindow.vb:line 639
   --- End of inner exception stack trace ---
   at N1MMLogger.Net.My.MyProject.MyForms.Create__Instance__[T](T Instance) in :line 190
   at N1MMLogger.Net.My.MyApplication.OnCreateMainForm() in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\My Project\Application.Designer.vb:line 183
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
---------------------------------------------------------------------------------------
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at System.Windows.Forms.UnsafeNativeMethods.CoCreateInstance(Guid& clsid, Object punkOuter, Int32 context, Guid& iid)
   at System.Windows.Forms.AxHost.CreateWithLicense(String license, Guid clsid)
   at System.Windows.Forms.AxHost.CreateInstanceCore(Guid clsid)
   at System.Windows.Forms.AxHost.CreateInstance()
   at System.Windows.Forms.AxHost.GetOcxCreate()
   at System.Windows.Forms.AxHost.TransitionUpTo(Int32 state)
   at System.Windows.Forms.AxHost.CreateHandle()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.AxHost.EndInit()
   at N1MMLogger.Net.EntryWindow.InitializeComponent() in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\Forms\EntryWindow.Designer.vb:line 3485
   at N1MMLogger.Net.EntryWindow..ctor() in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\Forms\EntryWindow.vb:line 639
---------------------------------------------------------------------------------------
 
 
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:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Library\Classes\SharedCode.vb:line 91
   at N1MMLogger.Net.SharedCode.HandleError(Exception e, String PortName, String Info, String additionalInfoForLogFile) in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\Modules\SharedCode.vb:line 213
   at N1MMLogger.Net.My.MyApplication.MyApplication_UnhandledException(Object sender, UnhandledExceptionEventArgs e) in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\ApplicationEvents.vb:line 14
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.raise_UnhandledException(Object sender, UnhandledExceptionEventArgs e)
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnUnhandledException(UnhandledExceptionEventArgs e)
   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

The error message suggests possible corrupt memory, so I ran a Windows diagnostic memory test, but it reported that there are no issues with any of the installed memory.

I tried uninstalling and reinstalling the program (moved all the data files to a backup folder and removed the N1MM data folder). After running the full installer and the most recent update (ran both as administrator), I receive the same error message and the only file written to the data folder is LogError.txt.

I'm guessing that a recent Windows update may have added some unwanted protection to the Documents folder, but I don't see anyone else experiencing the same problem. Otherwise, I have no idea as to how to get the program up and running again.

Does anyone have any ideas that may get me running the logger again?

Joe, W2QQ


Re: F2 Msg Exch #n1mm

ve3ki
 

Is there a # character in the Sent Exchange box in your contest setup dialog? That will cause the {EXCH} macro to send a serial number. Also, if there is a # character in your F2 message, that will send a serial number regardless of what is in the Sent Exchange box.

73,
Rich VE3KI


On Sun, Nov 22, 2020 at 09:15 AM, Gilles DESANSAC F6IRA wrote:
Hi Timon. I've try ctrl O without no more sucess. I not to sure if  I delete and create new .ini file will be an good idea because except {EXCH} all my setup configuration is OK and work fine. Just before contest start i do as Robert N7WY write on his help message ( I'll do like that each time where contests rules need fixed zone instead progressive numbers) Perhaps some give good idea where will need to fix move eyes to fix the behavior. Thanks to all for help. Gilles F6IRA


Re: F2 Msg Exch #n1mm

Gilles DESANSAC F6IRA
 
Edited

Hi Timon. I've try ctrl O without no more sucess. I not to sure if  I delete and create new .ini file will be an good idea because except {EXCH} all my setup configuration is OK and work fine. Just before contest start i do as Robert N7WY write on his help message ( I'll do like that each time where contests rules need fixed zone instead progressive numbers) Perhaps some give good idea where will need to fix move eyes to fix the behavior. Thanks to all for help. Gilles F6IRA


Re: WSJT-X / N1MM+ with FT-857D

ve3ki
 

One of your settings is wrong.

Go to <https://n1mmwp.hamdocs.com/manual-windows/wsjt-x-decode-list-window/>. Look at the first screen shot image on that page, and in particular at the uppermost of the three red boxes. In N1MM+, with everything in either CW or SSB mode (WSJT-X not running), open the Configurer and select the WSJT/JTDX Setup tab. Make sure that in your configuration your IP Address and UDP Port are the same as shown there, and that the Enable check box is checked.

After closing the Configurer, if you made any changes to the settings above, close down N1MM+ and restart it. Now make sure that rig control works from N1MM+. When you type a frequency in kHz (like 14070) into the Entry window's call sign box, the rig's frequency should change to match.

Once that is all working, open WSJT-X from N1MM+ by typing FT8 into the call sign box and pressing Enter. Open the WSJT-X Settings window and select the Reporting tab. Just over halfway down the window, in the area called "UDP Server", make sure the "Accept UDP requests" check box is checked. The UDP Server IP address and port number should match the ones shown in the third screen shot image on the web page I referred to above.

After closing the Settings window, the communications between the two programs should now be working. If not, go back to the web page I referred to above and go through all of your settings step by step.

73,
Rich VE3KI




On Sun, Nov 22, 2020 at 08:37 AM, <donmar1234@...> wrote:
I had this setup working for FT-8 several months ago but it won't work, now.  Today, I uninstalled both programs and downloaded the latest versions of both.  Independently, both programs are working, i.e., rig control and signal decoding.  However, I can not get WSJT-X to startup properly or control the rig from within N1MM+.

1) Open N1MM+, type FT8 in the callsign field.
2) After about 15 seconds WSJT-X opens, no spectrum display or signal decoding.
3) If I click on the Band dropdown and select a frequency, the spectrum display begins working and signals are decoded.
The Circle for CAT control next to the Band is Orange at first and later turns Red.  The frequency display is 0.000 000.  After several minutes, the WSJT-X Rig Control Error pops up.
WSJT-X is set to: DX Lab Suite Commander, N1MM+ is set to Yaesu FT-857 Com3.

I've ran out of ideas, is this an N1MM+ or WSJT-X issue (or both)?

73,
Don / KW7R


Re: WSJT-X / N1MM+ with FT-857D

Rick Ellison
 

In the main N1MM config on the WSJT/JTDX tab do you have the Path and port numbers configured correctly?? My guess either in N1MM or WSJT you do not have the correct ports setup properly. When N1MM loads WSJT a TCP connection is started between the two programs. Since you do not get a green circle in WSJT the TCP connection is failing. If you send me screen shots of the N1MM WSJT tab and the Radio and reporting tabs in WSJT I should be able to tell you where your issue is. Send them directly to rellison@....

 

73 Rick N2AMG

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of donmar1234 via groups.io
Sent: Saturday, November 21, 2020 11:23 PM
To: N1MMLoggerPlus@groups.io
Subject: [N1MM+] WSJT-X / N1MM+ with FT-857D

 

I had this setup working for FT-8 several months ago but it won't work, now.  Today, I uninstalled both programs and downloaded the latest versions of both.  Independently, both programs are working, i.e., rig control and signal decoding.  However, I can not get WSJT-X to startup properly or control the rig from within N1MM+.

1) Open N1MM+, type FT8 in the callsign field.
2) After about 15 seconds WSJT-X opens, no spectrum display or signal decoding.
3) If I click on the Band dropdown and select a frequency, the spectrum display begins working and signals are decoded.
The Circle for CAT control next to the Band is Orange at first and later turns Red.  The frequency display is 0.000 000.  After several minutes, the WSJT-X Rig Control Error pops up.
WSJT-X is set to: DX Lab Suite Commander, N1MM+ is set to Yaesu FT-857 Com3.

I've ran out of ideas, is this an N1MM+ or WSJT-X issue (or both)?

73,
Don / KW7R


Virus-free. www.avast.com


WSJT-X / N1MM+ with FT-857D

Don R
 

I had this setup working for FT-8 several months ago but it won't work, now.  Today, I uninstalled both programs and downloaded the latest versions of both.  Independently, both programs are working, i.e., rig control and signal decoding.  However, I can not get WSJT-X to startup properly or control the rig from within N1MM+.

1) Open N1MM+, type FT8 in the callsign field.
2) After about 15 seconds WSJT-X opens, no spectrum display or signal decoding.
3) If I click on the Band dropdown and select a frequency, the spectrum display begins working and signals are decoded.
The Circle for CAT control next to the Band is Orange at first and later turns Red.  The frequency display is 0.000 000.  After several minutes, the WSJT-X Rig Control Error pops up.
WSJT-X is set to: DX Lab Suite Commander, N1MM+ is set to Yaesu FT-857 Com3.

I've ran out of ideas, is this an N1MM+ or WSJT-X issue (or both)?

73,
Don / KW7R


Wrong adif after LZ DX Contest #n1mm

EI6KW
 

All LZ districts abreviations went to itu zone in adif file, e.g:

<CALL:5>LZ1QN <QSO_DATE:8>20201121 <TIME_ON:6>120203 <TIME_OFF:6>120203 <ITUZ:2>BU
<CALL:4>LZ5Y <QSO_DATE:8>20201121 <TIME_ON:6>120729 <TIME_OFF:6>120729 <ITUZ:2>SZ

and so on.

Slav, EI6KW


Airspy failure(?)

Pete Smith
 

When I try to use the Spectrum Display, it starts fine, and when I connect to my Airspy HF+, it comes up briefly in my taskbar and then I get an unhandled exception with the following text:

************* Exception Text **************
System.ApplicationException: Device got disconnected
   at N1MMLogger.Net.SDRSharp.FrontEnds.SpyServer.SpyClient.Connect(String host, Int32 port) in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\Classes\AirspyInterface.vb:line 166
   at N1MMLogger.Net.SpectrumWindow.SpyConnect() in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 4252
   at N1MMLogger.Net.SpectrumWindow.ConnectSpy() in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 4229
   at N1MMLogger.Net.SpectrumWindow.AirspyConnect_Click(Object sender, EventArgs e) in C:\Users\micro\source\Workspaces\N1MM Logger on .NET\main\N1MM Logger.Net\Forms\SpectrumWindow.vb:line 4445
   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.4250.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
N1MMLogger.net
    Assembly Version: 1.0.8730.0
    Win32 Version: 1.0.8730
    CodeBase: file:///C:/Program%20Files%20(x86)/N1MM%20Logger+/N1MMLogger.net.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 14.8.4084.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.4200.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.4270.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

It looks like something with the spyserver.  Has anyone else seen this and (hopefully, he says) figured out how to cure it?

-- 
73, Pete N4ZR
Check out the Reverse Beacon Network 
at <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.


Re: Radio reconnect lag

ve3ki
 

It's not automatic, but there is a "Reset Radio" button at the bottom of the Bandmap window that appears when radio communications are lost. Or you can use the :Reset Radios" menu item in the right-click menu in the Bandmap window. Either one should be quicker than going through the Configurer.

73,
Rich VE3KI



On Sat, Nov 21, 2020 at 09:50 PM, Ignacy Misztal wrote:
When a radio turns off and on, N1MM+ loses CAT. Running "Configure ports.." makes CAT work again. But when that menu is clicked, it takes 5-20 s to for the "Configure ports..." window to show up. 

Is there any way for N1MM+ to do automatic reconnection?

Ignacy NO9E