Author Topic: N1MM+ New User Help  (Read 6836 times)

K6DGW

  • Newbie
  • *
  • Posts: 9
    • View Profile
    • Email
N1MM+ New User Help
« on: 2015-11-13, 22:45:07 »
Extreme newbie here.  K3 control to a K3 remote.  I have the RR1258 MK2 working, latest FW, CW only right now.  Paddle to WinkerUSB [which show up as COM3 in device mgr] keys the RR through pin 4 of the I/O connector on the rear of the RR.  Works fine.  COM15 is the RR Virtual COM1 port in device mgr. 

I configured N1MM+ for K3 on COM15, 38400,8,N,1 and Winkey on COM3.  N1MM+ never sees the K3 and keeps telling me the K3 is not responding.  Any ideas appreciated

73,

Fred K6DGW
Sparks NV

W1UE

  • Full Member
  • ***
  • Posts: 140
    • View Profile
    • Email
Re: N1MM+ New User Help
« Reply #1 on: 2015-11-14, 11:55:31 »
Fred

A few suggestions.  On the Control RRC, plug the USB cable into the computer.  That will create 4 comports.  Write down the Windows comport number for Com 1 and Com FSK.  Now go into N1MM+, and configure the Windows Comport number for the radio and the Windows Comport number for the Winkey.  Plug the paddle directly into the RR unit.  In the RRC Control web page, under Serial tab, make "Com3 Mode (USB-COMFSK)" drop down box to read "Mode 8- Winkeyer".  That will use the Winkey emulator within the RRC Control unit. 

Dennis W1UE

K2MK

  • Newbie
  • *
  • Posts: 7
    • View Profile
    • Email
Re: N1MM+ New User Help
« Reply #2 on: 2015-11-14, 12:01:06 »
Hi Fred,

Also a newbie here using a K3 to communicate with RHR. My intermittent communication problems at the control end were resolved by changing the baud rate on N1MM to 9600. Also change the baud rate on your PC for COM 15 to 9600 using your PC device manager. And a corresponding change to the baud rate on the RRC serial setting screen.

73,
Mike K2MK
« Last Edit: 2015-11-14, 12:06:15 by K2MK »

K6DGW

  • Newbie
  • *
  • Posts: 9
    • View Profile
    • Email
Re: N1MM+ New User Help
« Reply #3 on: 2015-11-14, 22:41:14 »
Thanks for the advice and guidance.  Setting N1MM+, RR COM1, and the RR Virtual COM1 [real COM15 on my computer] did not fix the problem.  I'm coming to the conclusion that I need to learn a lot more about how RR works ... right now I just seem to be "trying stuff" with no real plan and the only outcome I can ever report is, "It works," or, "It didn't work.  I'll see if I can get smarter on some of this first.

73,

Fred K6DGW
Sparks NV