Return-Path: Sender: "Marvin Kaye" To: lml@lancaironline.net Date: Sun, 17 Oct 2004 09:29:00 -0400 Message-ID: X-Original-Return-Path: Received: from rwcrmhc11.comcast.net ([204.127.198.35] verified) by logan.com (CommuniGate Pro SMTP 4.2.5) with ESMTP id 476051 for lml@lancaironline.net; Sun, 17 Oct 2004 08:40:51 -0400 Received-SPF: none receiver=logan.com; client-ip=204.127.198.35; envelope-from=edechazal@comcast.net Received: from cc1860069a (pcp09040864pcs.rocsth01.mi.comcast.net[69.244.182.42]) by comcast.net (rwcrmhc11) with SMTP id <2004101712402201300t4g51e>; Sun, 17 Oct 2004 12:40:22 +0000 X-Original-Message-ID: <00a601c4b446$282f10a0$6401a8c0@rocsth01.mi.comcast.net> From: X-Original-To: "Lancair Mailing List" References: Subject: S-TEC 50 Problem - LNC2 X-Original-Date: Sun, 17 Oct 2004 08:38:08 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00A3_01C4B424.A0C98440" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 This is a multi-part message in MIME format. ------=_NextPart_000_00A3_01C4B424.A0C98440 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I've got an S-TEC 50 autopilot installed in my 360. Altitude hold no = longer works properly. A few months ago some of you gave me advice on = looking at the pitch servo and possibly the pressure transducer. The = pitch servo meets factory specs, I was able to determine. The pressure = transducer, however, appears flaky. Probing the back of the connector = indicates an open circuit in the signal path in the transducer. = Although this could be the contact inside the connector too, since I was = only able to probe the harness side. The transducer seemed to work on = the bench (signal moved properly with pressure change, but my setup = could not rule out intermittencies). I removed the connector and = attached the leads directly to the male pins on the transducer with = higher quality female contacts. Result seemed better than before, but a = full down command still occurred, and the system hunted excessively (50 = foot excursions up and down). I'm going to wire it so that I can monitor the output signal during = flight and during commanded excursions to try to catch the culprit in = the act. =20 Do any of you have an S-TEC pressure transducer you are not using (you = switched to Tru-Trak) that you'd be willing to part with? Thanks, Ed de Chazal ------=_NextPart_000_00A3_01C4B424.A0C98440 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

I've got an S-TEC 50 = autopilot=20 installed in my 360. Altitude hold no longer works properly. = A few=20 months ago some of you gave me advice on looking at the pitch servo and = possibly=20 the pressure transducer. The pitch servo meets factory specs, I = was able=20 to determine. The pressure transducer, however, appears = flaky. =20 Probing the back of the connector indicates an open circuit in the = signal path=20 in the transducer. Although this could be the contact inside the = connector=20 too, since I was only able to probe the harness side. The=20 transducer seemed to work on the bench (signal moved properly with = pressure=20 change, but my setup could not rule out intermittencies). I removed = the=20 connector and attached the leads directly to the male pins on the = transducer=20 with higher quality female contacts. Result seemed better = than=20 before, but a full down command still occurred, and the system hunted=20 excessively (50 foot excursions up and down).

I'm going to wire it so = that I can=20 monitor the output signal during flight and during commanded excursions = to try=20 to catch the culprit in the act.

Do any of you = have an=20 S-TEC pressure transducer you are not using (you switched to = Tru-Trak) that=20 you'd be willing to part with?

Thanks,

Ed de=20 Chazal

------=_NextPart_000_00A3_01C4B424.A0C98440--