[PVRCNC] Wierd issue with K3 / N1MM / telnet spotting

[Roberts, Will]

I am having another weird issue with my K3 when using N1MM and telnet spotting. It had appeared before and an Elecraft software upgrade had helped, but not cured the issue. It is now back with a vengeance. Is anyone else experiencing this?

N1MM Classic (latest version)
K3 (latest software download)
Telnet spotting using W4MR and various other local or regional nodes or VE7CC-1. (Problem seems to be independent of node used).
Spots are filtered for SS to show only domestic spots using VE7CC filters.

K3 will at times stop transmitting during a contest. Very occasionally it will show ERR FW2 error which requires a power cycle to reboot.
When clicking on a spot in the N1MM bandmap, there is a 2 to 5 second delay between the click and the K3 QSying to that frequency. It seems that the K3's processor is being overwhelmed. The problem was especially bad in the CW SS. A subsequent firmware upgrade helped but did not cure the problem experienced in the Phone SS. Disconnecting the RS232 connection to the K3 solves the transmit issue instantly, but obviously disables rig control functions.

I have slowed the baud rate between my PC and K3 to 4800baud from 38400baud with no effect. The PC is a reasonably fast Dell Optiplex desktop with 4 GB RAM running Windows XP.

Any ideas?

Tnx/73,

Will AA4NC