Both logs seems to have something in common:<div><br></div><div>Rig 1 on Band A (RUN)</div><div>Rig 2 on Band B (S&P)</div><div><br></div><div>All is OK until Rig 2 is moved to Band C. The very <i>first</i> QSO that Rig 2 makes on Band C logs the band correctly (C) but the <i>frequency</i> incorrectly (it instead logs the frequency from the very last QSO that Rig 2 made on band B).</div>
<div><br></div><div>Was this the first QSO that SE5E made on 20m with Rig 2?</div><div><br></div><div>The question now is, how are you guys moving the secondary radio to the 3rd band? </div><div><ol><li>Right click on Announcements Window and "Pass frequency to secondary radio"?</li>
<li>By using the band switch on the radio?</li><li>Via CapsLock + Alt-F1/Alt-F2?</li><li>Via CapsLock + type in new band in meters (20 Enter)?</li><li>Via CapsLock + type in new frequency in kHz (14020 Enter)?</li><li>By right clicking on a spot in the Announcements window?</li>
<li>By clicking on an SDR waterfall display (e.g. HDSDR + OmniRig Sync)?</li><li>Using a MEMORY in the Radio (M->V)?</li><li>Some other method?</li></ol></div><div>Are you using OmniRig? Are you both using StackCalls (which simulates pressing Alt-1, which caused the problem reported in Task #259).</div>
<div><br></div><div>73,</div><div><div>Bob, N6TV</div><div><br></div><div class="gmail_quote">On Tue, Oct 4, 2011 at 11:18 PM, SM5AJV <span dir="ltr"><<a href="mailto:sm5ajv@qrq.se">sm5ajv@qrq.se</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">It's impossible to remember any key sequences but I will<br>
try to resume the "facts" below.<br>
<br>
I think it may have something to do with the updating of<br>
the frequency from the secondary radio.<br>
<br>
And there should never be any difference between what seen<br>
on the log screen and what's in the database...<br>
<br>
I can provide the log-file if its of any use.<br>
<br>
<br>
Some facts:<br>
<br>
* WT version 4.8.0<br>
* RADIO1 FT1000MP<br>
* RADIO2 TS-480<br>
* SO2R with Secondary Radio Window<br>
* RUN station on 15 meters (FT1000MP)<br>
* RADIO2 on 20 meters (TS480)<br>
* Last QSO (#221) on 28 MHz before the faulty one was on 28010 with RADIO2<br>
See Cabrillo below.<br>
* The faulty (#236) QSO was shown as 20 meters on the log screen<br>
but 28010 in the actual log (ALT-F and Cabrillo)<br>
* The actual frequency of the faulty QSO was 14037<br>
* All QSO's between #221 and #236 was on 15 meters.<br>
<br>
Here is a snippet from the Cabrillo:<br>
<br>
QSO: 28010 CW 2011-09-17 1424 SE5E 599 0221 SP9DUX 599 062<br>
QSO: 21023 CW 2011-09-17 1425 SE5E 599 0222 R9QQ 599 011<br>
QSO: 21023 CW 2011-09-17 1426 SE5E 599 0223 K4MTI 599 016<br>
QSO: 21023 CW 2011-09-17 1427 SE5E 599 0224 DL5YM 599 010<br>
QSO: 21023 CW 2011-09-17 1427 SE5E 599 0225 UA1ZZ 599 034<br>
QSO: 21023 CW 2011-09-17 1428 SE5E 599 0226 KA2ETG 599 001<br>
QSO: 21023 CW 2011-09-17 1428 SE5E 599 0227 AC5K 599 031<br>
QSO: 21023 CW 2011-09-17 1428 SE5E 599 0228 YO9WF 599 012<br>
QSO: 21023 CW 2011-09-17 1429 SE5E 599 0229 OK2MBP 599 063<br>
QSO: 21023 CW 2011-09-17 1430 SE5E 599 0230 W3IUU 599 007<br>
QSO: 21023 CW 2011-09-17 1431 SE5E 599 0231 K3DQB 599 013<br>
QSO: 21023 CW 2011-09-17 1431 SE5E 599 0232 W2LE 599 079<br>
QSO: 21023 CW 2011-09-17 1431 SE5E 599 0233 EK6LP 599 019<br>
QSO: 21023 CW 2011-09-17 1432 SE5E 599 0234 N8II 599 085<br>
QSO: 21023 CW 2011-09-17 1433 SE5E 599 0235 K2LP 599 021<br>
QSO: 28010 CW 2011-09-17 1434 SE5E 599 0236 SV1ENG 599 084 <-- actually on 14037<br>
QSO: 21023 CW 2011-09-17 1435 SE5E 599 0237 LZ2FM 599 097<br>
QSO: 21023 CW 2011-09-17 1435 SE5E 599 0238 AA3B 599 058<br>
<br>
<br>
73<br>
Ingo SM5AJV<br>
<div class="im"><br>
<br>
> A similar problem was reported and fixed two years ago. See Task<br>
</div>> #259<<a href="http://flyspray.win-test.com/index.php?do=details&id=259" target="_blank">http://flyspray.win-test.com/index.php?do=details&id=259</a>>.<br>
<div><div></div><div class="h5">> Where you using WT 4.8 or 4.9-dev?<br>
><br>
> Please try to come up with an exact sequence of steps to easily reproduce<br>
> the problem (as ES5TV did two years ago). The sooner you can do that, the<br>
> sooner the problem can be fixed. I can't really open a bug report without<br>
> more details about how to reproduce it.<br>
><br>
> Did you use the Partner window at all? Did you press Alt-1? (Not Alt-F1).<br>
> Were you using SO2R and the secondary radio window? Did you ever press<br>
> Alt-F1 or Alt-F2 to change bands of a previously-logged QSO? Or to change<br>
> bands at all? Were you using OmniRig? What radio models were selected?<br>
><br>
> 73,<br>
> Bob, N6TV<br>
><br>
> On Tue, Oct 4, 2011 at 1:44 PM, Bjorn LB1GB <<a href="mailto:lb1gb@la8w.com">lb1gb@la8w.com</a>> wrote:<br>
><br>
>> I was puzzled by losing a multiplier in SAC, but thought I made a<br>
>> mistake. After your post I investigated a bit and found RA9AP that I<br>
>> worked on 10 meters shows 21009.5 when doing Alt-F. Thus losing the<br>
>> mulitipier.<br>
>><br>
>> wt4 file shows 10M, cabrillo shows 21009.5.<br>
>><br>
>> The ADI file is correct and the QSO was confirmed as a 10M qso on LOTW.<br>
>><br>
>> Bjorn LB1GB<br>
>><br>
>><br>
>> On 4 October 2011 22:01, SM5AJV <<a href="mailto:sm5ajv@qrq.se">sm5ajv@qrq.se</a>> wrote:<br>
>> > Hi!<br>
>> ><br>
>> > I am checking my log from SAC CW and I found one serious fault.<br>
>> ><br>
>> > The log line in WinTest (screen) says:<br>
>> > QSO Bd Time Callsign<br>
>> > 275 20 14:35 SV1ENG<br>
>> ><br>
>> > But I if push Alt-F to check the details it says that we<br>
>> > worked on 28 MHz! The resulting Cabrillo shows 28 MHz and<br>
>> > not the correct 20 meters frequency.<br>
>> ><br>
>> > How on earth is it possible to have one band on the log and<br>
>> > another in the actual log? The fault will result i WRONG BAND<br>
>> > during the logcheck and zero points/mult :-(<br>
>> ><br>
>> > Used WT version 4.8.0<br>
>> ><br>
>> > 73<br>
>> > Ingo SM5AJV / SE5E<br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > Support mailing list<br>
>> > <a href="mailto:support@win-test.com">support@win-test.com</a><br>
>> > <a href="http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support" target="_blank">http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support</a><br>
>> ><br>
>> _______________________________________________<br>
>> Support mailing list<br>
>> <a href="mailto:support@win-test.com">support@win-test.com</a><br>
>> <a href="http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support" target="_blank">http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support</a><br>
>><br>
> _______________________________________________<br>
> Support mailing list<br>
> <a href="mailto:support@win-test.com">support@win-test.com</a><br>
> <a href="http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support" target="_blank">http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support</a><br>
><br>
<br>
<br>
_______________________________________________<br>
Support mailing list<br>
<a href="mailto:support@win-test.com">support@win-test.com</a><br>
<a href="http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support" target="_blank">http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support</a><br>
</div></div></blockquote></div><br></div>