RcForb, N1MM, and USB Warning!

How to Connect a Remote K3*, RcForb Server,
RcForb Client, N1MM, and USB Warning!

April 8, 2021

  

Power on the K3

  • In the K3 Config Menu, set PTT-KEY to OFF-DTR.  Be sure to save the change.

  

  

Launch the RcForb Server

  • In the RcForb Server under Options->Radio Config->PPT & CW Keying, enable "External CW" and select the same COMx port as used for the local K3, and select DTR. Note in the example shown below, the RcForb server connects to the K3 via COM9.   
  • Save and restart the RcForb server.  We are finished working with RcForb Server.

    

    
  

Working now with the RcForb Client

  • Launch RcForb Client Version 9
  • Select Virtual Devices from the top menu
  • Under Virtual Devices, select an unused COMx port, in the example shown below,  COM5 has been selected.  Set the slider to ON (leave it ON). 
  • Now, Exit the RcForb Client to save this new configuration.  This new COMx port will be created the next time you start the RcForb Client.



  
  

Working now with N1MM

  • In N1MM, go to Config and under Port enter the COMx port you created in the RcForb Client, and under Radio, select Elecraft K3, check CW/Other, and check Set.
  • In the pulldown, set DTR to CW and RTS to Always Off.
  • Disable all 4 items regarding PTT options and uncheck Allow ext interrupts .  
  • That's it.  Okay out of all the dialog boxes.


   
  
  

Operating Instructions
  • When you use N1MM with RcForb, always start the RcForb Client first.  
  • The RcForb Client creates the virtual COMx port use by N1MM.  
  • RcForb creates this port every time it starts and removes it when you close the RcForb Client.  Comx is NOT persistent.
  • When using CW on the K3 be sure VOX is on.
  • Good DX and Contesting!

*A very special thank you to Roger, W8JR, at RemoteHams.   This post would NOT have been possible without his help.  Thank you Roger. 

USB WARNING!

The Windows default behavior for USB hubs is to shut them down to save power after a period of inactivity. Unfortunately, the only activity Windows appears to be aware of is keyboard or mouse activity. A USB port that is being used for something else, such as a USB-to-serial adapter, looks to Windows as if it is inactive, and Windows shuts that USB hub down after a few minutes. This will cause the port to stop working ....

The solution to this comes in two steps, but first, be sure that the USB device you’re having trouble with is connected to its port.  First...
  • Open Device Manager, expand the section on Universal Serial Bus controllers, and 
  • then open each entry labelled either “Generic USB Hub”, “USB Root Hub” or “USB 3.0 eXtensible Host Controller” (or something similar), 
  • open its Properties dialog, 
  • select the Power Management tab, and 
  • uncheck the check box called “Allow the computer to turn off this device to save power”.
The second involves Power Options on the Control Panel. You will not necessarily find all of these settings on every system, but every system running N1MM Logger+ or any other logging software should be set to minimize Windows “power saving”.

  • Open the Control Panel and select Power Options. 
  • One of the “Plans” will be “High Performance” – select it. Then 
  • click “Change plan settings” and set “put the computer to sleep” to “never”. 
  • If found, also select “Change advanced power settings” and set “Sleep | “Hibernate after” to “Never” and “Allow hybrid sleep” to “Off”. 
  • In “USB Settings” set “USB selective suspend setting” to “Disabled” and 
  • under “PCI Express” set “Link State Power Management” to “Off”. 
  • Also set “Wireless adapter Settings” to “Maximum Performance”.
For the full reference please see:



No comments: