Return-Path: Received: from rly-mf07.mx.aol.com (rly-mf07.mail.aol.com [172.20.29.177]) by air-mf02.mail.aol.com (v121_r4.4) with ESMTP id MAILINMF021-96b497c497a7e; Sun, 25 Jan 2009 06:14:30 -0500 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-mf07.mx.aol.com (v121_r4.4) with ESMTP id MAILRELAYINMF071-96b497c497a7e; Sun, 25 Jan 2009 06:14:10 -0500 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1LR2vC-0003OC-L8 for rs_out_1@blacksheep.org; Sun, 25 Jan 2009 11:12:58 +0000 Received: from [83.244.159.144] (helo=relay3.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1LR2vB-0003O3-8q for rsgb_lf_group@blacksheep.org; Sun, 25 Jan 2009 11:12:57 +0000 Received: from fk-out-0910.google.com ([209.85.128.187]) by relay3.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1LR2v8-0003g7-3V for rsgb_lf_group@blacksheep.org; Sun, 25 Jan 2009 11:12:54 +0000 Received: by fk-out-0910.google.com with SMTP id e30so2185997fke.4 for ; Sun, 25 Jan 2009 03:12:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=QV5Zyna0g6fVD6eQDYkzh0FXds1Jg4k0BA9FQGtu5gs=; b=XkryNbTdRkkpYsBSkZzXu6vgHnpvFNX5LqoxmmkalypJcdbSBCMnrpAz+vQ4RwgyrJ MVjFJ3Rk22H5EtxEko1cDEpCcEAglbs6coxpSjYMhmeIlMZj7oG56kZPPJjch2bs+p5H mfMoeYvSRKbd4MoPYTcgGNZ9P5IB5GdNLSQJc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=iFquk6C/8FK4UAJ9Ej+8HQXPLMMhW7Z30MlASkO0w0ttz3lRjgadkCbeBOv35spNmb GwNQr8fomSnk28cRfkZ9DS73cjcBfbx/eQQU9igAwuTJSdTen8xt3Q3O36J6TOpugBEG UN2wP89pAnbsGr8v/0lwrp2ZfhkW3ZoThOnfw= MIME-Version: 1.0 Received: by 10.181.60.14 with SMTP id n14mr351903bkk.79.1232881972428; Sun, 25 Jan 2009 03:12:52 -0800 (PST) In-Reply-To: <004001c97edb$4ebaeaa0$6401a8c0@asus> References: <5F3E5A778D18465DB680DC48CC7FBE48@JimPC> <09254C21C2884198957A5719438826D6@p4> <004001c97edb$4ebaeaa0$6401a8c0@asus> Date: Sun, 25 Jan 2009 11:12:52 +0000 Message-ID: From: Andy Talbot To: rsgb_lf_group@blacksheep.org DomainKey-Status: good (testing) X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,none Subject: Re: LF: RE: Re: WSPR Beacon on 503.5kHz Content-Type: text/plain; charset=ISO-8859-1 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 X-AOL-IP: 193.82.116.20 X-AOL-SCOLL-AUTHENTICATION: mail_rly_antispam_dkim-d251.2 ; domain : googlemail.com DKIM : pass X-Mailer: Unknown (No Version) I have (sort-of) sorted out the transmitter control problem. While both WSPR.EXE and WSJT6 both refuse to properly control the PC-installed COM1 port, they do both behave properly with an FTDI type USB COM port. So am running a WSPR beacon on 503.47kHz for a while. Still intrigued to know why Joe's software won't drive my COM 1 properly, whereas it works with USB based conm ports. Whereas other software, including direct programming it from VB6, does allow complete control of DTR and RTS signal lines. Andy G4JNT www.g4jnt.com