X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Fri, 17 Aug 2007 15:36:25 -0400 Message-ID: X-Original-Return-Path: Received: from mta13.adelphia.net ([68.168.78.44] verified) by logan.com (CommuniGate Pro SMTP 5.1.11) with ESMTP id 2268604 for lml@lancaironline.net; Fri, 17 Aug 2007 10:06:21 -0400 Received-SPF: pass receiver=logan.com; client-ip=68.168.78.44; envelope-from=glcasey@adelphia.net Received: from [75.82.253.35] by mta13.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20070817140541.RUBI20883.mta13.adelphia.net@[75.82.253.35]> for ; Fri, 17 Aug 2007 10:05:41 -0400 Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: References: Content-Type: multipart/alternative; boundary=Apple-Mail-1-746426653 X-Original-Message-Id: <6B57404B-6799-4852-B480-9FC77AC068F0@adelphia.net> From: Gary Casey Subject: Re: Vision Micro Problem X-Original-Date: Fri, 17 Aug 2007 07:05:40 -0700 X-Original-To: "Lancair Mailing List" X-Mailer: Apple Mail (2.752.2) --Apple-Mail-1-746426653 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed I'm not too familiar with the Vision system, but I've made several million MAP sensors (only a few came back. Honest...). THere is almost no way the sensor itself could fail that way, so I would almost guarantee there is blockage in the line or port. They probably use a small MEMS sensor more likely than not the same one you can buy from the Newark catalog and it has a very small pressure port. The might have positioned it close to the outside of the box so that its port protrudes or it is inside connected with a short hose that could be kinked. If the sensor port is exposed you can look into it, but shouldn't stick a wire in it as the sense element might be the first thing the wire hits. Very fragile. Gary On Aug 17, 2007, > From: "Randy" > Date: August 16, 2007 6:19:17 PM PDT > To: lml@lancaironline.net > Subject: Vision Micro Problem > > > Has anyone had a problem with their VisionMicro 1000 MAP sensor? > Mine is reading very very slow. It's solid and I checked all the > wiring. I connected a vacuum pump to it today and when I run the > pressure down the VM 1000 will start to read lower and lower but it > takes about 10 seconds for it to change a very small amount. EX: > from 27 to 10 might take 4 ~ 5 minutes, and back again the same. > It seems like the MAP sensor is reading right but takes forever to > change... Anyone see this, or fixed the same problem? > Thanks, > Randy Stuart > LNC2 --Apple-Mail-1-746426653 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1 I'm not too familiar with the = Vision system, but I've made several million MAP sensors (only a few = came back.=A0 Honest...).=A0 THere is almost no way the sensor itself = could fail that way, so I would almost guarantee there is blockage in = the line or port.=A0 They probably use a small MEMS sensor more likely = than not the same one you can buy from the Newark catalog and it has a = very small pressure port.=A0 The might have positioned it close to the = outside of the box so that its port protrudes or it is inside connected = with a short hose that could be kinked.=A0 If the sensor port is exposed = you can look into it, but shouldn't stick a wire in it as the sense = element might be the first thing the wire hits.=A0 Very = fragile.
Gary
On Aug 17, 2007,=A0
From: "Randy" <randystuart@hotmail.com>
Date: August 16, 2007 6:19:17 PM = PDT
To: lml@lancaironline.net
Subject: Vision Micro = Problem

=
Has anyone had a problem = with their VisionMicro 1000 MAP sensor? Mine is reading very very slow. = It's solid and I checked all the wiring. I connected a vacuum pump to it = today and when I run the pressure down the VM 1000 will start to read = lower and lower but it takes about 10 seconds for it to change a very = small amount. EX: from 27 to 10 might take 4 ~ 5 minutes, and back again = the same.
It seems like the MAP sensor is reading right but takes = forever to change... Anyone see this, or fixed the same = problem?
Thanks,
Randy Stuart
=
LNC2
= --Apple-Mail-1-746426653--