KComm error message: List index (4) out of bounds

[Bill Feidt]

I'm trying to get up to speed on G4ILO's KComm program connecting from a
Windows XP computer to my K3 using the USB-to-serial cable provided by
Elecraft.  I'm using v1.5 of KComm.  The radio control functions work
fine. I have entered my call sign in the "Your call" field of the Log
settings screen.  Using the default macro file, I

   1. Connect to the radio.
   2. Enter a call sign into the Call field of the logger.
   3. Click the F1 "Call stn" button.

and the program generates this error message:

   List index (4) out of bounds

   Press OK to ignore and risk data corruption.
   Press Cancel to kill the program.

If I press OK and re-press "Call Stn" the message is sent as expected.

The default F1 macro reads,

   ^c^t
   %c de %m %m pse K^r

Wonder if anyone has run into this problem and might have an idea as to
what I'm doing wrong?

Thanks for any advice.

73,

Bill/NG3K
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

[Julian, G4ILO]

Hello Bill.

I just installed the same version you downloaded. After the program started I entered by call, and set up the comm port details for the K3. Then I connected to the radio. I selected CW mode, and opened the default macro file. I put a call in the log field and then clicked "Call Stn" and the message was sent as expected.

I have never seen that error message. I can only think that it depends on the call you entered. There is a function that looks up the call in a data table to find the country, continent etc, and thencompares it with previous log entries so it can display information like country, beam heading and whether you need to work it. It does this the first time you enter a new call in the call field and then tab away from it or click a button. I think this must be where the error is occurring, but I need to know how to reproduce it in order to find exactly where the fault is.