Information on developing contest modules for Writelog has been posted for several years: http://writelog.com/downloads/programmer-resources Look for the "contest wizard." Getting support for "local
Jim, What do you mean by the "full MMTTY window?" Try, TU Type | TNC Setup and uncheck "show control buttons area", "Show Profile Panel" and "Show Pulldown menus" as needed to adjust what you want to
Jim, Is you path to MMTTY pointing to a shortcut instead of the EXE file - or is there a shortcut in the target directory? The MMTY plug-in for WriteLog calls the exe file with some special command s
If it works in MMTTY it should work the very same way in WriteLog. SignaLink USB is a "dumb" sound card - it does not have a serial port interface so it can't do FSK. WriteLog's RTTY serial port (RT
This is a classic misunderstanding of Writelog ... stereo mode is not persistent, nor is there any need for it to be persistent. In fact, one does not want stereo/split as the default when WriteLog s
Bill, Sounds like a conflict with DTR/RTS/Handshake on the radio port. Look at the "COMn_RTS_INIT and COMn_DTR_INIT directives in the [Rigs] section of the writelog.ini file - check the Writelog help
Sounds like the Trendnet adapter uses the Prolific chipset which is known to have defective drivers with Windows 7. I suggest you look for updated drivers as the latest drivers are reported to resolv
FTDI is a chip house - many of OEMs use the FTDI chip set. The chipset is generally given in the specification (read the fine print <G>). One vendor I know of that specifies the chip set is Byterunne
The problem with the CQ rule is that it is completely unrealistic for the "multiplier radio" in M/S and M/2. None of the popular software provides a "band aware" interlock function (and interlocks -
See the example configuration for WriteLog and the microHAM interfaces available either via "Help | Download Documents" in microHAM Router or on-line at www.microHAM-USA.com/support.html. 73, ... Joe
The AA6YQ FIR512 profile is not appropriate for 75 baud in any case. The filter is too narrow. One is better served to use a wider prefilter (I like the looks of FW=200, Tap=256 for 75 baud although
Microsoft support for Windows 98 ended five years ago (July 11, 2006). I think you have supported Windows 98 for far longer than necessary. Even Windows XP and Windows 2000 are getting a bit long in
Have you configured the Left/Right radios (or VFOs in the case of SO2V)? "Radio -> This Windows is ..." in the main window menu. 73, ... Joe, W4TV _______________________________________________ Wri
What CI-V interface are you using? Does it require power via DTR or RTS? If so, have you properly configured any necessary overrides on COMn_RTS_INIT and COMn_DTR_INIT? Why are you not using the buit
Tony, Where are you selecting COM 10? WriteLog passes the COM port to MMTTY when it initializes the plug-in. Set the COM Port in the RTTYrite menu then select MMTTY as the TU Type to open/initialize
Eric, There is an option "More" in the Ports menu that shows COM9-COM16. Unfortunately, I just checked and at least in WL 10.88 and 10.90, if a port other than COM1-COM8 is selected, that port select
Icom still doesn't have a command to return the "back" or "other" VFO in *any* radio. They only just added a command to return the Split status in a recent update for the 7800 - still none in any of
George, What operating system - XP, Vista, Windows 7? 32 or 64 bit? Do you have the necessary LPT driver (DirectIO) installed and properly configured? Have you selected "DVK" in the appropriate LPT l
What operating system are you using? If all LPT port selections are greyed out, it means that WriteLog can not control the LPT port - either the ports are disabled in BIOS or you have not installed
What interface are you using? Do you have RTS/CTS properly connected and configured? Kenwood transceivers require handshake (or "fake handshake" if you are using the radio port for CW). Read the Writ