[Dx4win] Icom 756 Pro II rig file

[Jim Reisert AD1C]

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.

I don't think this happens with real hardware COM ports because there are sideband signals which indicate when the port is busy (DTR, RTS, etc).  I thought that a virtual COM port would implement the same sideband signals, but I can't say.

Again, this is only speculation on my part, and may be totally unrelated to the real problem.

73 - Jim AD1C

--
Jim Reisert AD1C/Ø, <jjreisert at alum.mit.edu>, http://www.ad1c.us



----- Original Message ----
From: Steve Tobe <stephen.tobe at gmail.com>
To: Jim Reisert AD1C <jjreisert at alum.mit.edu>
Cc: Dx4win at mailman.qth.net
Sent: Monday, September 15, 2008 5:15:07 AM
Subject: Re: [Dx4win] Icom 756 Pro II rig file

jim:

i am using a usb interface for dx4win. but i have found a fix for the
problem, through experimentation. i just changed my baud rate to 19200
on the 756 pro II (and of course in dx4win--you must uncheck the
'default' box) and all works fine now.

thanks for your suggestions.

73

steve  VE3XO