First, the fastest way to restart/reset all the COM ports is to keep your hand off the mouse and use a text command shortcut. In the logging window, type:<br><ol><li>SETUP [Enter] (displays Interface Configuration dialog)</li>
<li>[Enter] (like pressing OK)</li></ol>The text commands are all listed <a href="http://docs.win-test.com/wiki/Text_commands">here</a>. They are also shown in pop-help if you hover over a menu item, if the <a href="http://docs.win-test.com/wiki/Menu:Help#Display_text_command_tips_for_menu_items">Text command tips option</a> is checked in the Help menu. Text commands are big time savers.<br>
<br>For the VFO incorrect frequency problem, a lot of things might explain why a rig's displayed frequency may not match what is shown in Win-Test:<br><ol><li>Yaesu rig in "MEM TUNE" mode instead of VFO mode</li>
<li>Incorrectly configured COM port handshaking (use the DEFAULTS button)<br></li><li>Use of a USB-to-Serial converter based on the PROLIFIC chipset (use FTDI chipset instead -- I think Edgeport is OK)<br></li><li>OmniRig bug (but no reports on that to date)</li>
<li>New Win-Test bug (seems unlikely since so few have reported this, and I'm not aware of any recent changes to the rig control code)</li><li>AntiVirus software (or virus or other monitoring software) is periodically "poking" the COM ports (seems unlikely)<br>
</li><li>RFI in the USB/serial port lines</li><li>USB connector is bad or loose<br></li><li>USB port is powering itself off<br></li></ol>To fix the last item:<br><ol><li>Go into the Windows Device Manager (Start, Run, DEVMGMT.MSC)<br>
</li><li>Expand Universal Serial Bus controllers (click the [+])<br></li><li>Right click on each <b>USB Root Hub</b></li><li>Select <b>Properties</b> (left click)<br></li><li>Click on the <b>Power Management</b> tab</li>
<li>
<i>Uncheck</i> <b>Allow the computer to turn off this device to save power</b></li></ol>To help isolate the issue, please report:<br><ol><li>Version of Win-Test</li><li>USB-to-Serial converter brand and model (if any)<br>
</li><li>USB-to-Serial driver version</li><li>Radio Type and Model<br></li><li>All COM port settings for that radio (baud rate, data bits, stop bits, handshaking)<br></li><li>Exactly what you saw on the Win-Test screen and the radio re. frequency displays.<br>
</li></ol>73,<br>Bob, N6TV<br><br><div class="gmail_quote">On Wed, Aug 25, 2010 at 8:00 AM, Carlos Neves (CT3FQ) <span dir="ltr"><<a href="mailto:ct3fq@ct3team.com">ct3fq@ct3team.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
It happens to me too! I'm using a 1000MP MKV and ominirig connected
to an Edgeport USB device.<div><div></div><div class="h5"><br>
<br>
<br>
On 8/25/2010 3:31 PM, Dez Watson wrote:
<blockquote type="cite">
I have also noticed this problem happen 2 or 3 times each contest
but I
found a faster solution than shutting down WT.<br>
<br>
All I do is:<br>
<br>
Options > Configure Interfaces > Ok<br>
<br>
And that seems to kick-start the CAT link.<br>
<br>
I am using 3.27 a FT-1000MP MK-V and a USB - Serial converter,
again
not too sure of the chipset.<br>
<br>
73<br>
<br>
Dez, G3WW<br>
<br>
<br>
Armin Sturm wrote:
<blockquote type="cite">
<div><span><font color="#0000ff" face="Arial" size="2">Hi Bob, I believe the Radio B was
ok, but not
sure. It is true, I use a USB to serial converter but
don't know what
kind of chipset it is based on. RF is not an issue as the
transmitting
antenna is more than 500 ft away from the shack. But good
to get this
information and will check it out. I was wondering that
after restart
of the software it was working again. And yes I use the
default wintest
settings for the FT1k MP.</font></span></div>
<div><span><font color="#0000ff" face="Arial" size="2">Thanks for the fast reply</font></span></div>
<div><span><font color="#0000ff" face="Arial" size="2">Armin, DK9PY</font> </span></div>
<blockquote style="margin-right: 0px;">
<div dir="ltr" align="left" lang="de"><font face="Tahoma"><font size="2"><span><font color="#0000ff" face="Arial"> </font></span>-----Ursprüngliche
Nachricht-----<br>
<b>Von:</b> <a href="mailto:support-bounces@win-test.com" target="_blank">support-bounces@win-test.com</a>
[<a href="mailto:support-bounces@win-test.com" target="_blank">mailto:support-bounces@win-test.com</a>]
<b>Im Auftrag von </b>Bob
Wilson, N6TV<br>
<b>Gesendet:</b> Dienstag, 17. August 2010 20:19<br>
<b>An:</b> <a href="mailto:support@win-test.com" target="_blank">support@win-test.com</a><br>
<b>Betreff:</b> Re: [WT-support] Radio 1 Window in
WT4.5.0<br>
<br>
</font></font></div>
I don't recall seeing any reports like this before.<br>
<br>
Are you using a USB-to-Serial adapter? If so, and if that
adapter is
based on the "Prolific" chipset, perhaps that is the problem.
These
devices are notoriously unreliable. Perhaps new drivers will
help, or
a new USB-to-Serial interface based on the FTDI chipset.<br>
<br>
Also, what was happening on VFO B at the time?<br>
<br>
I assume that you are using the Win-Test FT-1000MP defaults:
4800,N,8,2
DTR/RTS = Always OFF.<br>
<br>
73,<br>
Bob, N6TV<br>
<br>
<div class="gmail_quote">On Tue, Aug 17, 2010 at 11:06 AM,
Armin
Sturm <span dir="ltr"><<a href="mailto:dk9py@t-online.de" target="_blank">dk9py@t-online.de</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br>
I noticed a very strange behaviour in the VFO A frequency
field of
Radio 1<br>
(FT1000MP MarkV). During the contest I was wondering that
the band
suddenly<br>
changed in the working area from 20m to 15m (although the
xcvr was
still on<br>
20m). The frequency shown in the VFO A field was something
like 12405.?.<br>
Changing the band with the arrow keys worked still fine on
the xcvr,
but in<br>
the working field it jumped to 15m again. I only could
stop the
behaviour by<br>
closing WT and restart it again. It happend 3 times during
the contest.<br>
Luckily I watched afterwords the VFO A field in the Radio
window and the<br>
frequency on the radio to make sure that when it happens
to restart WT.<br>
Hopefully WT did not log QSOs in the wrong band. Has this
been seen
before?<br>
I can remember that it happend also last year with WT3.27,
but forgot to<br>
report.<br>
73 / Armin, DK9PY<br>
</blockquote>
</div>
<br>
</blockquote>
<pre><hr size="4" width="90%">
<br></pre></blockquote></blockquote></div></div></div></blockquote></div><br>