Return-Path: Received: from rly-mh11.mx.aol.com (rly-mh11.mail.aol.com [172.21.166.147]) by air-mh03.mail.aol.com (v123.3) with ESMTP id MAILINMH033-61449c01d4b3bc; Tue, 17 Mar 2009 18:00:04 -0400 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-mh11.mx.aol.com (v123.3) with ESMTP id MAILRELAYINMH111-61449c01d4b3bc; Tue, 17 Mar 2009 17:59:42 -0400 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1LjhJn-0007nB-8U for rs_out_1@blacksheep.org; Tue, 17 Mar 2009 21:59:27 +0000 Received: from [193.82.116.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1LjhJm-0007n2-F9 for rsgb_lf_group@blacksheep.org; Tue, 17 Mar 2009 21:59:26 +0000 Received: from mk-filter-2-a-1.mail.uk.tiscali.com ([212.74.100.53]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1LjhJg-00036d-Fy for rsgb_lf_group@blacksheep.org; Tue, 17 Mar 2009 21:59:26 +0000 X-Trace: 168623406/mk-filter-2.mail.uk.tiscali.com/B2C/$b2c-THROTTLED-DYNAMIC/b2c-CUSTOMER-DYNAMIC-IP/88.106.59.96/None/g4wgt@tiscali.co.uk X-SBRS: None X-RemoteIP: 88.106.59.96 X-IP-MAIL-FROM: g4wgt@tiscali.co.uk X-MUA: Microsoft Office Outlook 11Produced By Microsoft MimeOLE V6.00.2900.3350 X-IP-BHB: Once X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArAHAIu5v0lYajtg/2dsb2JhbACCJitURIU6fYNfxXQHg3UG X-IronPort-AV: E=Sophos;i="4.38,381,1233532800"; d="gif'147?scan'147,208,217,147";a="168623406" Received: from 88-106-59-96.dynamic.dsl.as9105.com (HELO asus) ([88.106.59.96]) by smtp.tiscali.co.uk with ESMTP; 17 Mar 2009 21:59:17 +0000 From: "Gary - G4WGT" To: References: <005501c9a73b$dd0b8ac0$6401a8c0@asus> Date: Tue, 17 Mar 2009 21:59:16 -0000 Message-ID: <007901c9a74b$9e595450$6401a8c0@asus> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 Thread-Index: AcmnQGpNLR16XYh4TuCtDgP6Dpa1XwAB4GUQ X-Karma: unknown: X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,HTML_MESSAGE=0.001 Subject: RE: LF: RE: Who's playing on 503.7 Content-Type: multipart/related; boundary="----=_NextPart_000_007A_01C9A74B.9E595450" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.2 required=5.0 tests=HTML_60_70, HTML_FONTCOLOR_UNKNOWN,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-IP: 193.82.116.20 ------=_NextPart_000_007A_01C9A74B.9E595450 Content-Type: multipart/alternative; boundary="----=_NextPart_001_007B_01C9A74B.9E595450" ------=_NextPart_001_007B_01C9A74B.9E595450 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Andy, >>>> Did the messages about the modified beacon timing software get though this reflector - don't appear to see them in the in box? I received the original & the correction to the url. OK, I used "decode" as the first word that came out of my head. I have looked at the black trace on my beacon chart & it doesn't seem to coincide with the peaks on the blue & green trace, there is a black peak but slightly offset. On my grabber saves there is very high noise level for a couple of minutes some times the blue & green has a peak which shows on the text log as well. But I have also seen very short carriers which I thought at first were part of you normal beacon signal & when looking carefully at the timestamp were at the following times - 1735, 1750 & 1751. At these times there was no burst of noise. Cheers, Gary - G4WGT. _____ From: owner-rsgb_lf_group@blacksheep.org [mailto:owner-rsgb_lf_group@blacksheep.org] On Behalf Of Andy Talbot Sent: 17 March 2009 20:36 To: rsgb_lf_group@blacksheep.org Subject: Re: LF: RE: Who's playing on 503.7 continued ... The black trace gives it away. If there is extended QRM that spans the noise measurement period (which is the WHOLE minute before) and the 5s Tx period it will show up on both. The different system of noise measurement explains why the (no QRMed) green and blue traces are not sitting on top of teh black trace. Ideally, with no signal there, they should. Andy G4JNT www.g4jnt.com 2009/3/17 Andy Talbot I filled in a couple at 1800, deliberately, by flicking the test switch on my beacon Tx. But there are too many peaks on the green annd blue traces to not suspect someone else is firing up a Tx. Its not a case of false decodes - there's not such thing as a 'decode' with this monitoring S/W. All it does is to measure the signal power over precisely this time slot, using a synchronised FFT with a bin size of 0.2Hz, which after windowing gives about 0.4Hz noise bandwidth. So any QRM would have to be quite strong to make a significant impact, and persist over 5 seconds. Short spikes get averaged out to not-a-lot. Did the messages about the modified beacon timing software get though this reflector - don't appear to see them in the in box? If not, http://www.g4jnt.com/beacons.htm at the bottom look for PCBCN Directly, http://www.g4jnt.com/PCBCN.zip Andy G4JNT www.g4jnt.com 2009/3/17 Gary - G4WGT Hi Andy, LF, I have not detected anything here other than your Tx. I was going to e-mail anyway because I have some false decodes on the 5 & 6 minute slots, see list below. These coincide with high bursts of noise which I experience here from time to time. Is there an issue with the decode software being "foxed" by high noise level? Gary - G4WGT. 15:45 40.35 25.76 -240.0 0.0 15:46 41.05 25.76 -240.0 1499.5 15:47 39.52 25.76 -240.0 0.0 16:00 41.70 25.75 -240.0 1499.5 16:01 41.62 25.75 -240.0 1510.6 16:02 31.49 25.75 -240.0 0.0 16:15 40.10 25.47 -240.0 0.0 16:16 30.16 25.47 -240.0 0.0 16:17 29.17 25.47 -240.0 0.0 16:30 37.85 28.93 -240.0 0.0 16:31 41.80 28.93 -240.0 0.0 16:32 36.23 28.93 -240.0 0.0 16:45 40.98 25.80 -240.0 1499.6 16:46 29.45 25.80 -240.0 0.0 16:47 30.17 25.80 -240.0 0.0 17:00 35.23 25.58 -240.0 0.0 17:01 28.35 25.58 -240.0 0.0 17:02 35.28 25.58 -240.0 0.0 17:15 45.32 25.10 -240.0 1499.4 17:16 30.14 25.10 -240.0 0.0 17:17 27.57 25.10 -240.0 0.0 17:30 51.09 25.30 -240.0 1499.5 17:31 53.16 25.30 -240.0 1499.6 17:32 30.18 25.30 -240.0 0.0 17:45 47.93 25.21 -240.0 1499.5 17:46 48.63 25.21 -240.0 1499.5 17:47 49.12 25.21 -240.0 1499.5 18:00 38.75 34.29 -240.0 0.0 18:01 32.01 34.29 -240.0 0.0 18:02 28.89 34.29 -240.0 0.0 18:15 51.36 26.01 -240.0 1499.6 18:16 38.85 26.01 -240.0 0.0 18:17 40.74 26.01 -240.0 0.0 18:30 43.06 24.96 -240.0 1499.5 18:31 29.24 24.96 -240.0 0.0 18:32 29.61 24.96 -240.0 0.0 18:45 36.98 26.26 -240.0 0.0 18:46 34.87 26.26 -240.0 0.0 18:47 36.14 26.26 -240.0 0.0 19:00 50.09 26.57 -240.0 1499.7 19:01 42.04 26.57 -240.0 1518.0 19:02 28.58 26.57 -240.0 0.0 _____ From: owner-rsgb_lf_group@blacksheep.org [mailto:owner-rsgb_lf_group@blacksheep.org] On Behalf Of Andy Talbot Sent: 17 March 2009 19:48 To: rsgb_lf_group@blacksheep.org Subject: LF: Who's playing on 503.7 OK, Who is it? We can see you There's activity in the 5 and 6 minutes slots. Andy G4JNT www.g4jnt.com ------=_NextPart_001_007B_01C9A74B.9E595450 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Andy,

&nb= sp;

>>= >> Did the messages about the modified beacon timing software get though this reflector - don't appear to see them in the in box?

I received the original & the correction to the url.

&nb= sp;

OK, I used “decode” as the first word that came out of my head.

&nb= sp;

I have looked at the black trace on my beacon chart & it doesn’t seem to=20= coincide with the peaks on the blue & green trace, there is a black peak but slightly offset. On my grabber saves there is very high noise level for a couple of minutes some times the blue & green has a peak which shows on=20= the text log as well.

&nb= sp;

But I have also seen very short carriers which I thought at first were part of you normal beacon signal & when looking carefully at the timestamp were at t= he following times – 1735, 1750 & 1751. At these times there was no burst of noise.

&nb= sp;

Cheers,<= o:p>

&nb= sp;

Gary - G4WGT.

&nb= sp;

&nb= sp;

&nb= sp;


From: owner-rsgb_lf_group@blacksheep.org [mailto:owner-rsgb_lf_group@blacksheep.org] On Behalf Of Andy Talbot
Sent: 17 March 2009 20:36
To: rsgb_lf_group@blacksheep.org
Subject: Re: LF: RE: Who's pl= aying on 503.7

 

continued ...

 

The black trace gives it away.  If there is extended=  QRM that spans  the noise measurement period (which is the WHOLE minute before) and the 5s Tx period it will show up on both.   The differ= ent system of noise measurement explains why the (no QRMed) green and blue traces are not sitting on top of teh black trace.   Ideally, with=20= no signal there, they should.


Andy  G4JNT
www.g4jnt.com

2009/3/17 Andy Talbot <andy.g4jnt@google= mail.com>

I filled in a couple at 1800, deliberately, by flicking t= he test switch on my beacon Tx.   But there are too many peaks on the green annd blue traces to not suspect someone else is firing up a Tx.

 

Its not a case of false decodes - there's not such thing=20= as a 'decode' with this monitoring S/W.   All it does is to measure the sig= nal power over precisely  this time slot, using a synchronised FFT wit= h a bin size of 0.2Hz, which after windowing gives about 0.4Hz noise bandwidth.  So any QRM would have to be quite strong to make a significant impact, and persist over 5 seconds.   Short spikes get  averaged out to not-a-lot.

 

Did the messages about the modified beacon timing softwar= e get though this reflector - don't appear to see them in the in box?

 

If not,  http://www.g4jnt.com/beacons.htm at the bottom look for PCBCN

 


Andy  G4JNT
www.g4jnt.com

2009/3/17 Gary - G4WGT <g4wgt@tiscali.co.uk>

 

Hi Andy, LF,

 <= o:p>

I have not detected anyth= ing here other than your Tx.

 <= o:p>

I was going to e-mail any= way because I have some false decodes on the 5 & 6 minute slots, see list below. These coincide with high bursts of noise which I experience here from time to time. Is there an issue with the decode software being “foxed” by high noise level?

 <= o:p>

Gary – G4WGT.

 <= o:p>

15:45  40.35  25.76  -240.0  0.0

15:46  41.05  25.76  -240.0  1499.5

15:47  39.52  25.76  -240.0  0.0

16:00  41.70  25.75  -240.0  1499.5

16:01  41.62  25.75  -240.0  1510.6

16:02  31.49  25.75  -240.0  0.0

16:15  40.10  25.47  -240.0  0.0

16:16  30.16  25.47  -240.0  0.0

16:17  29.17  25.47  -240.0  0.0

16:30  37.85  28.93  -240.0  0.0

16:31  41.80  28.93  -240.0  0.0

16:32  36.23  28.93  -240.0  0.0

16:45  40.98  25.80  -240.0  1499.6

16:46  29.45  25.80  -240.0  0.0

16:47  30.17  25.80  -240.0  0.0

17:00  35.23  25.58  -240.0  0.0

17:01  28.35  25.58  -240.0  0.0

17:02  35.28  25.58  -240.0  0.0

17:15  45.32  25.10  -240.0  1499.4

17:16  30.14  25.10  -240.0  0.0

17:17  27.57  25.10  -240.0  0.0

17:30  51.09  25.30  -240.0  1499.5

17:31  53.16  25.30  -240.0  1499.6

17:32  30.18  25.30  -240.0  0.0

17:45  47.93  25.21  -240.0  1499.5

17:46  48.63  25.21  -240.0  1499.5

17:47  49.12  25.21  -240.0  1499.5

18:00  38.75  34.29  -240.0  0.0

18:01  32.01  34.29  -240.0  0.0

18:02  28.89  34.29  -240.0  0.0

18:15  51.36  2= 6.01  -240.0  1499.6

18:16  38.85  26.01  -240.0  0.0

18:17  40.74  26.01  -240.0  0.0

18:30  43.06  24.96  -240.0  1499.5

18:31  29.24  24.96  -240.0  0.0

18:32  29.61  24.96  -240.0  0.0

18:45  36.98  26.26  -240.0  0.0

18:46  34.87  26.26  -240.0  0.0

18:47  36.14  26.26  -240.0  0.0

19:00  50.09  26.57  -240.0  1499.7

19:01  42.04  26.57  -240.0  1518.0

19:02  28.58  26.57  -240.0  0.0

 <= o:p>

 <= o:p>

 <= o:p>


From: owner-rsgb_lf_group@blacksheep.org [mailto:owner-rsgb_lf_group@blacksheep.org] On Behalf Of Andy Talbot
Sent: 17 March 2009 19:48
To: rsgb_lf_group@blacksheep.org Subject: LF: Who's playing on 503.7

=  

= OK, Who is it? <= o:p>

= We can see you

= There's activity in the 5 and 6 minutes slots.

=  

=  

=
Andy  G4JNT
www.g4jnt.com

 

 

------=_NextPart_001_007B_01C9A74B.9E595450-- ------=_NextPart_000_007A_01C9A74B.9E595450 Content-Type: image/gif; name="image001.gif" Content-Transfer-Encoding: base64 Content-ID: R0lGODlhDAAPAKIFAJh3AP/zxAAAANyuAP/gaP///wAAAAAAACH/C05FVFNDQVBFMi4wAwEA AAAh+QQJAAAFACwAAAAADAAPAAADLVi63P6wjEmrDDjrGYj/H0cIIElwpJmeQweC4hu2BGDf nnjjrLvPLtlJUikWEgAh+QQJAAAFACwAAAAADAAPAAADLVi63M4jyllGuDjHQLr3GyF8I7GN JWpaXxu2IAvMdBfS9coReLzDpspk+HAkAAAh+QQJCgAFACwAAAAADAAPAAADLVi6vPMwlhGq vS+QzXkmQhcSWTiaJNWt3+qpQCxvnzynGmG/uUtOkWBjSCQmAAAh+QQJFAAFACwAAAAADAAP AAADLViz3BowyhWIvZcSgTmhnBd+Q4Vh2pmVBOC+lvbCpDmvpvopTV/8wKBwSCwWEgAh+QQJ CgAFACwAAAAADAAPAAADLVi6vPMwlhGqvS+QzXkmQhcSWTiaJNWt3+qpQCxvnzynGmG/uUtO kWBjSCQmAAAh+QQFAAAFACwAAAAADAAPAAADLVi63M4jyllGuDjHQLr3GyF8I7GNJWpaXxu2 IAvMdBfS9coReLzDpspk+HAkAAA7 ------=_NextPart_000_007A_01C9A74B.9E595450--