[DXLog.net - Support] K3 SO2V

Fred Handscombe fredch at homeshack.freeserve.co.uk
Sun Nov 20 12:40:13 CET 2016


This has happened to me several times and Im trying to work out why as 
it usually works then stops.  BTW that is on SSB

You can log that QSO with CTRL- +, the forced log command

I *think* it seems to be if you have some partial QSO entry in the 
"main" log line

I also have the situation the entry for 2nd VFO think it is on CW and 
refuses to change to SSB even though the rig is connected correctly and 
is on SSB!
That was only fixed by a total PC and programme restart!

the SO2V problems seems to come and go, try an ALT-W in the main log and 
see it it then works?

73 Fred

> Message: 1
> Date: Sat, 19 Nov 2016 16:04:44 +0000
> From: SIMON M0VKY <dxm0vky at gmail.com>
> To: support at dxlog.net
> Subject: [DXLog.net - Support] secondary keyboard
> Message-ID: <9f2a3eb8-415f-2832-6b2d-ec912a4a2739 at gmail.com>
> Content-Type: text/plain; charset=utf-8; format=flowed
> evening
> in cqww SSB using k3 with second receiver installed in SO2V mode with
> secondary keyboard, worked a treat.
> just setting up for cqww CW. i will be using VFO A for RUN and VFO B for
> s&p. dxlog is set to SO2V.
> everything works except, when i come to log a Q on the secondary
> keyboard (VFO B) in S&P mode. ALL F keys work except when i try to log
> the Q.
> ENTER dosnt work, INSERT dosnt and + key dosnt work either. it will send
> the correct string.
> the main keyboard works as it should.
> what am i missing ??
> simon, M0VKY.

More information about the Support mailing list