[WT-support] Wrong Frequency/Band in Cabrillo

Bob Wilson, N6TV n6tv at arrl.net
Wed Oct 5 08:50:05 CEST 2011 

Both logs seems to have something in common:

Rig 1 on Band A (RUN)
Rig 2 on Band B (S&P)

All is OK until Rig 2 is moved to Band C.  The very *first* QSO that Rig 2
makes on Band C logs the band correctly (C) but the *frequency* incorrectly
(it instead logs the frequency from the very last QSO that Rig 2 made on
band B).

Was this the first QSO that SE5E made on 20m with Rig 2?

The question now is, how are you guys moving the secondary radio to the 3rd
band?

   1. Right click on Announcements Window and "Pass frequency to secondary
   radio"?
   2. By using the band switch on the radio?
   3. Via CapsLock + Alt-F1/Alt-F2?
   4. Via CapsLock + type in new band in meters (20 Enter)?
   5. Via CapsLock + type in new frequency in kHz (14020 Enter)?
   6. By right clicking on a spot in the Announcements window?
   7. By clicking on an SDR waterfall display (e.g. HDSDR + OmniRig Sync)?
   8. Using a MEMORY in the Radio (M->V)?
   9. Some other method?

Are you using OmniRig?  Are you both using StackCalls (which simulates
pressing Alt-1, which caused the problem reported in Task #259).

73,
Bob, N6TV

On Tue, Oct 4, 2011 at 11:18 PM, SM5AJV <sm5ajv at qrq.se> wrote:

> It's impossible to remember any key sequences but I will
> try to resume the "facts" below.
>
> I think it may have something to do with the updating of
> the frequency from the secondary radio.
>
> And there should never be any difference between what seen
> on the log screen and what's in the database...
>
> I can provide the log-file if its of any use.
>
>
> Some facts:
>
> * WT version 4.8.0
> * RADIO1 FT1000MP
> * RADIO2 TS-480
> * SO2R with Secondary Radio Window
> * RUN station on 15 meters (FT1000MP)
> * RADIO2 on 20 meters (TS480)
> * Last QSO (#221) on 28 MHz before the faulty one was on 28010 with RADIO2
>  See Cabrillo below.
> * The faulty (#236) QSO  was shown as 20 meters on the log screen
>  but 28010 in the actual log (ALT-F and Cabrillo)
> * The actual frequency of the faulty QSO was 14037
> * All QSO's between #221 and #236 was on 15 meters.
>
> Here is a snippet from the Cabrillo:
>
> QSO: 28010 CW 2011-09-17 1424 SE5E  599 0221   SP9DUX   599 062
> QSO: 21023 CW 2011-09-17 1425 SE5E  599 0222   R9QQ     599 011
> QSO: 21023 CW 2011-09-17 1426 SE5E  599 0223   K4MTI    599 016
> QSO: 21023 CW 2011-09-17 1427 SE5E  599 0224   DL5YM    599 010
> QSO: 21023 CW 2011-09-17 1427 SE5E  599 0225   UA1ZZ    599 034
> QSO: 21023 CW 2011-09-17 1428 SE5E  599 0226   KA2ETG   599 001
> QSO: 21023 CW 2011-09-17 1428 SE5E  599 0227   AC5K     599 031
> QSO: 21023 CW 2011-09-17 1428 SE5E  599 0228   YO9WF    599 012
> QSO: 21023 CW 2011-09-17 1429 SE5E  599 0229   OK2MBP   599 063
> QSO: 21023 CW 2011-09-17 1430 SE5E  599 0230   W3IUU    599 007
> QSO: 21023 CW 2011-09-17 1431 SE5E  599 0231   K3DQB    599 013
> QSO: 21023 CW 2011-09-17 1431 SE5E  599 0232   W2LE     599 079
> QSO: 21023 CW 2011-09-17 1431 SE5E  599 0233   EK6LP    599 019
> QSO: 21023 CW 2011-09-17 1432 SE5E  599 0234   N8II     599 085
> QSO: 21023 CW 2011-09-17 1433 SE5E  599 0235   K2LP     599 021
> QSO: 28010 CW 2011-09-17 1434 SE5E  599 0236   SV1ENG   599 084 <--
> actually on 14037
> QSO: 21023 CW 2011-09-17 1435 SE5E  599 0237   LZ2FM    599 097
> QSO: 21023 CW 2011-09-17 1435 SE5E  599 0238   AA3B     599 058
>
>
> 73
> Ingo SM5AJV
>
>
> > A similar problem was reported and fixed two years ago.  See Task
> > #259<http://flyspray.win-test.com/index.php?do=details&id=259>.
> >  Where you using WT 4.8 or 4.9-dev?
> >
> > Please try to come up with an exact sequence of steps to easily reproduce
> > the problem (as ES5TV did two years ago).  The sooner you can do that,
> the
> > sooner the problem can be fixed.  I can't really open a bug report
> without
> > more details about how to reproduce it.
> >
> > Did you use the Partner window at all?  Did you press Alt-1?  (Not
> Alt-F1).
> >  Were you using SO2R and the secondary radio window?  Did you ever press
> > Alt-F1 or Alt-F2 to change bands of a previously-logged QSO?  Or to
> change
> > bands at all?  Were you using OmniRig?  What radio models were selected?
> >
> > 73,
> > Bob, N6TV
> >
> > On Tue, Oct 4, 2011 at 1:44 PM, Bjorn LB1GB <lb1gb at la8w.com> wrote:
> >
> >> I was puzzled by losing a multiplier in SAC, but thought I made a
> >> mistake. After your post I investigated a bit and found RA9AP that I
> >> worked on 10 meters shows 21009.5 when doing Alt-F. Thus losing the
> >> mulitipier.
> >>
> >> wt4 file shows 10M, cabrillo shows 21009.5.
> >>
> >> The ADI file is correct and the QSO was confirmed as a 10M qso on LOTW.
> >>
> >> Bjorn LB1GB
> >>
> >>
> >> On 4 October 2011 22:01, SM5AJV <sm5ajv at qrq.se> wrote:
> >> > Hi!
> >> >
> >> > I am checking my log from SAC CW and I found one serious fault.
> >> >
> >> > The log line in WinTest (screen) says:
> >> > QSO  Bd Time  Callsign
> >> > 275  20 14:35 SV1ENG
> >> >
> >> > But I if push Alt-F to check the details it says that we
> >> > worked on 28 MHz! The resulting Cabrillo shows 28 MHz and
> >> > not the correct 20 meters frequency.
> >> >
> >> > How on earth is it possible to have one band on the log and
> >> > another in the actual log? The fault will result i WRONG BAND
> >> > during the logcheck and zero points/mult :-(
> >> >
> >> > Used WT version 4.8.0
> >> >
> >> > 73
> >> > Ingo SM5AJV / SE5E
> >> >
> >> >
> >> > _______________________________________________
> >> > 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
> >>
> > _______________________________________________
> > 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/20111004/da73f9c8/attachment-0001.html>

More information about the Support mailing list