micro2R (and MK2R+) use WinKey 2 (either v.21, v.22 or v.23 depending on age of the unit). There is a substantial difference among v.10, v.21/22 and v.23 in the way WinKey PTT operates. Please refer
Would it make sense to use the WinKeyer USB, specifying that unit's COM port instead of MH Router's CW port in the logging program? No, it would only confuse matters. 73, ... Joe, W4TV Would it make
Looks like an issue with the CTY file in general - or in WriteLog's interpretation of it. 2Z, MZ, GZ are listed in Shetland - which should be included with Scotland for ARRL contests. 73, ... Joe, W4
Rigblaster Advantage has a *single* serial port. That port can be used for rig control (TxD/RxD), PTT (RTS) and CW (DTR) or it can be used for RTTY (FSK=DTR, PTT=RTS) *but not both*. If you are going
Is "CW in Voice" checked on the PTT tab in Router? 73, ... Joe, W4TV On 12/14/2013 9:48 AM, Courtney Judd wrote: using ft2000d with micro keyer2 ver 8.40... so while trying to change the tail on the
In order to have CW in SSB (MK II CW works during SSB), "CW in Voice" must be checked in Router's PTT tab (for transceivers that support it), and the transceiver must be in "break-in" (CW VOX must be
Per the Microham setup document for Writelog I had 'on LPT pin 16/COMM RTS' selected. I changed that by selecting 'none'. This seems to have solved the problem. My K3 now returns to receive quickly a
I don't know what you guys are doing - that makes absolutely no difference with any of my test systems. 73, ... Joe, W4TV I think I may have solved the problem. I went into setup|ports and selected t
That would tend to indicate an WriteLog initialization problem in the WinKey support code - K1EL WinKey, K1EL WinKeyer 2 and microHAM MK2R (which uses WinKey 2) - for WinKey. I would assume it might
microHAM interfaces do not provide for application controlled handshake. USB Interface II, USB Interface III, Digikeyer and Digikeyer II provide "fake handshake" (CTS to RTS) or a pull-up to +12V dep
microHAM have released version 8.5.2 of microHAM USB Device Router. This version provides a significant improvement in FSK generation for Digikeyer II, microKEYER II, MK2R+ and micro2R. 45.0 baud as
I would guess this might be a windows issue and not Writelog or the MKII. Correct. WriteLog has no audio input control, MK II has the front panel pots. Otherwise with Windows 7 and Windows 8 (the onl
It means you have not configured the sound card, WriteLog's "Sound board mixer control" and Writeelog's Setup | Sound Board options correctly for the way Windows Vista/Windows 7/Windows 8 handles sou
I sometimes see this error message from Vista too, even though I've setup the correct microHAM CODECS in the WL Sound Board window. When I go to recheck my settings the Sound Board window choices are
As *always* check the sound card selections in WriteLog's "Sound board mixer control" and the Windows "Recording Devices" settings for "Line (microHAM CODEC)" in Windows Sound Control Panel. Of cours
3. Eliminated all other Audio Codecs in the system . The MicroHAM Codec is the only audio device available to any application. Same result. *You can't do this!* Windows *must* have a default device f
I previously used "AFC ON/OFF w/CALL" but with the new OCX interface, I set "Sweep" on the AFC/ATC/PLL tab to 0.3 (not a standard choice but it can be entered manually) to limit the AFC range to +/-
Always make sure you have "COMM PTT" set to NO in WriteLog's Setup -> Ports dialog. Many rigs have a "race" condition between command PTT and hardware PTT which can result in a "hung in transmit" con
It depends on what interface you have. Both serial (DB9) and USB to CI-V interfaces are available but there is nothing in the Toshiba laptops that will control an Icom transceiver natively. 73, ... J
(2) Are there any other settings I have to adjust to make it work with USB in the 990S? Have you set the USB data rate in the TS-990 (7-01) to match the baud rate in WriteLog? The TS-990 defaults to