General Info & FAQ

In this document information is gathered about setting up the freeware contest program N1MM logger with the microHAM MK2R+ SO2R controller and Station Master banddecoder.

The original text from Joe, W4TV has been used as a start for this document and updated with texts from Pete, N4ZR his SO2R-only document. Also information from the N1MM and microHAM reflector are used and of course own trial and error.

This document has multiple sections. The information decribed is being used at the stations PA1T (Timon) and PA1M (Thomas). Choices have been made depending on the equipment used at these stations (PC, Radios etc). As an example: My PC has only 1 serial port so there is room for 7 virtual ports in uRouter in combination with N1MM logger. The shack PC at PA1T has 3 serial ports, so only 5 virtual ports are left to use and the LPT port is used.

The information below is a compilation of information from reflectors, e-mail lists etc.. and does not neccesarily mean we have encoutered all these problems or have had success with all proposed solutions.

I’d like to thank all who have written about the MK2R+ in combination with N1MM logger. Especially I’d like to thank Joe, W4TV and Pete, N4ZR for all information they have put on the web, reflectors and in personal e-mail to us. Thanks to Tom, N1MM for adding the microHam protocol to N1MM logger.

This information is placed on the web in the hope that it may help others in setting up the microHAM MK2R+ SO2R controller. The setup below is working for us but might not work at your place. The MK2R+ is a very complex hardware/software combination as it can be set up in so many different ways.

73’ Thomas

General information

Firmware updates and router versions

It is neccesary to have loaded the CORRECT firmware version for each version of Router. Each Router install file includes a firmware file. However, Router will only prompt for to load firmware if the installed version is OLD (reverting is not expected). Comparing the change logs for Router and the firmware for the MK2R. Whenever firmware is changed, new “Power-up settings” must be saved to the interface (except USB II) and power must be cycled in order to properly initialize the controller in the interface. The firmware gets loaded to the interface – leaving the file on the computer does no good. Having a mismatch between firmware and Router will almost guarantee problems with PTT and switching.

Router tells the firmware of the MK2R at the bottom of the router Screen. Just before the Winkey rev.

Vista and Windows 7, 8, 8.1, 10

Router 7.2.4 and up (now 8.5.6) work with both 32 and 64 bit versions of Windows 7, 8, 8.1, 10.
If you have performed an upgrade installation, disconnect all USB devices, start Router and “delete all” virtual ports then close Router and run the uninstaller from the microHAM group in the Start menu. After uninstalling, shutdown the computer – DO NOT allow the computer to hibernate or sleep.
Reboot the computer, download a fresh copy of Router 7.2.4 from the web site and install from the fresh file. Once the install is complete, connect the USB cable to the microHAM interface, start Router, create the necessary virtual ports and configure as needed.
The Windows 7 upgrade installation appears to damage some of the driver files required by Router. The effected drivers need to be removed and reinstalled. The only way to remove files that are in use is to do a complete reboot.

Router software

The exe file (download) is the same for update or fresh install.

Prevent Windows and USB ports/hub from invoking sleep mode

These steps appear to prevent Windows from invoking sleep mode or performing any hardware power down actions with the USB devices

1) Always set the Windows Control Panel “Power Options” to”High Performance” or “Maximum Performance” depending on version.
2) In the “High Performance” option
a) click on “Change Plan Settings” and set “Put the computer to sleep” to NEVER.
b) click on “Change advanced Power Settings”, select “USB Settings,” followed by “USB Selective suspend setting” and set Selective suspend to “disabled”
3) In Windows Device Manager, Universal Serial Bus Controllers double click on *every* USB Hub (both USB Root Hub and Generic USB Hub), select the Power Management Tab and clear (uncheck) the box marked “Allow the computer to turn off this device to save power”

When closing the computer, always do a full (power off) shutdown – do not select sleep, hibernate, or suspend.

These settings are designed to prevent the computer from entering sleep mode and thus turning off the power to USB ports. Note: it is the USB Hubs – both Root Hubs which interface to the processor I/O bus (Root hubs are built into the motherboard and found on PCI or PCIe expansion cards) and “generic hubs” (the hubs inside multi-port devices or external USB expansion boxes) that control power to the USB ports – *not* the USB Serial Converters themselves).



Proposed Virtual Port numbers

Note: The absolute port numbers do not matter. The key is consistency – the same port number must be used for a specific function every time it is used. The port numbers below will be used (as proposed by Joe, W4TV).

COM 3 – WinKeyer (it is best to assign WinKey to the lowest port to avoid loss of CW if another port is activated for CW)
COM 4 – Radio #1 (PTT and Footswitch is optional on this port)
COM 5 – Radio #2 (PTT and Footswitch is optional on this port)
COM 6 – Digital #1 FSK and PTT for Radio #1(assign Radio 1)
COM 7 – Digital #2 FSK and PTT for Radio #2(assign Radio 2)
COM 8 – MK2R Protocol port

The porposed ports below are used at PA1M where PA1T does not have COM 3 and also uses the LPT port.

Clean up your Com Ports

And for those who want to clear out those low number ports that don’t need to be cluttering up your Device Manager listing anymore, you can follow this

1. Click Start
2. Click Run
3. Type cmd.exe in the textbox and click OK
4. Type set devmgr_show_ nonpresent_ devices=1 and hit ENTER
5. Type cd\windows\system32 and hit ENTER
6. Type start devmgmt.msc and hit ENTER
7. When the device manager opens, click the View menu
8. Click Show Hidden Devices
9. Click on the + sign next to the Ports to see the full list of Com ports being used.
10. Highlight the port you wish to delete and then press delete. Accept when asked to do so and continue with any more that you wish to delete.

This works. I just did it on my computer and I had 3 com ports still assigned to an EZMaster I tried to get working almost 2 years ago.
If you delete something by mistake, the next time you reboot, the device will be reinstalled – although with a much lower com port number this time.

73, Bob W5OV

Ouch it’s not working – please check
a.. Confirm that you have selected the correct soundcard for audio in N1MM and microHAM Router.
b.. Confirm that you have selected the correct wave file path in N1MM Logger.
c.. Confirm that you have the correct audio connections between microKEYER and the soundcard (all three cables).
d.. Double-check the preamp setting (jumpers) in the microKEYER (enabled for dynamic mic, bypassed for electret mic).
e.. Confirm that any wave files are being played back on the left channel of the soundcard (microKEYER uses left only).

a.. For debugging purposes it is very convenient to connect a set of powered computer speakers in parallel with the soundcard “Line Out” (microKEYER SOUNDCARD OUT jack).
b.. If you hear the proper audio but it doesn’t reach the radio, the issue is in microKEYER’s audio switching …
c.. if you do not hear the right audio the issue is in the software (N1MM Logger or Windows).
d.. Refer to the Set-up Guide for microKEYER and N1MM Logger for Router configuration information and the N1MM Logger manual for N1MM configuration information.
e.. microKEYER/N1MM Set-up Guide is available through the “Download Documents” link in Router’s “Help” menu.

Q. Where are the MK2R settings stored
A. Using Router version 5 and up: C:\Documents and Settings\All Users\Application Data\microHAM\cfg\

Q. How to set up WYH on the MK2R

A. When WYH is selected it simply switches the headphone feed to the USB Audio CODEC andrecords ‘what you hear’. The audio settings selected by the RECORDING/DIGITAL LEFT/RIGHT controls are ignored. WYH is designed to be able to record ‘what you hear’.

WYH is headphone audio and will be effected by the radio volume control.

Q. How to setup SSB
What kind of microphone are you using and how is it connected? You MUST set the jumpers correctly on the Live mic preamp based on the type of microphone and you must configure the soundcards correctly in Router.

If you can play a wave file via USB Voice CODEC, the CODEC driver is installed (it is built into Windows and not a microHAM driver). However, N1MM Logger REQUIRES that the Audio Settings tab (in N1MM Logger) is set up properly to select the correct inputs.

Further, if your computer has a motherboard soundcard that uses the RealTek HD audio chipset (or an add-in soundcard by SoundMax with the RealTek HD audio chipset), N1MM Logger will often select the wrong input unless USB Voice CODEC is the Windows Default sound device (bad idea) because of issues with the non-standard RealTek driver.
Finally, MK2R+ MUST be in VOICE mode and the audio switching must be correct so that the microphone is switched to the sound card when you are recording … there are three possibilities depending on whether you are trying to record on air or not and whether the logger activates PTT.

MK2R+ audio switching should be CmCmA or CmCmCm and you should not press the PTT while recording. Radio(s) must be in SSB mode and Router must know that (black box around the VOICE switching configuration).

Q. My TX audio is not working anymore
Uninstalling and reinstalling Router will not change a thing with the CODECs. You are wasting your time.

Confirm that the microphone is connected correctly, the proper microphone input (front or back) selected, the correct CODEC assigned to the Voice and Digital/Recording sides of Router, and the proper CODEC assigned in the audio switching.

It is very easy to overlook the subtle difference between Voice and Audio CODEC in both the Audio Switching tab and the Audio Mixer tab.

I would also confirm that Windows has not done something strange like install another audio device, or change the order in which the CODECs are installed. Click on the Get ID buttons and be sure that Wave IN ID = Wave Out ID = Mixer ID. Confirm that the “Soundcard name in the “Get ID” box is the one you expect (that it matches the selected soundcard).

Q. TX Mic pull down does not offer “microphone” as a selection option. My laptop only has only mic in and line out.
A. If the TX Mic select box on Router does not offer a microphone chose, the sound card does not support echoing the microphone to the speaker/headphone output and you will not be able to route the microphone through the laptop sound card or change DVK messages “on the fly.”

You will still be able to record and playback messages with the N1MM Logger DVK but you will not be able to record while doing so. Configure your audio switching for ACA … this connects the mic directly to the radio “at rest” and when the hand mic or footswitch is pressed and connects the DVK
output to the radio when the computer PTT is active. When recording a wave file, do not press the hand mic PTT or footswitch.

Q What is the “blinking Busy light”
The “blinking Busy light” is a “same band lockout.” It will happen any time MK2R/Router loses CAT data from either radio and is a safety to prevent manually putting both radios on the same band (protect the rig front end). Check (and reset) your presets to find out which one has a bad radio configuration.

Q. I couldn’t find an “Apply” button or similar.
A. If you make a change, the change is applied immediately. If you want to save that change to the preset, use “Preset | Save As” to update (over write) the existing preset.
Note, you will probably want to set the VOICE/DIGITAL box on the Audio Switching TAB to “Use Voice Settings” for this weekend. Since TenTec does not include an AFSK mode in their radios/CAT command set, Router must determine Voice/Digital mode by operating frequency. By default operation between 7030 and 7045 is considered to be “DIGITAL” (AFSK).

Be sure to UNCHECK the “Mute mic on supported radios” box on the N1MM Logger Configurer “Other” tab. N1MM expects to run DVK via the AUX connector on the Orion. MK2R uses the mic input.

Q. How can I record SSB- and/or CW-QSOs in N1MM with SO2R/1R-configuration and MK2R+?
A. On CW, you can do it by selecting the USB Audio CODEC in N1MM’s configurer|Audio tab. On SSB you have to choose between the N1MM DVK and recording, because the Audio tab in the configurer does not allow you to set a different soundcard for recording and DVK purposes

Q. Function keys in SSB: Should I use the N1MM-DVK or the MK2R+ – DVK? Which is better?
A. I would use the N1MM DVK because it allows for full integration between N1MM functions and the DVK, and use a separate recording application.

Q. Which sound card driver to select in Windows
A. Windows automatically selects any newly installed audio device as the default device for Sound Playback and Sound recording. This is undesirable as Windows Sounds would be played through MK2R+ and onto the air!

For Windows 2000 or Windows XP. right click on the Speaker Icon on the task bar and select “Adjust Audio Properties” or open “Sounds and Audio Devices” in Control Panel and reset the Default device for Sound Playback and Sound Recording to your computer’s primary sound device.

For Windows Vista, right click on the Speaker Icon on the task bar and select “Playback Devices” or open “Sounds” in Control Panel and reset the Default Playback device to your computer’s primary sound device.

Q. Where is the mixer gone in the router program

A. There is no mixer in Router with Vista or Windows 7. Please see the audio set-up instructions (User Manual) for you particular interface.

Make absolutely certain that the soundcard you are using (in the computer or in the microHAM Interface) is not the Windows default device (does not have the green check in the Vista/Windows 7 Sound Control Panel) or MMTTY will not be able to select the correct (mic or line) input.

Q. I’m missing some virtual serial ports, can’t select them, can;t create them
A. First try to delete all virtual ports from within router and create them again.
If this does not help remove all virtual ports from within Windows (System from within the Configuration screen), after deleting all ports they will be automatically created again (and hopefully also the lost ones). It worked here..

Q. Do I have the Realtek sound card driver problem?
A. Select “microHAM CODEC” in the Audio Mixer tab and click, “Get ID”. If Wave IN ID <> Wave Out ID <> Mixer ID (ie. they do not have all the same number) you have the “Realtek problem” where the application is using the Mixer ID instead of the WAVE IN ID to select audio input.

Q. Using CAT and 2nd CAT ports
A. As two programs CAN NOT under any circumstances look at the same port simultaneously. That is the reason for the CAT and 2nd CAT ports in Router … the primary logging/control program looks at the CAT port to control the radio and the secondary program (e.g., CW Skimmer, Spectravue, PowerSDR, etc.) looks at the 2nd CAT port for Icom “transceive” broadcasts, Kenwood IF data or slow speed (< 500 msec) polling with older Yaesu rigs to get the operating frequency for synchronization.

Q. Where are router’s settings and presets stored?
Router’s settings and presets are stored in the Windows registry. The stored settings are updated when Router is closed. Any “registry protection” or “registry backup/restore” program will prevent saving the settings (by restoring the previous state). In addition, if Router does not close properly, the settings will not be saved.

Q. How works the virtual serial ports

A. The Eltima virtual serial port is a software interface e.g., it provides software equivalents to the various buffers and registers of an 8250 compatible UART – for OEM specific hardware and software. For Router, the Eltima VSP code provides an interface compatible with the Microsoft Communications Toolbox. The data to/from the foreign applications is transferred to Router which reformats it into a microHAM proprietary multiplexed data stream (Radio_1 CAT, Radio_2 CAT, Control – which includes the various PTT, Footswitch, audio routing, and PC generated CW flags – and WinKey channels) and sends it via a DLL interface at 230Kbps through the USB port and the FTDI UART in the interface to the microcontroller in the specific interface.

The microcontroller then demultiplexes the data and distributes it to the appropriate process in the controller. CAT and WinKey data is put in standard ASCII form and handled by UARTS in the controller. The various control flags are acted on by the firmware to generate the necessary internal or external controls.

If Router and the microHAM interface are not running, the VSP should either not exist (Router not running) or return an error (interface not running).

Virtual ports created and defined by Router can only be used to communicate with or control devices that are attached to a microHAM interface. Just as with a “real” port, only one program at a time may open a virtual serial port and no two ports (virtual or real) may have the same address (COM number).

Q. MK2R+ and Vista / Windows 7, 8, 8.1, 10
A. MK2R+ works with Vista. However, since Vista no longer allows an application (Router) to control the audio endpoints, it is more difficult to set-up. In effect, the user needs to use the Vista Volume Mixer to select each device/endpoint and set the level of that endpoint for each individual application (e.g., separate settings for Writelog, N1MM, WinTest, DX4Win, MMTTY, DXLab Suite, etc.).

With Vista / Windwos 7, 8, 8.1, 10 you will need to make “USB Voice CODEC” (headset microphone) the default input device for the OS and “USB Voice CODEC” (“headset speaker”) the default output device for the OS. Disable all Windows sounds and replace the default “ding” with “silence.wav” Then set the N1MM Audio device to “default.”

Q. No microphone audio – what to check..
1) what microphone are you using?
2) is it connected to the front or rear mic jack of the MK2R+?
3) is the front panel switch in the correct position?
4) if the microphone is an electret mic do you have the soundcard preamp bypasses?
5) if the microphone is a dynamic mic is the soundcard preaamp enabled?
6) Do you have the correct soundcard (USB Voice CODEC) selected for voice operation (left side of the audio mixer tab)?
7) Did you click on the “REC MIXER” button, confirm that that the mixer for the correct soundcard is opened and the microphone is not muted?
8) you should not press the PTT/footswitch when setting the REC MIC level and “On Air Recording” should not be selected on the DVK tab.

Q. Reset MK2R/Microkeyer/Digikeyer settings
Save Power up settings to reinitialize the EEPROM in microKEYER, close Router to save the settings and then restart Router.

FSK or CW messages
PTT ON/OFF is not supported as an embedded command in the MK2R. Use the F10 key from the PS/2 keyboard.

RF problems with my MK2R
The bypass modification for the microKEYER II has not been evaluated for the MK2R+. However, due to the layout it will not be as simple as the microKEYER II version. Circuit grounds for the USB “core” and the balance of MK2R+ are separated and there is no conveniently located place for field installable bypasses.

Difference uRouter K3 VS Patched K3 two radio settings?
There is a difference in the way the two settings behave when the radio is turned off. The “K3” setting will buffer polling data from a connected logging program as long as it runs. The “patched” setting will discard polling data if the K3 does not respond (is turned off).

Using one or two power supplies?

You should *ABSOLUTELY NOT* connect your MK2to the same supply as your radio. Using a common power supply for MK2R and *any* transceiver and any accessory that handles audio allows transceiver return currents to find their way back to the power supply via the accessory and “modulate” the power supply reference for the accessory.

In fact Kenwood *in all of their manuals* specifically instruct that a “TNC” should never be connected to the same power supply as the transceiver.

The issue is simple, if an accessory that processes or generates audio for transmission is connected to the same power supply as the transceiver, some portion of the transceiver “return current” will flow through the accessory during transmit. That current will vary in proportion to the transmit power level and will “modulate” the power supply reference in the accessory. This modulation of the ground reference will appear *IN SERIES* with the audio to the transceiver and will sound *JUST LIKE RFI* (the audio will sound much like directly rectified SSB – which it is in effect).

microHAM have gone to great lengths to isolate the audio, digital and power supply grounds to minimize ground loops and other sources of hum. However, when the user then connects the interface in series between the transceiver and transceiver power supply, there is nothing that can be done to eliminate the power supply modulation.


N1MM logger

F1 the ‘old’ way

In S&P F1 sends your Call and not place you into Run mode and CQ.


N1MM and Skimmer spots

N1MM Logger has de-duping built in for Skimmer spots. Being in the US, I personally prefer using a cluster like K1TTT, which supplies both traditional spots and RBN spots, and which runs ARCluster Version 6 software, which includes Skimmer-specific filters. for example, I use a filter like this to limit Skimmer spots
to stations that are near me, and to cut down on busted spots:

SET DX FILTER call=n4zr OR (SKIMMER AND UNIQUE>2) and (spotterstate=md
OR spotterstate=pa OR spotterstate=va OR spotterstate=WV).

73, Pete N4ZR

“PTT line” (usually RTS) on a serial port

One note with regard to N1MM Logger (and other logging/control software) … DigiKeyer and other microHAM interfaces responds to the “PTT line” (usually RTS) on a serial port. The interfaces do not respond to “PTT via command.”

In using N1MM with microHAM Router, it is best to set the PTT delay in N1MM slightly longer than the PTT Lead (microKEYER, microKEYER II, MK2R/MK2R+) or PTT Delay (DigiKeyer) parameter. N1MM Logger will begin producing audio (AFSK or Voice macro) when its delay time expires. If Router’s PTT Lead/PTT Delay is longer, the transceiver will not have switched before
N1MM Logger starts generating audio. A good starting point is to set N1MM Logger PTT delay to 20 msec and Router’s PTT Delay to 10 msec. If the particular configuration does not require a delay for receive antenna switching (LNA PTT) and the logging/control program provides its own PTT delay (like N1MM), it is even possible to set Router’s PTT delay to zero (0).

Always uncheck “PTT via command” when using microHAM Router. If “PTT via Command” is used, the PA PTT and/or LNA PTT outputs on the microHAM interface are not usable because Router and the keyer have no way of knowing that N1MM Logger has commanded the radio to begin transmitting.

The PTT delay setting in N1MM Logger and the PTT lead or PTT delay settings in microHAM Router should be adjusted for the particular installation. The PTT Lean/PTT Delay setting in Router should be less than the PTT delay in the logging program. Router’s PTT Delay will control the delay between PA PTT/LNA PTT activation and the activation of the transceiver PTT. The logger PTT will control the delay between activation of PA PTT/LNA PTT and the start of RF.

If the PA relay was very slow one might set PTT delay in N1MM Logger at 40 mSec and set PTT Lead/Delay in Router at 30 mSec. In that case PA PTT would activate as soon as the operator pressed an F-key while the radio PTT would activate 30 mSec later and RF (audio/CW) would start 10 mSec after the transceiver PTT. With hand mic PTT, the amplifier would still receive its PTT command 30 mSec before the transceiver to allow time for the (slow) relay to switch and settle.

“Err 4 – Opening recording device” when recording
Config option “Record QSOs”, the status line of the QSO entry form displays “Err 4 – Opening recording device”.

Setting up the N1MM Config \ Configurer \ AUdio tab:
1-Zero or Single Card…
Select Device = Realtek AC97 Audio. (See Note 1)
Select Input Line = Microphone
Select Line to Mute = Microphone
Recording bits = 8 or 16 (do not select 24 or higher)
Recording sample rate = 8000
Recording channels = 2
Max recording length = 30 seconds
Radio Input Port = line in

Note 1: If “Default” is chosen, the drop-down boxes for the remaining lines/ports are empty.

Winkey settings
Winkey lead time set to 2 will not crop the first CW element as when set to 0.

Station Master information

Quick Guide

  • Connect iLink cables between MK2R and Station Master
  • Check the “iLINK Couple” (frequency source) setting in Ports tab Station Master.
  • On SM: Go to MENU mode (push MENU button for more than 1 second and Select *** CAT *** (SM will follow radio)

Relays Station Master (Rotator interface adding a Tailtwister rotator)

All of the relays in Station Master are Forward model N4100HS3DC12. The specification on the case says: 3A/125VAC/30VDC.

Although the Tailtwister is specified at 2.25A operating, remember that the starting surge will be higher and there will be a substantial voltage “kick” on when the relays. The relays in the Station Master won’t handle the currents required by the Tailtwister, so it was necessary to use some SPDT power relays with 20A contacts and 12V coils that I obtained at a local electronics surplus outlet to buffer the Station Master relays. The power relay NO contacts were simply wired across the CW, CCW and Brake switches in the Tailtwister control box. The SM Analog Input was taken directly from Terminal 3 of the control box and the Analog Ground was wired directly to Terminal 1 of the box. Below in detail how to add a Tailtwister rotator.

I’ve got my Station Master working great controlling a Tailtwister. You MUST use three 12V coil external relays with contacts rated for 10A or better to interface with the Hy-Gain box. The currents involved, especially with the brake circuit, are far too high for the SM relays to handle. Here’s how you want to connect the thing up:

1. Wire the first relay, the Brake buffer relay, with its normally open (NO) pair of contacts directly across the NO contacts of the Brake switch in the Hy-Gain box. You can just put the relay contacts in parallel with the wires that are already on the Brake switch.
2. Wire relay number 2, the CW buffer relay, with its NO contacts across the CW Rotation switch. Connect the common of the relay to the 24VAC line at terminal 2 of the terminal strip on the rear of the control box. Connect the NO contact of the relay to terminal 6 of the control box terminal strip.
3. Wire relay number 3, the CCW buffer relay, with its NO contacts across the CCW Rotation switch. Connect the common of the relay to the 24VAC line at terminal 2 of the terminal strip on the rear of the control box, or just connect it to the common of the CW rotation buffer relay. Connect the NO contact of the relay to terminal 5 of the terminal strip.
4. With the buffer relays taken care of, it’s now time to wire the controls for the relays from the Station Master. How you do the interconnect is up to you. I made a “dongle” using a DB9 female connector that protruded from the rear of the control box and then built a mating control cable with a DB9 male connector on the control box side and a DB15 male connector that connects to the Station Master ROTOR port.
5. The positive side of all three buffer relay coils should be wired to the +12V supply from the Station master that is provided on Pin 1 of the DB15.
6. Wire Pin 3 (CW-COM), Pin 6 (CCW-COM) and Pin 12 (AUX-COM) to Pin 9 (Power Ground) at the DB15 connector plug. Also be sure to ground the shell of the DB15 connector.
7. If your relays don’t have them built in, wire snubber diodes across the relay coils. Connect the diode cathode to the positive coil terminal and the diode anode to the negative coil terminal. General purpose diodes such as 1N914, 1N4148 or rectifier diodes such as 1N4001, etc. will work equally well. We need these to protect the relay contacts in the Station Master from the inductive spike generated when the buffer relays are switched.
8. The negative terminal of the Brake buffer relay coil should be wired to Pin 4 (AUX-NO) of the DB15.
9. The negative terminal of the CW buffer relay coil should be wired to Pin 10 (CW-NO) of the DB15.
10. The negative terminal of the CCW buffer relay coil should be wired to Pin 13 (CCW-NO) of the DB15.
11. The Analog In at Pin 15 of the DB15 connector must be wired DIRECTLY to the high side of the rotator position pot at terminal 3 of the terminal strip on the rear of the control box. Try to keep this wire short and route it well away from the large 24VAC power transformer in the control box. This transformer is a fierce radiator of 60Hz, and we don’t want it getting into the Station Master’s sensitive sensor input.
12. The Analog Ground at Pin 8 of the DB15 connector must be wired DIRECTLY to the control box common at terminal 1 of the terminal strip on the rear of the control box. Don’t be tempted to connect it the control box chassis. The (rather poor) design of the Hy-Gain control box returns the substantial brake solenoid and motorcurrents to the power transformer via the chassis, and connecting the sensor common anywhere but directly to the rotator position pot wiper at terminal 1 will create a ground loop and cause 60Hz position measurement noise. Use as short a wire as possible for this connection as well.

This hookup will work fine. I’ve been using mine for several months now with no problems. There is one oddity of interfacing the Station Master this way: The CW and CCW direction LEDs on a Tailtwister control box front panel will NOT illuminate when the rotator is turning. This is because the normally closed contacts on the rotation switches in the control box short the LEDs.

I hope this information is useful. If there is any interest I will be glad to post a drawing in the group Files area detailing the interface schematically.

Randy, W8FN

Trap alarms
Extend the “Report time” setting on the “Display” tab to the maximum and make “Alarm” the only Report selection for the bottom line.

KEY IN TOO LONG – Key IN can be found in Router on PA & Sequencer subtab from Antenna Switching& PTT sequencer in Station Master
Cahange the setting or deselect when not used. Dont forget to Store this information to the Station Master…

Antenna lock out between Station Masters…. NO
With two Station Master controllers, one unit does not know which antennas are selected by the other controller. There is no provision for sharing rotors between the units – but the firmware/software continues to evolve.

Resource sharing
Networked resource sharing of rotors, SteppIR antennas, etc. are features planned for Station Master Deluxe.

Rotor control
With the present software, rotor control is tied to selection of an antenna on the rotor. There are two “solutions” – first use a separate RS-232 interfaces rotor controller with the “auxiliary” port or second define all antennas as being on the rotor.
Antenna rotor resources are not shared among multiple Station Master controllers. The rotor control, SteppIR control and amplifier control are bound to the Station Master and transceiver to which it is connected. Antennas are shared using a Double Ten Switch with each Station Master controlling one “side” or set of outputs.

Stack switch
Station Master can interface with a stack switch by defining each configuration as a separate antenna. However, if you do that you will need to design an external relay network to switch the stack switch control lines between the two Station Master controllers so that the “active” Station Master is controlling the stack switch.

Vox timing
VOX Timing is controlled entirely by the transceiver. PA PTT is a copy of the PTT IN signal, LNA PTT is a copy of the PTT IN with a release delay set by the PTT Tail parameter. As relay keying is rather slow, always (when possible) enable solid state keying instead of relay keying (it could solve hot switching ).

I lost my CW keying with my paddle (using iLink and coupled to MK2R+/microkeyerII, I lose the
( ilink couple = none, and keying the rig with the paddles worksagain)
Check the inhibit inputs (make sure they are not enabled if you do not have hardware that supports inhibit) and make sure you do not have any other frequency dependent device that might be “out of range.”


microKEYER (Version I has been discontinued)

Audio connections

microKEYER computer
Soundcard OUT Line Out
Soundcard IN Line IN
Soundcard Mic Mic IN

Elecraft K3

No audio on line in

CAT noise : Buzzing sort of doo doot sound in the background of the record
This is CAT polling noise. The K3 has RF chokes in the ground leads of the RS-232 port, the ACC port and the mic return. This results in common mode noise if the ground ring of the Foster mic connector is not tight and the KIO3 board is not seated properly. The polling noise is particularly significant if the rear panel (3.2mm) mic input is used because there is NO chassis ground on that jack other than through the RF choke.

Check all your grounds! With the K3 it will help to add jumpers between the ground/common pins of the DB9 (RS-232 – pin 5), DB15HD (ACC – pins 5 & 12) and Foster (Mic – pins 7 and 8) connectors and the shell of the connector. This allows the “ground” currents to reach the chassis directly rather than see approximately 4 Ohms in the common leads.

Echo when doing SSB
Check Playback Line In control being un-muted (audio mixer). the computer is almost certainly echoing Line > In to Line Out. Right click on the task bar speaker Icon and select “open Volume Control.” Select options | Properties | Playback and the miser device for the soundcard to which microKEYER/K3 is connected. Look to see if Line In is one of the “Volume controls” options … enable it and click “OK.” Now, make sure the Line IN level is all the way down and that channel is muted (note Line IN may be identified by the color of its jack). Update Router’s presets so the Line In is always muted on the playback side. microKEYER does not have any ability to connect Line In to Line Out.

Memory recall acting like band select
Memories 0-9 are quick memories which are accessed by the commands M-V and then the keypad number. Programme each of those memories with each band 160 thru 6 metres so changing bands without having to use the up/ down button. Programming the M1 thru M4 buttons to provide an additional four frequencies in each band is a bonus. You could even program VFO A and VFO B separately which gives access to up to nine frequencies (each with pre-programmed modes) quickly accessible for each

Access memories 10 and upwards
Press the M-V command and rotate the VFO A knob to get to the memory number you require. To program a memory with the current VFO A frequency, mode and
selectivity use the V-M command and then either press the keypad number to be programmed (0 thru 9) or rotate VFO A for memories 10 and upwards to select the number you want and then press V-M again.

K3 equalizer sound settings
It is quite common for the transceiver audio amplifier to have a 3 to 6 dB per octave roll off above 1000 Hz. While this helps reduce the impact of high frequency hiss, it has a negative effect on intelligibility. Elecraft have paid attention to audio response and achieved a very flat response from 50 Hz to 4.5 KHz (where the audio lowpass filter begins to take effect).

If you want a more “mellow” sound in SSB, set RXEQ for -3 at 1.6, -5 at 2.4 and -6 at 3.2. This will duplicate the 3 dB/octave roll off found in many other rigs. A 6 dB per octave roll off would be -6 at 1.6, -10 at 2.4 and -12 at 3.2 but that sounds a bit “muddy”.

For the CW operator, a more aggressive RXEQ may be appropriate to simulate the “peaked” CW response of some much older rigs. Possible settings are: -16 at 50, -6 at 100, 0 at 200 +3 at 400, 0 at 800, -6 at 1.6, -10 at 2.4 and -12 at 3.2 with good effect. The 1.6/2.4/3.2 numbers are again, the 6 dB/octave roll off while +3 at 400 gives a slight peak in the middle of the CW passband and -16 at 50 simply gets rid of low frequency hum/rumble.

Icom radios

CAT noise
With CAT noise in the Icom transceivers, check the ground connection on the “Remote” jack in the transceiver and on the shell of the “Remote” plug of the transceiver interface cable. There have been several reports in which the ground trace on the CAT (remote) has been opened. If the CAT return is open, CAT data will return through the ground lead of the ACC jack and can effect the “line” input which seems to be always on in Icom radios except the IC-7800.


Kenwood radios

No audio on SSB
With Kenwood radios you need to be aware of operating frequency and the “Digital Band Map.” If the “Voice/Digital” box is set to “by frequency,” audio and PTT settings will be set to either the Voice or FSK/Digital settings based on the operating frequency (Digital Band Map). In addition, most Kenwood transceivers require PTT_2 on digital (ACC jack audio input) and PTT_1 for Voice (Mic connector). Audio Routing C and A are appropriate with PTT_1. Audio Routing B generally requires PTT_2 which mutes the microphone.


All other Radios

CAT noise
The cat data reports are also more common among those users with non-Icom (dynamic) microphones as they generally run much higher “mic gain” levels which increases sensitivity at the line in.


Sound recording

N1MM Logger will not record QSOs with MK2R+ because its recording function can not be assigned to any soundcard other than the one being used for DVK (USB Voice CODEC in MK2R+). The only way to record contest audio with N1M Logger and MK2R+ (or a second soundcard) is to use separate software (like RecALL) to do a continuous recording of USB Audio CODEC or the second soundcard.

The recording in that case will depend on the transceiver. Some transceivers had both receive and monitor audio on their “Line Out” others only have receiver audio. Some have only main rx audio; some have mixed audio; some have dual audio.

You would still need to use a separate application since N1MM Logger can’t select an input on any card except the one being used for the mic input/output since it manipulates the hardware mute/select controls and virtual audio cables can’t create inputs that are not physically present. In fact, most VACs behave exactly link the USB Voice CODEC in MK2R+ – they are a single input/output device.

N1MM Logger expects a line input on a single soundcard. MK2R+ has two soundcards – one for the mic/DVK and one for digital modes (Line In/Line Out).

The solution has always been to allow the user to specify an arbitrary soundcard for the “record QSOs” function. It would also help those with “simple” soundcards that
lack separate mic and line inputs but so far the N1MM development team have not made that change.

N1MM soundcard options

Normally if you are using option 1 or 2 for a single sound card and one or two radios you would put the radio line-out to the sound card line-in and select line-in for the radio input port. The input line would be the microphone as would the line to mute, then plug the mic into the microphone input so you can record messages on the fly. N1mm will automatically switch from recording qso’s on the line-in to recording from the microphone when you do ctrl-shift-fx.

The problem comes when you try options 3 or 4, while I think the ocx could handle recording and so2r switching at the same time there could be some confusion about what is being recorded. It can only handle recording from one source at a time, so it couldn’t record from the line-in for one radio and the cd-player input for the other at the same time…. so that is why I suspect the radio input port is grayed out for those options… but apparently the record qso’s capability wasn’t turned off and is conflicting with something.


Realtek sound card drivers and MK2R+’s USB Voice CODEC

One soundcards installed (only Realtek)

This screenshot file explains how to get around a problem caused by some Realtek sound card drivers (used for Realtek and some Soundmax cards and onboard audio components) when trying to use the MK2R+’s USB Voice CODEC. I know this sounds nuts (after all, the MK2R+ uses its own sound cards, right?), but bear with me.

Certain sound cards and motherboard sound card components made by Realtek and Soundmax (which uses the Realtek drivers) prevent proper operation of features such as on-the-fly recording of DVK messages. There’s a lot of magic here about ID numbers and such, but instead of getting into that, here are some easy step-by-step screenshots to get you going.

If you have this problem, the usual symptom is that N1MM will record an empty file when you try to record with Ctrl+Shift+Fx.

First, in N1MM logger, go to the Audio tab in Config|Ports,other


Select the USB Voice CODEC as the Device. The only inputs it has are Microphone. Don’t worry about the Radio Input Port – N1MM can’t currently record QSOs with the Audio CODEC anyhow. Just set it up like this.

Now open Windows Control Panel, and select the Sounds and Audio Devices tab.

N4ZR-Realtek-Audio2.jpg N4ZR-Realtek-Audio3.jpg

Click on the Audio tab first. Set the USB Voice CODEC as the Default device for BOTH playback and Recording, and click Apply, then OK out. Now click the Sounds tab.

Normally, the Sound scheme will be identified as Windows Default, but if you leave it alone, the Windows sounds (like the File not found “clunk”, for example) may wind up in your recordings or even go out over the air. To prevent that, you need to create a new scheme. Starting from the Windows default scheme you select each sound in turn from the Program events list, and assign “None” to it. Then save the resulting scheme under the No Sounds title. Apply it and OK out.

Now go back into the Router, and make sure that the Audio Switching tab has CmCmCm set for Voice, and that the left channel is selected for radio 1.

That’s all there is to it. Now when you record DVK messages on the fly (by pressing Ctrl+Shift+Fx), your microphone audio will reach the Voice CODEC, and playback will work normally as well. Probably the best place to monitor your voice level is on the Audio Mixer tab of Router, in the left-hand bargraph. It has much more “resolution” than the simple indicator provided in the Info window of N1MM Logger. Enjoy!

73, Pete N4ZR

Ok I have the realtek problem

Depending on the software you are using to record the mic audio, Wave In ID <> Wave Out ID can be a real problem. You have set the default recording device to the microHAM CODEC and the default playback device to something else. The Mixer is still somewhereelse and most amateur software can not handle that condition.

Ok I have more than 3 mixers

The Windows XP mixer (SoundRec32.exe) only accepts mixers 0-3 on the command line (the way Router calls the TX or RX mixer). When you have at least four soundcards (five Mixers) in your system and microHAM CODEC is the fourth or fifth mixer, it can not becalled directly with the TX Mixer or RX Mixer button.

Two soundcards installed (disable Realtek and use the other..)

The issue with the RealTek HD Audio system is that RealTek creates two separate mixers: RealTek HD Audio Input and RealTek HD Audio Output.

Windows assigns the Audio Output as Mixer 0 (Windows Default) and Audio Input as Mixer 1. This results in a mismatch between the Wave In ID, Wave Out ID and Mixer ID for not only other soundcards but also the Wave Out device. For example a system with RealTek HD on the motherboard, Sound-Blaster Audigy 2 ZS, microHAM microKEYER II and microHAM MK2R+ looks like this under Windows XP (my own “testbed” system):

ID Wave Out Wave In Mixer
0 RealTek HD Out RealTek HD In RealTek HD output
1 SB Audigy 2 ZS Audigy 2 ZS RealTek HD input
2 USB Voice CODEC USB Voice CODEC Audigy 2 ZS
5 n/a n/a USB Audio CODEC

It is possible to force “normal” behavior by defining the desired soundcard as the Windows Default (with all the issues of “Windows sounds” impacting the radio and other software screwing with the audio settings). However, with a RealTek sound device installed, the HD Input Mixer will almost always take up the “Mixer ID 1” position and every device other than the default will be impacted by the Wave/Mixer mismatch.

N1MM Logger addresses the Wave In and Wave Out devices based on the Mixer ID. In the system documented above, setting N1MM Logger to use the microHAM microKEYER II (microHAM CODEC) results in an attempt to use the output and input devices attached to the “USB Audio CODEC” (the digital/recording input of microHAM MK2R+). Attempting to “cheat” by telling N1MM Logger to use “USB Voice CODEC” also fails because USB Voice CODEC has no “Line” input.
WriteLog will function in this environment because it addresses all of the systems inputs and outputs individually rather than through the mixer.

So when having two sound cards (Realtek onmotherboard) disable the Realtek in the motherboard BIOS. Use the other soundacrd installed and make it the “Windows
Default.” You can then allow Windows to access the default card without impacting “microHAM CODEC” and N1MM Logger should not have any problems selecting inputs since the Mixer ID will point to the correct end-points. This is exactly what I would do to prepare my test system for daily use (I leave the ReaTek enabled for testing/evaluation).

This situation is not restricted to systems with RealTek hardware. It sometimes occurs with old modems that support telephone answering/recording capabilities; they often install just an audio output but rely on the soundcard fortheir input. The Mixer/Wave mismatch also occurs in systems where the user has installed a USB Audio output only device like some of the digital audio playback “dongles.” Those devices install output mixers but no input mixer.

73, … Joe Subich, W4TV


USB-to-serial adapter

Do use a USB-to-serial adaptor that uses the FTDI chipset, the Prolific USB-to-serial adaptors often give problems.
Tthe Prolific problem is that their driver does not take care to make sure that the receive data is present when they issue a “new data” interrupt to the operating system. When they issue the interrupt before the data is actually ready software like N1MM Logger and CI-V Commander (part of DXLab Suite) get a “data pending” error from the operating system (other software using a different serial library apparently retries the “read” function until the data is present).

Some users have been able to find (or been lucky) a Prolific driver that works with their system but to date nobody has been able to point to a specific driver that works with all versions of Windows (particularly Vista) under all conditions.