Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-mb04.r1000.mx.aol.com (Internet Inbound) with ESMTP id 9DE9A3800009F; Fri, 2 Sep 2011 05:23:16 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1QzPxH-0000r0-1O for rs_out_1@blacksheep.org; Fri, 02 Sep 2011 10:22:31 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1QzPxG-0000qH-9u for rsgb_lf_group@blacksheep.org; Fri, 02 Sep 2011 10:22:30 +0100 Received: from mail-vw0-f43.google.com ([209.85.212.43]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1QzPxE-0004hK-Ms for rsgb_lf_group@blacksheep.org; Fri, 02 Sep 2011 10:22:30 +0100 Received: by vws10 with SMTP id 10so3488631vws.16 for ; Fri, 02 Sep 2011 02:22:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=jn5cbYjufKH/GMYNCy+6p08F//fULBUunLtSMs7jbQI=; b=V19uc2EhfgIYVMeD51DNIBnT7/e4Xfyj+8KqQlKZKxP9JH3n2H34+kxykM/uXknzMH OiyyCDO6l0GP84zUJaCu/yD4o9o5Q1FW9DZydsxJZXFs4Ln6ExVV73Be4hYTOBpsmCQb litzXP3X0YRBBBHa/5LEqMJDIGYng/2RdjzQQ= MIME-Version: 1.0 Received: by 10.52.28.80 with SMTP id z16mr797754vdg.75.1314955342577; Fri, 02 Sep 2011 02:22:22 -0700 (PDT) Received: by 10.220.192.70 with HTTP; Fri, 2 Sep 2011 02:22:22 -0700 (PDT) In-Reply-To: <20110902053904.477d773c@svr1> References: <004301cc68dc$3ee79540$0401a8c0@xphd97xgq27nyf> <4EEE84D5F0DF43BE878C6B3E1E455554@AGB> <005301cc68de$4c864c80$0401a8c0@xphd97xgq27nyf> <3C0C61D0515A436CB88A0DB5AFDD9CA9@AGB> <001101cc68e5$974df590$0401a8c0@xphd97xgq27nyf> <20110902053904.477d773c@svr1> Date: Fri, 2 Sep 2011 10:22:22 +0100 X-Google-Sender-Auth: d7KoSI0fGQwOL-54NmCPxDTdqCw Message-ID: From: Gary - G4WGT To: rsgb_lf_group@blacksheep.org X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,HTML_MESSAGE=0.001 Subject: Re: LF: ros Content-Type: multipart/alternative; boundary=20cf30780d5017011b04abf1e604 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=HTML_MESSAGE 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-global-disposition: G X-AOL-SCOLL-SCORE: 0:2:414215872:93952408 X-AOL-SCOLL-URL_COUNT: 0 X-AOL-SCOLL-AUTHENTICATION: mail_rly_antispam_dkim-d025.1 ; domain : gmail.com DKIM : fail x-aol-sid: 3039ac1d60184e60a0845f54 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none --20cf30780d5017011b04abf1e604 Content-Type: text/plain; charset=ISO-8859-1 John & All, Apparently the latest ROS version v6.6.9 has been changed to prevent beacon mode stopping when other signals encountered. 73, Gary - G4WGT. On 2 September 2011 06:39, John GM4SLV wrote: > On Thu, 1 Sep 2011 15:45:19 -0800 > Laurence KL7UK wrote: > > > > > KL7UK now ROS 500kHz for the night - > > > > > > Laurence, LF, > > ROS is NOT the mode for this sort of test! > > I came to the shack at 05:15 UTC to find the regular beaconing had > stopped running. Apparently if a signal is received the software stops > any beacon (to avoid causing QRM) and in this instance it didn't restart > the beacon timer afterwards - therefore my log shows that at 23:34 UTC > there was a (not correctly decoded) RX frame, and after that no further > beacons were sent. > > Sorry. > > WSPR would seem to be the mode for finding an opening, not ROS, > > I won't be using it again in anger. I find as a QSO mode it is very > ponderous, which I can accept for the ability to resolve signals deep > in the noise, inaudible even, but it didn't seem to perform very well in > the presence of lightning QRN - requiring signals to be audible before > it decoded them. > > On top of that I find the actual software to be very difficult to > drive. As Mal pointed out, the continuous appearance if spots & > information of activity on every other band is very annoying, and > seemingly can't be turned off. The Beacon functionality is seriously > flawed for the use we put it to. The secret nature of the modem means > no one else can integrate ROS into existing (more user friendly) > software (fldigi, multipsk etc). > > The PSKreporter spot-collecting website, while a laudable project, is > no way as usable as the WSPRNet online database, which makes finding > and tabulating reception reports more difficult. > > I'll stick with WSPR for beaconing, which is what it was intended for, > and look into other MFSK modes for QSOs. > > Anyone interested in some MFSK-4 tests over the weekend? > > > Cheers, > > John > GM4SLV > > --20cf30780d5017011b04abf1e604 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable John & All,

Apparently the latest ROS version v6.6.9= has been changed to prevent beacon mode stopping when other signals encoun= tered.

73, Gary - G4WGT.


On 2 September 2011 06:39, John GM4SLV <gm4slv@sighthound.demon.co.uk> wrote:
On Thu, 1 Sep 2011 15:45:19 -0800
Laurence KL7UK <helloz= erohellozero@hotmail.com> wrote:

>
> KL7UK now ROS 500kHz for the night -
>
>

Laurence, LF,

ROS is NOT the mode for this sort of test!

I came to the shack at 05:15 UTC to find the regular beaconing had
stopped running. Apparently if a signal is received the software stops
any beacon (to avoid causing QRM) and in this instance it didn't restar= t
the beacon timer afterwards - therefore my log shows that at 23:34 UTC
there was a (not correctly decoded) RX frame, and after that no further
beacons were sent.

Sorry.

WSPR would seem to be the mode for finding an opening, not ROS,

I won't be using it again in anger. I find as a QSO mode it is very
ponderous, which I can accept for the ability to resolve signals deep
in the noise, inaudible even, but it didn't seem to perform very well i= n
the presence of lightning QRN - requiring signals to be audible before
it decoded them.

On top of that I find the actual software to be very difficult to
drive. As Mal pointed out, the continuous appearance if spots &
information of activity on every other band is very annoying, and
seemingly can't be turned off. The Beacon functionality is seriously flawed for the use we put it to. The secret nature of the modem means
no one else can integrate ROS into existing (more user friendly)
software (fldigi, multipsk etc).

The PSKreporter spot-collecting website, while a laudable project, is
no way as usable as the WSPRNet online database, which makes finding
and tabulating reception reports more difficult.

I'll stick with WSPR for beaconing, which is what it was intended for,<= br> and look into other MFSK modes for QSOs.

Anyone interested in some MFSK-4 tests over the weekend?


=A0Cheers,

John
GM4SLV


--20cf30780d5017011b04abf1e604--