X-GM-THRID: 1220856406541331549 X-Gmail-Labels: rsgb lf X-Gmail-Received: 0a6e4afd448736624527de5c0191e3b9856e1c3e Delivered-To: daveyxm@gmail.com Received: by 10.70.28.15 with SMTP id b15cs149455wxb; Thu, 23 Nov 2006 08:29:59 -0800 (PST) Received: by 10.78.178.5 with SMTP id a5mr9228652huf.1164299398903; Thu, 23 Nov 2006 08:29:58 -0800 (PST) Return-Path: Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by mx.google.com with ESMTP id 10si12513917hug.2006.11.23.08.29.57; Thu, 23 Nov 2006 08:29:58 -0800 (PST) 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) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1GnHM0-0000BU-E1 for rs_out_1@blacksheep.org; Thu, 23 Nov 2006 16:23:12 +0000 Received: from [193.82.116.35] (helo=relay3.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1GnHLz-0000BK-NU for rsgb_lf_group@blacksheep.org; Thu, 23 Nov 2006 16:23:11 +0000 Received: from yk-mlwprd2.northwestel.ca ([198.235.201.13] helo=mail2.theedge.ca) by relay3.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1GnHLr-0000q1-UM for rsgb_lf_group@blacksheep.org; Thu, 23 Nov 2006 16:23:11 +0000 Received: from Radio (whthyt235-40.northwestel.net [207.189.235.40]) by mail2.theedge.ca (Spam Firewall) with SMTP id BC344CC4A8 for ; Thu, 23 Nov 2006 09:22:59 -0700 (MST) Message-ID: <003101c70f1b$a199e6e0$6801a8c0@Radio> From: "J. Allen" To: References: <5.1.0.14.0.20060928155327.013128d8@u0019445.kuleuven.be> <001901c6e317$42638850$3402a8c0@pmchelpdesk1> <20060928220707.q2fwvnrzac08oo04@webmail3.kuleuven.be> <5.1.0.14.0.20060929090742.00c15ae0@u0019445.kuleuven.be> Date: Thu, 23 Nov 2006 16:22:55 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Virus-Scanned: by Barracuda Spam Firewall at theedge.ca X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,none Subject: LF: more information...Temporary solution Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false Status: O X-Status: X-Keywords: X-UID: 4209 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.