[Dx4win] Icom 756 Pro II rig file

[Rick Murphy]

On Mon, Sep 15, 2008 at 12:24 PM, Jim Reisert AD1C
<jjreisert at alum.mit.edu> wrote:
> I am also running at 19.2K baud and that seems to minimize the problem for me.
>
> I *think* what happens, and Paul has never confirmed this to be the case, is that the radio (USB) interface is continuously broadcasting information to DX4WIN.  This is how the BAND field in the logbook gets set correctly when you're in the process of adding a QSO.  DX4WIN initiates a read of the radio state just before saving the QSO, and/or when you ALT-A to put out a spot.  I believe that this transaction that DX4WIN initiates sometimes collides with the data being broadcast from the radio interface to DX4WIN.  This collision can result in a garbled freuency being returned when logging a QSO or putting out a spot.

If that's the case, you can turn off the unsolicited chatter. On the
Setup/Other page, there's a setting "CI-V Transceive". Change that
from "On" to "Off".
What that does is to broadcast frequency updates so when you tune one
rig, a second rig on the same CI-V network will also change frequency.
If you've got only one rig, turning that off won't change how things
work but may fix it when DX4WIN gets confused due to the rig sending
stuff it doesn't expect.

Worth a shot, I suppose.
73,
    -Rick
-- 
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA