X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Thu, 20 Apr 2006 01:50:38 -0400 Message-ID: X-Original-Return-Path: Received: from vms042pub.verizon.net ([206.46.252.42] verified) by logan.com (CommuniGate Pro SMTP 5.0.9) with ESMTP id 1074156 for lml@lancaironline.net; Thu, 20 Apr 2006 01:30:56 -0400 Received: from jacky0da39824a ([71.111.168.219]) by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IY0005GA9ZG8FC3@vms042.mailsrvcs.net> for lml@lancaironline.net; Thu, 20 Apr 2006 00:30:56 -0500 (CDT) X-Original-Date: Wed, 19 Apr 2006 22:30:47 -0700 From: "Tom Gourley" Subject: Re: [LML] Re: Avionics: Black Art or Science X-Original-To: "Lancair Mailing List" Reply-to: "Tom Gourley" X-Original-Message-id: <000f01c6643b$94bde9c0$650610ac@jacky0da39824a> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Mailer: Microsoft Outlook Express 6.00.2900.2869 Content-type: text/plain; format=flowed; charset=iso-8859-1; reply-type=response Content-transfer-encoding: 7bit X-Priority: 3 X-MSMail-priority: Normal References: Someone once wrote, "Any sufficiently advanced technology is indistinguishable from magic." Depending on your personal technology level some of this stuff, especially the things that can go wrong, seems like magic. Heck, I'm an engineer and have spent a (depressingly) large amount of time in my career chasing down slippery problems. (But then if it weren't for problems there would be an awful lot of unemployed engineers.) Of course, once you get the problem fixed and look back at how you arrived at the solution you invariably think, this should have been obvious! Ah, the wonders of 20/20 hindsight. Have fun chasing those electrons. Tom Gourley ----- Original Message ----- From: "Marvin Kaye" To: "Lancair Mailing List" Sent: Wednesday, April 19, 2006 7:56 PM Subject: [LML] Re: Avionics: Black Art or Science > Posted for "Halle, John" : > > Brent writes (below) that electrons follow rules that can (sooner or > later) > be understood through the use of reason. Reminds me of the story about > the > lawyer who wrote a one-page legal document and sent a bill for $500 with a > single item: "draft document: $500." The client objected that it could > not > have taken more than a half hour to write the document. The lawyer sent > back > a revised bill with two items: 1. "draft document: $50"; 2. "knowing what > to > write: $450." > Having just finished replacing my panel, I must, at least superficially > agree > with Brent. The problem is that, as anyone who has ever looked at the > back of > a modern instrument panel knows, there are electrons going through > hundreds of > wires. Some of them are carrying digital data (whether the electrons are > analog or not) that may be AIRINC, RS232 or something else, some are > carrying > a simple current that is used to power something; some are carrying a > current > that is used to transmit data. A huge number of them are going to > something > called "ground", a simple concept until you try to actually do it right. > They > go to and from various boxes that have unbelievebly complex circuits > etched > onto chips and other devices. These boxes either do or don't talk to each > other using protocols understood only by software engineers. In theory we > don't have to understand how all this works because all we have to do is > follow the installation and setup directions, 100% of which are wrong or > incomplete in some respect and many of which are almost totally wrong or > incomplete. If something is not working properly, there are usually at > least > ten possible explanations that occur even to a non-engineer, to say > nothing of > the fifty explanations that occur to engineers. Each one of these > explanations involves the assumption that electrons follow simple rules > that > can be understood through the use of reason. The black art is knowing > which > explanation to investigate first. > > -- > For archives and unsub http://mail.lancaironline.net/lists/lml/ >