Return-Path: X-Spam-DCC: paranoid 1481; Body=3 Fuz1=3 Fuz2=3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on lipkowski.org X-Spam-Level: ** X-Spam-Status: No, score=2.3 required=5.0 tests=BAYES_00,DNS_FROM_AHBL_RHSBL, FORGED_RCVD_HELO,HTML_MESSAGE,HTML_TINY_FONT,SPF_PASS, SUBJECT_ENCODED_TWICE,SUBJECT_EXCESS_BASE64 autolearn=no version=3.1.3 Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by paranoid.lipkowski.org (8.13.7/8.13.7) with ESMTP id u7PIAM1g023488 for ; Thu, 25 Aug 2016 20:10:22 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1bcz1k-0003nZ-DY for rs_out_1@blacksheep.org; Thu, 25 Aug 2016 19:05:20 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1bcz1i-0003nQ-Gv for rsgb_lf_group@blacksheep.org; Thu, 25 Aug 2016 19:05:18 +0100 Received: from smtpcmd0763.aruba.it ([62.149.156.63]) by relay1.thorcom.net with esmtp (Exim 4.87) (envelope-from ) id 1bcz1f-0000Rl-U7 for rsgb_lf_group@blacksheep.org; Thu, 25 Aug 2016 19:05:17 +0100 Received: from ik0vve.net ([62.149.158.90]) by smtpcmd07.ad.aruba.it with bizsmtp id bW5E1t00E1xJdJu01W5E8C; Thu, 25 Aug 2016 20:05:14 +0200 Date: Thu, 25 Aug 2016 20:05:14 +0200 Message-Id: In-Reply-To: References: MIME-Version: 1.0 X-Sensitivity: 3 From: "Max IK0VVE" To: rsgb_lf_group@blacksheep.org X-XaM3-API-Version: V3(R2) X-SenderIP: 212.66.105.4 X-Scan-Signature: edae4bc128aa121544439b7b7cfd26a1 Subject: LF: =?utf-8?b?UmU6IExGOiBzZW5zb3JzIHRoYXQgcHJlZGljdCB3aGVuIHRoZSBOb3J0?= =?utf-8?b?aGVybiBMaWdodHMgd2lsbCBiZSB2aXNpYmxlIGluIHRoZSBVSy4=?= Content-Type: multipart/alternative; boundary="_=__=_XaM3_.1472148314.2A.353647.42.22520.52.42.007.7432938" 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-Scanned-By: MIMEDefang 2.56 on 10.1.3.11 Status: O X-Status: X-Keywords: X-UID: 8623 --_=__=_XaM3_.1472148314.2A.353647.42.22520.52.42.007.7432938 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable =0ADeath to lawnmowers!! (..and to LED lights, plasma TV, microwaves oven= , etc...) :(=0A=0AMax IK0VVE=C2=A0=0A=0A=0A______________________________= =C2=A0...here some of my HAM Radio projects...SkyGeM RotatorAntennaDinami= caRCR-DX=0Awww.ik0vve.net=0A=0A=0ADa: owner-rsgb_lf_group@blacksheep.org=0A= A: rsgb_lf_group@blacksheep.org=0ACc: =0AData: Thu, 25 Aug 2016 14:19:37 = +0100=0AOggetto: LF: sensors that predict when the Northern Lights will b= e visible in the UK.=0A=0A=0A=0A=0A=0A=0A=0A=0A73-G, =0A))=0AA lawnmower = has been blamed for wrongly =0Atriggering sensors that predict when the N= orthern Lights will be visible in the =0AUK.=0AA =0Ared alert issued via = the=C2=A0Aurora =0AWatch mailing list was withdrawn=C2=A0after sensor rea= dings were found to be =0A"spurious".=0AAn =0Ainvestigation revealed a la= wnmower had got too close to one sensor, triggering a =0A"massive spike" = in data.=0AAurora =0AWatch said it was looking into ways to avoid the inc= ident being repeated.=0AThe =0Abogus alert was issued during the afternoo= n of 23 August, after a magnetometer =0Aat the University of Lancaster re= corded a surge in geomagnetic activity.=0ATrim grass=0AAurora =0AWatch is= run by scientists at the university and takes readings from lots of =0Am= agnetometers to work out when the aurora borealis will be visible across = =0ABritain.=0AThe =0Aproject draws on magnetometers in Lancaster, Aberdee= n, the Faroe Islands and =0Afurther field.=0AThe =0Aalert was withdrawn f= our hours after being released as it emerged only =0Aone sensor had recor= ded the spike in activity.=0AA =0Alater update posted to the Aurora Watch= webpage said an investigation had =0Arevealed that a groundskeeper using= a "sit-on mower" to trim grass had been =0Adriving too close to the sens= or, prompting the spike.=0A"We'll =0Awork with the facilities team to try= and avoid an incident such as this =0Aoccurring in the future," said the= scientists.=0AThey =0Aexplained any metal placed on the instrument or ma= chinery operating nearby could =0Atrick it into recording more activity t= han was actually present.=0AReadings =0Afrom the Lancaster sensor were no= t typically used to trigger alerts, they said, =0Abut problems with the m= ain sensor in Aberdeen on 23 August meant it had become =0Athe lead monit= or.=0A --_=__=_XaM3_.1472148314.2A.353647.42.22520.52.42.007.7432938 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

Death to = lawnmowers!! (..and to LED lights, plas= ma TV, microwaves oven, etc...) :(

Max IK0VVE 

=
=

______________________________

 
...here some of my HAM Radio projects...



=0A
Da: owner-rsgb_lf_= group@blacksheep.org
=0A
A: rsgb_lf_group@blac= ksheep.org
=0A
Cc:
=0A
Data: Thu, 25 Aug 2016 14:19:37 +0100
=0A
Oggetto: LF: sensors that predict when the Northern Lights will be visib= le in the UK.
=0A
=0A=0A=0A=0A=0A=0A
=0A

73-G, =0A))

=0A

A lawnmower has been blamed fo= r wrongly =0Atriggering sensors that predict when the Northern Lights wil= l be visible in the =0AUK.

=0A

A =0Ared alert issued via the Aurora =0AWatch mailing list was with= drawn after sensor = readings were found to be =0A"spurious".

=0A

An =0Ainvestigation reveal= ed a lawnmower had got too close to one sensor, triggering a =0A"massive = spike" in data.

=0A

Aurora =0AWatch said it was looking into ways to av= oid the incident being repeated.

=0A

The =0Abogus alert was issued duri= ng the afternoon of 23 August, after a magnetometer =0Aat the University = of Lancaster recorded a surge in geomagnetic activity.

=0A

Trim grass

=0A

Aurora =0AWatch is run by scienti= sts at the university and takes readings from lots of =0Amagnetometers to= work out when the aurora borealis will be visible across =0ABritain.

= =0A

The =0Aproject draws on magnetometers in Lancaster, Aberdeen, the Faro= e Islands and =0Afurther field.

=0A

The =0Aalert was withdrawn four hou= rs after being released as it emerged only =0Aone sensor had reco= rded the spike in activity.

=0A

A =0Alater update posted to th= e Aurora Watch webpage said an investigation had =0Arevealed that a groun= dskeeper using a "sit-on mower" to trim grass had been =0Adriving too clo= se to the sensor, prompting the spike.

=0A

"We'll =0Awork with the faci= lities team to try and avoid an incident such as this =0Aoccurring in the= future," said the scientists.

=0A

They =0Aexplained any metal placed o= n the instrument or machinery operating nearby could =0Atrick it into rec= ording more activity than was actually present.

=0A

Readings =0Afrom th= e Lancaster sensor were not typically used to trigger alerts, they said, = =0Abut problems with the main sensor in Aberdeen on 23 August meant it ha= d become =0Athe lead monitor.

=0A
--_=__=_XaM3_.1472148314.2A.353647.42.22520.52.42.007.7432938--