X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Wed, 07 Nov 2007 09:46:33 -0500 Message-ID: X-Original-Return-Path: Received: from smtp0.av-mx.com ([137.118.16.56] verified) by logan.com (CommuniGate Pro SMTP 5.2c1) with ESMTP id 2459316 for lml@lancaironline.net; Tue, 06 Nov 2007 23:00:50 -0500 Received-SPF: pass receiver=logan.com; client-ip=137.118.16.56; envelope-from=pinetownd@volcano.net Received: from DennisDell (63-170-119-42.dsl.volcano.net [63.170.119.42]) (Authenticated sender: pinetownd@volcano.net) by smtp0.av-mx.com (Postfix) with ESMTP id 0486F1BF3E1 for ; Tue, 6 Nov 2007 23:00:13 -0500 (EST) X-Original-Message-ID: <00f701c820f2$b12ed4f0$6601a8c0@DennisDell> From: "Dennis Johnson" X-Original-To: "Lancair Mailing List" Subject: Fuses vs. Breakers X-Original-Date: Tue, 6 Nov 2007 20:00:08 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00F4_01C820AF.A1C75520" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 This is a multi-part message in MIME format. ------=_NextPart_000_00F4_01C820AF.A1C75520 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable >You fuse guys must have thought about this. What's the = counter-argument? I've strived to design my electrical system to avoid nuisance trips. I = don't expect the fuses to blow in my Legacy any more often than they = blow in my car, which is close to never. Therefore, if an electronic = device goes dead in flight, I'll leave it alone until I'm on the ground = because it most likely blew due to a fault. I do not want to do = electrical troubleshooting in flight. Once I get on the ground, I can = devote 100% of my attention to troubleshooting and repair. In your example, if the trim stops working, it doesn't matter to me if = the fuse blew or the servo is toasted. Either way, the trim's not = working and it's not coming back. If the fuse blew, it's very likely = due to a fault, so I wouldn't want to reset it even if I could. If the = servo's toasted, no amount of resetting a breaker is going to make it = come back, and could add to the trouble. =20 For my situation, I'm happy with fuses but I know that other people are = equally happy with breakers. I don't believe that there is a wrong and = a right way regarding breakers vs. fuses. We can fabricate equally good = electrical systems either way. =20 Best, Dennis Johnson Legacy =20 =20 =20 ------=_NextPart_000_00F4_01C820AF.A1C75520 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable

>You fuse guys must have thought about = this. =20 What's the counter-argument?

I've strived to design my electrical system to avoid = nuisance=20 trips. I don't expect the fuses to blow in my Legacy any more = often than=20 they blow in my car, which is close to never. Therefore, = if an=20 electronic device goes dead in flight, I'll leave it alone until = I'm on the=20 ground because it most likely blew due to a fault. I do not want = to do=20 electrical troubleshooting in flight. Once I get on the ground, I can devote 100% of my = attention to=20 troubleshooting and repair.

In your example, if the trim stops working, it doesn't = matter to=20 me if the fuse blew or the servo is toasted. Either way, the = trim's not=20 working and it's not coming back. If the fuse blew, it's very = likely due=20 to a fault, so I wouldn't want to reset it even if I could. If the = servo's=20 toasted, no amount of resetting a breaker is going to make it come back, = and=20 could add to the trouble.

For my situation, I'm happy with fuses but I know = that other=20 people are equally happy with breakers. I don't believe that there = is a=20 wrong and a right way regarding breakers vs. fuses. We can = fabricate=20 equally good electrical systems either = way.

Best,

Dennis Johnson

Legacy

------=_NextPart_000_00F4_01C820AF.A1C75520--