Date   
Re: Can’t get fsk com port in mmtty to stick

Rick Ellison
 

The ports that you are using for keying in MMTTY are they configured in N1MM?? With MMTTY you need to configure the ports in MMTTY itself. Open each instance of MMTTY in stand alone mode(Go into each directory to run MMTTY and setup the PTT/FSK ports). Most of the time this will allow the port number to stay the same but MMTTY loads its PTT setting into a shared memory space, when one instance of MMTTY closes down it has a tendency to save the wrong port number. Most of the time it will be the last port that was loaded. Sometimes it has no issues at all. This has been a known issue since it's been used.

73 Rick N2AMG

-----Original Message-----
From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Jamie WW3S
Sent: Thursday, January 3, 2019 10:34 PM
To: N1MMLoggerPlus@groups.io
Subject: [N1MMLoggerPlus] Can’t get fsk com port in mmtty to stick

Have 2 copies of mmtty, c:\mmtty and c:\mmtty2....di1 is k3 and microkeyer set for com3, di2 is 7610 and extfsk via built in port on radio....worked fine in CQWW rtty, now, the ports keep jumping, I set one and it works, then set di2 and di1 now has the same setting?!?! I’ve tried closing the digi window once properly set to make it stick, but once I open di2, di1 changes from com3 to extfsk.....

Run Time

Les Elliott
 

When setting up for the WWPMC this popped up 4 times,
when I test-logged a mult, I had to use Task Manager to stop Logger

Les, G4OGB

N1MMLogger.net - Version 1.0.7422.0
Built: 1/1/2019 1:33:24 PM
Microsoft Windows NT 6.1.7601 Service Pack 1,64:0,en-GB,en-US
Error occurred at: 1/4/2019 1:45:23 PM in Thread:
---------------------------------------------------------------------------------------
System.ArgumentException: An entry with the same key already exists.
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.TreeSet`1.AddIfNotPresent(T item)
at System.Collections.Generic.SortedDictionary`2.Add(TKey key, TValue value)
at N1MMLogger.Net.SectionMults.ReadLabels() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\Multipliers.vb:line 2356
---------------------------------------------------------------------------------------


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 57
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 212
at N1MMLogger.Net.SectionMults.ReadLabels() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\Multipliers.vb:line 2364
at N1MMLogger.Net.MultsByBand.RefreshAll() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\Multipliers.vb:line 411
at N1MMLogger.Net.MultsByBand.stn_ContestChanged(Contest& c, Boolean& IsClearSerialNumbers) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\Multipliers.vb:line 295
at N1MMLogger.Net.StationClass.ContestChangedEventHandler.Invoke(Contest& c, Boolean& IsClearSerialNumbers)
at N1MMLogger.Net.StationClass.RaiseContestChanged(String aString, Int32 aNR) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Classes\Station.vb:line 736
at N1MMLogger.Net.LogTypeSelectionDialog.NewContestPressOK() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\LogTypeSelectionDialog.vb:line 835
at N1MMLogger.Net.LogTypeSelectionDialog.OKButton_Click(Object eventSender, EventArgs eventArgs) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\LogTypeSelectionDialog.vb:line 807
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
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)
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.RunDialog(Form form)
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
at System.Windows.Forms.Form.ShowDialog()
at N1MMLogger.Net.EntryWindow.SelectNewOrExistingContest() in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\EntryWindow.vb:line 6827
at N1MMLogger.Net.EntryWindow.mnuSetLogType_Click(Object sender, EventArgs e) in C:\N1MM+Source\N1MM Logger on .NET\N1MM Logger.Net\Forms\EntryWindow.vb:line 17510
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)
at N1MMLogger.Net.My.MyApplication.Main(String[] Args) in :line 82

Re: ARRL RTTY RU: FT8 means no Single Op UNassisted

Jamie WW3S
 

#2 is incorrect, you are eligible for certificates or plaques as single op assisted....I won a plaque as DX winner of SOLP assisted from VP9 a few years back.....


From: "John Kludt" <johnnykludt@...>
To: N1MMLoggerPlus@groups.io
Sent: Friday, January 4, 2019 8:18:37 AM
Subject: Re: [N1MMLoggerPlus] ARRL RTTY RU: FT8 means no Single Op UNassisted

Victor,

Agreed.  But I wonder and maybe we need to take this off line, I have the impression that many of the hardcore RTTY contest crowd run two decoders at once,  So while each decoder is only decoding one signal at a time, as the operator, they are reviewing more than one decoded signal at a time.  So they must have the same issue.

John

On Fri, Jan 4, 2019 at 1:32 AM Victor Paul <vmpaul@...> wrote:
With many planning on using both RTTY and FT8 in the ARRL RTTY RU this weekend, I thought I would highlight some rules quirks of which I was unaware until I actually read the rules carefully.  A couple of take aways that folks should be aware of:

1) If you use WSJT-X or similar FT8 software that decodes more than one signal at a time you CANNOT enter as Single Op UnAssisted.  Quoting from the rules:
"Since ARRL contest rules regarding spotting assistance prohibit the use of “automated, multi-channel decoders” by Single-Operator entrants, stations using software that decodes more than one FT8 signal at a time will have to enter as Single-Operator Unlimited or as Multioperator, just as PSK participants have had to do in the past when using fldigi or DigiPan software."

2) If you enter as Single Op Assisted, it appears that you will be ineligible for a certificate, no matter how high your score is.  Reading section 8 of the rules I see that there will be certificates for the highest scoring Single Op High and Low power  and MultiOp high and low power in each ARRL/RAC section, but I see nothing about any certs or plaques for Single Op Unlimited (i.e. Assisted).  That may not be the intent, but its how I read it.  If that really is the case, those entering in the hopes of some wall paper may want to enter in the MultiOp category (with the attendant band change limits) rather than Single Op Unlimited/Assisted.

Yes, I realize this topic isn't specifically germane to the N1MM+ software, but thought it worth mentioning here.  Read the rules at:
http://www.arrl.org/rtty-roundup

73,
Victor WB0TEV


Re: ARRL RTTY RU: FT8 means no Single Op UNassisted

Jamie WW3S
 

diffrence with multiple decoders is we are decoding the same signal...with FT8, you are decoding multiple signals within the passband.....there was a similiar RTTY one out there, decoded maybe 3khz, with multiple signals within that passband, but I dont remember the name of it....but, if you use it, you are correct, that puts you in unlimited category....


From: "John Kludt" <johnnykludt@...>
To: N1MMLoggerPlus@groups.io
Sent: Friday, January 4, 2019 8:18:37 AM
Subject: Re: [N1MMLoggerPlus] ARRL RTTY RU: FT8 means no Single Op UNassisted

Victor,

Agreed.  But I wonder and maybe we need to take this off line, I have the impression that many of the hardcore RTTY contest crowd run two decoders at once,  So while each decoder is only decoding one signal at a time, as the operator, they are reviewing more than one decoded signal at a time.  So they must have the same issue.

John

On Fri, Jan 4, 2019 at 1:32 AM Victor Paul <vmpaul@...> wrote:
With many planning on using both RTTY and FT8 in the ARRL RTTY RU this weekend, I thought I would highlight some rules quirks of which I was unaware until I actually read the rules carefully.  A couple of take aways that folks should be aware of:

1) If you use WSJT-X or similar FT8 software that decodes more than one signal at a time you CANNOT enter as Single Op UnAssisted.  Quoting from the rules:
"Since ARRL contest rules regarding spotting assistance prohibit the use of “automated, multi-channel decoders” by Single-Operator entrants, stations using software that decodes more than one FT8 signal at a time will have to enter as Single-Operator Unlimited or as Multioperator, just as PSK participants have had to do in the past when using fldigi or DigiPan software."

2) If you enter as Single Op Assisted, it appears that you will be ineligible for a certificate, no matter how high your score is.  Reading section 8 of the rules I see that there will be certificates for the highest scoring Single Op High and Low power  and MultiOp high and low power in each ARRL/RAC section, but I see nothing about any certs or plaques for Single Op Unlimited (i.e. Assisted).  That may not be the intent, but its how I read it.  If that really is the case, those entering in the hopes of some wall paper may want to enter in the MultiOp category (with the attendant band change limits) rather than Single Op Unlimited/Assisted.

Yes, I realize this topic isn't specifically germane to the N1MM+ software, but thought it worth mentioning here.  Read the rules at:
http://www.arrl.org/rtty-roundup

73,
Victor WB0TEV


Re: ARRL RTTY RU: FT8 means no Single Op UNassisted

John Kludt
 

Victor,

Agreed.  But I wonder and maybe we need to take this off line, I have the impression that many of the hardcore RTTY contest crowd run two decoders at once,  So while each decoder is only decoding one signal at a time, as the operator, they are reviewing more than one decoded signal at a time.  So they must have the same issue.

John

On Fri, Jan 4, 2019 at 1:32 AM Victor Paul <vmpaul@...> wrote:
With many planning on using both RTTY and FT8 in the ARRL RTTY RU this weekend, I thought I would highlight some rules quirks of which I was unaware until I actually read the rules carefully.  A couple of take aways that folks should be aware of:

1) If you use WSJT-X or similar FT8 software that decodes more than one signal at a time you CANNOT enter as Single Op UnAssisted.  Quoting from the rules:
"Since ARRL contest rules regarding spotting assistance prohibit the use of “automated, multi-channel decoders” by Single-Operator entrants, stations using software that decodes more than one FT8 signal at a time will have to enter as Single-Operator Unlimited or as Multioperator, just as PSK participants have had to do in the past when using fldigi or DigiPan software."

2) If you enter as Single Op Assisted, it appears that you will be ineligible for a certificate, no matter how high your score is.  Reading section 8 of the rules I see that there will be certificates for the highest scoring Single Op High and Low power  and MultiOp high and low power in each ARRL/RAC section, but I see nothing about any certs or plaques for Single Op Unlimited (i.e. Assisted).  That may not be the intent, but its how I read it.  If that really is the case, those entering in the hopes of some wall paper may want to enter in the MultiOp category (with the attendant band change limits) rather than Single Op Unlimited/Assisted.

Yes, I realize this topic isn't specifically germane to the N1MM+ software, but thought it worth mentioning here.  Read the rules at:
http://www.arrl.org/rtty-roundup

73,
Victor WB0TEV

Re: ARRL RTTY RU: FT8 means no Single Op UNassisted

Drew Vonada-Smith K3PA
 

Unlimited categories are always eligble for the same awards.  Just imprecise language in the rules.  

73,
Drew K3PA

ARRL RTTY RU: FT8 means no Single Op UNassisted

Victor Paul
 

With many planning on using both RTTY and FT8 in the ARRL RTTY RU this weekend, I thought I would highlight some rules quirks of which I was unaware until I actually read the rules carefully.  A couple of take aways that folks should be aware of:

1) If you use WSJT-X or similar FT8 software that decodes more than one signal at a time you CANNOT enter as Single Op UnAssisted.  Quoting from the rules:
"Since ARRL contest rules regarding spotting assistance prohibit the use of “automated, multi-channel decoders” by Single-Operator entrants, stations using software that decodes more than one FT8 signal at a time will have to enter as Single-Operator Unlimited or as Multioperator, just as PSK participants have had to do in the past when using fldigi or DigiPan software."

2) If you enter as Single Op Assisted, it appears that you will be ineligible for a certificate, no matter how high your score is.  Reading section 8 of the rules I see that there will be certificates for the highest scoring Single Op High and Low power  and MultiOp high and low power in each ARRL/RAC section, but I see nothing about any certs or plaques for Single Op Unlimited (i.e. Assisted).  That may not be the intent, but its how I read it.  If that really is the case, those entering in the hopes of some wall paper may want to enter in the MultiOp category (with the attendant band change limits) rather than Single Op Unlimited/Assisted.

Yes, I realize this topic isn't specifically germane to the N1MM+ software, but thought it worth mentioning here.  Read the rules at:
http://www.arrl.org/rtty-roundup

73,
Victor WB0TEV

Re: Can’t get fsk com port in mmtty to stick

Carl Lester
 

Having kind of same issue (see my post from earlier today). My MMTTY FSK com port on the radio 2 changes to different port. This happens if I exit n1mm and then start it later. Not rebooting computer or anything. At least it’s not changing randomly in use like you seem to be suffering. At least not yet? Hmmm. BTW, radio 1 ports are stable. 

Can’t get fsk com port in mmtty to stick

Jamie WW3S
 

Have 2 copies of mmtty, c:\mmtty and c:\mmtty2....di1 is k3 and microkeyer set for com3, di2 is 7610 and extfsk via built in port on radio....worked fine in CQWW rtty, now, the ports keep jumping, I set one and it works, then set di2 and di1 now has the same setting?!?! I’ve tried closing the digi window once properly set to make it stick, but once I open di2, di1 changes from com3 to extfsk.....

Re: cant open COM10 for radio command ?!?!?

Jamie WW3S
 

Yep, you’re correct Rich, that’s what it was....


On Jan 3, 2019, at 10:13 PM, ve3ki <ve3iay@...> wrote:

Do you know which program that error message is coming from? I'd be willing to bet it's coming from MMTTY, not N1MM+. Assuming you are getting set up for the RTTY contest, in the MMTTY Setup window under the TX tab, click on the Radio Command button and see whether by any chance the Port is set to COM10 (it should be set to None).

73,
Rich VE3KI


On Thu, Jan 3, 2019 at 09:30 PM, Jamie WW3S wrote:
pulling what little hair I have left trying to determine the origin of that error.....I have 2 radios configured, K3 on COM1 and 7610 on COM12 (virtual port thru the radio), both radios work, frequency showing in bandmap, but when I change bands on the 7610 I get “Cant opne com10 for radio command”....I’ve searched hi and low, I don’t see COM10 defined anywhere in the config.....trying to determine cause so I can correct it....

Re: cant open COM10 for radio command ?!?!?

ve3ki
 

Do you know which program that error message is coming from? I'd be willing to bet it's coming from MMTTY, not N1MM+. Assuming you are getting set up for the RTTY contest, in the MMTTY Setup window under the TX tab, click on the Radio Command button and see whether by any chance the Port is set to COM10 (it should be set to None).

73,
Rich VE3KI


On Thu, Jan 3, 2019 at 09:30 PM, Jamie WW3S wrote:
pulling what little hair I have left trying to determine the origin of that error.....I have 2 radios configured, K3 on COM1 and 7610 on COM12 (virtual port thru the radio), both radios work, frequency showing in bandmap, but when I change bands on the 7610 I get “Cant opne com10 for radio command”....I’ve searched hi and low, I don’t see COM10 defined anywhere in the config.....trying to determine cause so I can correct it....

cant open COM10 for radio command ?!?!?

Jamie WW3S
 

pulling what little hair I have left trying to determine the origin of that error.....I have 2 radios configured, K3 on COM1 and 7610 on COM12 (virtual port thru the radio), both radios work, frequency showing in bandmap, but when I change bands on the 7610 I get “Cant opne com10 for radio command”....I’ve searched hi and low, I don’t see COM10 defined anywhere in the config.....trying to determine cause so I can correct it....

Re: RTTY Roundup and the Digital Interface window

Paul W5PF
 

That was it, thanks. I had hovered over the icon before and looked at that window, but all that showed was the N1MM+ Logo so I didn't realize that it was the DI window. Thanks for waking me up.

73, Paul W5PF


On 1/3/2019 7:41 PM, ve3ki wrote:
It sounds as if the DI window might be off-screen. The DI window is one of the N1MM+ windows that is grouped together on the Windows Task Bar. Hover the mouse over the N1MM+ icon on the Task Bar, and you should see a couple of thumbnail windows appear above the Task Bar - one of them should be the DI window. Right-click on the DI thumbnail window and select Restore, or if Restore is greyed out, select Move and hit one of the arrow keys on the keyboard two or three times. That should move it partly on-screen, then you can use the mouse to move it to where you want it and then click to leave it there.

If there is no DI window thumbnail, go back to the main N1MM+ screen, use the Window > Digital Interface menu item to try to open it, and then look for the thumbnail window again.

73,
Rich VE3KI


On Thu, Jan 3, 2019 at 08:35 PM, Paul W5PF wrote:
I have installed the latest update, 1.0.4722.0, in preparation for the
RTTY RU. I want to try the integration between N1MMLogger+ and WSJT.

I am using a Flex6600 radio on a Win7 Pro 64 bit computer.

I set up the udp interface between N1MM+ and WSJT and logged a couple
test QSOs from WSJT. All seemed to work as it should. The Flex was in
the DIGU mode.

I then decided to try a rtty qso so I changed my radio mode to RTTY.
N1MM+ followed the change showing the correct mode and frequency.
However, the Digital interface window is gone. Trying to turn it on
using the Window drop down menu does nothing. If I try to transmit the
radio does transmit a rtty signal however there is no window to show any
transmitted or received signals. The RTTY1 Engine window (MMTTY) is open
and functioning.

I am at a loss as to what to try next. I hesitate to uninstall and
reinstall N1MM+ but don't know what else to try.

I have shut down and rebooted the computer with no change.

Any ideas will be appreciated.

73, Paul W5PF

Re: RTTY Roundup and the Digital Interface window

Paul W5PF
 

Oops, there is a thumbnail under the N1MM logo Icon. Let me see if it solves my problem.

Paul W5PF

On 1/3/2019 7:41 PM, ve3ki wrote:
It sounds as if the DI window might be off-screen. The DI window is one of the N1MM+ windows that is grouped together on the Windows Task Bar. Hover the mouse over the N1MM+ icon on the Task Bar, and you should see a couple of thumbnail windows appear above the Task Bar - one of them should be the DI window. Right-click on the DI thumbnail window and select Restore, or if Restore is greyed out, select Move and hit one of the arrow keys on the keyboard two or three times. That should move it partly on-screen, then you can use the mouse to move it to where you want it and then click to leave it there.

If there is no DI window thumbnail, go back to the main N1MM+ screen, use the Window > Digital Interface menu item to try to open it, and then look for the thumbnail window again.

73,
Rich VE3KI


On Thu, Jan 3, 2019 at 08:35 PM, Paul W5PF wrote:
I have installed the latest update, 1.0.4722.0, in preparation for the
RTTY RU. I want to try the integration between N1MMLogger+ and WSJT.

I am using a Flex6600 radio on a Win7 Pro 64 bit computer.

I set up the udp interface between N1MM+ and WSJT and logged a couple
test QSOs from WSJT. All seemed to work as it should. The Flex was in
the DIGU mode.

I then decided to try a rtty qso so I changed my radio mode to RTTY.
N1MM+ followed the change showing the correct mode and frequency.
However, the Digital interface window is gone. Trying to turn it on
using the Window drop down menu does nothing. If I try to transmit the
radio does transmit a rtty signal however there is no window to show any
transmitted or received signals. The RTTY1 Engine window (MMTTY) is open
and functioning.

I am at a loss as to what to try next. I hesitate to uninstall and
reinstall N1MM+ but don't know what else to try.

I have shut down and rebooted the computer with no change.

Any ideas will be appreciated.

73, Paul W5PF

Re: RTTY Roundup and the Digital Interface window

Paul W5PF
 

Thanks for the suggestions Rich. Unfortunately there is no thumbnail and the Window>Digital Interface menu item does not create a window.

73, Paul W5PF

On 1/3/2019 7:41 PM, ve3ki wrote:
It sounds as if the DI window might be off-screen. The DI window is one of the N1MM+ windows that is grouped together on the Windows Task Bar. Hover the mouse over the N1MM+ icon on the Task Bar, and you should see a couple of thumbnail windows appear above the Task Bar - one of them should be the DI window. Right-click on the DI thumbnail window and select Restore, or if Restore is greyed out, select Move and hit one of the arrow keys on the keyboard two or three times. That should move it partly on-screen, then you can use the mouse to move it to where you want it and then click to leave it there.

If there is no DI window thumbnail, go back to the main N1MM+ screen, use the Window > Digital Interface menu item to try to open it, and then look for the thumbnail window again.

73,
Rich VE3KI


On Thu, Jan 3, 2019 at 08:35 PM, Paul W5PF wrote:
I have installed the latest update, 1.0.4722.0, in preparation for the
RTTY RU. I want to try the integration between N1MMLogger+ and WSJT.

I am using a Flex6600 radio on a Win7 Pro 64 bit computer.

I set up the udp interface between N1MM+ and WSJT and logged a couple
test QSOs from WSJT. All seemed to work as it should. The Flex was in
the DIGU mode.

I then decided to try a rtty qso so I changed my radio mode to RTTY.
N1MM+ followed the change showing the correct mode and frequency.
However, the Digital interface window is gone. Trying to turn it on
using the Window drop down menu does nothing. If I try to transmit the
radio does transmit a rtty signal however there is no window to show any
transmitted or received signals. The RTTY1 Engine window (MMTTY) is open
and functioning.

I am at a loss as to what to try next. I hesitate to uninstall and
reinstall N1MM+ but don't know what else to try.

I have shut down and rebooted the computer with no change.

Any ideas will be appreciated.

73, Paul W5PF

Re: RTTY Roundup and the Digital Interface window

ve3ki
 

It sounds as if the DI window might be off-screen. The DI window is one of the N1MM+ windows that is grouped together on the Windows Task Bar. Hover the mouse over the N1MM+ icon on the Task Bar, and you should see a couple of thumbnail windows appear above the Task Bar - one of them should be the DI window. Right-click on the DI thumbnail window and select Restore, or if Restore is greyed out, select Move and hit one of the arrow keys on the keyboard two or three times. That should move it partly on-screen, then you can use the mouse to move it to where you want it and then click to leave it there.

If there is no DI window thumbnail, go back to the main N1MM+ screen, use the Window > Digital Interface menu item to try to open it, and then look for the thumbnail window again.

73,
Rich VE3KI


On Thu, Jan 3, 2019 at 08:35 PM, Paul W5PF wrote:
I have installed the latest update, 1.0.4722.0, in preparation for the
RTTY RU. I want to try the integration between N1MMLogger+ and WSJT.

I am using a Flex6600 radio on a Win7 Pro 64 bit computer.

I set up the udp interface between N1MM+ and WSJT and logged a couple
test QSOs from WSJT. All seemed to work as it should. The Flex was in
the DIGU mode.

I then decided to try a rtty qso so I changed my radio mode to RTTY.
N1MM+ followed the change showing the correct mode and frequency.
However, the Digital interface window is gone. Trying to turn it on
using the Window drop down menu does nothing. If I try to transmit the
radio does transmit a rtty signal however there is no window to show any
transmitted or received signals. The RTTY1 Engine window (MMTTY) is open
and functioning.

I am at a loss as to what to try next. I hesitate to uninstall and
reinstall N1MM+ but don't know what else to try.

I have shut down and rebooted the computer with no change.

Any ideas will be appreciated.

73, Paul W5PF

RTTY Roundup and the Digital Interface window

Paul W5PF
 

I have installed the latest update, 1.0.4722.0, in preparation for the RTTY RU. I want to try the integration between N1MMLogger+ and WSJT.

I am using a Flex6600 radio on a Win7 Pro 64 bit computer.

I set up the udp interface between N1MM+ and WSJT and logged a couple test QSOs from WSJT. All seemed to work as it should. The Flex was in the DIGU mode.

I then decided to try a rtty qso so I changed my radio mode to RTTY. N1MM+ followed the change showing the correct mode and frequency. However, the Digital interface window is gone. Trying to turn it on using the Window drop down menu does nothing. If I try to transmit the radio does transmit a rtty signal however there is no window to show any transmitted or received signals. The RTTY1 Engine window (MMTTY) is open and functioning.

I am at a loss as to what to try next. I hesitate to uninstall and reinstall N1MM+ but don't know what else to try.

I have shut down and rebooted the computer with no change.

Any ideas will be appreciated.

73, Paul W5PF

Re: Today's N1MM Update - New real-time contest interface between WSJT-X and N1MM+

ve3ki
 

I did some testing earlier today and mine were identified with DG. Make sure that N1MM+ itself is in a digital mode (not CW or SSB). I don't know what you mean by "it only changed the Cabrillo header" - what only changed what?  FWIW, in the tests I did the Mode category for the contest was RTTY. FT8 contacts were recorded as DG in the Cabrillo, and as FT8 in ADIF.

73,
Rich VE3KI



On Thu, Jan 3, 2019 at 08:13 PM, Rod Linkous wrote:
Rick,

Simulating FT8 contacts using DIGITAL in N1MM contest setup resulted in FT8 contacts still as RY.  So all contacts [simulated] are RY in Cabrillo and ADIF format.  So it is after the contest editing chore.  Thanks for suggestion.  It only changed the Cabrillo header.
 
73
 
Rod W7OM

Re: Macros in the DI window

ve3ki
 

Open the DI Setup window, click on the Message Setup tab, choose which set of messages you want (there are a3 or 4 sets) and edit the messages there. See <http://n1mm.hamdocs.com/tiki-index.php?page=Digital+Setup&structure=N1MM+Logger+Documentation#Tab:_Message_Setup>.

73,
Rich VE3KI


On Thu, Jan 3, 2019 at 07:33 PM, Skip wrote:
Can someone tell me how to put various text strings into the macro buttons at the bottom of the DI window?  I believe I've tried every combination of click, type, save, [except the right one] and my text never appears in the button.

73,
Fred ["Skip"] K6DGW
Sparks NV DM09dn
Washoe County

Today's N1MM Update - New real-time contest interface between WSJT-X and N1MM+

Rod Linkous <W70m@...>
 

Rick,

Simulating FT8 contacts using DIGITAL in N1MM contest setup resulted in FT8 contacts still as RY.  So all contacts [simulated] are RY in Cabrillo and ADIF format.  So it is after the contest editing chore.  Thanks for suggestion.  It only changed the Cabrillo header.

73

Rod W7OM