[Dx4win] BandMap wildly wrong freq?

[Larry Gauthier (K8UT)]

Rick,

I also encountered problems tracking frequency with certain USB CI-v 
interfaces and DX4Win. Troubleshooting was made more difficult by the fact 
that some worked properly with my contest software (N1MM) but not with 
DX4Win. This bug was evident in v7, and probably still lingers in v8. You 
will see erroneous readings in the new v8 bandmap and the "Freq (KHz)" 
field.

Here's an easy test you can perform in either v7 or v8: from the main DX4Win 
dialogue window, select >Radio >Set frequency. Observe the Main Frequency 
reading as you spin the VFO. You'll probably see the correct frequency some 
of the time, but wrong frequencies most of the time. Whether that incorrect 
frequency is reflected in the bandmap or in your QSO "Freq (KHz)" field 
merely depends on when DX4Win does its polling. You can try to correct the 
problem by adjusting your CI-v interface settings in DX4Win, but there are 
some cables that DX4Win simply will not read correctly (although N1MM  does 
not have a problem).

[NOTE: when looking at that "Radio Frequency Control" dialogue window, keep 
in mind that DX4Win will not read the Icom split VFO frequency correctly . 
This is not DX4Win's problem nor a bug - it's a shortcoming of Icom's 
command language.]

-larry
K8UT
----- Original Message ----- 
From: "Mel" <ve2dc at videotron.ca>
To: "Rick Murphy" <k1mu at arrl.net>
Cc: "DX4WIN" <dx4win at mailman.qth.net>
Sent: Wednesday, August 12, 2009 21:07
Subject: Re: [Dx4win] BandMap wildly wrong freq?


> It sounds like you have the CI-V transceive function turned on causing
> data collisions. This is not recommended with DX4Win. Turn it off as per
> instructions and it should work fine. I would prefer Paul support
> transceive mode... but that isn't likely to happen soon...
>
> VE2DC... Mel
>
> Rick Murphy wrote:
>> I'm just starting out with DX4WIN 8; the rig is a IC-756 Pro III.
>> When I use the bandmap with "Follow radio" checked, it's pretty broken
>> due to completely wrong frequencies.
>>
>> For example, the rig is showing 50.125 Mhz right now. The band map
>> says "717,415.56 6m". It's sort of stable at that reading (sometimes
>> showing the right freq, usually not) until I spin the dial, then it'll
>> catch up for a few seconds until going to another bogus frequency.
>>
>> There's a pattern - usually 717,xxxx for 6m.  Or, switching the rig to
>> 20m (14,004.00) shows "475,416.56 20m". Or "1,400,526.00 20m".
>> (Currently it's swithcing between "14,005.08", "1,400,508.00", and
>> "475,416.56" in the bandmap.)
>>
>> The rig is set with default address, 9600 baud, CI-V transceive off.
>> DX4WIN set to poll at 5000 ms.
>>
>> How do I make this work right? Seems like a useful feature if it was
>> actually usable. :-)
>> 73,
>>     -Rick
> ______________________________________________________________
> Dx4win mailing list
> Home: http://mailman.qth.net/mailman/listinfo/dx4win
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Dx4win at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html