"Use PSK modem" is disabled
This occurs if the PSK Core DLL (PSKCore.dll) is missing or corrupt. If this file is present then try replacing it with this one.
"Unable to create application data folder"
There have been a few reports that the above message appears when starting KComm. I have no idea as to the cause of it. In one case a user found that a file named 'kcomm' had been created in the Application Data folder. This prevented KComm from creating a folder with the same name.
In all reported cases, the problem was resolved by creating the folder manually. Under Windows XP the path is normally C:\Documents and Settings\<username>\Application Data\kcomm. Under Windows 7 it appears to be C:\Users\<username>\AppData\Roaming\kcomm.
Note: KComm uses for its application data folder the folder where it finds the configuration file kcomm.conf. If you install by extracting from the zip file package then this will be in the same folder as the program. This has been done principally to allow portable setups under paths other than Program Files. Newer versions of Windows do not like configuration data and other changing data to be stored under the Program Files folder.
KComm vanishes after saving a contact
This can occur when sending an eQSL if the eQSL server sends a reply that is unexpected. The solution is to disable automatic eQSLing and then to send the eQSL manually from the record editor (double-click on the entry in the log window.)
Failure to connect to radio
When you start KComm and click Connect, nothing happens and the status bar shows "Connecting...". The program does not connect to your radio. It is not frozen and may be closed in the normal way using the Close (X) button.
Failure to connect may be caused by one of the following reasons:
- The wrong Port has been selected in the Radio Control settings.
- The Port is correct, but it is already being used by another program. (In this case, you will normally see a "Cannot open serial port" message.)
- The wrong Speed (baud rate) has been selected in the Radio Control settings. Confirm that it matches the selection made in the K3 Configuration menu. (K2s can only communicate at 4800 baud.)
- Data corruption is occurring and the program is not receiving the responses it expects from the radio.
KComm has a debug option that lets you see the messages that are sent to and from the radio. If you suspect that data is being corrupted, check the Debug Window option in the Radio Control settings and then click Connect. The Communications Trace window will open.
If you are using a K3 and communication is working normally, you should see the following:
KComm sends a "PS;" command to the radio when it first connects, and expects to receive "PS1;" in acknowledgement. When this is received, the status bar changes to "Connected". If the "PS1;" is not received then no further communication is attempted.
You can also try to test communication by typing commands such as "PS;" or "FA;" to see if a response occurs. Changing the frequency using the tuning knob, or changing band or mode should produce an "IF...;" reply.
Note: To make it easier to see the responses to specific commands, KComm disables polling by default when the trace window is opened. Therefore the S meter is not updated and certain other status conditions are not reported in the user interface unless you deselect the "Disable polling" option.
Tip: If you experience a communications failure, correct a configuration error, and KComm and your radio still won't talk, turn off the radio, reboot the computer and turn the radio back on again. It appears that some communications errors can put the serial port or radio in state where it won't respond even after the configuration has been corrected. Restarting everything will resolve that.
USB serial port adapters
The most common cause of communication failure after incorrect serial port settings is the use of USB to serial port adapters. There are many different makes and models of these, but most - including the Elecraft-supported KUSB adapter - use a Prolific PL2303 chipset. Unfortunately this chipset does not emulate a serial port very well and does not work with a number of programs. It appears to work with programs developed using Microsoft programming tools that use a Microsoft component to access the serial port. Programs developed using other programming tools (which include KComm and Fldigi) often have trouble with these adapters.
My recommendation is to use a USB to serial port adapter that contains an FTDI chipset. A UK supplier USBNow states "The FTDI chipset in our opinion is easier to work with and more reliable than Prolific versions. We base this opinion on 5 years experience of selling and supporting a range of USB to Serial adapters." A Google search for "USB Serial FTDI" should produce many potential suppliers.
Radio does not return to receive after sending data macro
You must disable VOX when operating digital modes. If VOX holds the TX on then the K3 ignores the command to return to receive. This could probably be considered a bug in the K3 firmware.
Some text captions are truncated
KComm was designed using Windows XP theme, standard fonts. In some other Windows themes (including Vista), and some Linux configurations the standard fonts are larger and may not fit the space available. One solution would have been to make the whole application larger, but I do not have a big enough screen. Therefore the solution I adopted was to provide an option to change the font under Settings, Misc. By picking a smaller or narrower font you should be able to get all the captions to fit.