[WT-support] win-test slow with omnirig

[Carlos Neves (CT3FQ)]

Thanks Bob for your reply,
I have only a Yaesu  configured @ 4800 baud in omnirig setup (my working 
pc is an old notebook acer4001)  ... ;-) .
When I click the spot, the transceiver changes imediatly but the   
highlight   still in  the previous callsign for a few seconds (one to 
three seconds) and that's why  sometimes I have to click twice in the 
spot callsign to be sure.
I'm using a RS-232 over IP device (Avocent ESP-4) and maybe the problem 
is there... I will check it with a true RS232 connection.

73
Carlos


On 26-04-2010 3:07, Bob Wilson, N6TV wrote:
> On Sun, Apr 25, 2010 at 1:59 PM, ct3fq at ct3team.com 
> <mailto:ct3fq at ct3team.com> <ct3fq at ct3team.com 
> <mailto:ct3fq at ct3team.com>> wrote:
>
>     Hi,
>     When using win-test with Omnirig driver, I have notice that the RADIO
>     window  take a few seconds to highlight  the spotted station after the
>     mouse click
>     Anyone have notice this? Can we configure win-test or  omnirig to get
>     it  faster?
>
>
> On a fast PC, I haven't noticed any real performance degradation when 
> using Omnirig to control my K3s instead of the native Elecraft K3 
> support built-in to Win-Test.  As you may know, using Omnirig allows 
> other programs besides Win-Test to control the radio at the same time 
> (e.g. Winrad).
>
> Check your Omnirig set-up and configure it to use the same baud rate 
> and stop bits that Win-Test would use for your particular radio.  Also 
> if you have only one rig, make sure Radio 2 is not defined.
>
> It's possible that Omnirig works better with some radios than it does 
> with others.
>
> 73,
> Bob, N6TV
>
>
> _______________________________________________
> Support mailing list
> Support at win-test.com
> http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
>    

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.f5mzn.org/pipermail/support/attachments/20100426/b68c2464/attachment.htm