[Dx4win] BandMap wildly wrong freq?

[Mel]

I use a Microham interface... it uses USB and virtual ports and works 
fine. So some USB interfaces do work.

Heinz Goeddemeier wrote:
> I had a similar problem. My old notebook Compaq EVO N800v doesn't have an
> COM interface, so I tried to use an USB- COM interface from Belkin FSU109. I
> used it once for controlling a RET-antenna unit successfully with that
> notebook.
> Recently I revived my amateur radio activities again using then DX4WIN 707,
> but couldn't achieve a working connection to the radio YEASU FT1000MP. I
> tried also the USB on the desktop without success as well. Tried to download
> the latest driver but no success, too. I am not that experienced with
> computers, so I dug free the only COM-interface on the desktop and radio
> control worked immediately and stable. Then I tried the notebook using the
> docking station`s COM port, also with success.
> Consequently I put the Belkin USB-COM interface back into my drawer......
> 
> Seems I need to obtain a COM interface card and forget about USB-COM
> interfaces. Anyone with an idea????
> 
> Heinz DK9DA 
>  
> 
> -----Original Message-----
> From: dx4win-bounces at mailman.qth.net [mailto:dx4win-bounces at mailman.qth.net]
> On Behalf Of Larry Gauthier (K8UT)
> Sent: Thursday, August 13, 2009 1:40 PM
> To: Mel; Rick Murphy
> Cc: DX4WIN
> Subject: Re: [Dx4win] BandMap wildly wrong freq?
> 
> 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 
> 
> ______________________________________________________________
> 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
> 
>