Delivered-To: daveyxm@virginmedia.com Received: by 10.50.203.68 with SMTP id ko4csp210503igc; Tue, 8 Apr 2014 06:16:14 -0700 (PDT) X-Received: by 10.180.211.207 with SMTP id ne15mr31706862wic.31.1396962973241; Tue, 08 Apr 2014 06:16:13 -0700 (PDT) Return-Path: Received: from post.thorcom.com (post.thorcom.com. [195.171.43.25]) by mx.google.com with ESMTP id ic2si878992wjb.24.2014.04.08.06.16.12 for ; Tue, 08 Apr 2014 06:16:13 -0700 (PDT) Received-SPF: neutral (google.com: 195.171.43.25 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org) client-ip=195.171.43.25; Authentication-Results: mx.google.com; spf=neutral (google.com: 195.171.43.25 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org) smtp.mail=owner-rsgb_lf_group@blacksheep.org; dkim=pass header.i=@googlemail.com Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1WXVN6-0006gR-Dq for rs_out_1@blacksheep.org; Tue, 08 Apr 2014 13:43:24 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1WXVN5-0006gI-S5 for rsgb_lf_group@blacksheep.org; Tue, 08 Apr 2014 13:43:23 +0100 Received: from mail-ee0-f47.google.com ([74.125.83.47]) by relay1.thorcom.net with esmtps (TLSv1:RC4-SHA:128) (Exim 4.82) (envelope-from <73dk7fc@googlemail.com>) id 1WXVN4-0004OW-1Z for rsgb_lf_group@blacksheep.org; Tue, 08 Apr 2014 13:43:22 +0100 Received: by mail-ee0-f47.google.com with SMTP id b15so627935eek.20 for ; Tue, 08 Apr 2014 05:43:20 -0700 (PDT) X-DKIM-Result: Domain=googlemail.com Result=Good and Known Domain DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Y3EmfpiNe/ek67ayO4oGiIvIIVow/O8fuj4lEqqEs0E=; b=d5eOGsTvbkfm5ncjoYAIzcgr49/smO3VNN2Kife2zGIRMGgdSwGllMQ2iNxr8C9Sp2 BDfjvnrh45HWASY6m/sxdLCQCJuSOHB2xuC3UmYmHKfwboBhI/wvPm+6BmlUzNxv5aDg vP3yIdmcQefnAkKswxGB+LdJ+MrFx1sO7/pjdgY7Zjgc0QEFwVUy/HFy/d/Zt3bUwUyk HpducSKJHz3t1pGtAdJNwGmGWX4Q1TXfmxcY9phdI1JJ1roLVlYXCxvbZ46tya/6FAyS gsbZ2pdur409hgNWkPVgxQ2+Brht7riF0AsJH49MPPdl+CFYTFw1gZ4mYHt/75YlGQHg IDVw== X-Received: by 10.14.194.133 with SMTP id m5mr4335870een.38.1396961000210; Tue, 08 Apr 2014 05:43:20 -0700 (PDT) Received: from [129.206.22.206] (pc206.iup.uni-heidelberg.de. [129.206.22.206]) by mx.google.com with ESMTPSA id u46sm4460588eel.1.2014.04.08.05.43.19 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 08 Apr 2014 05:43:19 -0700 (PDT) Message-ID: <5343EEE6.4010708@gmail.com> Date: Tue, 08 Apr 2014 14:43:18 +0200 From: DK7FC <73dk7fc@googlemail.com> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org References: <53430770.60406@gmail.com> <534319AD.3080900@gmx.net> In-Reply-To: <534319AD.3080900@gmx.net> X-Spam-Score: -0.7 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Hi Tobias, Am 07.04.2014 23:33, schrieb Tobias DG3LV: > [...]it would be best to first express your design-target in more detail: > > What minimum audio/IF-bandwith is acceptable for the MF/LF-receiver? Well, for MF and LF, 10 kHz would be sufficient. For VLF, 24 or even 48 kHz would be fine. If it is possible (data rate (meanwhile i think i learned to calculate the data rate ;-) )) to use a 1 MHz sample rate ADC, then one could directly sample VLF to MF !! That may be the best option, because then there is no need to use an extra converter. This reduces the complexity of the circuit and the power consumption, i assume. So the limiting factor would be the bandwidth of the 2.4 Ghz device. I found some with 2 Mbps, also ready to use modules (don't want to spend to much time with that GHz stuff). With a ADC covering VLF to MF, one just may need a few notch filters for stronger local out of band stations. OK, the answer to your question: 500 kHz. [...] 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 [74.125.83.47 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (73dk7fc[at]googlemail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Scan-Signature: b08ad821341ca291e1fd930f7b9292d3 Subject: Re: LF: A question to the experts Content-Type: text/plain; charset=ISO-8859-15; format=flowed 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.3 required=5.0 tests=FROM_HAS_MIXED_NUMS 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 Hi Tobias, Am 07.04.2014 23:33, schrieb Tobias DG3LV: > [...]it would be best to first express your design-target in more detail: > > What minimum audio/IF-bandwith is acceptable for the MF/LF-receiver? Well, for MF and LF, 10 kHz would be sufficient. For VLF, 24 or even 48 kHz would be fine. If it is possible (data rate (meanwhile i think i learned to calculate the data rate ;-) )) to use a 1 MHz sample rate ADC, then one could directly sample VLF to MF !! That may be the best option, because then there is no need to use an extra converter. This reduces the complexity of the circuit and the power consumption, i assume. So the limiting factor would be the bandwidth of the 2.4 Ghz device. I found some with 2 Mbps, also ready to use modules (don't want to spend to much time with that GHz stuff). With a ADC covering VLF to MF, one just may need a few notch filters for stronger local out of band stations. OK, the answer to your question: 500 kHz. > What minimum dynamic range (in dB) is acceptable? This has directly to do with the bits of the ADC, i learned. Well, for a directy sampling of the 2200m band we have to deal with DCF39 and HGA22 here. And if the 'far end device' has to be compact and has to deal with high temperature differences, we can't use complex high Q coils to get an extreme rejection of DCF39... Thus, i think we need at least 100 dB of dynamic range. So, from what i saw from the data sheets, we would need a 24 bit device. I also learned that it is not possible just to connect the 2 SPI ports of the two devices. So it becomes more complex. > What is the distance to be covered by the link-connection ? 2km or 3 km. It all depends of what is possible! I will need high gain yagis on both sides. But these are quite cheap avaliable at amazon or ebay. > Optical sight ? Yes. > Is it possible to erect a (small, DIN A4) solar power module at the > MF/LF-receiver site? Maybe, if necessary, yes. But it will be more expensive and more risky of someone discovers and damages the setup when hanging in a tree in the forest. Thus i would like to keep the costs below 50 EUR, the costs of the far end system. It is not my private property so it must be hidden in a high tree that i can climb. > Shall the MF/LF-receiver be operated 24/7 ? Yes. Ideally VLF to MF. But there can be compromises. Actually MF was the main focus. So, 8 kHz of BW and 80 dB dynamic range and 16 bit would be ok too. You see, the specifications are not totally fixed. It depends on what is possible. The limiting factor will be the data rate and the costs and the power consumption of the far end device. > What program will be used at your site in the institut, spectrum lab > or different? SpecLab! But i don't know, when i would use that 1 MHz sample rate ADC, it may be more useful to realise a direct digital link, USB or LAN. This may have advantages but then the system becomes not so flexible for others. > > Knowing this (and probably more) could help to design a suitable > link-connection between the remote MF/LF-receiver and your windows-PC. > The technology to be used cannot be specified without knowing this. Yes that is clear of course. But as you see there is a wide range of wishes and possibilities and limiting factors. Generally it would be nice to play arround with this stuff and get a sloution as useful as possible. So what is possible? And are there other factors that i don't see yet? Maybe the stability of the GHz link over that distance? At least i like the idea to learn about this stuff but i am on the first small steps. It looks like a completely different world of electronics to me! And it looks like all the informations are available in the web. The twente web SDR shows what is possible! But i don't need a solution reaching up to 30 MHz. 0...500 kHz is fine! > > 73 de dg3lv Tobias > (you have received this text in german language a week ago) Did i? Is that right, 500 kHz BW and 24 bit = 12 Mbps ? It may appear embrassing to demonstrate my limits of knowledge about that digital stuff but i decided to stay self-reliant here. These limits can be pushed in one evening i know. It just wasn't necessary so far... 73, Stefan/DK7FC