[WT-support] [?? Probable Spam] Re: Radio 1 Window in WT4.5.0
Bob Wilson, N6TV
n6tv at arrl.net
Wed Aug 25 20:32:41 CEST 2010
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,
1. SETUP [Enter] (displays Interface Configuration dialog)
2. [Enter] (like pressing OK)
The text commands are all listed
They are also shown in pop-help if you hover over a menu item, if the Text
command tips option<http://docs.win-test.com/wiki/Menu:Help#Display_text_command_tips_for_menu_items>is
checked in the Help menu. Text commands are big time savers.
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:
1. Yaesu rig in "MEM TUNE" mode instead of VFO mode
2. Incorrectly configured COM port handshaking (use the DEFAULTS button)
3. Use of a USB-to-Serial converter based on the PROLIFIC chipset (use
FTDI chipset instead -- I think Edgeport is OK)
4. OmniRig bug (but no reports on that to date)
5. 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)
6. AntiVirus software (or virus or other monitoring software) is
periodically "poking" the COM ports (seems unlikely)
7. RFI in the USB/serial port lines
8. USB connector is bad or loose
9. USB port is powering itself off
To fix the last item:
1. Go into the Windows Device Manager (Start, Run, DEVMGMT.MSC)
2. Expand Universal Serial Bus controllers (click the [+])
3. Right click on each *USB Root Hub*
4. Select *Properties* (left click)
5. Click on the *Power Management* tab
6. *Uncheck* *Allow the computer to turn off this device to save power*
To help isolate the issue, please report:
1. Version of Win-Test
2. USB-to-Serial converter brand and model (if any)
3. USB-to-Serial driver version
4. Radio Type and Model
5. All COM port settings for that radio (baud rate, data bits, stop bits,
6. Exactly what you saw on the Win-Test screen and the radio re.
On Wed, Aug 25, 2010 at 8:00 AM, Carlos Neves (CT3FQ) <ct3fq at ct3team.com>wrote:
> It happens to me too! I'm using a 1000MP MKV and ominirig connected to an
> Edgeport USB device.
> On 8/25/2010 3:31 PM, Dez Watson wrote:
> I have also noticed this problem happen 2 or 3 times each contest but I
> found a faster solution than shutting down WT.
> All I do is:
> Options > Configure Interfaces > Ok
> And that seems to kick-start the CAT link.
> I am using 3.27 a FT-1000MP MK-V and a USB - Serial converter, again not
> too sure of the chipset.
> Dez, G3WW
> Armin Sturm wrote:
> 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.
> Thanks for the fast reply
> Armin, DK9PY
> -----Ursprüngliche Nachricht-----
> *Von:* support-bounces at win-test.com [mailto:support-bounces at win-test.com<support-bounces at win-test.com>]
> *Im Auftrag von *Bob Wilson, N6TV
> *Gesendet:* Dienstag, 17. August 2010 20:19
> *An:* support at win-test.com
> *Betreff:* Re: [WT-support] Radio 1 Window in WT4.5.0
> I don't recall seeing any reports like this before.
> 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.
> Also, what was happening on VFO B at the time?
> I assume that you are using the Win-Test FT-1000MP defaults: 4800,N,8,2
> DTR/RTS = Always OFF.
> Bob, N6TV
> On Tue, Aug 17, 2010 at 11:06 AM, Armin Sturm <dk9py at t-online.de> wrote:
>> I noticed a very strange behaviour in the VFO A frequency field of Radio 1
>> (FT1000MP MarkV). During the contest I was wondering that the band
>> changed in the working area from 20m to 15m (although the xcvr was still
>> 20m). The frequency shown in the VFO A field was something like 12405.?.
>> Changing the band with the arrow keys worked still fine on the xcvr, but
>> the working field it jumped to 15m again. I only could stop the behaviour
>> closing WT and restart it again. It happend 3 times during the contest.
>> Luckily I watched afterwords the VFO A field in the Radio window and the
>> frequency on the radio to make sure that when it happens to restart WT.
>> Hopefully WT did not log QSOs in the wrong band. Has this been seen
>> I can remember that it happend also last year with WT3.27, but forgot to
>> 73 / Armin, DK9PY
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Support