[WT-support] Slow response in bandmap
Bob Wilson, N6TV
n6tv at arrl.net
Sun May 7 12:11:13 CEST 2017
The WinKey and Win-Test default is 1200. I didn't think the WinKey chip
inside the microHAM was capable of working at any other speed, unless they
changed something. What version of WinKey chip do you have and which
microHAM device and which firmware?
I suggest telling Win-Test to use 1200 baud for the WinKey port.
Otherwise, the problem may reoccur. Better yet, use the radio's serial
port DTR pin for CW and don't use the WinKey at all. Win-Test can send
great CW without it.
On May 7, 2017 2:57 AM, <gt-i at gmx.net> wrote:
there was no other program oder device polling the K3. Instead, I
discovered my WinKey (via microham) was running at 1200bd instead of 9600.
I have no clue how that happened, but now the response delay is gone.
73, Gernot, DF5RF
Am 06.05.2017 um 23:42 schrieb Bob Wilson, N6TV:
> This is commonly caused by too many programs trying to poll the radio at
> the same time, perhaps with a slow baud rate.
> Exit all copies of NaP3 and any other program that may be polling the
> radio (Elecraft K3?) at the same time as Win-Test. I'm sure if you reboot
> the computer and radio, everything will be back to normal.
> For now, do *not* set CONFIG: AUTOINF to AUTO 1 or AUTO 2 unless you
> /have/ to for a SteppIR or similar.
> Bob, N6TV
> On Sat, May 6, 2017 at 2:33 PM, <gt-i at gmx.net <mailto:gt-i at gmx.net>>
> Running Wt 4.24.
> Until today everything worked fine - hmm. Now, an update in the
> frequency takes about 1-2 seconds to show up in the VFO A display
> of the bandmap, and 2 seconds more until the needle of the band
> map jumped to the new frequency. If I enter a call sign before
> that jump, it will show up in the wrong place.
> I connected the TRX to a terminal program to check the connection
> - works immediately. Also, NaP3 follows immediately.
> I wonder if there is any setting int WT which I could have messed
> up somehow?
> tnx for help,
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Support