Received-SPF: neutral (google.com: 193.82.116.20 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org)
Message-ID: <20061123215013.b7egw160vdwgg84w@webmail3.kuleuven.be>
Date: Thu, 23 Nov 2006 21:50:13 +0100
From: Rik Strobbe <Rik.Strobbe@fys.kuleuven.be>
To: rsgb_lf_group@blacksheep.org
References: <5.1.0.14.0.20060928155327.013128d8@u0019445.kuleuven.be>
	<001901c6e317$42638850$3402a8c0@pmchelpdesk1>
	<20060928220707.q2fwvnrzac08oo04@webmail3.kuleuven.be>
	<BAY118-DAV6120029BBC37001F71599BE180@phx.gbl>
	<5.1.0.14.0.20060929090742.00c15ae0@u0019445.kuleuven.be>
	<003101c70f1b$a199e6e0$6801a8c0@Radio>
In-Reply-To: <003101c70f1b$a199e6e0$6801a8c0@Radio>
MIME-Version: 1.0
Content-Disposition: inline
User-Agent: Internet Messaging Program (IMP) H3 (4.1.2)
Subject: Re: LF: more information...Temporary solution
Content-Type: text/plain;
	charset=ISO-8859-1;
	DelSp="Yes";
	format="flowed"
Content-Transfer-Encoding: quoted-printable
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
Status: O

Hi J.,

I have done some tests (each taking one night) and found out that the =20
problem does not occur here when the fast CW-speed is set to 6 WPM =20
(instead of 12 WPM).
This could make sense as for 6 WPM "fast CW" the same timer si used as =20
for QRS while at higher WPM speeds a separate (more accurate but also =20
more CPU-time consuming) timer is used.
Did you ever encounter the prblem when the fast CW speed was set to 6 WPM?

73, Rik  ON7YD


Quoting "J. Allen" <vy1ja@northwestel.net>:

> Rik,
>
> I found yesterday that if I turn on the synchronize for 30 minutes AND
> am using dot / dash ratio of 1:3, it forces the system to continue
> running.  I think it is most logical that the dot / dash ratio has
> nothing to do with the problem, which means that by using
> synchronizing, the beacon ran all night.
>
> There must be a software counter in the program which gets reset every
> time the sync happens on the hour and half hour.
>
> At least now you know what to tell people who want to beacon
> continuously.... use synchronizing every half hour and if that does not
> prove to be the answer by itself, tell them to use 1:3 ratio as well.
>
> I will do more experimenting on this to find out if I can move back to
> 1:2 ratio, with SYNC on and see if it clears the problem up.. I will
> also try different sync times to see if they affect the problem.
>
> J.


Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm