I'll be releasing the new country file the first weekend of October
(2/3) with changes. As soon as there is an official announcement from
ARRL, a new country file will be released.
Just work every PJ2, PJ4, PJ5/6 and PJ7 station you hear. Your DXCC
totals will eventually be correct when the
I've solved the problem with data clashes between DX4WIN and my Icom PW1 amp
and the IC-7600 rig by modifying the 7600 rig file in DX4WIN to stop DX4WIN
from polling the 7600 for frequency but I'm not satisfied.
DX4WIN forces me into CIV data addresses in the preferences radio files
for the
Thanks to all of you that replied to my question.
I did not realize that the F2 key function was in the preferences section. Not
even sure it was in version 5.xx, but maybe as it's been so long ago. When I
updated to version 8.03 from 5.xx nothing at all was checked under the F2 key
I loaded Logger32 and watched the frequency indicated on it's QSO window and
did not see the same anomalies that I see with DX4WIN???
What is it that Logger32 is doing right that DX4WIN is not which is handling
communications between it and my 7600 with the data clashes between DX4WIN
and my Icom
Since my PW1 and DX4WIN are forced to have the same CIV
address that's where the problem lies. Data clashes
Not true: That is not the cause of of the data clashes.
The IC-7600 only has a USB to computer interface and does not have a
RS232 like the 7700 or the 7800 which do not utilize CIV
Could DX4WIN respond to the ASCII format of the USB output when setting the
menu to DECODE?
No that won't work. Decode is not used for rig communication.
On 2010-09-24 09:54, george wrote:
I've solved the problem with data clashes between DX4WIN and my Icom PW1 amp
and the IC-7600 rig by
6 matches
Mail list logo
