[Dx4win] ICOM interfacing troubles V8.05 continued

[Rick Murphy]

On Sun, Feb 6, 2011 at 12:34 PM, N0KK,Kirk <n0kk at usfamily.net> wrote:
> Upon further examination Ive tried the following to get my radios to
> track in 8.05.
>
> As I stated in earlier emails, My interface does work tracking
> frequency. IF and ONLY if I continue to change frequency via the radios
> tuning knob. If I stop turning the tuning knob the program times out
> after 5 seconds.

On your rig, do you have "CI-V Transceive" turned on? I sounds like
you do, because that has the rig transmit CI-V messages whenever you
change the frequency.
DX4WIN doesn't work this way - it polls the rig to find out the
current frequency periodically,

If enabling CI-V Transceive allows D4W to track your rig's frequency
but turning it off stops it, then there's something either keeping the
rig from responding to the poll messages.

> I originally thought that it may perhaps be the new Byterunner PCI multi
> port card I installed into this new PC, running windows XP. To rule the
> card out I removed it, uninstalled all drivers for the Byterunner
> device. I then took a Byterunner card from another PC that works 100%
> with DX4win 8.05.

I'm not able to make sense of this. You have another PC that works
fine with this rig, interface, and DX4WIN?

> Installed it, updated the driver files and the result
> was the same operational error mentioned above. So the Byterunner card
> clearly is not the issue.
>
> Then I decided to simply connect 1 rig, ICOM 756PROIII, to the Com 1
> port on the PC rather than to connect the rig to the virtual ports set
> up with the Byterunner application. Result? Same as above..the rig will
> track only if I turn the tuning knob on the ICOM. Stop tuning...time out
> occurs.

Are you using the same CI-V adapter for all of these cases? Perhaps
that's simply broken and not transmitting polls to the rig?
73,
    -Rick

-- 
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA