Message from discussion
Nanode network problem
Received: by 10.216.139.223 with SMTP id c73mr1745499wej.1.1325265726441;
Fri, 30 Dec 2011 09:22:06 -0800 (PST)
X-BeenThere: nanode-users@googlegroups.com
Received: by 10.180.97.232 with SMTP id ed8ls39223934wib.3.gmail; Fri, 30 Dec
2011 09:22:05 -0800 (PST)
Received: by 10.180.98.70 with SMTP id eg6mr830374wib.2.1325265725892;
Fri, 30 Dec 2011 09:22:05 -0800 (PST)
Received: by 10.180.98.70 with SMTP id eg6mr830373wib.2.1325265725884;
Fri, 30 Dec 2011 09:22:05 -0800 (PST)
Return-Path: <nig...@googlemail.com>
Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170])
by gmr-mx.google.com with ESMTPS id fw1si26658926wbb.0.2011.12.30.09.22.05
(version=TLSv1/SSLv3 cipher=OTHER);
Fri, 30 Dec 2011 09:22:05 -0800 (PST)
Received-SPF: pass (google.com: domain of nig...@googlemail.com designates 209.85.212.170 as permitted sender) client-ip=209.85.212.170;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of nig...@googlemail.com designates 209.85.212.170 as permitted sender) smtp.mail=nig...@googlemail.com; dkim=pass (test mode) header...@googlemail.com
Received: by wicr5 with SMTP id r5so16385761wic.1
for <nanode-users@googlegroups.com>; Fri, 30 Dec 2011 09:22:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlemail.com; s=gamma;
h=message-id:from:to:references:subject:date:mime-version
:content-type:content-transfer-encoding:x-priority:x-msmail-priority
:x-mailer:x-mimeole;
bh=ruDHjMlkpSI/EwRvCl2a7/FQ1ob+bdWYNxwa+Z+fmVM=;
b=D4r87s22yQDBt/k/n6sYKRp/O7j9gQUucaZX56vYMgRS++KRqeSM2jE5de7Ta4WsU7
qDWJLj4jl33WFgqJ5zOhqi1oOyuuErE34VCV+sMgoyZ518ThkkNFvarm9unbtgOMw4+v
AJYkWgFd4G4ygObUtSt4UtTF+HMQpA9AeBcsU=
Received: by 10.180.101.35 with SMTP id fd3mr77420287wib.22.1325265725831;
Fri, 30 Dec 2011 09:22:05 -0800 (PST)
Return-Path: <nig...@googlemail.com>
Received: from Freya (host109-151-141-84.range109-151.btcentralplus.com. [109.151.141.84])
by mx.google.com with ESMTPS id 1sm93854139wiz.11.2011.12.30.09.22.04
(version=TLSv1/SSLv3 cipher=OTHER);
Fri, 30 Dec 2011 09:22:05 -0800 (PST)
Message-ID: <EC97F9AD10F04BA1BD6655D19945DA8C@Freya>
From: "Nigel Worsley" <nig...@googlemail.com>
To: <nanode-users@googlegroups.com>
References: <35a85786-6857-411a-acca-012bc8cad...@t13g2000yqg.googlegroups.com> <001501ccc1b0$74b90870$5e2b1950$@org> <a83b5763-9d7f-4efe-b75c-cced45e6c...@p41g2000yqm.googlegroups.com> <b55acc5c-272f-40df-aa70-e5687f6a2...@u6g2000vbg.googlegroups.com> <CAG-W1H_+irv3BfyUw=zBDk3TLDqWVETMv8Pq1uYLyW4B8mA...@mail.gmail.com> <e0c3481c-1763-4d41-9b52-6d9851e14...@j10g2000vbe.googlegroups.com>
Subject: Re: Nanode network problem
Date: Fri, 30 Dec 2011 17:21:38 -0000
MIME-Version: 1.0
Content-Type: text/plain;
format=flowed;
charset="iso-8859-1";
reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512
mikethebee wrote:
> BTW I am missing 1 of the 7 ceramic 100nF caps in this
> second kit, is there any 1 that I could miss out and still use the N5RF?
If you aren't using analogue inputs then the one closest to pin 14 of the ENC28J60 can be omitted. The analogue inputs
should still work but there will be a lot of noise on the readings.
Nigle