Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by klubnl.pl (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id x0ALQEpg029876 for ; Thu, 10 Jan 2019 22:26:26 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1ghhkL-0006Rs-TH for rs_out_1@blacksheep.org; Thu, 10 Jan 2019 21:20:13 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1ghhjC-0006RX-E5 for rsgb_lf_group@blacksheep.org; Thu, 10 Jan 2019 21:19:02 +0000 Received: from viper.bpweb.net ([83.223.106.10]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91_59-0488984) (envelope-from ) id 1ghhj5-0001om-Tw for rsgb_lf_group@blacksheep.org; Thu, 10 Jan 2019 21:18:57 +0000 X-BpAuth: neil-g4dbn-uk Received: from [10.50.254.3] (neilsmith22.plus.com [81.174.129.86]) (authenticated bits=0) by viper.bpweb.net (8.14.4/8.14.4) with ESMTP id x0ALIc1e030081 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Thu, 10 Jan 2019 21:18:53 GMT To: rsgb_lf_group@blacksheep.org References: <1762043626.20190104174530@gmail.com> <9410247640.20190104185544@gmail.com> <1624085399.20190106110624@gmail.com> <1288743451.20190107142430@gmail.com> <5C336344.7010308@posteo.de> <5C352132.60005@posteo.de> <966331036.24087972.1546987477866@mail.yahoo.com> <5C35A030.90307@posteo.de> <2011563744.17492551.1547024300896@mail.yahoo.com> <6DB8451D7F3D3947A5918808A59621EA3151334E@servigilant.vigilant.local> <732048151.1004617.1547061181611@mail.yahoo.com> <56342861547142038@sas1-890ba5c2334a.qloud-c.yandex.net> <150673862.26005583.1547145453262@mail.yahoo.com> From: Neil Message-ID: Date: Thu, 10 Jan 2019 21:18:33 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <150673862.26005583.1547145453262@mail.yahoo.com> Content-Language: en-GB X-Antivirus: Avast (VPS 190110-2, 10/01/2019), Outbound message X-Antivirus-Status: Clean X-BpTo: X-Spam-Score: -0.7 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: This sounds interesting. Can you point at any published results to explain what technique was used, what power was used to obtain those results, and how the signal was launched? I imagine lots of peop [...] Content analysis details: (-0.7 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low trust [83.223.106.10 listed in list.dnswl.org] 0.0 HTML_MESSAGE BODY: HTML included in message X-Scan-Signature: bf9cd6b3d49c805062abf73a1027fea8 Subject: Re: VLF: GOTA Content-Type: multipart/alternative; boundary="------------A85AD770D5287DD402561B47" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.5 required=5.0 tests=HTML_20_30,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 This is a multi-part message in MIME format. --------------A85AD770D5287DD402561B47 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit This sounds interesting. Can you point at any published results to explain what technique was used, what power was used to obtain those results, and how the signal was launched? I imagine lots of people are considering the use of long lengths of metal infrastructure (on private land, with the express permission of the landowner), so if there is a solution which is demonstrably better, it would save a lot of unnecessary trouble for experimenters. Do you have any numbers comparing the technique used in these experiments against those obtained from using long lengths of armco or metal fencing or huge bridges, (putting aside any arguments about the rights and wrongs).  It would be good to see a documented comparison to show by what margin the experimental technique used is superior to using low steel structures with a large horizontal extent. Neil On 10/01/2019 18:37, David Hine wrote: > ... TX connexions to motorway > > guard rails, railway infrastructure, electric / gas supply utilities > and fences etc. are totally unnecessary for the transmitting of ELF > > signals. > > These DO NOT make good VLF / ELF TX antennas .. --------------A85AD770D5287DD402561B47 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

This sounds interesting. Can you point at any published results to explain what technique was used, what power was used to obtain those results, and how the signal was launched? I imagine lots of people are considering the use of long lengths of metal infrastructure (on private land, with the express permission of the landowner), so if there is a solution which is demonstrably better, it would save a lot of unnecessary trouble for experimenters.

Do you have any numbers comparing the technique used in these experiments against those obtained from using long lengths of armco or metal fencing or huge bridges, (putting aside any arguments about the rights and wrongs).  It would be good to see a documented comparison to show by what margin the experimental technique used is superior to using low steel structures with a large horizontal extent.

Neil

On 10/01/2019 18:37, David Hine wrote:
... TX connexions to motorway 

guard rails, railway infrastructure, electric / gas supply utilities and fences etc. are totally unnecessary for the transmitting of ELF 

signals. 

These DO NOT make good VLF / ELF TX antennas ..
--------------A85AD770D5287DD402561B47--