[WT-support] Wrong Frequency logged on second radio contacts

[Bob Wilson, N6TV]

Well it sounds like you have eliminated Prolific USB-to-Serial ports as a
possible cause.

I don't think there is any hope of resolving the problem until you can
provide a lot more hardware and setup details, including firmware and
software versions, plus step-by-step instructions to replicate the problem,
at least once out of ten tries (assuming it happens intermittently).

So far, there are only two reported cases?

Do you notice the frequency ever being incorrect at the top of the bandmap
window?

I do notice (when using a micro2R with K3s) that when you first start
Win-Test, the displayed band may not match the radio frequency, but typing
SETUP [Enter] [Enter], or logging the first contact seems to reinitalize
everything and fix it.  That may or may not be a related issue.

What radio type are you using, or does it happen with all radio types?
 Does it happen when using radio type OmniRig?  How are you making QSOs on
the secondary radio?  Via Caps Lock or Shift key binds to secondary radio,
or by pressing [ * ] or Ctrl-S?  Or are you using automated scripts like
the AltD scripts to make QSOs on the secondary radio and quickly swap back
to the primary?

The MK2R+ will allow you to enable COM port communications logging,
something that will be helpful to capture if you can ever replicate the
problem.  It seems likely that a communications glitch between the computer
and the radio is the root cause of the problem.  Win-Test won't change
bands unless it detects a valid frequency on a new band, as returned by the
radio.

It's also possible that Win-Test has a timing issue if you are logging a
QSO on the secondary radio at exactly the same time that you are switching
focus back to the primary radio, though it seems like such a problem would
have been more widely reported.

If you have the option of using a real serial port via desktop plugin card
or ExpressCard or similar, and you still see the problem, that would prove
that Win-Test or the radio firmware is at fault, rather than the
USB-to-Serial converters or the microHAM software.

In sum, please provide as many details as you can, screen shots of the
Win-Test SETUP and microHAM Router screens as a start.

73,
Bob, N6TV

On Fri, Nov 11, 2011 at 4:22 PM, Bjorn LB1GB <lb1gb at la8w.com> wrote:

> Hi Bob,
>
> We ditched the DX Doubler SO2Rxlat solution and bought a MK2R+, before
> even really trying out the DXD SO2rxlat thingy(just one contest).
> Still we have second radio contacts with wrong frequency.
>
> SE5E also reported this in the October archives.
> http://lists.f5mzn.org/pipermail/support/2011-October/081594.html
> (at this time we used DXD)
>
> We are running Win XP. I must say that we never saw this problem while
> running Writelog.
>
> The only USB driver used now must be the one between MK2R+ and PC.
>
> Bjorn LB1GB/LN8W
>
>
>
>
>
> On 12 November 2011 00:38, Bob Wilson, N6TV <n6tv at arrl.net> wrote:
> > During the ARRL Sweepstakes contest last weekend, unfortunately using
> > Windows 7 with unreliable Prolific USB-to-Serial adapters on each
> Elecraft
> > K3 radio, I was noticing that from time to time the frequency readout of
> the
> > inactive radio was displayed as a crazy number that made no sense.  I was
> > able to temporarily fix the problem by doing SETUP [Enter] [Enter], which
> > resets all Win-Test I/O port communications, but the problem returned
> every
> > few hours.  As we should all know by know, using Prolific USB drivers
> are to
> > be avoided, especially under Windows 7.  I tried setting DTR and RTS to
> > Always ON, but it did not help.
> > I noted that the band displayed by Win-Test 4.9.1 was always OK, but the
> > frequency often was not.
> > However, when I compared band to frequency later, in the exported TXT
> file,
> > I could not find a single QSO that was logged on the wrong band.  Many
> QSOs
> > were logged on 21.000 or 28.000 instead of the true and accurate
> frequency,
> > apparently at the time that the crazy radio frequencies were being
> noticed
> > in the Alt-J (Status) and Band Map windows, but no QSOs were logged on
> the
> > wrong band.  I made hundreds of secondary radio QSOs too.
> > The Win-Test 4.9.1 Release.txt file makes no mention of any fixes in this
> > area, but maybe that is just an oversight in the documentation.
> > Please remind me, which USB-to-Serial adapter are you using Bjorn?  The
> N1MM
> > documentation documents a good summary of what is available:
> > http://n1mm.hamdocs.com/tiki-index.php?page=USB+Interface+Devices
> > 73,
> > Bob, N6TV
> > On Fri, Nov 11, 2011 at 1:36 PM, Bjorn LB1GB <lb1gb at la8w.com> wrote:
> >>
> >> Anyone had a chance to check their logs for wrong frequency logging on
> >> the second radio?
> >>
> >> 73 Bjorn LB1GB/LN8W
> >>
> >> On 5 November 2011 15:01, Bjorn LB1GB <lb1gb at la8w.com> wrote:
> >> > Again we experience wrong frequency logged on several second radio
> >> > contacts, band is logged correctly.
> >> > Cabrillo output is frequency so this will many times produce dupes
> >> > instead of mults.
> >> >
> >> > We used WT version 4.8.0
> >> > Has anyone experience this with 4.9.1?
> >> >
> >> > 73 Bjorn LB1GB
> >
> > _______________________________________________
> > Support mailing list
> > support at win-test.com
> > http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
> >
> >
> _______________________________________________
> Support mailing list
> support at win-test.com
> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20111111/564a69d6/attachment.html>