Date   
Re: Function Keys still not responding

Steve London
 

Are you using a microham USB II interface or a microham digikeyer II or a microham microkeyer II interface ?

73,
Steve, N2IC

On 05/10/2019 09:31 AM, David Mitchell wrote:
This is a new problem.  I can key the radio fine with my paddles and also with my microham II interface.  It was fine  a couple of weeks ago.
-- Dave WB2PJH

Re: Function Keys still not responding

David AD4TJ
 

Are you sure the program is in CW mode? In the box where you type in calls, type in CW and press Enter. Now will your function keys work.

73, David AD4TJ

On Friday, May 10, 2019, 11:49:40 AM EDT, Robert Rantin via Groups.Io <robertrantin@...> wrote:


All working fine here
de Robbie(MI0RRE)

On Friday, 10 May 2019, 16:31:34 BST, David Mitchell <wb2pjh@...> wrote:


This is a new problem.  I can key the radio fine with my paddles and also with my microham II interface.  It was fine  a couple of weeks ago.

-- Dave WB2PJH

Re: Function Keys still not responding

Robert Rantin
 

All working fine here
de Robbie(MI0RRE)

On Friday, 10 May 2019, 16:31:34 BST, David Mitchell <wb2pjh@...> wrote:


This is a new problem.  I can key the radio fine with my paddles and also with my microham II interface.  It was fine  a couple of weeks ago.

-- Dave WB2PJH

Re: Function Keys still not responding

David Mitchell
 

This is a new problem.  I can key the radio fine with my paddles and also with my microham II interface.  It was fine  a couple of weeks ago.

-- Dave WB2PJH

Re: Sequequttial Numbers: Thanks Everyone

KEN
 

Thanks for the help guys, Larry , Merrill  , Pete, Tim , Doug                                                                                                                                                                                                                  ny 
WN8Y

Re: "Unnamed Scope Spectrum Monitor"?

ve3ki
 

Have you tried deleting the existing spectrum window (there is a menu item for this near the bottom of the right-click menu), and then starting over again with a new spectrum window?

73,
Rich VE3KI


On Fri, May 10, 2019 at 12:55 AM, F5vjc wrote:
Hi Rick, I think we may have similar problems, although my setup is not as complex as yours and does not involve remote working.
I use WinK3, CW Skimmer and N1MM+. This has worked flawlessly for some time now. However, after the last update to N1MM I started to have a problem with the N1MM Spectrum window. I usually use UDP in Win4K3 to feed the N1MM Spectrum and now I cannot get this to work and have the same symptoms as you describe, ie having named the UDP feed it always comes up in N1MM as 'Unnamed Scope Spectrum Monitor' if I change this manually it does not stick. Also N1MM will become unresponsive and crash when I select UDP broadcast in Win4K3, but all works fine without UDP selected.
I posted earlier in the week on this topic hoping someone else may have seen this problem, then I saw your post.
 
If you do have any thoughts or can help with this please let me know.
 
Thanks, 73
 
Denis F5VJC

On Thu, 9 May 2019 at 20:29, Rick Tavan <rtavan@...> wrote:
Update: I got the original control side logging computer working again. Looking closely at the server side MM instance, I discovered that the Relay name had disappeared! It's usually persistent but this time appears to have gone away. I re-specified it and achieved SD Window rendezvous on the original computer. The new computer still displays "Unnamed Scope Spectrum Monitor" in the title bar of the SD window.  I've confirmed that, with the Firewall enabled, there is a rule to allow MM to work. I've tried turning off the Win 10 Defender Firewall entirely to no avail. I don't see any other firewalls in operation.
 
Any advice would be greatly appreciated. Thanks,
 
/Rick N6XI

--

Rick Tavan
Truckee, CA

On Thu, May 9, 2019 at 10:04 AM Rick Tavan via Groups.Io <rtavan=gmail.com@groups.io> wrote:
I've been running Spectrum Display remotely for some months now with good success. Yesterday, I tried to introduce a new logging computer on the control side and couldn't get it working - the SD window title bar said "Unnamed Scope Spectrum Monitor". Yes, I changed the control site port forwarding to forward 13064 to the LAN address of the new computer but that didn't help. So I tried to revert to the original logging computer. Now, its(the original computer's) SD window displays the same title ("Unnamed Scope Spectrum Monitor"), even after reverting the port forward to the original computer's LAN address. Yes, I've re-specified Spectrum Source in the SD window right-click menu. I've tried restarting the SD Window, the entire MM program, and rebooting the control site operating system, all to no avail. I'm using Ubiquiti UniFi router, switches, and "cloud key" on both sides. It has a very good UI and seems straight-forward with respect to port forwarding. It lets me define both port forwards with check-boxes to Enable or Disable whichever one I'm not using. But something's not working. Questions:
 
What does "Unnamed Scope Spectrum Monitor" in the SD Window title bar imply after Spectrum Source has been specified correctly as the relay name in use on the radio side?
 
Any other suggestions as to what I might have screwed up?
 
Thanks,
 
/Rick N6XI

--

Rick Tavan
Truckee, CA

 

 

 

 

Re: N1MMLogger #facebook

ve3ki
 

The spotted call signs in the video are in red at the top of the spectrum window. You can see them better in the top screen shot at <https://n1mmwp.hamdocs.com/manual-windows/spectrum-display-window/>. They will be placed there either from DX cluster spots from the Telnet window, or by self-spotting from the program, such as by using the "QSYing Wipes the Call & Spots QSO in Bandmap" option. Anything that would be spotted to the Bandmap window is also spotted to the Spectrum Display window.

73,
Rich VE3KI


On Fri, May 10, 2019 at 03:47 AM, Lee Clayton wrote:
Probably a dumb question from a fairly new ham....but how were you able to tell only by looking at the spectrum display that one signal was spotted and another was not?  Were you looking at another screen that was not shown in the video?
‘73
Lee

Re: "Unnamed Scope Spectrum Monitor"?

John Bednar
 

N1MM web page: Click Files, select N1MMPlus Latest Update.

 

John, K3CT

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of F5vjc
Sent: Friday, May 10, 2019 4:42 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] "Unnamed Scope Spectrum Monitor"?

 

Hi Les, no I haven't, I wasn't sure it was possible to go back to earlier versions.

 

 

On Fri, 10 May 2019 at 10:37, Les Elliott via Groups.Io <g4ogb=tiscali.co.uk@groups.io> wrote:

Have you tried an earlier version?

 

Les, G4OGB

 

From: F5vjc

Sent: Friday, May 10, 2019 5:54 AM

Subject: Re: [N1MMLoggerPlus] "Unnamed Scope Spectrum Monitor"?

 

Hi Rick, I think we may have similar problems, although my setup is not as complex as yours and does not involve remote working.

I use WinK3, CW Skimmer and N1MM+. This has worked flawlessly for some time now. However, after the last update to N1MM I started to have a problem with the N1MM Spectrum window. I usually use UDP in Win4K3 to feed the N1MM Spectrum and now I cannot get this to work and have the same symptoms as you describe, ie having named the UDP feed it always comes up in N1MM as 'Unnamed Scope Spectrum Monitor' if I change this manually it does not stick. Also N1MM will become unresponsive and crash when I select UDP broadcast in Win4K3, but all works fine without UDP selected.

I posted earlier in the week on this topic hoping someone else may have seen this problem, then I saw your post.

 

If you do have any thoughts or can help with this please let me know.

 

Thanks, 73

 

Denis F5VJC

 

On Thu, 9 May 2019 at 20:29, Rick Tavan <rtavan@...> wrote:

Update: I got the original control side logging computer working again. Looking closely at the server side MM instance, I discovered that the Relay name had disappeared! It's usually persistent but this time appears to have gone away. I re-specified it and achieved SD Window rendezvous on the original computer. The new computer still displays "Unnamed Scope Spectrum Monitor" in the title bar of the SD window.  I've confirmed that, with the Firewall enabled, there is a rule to allow MM to work. I've tried turning off the Win 10 Defender Firewall entirely to no avail. I don't see any other firewalls in operation.

 

Any advice would be greatly appreciated. Thanks,

 

/Rick N6XI

 

--


Rick Tavan
Truckee, CA

 

 

On Thu, May 9, 2019 at 10:04 AM Rick Tavan via Groups.Io <rtavan=gmail.com@groups.io> wrote:

I've been running Spectrum Display remotely for some months now with good success. Yesterday, I tried to introduce a new logging computer on the control side and couldn't get it working - the SD window title bar said "Unnamed Scope Spectrum Monitor". Yes, I changed the control site port forwarding to forward 13064 to the LAN address of the new computer but that didn't help. So I tried to revert to the original logging computer Now, its(the original computer's) SD window displays the same title ("Unnamed Scope Spectrum Monitor"), even after reverting the port forward to the original computer's LAN address. Yes, I've re-specified Spectrum Source in the SD window right-click menu. I've tried restarting the SD Window, the entire MM program, and rebooting the control site operating system, all to no avail. I'm using Ubiquiti UniFi router, switches, and "cloud key" on both sides. It has a very good UI and seems straight-forward with respect to port forwarding. It lets me define both port forwards with check-boxes to Enable or Disable whichever one I'm not using. But something's not working. Questions:

 

What does "Unnamed Scope Spectrum Monitor" in the SD Window title bar imply after Spectrum Source has been specified correctly as the relay name in use on the radio side?

 

Any other suggestions as to what I might have screwed up?

 

Thanks,

 

/Rick N6XI

 

--


Rick Tavan
Truckee, CA

Re: "Unnamed Scope Spectrum Monitor"?

F5vjc
 

Hi Les, no I haven't, I wasn't sure it was possible to go back to earlier versions.


On Fri, 10 May 2019 at 10:37, Les Elliott via Groups.Io <g4ogb=tiscali.co.uk@groups.io> wrote:
Have you tried an earlier version?
 
Les, G4OGB
 
From: F5vjc
Sent: Friday, May 10, 2019 5:54 AM
Subject: Re: [N1MMLoggerPlus] "Unnamed Scope Spectrum Monitor"?
 
Hi Rick, I think we may have similar problems, although my setup is not as complex as yours and does not involve remote working.
I use WinK3, CW Skimmer and N1MM+. This has worked flawlessly for some time now. However, after the last update to N1MM I started to have a problem with the N1MM Spectrum window. I usually use UDP in Win4K3 to feed the N1MM Spectrum and now I cannot get this to work and have the same symptoms as you describe, ie having named the UDP feed it always comes up in N1MM as 'Unnamed Scope Spectrum Monitor' if I change this manually it does not stick. Also N1MM will become unresponsive and crash when I select UDP broadcast in Win4K3, but all works fine without UDP selected.
I posted earlier in the week on this topic hoping someone else may have seen this problem, then I saw your post.
 
If you do have any thoughts or can help with this please let me know.
 
Thanks, 73
 
Denis F5VJC
 
On Thu, 9 May 2019 at 20:29, Rick Tavan <rtavan@...> wrote:
Update: I got the original control side logging computer working again. Looking closely at the server side MM instance, I discovered that the Relay name had disappeared! It's usually persistent but this time appears to have gone away. I re-specified it and achieved SD Window rendezvous on the original computer. The new computer still displays "Unnamed Scope Spectrum Monitor" in the title bar of the SD window.  I've confirmed that, with the Firewall enabled, there is a rule to allow MM to work. I've tried turning off the Win 10 Defender Firewall entirely to no avail. I don't see any other firewalls in operation.
 
Any advice would be greatly appreciated. Thanks,
 
/Rick N6XI
 
--

Rick Tavan
Truckee, CA
 
 
On Thu, May 9, 2019 at 10:04 AM Rick Tavan via Groups.Io <rtavan=gmail.com@groups.io> wrote:
I've been running Spectrum Display remotely for some months now with good success. Yesterday, I tried to introduce a new logging computer on the control side and couldn't get it working - the SD window title bar said "Unnamed Scope Spectrum Monitor". Yes, I changed the control site port forwarding to forward 13064 to the LAN address of the new computer but that didn't help. So I tried to revert to the original logging computer. Now, its(the original computer's) SD window displays the same title ("Unnamed Scope Spectrum Monitor"), even after reverting the port forward to the original computer's LAN address. Yes, I've re-specified Spectrum Source in the SD window right-click menu. I've tried restarting the SD Window, the entire MM program, and rebooting the control site operating system, all to no avail. I'm using Ubiquiti UniFi router, switches, and "cloud key" on both sides. It has a very good UI and seems straight-forward with respect to port forwarding. It lets me define both port forwards with check-boxes to Enable or Disable whichever one I'm not using. But something's not working. Questions:
 
What does "Unnamed Scope Spectrum Monitor" in the SD Window title bar imply after Spectrum Source has been specified correctly as the relay name in use on the radio side?
 
Any other suggestions as to what I might have screwed up?
 
Thanks,
 
/Rick N6XI
 
--

Rick Tavan
Truckee, CA

Re: "Unnamed Scope Spectrum Monitor"?

Les Elliott
 

Have you tried an earlier version?
 
Les, G4OGB
 

From: F5vjc
Sent: Friday, May 10, 2019 5:54 AM
Subject: Re: [N1MMLoggerPlus] "Unnamed Scope Spectrum Monitor"?
 
Hi Rick, I think we may have similar problems, although my setup is not as complex as yours and does not involve remote working.
I use WinK3, CW Skimmer and N1MM+. This has worked flawlessly for some time now. However, after the last update to N1MM I started to have a problem with the N1MM Spectrum window. I usually use UDP in Win4K3 to feed the N1MM Spectrum and now I cannot get this to work and have the same symptoms as you describe, ie having named the UDP feed it always comes up in N1MM as 'Unnamed Scope Spectrum Monitor' if I change this manually it does not stick. Also N1MM will become unresponsive and crash when I select UDP broadcast in Win4K3, but all works fine without UDP selected.
I posted earlier in the week on this topic hoping someone else may have seen this problem, then I saw your post.
 
If you do have any thoughts or can help with this please let me know.
 
Thanks, 73
 
Denis F5VJC
 
On Thu, 9 May 2019 at 20:29, Rick Tavan <rtavan@...> wrote:
Update: I got the original control side logging computer working again. Looking closely at the server side MM instance, I discovered that the Relay name had disappeared! It's usually persistent but this time appears to have gone away. I re-specified it and achieved SD Window rendezvous on the original computer. The new computer still displays "Unnamed Scope Spectrum Monitor" in the title bar of the SD window.  I've confirmed that, with the Firewall enabled, there is a rule to allow MM to work. I've tried turning off the Win 10 Defender Firewall entirely to no avail. I don't see any other firewalls in operation.
 
Any advice would be greatly appreciated. Thanks,
 
/Rick N6XI
 
--

Rick Tavan
Truckee, CA
 
 
On Thu, May 9, 2019 at 10:04 AM Rick Tavan via Groups.Io <rtavan=gmail.com@groups.io> wrote:
I've been running Spectrum Display remotely for some months now with good success. Yesterday, I tried to introduce a new logging computer on the control side and couldn't get it working - the SD window title bar said "Unnamed Scope Spectrum Monitor". Yes, I changed the control site port forwarding to forward 13064 to the LAN address of the new computer but that didn't help. So I tried to revert to the original logging computer. Now, its(the original computer's) SD window displays the same title ("Unnamed Scope Spectrum Monitor"), even after reverting the port forward to the original computer's LAN address. Yes, I've re-specified Spectrum Source in the SD window right-click menu. I've tried restarting the SD Window, the entire MM program, and rebooting the control site operating system, all to no avail. I'm using Ubiquiti UniFi router, switches, and "cloud key" on both sides. It has a very good UI and seems straight-forward with respect to port forwarding. It lets me define both port forwards with check-boxes to Enable or Disable whichever one I'm not using. But something's not working. Questions:
 
What does "Unnamed Scope Spectrum Monitor" in the SD Window title bar imply after Spectrum Source has been specified correctly as the relay name in use on the radio side?
 
Any other suggestions as to what I might have screwed up?
 
Thanks,
 
/Rick N6XI
 
--

Rick Tavan
Truckee, CA

Re: N1MMLogger #facebook

Lee W4EIS
 

Probably a dumb question from a fairly new ham....but how were you able to tell only by looking at the spectrum display that one signal was spotted and another was not?  Were you looking at another screen that was not shown in the video?
‘73
Lee
W4EIS 

Re: "Unnamed Scope Spectrum Monitor"?

F5vjc
 

Hi Rick, I think we may have similar problems, although my setup is not as complex as yours and does not involve remote working.
I use WinK3, CW Skimmer and N1MM+. This has worked flawlessly for some time now. However, after the last update to N1MM I started to have a problem with the N1MM Spectrum window. I usually use UDP in Win4K3 to feed the N1MM Spectrum and now I cannot get this to work and have the same symptoms as you describe, ie having named the UDP feed it always comes up in N1MM as 'Unnamed Scope Spectrum Monitor' if I change this manually it does not stick. Also N1MM will become unresponsive and crash when I select UDP broadcast in Win4K3, but all works fine without UDP selected.
I posted earlier in the week on this topic hoping someone else may have seen this problem, then I saw your post.

If you do have any thoughts or can help with this please let me know.

Thanks, 73

Denis F5VJC

On Thu, 9 May 2019 at 20:29, Rick Tavan <rtavan@...> wrote:
Update: I got the original control side logging computer working again. Looking closely at the server side MM instance, I discovered that the Relay name had disappeared! It's usually persistent but this time appears to have gone away. I re-specified it and achieved SD Window rendezvous on the original computer. The new computer still displays "Unnamed Scope Spectrum Monitor" in the title bar of the SD window.  I've confirmed that, with the Firewall enabled, there is a rule to allow MM to work. I've tried turning off the Win 10 Defender Firewall entirely to no avail. I don't see any other firewalls in operation.

Any advice would be greatly appreciated. Thanks,

/Rick N6XI

--

Rick Tavan
Truckee, CA


On Thu, May 9, 2019 at 10:04 AM Rick Tavan via Groups.Io <rtavan=gmail.com@groups.io> wrote:
I've been running Spectrum Display remotely for some months now with good success. Yesterday, I tried to introduce a new logging computer on the control side and couldn't get it working - the SD window title bar said "Unnamed Scope Spectrum Monitor". Yes, I changed the control site port forwarding to forward 13064 to the LAN address of the new computer but that didn't help. So I tried to revert to the original logging computer. Now, its(the original computer's) SD window displays the same title ("Unnamed Scope Spectrum Monitor"), even after reverting the port forward to the original computer's LAN address. Yes, I've re-specified Spectrum Source in the SD window right-click menu. I've tried restarting the SD Window, the entire MM program, and rebooting the control site operating system, all to no avail. I'm using Ubiquiti UniFi router, switches, and "cloud key" on both sides. It has a very good UI and seems straight-forward with respect to port forwarding. It lets me define both port forwards with check-boxes to Enable or Disable whichever one I'm not using. But something's not working. Questions:

What does "Unnamed Scope Spectrum Monitor" in the SD Window title bar imply after Spectrum Source has been specified correctly as the relay name in use on the radio side?

Any other suggestions as to what I might have screwed up?

Thanks,

/Rick N6XI

--

Rick Tavan
Truckee, CA

Re: "Unnamed Scope Spectrum Monitor"?

Rick Tavan
 

Update: I got the original control side logging computer working again. Looking closely at the server side MM instance, I discovered that the Relay name had disappeared! It's usually persistent but this time appears to have gone away. I re-specified it and achieved SD Window rendezvous on the original computer. The new computer still displays "Unnamed Scope Spectrum Monitor" in the title bar of the SD window.  I've confirmed that, with the Firewall enabled, there is a rule to allow MM to work. I've tried turning off the Win 10 Defender Firewall entirely to no avail. I don't see any other firewalls in operation.

Any advice would be greatly appreciated. Thanks,

/Rick N6XI

--

Rick Tavan
Truckee, CA


On Thu, May 9, 2019 at 10:04 AM Rick Tavan via Groups.Io <rtavan=gmail.com@groups.io> wrote:
I've been running Spectrum Display remotely for some months now with good success. Yesterday, I tried to introduce a new logging computer on the control side and couldn't get it working - the SD window title bar said "Unnamed Scope Spectrum Monitor". Yes, I changed the control site port forwarding to forward 13064 to the LAN address of the new computer but that didn't help. So I tried to revert to the original logging computer. Now, its(the original computer's) SD window displays the same title ("Unnamed Scope Spectrum Monitor"), even after reverting the port forward to the original computer's LAN address. Yes, I've re-specified Spectrum Source in the SD window right-click menu. I've tried restarting the SD Window, the entire MM program, and rebooting the control site operating system, all to no avail. I'm using Ubiquiti UniFi router, switches, and "cloud key" on both sides. It has a very good UI and seems straight-forward with respect to port forwarding. It lets me define both port forwards with check-boxes to Enable or Disable whichever one I'm not using. But something's not working. Questions:

What does "Unnamed Scope Spectrum Monitor" in the SD Window title bar imply after Spectrum Source has been specified correctly as the relay name in use on the radio side?

Any other suggestions as to what I might have screwed up?

Thanks,

/Rick N6XI

--

Rick Tavan
Truckee, CA

"Unnamed Scope Spectrum Monitor"?

Rick Tavan
 

I've been running Spectrum Display remotely for some months now with good success. Yesterday, I tried to introduce a new logging computer on the control side and couldn't get it working - the SD window title bar said "Unnamed Scope Spectrum Monitor". Yes, I changed the control site port forwarding to forward 13064 to the LAN address of the new computer but that didn't help. So I tried to revert to the original logging computer. Now, its(the original computer's) SD window displays the same title ("Unnamed Scope Spectrum Monitor"), even after reverting the port forward to the original computer's LAN address. Yes, I've re-specified Spectrum Source in the SD window right-click menu. I've tried restarting the SD Window, the entire MM program, and rebooting the control site operating system, all to no avail. I'm using Ubiquiti UniFi router, switches, and "cloud key" on both sides. It has a very good UI and seems straight-forward with respect to port forwarding. It lets me define both port forwards with check-boxes to Enable or Disable whichever one I'm not using. But something's not working. Questions:

What does "Unnamed Scope Spectrum Monitor" in the SD Window title bar imply after Spectrum Source has been specified correctly as the relay name in use on the radio side?

Any other suggestions as to what I might have screwed up?

Thanks,

/Rick N6XI

--

Rick Tavan
Truckee, CA

Re: Sequequttial Numbers

Tim Shoppa
 

This is related, but more about on-air form rather than all the N1MM config options. It's great that N1MM can be configured to send leading zeroes (or leading "T"'s) but note that in WPX for example, the rules FAQ explicitly states that you do not need to send leading zeroes (and after the 999th contact you have to send all 4 digits). Similarly for ARRL sweepstakes, the rules explicitly states you do not have to send leading zeroes for your serial number.

Q: The rules say to begin with serial number 001. Do I have to send or announce the leading zeros in every serial number?

A: No, you do not. It is only important that you give out a number that increases in sequence as you work stations. When you reach 1000, you should continue sending all 4 digits.

Tim N3QE


On Tue, May 7, 2019 at 7:20 PM KEN <ham.wn8y@...> wrote:
Question about sequential numbers starting with 001.
In the ARI DX International the required exchange was RST and sequential numbers starting with 001. In the SENT EXCHANGE I had :   # 001.
The first QSO i sent my report and it came out  as 559   1.  Not 001 just 1. He asked for his report and i manually had to send 001.
I have checked in the N1MM reference and did not find any exceptions.

Any suggestions as to the  reason for this?

Kenny
WN8Y

Re: Sequequttial Numbers

KEN
 

Hi Pete,

Thank you for your response. Looks like it is working. When logged I do not show any zeros. But actually transmitting i can see them going out. So I guess those different contest sponsors are use to seeing that.
I can see now the reason  that i have read in more than one review to setup several days before the contest event.  I'm still on the learning curve but making progress..

73 & Regards

Ken WN8Y

IC-9700 switching VFO's & main/subband?

Frank PH2M
 

Hello all,

I just collected my brand new ICOM IC-9700 this week and planned to use it next week in our national VHF+ Dutch NLContest (Worked All Netherlands), is it possible to switch easy within N1MM+ via the keyboard/mouse between the VFO's and also between the Main/SubBand of the IC-9700? Also is it easy to switch between all 3 bands (2M / 70CM / 23CM) with N1MM+ ???

I 'am going to use my IC-9700 (like my previous IC-821h) in SO2R configuration together with my IC-7300 on at least 4M / 6M + 2M / 70CM (and maybe 23CM in the future) so jumping 4 or 5 bands by mouse-clicks and/or keyboard will be the easiest way ;)

73 de Frank PH2M

Re: SO2V radios

ART W2NRA
 

IMNSHO Your best choice for SO2V is the Icom IC-7610. It has dual receive and each VFO can be on different bands. But the biggest difference is the new Spectrum Display setup in N1MM Logger+. You can use these displays in place of the bandmaps. I’ve been using the IC-7610 in SO2V for thousands of QSO and the new Spectrum Displays for 2 weeks. 

73, art w2nra
CWOPS 1955

On May 8, 2019, at 6:07 PM, pineapple Lane via Groups.Io <AE1N@...> wrote:

What current radios can be used for SO2V operations? Layne AE1N

Re: Sequequttial Numbers

merrill brown
 

Just insert the # sign no number after it


Merrill
WK2g

On May 9, 2019, at 6:21 AM, Larry K8UT <k8ut@...> wrote:

Kenny,

Enable "Send Leading zeros in serial numbers" in the Configurer's Function Keys tab.

-larry (K8UT)

------ Original Message ------
From: "KEN" <ham.wn8y@...>
Sent: 2019-05-07 19:20:35
Subject: [N1MMLoggerPlus] Sequequttial Numbers

Question about sequential numbers starting with 001.
In the ARI DX International the required exchange was RST and sequential numbers starting with 001. In the SENT EXCHANGE I had :   # 001.
The first QSO i sent my report and it came out  as 559   1.  Not 001 just 1. He asked for his report and i manually had to send 001.
I have checked in the N1MM reference and did not find any exceptions.

Any suggestions as to the  reason for this?

Kenny
WN8Y

Re: Sequequttial Numbers

Larry K8UT
 

Kenny,

Enable "Send Leading zeros in serial numbers" in the Configurer's Function Keys tab.

-larry (K8UT)

------ Original Message ------
From: "KEN" <ham.wn8y@...>
Sent: 2019-05-07 19:20:35
Subject: [N1MMLoggerPlus] Sequequttial Numbers

Question about sequential numbers starting with 001.
In the ARI DX International the required exchange was RST and sequential numbers starting with 001. In the SENT EXCHANGE I had :   # 001.
The first QSO i sent my report and it came out  as 559   1.  Not 001 just 1. He asked for his report and i manually had to send 001.
I have checked in the N1MM reference and did not find any exceptions.

Any suggestions as to the  reason for this?

Kenny
WN8Y