[WT-support] Cabrillo error with WT4

Tõnno Vähk Tonno.Vahk at gildbankers.com
Mon Oct 19 21:26:38 CEST 2009


I found out at least one way to regenerate that problem even without any CAT!

 

That happens in the secondary radio window only.

 

When you activate secondary radio window and change bands with ALT+F1 for example with no radio connected then the frequency in the Bandmap follows the band. All nice.

 

But when you press ALT-1 for example then band is changed (don't know why as this key is meant to bring up calls from partner list) and frequency in the bandmap stays!!

 

So you can now log a QSO where band is different from the frequency logged. Should this be protected and not allowed by the program?

 

When I try to change frequency through Edit.. for any normal QSO to a frequency in the wrong band then it tells me WRONG BAND and does not let to change.

 

So there is a problem in Secondary Radio window.

 

This does not happen with main radio window.

 

73

Tonno

Es5tv

 

 

From: support-bounces at win-test.com [mailto:support-bounces at win-test.com] On Behalf Of Tõnno Vähk
Sent: Saturday, October 17, 2009 7:35 PM
To: support at win-test.com
Subject: Re: [WT-support] Cabrillo error with WT4

 

2 x MP mark V, no sub VFOs involved, no memory tune involved.

Both radios proper CAT, bandmaps show correct freq

MK2R+

WT4

 

The problem is that WT creates a situation that log shows correct band and that band is different from the actual frequency band that will be printed into Cabrillo.

 

That means, people could lose MANY QSOs plus penalties in CQWW if that happens because they never know that happened. They never know Cabrillo is wrong as they don't check that line by line vs log!

 

I ONLY found it very luckily because I had zero QSOs on 10 meters but when I created Cabrillo, corrected typos and imported it back to WT to create final ADIF in order to import to my log program I noticed one QSOs had appeared on 10m.

 

This should be addressed. Band cannot be different in log than the frequency behind it.

 

73

tonno

On Thu, Oct 15, 2009 at 2:03 PM, Tõnno Vähk <Tonno.Vahk at gildbankers.com> wrote:

Hi,

 

I was just making cabrillo from my SAC SSB log where I used WT4 for the first time.

 

Something very strange happened.

 

For 3 QSOs out of 770 WT put WRONG BAND into Cabrillo.

 

Those are all 2nd radio QSOs. The band is correct in the log file BUT when I open Edit > Edit Date, Time... and check the frequency then it is wrong.

 

For example - I made zero QSOs on 10 meters but my QSO with 8S0C which is on 20m and also shows 20m in the log (counted correctly in Summary, etc) has frequency 28450 attached to it and thus Cabrillo shows 28450!

 

This is 1st time I used SO2R with one computer and Secondary Radio Window. 

 

It is obvious that there is one very serious bug there - frequency is not taken correctly and even when band is recorded correctly frequency is taken probably at the wrong time or sth.

 

I have 3 QSOs wrong and I cannot quite understand where this wrong frequency comes from. It looks like old frequency. It looks like that maybe the Secondary Radio Window freezes the frequency on the time when you start entering sth to callsign field and does not actually take the frequency at the time when Enter is pressed, can this be it???

 

I can send the log file if you wish. It is also strange that when frequency is 28450 then log shows 20m!

 

73

Tonno

Es5tv

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.f5mzn.org/pipermail/support/attachments/20091019/0224a29b/attachment.htm 


More information about the Support mailing list